<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 08/17/2015 08:55 AM, Andrew Yager
wrote:<br>
</div>
<blockquote
cite="mid:CAEX38CM84L6dJxxQxiXq3ZFFVp_28w3hvWBQE0jLHeWER+0baA@mail.gmail.com"
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>
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="bugnotes" id="bugnotes"> (see our Handbook chapter "Extra
SIP listening ports": </a><a class="moz-txt-link-freetext" href="https://www.sipwise.org/doc/mr3.8.2/spce/ar01s05.html#_extra_sip_listening_ports">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="bugnotes" id="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/10.237.217.254.<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>
</body>
</html>