- Blue, 1500 points or more
I am looking at designing a dial plan for a client who has sites in several European countries.
I am toying with the idea of using fully qualified PSTN numbers as directory numbers for phones - e.g. +442081234567
I will be using CUCM 7.1(x) and so should not have any issues doing this for basic phone connectivity but am wondering how other applications will cope with the + sign in the DN.
The apps that will be deployed are Unity Connection 7.1(x) and Unified Contact Center Express 7.0(x).
Can anyone tell me whether these apps support + sign and, if not, what the workarounds are and if such support is roadmapped.
Finally if anyone has any experiences they wish to share with this type of dial plan I would be interested to hear about them.
CCX does not support E.164 at all according to the BU. Until SR5 introduced
/* Style Definitions */
mso-padding-alt:0in 5.4pt 0in 5.4pt;
font-family:"Times New Roman","serif";}
CSCtg90305 it worked fine as long as you didn't create E.164-formatted IPCC Extensions. Reporting and CAD display the information properly. You may want to consider this CSS/Partition setup as well: https://supportforums.cisco.com/message/3047257#3047257 I use this combined with E.164 dial plans and it works out well because I can give the user the same extension for both IPCC and normal extensions... or at least they think it's the same which allows returning missed calls and all to work seamlessly.
As for Unity Connections, the limitation is the Extension field which does not support E.164 yet because a user needs to be able to enter the value through DTMF. You can deal with this by assigning the non-E.164 formatted version (e.g. last four digits) and then putting the full E.164 version in the MWI and Alternate Number fields instead.