Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

MBG 7.1 in Gateway Mode - SIP Trunking issues HELP!

Status
Not open for further replies.

Cardine

Technical User
Jul 3, 2006
97
CA
Ok, i see alot of MBG forums but i think my config is a little different with have an MBG in Gateway mode, with a dedicated external IP address we can make incoming calls no problem work perfectly, but when we try and make an outgoing call we get "INVALID" on the 3300. - we've triple check the ARS programming and it's fine.

Now when we run a wireshark we don't see any SIP/UDP information on the external side of the MBG when making an outgoing call - strange!, on incoming calls we see all of the proper SIP messages and as mentioned before it works great, but on the internal side of the MBG we see the MXe and MBG talking using there internal addresses when we attempt an outgoing call. - the ITSP has also confirmed that the MBG doesn't seem to be talking to them during an outgoing attempt.


Has anyone set up an MBG in Gateway mode?

I'm really stuck here.

thanks in advance

Cardine
 
Is the 3300 using the MBG as its sip proxy?

Have you defined the MBG as a sip proxy in the network element assignment?

Have you taken traces on the MBG itself?
 
Hi Cardine,

I was wondering how you got around this?

Thanks
 
EddieV3, basically after sending some traces to Mitel they came back saying that they were expecting to see the proxy.xxxx.com address in the response but they were getting the xxxxx.com instead, when we tried putting the proxy.xxxxxx.com address into the MBG it still didn't work but Mitel said is was the providers problem now as the MBG likes what it is seeing....after calling the provider they said we can't use the proxy.xxxxx.com that we should be using the xxxxx.com..

Basically to solve the problem we manipulated the DNS to have both FQDN's point to the same address and it works perfectly.

I tried another sip provider and couldn't get it working at all.

Basically MBG SIP TRUNK PROXY is really hit or miss, most of the docs online show SIP using NAT through a firewall which is fine and work greats, but my opinion is that Mitel needs to make the MBG more viable as a SIP Trunk proxy, that being said MBG 7.1 has some great tools for troubleshooting including being able to run a wireshark capture right from the GUI and DNS tests....

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top