CallManager using GateKeeper without default-technology command

[calmichael]

Cisco documention alludes to the idea that one can

setup a CallManager Trunk to a IOS Based GateKeeper

that does not need to use the default-technology

command "gw-type-prefix 1#* default-technology".

My attempts at getting this to work result in calls

not getting routed in either direction, though a

"show gatekeeper endpoints" shows that CallManager

did register to the GateKeeper.

Adding the "gw-type-prefix 1#* default-technology"

and the "1#" under the CCM Trunk allows this to work,

but we would like to see a configuration that does

not rely on default-technology work successfully.

Can someone who has done this successfully post a

config snippet from the GateKeeper config and from

the CallManager Trunk (GK related) settings?

Thanks

[anup.anand]

From the Gatekeepers perspective, an incoming call will be routed only if it matches either one of the three conditions

1. A configured tech prefix is matched

2. There is a default tech prefix configured

3. The target address is registered as a E.164 address.

Callmanager registers with the gatekeeper using the H323-ID and not the E.164-ID.

Hence I think, you would either have to use a default tech prefix on the gatekeeper or have the Callmanager use a tech prefix to register with the gatekeeper.