11-05-2010 09:59 AM - edited 03-16-2019 01:45 AM
GK responding back to our IPIP GWY with ACF message but with IP address of destination remote missing–
value RasMessage ::= admissionConfirm :
{
requestSeqNum 39
bandWidth 160
callModel direct : NULL
destCallSignalAddress ipAddress : <MISSING>
… …
>Show gatekeeper endpoints
Showed the site is registered. Site was pingable. I rebooted GK. Waited 20 minutes and saw no site registration into GK but it eventually registered.
11-05-2010 10:52 AM
can u provide following from the GK?
deb h225 asn1
deb gatekeep main 10
sh gatek end
sh gatek zone prefix all
sh gatek gw
sh run
Pl. point to the ACF in ques.
11-05-2010 12:31 PM
See below for some of the requested info. We fixed it by rebooting the H323 TERMINAL. Even though GK showed TERM registered (and pingable), for some reason GK would not respond back with an IP of the TERM in the ACF message. The GK should've aged out the terminal if it wasn't a valid registration anymore. Since its working now, I cannot get you a full trace of all the information requested. The ACF message I posted was the actual message when it failed. I did not include all of it since it wasn't relevant.
--------------------------------
2901-GK-1#sh gatek end
GATEKEEPER ENDPOINT REGISTRATION
================================
CallSignalAddr Port RASSignalAddr Port Zone Name Type Flags
--------------- ----- --------------- ----- --------- ---- -----
172.17.152.129 1720 172.17.152.129 1719 gk-hns TERM
E164-ID: 5550304
E164-ID: 5550305
H323-ID: HN_Test
192.168.12.177 1720 192.168.12.177 57295 gk-hns H323-GW
H323-ID: ipip1@hns
Voice Capacity Max.= Avail.= Current.= 0
Total number of active registrations = 2
No zone prefix are defined. Its one big zone with intra-zone enabled calls.
2901-GK-1#sh gatek gw
GATEWAY TYPE PREFIX TABLE
=========================
Prefix: 1#* (Default gateway-technology)
Zone gk-hns master gateway list:
192.168.12.177:1720 ipip1
Prefix: 2#*
11-05-2010 01:56 PM
Correct..GK shd have flagged it or forced unregister the terminal
if there was an issue with TTL or Reg refresh.
But ofcourse that didn't happen. If GK was infact seeing it as
registered, it shd have returned proper IP address in the ACF.
So I agree some sort of glitch on the GK. If it happens again,
please do capture info requested.
Also, do u know if the terminal supports h323 ver v1 or a v2 ?
What do u see for TTL in RRQ ?
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: