Gatekeeper port number 1718 or 1719

Answered Question
Dec 25th, 2009

Hi

Here is a sample from IOS command ref:

- h323-gateway voip id GK2 ipaddr 172.18.193.65 1719

Some other doc on ciso site use port 1718 instead of 1719

What is the right one?

Thanks for help.

I have this problem too.
0 votes
Correct Answer by Paul Jones about 7 years 3 weeks ago

/* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-qformat:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin-top:0in; mso-para-margin-right:0in; mso-para-margin-bottom:10.0pt; mso-para-margin-left:0in; line-height:115%; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:"Times New Roman"; mso-fareast-theme-font:minor-fareast; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;}

Jonathan's reply is correct, but to be more precise, 1718 is for multicast signaling and 1719 is for unicast signaling.  I noted that the documentation he referenced is actually wrong, as it presently says that 1718 is for unicast traffic.  I'll see if I can get that corrected.  A correct listing of ports is shown here: http://www.packetizer.com/in/q119.html.

Virtually every real-world deployment I've seen uses unicast for discovery, registration, etc., so port 1719 is probably the only port you need.  That said, there has been confusion over these ports for years in the industry, so most devices will listen for traffic on both ports and you might encounter some devices that send unicast traffic to port 1718. While I recommend proper usage, I would expect that both ports might be used interchangeably.

Cheers!

Paul

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4.5 (4 ratings)
Loading.
Correct Answer
Paul Jones Fri, 12/25/2009 - 10:29

/* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-qformat:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin-top:0in; mso-para-margin-right:0in; mso-para-margin-bottom:10.0pt; mso-para-margin-left:0in; line-height:115%; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:"Times New Roman"; mso-fareast-theme-font:minor-fareast; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;}

Jonathan's reply is correct, but to be more precise, 1718 is for multicast signaling and 1719 is for unicast signaling.  I noted that the documentation he referenced is actually wrong, as it presently says that 1718 is for unicast traffic.  I'll see if I can get that corrected.  A correct listing of ports is shown here: http://www.packetizer.com/in/q119.html.

Virtually every real-world deployment I've seen uses unicast for discovery, registration, etc., so port 1719 is probably the only port you need.  That said, there has been confusion over these ports for years in the industry, so most devices will listen for traffic on both ports and you might encounter some devices that send unicast traffic to port 1718. While I recommend proper usage, I would expect that both ports might be used interchangeably.

Cheers!

Paul

Actions

This Discussion