Gatekeeper Controlled Trunk RRQ Rejected

Unanswered Question
Apr 3rd, 2009

Hi,

I am assisiting a Customer in trying to resolve a registration issue with a Gatekeeper Controlled Trunk in CCM.

The gatekeeper (non-cisco) has provided a trace and shows the registration is failing due to an "Invalid Alias". The alias / h323-ID shown in the trace is actually different from that configured in the Trunk "Device Name" configuration field in CCM as detailed below:

Configured Device Name (and therefore h323-ID) - CCM1_1

h323-ID in Gatekeeper trace - ipcc_1

Can anyone think what may be causing this within CCM Administration. I have checked all the obvious settings / parameters and nothing seems to be wrong.

Best wishes,

Matt

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Anonymous (not verified) Thu, 04/09/2009 - 10:04

When the H.323 gateway registers with a gatekeeper, sometimes an alias list is provided to the gatekeeper in the registration request (RRQ) message from gateway. Currently, this configuration is supported on Integrated Operating System (IOS) gateways when Foreign Exchange Station (FXS) ports are involved. If a request rejected (RRJ) message is received by gateway with reject reason of "invalidAlias", this is symptomatic of an alias list being provided to the gatekeeper but the gatekeeper not configured to be responsible for the prefix associated with each of the aliases.

So add a zone prefix entry to GK that would cause a match on the alias numbers that are trying to be registered.

Actions

This Discussion