[cisco-voip] Gatekeeper controlled devices with CCM4.2/IOS GK

Mon Jun 4 16:42:37 EDT 2007

Well, this could be a digit-match issue... but I am guessing at this
point... hell, it could be a CSS issue on the CCM trunk...

So, let's check those... What partition is the number you are trying
to call, what CSS does the trunk have for inbound calls? How many
digits are you receiving on the trunk, is there an explicit match on
CCM as a DN?

Jonathan

On 6/4/07, Dietmar <db7td at gmx.de> wrote:
> Hmm, I think the GK is okay. CCM registers as default zone GW and thus gets
> all the calls. This seems to work. I did traces on both the GK and the CCM,
> and the calls are received at the CCM side. Unfortunately, nothing happens
> there after the setup, and no more debug lines are printed. Finally, the
> endpoint gets a timeout and ends the call. "Warning: H323Stopped - Cisco
> CallManager not ready to handle calls for the indicated H323 device." is a
> nice message, but I really do not know what the problem is.
>
> I have also tried with Netmeeting instead of the Tandberg endpoint. In this
> setup I have the problem, that the GK does not pass the E.164 ID to CCM, so
> CCM rejects the call. It's really crazy.
>
>
> Dietmar
>
>
>
>
> On Monday 04 June 2007 20:28:14 Jonathan Charles wrote:
> > OK, now I get it...
> >
> > Basically the problem is that CCM is not registering its extensions
> > with the GK, which is why calls work one way and not the other...
> >
> > do a show gatekeeper endpoints on the GK and you will see the DNs
> > registered...
> >
> > CCM prob didn't register any... I am not sure off of the top of my
> > head the fix for this... unless you manually create the extension with
> > a zone prefix [name] 33..
> >
> >
> > Jonathan
> >
> > On 6/4/07, Dietmar <db7td at gmx.de> wrote:
> > > Hi Jonathan,
> > >
> > > thanks for your help so far! Well, I am not absolutely sure, but I think
> > > what you're describing is the "usual way" how to do this. A easier way
> > > (from an administrator's point of view) is to have a RASAggregatorTrunk
> > > (endpoint gatekeeper). This is described here:
> > > http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_implementat
> > >ion_design_guide_chapter09186a00806e8c4c.html#wp1065094
> > >
> > > This way, there is no need to create an extra trunk and forward the
> > > extensions manually. Instead, CCM creates the trunk in background and
> > > forwards the DNs automatically to the trunk. Right now, I can call the
> > > video endpoint from any CCM controlled phone (video endpoint is
> > > registered to GK and IP is RAS-resolved by CCM), but calls in the other
> > > direction are not possible.
> > >
> > > "MTP required" setting did not help...unfortunately.
> > >
> > >
> > > Dietmar
> > >
> > > On Monday 04 June 2007 19:23:28 Jonathan Charles wrote:
> > > > OK, I think I know what you are doing wrong...
> > > >
> > > > Sure, you can configure the H.323 client in CCM, but the H.323 client
> > > > must register to a gatekeeper (it will register with its phone
> > > > number), and then you create a route pattern on CCM with the same
> > > > route-pattern and point it at a GK-controlled trunk on CCM which will
> > > > register with the GK...
> > > >
> > > > RAS will take care of everything else.
> > > >
> > > > Check your H.323 thing's documentation on how to configure its
> > > > gatekeeper and point it at the GK... it should register automagically.
> > > >
> > > >
> > > >
> > > > Jonathan
> > > >
> > > > On 6/4/07, db7td at gmx.de <db7td at gmx.de> wrote:
> > > > > No, I have not checked it. There is only a RASAggregatorTrunk that is
> > > > > for gatekeeer controlled H.323 devices as described in the SRND. If I
> > > > > understand correctly, the GK does all the RAS stuff and forwards
> > > > > every call request to the CCM. This way, you can add any H323 client
> > > > > as usual phone (type H323 Client) to the CCM database and you have
> > > > > all features like search-space and so on.
> > > > >
> > > > > However, MTP can be checked there, too. I will try this.
> > > > >
> > > > >
> > > > >
> > > > > -------- Original-Nachricht --------
> > > > > Datum: Mon, 4 Jun 2007 11:21:39 -0500
> > > > > Von: "Jonathan Charles" <jonvoip at gmail.com>
> > > > > An: "db7td at gmx.de" <db7td at gmx.de>
> > > > > CC: cisco-voip at puck.nether.net
> > > > > Betreff: Re: [cisco-voip] Gatekeeper controlled devices with
> > > > > CCM4.2/IOS GK
> > > > >
> > > > > > On the trunk from CCM to the GK, did you check "MTP Required"?
> > > > > >
> > > > > > Where are you configuring the endpoints?
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > Jonathan
> > > > > >
> > > > > > On 6/4/07, db7td at gmx.de <db7td at gmx.de> wrote:
> > > > > > > Hi,
> > > > > > >
> > > > > > > I am trying to set up an endpoint gatekeeper as decribed in CCM4
> > > > > > > SRND.
> > > > > >
> > > > > > CCM registers to the GK, but CCM event log shows the following
> > > > > > error message
> > > > > >
> > > > > > when trying to configure an endpoint:
> > > > > > > Warning: H323Stopped - Cisco CallManager not ready to handle
> > > > > > > calls for
> > > > > >
> > > > > > the indicated H323 device.
> > > > > >
> > > > > > >   Device Name.: xxxxxxx
> > > > > > >   IP Address: xxxx
> > > > > > >   Device type. [Optional]: 61
> > > > > > >   Device description [Optional].: xxxxxxx
> > > > > > >   App ID: Cisco CallManager
> > > > > > >   Cluster ID: IPT-Cluster
> > > > > > >   Node ID: xxxx
> > > > > > > Explanation: Cisco CallManager is not ready to handle calls for
> > > > > > > the
> > > > > >
> > > > > > indicated H323 device.
> > > > > >
> > > > > > > Recommended Action: No action is required.
> > > > > > >
> > > > > > >
> > > > > > > I have added the H323 end device (a Tandberg terminal) to the
> > > > > > > database
> > > > > >
> > > > > > as "Gatekeeper controlled H.323 Client" with appropriate GK name,
> > > > > > E.164 value, tech-prefix (= 1#) and zone.
> > > > > >
> > > > > > > This is the GK config:
> > > > > > >
> > > > > > > gatekeeper
> > > > > > >  zone local MYZONE mydomain.i invia MYZONE outvia MYZONE
> > > > > >
> > > > > > enable-intrazone
> > > > > >
> > > > > > >  gw-type-prefix 1#* default-technology
> > > > > > >  no use-proxy MYZONE default inbound-to terminal
> > > > > > >  no use-proxy MYZONE default outbound-from terminal
> > > > > > >  no shutdown
> > > > > > >  endpoint ttl 60
> > > > > > >
> > > > > > > Calls from any (SCCP-) IP phone to the Tandberg terminal are
> > > > > > > woking, but
> > > > > >
> > > > > > the Tandberg can not call any CCM controlled device.
> > > > > >
> > > > > > > Any idea what's going wrong there?
> > > > > > >
> > > > > > >
> > > > > > > Thanks,
> > > > > > >   Dietmar
> > > > > > > _______________________________________________
> > > > > > > cisco-voip mailing list
> > > > > > > cisco-voip at puck.nether.net
> > > > > > > https://puck.nether.net/mailman/listinfo/cisco-voip
> > >
> > > --
> > > E-Mail: db7td at gmx.de
>
>
>
> --
> E-Mail: db7td at gmx.de
>