Brand new CUC 8.6 installation and integrating to CUCM 8.6. Is there a standard DN to start the VM ports at? Is there a consideration for these ports if your DN scheme is 5 digits vs. 4 digits?
Our old cluster (CCM 4.2 & Unity 4.2) has VM ports that are 4 digits, but we started out using 4 digit phone DN's as well. We have since moved to 5 digit phone DN's. I'm just wondering if in our new cluster if I should choose 5 digit DN's for the VM ports. Thanks!
Personally, I usually use long digit lengths, or SIP trunking.
SIP trunking just requires a pilot number, so you don't have to worry about port DNs at all.
If you have a system with 150 ports, and 2 servers, that's 300 numbers which is a big chunk out of a 4 digit dial plan. I would pick one 'voicemail' DN, and then append three 0's on the end - e.g. on a 4 digit plan I might use:
1000 - voicemail pilot
1001 - voicemail DNs (actually use 1001001 to 1001300)
That way if you expand your voicemail system you can easily add another 600 ports without worrying about getting messy by going up to 1002 which you might be using etc.
As was said earlier, the numbers should never be dialed directly. The only thing I would add is to put them into their own Partition. That way you can ensure that they can't be called and won't conflict with anything else in the dialing plan. Only the VM pilot number should be in a regular, dialable partition.
I am with Aaron here, I've purely deployed SIP integrated UCONs to CUCM in the last 2/3 years and it simplifies things quite bit. My typical approach to assigning port DNs in the past was to use non-DID range at the location the servers are hosted, so if UCON 1 is in site A where allocated non-DIDs are 85010000 - 85010999 I would pick something from that range, but ultimately as others said it should not matter.
Not really, just make sure you setup the SIP trunk on CUCM properly i.e. check diversion header checkboxes, and ensure Route Pattern(s) do not use "use external phone number mask" as these 2 items are common mistakes folks make.
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...