Dave Horton

I haven't tested on docker, but on a native server running drachtio server and freeswitch (configured to work with drachtio server), this app answers the call and plays your file...

that is actually the correct behavior, as far as the incoming leg (aka A leg). If you had used `srf.createB2BUA` you should have also seen a CANCEL generated on the...

On a cancel you should be falling through to ``` .catch((err: any) => { console.log(`Error connecting call: ${err.message}`); }); ``` can you show the full drachtio log, including the initial...

OK I think this is a bug in drachtio-server, where it fails to forward the CANCEL onwards over the existing websocket connection to the B party. If I create branch...

actually, could you actually show me a pastebin of a call that successfully connects? I would like to compare that with the earlier pastebin showing the CANCEL failure. That will...

If you are using wss or tcp as a protocol on the B leg, then I imagine it is related. I will try to have a patch for you to...

I've attempted a fix on branch `issue-84` of drachtio-server. I'd be interested to see a pastebin of a retest with that build

any chance you can validate that fix today?

I'm unable to recreate this issue, however your call flow has one interesting difference: after sending the INVITE to the B party and before receiving a 100 Trying, you send...

I reviewed that pastebin again. There is another difference. On the INVITE you send to the B party, the sip uri has two transport params: ``` INVITE sip:[email protected];transport=ws;transport=udp SIP/2.0 ```...