Preview Tool

Cisco Bug: CSCuq20108 - From header to getting truncated when using escaped characters.

Last Modified

May 28, 2020

Products (3)

  • Cisco Unified Communications Manager (CallManager)
  • Cisco Intercompany Media Engine
  • Cisco Unified Communications Manager Version 10.0

Known Affected Releases


Description (partial)

If the From header sent to a recording server exceeds 231 characters, the header will get truncated if escaped characters are found.  if the From header contains escaped characters, (i.e. %40), the dynamic buffer allocation doesn't account for this resulting in characters getting truncated.

For example:

Should be: x-farendaddr=905053663562
But it's coming through as: x-farendaddr=9050536635

Logs show the following:

20339440.029 |16:17:08.165 |AppInfo |//SIP/SIPHandler/ccbId=0/scbId=0/setFromUriInContainer: calculate otherParamLength
20339440.030 |16:17:08.165 |AppInfo |//SIP/SIPHandler/ccbId=0/scbId=0/setFromUriInContainer: otherParamLength=254 > MAX_SIP_OTHER_PARAMS_LEN
20339440.031 |16:17:08.165 |AppInfo |//SIP/SIPHandler/ccbId=0/scbId=0/setFromUriInContainer: copy otherparmsBuf = x-nearend;x-refci=18244183;x-nearendclusterid=StandAloneCluster;x-nearenddevice=SEPB4B676E28BC3;x-nearendaddr=8001;x-farendrefci=18244182;x-farendclusterid=StandAloneCluster;x-farenddevice=S0/SU0/;x-farendaddr=9050536635 to buff

From header to recording server exceeds 231 characters and contains escaped characters.

Related Community Discussions

Mediasense Search and Play Missing Part of the Incoming Phone Number
I have configured Mediasense and am recording calls successfully, thanks to the users of this community.  My helpdesk manager brought something to my attention today.  He said  in the Search and Play application, that when a recording is created, it shows the dial-in number and the receiving extension number.  The dial-in number, if it is external, is missing 2 digits, either at the end or in the middle.  I can't find any reason for this. Any help would be appreciated.
Latest activity: Mar 01, 2017
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.