Need help configuring a new SIP entity in Session Manager "Terminating location is null"

[rejackson]

Hi everyone,

I am configuring a new entity in SM for an ESNA system to test it for replacing our modular messaging. It is not my first new entity but I have not done many. I cannot figure out what is wrong. Below is a call routing test from SM and it shows the components I have set up, dial pattern, routing, entity, entity links. It looks like it is working until the last line. Terminating location is null.

This test does not actually send any data, it just shows the selected path. A wireshark trace shows the SM and ESNA servers are heartbeating on port 5060 and if I make a call to the pilot number the SM does send an invite (so maybe the trace test is bad?), but I get a fast busy. I need to talk to the vendor about their server but I wondered if anyone could explain the results of this trace?

Thanks
REJ

BEGIN EMERGENCY CALL CHECK: Determining if this is a call to an emergency number.
Conference Factory Well-Known URIs: No matches for uri < 100080@ryanco.com >.
Originating Location is null. Using digits < 100080 > and host < ryanco.com > for routing.
NRP Dial Patterns: No matches for digits < 100080 > and domain < ryanco.com >.
NRP Dial Patterns: Found a Dial Pattern match for pattern < 100080 > Min/Max length 6/6 and domain < null >.
NRP Routing Policies: Ranked destination NRP SIP Entities: ESNA.
NRP Routing Policies: Removing disabled routes.
NRP Routing Policies: Ranked destination NRP SIP Entities: ESNA.
NRP Dial Patterns: Chose route matching pattern 100080
END EMERGENCY CALL CHECK: This is not an emergency call.
Adapting and proxying for SIP Entity ESNA.
NRP Entity Links: Found direct link to destination. Link uses TCP to port 5060.
NRP Adaptations: no Outgoing Adaptation administered.
Route < sip:100080@ryanco.com > to SIP Entity ESNA (10.100.0.31). Terminating Location is null.

 

[kyle555]

That's odd. I know every SIP entity needs a location. You can really just add a location, give it a name, and save or be more elaborate with IP address patterns. You assign that to an entity. Its used in dial plan processing and is basically the SM equivalent of CM's network regions and locations where different IP ranges associate to different locations and associate to different routing logic.

Maybe remove/readd it? Maybe there's a little corruption in your SM? Try adding the IP of the Esna at the bottom of the location as a /32 exact match. You shouldn't have to, but it might help.

 

[rejackson]

Thanks kyle. I got past this problem and on to the next one. THis problem was exactly what the message said. There was no Location specified in the SIP entity for the ESNA server. I went back over the Avaya application note for configuration SIP with ESNA and it skips right over that field in the section for configuring the entity.

 

[kyle555]

I didn't think it ever would let you add an entity without a location. Odd.