Help! SRG sets will not register in Normal Mode 1

[Jephph]

I've spent WAY too much time on this issue, but I can't get my SRG's 1140e sets to work in normal mode -- they only come up in local mode. The SRG is 3.0 and the CS1000 is 6.0, and they're connected via working SIP trunks -- the 1140e sets (in local mode) can dial the SIP trunk access code and get over to the other side just fine. The 1140e sets also work perfectly when registering directly to the CS1000 (via port 4100, versus 7300) to their MOTN.
When I browse the SRG's alarm log, it states that the SRG can't located the MO's TPS. Clearly the Main Office's TPS is working, or the 1140e sets wouldn't work when directly registering to the CS1000.
There are no port blockages or firewall issues in play.
Any ideas out there?

 

[teekow]

SRG units utilize the NCS functionality of NRS at the main office. That should be a checkbox on the CS1K endpoint. I assume you have entered the MOTN and BUID in the SRG within element manager? The NCS address is a field within the SRG next to the gatekeeper address fields. You must use the NRS address and not the node address in this field. The fact that those fields are together leads me to believe that NCS is related to the gatekeeper so you may need to enable the gatekeeper on the NRS sig server even though you are not using H323 trunks. Last thing is that the BUID used for the phones has to be entered as routing entries in NRS pointed to the CS1K (not the SRG).

hope this helps
Rob

 

[Jephph]

Teekow -- thanks for the reply. The MOTN/BUID has been entered, and the NRS address, NCS checkbox, and NRS routting entries have also been configured. You bring up an interesting point about perhaps having to enable GK functionality, even though it's pure SIP. I may have to give that a try, although it will have to wait until I can reboot the UCM/Sigserv/NRS after the change.

 

[teekow]

I would also change the SRG endpoint to both a static SIP AND dynamic H323 endpoint to confirm that you are seeing the SRG register as an H323 endpoint. Even though you are using SIP trunks, this will at a minimum confirm IP connectivity to the NRS and show that the NRS is "recognizing" the SRG. Unfortunately, the SRGs don't have the capability to register to NRS SIP Redirect Server as a dynamic SIP endpoint so you are stuck with static.
hope this helps
rob

 

[Jephph]

Teekow --
Turned out that I needed to enable the node to use both h.323 and SIP, even though we are only using SIP trunking. Once I did this and synchronized, it worked properly. Thanks for your help.