Re: Sip Traffic

Linux Advanced Routing and Traffic Control

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



About SIP: the traffic does not "jump" at a random port, it is another type of traffic that you see afterwards, it's the RTP stream.
SIP is used only for signaling a session hence the name Session Initiation Protocol. The SIP messages contain the IP Address + Port where the RTP flow will appear. The RTP might not have the same IP address as the SIP destination. If you want to prioritize SIP and RTP you can use your own SIP Proxy (i'm using SER from www.iptel.org) with somekind of gateway (RTPPROXY may be just enough for an end user).
By the way, if some SIP clients do not find port 5060 free, they choose cvasi-randomly another port.

Marius

On 4/21/06, Francisco <ranmakun@xxxxxxxxxxxx> wrote:
L7 filter works very well too:
http://l7-filter.sourceforge.net/

Although I didn't try it with sip, I use it to control my P2P and server
applications and have a very usable ADSL link at almost 100% utilization of
my upstream.


El Martes, 18 de Abril de 2006 07:45, LinuXKiD escribió:
> mmm... intresting....
>
> http://sipx-wiki.calivia.com/index.php/HowTo_configure_iptables
>
> ip_conntrack_sip
>
> Someone has tried it ?
>
> works on 2.4 kernel series ?
>
> thanks
>
>
>
>
> ->
> ->
> -> Hi I am pretty much a newbie, I found with sip if I match ports 5060 and
> -> 10000 - 20000 it works I noticed on some phones the use 13000 - 14000
> and -> others use 18000 - 19000.  there is a new sip-contrack out although
> I -> haven't tried it yet.
> ->
> -> william
> ->
> -> -----Original Message-----
> -> From: lartc-bounces@xxxxxxxxxxxxxxx
> -> [mailto: lartc-bounces@xxxxxxxxxxxxxxx]
> -> On Behalf Of LinuXKiD
> -> Sent: 17 April 2006 15:59
> -> To: lartc
> -> Subject: Sip Traffic
> ->
> ->
> -> Hi.
> ->
> -> there is a way to MARK udp VOIP (SIP) traffic,
> -> in order to put in a highest prio class ?
> ->
> -> Traffic flow seems start on udp 5060 port, but
> -> next both server and client seems jump to a
> -> random(?) port.
> ->
> -> I can't use CONNMARK because is udp traffic.
> ->
> -> I only see a pattern for L7 patch in order to
> -> SIP traffic identification , but I run 2.4
> -> kernel series .
> ->
> -> When you patch 2.4 kernel with L7 patch,
> -> later, Connmark (patch o matic ) can't apply.
> -> (conflicts)
> ->
> -> thank you.
> -> --
> -> Andres
> -> _______________________________________________
> -> LARTC mailing list
> -> LARTC@xxxxxxxxxxxxxxx
> -> http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
> ->
>
> _______________________________________________
> LARTC mailing list
> LARTC@xxxxxxxxxxxxxxx
> http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
_______________________________________________
LARTC mailing list
LARTC@xxxxxxxxxxxxxxx
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

_______________________________________________
LARTC mailing list
LARTC@xxxxxxxxxxxxxxx
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

[Index of Archives]     [LARTC Home Page]     [Netfilter]     [Netfilter Development]     [Network Development]     [Bugtraq]     [GCC Help]     [Yosemite News]     [Linux Kernel]     [Fedora Users]
  Powered by Linux