H.323 and dynamic addressing in cm 4.1.2

[f.chiesa]

All,

I'm trying to configure 2 netmeeting (h.323 device) registered to a gatekeeper, to be managed by a call manager v. 4.1.2 using the new feaure "dynamic addressing". This is based on the viazone feature on the GK. Now, i'm able to call from a IP phone to the netmeeting, or from a VTa to the netmeeting but I'm not able to call from the netmeeting to the "call manager" devices. I see from the trace that the call arrives to the CM but it reject the calls. Anyone has tried to do it and can give some indication? Probably there is something missing in the config.

Note: if the two netmeeting are configured statically on the CM with their IP address all works without problems.

Thanks,

Fabio

[irisrios]

Please make sure the following configurations are done.

1) You must ensure that gatekeeper is configured in Cisco CallManager before an H.323 client can specify that gatekeeper in its configuration. The Gatekeeper field stays empty by default.

2) Ensure that the Gatekeeper field on H.323 client configuration is configured as it is for H.323 trunk.

3) Be sure to add the gatekeeper name, technology prefix, zone, and E.164 fields to the H.323 client configuration. You do not need to add Terminal Type. Default specifies the gateway type. If the gatekeeper is not chosen for the gatekeeper field during configuration of each of these fields, these fields cannot populate.

4) Gatekeeper, zone, technology prefix fields, and E.164 information display under H.323 Information group on H.323 Client configuration.

5) When a H.323 client uses the same gatekeeper, zone and technology prefix as those of another client, consider both clients in the same group. This group represents a single endpoint to the gatekeeper.

6) You cannot use the same zone name for the H.323 client and trunk. A zone that a H.323 client uses must differ from the one that an H.323 trunk or a gatekeeper-controlled intercluster trunk uses.

7) Ensure service parameter Send Product Id and Version ID is set to True.

8) If a H.323 client is configured with an E.164 address and a gatekeeper, the database stores this information when the configuration is updated. This information gets loaded at boot time or when the device is reset.

[f.chiesa]

I have done some troubleshooting: if I change the endpoint with a VC station (tandberg) the problem doesn't appear. This is what happens on the CM:

04/04/2005 10:30:44.715 CCM|SPROCRas - {

h323-uu-pdu

{

h323-message-body setup :

{

protocolIdentifier { 0 0 8 2250 0 2 },

sourceAddress

{

h323-ID : "fabio chiesa"

--------------------->>>>>>>>>> source caller id E.164 number missing here !!!

},

sourceInfo

{

vendor

{

vendor

{

t35CountryCode 181,

t35Extension 0,

manufacturerCode 21324

},

productId '4D6963726F736F6674AE204E65744D656574696E67AE00'H,

versionId '332E3000'H

},

terminal

{

},

mc FALSE,

undefinedNode FALSE

},

destinationAddress

{

e164 : "80102"

},

activeMC FALSE,

conferenceID 'D86C767CDAD6464DBE7CFB8412014670'H,

conferenceGoal create : NULL,

callType pointToPoint : NULL,

sourceCallSignalAddress ipAddress :

{

ip '0A83422A'H,

port 1391

},

callIdentifier

{

guid |<:CMSLU1-CLUSTER><:CMSLU1>

04/04/2005 10:30:44.715 CCM|FF99A5D7DBAFCF479925C2A320CEAAB5'H

},

mediaWaitForConnect FALSE,

canOverlapSend FALSE

},

nonStandardData

{

nonStandardIdentifier h221NonStandard :

{

t35CountryCode 181,

t35Extension 0,

manufacturerCode 21324

},

data '0200000028000000000000001B0000008138427484CCD211B4E300A0C90D0660100000 ...'H

}

}|<:CMSLU1-CLUSTER><:CMSLU1>

04/04/2005 10:30:44.715 CCM|}|<:CMSLU1-CLUSTER><:CMSLU1>

04/04/2005 10:30:44.715 CCM|H225Handler::getSourceE164Address ERROR Could not find e164 address|<:CMSLU1-CLUSTER><:CMSLU1><:1><:10.131.66.42><:>

04/04/2005 10:30:44.715 CCM|e164 H225Handler::parseAndFwdH225uuie ERROR Incoming H225 call, Could not find H225D (client or gateway is missing)|<:CMSLU1-CLUSTER><:CMSLU1><:1><:10.131.66.42><:>

04/04/2005 10:30:44.715 CCM|value H323-UserInformation ::= |<:CMSLU1-CLUSTER><:CMSLU1>

04/04/2005 10:30:44.715 CCM|{

h323-uu-pdu

{

h323-message-body releaseComplete :

{

protocolIdentifier { 0 0 8 2250 0 2 },

callIdentifier

{

guid 'FF99A5D7DBAFCF479925C2A320CEAAB5'H

}

},

h245Tunneling FALSE

}|<:CMSLU1-CLUSTER><:CMSLU1>