[Spce-user] [EXTERNAL] Register Peering Servers

[Marco Capetta]

Hi Cesar,

We have found some issues in the remote peer authentication some time ago
and we fixed it in all the supported releases. Version mr13.2.1 is out of
support since a while, so I suggest you to upgrade your system to mr13.5.1
version that is the last supported version.

I have just double checked and in mr13.5.1 all looks working fine for me.

Thank you
Marco







On Wed, Dec 10, 2025 at 3:24 PM Marco Capetta <mcapetta at sipwise.com> wrote:

> Hi Cesar,
>
> we will try to replicate the case on our systems and let you know.
>
> Thank you
> Marco
>
> On Tue, Dec 9, 2025 at 7:43 PM Cesar Mora <cesarluis89 at gmail.com> wrote:
>
>> This is what I’ve discovered so far:
>>
>> On the GUI we set the required register parameters, and enabled
>> registration by "peer_auth_register = True”.
>> No visible registration under sngrep.
>>
>> Restarted sems with no notable changes.
>>
>> Inspected /var/log/ngcp/sems.log and found the following:
>>
>> - Normal startup, SBC/DSM loaded, but WARNING: "no complete account
>> provided: 'reg_agent' module remains inactive”. (I suspect reg_agent is
>> legacy).
>> - db_reg_agent loads OK (query in conf fetches prefs from
>> provisioning.voip_peer_preferences)
>> - Still no register.
>>
>> I went and took a look at /etc/ngcp-sems/etc/reg_agent.conf which
>> appears to be for the legacy register method, and the reason for the "no
>> complete account provided: 'reg_agent' module remains inactive” error.
>>
>> Took a look at /etc/ngcp-sems/etc/db_reg_agent.conf and extracted the
>> password for "mysql_user=sems_prepaid”
>>
>> Logged in to mysql and ran joined_query_peerings from db_reg_agent.conf
>> in MySQL (u sems_prepaid / DB kamailio).
>>
>> - When "peer_auth_register = false” there is no db info available. When "peer_auth_register
>> = True” the correct parameters are populated in the DB,
>> “registration_status” displays “2”, 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
>>
>> I went and did "ngcpcfg apply” multiple times which should regenerate
>> templates and restart SEMS. But still same results.
>>
>> As a last resort I tried a legacy 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 ngcpcfg apply
>>
>> Under /var/log/ngcp/sems.log got a loop with (probably expected,
>> deprecated register method):
>>
>> 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
>>
>> Any ideas?
>>
>> Cesar
>>
>>
>>
>> On Dec 9, 2025, at 9:10 AM, Cesar Mora <cesarluis89 at gmail.com> wrote:
>>
>> Hi!
>>
>> Thanks for the reply.
>>
>> 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.
>>
>> 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.
>>
>> 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.
>>
>> Thanks,
>> César Mora
>>
>> On Dec 9, 2025, at 6:26 AM, Marco Capetta <mcapetta at sipwise.com> wrote:
>>
>> 
>> Hi Cesar,
>>
>> There is no version mr13.2.1.3, but only mr13.2.1. Maybe you are
>> referring to a particular version of a package?
>>
>> 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?
>>
>> Additionally, can you check what happens if, after having configured the
>> outbound registrations, you restart sems service. Does it sends out the
>> registration messages?
>>
>> Thank you
>> Marco
>>
>>
>>
>>
>>
>> On Mon, Dec 8, 2025 at 5:06 PM Cesar Mora <cesarluis89 at gmail.com> wrote:
>>
>>> Hi all,
>>>
>>> I was wondering if anyone has encountered any issues with registering
>>> peering servers (trunks) on SipWise CE mr13.2.1.3
>>>
>>> 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.
>>>
>>> Thanks,
>>>
>>> Cesar
>>> --
>>> Spce-user mailing list
>>> Spce-user at lists.sipwise.com
>>> http://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com
>>>
>>
>> --
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com
>> http://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20251211/beeae1a2/attachment.htm>