SIP trunks on 3300 MX

[navigatorsaregay]

All,

Installed 10 x liscenses on 3300 MX today for 10 Sips to Gamma Telco. As Gamma are a supported provider, Mitel released a doc in the knowledge base in 2008 ish running through step by step guide to progrsmming the trunks.

This has always worked for me before.

Programmed trunks and tried to dial out - got access denied.
After removing ALL class of restriction from system i soon reslised it was nothing to do with th system. SIP state commands see the link is up and i was getting authentication errors in the logs.

Authentication type is IP ADDRESS NOT username and password.

Called Gamma to see if they were getting any auth requests from us. They sent me a wireshark trace showing the reason for the failure.

The packet header shows the publicly routable IP address of the customers router. However, when you actually open the packet and look at the invite for authentification part it shows as being from 172.16.240.2 which is the internal LAN IP address of the 3300. Gamma say this is the reason for the authentication fail. It needs ALL ip addresses in the packets to be the publicly routable address.

Im now stuck in the middle of a cat fight between Mitel and the customer IT guys. I know the Mitel cannot forge an IP address to send out. But i am still very inexperienced when it comes to SIP and was wondering if any of you had come accross anything like this before

3300 is on Version 8.

 

[LoopyLou]

Not a SIP expert either but sounds like a SIP proxy would solve the issue. Don't have a MBG do you?

Maybe someone else has advice on your NAT problem.

 

[Mitel100]

NAT is the bane of all SIP implementations because the SIP
protocol includes network addresses in its payload. These addresses define the end?points for the media
stream, the voice conversation or video session.

Standard NAT changes the network addresses used to send
and receive SIP requests but does not change the contents of those requests. These means that when a SIP
request passes through a NAT gateway the media end?points are incorrect.

Solutions:

SIP aware routers / firewalls


__________________________

There is no 'I' in 'Team'
__________________________

 

[bobcheese]

As it happens navigatorsaregay, I have been dealing with Gamma with the same sort of problem myself this week. We have a SIP circuit that suddenley started having issues with calls (after previously working for a number of months if not longer). The response I got from Gamma was that the VIA header contained the internal address of the 3300 and not the public address. After much consultation with Gamma and SIP traces being captured I got the response from them that an upgrade on the 3300 to R9 or higher would fix the issue. Don't ask me how they know this info but thats what they said. Job is scheduled so we will wait and see. They guy did tell me that they upgraded the SW on their Border Controllers recentley maybe this has something to do with it.

 

[navigatorsaregay]

Bob!

I too am on Version 8!


Keep me updated...

 

[LoopyLou]

Gee they upgraded the Border gateways and a problem occurred hmmm.

 

[bobcheese]

Yeah I know. I think his actual response was something like....'Its abit of a grey area as too who's fault this is but I have been informed that if you upgrade the Mitel to R9 or above everything should be ok'

 

[jon83]

Hi I had a similar problem last week with Gamma with phones unable to transfer calls or hold and upgraded from 8 to 9 ur3 and problem fixed ! I was given advice from Gamma to upgrade.