Dave Horton

I have plenty of projects where I've used rtpengine but no git showing exactly what I outline above

The problem is you moved rtpengine to listen for traffic on port 2223 instead of its default port 22222: ``` listen-ng = 127.0.0.1:2223 ``` You then configured your node.js application...

rtpengine is saying it ran out of ports, which is strange since it is configured to have a range of 10,000 ports. Look in /var/log/syslog for more logging from rtpengine...

turn drachtio server log level to debug, run the node.js app with DEBUG=drachtio:* and re-do your test. Seems like some bit of configuration between the app and the server is...

Your problem is with your rtpengine config. Specifically this ``` interface = 34.200.127.219 ``` I can see from the drachtio logs that that address is not a local address on...

you should get a network trace and study it to see if you are receiving RTP on the B leg

thanks will look into it. Also feel free to join our slack at https://joinslack.jambonz.org and post questions in the drachtio-community channel

There are rules for what a P-Asserted-Identity header must look like....specifically, it must be a sip uri

https://tools.ietf.org/html/rfc3325#section-9.1

drachtio does not have any logic to handle unsolicited Route headers on a new INVITE, which it seems your scenario is dependent on. (not related to this, the drachtio server...