[Spce-user] ISSUE: mr14.1.1 Continually re-registering

[SPCE Newbie]

> Hello,
> 
> have never got past a simple "extension to extension" call with
> 
> Can you please provide more details to this? By default, once the
> system has been correctly installed, it should work right out of the
> box.

Expected behaviour was that it work right out of the box

Observed behaviour was:

- Reported 15/12/25 - mr13.5.1 No PSTN gateways available
- Reported 16/12/25 - mr13.5.1 Contract Numbering appears one out
- Reported 19/12/25 - mr14.0.1 peer_auth_pass: Internal Server Error
- Reported 21/12/25 - mr14.0.1 peer_auth_register: Internal Server Error
- Reported 22/12/25 - mr14.0.1 filling  /ngcp-data/logs/kamailio-proxy.log
- Reported 29/01/26 - mr14.0.1 [Object Object] Error: peering/2/details/outboundrules/create
- Reported 20/02/26 - mr14.0.1 Continually re-registering
- Reported 02/03/26 - mr14.1.1 Continually re-registering

> 
> 1.  An "About" page in the GUI...
> 
> What do you mean by an "About" page? What information do you need?

On Wed, 11 Feb 2026 09:29:13 +0100
Jose Antonio Su Ng <jsung at sipwise.com> wrote:

To provide further support, I recommend sharing the admin-ui/panel 
package version,  

> 
> 2.  A "Factory Reset" in preference to wearing SSDs with repeated bare
> > metal re-installs...  
> 
> Unfortunately this makes little sense, as we do not see any reason to
> add this option,

Others find it makes sense to:
- Provide a save settings
- Provide a restore settings
- Provide a factory reset

> as mentioned in my reply a few lines above if the
> system is installed properly it should work right out of the box.

SPCE promises to provide the degree of control to modify INVITEs, to
provide fine control of caller id, recording, speech to text etc. that
were appealing.   The mileage of others may vary, but lived experience,
with SPCE over the past 6 months, hasn't lived-up to those expectations.

The existing platforms by contrast are trouble-free and have to be as
the are both EOL & EOS.  The situation has never arisen where an uncaught
error is thrown in the UI and the situation has never arisen where by
using the UI alone they are left in a state where no back-track set of UI
actions can be made to restore sane operation and where reset is required.

SPCE is highly capable and so highly complex.  But as with any complex
system, if it is possible for a naive user (the clue is in the list
subscriber name) to break it, then it isn't idiot proof.

> If you cannot manage to properly install it, you can get in contact
> with our Sales Team and ask for professional services to help you
> install the system correctly.

I did.

- Paying for support with some advanced configuration is one thing.
- Paying for issues is another.

> Best regards,
> Jose Su

Best regards

> On Thu, Mar 5, 2026 at 7:42 PM SPCE Newbie <spce-user at tel.co.uk>
> wrote:
> 
> > Dear Jose,
> >
> > Thank you for your continued support.
> >
> > Since trying SPCE 13.5.1 six months ago, have never got past a
> > simple "extension to extension" call with, to the best of my
> > knowledge, little if any customisation.
> >
> > May I offer two feature requests:-
> >
> > 1.  An "About" page in the GUI...
> > 2.  A "Factory Reset" in preference to wearing SSDs with repeated
> > bare metal re-installs...
> >
> > Again, thank you for your continued support.
> >
> >
> > ----- Original Message -----
> > Date: Wed, 4 Mar 2026 15:27:22 +0100
> > From: Jose Antonio Su Ng <jsung at sipwise.com>
> > To: SPCE Newbie <spce-user at tel.co.uk>, spce-user at lists.sipwise.com
> > Subject: Re: [EXTERNAL] Re: [Spce-user] ISSUE: mr14.1.1 Continually
> > re-registering
> >
> >
> > Hi,
> >
> > Issue has been acknowledged and a ticket with number MT#64552 has
> > been created.
> >
> > Best regards,
> > On 3/2/26 17:32, SPCE Newbie wrote:  
> > > Hi,
> > >
> > > Completed all mr14.0.1 to mr14.1.1 steps per the manual.
> > >
> > > As soon as maintenance mode disabled, SPCE begins, and continues
> > > to, register with peer multiple times per second.
> > > Intervals/expires are:
> > >
> > >
> > > b2b.dialog_publish_expires: 3600
> > > b2b.sbc.session_timer.session_expires: '300'
> > > kamailio.proxy.default_expires: '3600'
> > > kamailio.proxy.default_expires_range: '30'
> > > kamailio.proxy.emergency_prioritization.register_fake_expires:
> > > '3600' kamailio.proxy.lnp.api.keepalive_interval: '3'
> > > kamailio.proxy.expires_range: '30'
> > > kamailio.proxy.loop_detection.expire: '1'
> > > kamailio.proxy.max_expires: '43200'
> > > kamailio.proxy.min_expires: 600
> > > kamailio.proxy.natping_interval: '30'
> > > kamailio.proxy.nonce_expire: '300'
> > > kamailio.proxy.peer_probe.interval: '10'
> > > kamailio.proxy.presence.max_expires: '3600'
> > > kamailio.proxy.presence.min_expires: 3600
> > > kamailio.proxy.presence.min_expires_action: 2
> > > kamailio.proxy.stir.cache_expire: 3600
> > > kamailio.proxy.stir.expire: 300
> > > mediator.intermediate_interval: 60
> > > mediator.interval: '10'
> > > monitoring.interval: 10
> > > monitoring.staleness_interval: 30
> > > rateomat.loopinterval: '10'
> > > rtpengine.graphite.interval: 600
> > > sms.smsc.enquire__link_interval: '58'
> > > systemd.journald.rate_limit_interval: 0s
> > > witnessd.interval: ~
> > > www_admin.security.jwt.expires: 36000  
> >  
>