<div dir="ltr">Hi Cesar,<div><br></div><div>we will try to replicate the case on our systems and let you know.</div><div><br></div><div>Thank you</div><div>Marco</div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Tue, Dec 9, 2025 at 7:43\u202fPM Cesar Mora <<a href="mailto:cesarluis89@gmail.com">cesarluis89@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>This is what I\u2019ve discovered so far:<div><br></div><div>On the GUI we set the required register parameters, and enabled registration by "<span>peer_auth_register = True\u201d.</span></div><div><span>No visible registration under sngrep.</span></div><div><span><br></span></div><div><span>Restarted sems with no notable changes.</span></div><div><span><br></span></div><div><span>Inspected </span><span style="white-space:pre-wrap">/var/log/ngcp/sems.log and found the following:</span></div><div><span><br></span></div><div><span>- Normal startup, SBC/DSM loaded, but WARNING: "no complete account provided: 'reg_agent' module remains inactive\u201d. (I suspect reg_agent is legacy).</span></div><div><span>- </span><span style="white-space:pre-wrap">db_reg_agent loads OK (query in conf fetches prefs from provisioning.voip_peer_preferences)</span></div><div><span>- Still no register.</span></div><div><span><br></span></div><div><span>I went and took a look at </span>/etc/ngcp-sems/etc/reg_agent.conf which appears to be for the legacy register method, and the reason for the "<span>no complete account provided: 'reg_agent' module remains inactive\u201d error.</span></div><div><br></div><div>Took a look at <span style="white-space:pre-wrap">/etc/ngcp-sems/etc/</span><span style="white-space:pre-wrap">db_reg_agent.conf and extracted the password for "</span><span style="white-space:pre-wrap">mysql_user=sems_prepaid</span><span>\u201d</span></div><div><span style="white-space:pre-wrap"><br></span></div><div>Logged in to mysql and r<span style="white-space:pre-wrap">an joined_query_peerings from db_reg_agent.conf in MySQL (u sems_prepaid / DB kamailio).</span></div><div><span style="white-space:pre-wrap"><br></span></div><div><span style="white-space:pre-wrap">- When </span>"<span>peer_auth_register = false\u201d there is no db info available. When </span>"<span>peer_auth_register = True\u201d the correct parameters are populated in the DB, \u201cregistration_status\u201d displays \u201c2\u201d, user/pass/realm/auth_user/contact all display the correct and expected information, but still, no outgoing registrations are seen on sngrep or on sems.log</span></div><div><span><br></span></div><div><span>I went and did "ngcpcfg apply\u201d multiple times which should regenerate templates and restart SEMS. But still same results.</span></div><div><span><br></span></div><div><span>As a last resort I tried a l</span><span style="white-space:pre-wrap">egacy workaround: Created /etc/ngcp-config/templates/etc/ngcp-sems/etc/reg_agent.conf.customtt.tt2 with populated [account] (domain/user/pwd/proxy/contact/registrar from GUI, using TT2 vars sip_lb_ips/sip_ext_ips). Ran </span><span style="white-space:pre-wrap">ngcpcfg apply</span></div><div><br></div><div><span>Under </span><span style="white-space:pre-wrap">/var/log/ngcp/sems.log </span><span>got a loop with (probably expected, deprecated register method):</span></div><div><span><br></span></div><div>Dec 9 14:14:07.405195 spce ngcp-sems[17255]: [#7fe37d83d6c0] [doRegistration, AmSipRegistration.cpp:135] ERROR: failed to send registration.
Dec 9 14:14:17.404817 spce ngcp-sems[17255]: [#7fe37d83d6c0] [sendRequest, AmBasicSipDialog.cpp:763] ERROR: Could not send request: method=REGISTER; call-id=73957BFC-693866F900062A91-7D83D6C0; cseq=50</div><div><span><br></span></div><div><span>Any ideas?</span></div><div><span><br></span></div><div><span>Cesar</span></div><div><span><br></span></div><div><span><br></span></div><div><span><br></span></div><div><div><blockquote type="cite"><div>On Dec 9, 2025, at 9:10\u202fAM, Cesar Mora <<a href="mailto:cesarluis89@gmail.com" target="_blank">cesarluis89@gmail.com</a>> wrote:</div><br><div><div dir="auto"><div dir="ltr">\ufeffHi!<div><br></div><div>Thanks for the reply.</div><div><br></div><div>The last number is just the service package which is the latest for this version, it shows as 13.2.1.3 under ngcp-status. Just for clarifying that I am running the latest fix for that particular version.</div><div><br></div><div><span>I am configuring from the Web GUI interface. I have tried both the new and old GUI with the same results. Parameters as set under Remote Authentication as expected.</span></div><div><br></div><div>Using this same method and parameters on a test instance with mr12.5.1 works and registers as intended. No, I have not tried restarting sems, will try that now.</div><div><div dir="ltr"><br></div><div dir="ltr">Thanks,<br><div>César Mora</div></div><div dir="ltr"><br><blockquote type="cite">On Dec 9, 2025, at 6:26\u202fAM, Marco Capetta <<a href="mailto:mcapetta@sipwise.com" target="_blank">mcapetta@sipwise.com</a>> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr">\ufeff<div dir="ltr">Hi Cesar,<div><br></div><div>There is no version mr13.2.1.3, but only mr13.2.1. Maybe you are referring to a particular version of a package?</div><div><br></div><div>Can you also clarify how you configure the outbound peer registration? Do you do all the configuration from the web interface or you are still using the legacy method with the sems configuration file?</div><div><br></div><div>Additionally, can you check what happens if, after having configured the outbound registrations, you restart sems service. Does it sends out the registration messages?</div><div><br></div><div>Thank you</div><div>Marco</div><div><br></div><div><br></div><div><br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Dec 8, 2025 at 5:06\u202fPM Cesar Mora <<a href="mailto:cesarluis89@gmail.com" target="_blank">cesarluis89@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi all,<br>
<br>
I was wondering if anyone has encountered any issues with registering peering servers (trunks) on SipWise CE mr13.2.1.3<br>
<br>
We've been trying for a while to get our mr13.2.1.3 server to register with peering groups with no luck. IP Auth peerings work without any issues, but whenever you set register parameters, there is no visible outbound register requests in sngrep. We have tried with different peers, ip addresses, there is no firewall in between, but we never see any register attempts. We set up a test server with the same parameters on version mr12.5.1 and it registers as expected, but no luck with our main one at mr13.2.1.3.<br>
<br>
Thanks,<br>
<br>
Cesar<br>
-- <br>
Spce-user mailing list<br>
<a href="mailto:Spce-user@lists.sipwise.com" target="_blank">Spce-user@lists.sipwise.com</a><br>
<a href="http://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com" rel="noreferrer" target="_blank">http://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com</a><br>
</blockquote></div>
</div></blockquote></div></div></div></div></blockquote></div><br></div></div>-- <br>
Spce-user mailing list<br>
<a href="mailto:Spce-user@lists.sipwise.com" target="_blank">Spce-user@lists.sipwise.com</a><br>
<a href="http://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com" rel="noreferrer" target="_blank">http://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com</a><br>
</blockquote></div>