[Freeswitch-users] SIP over WSS responding with 5060; transport=udp in Contact:

[Ciprian Dosoftei]

Hi Nathan,

If you could provide the full SIP trace for a sample, that would be great.

While the Contact header is indeed typically pointing back at the standard
SIP IP/port combination (i.e. non-WebSocket), most JS SIP client library
gracefully work around it (even without rport hints).

Do you use a public stack for the client portion or a implementation?

-Ciprian

On Mon, 30 Sep 2019 at 13:46, Nathan Stratton <nathan at robotics.net> wrote:

> I am using SIP over WebSockets on port 443, most things work correctly,
> but when I terminate a call that is ringing I can't because port and
> transport are wrong.
>
> Incoming WSS port 443:
>
> recv 461 bytes from wss/[50.246.121.173]:34738 at 17:03:00.035305:
> ------------------------------------------------------------------------
> SIP/2.0 180 Ringing
> Via: SIP/2.0/WSS 18.211.78.106:443;rport;branch=z9hG4bKvNgc7Dy2r4rHS
> From: "Beth User" <sip:beth at 18.211.78.106>;tag=B1564gFygm3jN
> To: <sip:r6ucrocm at 3val7ifjblg6.invalid;transport=ws;received=
> 50.246.121.173:34738>;tag=aa53u3jvjt
> CSeq: 10377697 INVITE
> Call-ID: ff8ac04a-5e46-1238-2787-0251a831415e
> Supported: outbound
> User-Agent: nathan at stage.illumy1.com
> Contact: <sip:r6ucrocm at 3val7ifjblg6.invalid;transport=ws>
> Content-Length: 0
>
> Outgoing WSS port 443:
>
> send 760 bytes to wss/[50.246.121.173]:34010 at 17:03:00.061145:
> ------------------------------------------------------------------------
> SIP/2.0 180 Ringing
> Via: SIP/2.0/WSS
> vg5qpm92h7dm.invalid;branch=z9hG4bK2823219;received=50.246.121.173;rport=34010
> From: "beth at stage.illumy1.com" <sip:beth at stage.illumy1.com>;tag=ukhk0sdsd9
> To: <sip:nathan at stage.illumy1.com>;tag=9eKN1tDQp2pDe
> Call-ID: reo4ds005e1qlr4784v8
> CSeq: 2 INVITE
> Contact: <sip:nathan at 18.211.78.106:5060;transport=udp>
> User-Agent: FreeSWITCH-mod_sofia/1.10.0-release~64bit
> Accept: application/sdp
> Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER,
> REFER, NOTIFY, PUBLISH, SUBSCRIBE
> Supported: path, replaces
> Allow-Events: talk, hold, conference, presence, as-feature-event, dialog,
> line-seize, call-info, sla, include-session-description, presence.winfo,
> message-summary, refer
> Content-Length: 0
>
> As you can see, Contact incorrectly states port and transport.
>
> ><>
> nathan stratton
> _________________________________________________________________________
>
> The FreeSWITCH project is sponsored by SignalWire https://signalwire.com
> Enhance your FreeSWITCH install with disruptive priced SMS and PSTN
> services.
> Build your next product on our scalable cloud platform.
>
> Join our online community to chat in real time
> https://signalwire.community
>
> Professional FreeSWITCH Services
> sales at freeswitch.com
> https://freeswitch.com
>
> Official FreeSWITCH Sites
> https://freeswitch.com/oss
> https://freeswitch.org/confluence
> https://cluecon.com
>
> FreeSWITCH-users mailing list
> FreeSWITCH-users at lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
> https://freeswitch.com



-- 
Best Regards,
Ciprian Dosoftei

The information transmitted is intended only for the addressee and may
contain privileged and/or confidential material. If you are not the
intended recipient, kindly contact the sender and delete the message.

Any disclosure, distribution or copying of this message is strictly
prohibited without the expressed permission of the sender.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20190930/b0ae5dc3/attachment.html>