ASM Call Routing Problem: 404 Not Found

[t2true]

We have two sites: each has a System Manager (SM) and Session Manager (ASM). But, each uses one Communication Manager (CM) located at one of the sites. (The other site houses the ESS CM.)

We are implementing a fax server at each site. Each one connects to the ASM at its site. Calls coming from the fax server route through ASM and go to CM over a SIP trunk.

Site A’s fax server works fine; calls route correctly. Site B’s fax server fails every time.

Both ASMs are configured exactly the same save the name and IP addresses of the SIP entity (fax server). (I have gone over it three time and had someone else review it twice. There are no differences.)

The error I get on the site B’s traceSM is “404 Not Found (cannot determine routing domain, check SM ports).”
Here is the trace:

FastFax Roc

​

SM100

|--INVITE--> | | | (1) T:9143991167 F:9143899400 U:9143991167
|<--Trying-- | | | (1) 100 Trying
|<--Not Fou- | | | (1) 404 Not Found (cannot determine routing domain, check SM ports)
|----ACK---> | | | (1) sip:9143991167@161.111.40.113

The domain is set in Routing>Domains and the port is set in Routing>Entity Links

I cannot figure out why one site works and the other does not when everything is configured the same.

Any help would be greatly appreciated.


Thanks

 

[kyle555]

Well, SM wants to look at a number of things to decide how to route a call.

Location - your SIP entity to your fax server is in a location. Your destination, or routing policy is determined by dialed number for a domain, and originating location.

So, pretend I have 2 tenants on my core, each with a location in 2 states, for a total of 4 sites:
Widget NY
Gadget NY
Widget CA
Gadget CA

And we also have the widget.com domain and the gadget.com domain. And each location has an Audiocodes MP112 because I want to route the analog calls out the appropriate gateway to get to the local police

I'd have dial pattern 911 for the widget.com domain
and if originating location is "CA" send to "CA Widget gateway"
and if originating location is "NY" send to "NY Widget gateway"

I'd also have dial pattern 911 for the gadget.com domain
and if originating location is "CA" send to "CA gadget gateway"
and if originating location is "NY" send to "NY gadget gateway"

Somewhere along the line, you missed something.
Also, SM loves domains and hates IPs. If your fax server only sends invites to 123@192.168.1.1 and not @yourdomain, you'd need an adaptation on that SIP entity where SM can translate all incoming IPs to a domain, and all outgoing domains to an IP to play nice with your box.

 

[t2true]

I am using the same domain and location for each site. The fax server is set up with the same domain. And, the routing policy and dial patterns are configured the same.
In comparing the good trace with the bad, the good call passes through the SM100 and reaches CM. The bad call never makes it to CM.

I understand what you are saying, Kyle, about sending invites to an IP instead of the domain name. However, as I see it, the call should go to the domain name instead. I do not know why it is being sent to the IP address as shown in the trace.

 

[kyle555]

If your SM isn't too busy, enable call processing traces. You'll see the thinking that SM goes through and see what's up. Is the leading 9 maybe a problem?

 

[redphone]

This may help:

thread690-1723414

 

[t2true]

@redphone...I have checked and re-checked all settings identified in the post you mentioned. My signaling group is correct; the SM domain is defined; the SIP entity and entity links are configured correctly.

Both ASMs are configured identically.