<div dir="ltr">Hi Andrew,<div><br></div><div>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:</div><div>
<p class="p1"><span class="s1">[% FOREACH extip IN sip_ext_ips -%] || $rd == "[% extip %]" [% END %]</span></p><p class="p1">does not add the IPs for interfaces which aren't "sip_ext", and so the "OPTIONS" packets were just ignored.</p><p class="p1">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?</p><p class="p1"><br></p><p class="p1">Thanks,</p><p class="p1">Andrew</p></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On 17 August 2015 at 18:00, Andrew Pogrebennyk <span dir="ltr"><<a href="mailto:apogrebennyk@sipwise.com" target="_blank">apogrebennyk@sipwise.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><span class="">
<div>On 08/17/2015 08:55 AM, Andrew Yager
wrote:<br>
</div>
<blockquote type="cite">
<div>
<div> - sip_ext</div>
<div> - rtp_ext</div>
<div> - ssh_ext</div>
<div> - web_int</div>
</div>
<div>
<div> eth1:</div>
<div> ip: 10.237.217.254</div>
<div> netmask: 255.255.255.252</div>
<div> type:</div>
<div> - sip_ext</div>
<div> - rtp_ext</div>
</div>
<div><br>
</div>
<div>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.</div>
</blockquote>
<br></span>
The network.yml is not correct, you should not put rtp_ext on more
than one interface.<br>
Also you may remove the sip_ext type from eth1 because they have to
be specified in the extra sockets.<br>
<a name="14f3aac7ce8c849e_bugnotes"> (see our Handbook chapter "Extra
SIP listening ports": </a><a href="https://www.sipwise.org/doc/mr3.8.2/spce/ar01s05.html#_extra_sip_listening_ports" target="_blank">https://www.sipwise.org/doc/mr3.8.2/spce/ar01s05.html#_extra_sip_listening_ports</a>)<br>
it does no harm and makes almost on differences whether you put
sip_ext there or not..<br>
But the important thing is that rtp_ext is supposed to be unique.
For your peer you may <a name="14f3aac7ce8c849e_bugnotes">invent a new
type beginning with "rtp_", just put whatever you like, e.g.
"rtp_mypeer"</a>:<br>
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.<br>
Execute ngcpcfg apply and check ps auxww | grep rtpengine<br>
you'll see that it knows now two RTP interfaces with different
labels: ext/XXX.XXX.XXX.XXX and mypeer/<a href="http://10.237.217.254" target="_blank">10.237.217.254</a>.<br>
After that finish the peer configuration via web UI:<br>
- select the previously configured SIP interface from the list in
preference outbound_socket;<br>
- set preference rtp_interface to "mypeer".<br>
<br>
Regards,<br>
Andrew<br>
</div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><b>Andrew Yager, Managing Director</b> <i>(BCompSc, JNCIS-SP, MACS (Snr) CP)</i><br></div><div dir="ltr">Real World Technology Solutions - IT People you can trust</div><div dir="ltr">Voice | Data | IT Procurement | Managed IT</div><div dir="ltr"><a href="http://rwts.com.au" target="_blank">rwts.com.au</a> | 1300 798 718</div><div dir="ltr"><br></div><div dir="ltr"><img src="http://www.rwts.com.au/email-signature-logo.jpg"><br></div><div dir="ltr"><i style="font-family:arial;font-size:small">Real World is a Dell Premier Partner</i><br></div><div dir="ltr"><br></div><div dir="ltr">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.</div></div></div></div></div></div></div></div></div></div>
</div>