David

How do you register the BCM50 with the Sig Server? We are actually programming an SRG50 but it is really just a scaled down BCM 50. We are trying to get the IP trunks to register with the siganling server but it keeps saying "attempting to discover the Gatekeeper at 123.45.678.9".

Cavscout

If it actually says:

"attempting to discover the Gatekeeper at 123.45.678.9" it sounds like your SRG is not configured to point to the SS or GW.

PBXtech.info

 

David

We have been able to finally get the SRG50 to register with the Signaling Server but after about a minute the SRG50 becomes de-registered from the Signaling Server.
It goes back to "attempting to discover gatekeeper at. " So we still can't register really.

Also we are trying to configure the SRG50 to perform external paging through Active physical port 62.
Active physical port 62 is assigned to line pool B.
Line pool B is set up with an access code of 0080, so that if you dial that access code you should get routed out of Active physical port 62 the only port in that group. But It doesn't seem to work just yet.

Cavscout

Regarding your end point de-registering from the GK.

On the CLI of the GK you should get some messages when the endpoint (SRG50 in your case) de-registers.

I suspect that will be something like:
raAdd (RAS IN TX): Array full
raAdd (RAS OUT TX): Array full (402 elements)

In addition you should have some log entries like:
LOG0003 NPM: npmGKRegister: GateKeeper <IP ADDRESS> registration stack transaction failed
LOG0003 NPM: npmGKDisengage: Unable to start a RAS transaction

If you get error messages like this then the fix is a patch or two. MPLR19521 may applicable to your system. Since you stated that the SRG would register, but then deregister I think it is likely that your configuration is correct, or at least mostly correct.

Good Luck

peter-mey

In the NRS endpoint srg50 you have to check the box network connection server.

:devil:

David

Well you know we never could get these guys to stay registered and with no solid fix so we decided to send them all back to Verizon. I wish they had worked out but, we just don't know nor can Nortel point us to anyone who has them up and working with a Signaling Server. I do appreciate your input and replies to this subject though. We know a lot more about SRG-50 s now at least. Hopefully in the future we will return to them once they are more established in the Telecom community.

PBXtech.info