PBXtech.info - View Single Post - Not able to register BCM 50 with the Sig Server

Cavscout · February 24th, 2006, 01:43 PM

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

February 24th, 2006, 01:43 PM	#4 (permalink)
Cavscout PBXtech GOLD 100+ posts Join Date: Nov 2005 Posts: 132	Re: Not able to register BCM 50 with the Sig Server 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