04-28-06 12:11 AM
I stand corrected. I thought the syntax was range only at the end but I
got on my router and ......................... Once again I"M WRONG....
Thanks for bring it to my attention Ed.
Scott
________________________________
From: Ed Leatherman [mailto:ealeatherman@gmail.com]
Sent: Thursday, April 27, 2006 4:15 PM
To: Voll, Scott
Cc: Robin H; cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] TCP/UDP ports used by CCM3.3
I think option 1 also.
I'm curious though, why can you only put the range at the end?
On 4/27/06, Voll, Scott < Scott.Voll@wesd.org
<mailto:Scott.Voll@wesd.org> > wrote:
I believe the range and ports can only go at the end so the first one
would be right.
Scott
-----Original Message-----
From: cisco-voip-bounces@puck.nether.net
[mailto: cisco-voip-bounces@puck.nether.net
<mailto:cisco-voip-bounces@puck.nether.net> ] On Behalf Of Robin H
Sent: Thursday, April 27, 2006 6:44 AM
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] TCP/UDP ports used by CCM3.3
I read document for TCP/UDP ports used by cisco CallManager 3.3 but
still not sure how to apply the ACL to match the requirement for
marking RTP packets.
In the document, it is stated for RTP uses "Remote Source Port" and
"Remote Device Destination Port" value UDP 16384 - 32767 so when I
want to use LLQ for outgoing ACL at remote gateway to match it, which
one is correct?
1. access-list 100 permit udp any any range 16384 32767
2. access-list 100 permit udp any any range 16384 32767
access-list 100 permit udp any range 16384 32767 any
Anyone can enlighten me? thanks
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
--
Ed Leatherman
IP Telephony Coordinator
West Virginia University
Telecommunications and Network Operations
Attachment:
This has been downloaded 0 time(s).
[ Post a follow-up to this message ]
|