Cisco Bug: CSCta32019 - UCM can't process SIP SDP with a audio m line with port 0
Jul 06, 2017
- Cisco Unified Communications Manager (CallManager)
Known Affected Releases
Symptom: UCM can't process SIP SDP with a audio m line with port 0. Manifests to user as dropped calls or other unexpected call behavior when using SIP call signaling protocol. Conditions: Third party SIP IVR trying to put call hold on by sending below message v=0 c=IN IP4 0.0.0.0 t=0 0 m=audio 0 RTP/AVP 0 101 a=rtpmap:0 PCMU/8000 UCM code does not handle this combination of parameters.
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