Dave Horton

I believe the problem is that the drachtio server does not currently select the interface based on the destination ip..it selects only based on protocol. This is something I have...

Could you please build the `interface-selection-improvements` branch, and then retry your tests? If you can provide the drachtio server log file with loglevel 'debug' once you have tested that would...

Note that the latest changes on the above-mentioned branch (interface-selection-improvements) include changes to the underlying sofia sip library so after pulling the latest make sure to do ``` git submodule...

could you try with the latest on this branch when you have a chance? Do make sure to update and rebuild dependencies as before

hmm, actually hold off a bit. I am still runnning some tests..

OK if you can try your tests with the tip of this branch I would appreciate it

The main issue here has been that you are sending to a DNS name, and DNS resolution has been occurring _after_ the selection of the IP/interface to use. In the...

The failure case seems to be because the INVITE request is too large to be sent over udp: ``` 2020-09-29 18:17:25.246605 nta.c:8686 outgoing_print_tport_error() nta: INVITE (26146130): Message too long (90)...

Is it possible you could recreate this failure with sofia log level turned up to 9? In this case (failure response) the sofia sip stack generates the ACK itself and...

Sorry, been off on some other projects myself. I should be able to re-engage on it this week.