[Spce-user] 400 Invalid SDP body - mr12.4.1

[Pa Ka]

I managed to resolve this issue. The main issue is caused by the JsSIP and SipJS agent sending an incompatible protocol (UDP/TLS/RTP/SAVPF).

I modified the line below in the SIPjs code (web phone use this framework) to send RTP/AVP protocol.

sessionDescriptionHandlerModifiers

resolved

From: Pa Ka <pa.ka12 at outlook.com>
Sent: Thursday, August 15, 2024 2:34 AM
To: spce-user at lists.sipwise.com
Cc: mcapetta at sipwise.com
Subject: Re: 400 Invalid SDP body - mr12.4.1

I think the Invalid SDP body error message is caused by media transport protocol. Web phone(web phone from the customer selfcare with JsSip) send UDP/TLS/RTP/ASVP. While the pstn switch was execting a different protocol (bes RTP/AVP)

Even if , i changed the transport protocol for both domain and subscriber preference under Nat and Media flow to RTP/AVP, the web phone keeps sending  a different protocol.

Is it possible fix that in ngcp?


________________________________
From: Pa Ka <pa.ka12 at outlook.com<mailto:pa.ka12 at outlook.com>>
Sent: Wednesday, August 14, 2024 16:11
To: spce-user at lists.sipwise.com<mailto:spce-user at lists.sipwise.com> <spce-user at lists.sipwise.com<mailto:spce-user at lists.sipwise.com>>
Cc: mcapetta at sipswise.com<mailto:mcapetta at sipswise.com> <mcapetta at sipswise.com<mailto:mcapetta at sipswise.com>>
Subject: RE: 400 Invalid SDP body - mr12.4.1

Hello, I think the issue is cause by this unknow attribute the web phone sends. The same issue with the Sipwise web phone from the customer self-care web interface. It sends these unknow attribute.


I updated the config.yml to remove line start with these attributes via: remove_line_startswith:

the loadbalancer removes those lines in the invite. However, the proxy doesn't remove them. Any lead would be appreciated.

Aug 14 16:04:30 sips ngcp-sems[180831]: [#7efc1f56c6c0] [attr_check, AmSdp.cpp:1591] DEBUG:  unknown attribute: rtcp-rsize
Aug 14 16:04:30 sips ngcp-sems[180831]: [#7efc1f56c6c0] [attr_check, AmSdp.cpp:1591] DEBUG:  unknown attribute: rtcp-rsize
Aug 14 16:04:30 sips ngcp-sems[180831]: [#7efc1f56c6c0] [attr_check, AmSdp.cpp:1591] DEBUG:  unknown attribute: oldmediaip
Aug 14 16:04:30 sips ngcp-sems[180831]: [#7efc1f56c6c0] [attr_check, AmSdp.cpp:1591] DEBUG:  unknown attribute: rtcp
Aug 14 16:04:30 sips ngcp-sems[180831]: [#7efc1f56c6c0] [attr_check, AmSdp.cpp:1591] DEBUG:  unknown attribute: crypto
Aug 14 16:04:30 sips ngcp-sems[180831]: [#7efc1f56c6c0] [attr_check, AmSdp.cpp:1591] DEBUG:  unknown attribute: crypto
Aug 14 16:04:30 sips ngcp-sems[180831]: [#7efc1f56c6c0] [attr_check, AmSdp.cpp:1591] DEBUG:  unknown attribute: crypto
Aug 14 16:04:30 sips ngcp-sems[180831]: [#7efc1f56c6c0] [attr_check, AmSdp.cpp:1591] DEBUG:  unknown attribute: crypto
Aug 14 16:04:30 sips ngcp-sems[180831]: [#7efc1f56c6c0] [attr_check, AmSdp.cpp:1591] DEBUG:  unknown attribute: crypto
Aug 14 16:04:30 sips ngcp-sems[180831]: [#7efc1f56c6c0] [attr_check, AmSdp.cpp:1591] DEBUG:  unknown attribute: crypto
Aug 14 16:04:30 sips ngcp-sems[180831]: [#7efc1f56c6c0] [attr_check, AmSdp.cpp:1591] DEBUG:  unknown attribute: crypto
Aug 14 16:04:30 sips ngcp-sems[180831]: [#7efc1f56c6c0] [attr_check, AmSdp.cpp:1591] DEBUG:  unknown attribute: crypto
Aug 14 16:04:30 sips ngcp-sems[180831]: [#7efc1f56c6c0] [attr_check, AmSdp.cpp:1591] DEBUG:  unknown attribute: crypto
Aug 14 16:04:30 sips ngcp-sems[180831]: [#7efc1f56c6c0] [attr_check, AmSdp.cpp:1591] DEBUG:  unknown attribute: crypto
Aug 14 16:04:30 sips ngcp-sems[180831]: [#7efc1f56c6c0] [attr_check, AmSdp.cpp:1591] DEBUG:  unknown attribute: crypto
Aug 14 16:04:30 sips ngcp-sems[180831]: [#7efc1f56c6c0] [attr_check, AmSdp.cpp:1591] DEBUG:  unknown attribute: crypto
Aug 14 16:04:30 sips ngcp-sems[180831]: [#7efc1f56c6c0] [attr_check, AmSdp.cpp:1591] DEBUG:  unknown attribute: setup
Aug 14 16:04:30 sips ngcp-sems[180831]: [#7efc1f56c6c0] [attr_check, AmSdp.cpp:1591] DEBUG:  unknown attribute: fingerprint
Aug 14 16:04:30 sips ngcp-sems[180831]: [#7efc1f56c6c0] [attr_check, AmSdp.cpp:1591] DEBUG:  unknown attribute: tls-id

From: Pa Ka <pa.ka12 at outlook.com<mailto:pa.ka12 at outlook.com>>
Sent: Wednesday, August 14, 2024 1:47 AM
To: spce-user at lists.sipwise.com<mailto:spce-user at lists.sipwise.com>
Subject: 400 Invalid SDP body - mr12.4.1

Hi, kindly guide me on how to resolve this issue below

FusionPBX is registered to spce via Gateway.
Calls initated from the fusionPBX returns the error below. Sngrep returns 400 Invalid SDP body error.

Aug 14 01:38:15.999565 sips proxy[3824]: NOTICE: FAILURE_ROUTE_LEG_B <script>: *** Failure route for leg-b call, code='400' - R=<sip:E.14 at pstnIP:5060;transport=udp> ID=<3ed635f8-d4a2-123d-5d9b-6045bd5f9da7_b2b-1> UA='<null>'

Aug 14 01:38:16.000011 sips proxy[3821]: NOTICE: REPLY_ROUTE_NAT <script>: NAT-Reply - S=400 - Invalid SDP body M=INVITE IP=<MP fusionpbx IP>:<53205> (<127.0.0.1>:<5080>) ID=<3ed635f8-d4a2-123d-5d9b-6045bd5f9da7> UA='<null>' DESTIP=<127.0.0.1>:<6052>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20240815/19c75966/attachment.htm>