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

[Marco Capetta]

Hi,

you don't need to edit any line in webrtc code, but simply to setup the
'transport protocol' of the PEER (not the one of the subscriber) to RTP/AVP.

I noticed you are having many problems in setting up your SPCE system.
I suggest you to contact our sales (sales at sipwise.com) to understand how we
can help you in this process.
Thank you

Marco


On Thu, Aug 15, 2024 at 8:41 PM Pa Ka <pa.ka12 at outlook.com> wrote:

> 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>
> *Sent:* Wednesday, August 14, 2024 16:11
> *To:* spce-user at lists.sipwise.com <spce-user at lists.sipwise.com>
> *Cc:* mcapetta at sipswise.com <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>
> *Sent:* Wednesday, August 14, 2024 1:47 AM
> *To:* 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»
>


-- 

Sipwise GmbH | an Alcatel-Lucent Company
Leonard-Bernstein-Straße 10 | 1220 Wien
Email: invoice at sipwise.com <gfuchs at sipwise.com>
Website: https://www.sipwise.com

Particulars according Austrian Companies Code paragraph 14
Geschäftsführer: DI Dr. Gernot Fuchs      Sitz: Wien             FG:
Landesgericht Wien              FN: 305595f
Die übermittelten Informationen sind ausschließlich dem Empfänger
vorbehalten und können vertrauliches oder privilegiertes Material
enthalten. Ein Gebrauch, Weiterleitung oder Verbreitung in jeglicher Form
seitens Dritter ist nicht gestattet. Sollten Sie diese Nachricht irrtümlich
erhalten haben, bitten wir Sie, sich mit dem Absender in Verbindung zu
setzen und die Nachricht einschließlich der Anlagen zu löschen. Jegliche
nicht autorisierte Nutzung dieser E-Mail ist illegal.
Hinweis zum Datenschutz: Sipwise GmbH ist der Schutz Ihrer Daten wichtig.
Auch durch die Kommunikation per E-Mail werden personenbezogene Daten
ausgetauscht. Erfahren Sie mehr unter: www.sipwise.com

Managing Director: DI Dr. Gernot Fuchs     HQ: Vienna       FG: Vienna
Regional Court        FN: 305595f
Confidentially notice. This e-mail transmission may contain legally
privileged and/or confidential information. Please do not read it if you
are not the intended recipient(s). Any use, reproduction or disclosure by
any other person is prohibited. If you have received this e-mail in error,
please notify the sender and destroy the original transmission and its
attachments without reading or saving it in any manner. Any unauthorized
use of this e-mail is illegal.
Note on data protection: Sipwise GmbH attaches great importance to the
protection of your data. Personal data is also exchanged through
communication by e-mail. Learn more at: www.sipwise.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20240819/a0df815d/attachment.htm>