BCM to CS1000: peer networking H.323 trunk 1

[noseygomu]

wonder if anyone can point me to right direction on how to H.323-trunk between BCM to CS1000 (also served as NRS/gatekeeper).
so far, i can't see any RAS registrationRequest coming from BCM.
i thought i had everything configured correctly.
there's license for 2 VOIP gateway port(s) in the BCM.
TIA.

 

[biv343]

Under IP Trunks, H.323 trunks, make sure you are set to gatekeeper resolved. Enter the IP of the signalling server. For the H.323 alias, enter NAME:aliasid (where alias ID is the name you have given the endpoint in NRS).

Don't forget the NAME: - must be before the alias ID, and must be in capitals. The alias ID can be whatever you want, but is case sensitive.

After that, its regular line pools/destination codes/routing on the BCM end.

Also make sure you are entering the signalling server IP as the gatekeeper address, not the node address. If you enter the incorrect address you'll see failed registration attempts being logged on the NRS.

 

[noseygomu]

thanks biv343, i got everything configured correctly just like what you explained; except one thing: ENABLE the feature (DUHHH!!!).
so, moving on, i managed to get both BCM & CS1K registered, but there are 2 prominent situation that leads me to believe there's some parts in CS1K not configured quite properly:

1. calls made to CS1K XXXX from BCM client will trigger H323-RAS admissionReq, admissionConfirm between BCM - Gatekeeper; but then CS1K sends CS:ReleaseComplete (reason: gatewayResources)

2. calls made to BCM YYYY from CS1k client will trigger Q.931 signalling initiation from CS1K (??? why???).
i couldn't find a way to disable ISDN signalling in callServer's virtual trunk/route (H323 trunk).

looking at point #1. above, imho, that's an expected behavior, right?
as for #2., what mistakes did i do in configuring the trunking/signalling part?

the plan is to enable peer networking using CDP without any digit manipulation to start with.
any helps would be appreciated.