Hi, Salman!
Well, this is what I was suggesting - even though you were doing
RTPProxy per branch, you still should have closed the old/unestablished
leg before starting a new one. So I can confirm that your approach is
the proper one.
Best regards,
Razvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com
On 01/06/2014 05:26 PM, Salman Zafar wrote:
Hi Razvan,
I got it working without branching, after banging head a lot I
got to learn unforcing drops the media ports for previous rtpproxy
offer/answer and after that directing the new flow though rtpproxy
flags,IP media works. I am able to traverse from eternal to internal
play media and then on failure do external to external with media
flowing between public interfaces. Just wondering if you know this
method or certify.
On Mon, Jan 6, 2014 at 4:35 PM, Răzvan Crainea <raz...@opensips.org
<mailto:raz...@opensips.org>> wrote:
Hi, Salman!
The sockets used by RTPProxy are created when the session is started
(the first offer) and cannot be updated afterwards. Therefore the
only solution I can see is to configure a per branch scenario, as
you mentioned.
Best regards,
Razvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.__com <http://www.opensips-solutions.com>
On 12/30/2013 01:11 PM, Salman Zafar wrote:
Hi,
I have a scenario of playing media at a private-ip media
server and
send BUSY, next in failure route bridge call to a public IP.
(SIP to SIP).
So the scenario is as follows:
UA(Phone1) -> OpenSIPS/RTpProxy(ei) -> Media-Server (Private IP)
-> BUSY
-> OpenSIPS(failure route) -> RTpProxy(ee) -> lookup -> (UA Phone2)
Now the problem is RtpProxy is being offered (EI flags) in first
case
where routing to Media sever at private IP, after failure it is
again
used with (EE flags), also in corresponding replies.
The second time RTpProxy does not effect SDP c= and ports in a
way to
build media communication. SDP fix directly does not effect rtp
ports.
Is there any way of using RtpProxy differently in fail-over, or
I have
to go for rtpproxy per branch?.
Thanks in advance.
--
Regards
Salman
_________________________________________________
Users mailing list
Users@lists.opensips.org <mailto:Users@lists.opensips.org>
http://lists.opensips.org/cgi-__bin/mailman/listinfo/users
<http://lists.opensips.org/cgi-bin/mailman/listinfo/users>
_________________________________________________
Users mailing list
Users@lists.opensips.org <mailto:Users@lists.opensips.org>
http://lists.opensips.org/cgi-__bin/mailman/listinfo/users
<http://lists.opensips.org/cgi-bin/mailman/listinfo/users>
--
Regards
M. Salman Zafar
VoIP Professional
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
