Preview Tool

Cisco Bug: CSCsz24623 - priCSS is NOT populated in SsRedirectCallReq from CTI causing Callfailur

Last Modified

Feb 22, 2014

Products (1)

  • Cisco Unified Communications Manager (CallManager)

Known Affected Releases


Description (partial)


Intermittently 911 Call Redirect from CER to CUCM fails with :

JTAPI-PROTOCOL-7-UNK:(P1- received Response: {
  sequenceNumber = 655
  result         = -1932787660
  description    = redirect failure

Get following error message in CER event logs :

"Emergency call from 5555 could not be routed using the following Routepatterns. 5000.911--48551126 Call Routed to 5000.911--48551127 Please check the availability of the above routes.Also,Check for the following error conditions.  1)If FAC and/or CMC are configured on the route patterns used for CER, please disable them.  2)If the "Calling Party Number Modification" flag on the CER user page in the call manager is not enabled, please enable it."

The reason for this error message is when the call is routed back from CER to CUCM using 911 CTI RP, for the failed calls it doesn't use the CSS of the CTI RP (which has access to Route pattern, 5000911) but of the Calling device ( Ip phone, which doesn't have access to the route pattern). In both cases JTAPI sends the same call redirect request with "callingsearchspace = 2". 


CER integrated with CUCM 6.x
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.