Twilio->dSIP->PBX Calls Drop due to Contact Header Translation

[Johnny Robbins]

I'm running into an issue where for inbound, my calls successfully pass from Twilio to dSIPRouter then to my PBX and I'm able to answer the call with my softphone connected to the PBX. However the calls drop on the receiving end (softphone) consistently after 25 seconds of solid 2-way audio. The caller side (cellphone) doesn't hang up.

Consistently on my tests, at about the 4 second mark, the PBX sends a new Invite message, which dSIPRouter then tries to send to Twilio 10 times without  a response before sending a 408 Request Timeout message back to the PBX at about 25 seconds.

I've opened a ticket with Twilio and they've stated my issue of calls dropping is a result of the PBX's re-invite using Twilio's external IP address instead of the internal address (which is weird to me, but the internal IP address is what Twilio is expecting). 
I suspect this results from dSIProuter translating the Contact header in the invite from Twilio's internal IP address to it's external IP address when forwarding the invite to the PBX. As a result, the PBX's re-invite RURI uses the external IP address for Twilio instead of the internal.
Has anyone run into issues with this, or have suggestions on how to prevent the IP address from being translated in dSIPRouer? (edited) 

[Mack Hendricks]

Hey Johnny,

We have a new feature coming called SBC Translation, which will handle this.  A quick fix is to turn off RE-INVITE's on the PBX if possible.

--
You received this message because you are subscribed to the Google Groups "dSIPRouter" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dSIPRouter+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/dSIPRouter/456560c6-d9d3-458e-afce-7666f176acecn%40googlegroups.com.