Session Manger - SIP / 2.0 404 Not Found

[padeiro]

I'm having a call failure (SIP error message: "SIP / 2.0 404 Not Found (can not determine routing domain, check SM ports)"). By SM trace the message is sent from the SM100 for the Session Manager. The Session Manager does not send the call to the CM.

Scenario:
Main site:
1 CUCM - Cisco Unified Communications Manager
1 SM - Session Manager;
1 System Manager;
1 AACM - Avaya Aura Communication Manager
Secondary Site
1 CUCM - Cisco Unified Communications Manager
1 SM - Session Manager;
1 AACM - Avaya Aura Communication Manager

Failure:
CUCM Call (main) to the SM (secondary) presents the error

Note: Links CUCM (main) to the SM (main) the call is completed successfully.
NOTE: Main site and secondary different address

We have already entered the 5060 ports (TCP and UDP) and trust in the System Manger. Also enter the CUCM entities (main) and trust to the SM (secondary). Imagine to be some configuration "reliability" / trust in the System Manger, but still do not know what exactly.

Is anyone aware to Session Manger and System Manager configuration that can give a help in this case?

 

[ZeroZeroOne]

Assuming the SIP Entities and Links are built and are up, how are you routing?
Do you use different domains for CUCM and ACM?
Do you use Dialing Rules or Regular Expressions?
Do you have any Adaptation on the CUCM?
Are the Routing Policies in place?

Under Session Manager / System Tools / Call Routing Test you can see how ASM checks the Rules and Regular Expressions to find the correct Route.

Maybe answering those questions will help you find the solution.

 

[kyle555]

On the SIP entity for your SM you can define a default domain for different ports - like 5060 being yourcompany.com.

That might be enough to get SM to process invites from cisco of 1234@your.sm.IP

Otherwise, DNS SRV records might be how you need to set the sip trunk on CUCM to destination IP of "yoursipdomain.com" and CUCM will DNS lookup that, then send 1234@yoursipdomain.com and address that to the SM100 IP

 

[padeiro]

thank you guys. I solved the problem by releasing the UDP port 5060, within the SIP entity.