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

Andrew Yager andrew at rwts.com.au
Mon Aug 17 08:37:47 EDT 2015

Thanks Andrew.

Have just done as you suggested (which was similar to a version of config
we had already tried) and am still seeing the same behaviour.

The outbound_socket and rtp_socket are both using the "mypeer" RTP socket,
but the SDP still includes the endpoint IP.

What should we look at next?


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

> On 08/17/2015 10:03 AM, Andrew Yager wrote:
> > 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, all is clear now. No problem, you may leave the sip_ext on the
> second interface for now, it doesn't harm. The only thing I have
> recognized when having more than one sip_ext interface in the
> network.yml is that the LB is masking the internal Contact to
> sip:ngcp_lb@[% sip_ext_ips.0 %] and in that case this was awkward
> because the customer had extra interface listed before the public
> sip_ext, but I see no issue with marking all of them as sip_ext in
> general. The patch is fine too - whatever you prefer.
> 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/32415705/attachment-0001.html>

More information about the Spce-user mailing list