Cisco Bug: CSCtd00332 - SIP Call with TLS rejected with 400 response
Jan 31, 2017
- Cisco IOS
- Cisco 6500/7600 Series Multiprocessor WAN Application Module
Known Affected Releases
Symptoms: When call comes with Contact header having an unsupported transport type (like TLS in Cisco IOS Release 12.4), then the call is immediately rejected with 400 bad request response. The call is rejected even if the SIP INVITE has Record-Route header with transport as non-TLS (TCP or UDP). Conditions: This issue can be seen when a proxy sits between two SIP UAs and is interworking between the two UA for the transport. For example, if the Originating UA uses TLS and the Terminating UA uses non- TLS (TCP or UDP), the proxy forwards the INVITE from the Originating UA to the Terminating UA with the same Contact header (having the TLS as the transport). However, the proxy adds the Record-Route header to indicate that the responses/subsequent requests should go via the proxy using non-TLS transport. Here, the Terminating UA is Cisco SIP-TDM gateway.
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