Cisco Bug: CSCuo56103 - CUCM treats as SIPS call even if its not a proper SIPS URI
Aug 27, 2019
- Cisco Unified Communications Manager (CallManager)
Known Affected Releases
Symptom: CUCM reject the incoming call by replying 301 Redirect to the specified contact. Conditions: CUCM looks for a "sips:" string in the contact header, if found, then treats it as sips call even if its not a URI at all. Below is a sample contact header which have SIP and SIPS. Contact: "ABC" <sip:XXXX@22.214.171.124:5060;gsid=af887e60-ad6f-11e3-a3d4-0050568630b3;epv=%3csips:50009%40rmit.edu.au%3bgr%3d8ed8d01a7f0adeef70ad320d06d2fafe%3e;transport=tcp There is only one URI there in Contact header, it is sip:XXXX@126.96.36.199:5060 sips:50009%40rmit.edu.au%3bgr%3d8ed8d01a7f0adeef70ad320d06d2fafe%3e is not a URI at all. CUCM looks for SIPS in the contact header and treats as SIPS call. As per RFC , CUCM should look for Valid SIP URI or SIPS URI in the contact header.
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)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases