[Index]

Model: data/GlobalSIPVMDPProfile

Dial Plan Profile

Full HTML Help

Tip

Use the Action search to navigate Automate

On the Dial Plan Profile page, an advanced administrator can define all of the dial plan elements that make up the CUC integration.

Note

You can only add a SIP integration once a dial plan profile is configured.

You will need to complete at least the following mandatory fields:

You can configure details on this page with static (exact) values if you wish to deploy these same values over and over at store level. Typically, this option is not used.

At the Provider hierarchy, macros are used to make the profile portable across several customers. For example, if you had two or three different versions of dial plans, then you would have two or three versions of this profile. The lower level administrators could then apply the profiles as required.

pre-configured Dial Plan Framework for Global VM SIP Integrations

Model Details: data/GlobalSIPVMDPProfile

Title Description Details
Profile Name Friendly Name for Voicemail Dial Plan Profile
  • Field Name: name
  • Type: String
Device Pool
  • Field Name: cucmDevicePool
  • Type: String
SIP Profile SIP Profile
  • Field Name: cucmSipProfile
  • Type: String
SIP Trunk Security Profile SIP Trunk Security Profile
  • Field Name: cucmStsprofile
  • Type: String
Route Group Route Group
  • Field Name: cucmRouteGroup
  • Type: String
Route List Route List
  • Field Name: cucmRouteList
  • Type: String
SIP Trunk Inbound CSS SIP Trunk Inbound CSS
  • Field Name: cucmSipTrunkInCSS
  • Type: String
SIP Trunk ReRouting CSS SIP Trunk ReRouting CSS
  • Field Name: cucmSipTrunkReRouteCSS
  • Type: String
Call Manager Group Call Manager Group
  • Field Name: cucmCMG
  • Type: String
Voicemail Pilot CSS Voicemail Pilot CSS
  • Field Name: cucmVMPCSS
  • Type: String
Voicemail Route Pattern Partition Partition that the phones can dial
  • Field Name: cucmRoutePatternPartition
  • Type: String
Notes Notes for tooling
  • Field Name: notes
  • Type: String