Solved Cisco CUBE Malformed SIP

[r-yang]

Hi,

We are currently trying to integrate a new 3CX server with an existing Cisco CUBE via SIP trunk, and 3CX is logging 'malformed SIP' when trying to make or receive a call.

It logs on all SIP messages from it, but I cannot see anything obviously wrong with the headers - has anybody had this issue before?

03/31/2022 10:20:06 AM - Malformed SIP request received:
BadSip Recv Req INVITE from 10.100.100.100:12792 tid=E292623A2 Call-ID=[email protected]:
INVITE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/TCP 10.100.100.100:5060;branch=z9hG4bKE292623A2
Max-Forwards: 28
Contact: <sip:[email protected]:5060;transport=tcp>
To: <sip:[email protected]>
From: <sip:[email protected]>;tag=A495DF3-25B3
Call-ID: [email protected]
CSeq: 101 INVITE
Expires: 300
Min-SE: 1800
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Call-Info: <sip:10.100.100.100:5060>;method="NOTIFY;Event=telephone-event;Duration=2000"
Content-Disposition: session;handling=required
Content-Type: application/sdp
Date: Thu, 31 Mar 2022 10:20:06 AWST
Supported: 100rel, timer, resource-priority, replaces, histinfo, sdp-anat
Timestamp: 1648693206
User-Agent: Cisco-SIPGateway/IOS-16.6.3
Allow-Events: telephone-event
P-Asserted-Identity: <sip:[email protected]>
History-Info: <sip:[email protected]:5060>;index=1
Cisco-Guid: 3933085748-2949583340-2964256986-2701345534
Session-ID: 01212b5157d350a683bf556d50f4c280;remote=00000000000000000000000000000000
Content-Length: 302

v=0
o=CiscoSystemsSIP-GW-UserAgent 4484 5228 IN IP4 10.100.100.100
s=SIP Call
c=IN IP4 10.100.100.100
t=0 0
m=audio 10090 RTP/AVP 8 100 101
c=IN IP4 10.100.100.100
a=rtpmap:8 PCMA/8000
a=rtpmap:100 X-NSE/8000
a=fmtp:100 192-194
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20




03/31/2022 10:20:12 AM - Malformed SIP request received:
BadSip Recv Req CANCEL from 10.100.100.100:12792 tid=E292623A2 Call-ID=[email protected]:
CANCEL sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/TCP 10.100.100.100:5060;branch=z9hG4bKE292623A2
Max-Forwards: 70
To: <sip:[email protected]>
From: <sip:[email protected]>;tag=A495DF3-25B3
Call-ID: [email protected]
CSeq: 101 CANCEL
Date: Thu, 31 Mar 2022 10:20:06 AWST
Timestamp: 1648693212
Reason: Q.850;cause=16
Session-ID: 01212b5157d350a683bf556d50f4c280;remote=00000000000000000000000000000000
Content-Length: 0

Thanks!

Ryan

 

[r-yang]

OK we've found a fix for this - I found the very helpful post here, which led me to check our 'Date' header;

Date: Thu, 31 Mar 2022 10:20:06 AWST

While the Date header wasn't null in our case, I did notice that the time zone had been set to AWST, whereas the SIP protocol specifies that GMT is the only supported time zone.

The better solution would likely be to set this to GMT, however as we are on an existing production system we added a SIP profile to drop the Date header from all SIP packets just on our 3CX dial peer;

voice class sip-profiles 2003
request ANY sip-header Date Remove
response ANY sip-header Date Remove

dial-peer voice 2003 voip
voice-class sip profiles 2003

Calls are now going through OK.

 

[YiannisH_3CX]

Glad to see your issue has been resolved and thank for you for sharing your solution with the community.