[asterisk-bugs] [JIRA] (ASTERISK-30015) Video calls getting 400 response after chrome update 100.0.4896.75-1

[Josh Hogan (JIRA)]

Josh Hogan created ASTERISK-30015:
-------------------------------------

             Summary: Video calls getting 400 response after chrome update 100.0.4896.75-1
                 Key: ASTERISK-30015
                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-30015
             Project: Asterisk
          Issue Type: Bug
      Security Level: None
          Components: pjproject/pjsip
    Affects Versions: 18.11.1, 18.8.0
            Reporter: Josh Hogan
            Severity: Major


Using the most recent chrome update (100.0.4896.75-1) when initiating a *video* call generates a longer SDP section for INVITE packets.
This seems to exceed the upper limit of PJMEDIA_MAX_SDP_ATTR.
Asterisk responds with a 400 response to the INVITE, and the call fails to start.

Here are the asterisk error logs
sdp.c .Error adding media attribute, attribute is ignored: Too many objects of the specified type (PJ_ETOOMANY)
**repeats above error several times**
sdp.c .Error adding media attribute, attribute is ignored: Too many objects of the specified type (PJ_ETOOMANY)
sip_inv.c .Error parsing/validating SDP body: Missing SDP rtpmap for dynamic payload type (PJMEDIA_SDP_EMISSINGRTPMAP)`

We noticed that on an older version of chrome (99.0.4844.84-1) the INVITE packet was not as long so the issue did not occur.
When chrome was updated to the newest version (100.0.4896.75-1) we started getting these errors, and 400 responses from Asterisk.

[Here is a diff of the two INVITES](https://www.diffchecker.com/GXFq5nYm)

Although the chrome update isn't necessarily the bad guy here, it was the catalyst that triggered this issue.

I can confirm that the fix of increasing the PJMEDIA_MAX_SDP_ATTR did fix the issue and the errors no longer occurred.

Temporary fix
#define PJMEDIA_MAX_SDP_ATTR   (PJMEDIA_MAX_SDP_FMT*3 + 4)


Here is a link to the discussion
https://community.asterisk.org/t/invite-from-some-chrome-webrtc-clients-rejected-with-pjmedia-sdp-emissingrtpmap/92199/2



--
This message was sent by Atlassian JIRA
(v6.2#6252)