flexisip-developers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Flexisip with Websockify and SIP.js


From: Nik Pakar
Subject: Re: Flexisip with Websockify and SIP.js
Date: Wed, 22 Apr 2020 09:01:43 +0530

first 2 messages are inbound and only the last one is outbound. Might have to inspect tcp headers as well and also the state of the websocket. If u can provide the websocify config i can give it a quick try and see what it is. But really dont hv time to research on websockify.


On Tue, Apr 21, 2020 at 11:19 PM AJ Mork <address@hidden> wrote:
Yes, websockify facilitates bi-directional communication. 

Initial Invite
INVITE sip:address@hidden;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 2neshedg0pjf.invalid;branch=z9hG4bK9595928
To: <sip:address@hidden>
From: <sip:address@hidden>;tag=luo8ahg6hu
CSeq: 1 INVITE
Call-ID: hqhlk9cv5b1i0dp3smas
Max-Forwards: 70
Contact: <sip:82409ako@2neshedg0pjf.invalid;transport=ws;ob>
Allow: ACK,CANCEL,INVITE,MESSAGE,BYE,OPTIONS,INFO,NOTIFY,REFER
Supported: outbound
User-Agent: foy
Content-Type: application/sdp
Content-Length: 6346

received after picking up the call, then every second or so after (truncated)
SIP/2.0 200 OK
Via: SIP/2.0/TCP 2neshedg0pjf.invalid;branch=z9hG4bK9595928;received=127.0.0.1;rport=51076
Record-Route: <sip:foy.techgeekery.net:5060;transport=tcp;lr>
From: <sip:address@hidden>;tag=luo8ahg6hu
To: <sip:address@hidden>;tag=5ti2omnkjl
Call-ID: hqhlk9cv5b1i0dp3smas
CSeq: 1 INVITE
Contact: <sip:g5ghg1fh@127.0.0.1:51074;transport=tcp;verified>
User-Agent: foy
Allow: ACK, BYE, CANCEL, INFO, INVITE, MESSAGE, NOTIFY, OPTIONS, PRACK, REFER, REGISTER, SUBSCRIBE
Supported: outbound
Content-Type: application/sdp
Content-Length: 5407

ACK response that never makes it
ACK sip:g5ghg1fh@mtb2u65gmdml.invalid;transport=tcp SIP/2.0
Route: <sip:foy.techgeekery.net:5060;transport=tcp;lr>
Via: SIP/2.0/TCP 2neshedg0pjf.invalid;branch=z9hG4bK9008834
To: <sip:address@hidden>;tag=5ti2omnkjl
From: <sip:address@hidden>;tag=luo8ahg6hu
CSeq: 1 ACK
Call-ID: hqhlk9cv5b1i0dp3smas
Max-Forwards: 70
Supported: outbound
User-Agent: foy
Content-Length: 0 

On Tue, Apr 21, 2020 at 1:36 PM Nik Pakar <address@hidden> wrote:
It should listen back from flexisip as well. Not just one way packet forward.

On Tue, 21 Apr 2020 at 10:55 pm, AJ Mork <address@hidden> wrote:
Yeah, the more I dig into this more I am realizing that. just frustrating that at a base level it seems to work, just the ACK message is getting lost.

As far as the websockify config, there really isn't much of one, just telling it the port to listen on and where to send it, in this case 8080 and 127.0.0.1:5060.

On Tue, Apr 21, 2020 at 1:14 PM Nik Pakar <address@hidden> wrote:
It's very unlikely a transport layer proxy will work for this.

Can u share your websockify code/config

On Mon, 20 Apr 2020 at 7:01 pm, AJ Mork <address@hidden> wrote:
I have websockify listening on 8080 and feeding to the normal SIP port - 5060

On Mon, Apr 20, 2020 at 4:52 AM Nik Pakar <address@hidden> wrote:
How did you implement the sip interworking to flexisip from websockify ?

On Mon, Apr 20, 2020 at 2:15 AM AJ Mork <address@hidden> wrote:
Greetings and salutations,

Please forgive my ignorance but I'm running into an issue with ACK messages after an INVITE.

I am developing a web/mobile friendly one-click support app, hence the need to proxy from Websockets to TCP sockets, everything works fine when using a TCP based app to call, but when using Websockify the call connects and audio/video is good but the connection drops after a few seconds. Upon further investigation, the ACK messages are not making it through. Has anyone had any luck with this or insight?

Thank you in advance.

--
AJ Mork
Developer
Tech Geekery, inc.
Monday thru Friday, 9am to 5pm


--
AJ Mork
Developer
Tech Geekery, inc.
Monday thru Friday, 9am to 5pm


--
AJ Mork
Developer
Tech Geekery, inc.
Monday thru Friday, 9am to 5pm


--
AJ Mork
Developer
Tech Geekery, inc.
Monday thru Friday, 9am to 5pm

reply via email to

[Prev in Thread] Current Thread [Next in Thread]