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
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
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
