Dave Horton

OK, but having transport=udp is wrong since this is going to go out wss. Why do you have that there? Or are you not putting it there (from your app)?...

I've only looked at it no. 3 since the others are irrelevant (transport=udp is not appropriate) As far as test no. 3 you are still including a transport=ws header. ```...

I'm talking about your node.js app, not your client app. Please run the node.js app with DEBUG=drachtio:* and provide that output

Its interesting, because this seems like it is coming from your app: ``` drachtio:srf createB2BUA: creating UAC, opts: {"headers":{"X-ch-crid":"54","X-ch-calleepid":"98","X-ch-calleremail":"[email protected]"},"passFailure":false,"uri":"sip:[email protected];transport=ws","method":"INVITE","responseHeaders":{},"callingNumber":"lenny","calledNumber":"chromebook ``` i.e., the uri you are providing is `sip:[email protected];transport=ws`. Can you...

What I am saying is that I would like to see your server code. Also, please do update to latest drachtio-srf and retest

Can you log endpoint_aor? ``` endpoint_aor = user[deviceId]; const uri = `${endpoint_aor}`; ``` I think that will have the transport=ws in it. Could you try stripping that out (the transport...

Yes, this is how it currently works. If you destroy the Endpoint (as you do in the 'destroy' handler for the sip dialog) then any operations are terminated by freeswitch...

ok. I'm still going to look into properly resolving/rejecting those promises. let's leave this issue open until I do so.

It sounds like either the 'offer' message is not making it to rtpengine, or the response from rtpengine is not making it back. Can you check the rtpengine logs first,...

which docker image are you using? I think you need to expose the rtp ports as well. Try this and let me know if this resolves the error you are...