Unsupported SIP Malformed Request

[Shane_Stratys]

Hi,

I currently have a new v18 setup, and a unsupported trunk provider setup for IP based authentication running metaswitch. I am able to see the SIP Invite come in from the provider, however I am receiving a "Malformed SIP Request received" error. Both the provider and I are not sure which part of the SIP message is malformed. Would appreciate any help on identifying how to fix this error.

07/21/2021 2:39:27 AM - Malformed SIP request received:
BadSip Recv Req INVITE from 8.14.139.8:5060 tid=-2588430fb3af565b62824a766033556f1-8.14.139.8-1 [email protected]:
INVITE sip:[email protected]:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 8.14.139.8:5060;rport=5060;branch=z9hG4bK-2588430fb3af565b62824a766033556f1-8.14.139.8-1
Max-Forwards: 69
Contact: "MOUNTAIN VW CA" <sip:[email protected]:5060>
To: <sip:[email protected]>
From: "MOUNTAIN VW CA" <sip:[email protected]:5060>;tag=8.14.139.8+1+219e29+22daca50
Call-ID: [email protected]
CSeq: 60000479 INVITE
Expires: 180
Alert-Info: Alert-info strings for Distinctive ringing
Content-Type: application/sdp
Organization: Metaswitch Networks
Supported: resource-priority, siprec, 100rel
Allow-Events: message-summary, refer, dialog, line-seize, presence, call-info, as-feature-event, calling-name
P-Asserted-Identity: "MOUNTAIN VW CA" <sip:[email protected]:5060>
Content-Length: 122

Thanks all!

 

[karrj@londontechnologyser]

We encountered this as well. Almost identical, even down to the Metaswitch. We were able to make outbound calls, but inbound calls would fail at 10 seconds. First with that invite, followed by a malformed cancel request.

After scratching our heads for weeks, we finally decided to rebuild the trunk on both ends.

We were able to fix it by turning ON ip based authentication at the switch and we started using that. You'll want to assign an auth did in 3cx for the trunk also (right under the use ipBased Auth drop down on SIP setup).

The other change we made when rebuilding was the carrier didn't assign any did's to the trunk @Metaswitch.

I missed it, but I see you are already setup for IP based authentication. If you would be interested in switching trunk providers, send me a DM.