<div dir="ltr"><span style="font-family:arial,sans-serif;font-size:13px">Thank you Razvan,</span><div style="font-family:arial,sans-serif;font-size:13px"><br></div><div style="font-family:arial,sans-serif;font-size:13px"><br>
</div><div style="font-family:arial,sans-serif;font-size:13px">As you said rtpproxy2 will send rtp to rtpproxy1. How can i implement this?</div><div style="font-family:arial,sans-serif;font-size:13px"><br></div><div style="font-family:arial,sans-serif;font-size:13px">
What are configuration in opensips or rtpproxy to make this possible?</div><div style="font-family:arial,sans-serif;font-size:13px"><br></div><div style="font-family:arial,sans-serif;font-size:13px"><br></div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Tue, May 20, 2014 at 3:30 PM, <span dir="ltr"><<a href="mailto:devel-request@lists.opensips.org" target="_blank">devel-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 Devel mailing list submissions to<br>
<a href="mailto:devel@lists.opensips.org">devel@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/devel" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/devel</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:devel-request@lists.opensips.org">devel-request@lists.opensips.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:devel-owner@lists.opensips.org">devel-owner@lists.opensips.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of Devel digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. [opensips] UAC_REGISTRANT module: fixed expiration time<br>
calculation (#236) (Nick Altmann)<br>
2. Re: [opensips] uac_registrant and external "expires"<br>
parameter (in 200OK) (#217) (Nick Altmann)<br>
3. Re: [opensips] UAC_REGISTRANT module: fixed expiration time<br>
calculation (#234) (Nick Altmann)<br>
4. [opensips] RTPPROXY module: compatibility with topology<br>
hiding (#237) (Nick Altmann)<br>
5. Re: [opensips] RTPPROXY module: compatibility with topology<br>
hiding (#237) (Walter Doekes)<br>
6. Re: [opensips] RTPPROXY module: compatibility with topology<br>
hiding (#237) (Walter Doekes)<br>
7. Send rtp packet between two rtpproxy server (kaushik parmar)<br>
8. Re: Send rtp packet between two rtpproxy server (R?zvan Crainea)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Mon, 19 May 2014 23:01:24 -0700<br>
From: Nick Altmann <<a href="mailto:notifications@github.com">notifications@github.com</a>><br>
Subject: [OpenSIPS-Devel] [opensips] UAC_REGISTRANT module: fixed<br>
expiration time calculation (#236)<br>
To: <a href="mailto:devel@lists.opensips.org">devel@lists.opensips.org</a><br>
Message-ID: <OpenSIPS/opensips/pull/<a href="mailto:236@github.com">236@github.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
<br>
You can merge this Pull Request by running:<br>
<br>
git pull <a href="https://github.com/nikbyte/nikbyte-opensips" target="_blank">https://github.com/nikbyte/nikbyte-opensips</a> uac_registrant<br>
<br>
Or you can view, comment on it, or merge it online at:<br>
<br>
<a href="https://github.com/OpenSIPS/opensips/pull/236" target="_blank">https://github.com/OpenSIPS/opensips/pull/236</a><br>
<br>
-- Commit Summary --<br>
<br>
* UAC_REGISTRANT module: fixed expiration time calculation<br>
<br>
-- File Changes --<br>
<br>
M modules/uac_registrant/registrant.c (13)<br>
<br>
-- Patch Links --<br>
<br>
<a href="https://github.com/OpenSIPS/opensips/pull/236.patch" target="_blank">https://github.com/OpenSIPS/opensips/pull/236.patch</a><br>
<a href="https://github.com/OpenSIPS/opensips/pull/236.diff" target="_blank">https://github.com/OpenSIPS/opensips/pull/236.diff</a><br>
<br>
---<br>
Reply to this email directly or view it on GitHub:<br>
<a href="https://github.com/OpenSIPS/opensips/pull/236" target="_blank">https://github.com/OpenSIPS/opensips/pull/236</a><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.opensips.org/pipermail/devel/attachments/20140519/0f8ba69b/attachment.html" target="_blank">http://lists.opensips.org/pipermail/devel/attachments/20140519/0f8ba69b/attachment.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Mon, 19 May 2014 23:02:59 -0700<br>
From: Nick Altmann <<a href="mailto:notifications@github.com">notifications@github.com</a>><br>
Subject: Re: [OpenSIPS-Devel] [opensips] uac_registrant and external<br>
"expires" parameter (in 200OK) (#217)<br>
To: <a href="mailto:devel@lists.opensips.org">devel@lists.opensips.org</a><br>
Message-ID: <OpenSIPS/opensips/issues/217/<a href="mailto:43589176@github.com">43589176@github.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Recreated pull request. The proper one: <a href="https://github.com/OpenSIPS/opensips/pull/236" target="_blank">https://github.com/OpenSIPS/opensips/pull/236</a><br>
<br>
---<br>
Reply to this email directly or view it on GitHub:<br>
<a href="https://github.com/OpenSIPS/opensips/issues/217#issuecomment-43589176" target="_blank">https://github.com/OpenSIPS/opensips/issues/217#issuecomment-43589176</a><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.opensips.org/pipermail/devel/attachments/20140519/49c3613f/attachment-0001.htm" target="_blank">http://lists.opensips.org/pipermail/devel/attachments/20140519/49c3613f/attachment-0001.htm</a>><br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Mon, 19 May 2014 23:03:05 -0700<br>
From: Nick Altmann <<a href="mailto:notifications@github.com">notifications@github.com</a>><br>
Subject: Re: [OpenSIPS-Devel] [opensips] UAC_REGISTRANT module: fixed<br>
expiration time calculation (#234)<br>
To: <a href="mailto:devel@lists.opensips.org">devel@lists.opensips.org</a><br>
Message-ID:<br>
<OpenSIPS/opensips/pull/234/issue_event/<a href="mailto:122760818@github.com">122760818@github.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Closed #234.<br>
<br>
---<br>
Reply to this email directly or view it on GitHub:<br>
<a href="https://github.com/OpenSIPS/opensips/pull/234#event-122760818" target="_blank">https://github.com/OpenSIPS/opensips/pull/234#event-122760818</a><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.opensips.org/pipermail/devel/attachments/20140519/fdddcbdc/attachment-0001.htm" target="_blank">http://lists.opensips.org/pipermail/devel/attachments/20140519/fdddcbdc/attachment-0001.htm</a>><br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Mon, 19 May 2014 23:06:53 -0700<br>
From: Nick Altmann <<a href="mailto:notifications@github.com">notifications@github.com</a>><br>
Subject: [OpenSIPS-Devel] [opensips] RTPPROXY module: compatibility<br>
with topology hiding (#237)<br>
To: <a href="mailto:devel@lists.opensips.org">devel@lists.opensips.org</a><br>
Message-ID: <OpenSIPS/opensips/pull/<a href="mailto:237@github.com">237@github.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
RTPPROXY module: workaround to run rtpproxy when we use dialog topology hiding and thus we have not 2nd via in reply<br>
<br>
It fixes autobridging for rtpproxy when using topology hiding.<br>
The problem is reply doesn&#39;t have second via.<br>
<br>
We used this patch on production system about 7 months without any problems.<br>
You can merge this Pull Request by running:<br>
<br>
git pull <a href="https://github.com/nikbyte/nikbyte-opensips" target="_blank">https://github.com/nikbyte/nikbyte-opensips</a> rtpproxy<br>
<br>
Or you can view, comment on it, or merge it online at:<br>
<br>
<a href="https://github.com/OpenSIPS/opensips/pull/237" target="_blank">https://github.com/OpenSIPS/opensips/pull/237</a><br>
<br>
-- Commit Summary --<br>
<br>
* RTPPROXY module: workaround to run rtpproxy when we use dialog topology hiding and thus we have not 2nd via in reply<br>
<br>
-- File Changes --<br>
<br>
M modules/rtpproxy/rtpproxy.c (22)<br>
<br>
-- Patch Links --<br>
<br>
<a href="https://github.com/OpenSIPS/opensips/pull/237.patch" target="_blank">https://github.com/OpenSIPS/opensips/pull/237.patch</a><br>
<a href="https://github.com/OpenSIPS/opensips/pull/237.diff" target="_blank">https://github.com/OpenSIPS/opensips/pull/237.diff</a><br>
<br>
---<br>
Reply to this email directly or view it on GitHub:<br>
<a href="https://github.com/OpenSIPS/opensips/pull/237" target="_blank">https://github.com/OpenSIPS/opensips/pull/237</a><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.opensips.org/pipermail/devel/attachments/20140519/b197951e/attachment-0001.htm" target="_blank">http://lists.opensips.org/pipermail/devel/attachments/20140519/b197951e/attachment-0001.htm</a>><br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Tue, 20 May 2014 00:00:54 -0700<br>
From: Walter Doekes <<a href="mailto:notifications@github.com">notifications@github.com</a>><br>
Subject: Re: [OpenSIPS-Devel] [opensips] RTPPROXY module:<br>
compatibility with topology hiding (#237)<br>
To: <a href="mailto:devel@lists.opensips.org">devel@lists.opensips.org</a><br>
Message-ID: <OpenSIPS/opensips/pull/237/<a href="mailto:r12830089@github.com">r12830089@github.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
> @@ -3229,6 +3229,8 @@ force_rtp_proxy(struct sip_msg* msg, char* str1, char* str2, char *setid, char *<br>
> struct force_rtpp_args args;<br>
> struct force_rtpp_args *ap;<br>
> union sockaddr_union to;<br>
> + struct socket_info *si;<br>
> + struct dlg_cell * dlg;<br>
<br>
Please stay consistent with local code style: join the `*` to the `dlg`.<br>
<br>
---<br>
Reply to this email directly or view it on GitHub:<br>
<a href="https://github.com/OpenSIPS/opensips/pull/237/files#r12830089" target="_blank">https://github.com/OpenSIPS/opensips/pull/237/files#r12830089</a><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.opensips.org/pipermail/devel/attachments/20140520/a755c425/attachment-0001.htm" target="_blank">http://lists.opensips.org/pipermail/devel/attachments/20140520/a755c425/attachment-0001.htm</a>><br>
<br>
------------------------------<br>
<br>
Message: 6<br>
Date: Tue, 20 May 2014 00:01:40 -0700<br>
From: Walter Doekes <<a href="mailto:notifications@github.com">notifications@github.com</a>><br>
Subject: Re: [OpenSIPS-Devel] [opensips] RTPPROXY module:<br>
compatibility with topology hiding (#237)<br>
To: <a href="mailto:devel@lists.opensips.org">devel@lists.opensips.org</a><br>
Message-ID: <OpenSIPS/opensips/pull/237/<a href="mailto:r12830105@github.com">r12830105@github.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
> } else {<br>
> - LM_ERR("can't extract 2nd via found reply\n");<br>
> + if (parse_headers(msg, HDR_VIA2_F, 0) != -1 &&<br>
<br>
You could make the `} else {` above an `} else if {`, that saves you some indentation.<br>
<br>
Feel free to squash and push -f.<br>
<br>
---<br>
Reply to this email directly or view it on GitHub:<br>
<a href="https://github.com/OpenSIPS/opensips/pull/237/files#r12830105" target="_blank">https://github.com/OpenSIPS/opensips/pull/237/files#r12830105</a><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.opensips.org/pipermail/devel/attachments/20140520/37e66a92/attachment-0001.htm" target="_blank">http://lists.opensips.org/pipermail/devel/attachments/20140520/37e66a92/attachment-0001.htm</a>><br>
<br>
------------------------------<br>
<br>
Message: 7<br>
Date: Tue, 20 May 2014 12:47:27 +0530<br>
From: kaushik parmar <<a href="mailto:androidjpc0@gmail.com">androidjpc0@gmail.com</a>><br>
Subject: [OpenSIPS-Devel] Send rtp packet between two rtpproxy server<br>
To: <a href="mailto:devel@lists.opensips.org">devel@lists.opensips.org</a><br>
Message-ID:<br>
<CAGzPE1-QJdJ4-LKhwn4rVWeEFGUJQ0RZG92kquWyw+c=<a href="mailto:vhpeqQ@mail.gmail.com">vhpeqQ@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hello,<br>
<br>
Is it possible to send media rtp packets from one rtpproxy server to<br>
another rtpproxy server?<br>
<br>
In my scenario , i am registering voip account via opensips proxy server.<br>
We have rtpproxy and opensips server hosted on same place. opensips changes<br>
c= and m= lines of SDP accordingly but when packet goes to voip switch ,<br>
its rtpproxy server also changes SDP. So Peer1 is sending packets to hout<br>
hosted rtpproxy server and peer2 sending rtp packets to voip switch's<br>
rtpproxy server.<br>
<br>
<br>
SIP packets : Peer <--> opensips <--> asterisk<br>
<br>
RTP packets peer1 <--> rtpproxy1 =X= rtpproxy2 <-->peer2<br>
<br>
here no connection between rtpproxy1 and rtpproxy 2 so no media transfer<br>
between peer1 and peer2. Please help to solve this problem.<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/devel/attachments/20140520/4b43dea8/attachment-0001.htm" target="_blank">http://lists.opensips.org/pipermail/devel/attachments/20140520/4b43dea8/attachment-0001.htm</a>><br>
<br>
------------------------------<br>
<br>
Message: 8<br>
Date: Tue, 20 May 2014 10:34:42 +0300<br>
From: R?zvan Crainea <<a href="mailto:razvan@opensips.org">razvan@opensips.org</a>><br>
Subject: Re: [OpenSIPS-Devel] Send rtp packet between two rtpproxy<br>
server<br>
To: <a href="mailto:devel@lists.opensips.org">devel@lists.opensips.org</a><br>
Message-ID: <<a href="mailto:537B0592.8060901@opensips.org">537B0592.8060901@opensips.org</a>><br>
Content-Type: text/plain; charset=UTF-8; format=flowed<br>
<br>
Hi, Kaushik!<br>
<br>
I don't see any problem with your scenario, it should work without any<br>
issues - peer2 should send RTP to rtpproxy2 which relays them to<br>
rtpproy1 and then peer1, and the other way around.<br>
Are you sure both proxies advertise the correct IP in the SDP, for both<br>
INVITE and 200 OK?<br>
<br>
Best regards,<br>
<br>
PS: this is not a devel question. Please register on<br>
<a href="mailto:users@lists.opensips.org">users@lists.opensips.org</a> and move the thread there.<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 05/20/2014 10:17 AM, kaushik parmar wrote:<br>
> Hello,<br>
><br>
> Is it possible to send media rtp packets from one rtpproxy server to<br>
> another rtpproxy server?<br>
><br>
> In my scenario , i am registering voip account via opensips proxy<br>
> server. We have rtpproxy and opensips server hosted on same place.<br>
> opensips changes c= and m= lines of SDP accordingly but when packet goes<br>
> to voip switch , its rtpproxy server also changes SDP. So Peer1 is<br>
> sending packets to hout hosted rtpproxy server and peer2 sending rtp<br>
> packets to voip switch's rtpproxy server.<br>
><br>
><br>
> SIP packets : Peer <--> opensips <--> asterisk<br>
><br>
> RTP packets peer1 <--> rtpproxy1 =X= rtpproxy2 <-->peer2<br>
> here no connection between rtpproxy1 and rtpproxy 2 so no media transfer<br>
> between peer1 and peer2. Please help to solve this problem.<br>
><br>
> --<br>
> Kind regards,<br>
><br>
> Kaushik Parmar<br>
><br>
><br>
> _______________________________________________<br>
> Devel mailing list<br>
> <a href="mailto:Devel@lists.opensips.org">Devel@lists.opensips.org</a><br>
> <a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/devel" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/devel</a><br>
><br>
<br>
<br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
Devel mailing list<br>
<a href="mailto:Devel@lists.opensips.org">Devel@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/devel" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/devel</a><br>
<br>
<br>
End of Devel Digest, Vol 71, Issue 42<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>