RE: Matching Voice Signalling traffic

From: Scott Morris (swm@emanon.com)
Date: Thu Sep 30 2004 - 11:31:22 GMT-3


H.323 voice (your voip dial peers) will use TCP 1720 as the signalling
(H.225 portion).

TCP 2000-2002 is the Cisco skinny stuff for the IP phones
I have no idea where 2748 comes from though. TCP 2428 (and UDP 2427) is
used for MGCP controls. You don't have MGCP on the R&S lab.

I wouldn't stress out about it. Not a core topic here. If you are looking
to go for the Voice CCIE, I'd know those ports plus the H.245 ones, SIP and
GK as well. Just a thought. But otherwise, no worries. :)

HTH,

 
Scott Morris, CCIE4 (R&S/ISP-Dial/Security/Service Provider) #4713, CISSP,
JNCIP, et al.
IPExpert CCIE Program Manager
IPExpert Sr. Technical Instructor
swm@emanon.com/smorris@ipexpert.net
http://www.ipexpert.net
 
 

-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
David Duncon
Sent: Thursday, September 30, 2004 9:02 AM
To: ccielab@groupstudy.com
Subject: Matching Voice Signalling traffic

Hello Group,

I am little unsure on the best way to *match* the Signaling traffic.

In the recent past I have a seen a config where the author has used to match
the destination port greater than TCP 3000 , equal to TCP 2000 & 2748. And
also equal to TCP 1720.

Can some please explain why these ports are necessary to match signaling
traffic. I was impression that signaling only uses TCP 1720 :(

And also like RTP using the *even* ports from 16384 to 32768 , I was
impression that Signaling uses *odd* ports in the same range ??

I appreciate any clarification on the above queries :-)

Thanks in advance

David.



This archive was generated by hypermail 2.1.4 : Fri Oct 01 2004 - 15:00:51 GMT-3