After reading your kindly reply, I got following list for blocking VoIP at edge router: 1. block traffic on port 1719, 1720 (both tcp/udp), but this could not deal with those who modified signaling port; 2. content filtering by using some special euqipment; , very expensive 3. legismation by gov., well I don't think this could be a method possible 4. ???? for IM with voice ability 5. change QoS level for marked packets, (how could it be done with no QoS network, RED ?) here goes my further question: a) Could WRED be applied with current network for VoIP packets selectively? ( I means RTP packets carrying unwanted VoIP ) b) Is there anyway to cache those equipment modifying signaling port number? c) any better way ? any experience? regards Joe --- Robert Mathews <mathews@hawaii.edu> wrote:
On Thu, 11 Nov 2004, Christopher L. Morrow wrote:
Date: Thu, 11 Nov 2004 19:49:10 +0000 (GMT) From: Christopher L. Morrow <christopher.morrow@mci.com> To: Robert Mathews <mathews@hawaii.edu> Cc: NANOG <nanog@merit.edu> Subject: Re: How to Blocking VoIP ( H.323) ?
On Thu, 11 Nov 2004, Robert Mathews wrote:
To Joe Shen:
Perhaps 'I am failing to see it' but, what can
be gained by blocking VoIP
traffic other than freeing bandwidth and CPU churnings?
reference panamanian gov'ts choice to protect legacy/incumbant carrier business by blocking voip. no one said it was 'smart' just that it was what the gov't wanted. Perhaps Joe lives in a similar situation?
Hi Chris:
Indeed.... hegemonic tendencies/behaviour by telcos aside, I was attempting to understand if there were 'some' ORGANIZATIONAL dyscrasias that prohibited 'operationlizing' of VoIP. To be brief, I would humbly submit that any malady in this area is worthy of greater exploration IF ONLY to expedite and effectuate the alignment of org-to-org operational instruments and their respective interfaces.
Best, Robert. -------
__________________________________________________ Do You Yahoo!? Log on to Messenger with your mobile phone! http://sg.messenger.yahoo.com