From marcoshack at gmail.com  Thu Jun  4 08:35:38 2009
From: marcoshack at gmail.com (Marcos Hack)
Date: Thu, 4 Jun 2009 12:35:38 -0300
Subject: [RTPproxy Users] Protocol documentation
Message-ID: <842e837b0906040835x40d12b11n25ed19d5545d4e77@mail.gmail.com>

Hello all,

Is there any additional documentation about RTPProxy protocol beyond
[1]? I would like to know what are the possible "[args]" that some
commands accept.

Thank you,
Marcos Hack.

[1] http://www.rtpproxy.org/wiki/RTPproxy/Protocol


From oriolc at voztele.com  Thu Jun  4 09:09:21 2009
From: oriolc at voztele.com (Oriol Capsada)
Date: Thu, 4 Jun 2009 18:09:21 +0200
Subject: [RTPproxy Users] RTP mapping after session update
Message-ID: <8F44456A-A271-48E5-9D1D-69B349F4C024@voztele.com>

Hi list,

Let me expose you a session update scenario to see how should the RTP  
packets be forwarded after the update command:

- A session is setup in the RTPproxy.

U 2009/06/03 17:20:34.502864 127.0.0.1:55660 -> 127.0.0.1:7899
   8621_88 U 229094d2-8d433f4 at 172.18.2.110 1.1.1.1 16454  
2f974f3a19a27caco1;1

U 2009/06/03 17:20:34.503319 127.0.0.1:7899 -> 127.0.0.1:55660
   8621_88 40980 9.9.9.9.

U 2009/06/03 17:20:36.144789 127.0.0.1:55332 -> 127.0.0.1:7899
   8620_92 L 229094d2-8d433f4 at 172.18.2.110 2.2.2.2 14046  
2f974f3a19a27caco1;1 9B3D5CCB0A55EFE3FD500996F5BB5514;1

U 2009/06/03 17:20:36.146491 127.0.0.1:7899 -> 127.0.0.1:55332
   8620_92 62166 9.9.9.9.

1.1.1.1:16454 <--------> 9.9.9.9:40980 (RTPproxy) 9.9.9.9:62166  
<---------> 2.2.2.2:14046

- RTPproxy receives and UPDATE command and it keeps receiving RTP  
packets from the first source

U 2009/06/03 17:20:39.465107 127.0.0.1:55660 -> 127.0.0.1:7899
   8621_89 U 229094d2-8d433f4 at 172.18.2.110 3.3.3.3 35108  
9B3D5CCB0A55EFE3FD500996F5BB5514;1 2f974f3a19a27caco1;1

U 2009/06/03 17:20:39.500070 127.0.0.1:7899 -> 127.0.0.1:55660
   8621_89 62166 9.9.9.9.

1.1.1.1:16454 <--------> 9.9.9.9:40980 (RTPproxy) 9.9.9.9:62166  
<---------> 2.2.2.2:14046
                                                                                           9.9.9.9 
:62166 <--------- 3.3.3.3:35108

In some cases the RTP mapping changes and the RTP received from  
1.1.1.1 is forwarded to 3.3.3.3, but in some other cases, it is still  
sent to 2.2.2.2.

How should the RTPproxy manage the following UPDATE situation? Should  
it change the IP addresses mapping to a different one than the first  
call established or should it change it to the first RTP packet it  
receives after the UPDATE (no matter if it was the same one as before  
or not) ?

I hope you can give me a hint on that.

Regards,
Oriol.


From lemenkov at gmail.com  Thu Jun  4 09:46:20 2009
From: lemenkov at gmail.com (Peter Lemenkov)
Date: Thu, 4 Jun 2009 20:46:20 +0400
Subject: [RTPproxy Users] Protocol documentation
In-Reply-To: <842e837b0906040835x40d12b11n25ed19d5545d4e77@mail.gmail.com>
References: <842e837b0906040835x40d12b11n25ed19d5545d4e77@mail.gmail.com>
Message-ID: <adf480660906040946i2cda64eeq8ffa200862cb8180@mail.gmail.com>

Hello!

2009/6/4 Marcos Hack <marcoshack at gmail.com>:
> Hello all,
>
> Is there any additional documentation about RTPProxy protocol beyond
> [1]?

No, afaik. But you may look into the sources of rtpproxy itself.

Also, very useful will be to look at the meanings of the additional
flags in the "force_rtp_proxy" function from the nathelper module of
ser/openser/opensipr/kamailio/sip-router:

http://kamailio.org/docs/modules/devel/nathelper.html#id2468157

-- 
With best regards!


From eric.vandeweyer at be.verizonbusiness.com  Thu Jun 25 06:04:24 2009
From: eric.vandeweyer at be.verizonbusiness.com (Vandeweyer, Eric)
Date: Thu, 25 Jun 2009 15:04:24 +0200
Subject: [RTPproxy Users]  RTP-Proxy as announcement server
In-Reply-To: a155b54dcea16606b34c25931a8fc0ba
References: a155b54dcea16606b34c25931a8fc0ba
Message-ID: <C4B7767B6B641243B4CC07F9000AE22807128299@ms-par-e3mb01.emea.dsmain.com>

Hey everyone,
 
Can the RTP-Proxy also be used as announcement server, to play an
announcement when a call fails ...
In case you can, can someone also tell me how I have to do this.
 
Many Thanks
 
Eric



NV Verizon Belgium Luxembourg SA - Siege social: Rue de la Science 37, 1040 Bruxelles, Belgique - Siege principal: Rue de la Science 37, 1040 Bruxelles, Belgique - Registre des Personnes Morales: RPM Bruxelles 0452.182.326

NV Verizon Belgium Luxembourg SA - Maatschappelijke zetel: Wetenschapsstraat 37, 1040 Brussel, Belgie - Hoofdzetel: Wetenschapsstraat 37, 1040 Brussel, Belgie -Rechtspersonenregister: RPR Brussel 0452.182.326
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.rtpproxy.org/pipermail/users/attachments/20090625/a8c6dc00/attachment.htm 

From lemenkov at gmail.com  Thu Jun 25 06:34:02 2009
From: lemenkov at gmail.com (Peter Lemenkov)
Date: Thu, 25 Jun 2009 17:34:02 +0400
Subject: [RTPproxy Users] RTP-Proxy as announcement server
In-Reply-To: <C4B7767B6B641243B4CC07F9000AE22807128299@ms-par-e3mb01.emea.dsmain.com>
References: <C4B7767B6B641243B4CC07F9000AE22807128299@ms-par-e3mb01.emea.dsmain.com>
Message-ID: <adf480660906250634h5439eff5vb2922f115da098b@mail.gmail.com>

2009/6/25 Vandeweyer, Eric <eric.vandeweyer at be.verizonbusiness.com>:
> Hey everyone,
>
> Can the RTP-Proxy also be used as announcement server, to play an
> announcement when a call fails ...

I'm sure that SEMS is the right tool for this task.


-- 
With best regards!