<div dir="ltr"><span style="font-family:arial,sans-serif;font-size:13px"> Re: Route RTP packets through</span><br><div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:13px">Hello Razvan,</span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:13px">Yes i am using "r" as </span><font face="arial, sans-serif">rtpproxy_offer("r","xx.xx.xx.xx"); </font></div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jun 11, 2014 at 11:00 PM, <span dir="ltr"><<a href="mailto:users-request@lists.opensips.org" target="_blank">users-request@lists.opensips.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send Users mailing list submissions to<br>
<a href="mailto:users@lists.opensips.org">users@lists.opensips.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:users-request@lists.opensips.org">users-request@lists.opensips.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:users-owner@lists.opensips.org">users-owner@lists.opensips.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of Users digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Route RTP packets through (kaushik parmar)<br>
2. Re: Route RTP packets through (R?zvan Crainea)<br>
3. binary replication (Tito Cumpen)<br>
4. mediaproxy bug with offer answer in different transaction<br>
(Eric Tamme)<br>
5. Re: RabbitMQ Timer Route Not Working (Kneeoh)<br>
6. Re: binary replication (Liviu Chircu)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Wed, 11 Jun 2014 17:21:24 +0530<br>
From: kaushik parmar <<a href="mailto:androidjpc0@gmail.com">androidjpc0@gmail.com</a>><br>
Subject: [OpenSIPS-Users] Route RTP packets through<br>
To: <a href="mailto:devel@lists.opensips.org">devel@lists.opensips.org</a>, <a href="mailto:users@lists.opensips.org">users@lists.opensips.org</a><br>
Message-ID:<br>
<<a href="mailto:CAGzPE1-w0CXqURBPByHwEF_fRdabkpmrVT%2BtX0tcSjqFdxV7zA@mail.gmail.com">CAGzPE1-w0CXqURBPByHwEF_fRdabkpmrVT+tX0tcSjqFdxV7zA@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hello ,<br>
<br>
I am using opensips and rtpproxy for sip and rtp proxy server. Here problem<br>
is rtpproxy is sending rtp packets on private ip address and so packet lost.<br>
<br>
How to use nat so 66.33.66.256 can transfer rtp packets on nated ip instead<br>
of private ip network that available in SDP.<br>
<br>
*Current Scenario : *<br>
<br>
Peer1(public IP) opensips+rtpproxy Voip Switch Peer1(public IP)<br>
<br>
49.91.256.235 66.33.66.256<br>
78.20.56.23 192.168.1.50<br>
<br>
| | RTP (G729) | |<br>
<br>
| RTP (G729) |<-------------------| |<br>
<br>
|--------------------->| RTP (G729) |<br>
|<br>
<br>
| |--------------------------------->|<br>
<br>
<br>
<br>
*Actual Scenario Should be : *<br>
<br>
<br>
<br>
Peer1(public IP) opensips+rtpproxy Voip Switch Peer1(public IP)<br>
<br>
49.91.256.235 66.33.66.256<br>
78.20.56.23 192.168.1.50<br>
<br>
| | RTP (G729) |<br>
|<br>
<br>
| RTP (G729) |<-------------------| |<br>
<br>
|--------------------->| RTP (G729) |<br>
|<br>
<br>
| RTP (G729)<br>
|---------------------------------->| |<br>
<br>
|<---------------------| | |<br>
<br>
<br>
--<br>
Kind regards,<br>
<br>
Kaushik Parmar<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.opensips.org/pipermail/users/attachments/20140611/3a12849d/attachment-0001.htm" target="_blank">http://lists.opensips.org/pipermail/users/attachments/20140611/3a12849d/attachment-0001.htm</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Wed, 11 Jun 2014 14:52:15 +0300<br>
From: R?zvan Crainea <<a href="mailto:razvan@opensips.org">razvan@opensips.org</a>><br>
Subject: Re: [OpenSIPS-Users] Route RTP packets through<br>
To: <a href="mailto:users@lists.opensips.org">users@lists.opensips.org</a><br>
Message-ID: <<a href="mailto:539842EF.1080001@opensips.org">539842EF.1080001@opensips.org</a>><br>
Content-Type: text/plain; charset=UTF-8; format=flowed<br>
<br>
Hi, Kaushik!<br>
<br>
Are you using the "r" flag for rtpproxy_offer/answer() functions?<br>
<br>
Best regards,<br>
<br>
Razvan Crainea<br>
OpenSIPS Core Developer<br>
<a href="http://www.opensips-solutions.com" target="_blank">http://www.opensips-solutions.com</a><br>
<br>
On 06/11/2014 02:51 PM, kaushik parmar wrote:<br>
> Hello ,<br>
><br>
> I am using opensips and rtpproxy for sip and rtp proxy server. Here<br>
> problem is rtpproxy is sending rtp packets on private ip address and so<br>
> packet lost.<br>
><br>
> How to use nat so 66.33.66.256 can transfer rtp packets on nated ip<br>
> instead of private ip network that available in SDP.<br>
><br>
> *Current Scenario :*<br>
><br>
><br>
> Peer1(public IP) opensips+rtpproxy Voip SwitchPeer1(public IP)<br>
><br>
> 49.91.256.235 66.33.66.256 78.20.56.23 192.168.1.50<br>
><br>
><br>
> | |RTP (G729) | |<br>
><br>
> |RTP (G729) |<-------------------||<br>
><br>
> |--------------------->|RTP (G729) | |<br>
><br>
> | |--------------------------------->|<br>
><br>
><br>
><br>
><br>
><br>
> *Actual Scenario Should be :*<br>
><br>
> *<br>
> *<br>
><br>
> *<br>
> *<br>
><br>
> Peer1(public IP) opensips+rtpproxy Voip SwitchPeer1(public IP)<br>
><br>
> 49.91.256.235 66.33.66.256 78.20.56.23 192.168.1.50<br>
><br>
><br>
> | |RTP (G729) | |<br>
><br>
><br>
> |RTP (G729) |<-------------------||<br>
><br>
><br>
> |--------------------->|RTP (G729) | |<br>
><br>
> |RTP (G729) |---------------------------------->| |<br>
><br>
><br>
> |<---------------------| | |<br>
><br>
><br>
> --<br>
> Kind regards,<br>
><br>
> Kaushik Parmar<br>
><br>
><br>
> _______________________________________________<br>
> Users mailing list<br>
> <a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
> <a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
><br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Wed, 11 Jun 2014 08:27:58 -0400<br>
From: Tito Cumpen <<a href="mailto:tito@xsvoce.com">tito@xsvoce.com</a>><br>
Subject: [OpenSIPS-Users] binary replication<br>
To: OpenSIPS users mailling list <<a href="mailto:users@lists.opensips.org">users@lists.opensips.org</a>><br>
Message-ID:<br>
<CANZPVB4ou3Jg0P=qStgzTaHq2HxrBiFQWhwFXarVJV=<a href="mailto:znb1uAw@mail.gmail.com">znb1uAw@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Group,<br>
<br>
Playing with the idea of using binary replication. Just curious if anyone<br>
can provide a use case. Would this coupled with a virtual ip? I am not<br>
certain how the instance that accepts replications would take over.<br>
<br>
<br>
Thanks,<br>
Tito<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.opensips.org/pipermail/users/attachments/20140611/f73c5049/attachment-0001.htm" target="_blank">http://lists.opensips.org/pipermail/users/attachments/20140611/f73c5049/attachment-0001.htm</a>><br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Wed, 11 Jun 2014 08:53:47 -0600<br>
From: Eric Tamme <<a href="mailto:eric.tamme@onsip.com">eric.tamme@onsip.com</a>><br>
Subject: [OpenSIPS-Users] mediaproxy bug with offer answer in<br>
different transaction<br>
To: <a href="mailto:users@lists.opensips.org">users@lists.opensips.org</a><br>
Message-ID: <<a href="mailto:53986D7B.70007@onsip.com">53986D7B.70007@onsip.com</a>><br>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed<br>
<br>
Hi Sa?l, and others,<br>
<br>
We have discovered a bug in mediaproxy where it does not recognize an<br>
answer that is part of a different transaction, this is caused by how<br>
mediaproxy tracks offer/answer based on cseq. Here is the example offer<br>
answer scenario from RFC3262 that does not work.<br>
<br>
UAC INVITE Cseq: 1 (no SDP offer) -><br>
<br>
<- 183 with SDP offer<br>
<br>
PRACK CSeq: 2, Rseq: 1 with SDP answer-><br>
<br>
Because the PRACK is a different transaction, and has a different CSeq<br>
than the offer, mediaproxy assumes it is a new offer, rather than an answer.<br>
<br>
Can you offer any thoughts on what might be the best way to fix this<br>
issue? We are happy to work on a patch as well - but would like to have<br>
input from the maintainers so that we can be sure it would be accepted<br>
upstream.<br>
<br>
Thanks,<br>
<br>
-Eric<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Wed, 11 Jun 2014 10:08:31 -0700 (PDT)<br>
From: Kneeoh <<a href="mailto:kneeoh@yahoo.com">kneeoh@yahoo.com</a>><br>
Subject: Re: [OpenSIPS-Users] RabbitMQ Timer Route Not Working<br>
To: R?zvan Crainea <<a href="mailto:razvan@opensips.org">razvan@opensips.org</a>>, Opensips Users<br>
<<a href="mailto:users@lists.opensips.org">users@lists.opensips.org</a>><br>
Message-ID:<br>
<<a href="mailto:1402506511.64730.YahooMailNeo@web122606.mail.ne1.yahoo.com">1402506511.64730.YahooMailNeo@web122606.mail.ne1.yahoo.com</a>><br>
Content-Type: text/plain; charset=utf-8<br>
<br>
Is there an unsubscribe option? I'm going to try removing haproxy and just let the vip be shared among the rabbit cluster nodes and see if that tricks it.<br>
<br>
<br>
<br>
On Tuesday, June 10, 2014 9:01 AM, R?zvan Crainea <<a href="mailto:razvan@opensips.org">razvan@opensips.org</a>> wrote:<br>
Hi, Kneeoh!<br>
<br>
I think that the only solution that would work properly was your first<br>
approach. However, since this is not yet implemented, all I can think of<br>
is an external process that periodically test if the node is up. If it<br>
is not, unsubscribe it and re-subscribe the second node.<br>
<br>
PS: I haven't really used haproxy so I have no idea how it works.<br>
<br>
Best regards,<br>
<br>
Razvan Crainea<br>
OpenSIPS Core Developer<br>
<a href="http://www.opensips-solutions.com" target="_blank">http://www.opensips-solutions.com</a><br>
<br>
<br>
<br>
<br>
On 06/06/2014 06:15 PM, Kneeoh wrote:<br>
> Hi Razvan, thank you for the reply. I don't necessarily need expiration of subscriptions to rabbit or the timer route per se. I'm just trying to figure out (with the existing capabilities) how to make opensips fail to another member in the rabbit cluster in the event that the current node dies. My first thought was that you could simply stack entry points like:<br>
><br>
> subscribe_event("E_ACC_CDR", "<a href="mailto:rabbitmq%3Arabbitmq%3Arabbit@192.168.2.30">rabbitmq:rabbitmq:rabbit@192.168.2.30</a>;<a href="mailto:rabbitmq%3Arabbit@192.168.2.31">rabbitmq:rabbit@192.168.2.31</a>;<a href="http://rabbitmq:rabbit@192.168.2.33/cdr1" target="_blank">rabbitmq:rabbit@192.168.2.33/cdr1</a>")<br>
><br>
> However, it sounds like that's not in the present implementation of the rabbit module.<br>
><br>
> So my second thought was to trick opensips and put HAProxy between it and Rabbit, which works, but if I fail an HAProxy via corosync to the other HAproxy something with the subscription breaks. Since it looked like the two options were either put the subscribes in the startup route (only happens once so probably won't failover) OR use the timer route to subscribe (which is what i'm doing) I figured that in the event of an HAProxy failure, I might miss a few messages but on the next timer fire opensips would resubscribe to haproxy which would relay that to the appropriate rabbit server (I haven't failed over any rabbit servers in this scenario so haproxy2 is talking to the same rabbit server as haproxy1. All i'm doing is killing haproxy1 right now and letting the VIP go to haproxy2). However it doesn't look like this is working and I can't tell if its because the subscription isn't happening, OR it is happening but opensips sees it already exists in the<br>
>? subscribers list and does nothing (I think this is the case). If this IS the case perhaps a solution would be to kill the subscriber entry on new subscribe. If I'm way off, let me know, I'd really like to figure this out. Am I going about this all wrong? How would you handle a rabbit node failure?<br>
><br>
> Regards<br>
><br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 6<br>
Date: Wed, 11 Jun 2014 20:29:55 +0300<br>
From: Liviu Chircu <<a href="mailto:liviu@opensips.org">liviu@opensips.org</a>><br>
Subject: Re: [OpenSIPS-Users] binary replication<br>
To: <a href="mailto:users@lists.opensips.org">users@lists.opensips.org</a><br>
Message-ID: <<a href="mailto:53989213.6020409@opensips.org">53989213.6020409@opensips.org</a>><br>
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"<br>
<br>
Hello Tito,<br>
<br>
Both dialog and user location replication were actually designed to work<br>
with VIPs only! From the moment the "receiving" instance takes over, it<br>
should have the same pool of registered users as instance #1, and it<br>
should be able to process all existing dialogues.<br>
<br>
Best regards,<br>
<br>
Liviu Chircu<br>
OpenSIPS Developer<br>
<a href="http://www.opensips-solutions.com" target="_blank">http://www.opensips-solutions.com</a><br>
<br>
On 06/11/2014 03:27 PM, Tito Cumpen wrote:<br>
> Group,<br>
><br>
> Playing with the idea of using binary replication. Just curious if<br>
> anyone can provide a use case. Would this coupled with a virtual ip?<br>
> I am not certain how the instance that accepts replications would<br>
> take over.<br>
><br>
><br>
> Thanks,<br>
> Tito<br>
><br>
><br>
> _______________________________________________<br>
> Users mailing list<br>
> <a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
> <a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.opensips.org/pipermail/users/attachments/20140611/624e6646/attachment.htm" target="_blank">http://lists.opensips.org/pipermail/users/attachments/20140611/624e6646/attachment.htm</a>><br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br>
<br>
End of Users Digest, Vol 71, Issue 41<br>
*************************************<br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr"><div><div><font face="arial">Kind regards,</font></div><div><font face="arial"><br></font></div><div><font face="arial">Kaushik Parmar</font></div>
</div></div>
</div>