[OpenSIPS-Users] Access to listen/advertised IP Addresses

David Villasmil david.villasmil.work at gmail.com
Mon Apr 6 15:27:07 EST 2020


this is where the advertised address is set

https://github.com/OpenSIPS/opensips/blob/628a126fe3523e800440855f10f9841d6a2c39eb/cfg.y#L2373

Regards,

David Villasmil
email: david.villasmil.work at gmail.com
phone: +34669448337


On Mon, Apr 6, 2020 at 4:12 PM David Villasmil <
david.villasmil.work at gmail.com> wrote:

> i only see $rd which is the domain to which the sip message was sent, it
> "should" have the advertised ip, or de actual domain, in which case if you
> need the actual ip, it is useless
> Regards,
>
> David Villasmil
> email: david.villasmil.work at gmail.com
> phone: +34669448337
>
>
> On Mon, Apr 6, 2020 at 4:00 PM Johan De Clercq <johan at democon.be> wrote:
>
>> It,s not exposed I think. I can’t find it back either
>>
>> Outlook voor iOS <https://aka.ms/o0ukef> downloaden
>> ------------------------------
>> *Van:* Users <users-bounces at lists.opensips.org> namens David Villasmil <
>> david.villasmil.work at gmail.com>
>> *Verzonden:* Monday, April 6, 2020 4:49:36 PM
>> *Aan:* OpenSIPS users mailling list <users at lists.opensips.org>
>> *Onderwerp:* Re: [OpenSIPS-Users] Access to listen/advertised IP
>> Addresses
>>
>> No, you’re right. It’s not in the core variables and I can’t find it
>> either. Which makes me think it’s either not exposed or somewhere in a
>> module (it’s not in proto_udp)
>>
>> I will research a little to try and find it..
>>
>> On Mon, 6 Apr 2020 at 14:04, Mark Farmer <farmorg at gmail.com> wrote:
>>
>> Thanks David. But I see no reference to the same variable in OpenSIPS.
>>
>> https://www.opensips.org/Documentation/Script-CoreVar-2-4
>>
>> Am I missing something?
>>
>>
>> On Mon, 6 Apr 2020 at 13:45, David Villasmil <
>> david.villasmil.work at gmail.com> wrote:
>>
>> Right here:
>>
>>
>> https://www.kamailio.org/wiki/cookbooks/5.2.x/pseudovariables#rai_-_received_advertised_ip_address
>>
>> Regards,
>>
>> David Villasmil
>> email: david.villasmil.work at gmail.com
>> phone: +34669448337
>>
>>
>> On Mon, Apr 6, 2020 at 12:08 PM Mark Farmer <farmorg at gmail.com> wrote:
>>
>> Many thanks for the reply.
>>
>> $Ri is certainly useful when the request comes from a non-natted
>> interface. Thanks for pointing that out :)
>>
>> Is there a way to reference the advertised IP address defined in the
>> listen statement?
>>
>> listen=udp:xxx.xxx.xxx.xxx:5060 as xxx.xxx.xxx.xxx:5060
>>
>> Thanks
>> Mark.
>>
>>
>> On Thu, 2 Apr 2020 at 17:32, Sharad Kumar via Users <
>> users at lists.opensips.org> wrote:
>>
>> Hi Mark,
>>
>>  If your initial goal is to get the interface IP where request is
>> received then you can try these variables.
>>
>> *$Ri* - reference to IP address of the interface where the request has
>> been received
>>
>> *$Rp* - reference to the port where the message was received
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
>>
>> --
>> Mark Farmer
>> farmorg at gmail.com
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
>>
>> --
>> Mark Farmer
>> farmorg at gmail.com
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>> --
>> Regards,
>>
>> David Villasmil
>> email: david.villasmil.work at gmail.com
>> phone: +34669448337
>> _______________________________________________
>> Users mailing list
>> 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/20200406/2a6be6f8/attachment.html>


More information about the Users mailing list