cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
6075
Views
5
Helpful
5
Replies

Gateway/Gatekeeper port 1718 & 1719

yytellmey
Level 1
Level 1

Hi guys,

How to use port 1718 and 1719 in gateway and gatekeeper?

When I configure gateway and gatekeepter, I got the both default port 1719. Is it right? Should I change them? They are UDP or TCP port? What are their functions?

GW-A1#

!

interface Ethernet0/0

ip address 172.22.1.1 255.255.255.0

h323-gateway voip interface

h323-gateway voip id GK-A ipaddr 172.22.1.3 1719

h323-gateway voip h323-id GW-A1@abc.com

h323-gateway voip tech-prefix 1#

!

GK-A#

!

gatekeeper

zone local GK-A abc.com

zone remote GK-B abc.com 172.22.2.3 1719

zone prefix GK-B 214.......

zone prefix GK-A 512.......

gw-type-prefix 1#* default-technology

arq reject-unknown-prefix

no shutdown

!

Thanks a lot.

yytellmey

5 Replies 5

baytan
Level 1
Level 1

1- ras signalling port to communicate between gk and remote gk is 1719 default. (inter zone ras)

2-ras signalling port to communicate between gw and local gk is 1718 default. (intra zone ras)

3-both 1718 and 1719 ras signalling ports are tcp ports.

4- you can change default ports by using:

on gateways:

h323-gateway voip id yyyy ipaddr x.x.x.x [port number]

on gatekeepers:

zone remote yyyy zzzz.com x.x.x.x [port number]

5- changing default ports is not a "must",but can be done, and also i advise not to change unless you really need it.

6-these ports are used for ras signalling for both gk-to-gk and gw-to-gk.

I have a maybe related question....

how do i prevent an H323 GW,AS5300 w 12.3(13),

from continually trying to register with some GK it finds on the net....

Mar 16 20:16:50 GMT: %CCH323-2-GTWY_REGSTR_FAILED: Gateway PRBppd failed to register with Gatekeeper tbhudnws.TOABAJAHUD.LOCAL even after 2 retries

Mar 16 20:17:06 GMT: %CCH323-2-GTWY_REGSTR_FAILED: Gateway PRBppd failed to register with Gatekeeper tbhudnws.TOABAJAHUD.LOCAL even after 2 retries

voipgw#

Rich

RAS Gatekeeper Discovery:

There are two processes by which H.323 terminals/gateways discover their zone gatekeepers:

Unicast Discovery (manual method) - Uses UDP port 1718. In this process, endpoints are configured with the gatekeeper IP address and can attempt registration immediately. The gatekeeper replies with a gatekeeper confirm (GCF) or gatekeeper rejection (GRJ) message.

Multicast Discovery (auto-discovery) - Uses UDP multicast address 224.0.1.41. Auto discovery enables an endpoint to discover its gatekeeper through a multicast message. Because endpoints do not have to be statically configured for gatekeepers, this method has less administrative overhead. A gatekeeper replies with a GCF message or remains silent. A gatekeeper can be configured to respond only to certain subnets.

If a gatekeeper is not available, the gateway periodically attempts to rediscover a gatekeeper. If a gateway discovers the gatekeeper has gone off-line, it stops accepting new calls and attempts to rediscover a gatekeeper. Active calls are not affected.

baytan
Level 1
Level 1

baytan
Level 1
Level 1

Sorry, made a mistake. RAS uses udp 1718 and 1719, not tcp!!!