From mmalkov at sipwise.com  Fri Jan 14 08:49:39 2022
From: mmalkov at sipwise.com (Mykola Malkov)
Date: Fri, 14 Jan 2022 14:49:39 +0100
Subject: [Spce-user] New Sipwise C5 CE mr7.5.11 is now available
Message-ID: <64a8-61e17f80-5-26baa98@68017928>


Hello everyone,

This is to inform you about the availability of the new Sipwise C5 mr7.5.11!

Please find a list of new features and changes on our website:
https://www.sipwise.com/spce/blog/sipwise-c5-mr7-5-11-released/

mr7.5.11 is the next build of LTS release mr7.5.
Release mr7.5 will be supported until mr7.5.14 is released.

Detailed release planning you can find in public calendar
https://www.sipwise.com/releases/

The InstallCD media, Vagrant box, Virtualbox, VMware and
AMI images,as well as Docker hub container,have been uploaded.
As usual, please check the handbook for details:
https://www.sipwise.com/doc/mr7.5.11/spce

If you find any issues please report them on this mailing list.
Thank you for being a part of the community!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20220114/ea3f174d/attachment.html>

From ts at ferncast.de  Fri Jan 21 06:53:39 2022
From: ts at ferncast.de (Thomas Schlien)
Date: Fri, 21 Jan 2022 12:53:39 +0100
Subject: [Spce-user] Redis connection problem
Message-ID: <a21b96f8-77b5-7753-f786-6ed1d50bf2f8@ferncast.de>

Hi,

we use Sipwise CE mr10.1.1 and around every two weeks we get this kind 
of repetitive errors in /var/log/ngcp/kamailio-proxy.log:

Jan 21 08:43:53.398727 sip2 proxy[1837067]: NOTICE: DEFAULT_ROUTE 
<script>: New request on proxy - M=REGISTER R=?sip:sip.example.de? 
F=?sip:client at sip.example.de? T=?sip:client at sip.example.de? 
IP=?1.2.3.4?:?48941? (?127.0.0.1?:?5060?) 
ID=?tpB4lmA~R6v9ho]k+3. at 1.2.3.4? UA='2wcom 4audio IP-4c 2.06.9 (1.07)' 
DESTIP=?127.0.0.1?:?5062?
Jan 21 08:43:53.398806 sip2 proxy[1837067]: NOTICE: DEFAULT_ROUTE 
<script>: Sending reply S=100 Trying M=REGISTER fs='?127.0.0.1?:?5062?' 
du='?127.0.0.1?:?5060?' - R=?sip:sip.example.de? 
ID=?tpB4lmA~R6v9ho]k+3. at 1.2.3.4? UA='2wcom 4audio IP-4c 2.06.9 (1.07)'
Jan 21 08:43:53.398876 sip2 proxy[1837067]: NOTICE: ROUTE_AUTH <script>: 
Authentication failed, no credentials - R=?sip:sip.example.de? 
ID=?tpB4lmA~R6v9ho]k+3. at 1.2.3.4? UA='2wcom 4audio IP-4c 2.06.9 (1.07)' 
Auth=?<null>?
Jan 21 08:43:53.399508 sip2 proxy[1837067]: NOTICE: ROUTE_AUTH <script>: 
Sending reply S=401 fs='?127.0.0.1?:?5062?' du='?127.0.0.1?:?5060?' - 
ID=?tpB4lmA~R6v9ho]k+3. at 1.2.3.4? UA='2wcom 4audio IP-4c 2.06.9 (1.07)'
Jan 21 08:43:53.423845 sip2 proxy[1837070]: NOTICE: DEFAULT_ROUTE 
<script>: New request on proxy - M=REGISTER R=?sip:sip.example.de? 
F=?sip:client at sip.example.de? T=?sip:client at sip.example.de? 
IP=?1.2.3.4?:?48941? (?127.0.0.1?:?5060?) 
ID=?tpB4lmA~R6v9ho]k+3. at 1.2.3.4? UA='2wcom 4audio IP-4c 2.06.9 (1.07)' 
DESTIP=?127.0.0.1?:?5062?
Jan 21 08:43:53.423922 sip2 proxy[1837070]: NOTICE: DEFAULT_ROUTE 
<script>: Sending reply S=100 Trying M=REGISTER fs='?127.0.0.1?:?5062?' 
du='?127.0.0.1?:?5060?' - R=?sip:sip.example.de? 
ID=?tpB4lmA~R6v9ho]k+3. at 1.2.3.4? UA='2wcom 4audio IP-4c 2.06.9 (1.07)'
Jan 21 08:43:53.431007 sip2 proxy[1837070]: ERROR: ROUTE_REG_HANDLE 
db_redis [redis_connection.c:127]: db_redis_connect(): cannot open 
connection to redis://localhost:6379/20: System error
Jan 21 08:43:53.431078 sip2 proxy[1837070]: ERROR: ROUTE_REG_HANDLE 
db_redis [redis_connection.c:381]: db_redis_get_reply(): Failed to 
reconnect to redis db
Jan 21 08:43:53.431123 sip2 proxy[1837070]: ERROR: ROUTE_REG_HANDLE 
db_redis [redis_dbase.c:2043]: db_redis_perform_update(): Failed to get 
reply for query: <broken redis connection>
Jan 21 08:43:53.431166 sip2 proxy[1837070]: ERROR: ROUTE_REG_HANDLE 
db_redis [redis_dbase.c:2298]: db_redis_perform_update(): failed to 
perform the update
Jan 21 08:43:53.431208 sip2 proxy[1837070]: ERROR: ROUTE_REG_HANDLE 
db_redis [redis_dbase.c:2850]: db_redis_update(): failed to do the query
Jan 21 08:43:53.431258 sip2 proxy[1837070]: ERROR: ROUTE_REG_HANDLE 
usrloc [ucontact.c:1147]: db_update_ucontact_ruid(): updating database 
failed
Jan 21 08:43:53.431301 sip2 proxy[1837070]: ERROR: ROUTE_REG_HANDLE 
usrloc [ucontact.c:1663]: update_contact_db(): failed to update database
Jan 21 08:43:53.431343 sip2 proxy[1837070]: ERROR: ROUTE_REG_HANDLE 
registrar [save.c:796]: update_contacts(): failed to update contact
Jan 21 08:43:53.431386 sip2 proxy[1837070]: ERROR: ROUTE_REG_HANDLE 
<script>: Contacts failed - R=?sip:sip.example.de? 
ID=?tpB4lmA~R6v9ho]k+3. at 1.2.3.4? UA='2wcom 4audio IP-4c 2.06.9 (1.07)'
Jan 21 08:43:53.431430 sip2 proxy[1837070]: NOTICE: ROUTE_REG_HANDLE 
<script>: Sending reply S=500 Server Error fs='?127.0.0.1?:?5062?' 
du='?127.0.0.1?:?5060?' - R=?sip:sip.example.de? 
ID=?tpB4lmA~R6v9ho]k+3. at 1.2.3.4? UA='2wcom 4audio IP-4c 2.06.9 (1.07)'
Jan 21 08:43:53.431473 sip2 proxy[1837070]: ERROR: ROUTE_REG_HANDLE sl 
[sl_funcs.c:414]: sl_reply_error(): stateless error reply used: I'm 
terribly sorry, server error occurred (1/SL)

When the first message of this arrives, registering and calling is no 
longer possible. I already looked at the redis log (after enabling it), 
but there is no useful information. In addition I connected via 
"redis-cli -p 6379 -n 20" via SSH Console and the command "KEYS *" works 
without problem in the situation.

The only way to get the server back to work was to reboot the system or 
do a "systemctl restart redis-server".

Do you have any hint how I can find out what is going wrong?

Best regards,
Thomas

-- 
Dr.-Ing. Thomas Schlien
Ferncast GmbH
Gallierstr. 41a, 52074 Aachen
Germany

Phone: +49 241 99034567
Web:   www.ferncast.de
--
CEO: Detlef Wiese
Court of Registration: Amtsgericht Aachen
Commercial Register: HRB 22350



From manwe at sipdoc.net  Mon Jan 31 11:58:04 2022
From: manwe at sipdoc.net (Jon Bonilla (Manwe))
Date: Mon, 31 Jan 2022 17:58:04 +0100
Subject: [Spce-user] Backporting kamailio
Message-ID: <20220131175804.5e438715@multivac.sipdoc.net>

Hi all

I'm trying to install ngcp-kamailio mr10.2 in a spce mr7.5 box. 

I built it from sources and installed the packages, adapted the script to the
changes but when I try to start it I get a timeout from systemd

# systemctl status  kamailio-proxy
? kamailio-proxy.service - Kamailio (OpenSER) - the Open Source SIP Server,
Proxy Loaded: loaded (/lib/systemd/system/kamailio-proxy.service; enabled;
vendor preset: enabled) Drop-In: /etc/systemd/system/kamailio-proxy.service.d
           ??override.conf
   Active: failed (Result: timeout) since Mon 2022-01-31 10:44:55 EST; 1h 7min
ago Process: 23495 ExecStart=/usr/sbin/kamailio -P
/run/kamailio/kamailio.proxy.pid -f $CFGFILE -m $SHM_MEMORY -M $PKG_MEMORY -DD
(code=exited, status=0/SUCCESS) Main PID: 23495 (code=exited, status=0/SUCCESS)

Looks like kamailio starts but after some time systemd stops it for timeout.
Could this be caused because is a NOTIFY unit and systemd doesn't detect it?

Looks like the database and redis schemas are compatible, I don't see errors
there.

any hints?


cheers,

Jon


-- 
PekePBX, the multitenant PBX solution
https://pekepbx.com
-------------- 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/20220131/e06debaa/attachment.sig>

From rbetancor at serlink.es  Mon Jan 24 09:30:30 2022
From: rbetancor at serlink.es (=?utf-8?B?UmHDumw=?= Alexis Betancor Santana)
Date: Mon, 24 Jan 2022 14:30:30 -0000
Subject: [Spce-user] Adding custome headers for a peer
Message-ID: <651094847.1653834.1643034581646.JavaMail.zimbra@serlink.es>

Been digging on the list archives, but did not found anything related. 

We need to add a custom header on request going to a peer, it's not a dynamic one ... it just and static header, but I could not find a way to do it on mr 7.5.X 

Any hit? 

Saludos 
-- 
Ra?l Alexis Betancor Santana 
Serlink Telecom S.R.L.U. 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20220124/dbbc5ba6/attachment-0001.html>

From rob at bulk.nl  Tue Jan 25 10:37:58 2022
From: rob at bulk.nl (Rob van den Bulk)
Date: Tue, 25 Jan 2022 15:37:58 -0000
Subject: [Spce-user] found 1 failed service(s): ngcp-rest-api
Message-ID: <VI1PR08MB4414BA4E864978A9D78EFBB5B95F9@VI1PR08MB4414.eurprd08.prod.outlook.com>

Hello,

After new install 10.2.1

ngcp-status

found 1 failed service(s): ngcp-rest-api


starting the service don't work...

Any one?

Greeting Rob van den Bulk

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20220125/1585784c/attachment-0001.html>

From mmalkov at sipwise.com  Fri Jan 14 08:49:39 2022
From: mmalkov at sipwise.com (Mykola Malkov)
Date: Fri, 14 Jan 2022 14:49:39 +0100
Subject: [Spce-user] New Sipwise C5 CE mr7.5.11 is now available
Message-ID: <64a8-61e17f80-5-26baa98@68017928>


Hello everyone,

This is to inform you about the availability of the new Sipwise C5 mr7.5.11!

Please find a list of new features and changes on our website:
https://www.sipwise.com/spce/blog/sipwise-c5-mr7-5-11-released/

mr7.5.11 is the next build of LTS release mr7.5.
Release mr7.5 will be supported until mr7.5.14 is released.

Detailed release planning you can find in public calendar
https://www.sipwise.com/releases/

The InstallCD media, Vagrant box, Virtualbox, VMware and
AMI images,as well as Docker hub container,have been uploaded.
As usual, please check the handbook for details:
https://www.sipwise.com/doc/mr7.5.11/spce

If you find any issues please report them on this mailing list.
Thank you for being a part of the community!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20220114/ea3f174d/attachment-0002.html>

From ts at ferncast.de  Fri Jan 21 06:53:39 2022
From: ts at ferncast.de (Thomas Schlien)
Date: Fri, 21 Jan 2022 12:53:39 +0100
Subject: [Spce-user] Redis connection problem
Message-ID: <a21b96f8-77b5-7753-f786-6ed1d50bf2f8@ferncast.de>

Hi,

we use Sipwise CE mr10.1.1 and around every two weeks we get this kind 
of repetitive errors in /var/log/ngcp/kamailio-proxy.log:

Jan 21 08:43:53.398727 sip2 proxy[1837067]: NOTICE: DEFAULT_ROUTE 
<script>: New request on proxy - M=REGISTER R=?sip:sip.example.de? 
F=?sip:client at sip.example.de? T=?sip:client at sip.example.de? 
IP=?1.2.3.4?:?48941? (?127.0.0.1?:?5060?) 
ID=?tpB4lmA~R6v9ho]k+3. at 1.2.3.4? UA='2wcom 4audio IP-4c 2.06.9 (1.07)' 
DESTIP=?127.0.0.1?:?5062?
Jan 21 08:43:53.398806 sip2 proxy[1837067]: NOTICE: DEFAULT_ROUTE 
<script>: Sending reply S=100 Trying M=REGISTER fs='?127.0.0.1?:?5062?' 
du='?127.0.0.1?:?5060?' - R=?sip:sip.example.de? 
ID=?tpB4lmA~R6v9ho]k+3. at 1.2.3.4? UA='2wcom 4audio IP-4c 2.06.9 (1.07)'
Jan 21 08:43:53.398876 sip2 proxy[1837067]: NOTICE: ROUTE_AUTH <script>: 
Authentication failed, no credentials - R=?sip:sip.example.de? 
ID=?tpB4lmA~R6v9ho]k+3. at 1.2.3.4? UA='2wcom 4audio IP-4c 2.06.9 (1.07)' 
Auth=?<null>?
Jan 21 08:43:53.399508 sip2 proxy[1837067]: NOTICE: ROUTE_AUTH <script>: 
Sending reply S=401 fs='?127.0.0.1?:?5062?' du='?127.0.0.1?:?5060?' - 
ID=?tpB4lmA~R6v9ho]k+3. at 1.2.3.4? UA='2wcom 4audio IP-4c 2.06.9 (1.07)'
Jan 21 08:43:53.423845 sip2 proxy[1837070]: NOTICE: DEFAULT_ROUTE 
<script>: New request on proxy - M=REGISTER R=?sip:sip.example.de? 
F=?sip:client at sip.example.de? T=?sip:client at sip.example.de? 
IP=?1.2.3.4?:?48941? (?127.0.0.1?:?5060?) 
ID=?tpB4lmA~R6v9ho]k+3. at 1.2.3.4? UA='2wcom 4audio IP-4c 2.06.9 (1.07)' 
DESTIP=?127.0.0.1?:?5062?
Jan 21 08:43:53.423922 sip2 proxy[1837070]: NOTICE: DEFAULT_ROUTE 
<script>: Sending reply S=100 Trying M=REGISTER fs='?127.0.0.1?:?5062?' 
du='?127.0.0.1?:?5060?' - R=?sip:sip.example.de? 
ID=?tpB4lmA~R6v9ho]k+3. at 1.2.3.4? UA='2wcom 4audio IP-4c 2.06.9 (1.07)'
Jan 21 08:43:53.431007 sip2 proxy[1837070]: ERROR: ROUTE_REG_HANDLE 
db_redis [redis_connection.c:127]: db_redis_connect(): cannot open 
connection to redis://localhost:6379/20: System error
Jan 21 08:43:53.431078 sip2 proxy[1837070]: ERROR: ROUTE_REG_HANDLE 
db_redis [redis_connection.c:381]: db_redis_get_reply(): Failed to 
reconnect to redis db
Jan 21 08:43:53.431123 sip2 proxy[1837070]: ERROR: ROUTE_REG_HANDLE 
db_redis [redis_dbase.c:2043]: db_redis_perform_update(): Failed to get 
reply for query: <broken redis connection>
Jan 21 08:43:53.431166 sip2 proxy[1837070]: ERROR: ROUTE_REG_HANDLE 
db_redis [redis_dbase.c:2298]: db_redis_perform_update(): failed to 
perform the update
Jan 21 08:43:53.431208 sip2 proxy[1837070]: ERROR: ROUTE_REG_HANDLE 
db_redis [redis_dbase.c:2850]: db_redis_update(): failed to do the query
Jan 21 08:43:53.431258 sip2 proxy[1837070]: ERROR: ROUTE_REG_HANDLE 
usrloc [ucontact.c:1147]: db_update_ucontact_ruid(): updating database 
failed
Jan 21 08:43:53.431301 sip2 proxy[1837070]: ERROR: ROUTE_REG_HANDLE 
usrloc [ucontact.c:1663]: update_contact_db(): failed to update database
Jan 21 08:43:53.431343 sip2 proxy[1837070]: ERROR: ROUTE_REG_HANDLE 
registrar [save.c:796]: update_contacts(): failed to update contact
Jan 21 08:43:53.431386 sip2 proxy[1837070]: ERROR: ROUTE_REG_HANDLE 
<script>: Contacts failed - R=?sip:sip.example.de? 
ID=?tpB4lmA~R6v9ho]k+3. at 1.2.3.4? UA='2wcom 4audio IP-4c 2.06.9 (1.07)'
Jan 21 08:43:53.431430 sip2 proxy[1837070]: NOTICE: ROUTE_REG_HANDLE 
<script>: Sending reply S=500 Server Error fs='?127.0.0.1?:?5062?' 
du='?127.0.0.1?:?5060?' - R=?sip:sip.example.de? 
ID=?tpB4lmA~R6v9ho]k+3. at 1.2.3.4? UA='2wcom 4audio IP-4c 2.06.9 (1.07)'
Jan 21 08:43:53.431473 sip2 proxy[1837070]: ERROR: ROUTE_REG_HANDLE sl 
[sl_funcs.c:414]: sl_reply_error(): stateless error reply used: I'm 
terribly sorry, server error occurred (1/SL)

When the first message of this arrives, registering and calling is no 
longer possible. I already looked at the redis log (after enabling it), 
but there is no useful information. In addition I connected via 
"redis-cli -p 6379 -n 20" via SSH Console and the command "KEYS *" works 
without problem in the situation.

The only way to get the server back to work was to reboot the system or 
do a "systemctl restart redis-server".

Do you have any hint how I can find out what is going wrong?

Best regards,
Thomas

-- 
Dr.-Ing. Thomas Schlien
Ferncast GmbH
Gallierstr. 41a, 52074 Aachen
Germany

Phone: +49 241 99034567
Web:   www.ferncast.de
--
CEO: Detlef Wiese
Court of Registration: Amtsgericht Aachen
Commercial Register: HRB 22350




From manwe at sipdoc.net  Mon Jan 31 11:58:04 2022
From: manwe at sipdoc.net (Jon Bonilla (Manwe))
Date: Mon, 31 Jan 2022 17:58:04 +0100
Subject: [Spce-user] Backporting kamailio
Message-ID: <20220131175804.5e438715@multivac.sipdoc.net>

Hi all

I'm trying to install ngcp-kamailio mr10.2 in a spce mr7.5 box. 

I built it from sources and installed the packages, adapted the script to the
changes but when I try to start it I get a timeout from systemd

# systemctl status  kamailio-proxy
? kamailio-proxy.service - Kamailio (OpenSER) - the Open Source SIP Server,
Proxy Loaded: loaded (/lib/systemd/system/kamailio-proxy.service; enabled;
vendor preset: enabled) Drop-In: /etc/systemd/system/kamailio-proxy.service.d
           ??override.conf
   Active: failed (Result: timeout) since Mon 2022-01-31 10:44:55 EST; 1h 7min
ago Process: 23495 ExecStart=/usr/sbin/kamailio -P
/run/kamailio/kamailio.proxy.pid -f $CFGFILE -m $SHM_MEMORY -M $PKG_MEMORY -DD
(code=exited, status=0/SUCCESS) Main PID: 23495 (code=exited, status=0/SUCCESS)

Looks like kamailio starts but after some time systemd stops it for timeout.
Could this be caused because is a NOTIFY unit and systemd doesn't detect it?

Looks like the database and redis schemas are compatible, I don't see errors
there.

any hints?


cheers,

Jon


-- 
PekePBX, the multitenant PBX solution
https://pekepbx.com
-------------- 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/20220131/e06debaa/attachment-0002.sig>

From rbetancor at serlink.es  Mon Jan 24 09:30:30 2022
From: rbetancor at serlink.es (=?utf-8?B?UmHDumw=?= Alexis Betancor Santana)
Date: Mon, 24 Jan 2022 14:30:30 -0000
Subject: [Spce-user] Adding custome headers for a peer
Message-ID: <651094847.1653834.1643034581646.JavaMail.zimbra@serlink.es>

Been digging on the list archives, but did not found anything related. 

We need to add a custom header on request going to a peer, it's not a dynamic one ... it just and static header, but I could not find a way to do it on mr 7.5.X 

Any hit? 

Saludos 
-- 
Ra?l Alexis Betancor Santana 
Serlink Telecom S.R.L.U. 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20220124/dbbc5ba6/attachment-0002.html>

From rob at bulk.nl  Tue Jan 25 10:37:58 2022
From: rob at bulk.nl (Rob van den Bulk)
Date: Tue, 25 Jan 2022 15:37:58 -0000
Subject: [Spce-user] found 1 failed service(s): ngcp-rest-api
Message-ID: <VI1PR08MB4414BA4E864978A9D78EFBB5B95F9@VI1PR08MB4414.eurprd08.prod.outlook.com>

Hello,

After new install 10.2.1

ngcp-status

found 1 failed service(s): ngcp-rest-api


starting the service don't work...

Any one?

Greeting Rob van den Bulk

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20220125/1585784c/attachment-0002.html>