CM to Session Manager - 404 Not found (No route available)

[underwoj]

I am having an issue with some phones that can not use a SIP tie trunk between 2 CM's we have. They are setup with the same COR...using same Route Pattern...going out same SIP tie trunk. Yet - I am receiving a 404 Not found (No route available) on some of my stations. Why are some being blocked and some being passed? I have attached a screen shot of a successful and non-successful trace. Trace on the left you will see the call being blocked...on the right - the SIP/tie trunk allows the call to proceed to the other CM (getting the 180 ringing response).

Please help.

thanks
Robert

 

[jtc22]

The obvious difference is the number you are calling. The dialed number in the left may not be in the SM dial patterns or the originating CM is not allowed to make that call.

 

[dialtonebone]

You should check with the far end since they sent you the message. If it's an SBC or SM, then do a trace from there.

 

[kyle555]

depending how busy your SM is, you can trace with call processing enabled.

Either way, you need a match in SMs dial plan. So, a dial pattern, for a SIP domain (or, ALL domains), for a location, or ALL locations. It sounds like something's missing. Like the dial pattern matches, but from originating location CM1 and not CM2.

SM looks at the oldest VIA header in the invite to get the source IP - whether it's a H323 phone or whatever and assesses location based on that. It's likely that this could associate to a location it knows about.