[OpenSIPS-Users] Selecting RTPproxy instance on 200 OK reply

Grant Bagdasarian GB at cm.nl
Tue Oct 28 13:49:38 CET 2014


Awesome!

Thank you for answering! :D

From: users-bounces at lists.opensips.org [mailto:users-bounces at lists.opensips.org] On Behalf Of Razvan Crainea
Sent: Tuesday, October 28, 2014 1:24 PM
To: users at lists.opensips.org
Subject: Re: [OpenSIPS-Users] Selecting RTPproxy instance on 200 OK reply

Hi, Grant!

For the reply, you have to select _the same_ set. You don't really have to add the same decision logic for reply, you can store the set used for requests in the AVP and use that AVP on the reply.

Best regards,


Răzvan Crainea

OpenSIPS Solutions

www.opensips-solutions.com<http://www.opensips-solutions.com>
On 10/27/2014 11:07 AM, Grant Bagdasarian wrote:
Hello,

I have the following RTPproxy configuration:
modparam("nathelper", "rtpproxy_sock", "1 == udp:127.0.0.1:12221")
modparam("nathelper", "rtpproxy_sock", "2 == udp:127.0.0.1:12222")

In the main route I decide which instance to select for each INVITE containing SDP:
if($ru=~"1.1.1.10") {
               set_rtp_proxy_set("1");
                xlog("L_INFO", "USE RTP PROXY 01 \r\n");
} else if($ru=~"2.2.2.10") {
               set_rtp_proxy_set("2");
                xlog("L_INFO", "USE RTP PROXY 02 \r\n");
} else {
               t_reply("404", "Not Found");
               exit;
}
rtpproxy_offer();

I’m getting the following error for a 200 OK:
ERROR:nathelper:select_rtpp_node: script error -no valid set selected
ERROR:nathelper:force_rtp_proxy_body: no available proxies

Do I need to do the same decision for 200 OK messages, and call rtpproxy_answer()?

Regards,

Grant





_______________________________________________

Users mailing list

Users at lists.opensips.org<mailto:Users at lists.opensips.org>

http://lists.opensips.org/cgi-bin/mailman/listinfo/users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20141028/944e046d/attachment.htm>


More information about the Users mailing list