Preview Tool

Cisco Bug: CSCtd69174 - MOC RCC failed when DN is e.164

Last Modified

Jul 04, 2017

Products (1)

  • Cisco Unified Communications Manager IM & Presence Service

Known Affected Releases


Description (partial)

MOC RCC will fail  when DN of device/endpoint is configured as an E.164 number (e.g +1 408 123 4567), in CUCM, the dn is configured as \+14081234567, and when tel URI (line URI) in AD/OCS is configured as the following format:


MOC RCC will work when in CUCM, the dn is configured as 14081234567, and when the tel URI is configured as:


When MOC RCC failed as above, it failed in ctigw authorization:

12/03/2009 07:06:42.762 ESP|PID(15623) mod_sip_ctigw.c(2174) Authorizing user (testuser.35 DN (+14081234567) DEV (SEP00260B5D48D9) Partition (INTERNAL)

12/03/2009 07:06:42.762 ESP|Thu Dec 03 07:06:42 2009] PID(15623) mod_sip_ctigw.c(1634) CTIGW DB query : execute procedure GetMOCLineAppearanceInEffect('testuser.35', '', '+14081234567', 'SEP00260B5D48D9', 'UK-INTERNAL')

12/03/2009 07:06:42.778 ESP|PID(15623) mod_sip_ctigw.c(2235) The tel uri specified for user testuser.35 is invalid

12/03/2009 07:06:42.779 ESP|PID(15623) mod_sip_ctigw.c(6126) ctigw_csta_handler:: FAIL AUTHORIZED userID=testuser.35 line=+14081234567, device=SEP00260B5D48D9


Dn is configured as e.164 in CUCM.
Microsoft server type is configured as Microsoft server OCS
Bug details contain sensitive information and therefore require a account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.