Re: Kamailio SBC using RTPproxy

Maxim Sobolev via sr-users <[email protected]>
Newsgroups gmane.comp.voip.ser
Message-ID <CAH7qZfvEvW_47KOHnrr=7q_Bqj=3p2N3Eu8rMdR5HNpbutEy7g@mail.gmail.com>
Hi Ibe,

Thank you for your interest. Please see my comments below:

On Thu, Sep 25, 2025 at 6:18 AM Ibe Van de Veire via sr-users
<[email protected]> wrote:
> This way, both external devices try to send the RTP data to the internal (inaccessible) address of the SBC.
> How can I configure the SBC to stop translating the IN IP4 field when both devices are external?
>
> I have the following configuration that talks to the RTPproxy service:
>
> ==========================
>
>     if(nat_uac_test("8")) {
>         if($Ri == "MY_PUBLIC_IP") {
>             rtpproxy_manage("coiew");
>         } else {
>             rtpproxy_manage("faei");
>         }
>     } else {
>         rtpproxy_manage("cor");
>     }
>
> ==========================

I'd say you also need section with "EE" (i.e. external-external)
section too, please insert your own logic into the
[DESTINATION_INTERNAL] placeholder.

     if(nat_uac_test("8")) {
         if($Ri == "MY_PUBLIC_IP") {
             rtpproxy_manage("coiew");
         } else {
+            if ([DESTINATION_INTERNAL]) {
                 rtpproxy_manage("faei");
+            } else {
+               rtpproxy_manage("faee");
+             }
        }
     } else {
         rtpproxy_manage("cor");
     }

Hope it helps. You may also consider using R ("remote") or L ("local")
options to pin the media address explicitly, which are orthogonal
methods of doing media pinning.

Regards,
-- 
Maksym Sobolyev
Sippy Software, Inc.
Internet Telephony (VoIP) Experts
Tel (Canada): +1-778-783-0474
Tel (Toll-Free): +1-855-747-7779
Fax: +1-866-857-6942
Web: http://www.sippysoft.com
MSN: [email protected]
Skype: SippySoft
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions -- [email protected]
To unsubscribe send an email to [email protected]
Important: keep the mailing list in the recipients, do not reply only to the sender!
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.