I’m running into an issue where Asterisk 16.0.1 will randomly reject SIP INVITE messages, claiming that the SDP contains invalid attributes. I say ‘randomly’ since my SIP clients always send INVITE messages with the same structure, but Asterisk only encounters problems parsing the SDP some of the time.
ERROR: pjproject:0 <?>: sip_inv.c .Error parsing/validating SDP body: Invalid SDP attributes (PJMEDIA_SDP_EINATTR)
This problem occurs about 10% of the time when using the Speex codec, but I have also seen it happen with PCMA, albeit far less often. Asterisk responds with “400 Bad Request”. I have verified in Wireshark that the SIP/SDP of accepted and rejected INVITE messages are in fact identical (apart from dynamic elements such as the URI and ports, naturally). Speex SDP is attached. Could race conditions be at play? Is this a known issue?
SDP as seen in Wireshark:
Session Description Protocol Version (v): 0
Owner/Creator, Session Id (o): Test 123 123 IN IP4 126.96.36.199
Session Name (s): CaptureME
Connection Information ©: IN IP4 188.8.131.52
Time Description, active time (t): 0 0
Media Description, name and address (m): audio 49835 RTP/AVP 110
Media Attribute (a): rtpmap:110 speex/8000
Media Attribute (a): fmtp:110 mode=“3,any”
Media Attribute (a): sendrecv
I’m currently trying to find a way to reliably reproduce the issue. My program contains multiple SIP endpoints that attempt to call a ConfBridge conference at startup. The more clients I spin up, the more likely I am to encounter the issue.
Thanks in advance for you help!