When it happens
- SDP sent with a wrong Content-Type, or a multipart body the far end cannot read.
What to check
- Check the Content-Type header and disable multipart bodies (for example, with ISUP) towards that peer.
What the response looks like
SIP/2.0 415 Unsupported Media Type
Via: SIP/2.0/UDP 203.0.113.10:5060;branch=z9hG4bK776asdhds
From: <sip:101@pbx.example>;tag=1928301774
To: <sip:+15551234567@pbx.example>;tag=a6c85cf
Call-ID: a84b4c76e66710@203.0.113.10
CSeq: 2 INVITE
Reason: Q.850;cause=79;text="Service or option not implemented, unspecified"
Content-Length: 0