Guest

Preview Tool

Cisco Bug: CSCvs47225 - CUCM documentation - Port in Call-Info Header with purpose=x-cisco-origIP is ignored

Last Modified

Jan 20, 2020

Products (1)

  • Cisco Unified Communications Manager (CallManager)

Known Affected Releases

12.5(1.10000.22)

Description (partial)

Symptom:
When CUCM receives a SIP Invite where the Call-Info header is populated with a purpose=x-cisco-origIP value, CUCM ignores the port in this value and looks for a trunk with the IP from that field along with the port that the INVITE came in via.

Example:
1) CUCM Receives an invite from CVP (IP: 1.1.1.2) on port 5069 with this header:

Call-Info: <sip:1.1.1.1:5060>;purpose=x-cisco-origIP

2) CUCM looks for a trunk that is 1.1.1.1 with a port of 5069.

This occurs because CVP has no knowledge of the SIP Trunk Security Profiles configured on CUCM.  Since it can't know what port to put in the Call-Info header, it just uses the default of 5060.

The SIP Profile help page incorrectly states that the port is used for call redirection, when it is not:

https://<CUCM_IP>:8443/Help/en_US/ccm/ctx/index.html?CUCM_RF_S11B8BF2_00_sip-profile-settings.html#ccm_sipprofile

Call-Info Header with purpose=x-cisco-origIP—If the SIP trunk uses a Customer Voice Portal (CVP) or a Back-to-Back User Agent (B2BUA), choose this option. When the incoming request is received, Cisco Unified Communications Manager parses the Call-Info header, looks for the parameter, purpose=x-cisco-origIP, and uses the IP address or domain name and the signaling port number that is specified in the header to reroute the call to the SIP trunk that uses the IP address and port. If the parameter does not exist in the header or no SIP trunk is identified, the call occurs on the SIP trunk on which the call arrived.

Two things need to be done here:
1) Remove the following from the paragraph from the SIP Profile help page:
'and the signaling port number'
2) Add a second paragraph stating that the listening port on both trunks need to match for this header to be used correctly.

Conditions:
N/A
Bug details contain sensitive information and therefore require a Cisco.com 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.