MiCollab with MBG - unable to make outbound SIP calls

[ralph]

I've been fighting a SIP issue for the last two days. 
 - New install. 
 - MiCollab with MBG. 
 - Server Gateway mode.
 - Inbound calls work fine
 - Using FQDN rather than IP

I've pulled several Wireshark sniffs.  I don't see where any call attempt has even tried to make it to the carrier.  But I'm seeing ICMP redirects that Mitel suggest is coming from the network.   The problem is, I don't see anything at all ever try to reach the carrier when I call.  Nothing.  So I'm having a hard time in understanding why I'd be seeing ICMP redirects.
I can ping the FQDN with no issues.   There's no firewall between us.  All inbound works fine.

Has anyone seen this before?

~Ralph

[dilkie]

have you tried using an ip instead? is msl resolving to a funky/split dns or is it configured to use it's own, internet, resolver?

when an INVITE comes from the icp, what does the tug logs show? it should be finding a trunk and forwarding it.

[ralph]

I've used the internal DNS server, and two different external DNS servers.
I've also tried just using the IP address. 

I'll check the Tug logs and report back.

Thanks.
Ralph

[ralph]

I just made my first successful outbound call on the SIP trunks.
The problem is, though, I bypassed the MBG proxy to do it.
I just used the MiCollab server as a router.

There's something about the MBG that's causing the call to fail.

For some reason the call won't set up when using the proxy.

[ralph]

After pulling my hair out for two days I discovered that I fat fingered the port settings in the 3300 SIP proxy config.
I put 5050 rather than 5060.

I must have looked at that dozens of times.  Even Mitel tech support didn't see it.
It was only after I configured the system to bypass the proxy that I finally found the problem.

It's always that simple things that mess you up.

Thanks
Ralph

[dilkie]

haha... we've all done that!