[Spce-user] Issue with RTP proxy on dual interface host

[Andrew Yager]

Hi Andrew,

Thanks; can easily make that change. We had specified sip_ext as the
provider insists on sending SIP OPTIONS packets, which in the default
kamailio.cfg.tt2 for the proxy:

[% FOREACH extip IN sip_ext_ips -%] || $rd == "[% extip %]" [% END %]

does not add the IPs for interfaces which aren't "sip_ext", and so the
"OPTIONS" packets were just ignored.

Is the best thing to manually patch the .tt2 file to deal with this and
preserve this through updates, or is there another way to make this be
honoured?


Thanks,

Andrew


On 17 August 2015 at 18:00, Andrew Pogrebennyk <apogrebennyk at sipwise.com>
wrote:

> On 08/17/2015 08:55 AM, Andrew Yager wrote:
>
>         - sip_ext
>         - rtp_ext
>         - ssh_ext
>         - web_int
>     eth1:
>       ip: 10.237.217.254
>       netmask: 255.255.255.252
>       type:
>         - sip_ext
>         - rtp_ext
>
> The peer appears to be set up correctly and behaving normally; but I might
> be missing something. Can you suggest where to debug/what we might have
> possibly done wrong from the above description. Happy to provide more info
> as needed.
>
>
> The network.yml is not correct, you should not put rtp_ext on more than
> one interface.
> Also you may remove the sip_ext type from eth1 because they have to be
> specified in the extra sockets.
> (see our Handbook chapter "Extra SIP listening ports":
> https://www.sipwise.org/doc/mr3.8.2/spce/ar01s05.html#_extra_sip_listening_ports
> )
> it does no harm and makes almost on differences whether you put sip_ext
> there or not..
> But the important thing is that rtp_ext is supposed to be unique. For your
> peer you may invent a new type beginning with "rtp_", just put whatever
> you like, e.g. "rtp_mypeer":
>  This is recognized by the ngcpcfg framework and the new rtp interface
> automatically appears in the Browser (preference rtp_interface) - just like
> with extra_sockets option.
> Execute ngcpcfg apply and check ps auxww | grep rtpengine
> you'll see that it knows now two RTP interfaces with different labels:
> ext/XXX.XXX.XXX.XXX and mypeer/10.237.217.254.
> After that finish the peer configuration via web UI:
> - select the previously configured SIP interface from the list in
> preference outbound_socket;
> - set preference rtp_interface to "mypeer".
>
> Regards,
> Andrew
>



-- 
*Andrew Yager, Managing Director* *(BCompSc, JNCIS-SP, MACS (Snr) CP)*
Real World Technology Solutions - IT People you can trust
Voice | Data | IT Procurement | Managed IT
rwts.com.au | 1300 798 718


*Real World is a Dell Premier Partner*

This document should be read only by those persons to whom it is addressed
and its content is not intended for use by any other persons. If you have
received this message in error, please notify us immediately. Please also
destroy and delete the message from your computer. Any unauthorised form of
reproduction of this message is strictly prohibited. We are not liable for
the proper and complete transmission of the information contained in this
communication, nor for any delay in its receipt. Please consider the
environment before printing this e-mail.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20150817/b034eb90/attachment-0001.html>