MBG DMZ Profile and Twilio no Go

[way2fast59]

Running into an odd situation.

Outside calls have dead air and never complete.

We have a setup where the client cannot configure their MBG in Server-Gateway mode due to security reason and politics. The only way around this is using the DMZ profile, but we cannot establish any outbound calls to Twilio. MiVB and MBG are configured per the Twilio CoE document, and the SIP trunk shows a green check mark for the status. 

MiVB, MBG and the phones are all on the same network.

Pcaps (on the MBG) show the call setup communications between MiVB and MBG, but we never see the MBG reaching out to Twilio. FW rules are an any-any for the NAT. Tried flipping to 'custom profile' and using the inside ip address for the set-side with the same results.

Thoughts?

[billbry66]

try putting the TW public ip on the set side in custom mode

[way2fast59]

So a bit of an update.

Moved to custom, private ip on the ICP side, public ip on the Set side.  Still same problem.  Reviewed the Twilio integration Mitel Doc and started changing settings one by one. Discovered that Twilio does not require "SIP Registrar FQDN or IP Address" in the config.  Removed this and now some progress.  The far end is ringing (my cell phone), but when I pick up the call on my cell, it continues to ring on the 6930 phone. Appears the "Hey, the far end picked up" message is not getting back to the MBG and/or MiVB.

Fun times.

[way2fast59]

We have calls working somewhat now. Pcaps are showing the inbound RTP to the MBG and then over to the phone. However, pcaps from the phone show that it is not placing outbound audio packets to the MBG. Hmmmm