Hi all: in http://www.voip-info.org/tiki-index.php?page=Portaone%20rtpproxy is says rtpprxoy will waits for receiving at least one UDP packet from each of two parties participating in the call Once suc packet is received, the proxy fills one of two ip:port structures associated with each call with source ip:port of that packet and when both structures are filled in, the proxy starts relaying UDP packets between parties; is it always do so ? Cause when I have try rtpproxy with nathelper , but when i trace the etherreal log rtpproxy's behavior seems not waits for receiving at least one UDP packet from each of two parties after when receive only one part of the UA , rtpproxy directly transfering the rtp packet to another UA
Can any tell me will rtpproxy wait for when both UA's first packet has received then start relay it ?
Or it's behavior is really the same as the page said ? (http://www.voip-info.org/tiki-index.php?page=Portaone%20rtpproxy)
Thanks Jimmy
The old rtpproxy (1.1.1.1) has to wait for at least one packet from each client. For the new version of rtpproxy it depends on the configuration, i.e. if the rtpproxy is symmetric on both ends or only on one end.
klaus
jimmy huang wrote:
Hi all: in http://www.voip-info.org/tiki-index.php?page=Portaone%20rtpproxy is says rtpprxoy will waits for receiving at least one UDP packet from each of two parties participating in the call Once suc packet is received, the proxy fills one of two ip:port structures associated with each call with source ip:port of that packet and when both structures are filled in, the proxy starts relaying UDP packets between parties; is it always do so ? Cause when I have try rtpproxy with nathelper , but when i trace the etherreal log rtpproxy's behavior seems not waits for receiving at least one UDP packet from each of two parties after when receive only one part of the UA , rtpproxy directly transfering the rtp packet to another UA
Can any tell me will rtpproxy wait for when both UA's first packet has received then start relay it ?
Or it's behavior is really the same as the page said ? (http://www.voip-info.org/tiki-index.php?page=Portaone%20rtpproxy)
Thanks Jimmy
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Klaus Darilion wrote:
The old rtpproxy (1.1.1.1) has to wait for at least one packet from each client. For the new version of rtpproxy it depends on the configuration, i.e. if the rtpproxy is symmetric on both ends or only on one end.
The default behaviour is to start relaying immediately to the port specified in the SDP, but once the firt packet from UA has been received check that actual source port match and update internal session data if it does not so that all subsequent packets will be relayed to the proper "NAT hole".
-Maxim
klaus
jimmy huang wrote:
Hi all: in http://www.voip-info.org/tiki-index.php?page=Portaone%20rtpproxy is says rtpprxoy will waits for receiving at least one UDP packet from each of two parties participating in the call Once suc packet is received, the proxy fills one of two ip:port structures associated with each call with source ip:port of that packet and when both structures are filled in, the proxy starts relaying UDP packets between parties; is it always do so ? Cause when I have try rtpproxy with nathelper , but when i trace the etherreal log rtpproxy's behavior seems not waits for receiving at least one UDP packet from each of two parties after when receive only one part of the UA , rtpproxy directly transfering the rtp packet to another UA
Can any tell me will rtpproxy wait for when both UA's first packet has received then start relay it ?
Or it's behavior is really the same as the page said ? (http://www.voip-info.org/tiki-index.php?page=Portaone%20rtpproxy)
Thanks Jimmy
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Maxim Sobolev wrote:
Klaus Darilion wrote:
The old rtpproxy (1.1.1.1) has to wait for at least one packet from each client. For the new version of rtpproxy it depends on the configuration, i.e. if the rtpproxy is symmetric on both ends or only on one end.
The default behaviour is to start relaying immediately to the port specified in the SDP, but once the firt packet from UA has been received check that actual source port match and update internal session data if it does not so that all subsequent packets will be relayed to the proper "NAT hole".
Cool, a nice feature - I guess I should give the new rtpproxy a try. :-)
Klaus
Hi,
how can i check which version of rtpproxy i am running? There is no "-v / show version option" and and a "grep -i version" on the source files doesnt reveal anything too.
Is this http://www.portaone.com/~sobomax/rtpproxy.tar the latest release?
:: arnd ::
take a look at main.c - the line before the history reveals the version.
* * $Id: main.c,v 1.19 2004/04/20 17:10:40 sobomax Exp $ * * History: * --------
regards, klaus
Arnd Vehling wrote:
Hi,
how can i check which version of rtpproxy i am running? There is no "-v / show version option" and and a "grep -i version" on the source files doesnt reveal anything too.
Is this http://www.portaone.com/~sobomax/rtpproxy.tar the latest release?
:: arnd ::
Klaus Darilion wrote:
take a look at main.c - the line before the history reveals the version.
- $Id: main.c,v 1.19 2004/04/20 17:10:40 sobomax Exp $
- History:
ok, so thats the most recent version then?
:: arnd ::
To check the different versions of the files I always use the web-cvs. http://cvs.berlios.de/cgi-bin/viewcvs.cgi/ser/rtpproxy/ As you see, 1.19 is the most recent version.
I especially like the revision graph (the small icon left to the version number), which shows the several branches and tags, e.g. http://cvs.berlios.de/cgi-bin/viewcvs.cgi/ser/rtpproxy/main.c?graph=1.19
regards, Klaus
Arnd Vehling wrote:
Klaus Darilion wrote:
take a look at main.c - the line before the history reveals the version.
- $Id: main.c,v 1.19 2004/04/20 17:10:40 sobomax Exp $
- History:
ok, so thats the most recent version then?
:: arnd ::
Arnd Vehling wrote:
Hi,
how can i check which version of rtpproxy i am running? There is no "-v / show version option" and and a "grep -i version" on the source files doesnt reveal anything too.
Is this http://www.portaone.com/~sobomax/rtpproxy.tar the latest release?
No, it is not the latest one. The latest one is available from the ser's cvs, module rtpproxy. Check http://www.iptel.org/ser/ for details on how to get source code from ser's cvs repository.
-Maxim
-
Arnd Vehling -
jimmy huang -
Klaus Darilion -
Maxim Sobolev