05-12-2010 02:40 PM - edited 03-19-2019 12:56 AM
Hi - Our customer has AD Telephone Number field and CUCM DNs defined as pure +E164 numbers.
This works great for dialling, however, when we try to assign CUPC softphone and deskphone modes to CUCM DNs that are defined in the \+XXXXXXXXXX format the softphone receives a connection refused error and the Desk Phone receives a CTI error. When we remove the \+ string from the DN both softphone and deskphone mode work ok.
A packet capture looks to be appending %5C to replace the \ delimeter in the SIP URI.
Is there anyway we can support \+XXXXXXXXXX DN formatting in CUCM with CUPC?
thanks again (Michael )
Brian
Solved! Go to Solution.
05-12-2010 03:09 PM
This is a known bug in the public 7.0(2) version of CUPC. Cisco had published a 7.0(2a) version but that has since been recinded due to its own issues. You will need to open a TAC case for special file access.
The bug toolkit appears to be nonresponsive today or I would look up the defect ID for you as well.
05-12-2010 04:21 PM
Bug ID was "CSCsz13100 CUPC registration fails if the DN in callmanager is defined with \+ ".
Per release note, this bug was fixed in the CUPC 7.1.1 release (downloadable from CCO).
http://www.cisco.com/en/US/docs/voice_ip_comm/cupc/7_1/english/release/notes/cupc71.html#wp98843
Michael
05-12-2010 03:09 PM
This is a known bug in the public 7.0(2) version of CUPC. Cisco had published a 7.0(2a) version but that has since been recinded due to its own issues. You will need to open a TAC case for special file access.
The bug toolkit appears to be nonresponsive today or I would look up the defect ID for you as well.
05-12-2010 04:21 PM
Bug ID was "CSCsz13100 CUPC registration fails if the DN in callmanager is defined with \+ ".
Per release note, this bug was fixed in the CUPC 7.1.1 release (downloadable from CCO).
http://www.cisco.com/en/US/docs/voice_ip_comm/cupc/7_1/english/release/notes/cupc71.html#wp98843
Michael
05-12-2010 04:27 PM
Jonathan / Michael - thanks very much again, will look at 7.1.x rather than renumber the customer dial plan (as i had just managed to convince them to move to +e164!)
thanks
Brian
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: