[Spce-user] API timeout

Jon Bonilla (Manwe) manwe at sipdoc.net
Thu Mar 4 17:20:01 EST 2021

El Tue, 2 Mar 2021 21:02:09 +0100
"Rene Krenn" <rkrenn at sipwise.com> escribió:

> no, this requires a sequence of additional commits.
> br

I've raised the timeout to check what's going on. I called a PATCH to a
subscriber registration

time curl -i -k -u user:password  -H
"Content-type:application/json-patch+json"  -XPATCH
-d "[{\"op\":\"replace\", \"path\":\"\/contact\",
\"value\":\"sip:bbb at bbb.com:5060\"}]"

The command takes more than 1 minute. 

I tcpdumped redis and I see that all subscriber registrations are asked to the

Then SMEMBERS and HGETALL for each registration. 

Is this the way it should be?

> -----Ursprüngliche Nachricht-----
> Von: Jon Bonilla (Manwe) [mailto:manwe at sipdoc.net] 
> Gesendet: Dienstag, 2. März 2021 19:23
> An: spce-user at lists.sipwise.com
> Betreff: [Spce-user] API timeout
> Hi all
> A customer of mine is experiencing API issues (404 in the api log) when
> dealing with subscriber registrations. 
> Could it be that this patch is needed in v7.5.X?
> https://github.com/sipwise/ngcp-panel/commit/2741e9ec799f144a18226be9bbddc8a
> e202c0c17
> Just want to know if it's planned to manually patch myself before 7.5.8 is
> released as this can't wait long. If not I'll try to search elsewhere. 
> cheers,
> Jon
> --
> PekePBX, the multitenant PBX solution
> https://pekepbx.com

PekePBX, the multitenant PBX solution
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: Firma digital OpenPGP
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20210304/20bcb0a0/attachment-0002.sig>

More information about the Spce-user mailing list