| Jens Faulhaber 2005-12-06, 5:45 pm |
| Its in configured in the CM as a H.323 Client - but gatekeeper controlled. =
-> in the NetMeeting we entered the GK address and E.164 info.
-----Urspr=FCngliche Nachricht-----
Von: Ryan Ratliff [mailto:rratliff@cisco.com] =
Gesendet: Dienstag, 6. Dezember 2005 16:57
An: Jens Faulhaber
Cc: cisco-voip@puck.nether.net
Betreff: Re: [cisco-voip] RASAggregator trunk issue
Is H323TRM03 added as an H.323 gateway in the CCMAdmin? By default =
CM will not accept calls from H.323 endpoints that are not in the =
database.
-Ryan
On Dec 6, 2005, at 10:31 AM, Jens Faulhaber wrote:
Hi Guys mabe one of you can help us.....
We have the following issue:
We are using CCM 4.1.3 SR 1 and we have the issue that the =
RASAggregator trunk is not working properly.
It is setup as described in the SRND but our NetMeeting clients are =
not able to call any client registered on CCM. They can receive calls =
but cannot set up the call by themselves.
The configuration looks like that.
H323TRM01 - gatekeeper controlled - this is the RASAggregator trunk =
to our gatekeeper - and successfully registered on the GK. With the =
DN 1101
H323TRM03 - registered on CCM via IP with the DN 1002
Gatekeeper on 2611 with IOS 2600-ix-mz.123-14.T5.bin and the GK config.
zone local sj-zone cisco.com invia sj-zone outvia sj-zone enable- =
intrazone
gw-type-prefix 1#* default-technology
no use-proxy sj-zone default inbound-to terminal
no use-proxy sj-zone default outbound-from terminal
no shutdown
endpoint ttl 60
the GK show command show that everything should be fine....
GK01#sh gatekeeper endpoints
GATEKEEPER ENDPOINT REGISTRATION
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
3D
CallSignalAddr Port RASSignalAddr Port Zone Name Type =
Flags
--------------- ----- --------------- ----- --------- ---- =
-----
10.1.1.1 49875 10.1.1.1 49821 sj-zone H323-GW
H323-ID: RasAggregator16_sj-zone_1
Voice Capacity Max.=3D Avail.=3D Current.=3D 0
10.128.128.65 1720 10.128.128.65 2295 sj-zone TERM
E164-ID: 1103
10.128.128.113 1720 10.128.128.113 2363 sj-zone TERM
E164-ID: 1101
Total number of active registrations =3D 3
GK01#sh gatekeeper gw-type-prefix
GATEWAY TYPE PREFIX TABLE
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Prefix: 1#* (Default gateway-technology)
Zone sj-zone master gateway list:
10.1.1.1:49875 RasAggregator16_sj-zone_1
The CallManager can process the call from H323TRM03 (non GK =
controlled) to the H323TRM01 (GK controlled)
In the CCM trace we find the info that the CCM cannot process the =
call because he does not find the DN or GW
We find that CC trace output for every unsucessfull call:
}|<CLID::StandAloneCluster><NID::10.1.1.1>
12/06/2005 10:56:42.942 CCM|}|<CLID::StandAloneCluster><NID::10.1.1.1>
12/06/2005 10:56:42.958 CCM|H225Handler::getSourceE164Address ERROR =
Could not find e164 address|<CLID::StandAloneCluster><NID:: =
10.1.1.1><CT::1,100,132,143.1><IP::10.128.128.113><DEV::>
12/06/2005 10:56:42.958 CCM|e164 H225Handler::parseAndFwdH225uuie =
ERROR Incoming H225 call, Could not find H225D (client or gateway is =
missing)|<CLID::StandAloneCluster><NID::10.1.1.1><CT:: =
1,100,132,143.1><IP::10.128.128.113><DEV::>
12/06/2005 10:56:42.958 CCM|value H323-UserInformation ::=3D | =
<CLID::StandAloneCluster><NID::10.1.1.1>
And now the Gatekeeper gets a DRQ from the CCM and the call fails....
Do you have any ideas where our issues are?
___________________
Jens Faulhaber
Senior IT-Consultant
avodaq AG
Moosstra=DFe 16
82319 Starnberg
Tel.: +49 8151 36858347
Mobil: +49 163 7788247
Fax: +49 8151 91 8382
http://www.avodaq.com
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
|