Anybody done XO eSIP trunks?
They are delivering use their trunks in kind of an odd way (to me at least), they won't use our MBG but instead delivered a Cisco 1941 router and with a LAN interface on the voice VLAN subnet, and said it needs to be the gateway to signal to their SIP server, which is XXX.XXX.XXX.30 with a caveat that says (Note: Customer should open the NBS Block XXX.XXX.XXX.16/28. Doing so will account for the RTP IPs), and they will signal to the vMCD's private LAN IP.
So I need to set this up, is it common to build the router as an Outbound Proxy (like an MBG) in network elements and set it up pretty much the same as a SIP carrier through that proxy, or do I need to go into MSL and build a route that says for XXX.XXX.XXX.16/28 use the gateway of the LAN IP address of the Cisco router?
All the documentation on XO and Mitel's website (
https://www.xo.com/sites/default/files/inline-files/10-4940-00105_3-XOCommunications_MiVB5.pdf) seems to dictate a MBG is used and it's signalling to a public IP in the cloud, but we had no way to implement that as this installation is in a data center and completely virtual, even the WAN of the MBG, but the carrier delivered us a router (and our MBG signals to several other SIP carriers in the cloud).
I can't test it with the carrier until next Monday, but our implementation window is small, I would like to have these working as quickly after initial testing.