<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hi,<br>
sems SIP signaling is going out via localhost:5080, so no issue
here.<br>
I still don't get what is the problem, as you said:"the registration
comes out the correct interface,".<br>
<br>
You can check the kamailio.lb log, to see which From Socket (fs) has
been used to send out the registration.<br>
<br>
<br>
<br>
Daniel<br>
<br>
<br>
<br>
<br>
<div class="moz-cite-prefix">On 05/28/2018 11:03 AM, Chris Hoffmann
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAN8EJkyPWS3PHa5Np0rSey8zH3yGC8h+FHo=zx_Vqj3QocvCtg@mail.gmail.com">
<div dir="ltr">Hi,
<div><br>
</div>
<div>I have still not managed to solve this issue, but I think i
might have an idea. My understanding is that SEMS constucts
the registration. Looking at my ./ngcp-sems/sems.conf</div>
<div><br>
</div>
<div>I can see that my config only has the 1 x IP:</div>
<div><br>
</div>
<div>
<div><br>
</div>
<div>fork=yes</div>
<div>stderr=no</div>
<div>loglevel=2</div>
<div><br>
</div>
<div>sip_ip=127.0.0.1</div>
<div>media_ip=103.x.37.211</div>
<div>sip_port=5080</div>
<div>rtp_low_port=15000</div>
<div>rtp_high_port=19999</div>
<div>plugin_path=/usr/lib/ngcp-sems/plug-in/</div>
<div>plugin_config_path=/etc/ngcp-sems/etc/</div>
<div># the order is important - load xmlrpc2di as the last one
(mantis:8181)</div>
<div>load_plugins=wav;gsm;di_dial;stats;uac_auth;session_timer;click2dial;sbc;sw_vsc;registrar_client;reg_agent;db_reg_agent;dsm;xmlrpc2di;cc_call_timer</div>
<div><br>
</div>
<div>application=$(apphdr)</div>
<div><br>
</div>
<div>media_processor_threads=10</div>
<div>session_processor_threads=10</div>
<div><br>
</div>
<div>use_default_signature=no</div>
<div>signature="Sipwise NGCP Application Server 6.X"</div>
<div>single_codec_in_ok=no</div>
<div>codec_order=PCMA;PCMU</div>
<div><br>
</div>
<div>unhandled_reply_loglevel=info</div>
<div>accept_fr_without_totag=yes</div>
<div>wait_for_bye_transaction=yes</div>
<div>sip_timer_B=6000</div>
<div>sip_timer_F=6000</div>
<div><br>
</div>
<div><br>
</div>
<div>#disable rtp timeout</div>
<div>dead_rtp_time=0</div>
<div><br>
</div>
<div># disable transaction-based blacklist</div>
<div>default_bl_ttl=0</div>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div>Could this be the cause of my SIP registration comming from
the wrong ip address? </div>
<div><br>
</div>
<div>If so how would I go about configuring SEMS to be aware of
my multiple interfaces? I looks like SEMS.conf isn't using the
network.yaml when its built. </div>
<div><br>
</div>
<div>Am i on the right track?</div>
<div><br>
</div>
<div>Cheers,</div>
<div><br>
</div>
<div>Chris</div>
<div><br>
</div>
<div><br>
</div>
</div>
<!--'"--><br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Spce-user mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Spce-user@lists.sipwise.com">Spce-user@lists.sipwise.com</a>
<a class="moz-txt-link-freetext" href="https://lists.sipwise.com/listinfo/spce-user">https://lists.sipwise.com/listinfo/spce-user</a>
</pre>
</blockquote>
<br>
</body>
</html>