Inbound SIP not working

[CraigDavies]

Dear techs,
A client of mine has a Mitel 3300 MXe-III (software 10.2.1.13) where inbound calls appear to have recently stopped working over SIP.
When an inbound call is placed an engaged tone is presented to the caller. This client recently moved away from the Mitel requiring a registration username/password in favour of authentication by IP to use the SIP.
Our client tells me that their line provider has checked their firewall rules and believe they are correct. I agree that they are correct as we can see during a packet capture that the Mitel controller is responding with "503 Service Unavailable"

Any assistance or input on this would be greatly appreciated.

Regards,
Craig Davies

 

[james1982]

how many digits are you absorbing? common programming error can be that this is left blank, when you need a entry - if needs be 0

 

[CraigDavies]

James,
This has been checked already and fairly confident that this is correct. the provider is presenting 11 digits, the controller absorbs 5 and then presents 6.

 

[EddieV3]

Can you run a CCS trace, simulate an incoming call, and post the results here?

Same again via WireShirk too.

Thanks.

 

[LoopyLou]

What changes were made in the Mitel when you changed the method of registration?

I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.

 

[CraigDavies]

Thanks for the responses guys, I ran a CCS trace whilst all our phones were quiet. whilst trying to place the call from my mobile no logs were written which suggests to me this is the line providers firewall rules?

In terms of what was changed when they moved to IP authentication, the authentication options in the "SIP peer profiles" form was changed to "No Authentication" as the providers firewall rules are configured to automatically allow traffic from our IP.

 

[LoopyLou]

This is simplistic but since you made one minor change on the Mitel I would think the trouble is not there but as you suggest in the providers firewall.

I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.

 

[CraigDavies]

Guys,
I'm having abit of a "tail between legs" moment here. it's fixed....
The SIP peer profile form wasn't pointing to correct trunk attribute (was set to analogue)

Thanks for the input on this one, really appreciate it.

Craig

 

[LoopyLou]

You bastard

I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.

 

[CraigDavies]

Thankyou LoopLou ;-)
On the bright side, this change was made by their inhouse tech's so something I previosuly configured that was working I wouldn't have suspected of been the problem..... Until I went back to basics when all else failed!

We live and learn!

Craig

 

[kwbMitel]

If you can't learn form your mistakes, learn from mine moment

**********************************************
What's most important is that you realise ... There is no spoon.