From mmalkov at sipwise.com  Wed May 10 08:13:38 2023
From: mmalkov at sipwise.com (Mykola Malkov)
Date: Wed, 10 May 2023 14:13:38 +0200
Subject: [Spce-user] =?utf-8?q?New_Sipwise_C5_CE_mr9=2E5=2E7_is_now_avail?=
 =?utf-8?q?able?=
Message-ID: <10aa-645b8a80-1-12b90da0@72623379>


Hello everyone,

We would like to inform you that a new release of Sipwise C5, version mr9.5.7,
is now available!

You can find a list of new features and changes on our website at
https://www.sipwise.com/spce/blog/sipwise-c5-mr9-5-7-released/

mr9.5.7 is the latest build of the LTS release mr9.5.
Release mr9.5 will be supported until mr9.5.14 is released.

You can find the detailed release plan on our public calendar at
https://www.sipwise.com/releases/

We have uploaded the Install-CD media, Vagrant box, Virtualbox, VMware,
and AMI images. Please refer to the handbook at
https://www.sipwise.com/doc/mr9.5.7/spce for further details.

If you encounter any issues, please report them to this mailing list.
Thank you for being part of our community!
?????
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20230510/ab241366/attachment.html>

From marcos.pytel at cotesma.com.ar  Wed May 10 10:44:44 2023
From: marcos.pytel at cotesma.com.ar (Marcos Pablo Pytel)
Date: Wed, 10 May 2023 14:44:44 +0000
Subject: [Spce-user] re-route inbound call
Message-ID: <RO2P152MB69045DD81D051E8E8A7AB117B1779@RO2P152MB6904.LAMP152.PROD.OUTLOOK.COM>

Hello!

I have 2 sip peerings, one to the PSTN and other to IPBX.
How I can configure the sipwise to when I receive a call from PSTN, it re route the call to other peer (IPBX)


May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Call from PSTN - R=sip:428355 at x.x.x.x ID=1833815809 at x.x.x.x UA='Synway/5.3.2.1'
May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Inbound peering group '1' matched, looking up peer host - R=sip:428355 at x.x.x.x ID=1833815809 at x.x.x.x UA='Synway/5.3.2.1'
May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Selected peering host id '1' as inbound peer - R=sip:428355 at x.x.x.x ID=1833815809 at x.x.x.x UA='Synway/5.3.2.1'
May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Dialog managed, lua_dlg_callid:[1833815809 at x.x.x.x] - R=sip:428355 at x.x.x.x ID=1833815809 at x.x.x.x UA='Synway/5.3.2.1'
May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: User-Provided CLI '2972427000' taken from From-User - R=sip:428355 at x.x.x.x ID=1833815809 at x.x.x.x UA='Synway/5.3.2.1'
May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Network-Provided CLI '2972427000' taken from From-User - R=sip:428355 at x.x.x.x ID=1833815809 at x.x.x.x UA='Synway/5.3.2.1'
May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Setting '2972427000 at x.x.x.x' as initiating user-provided CLI - R=sip:428355 at x.x.x.x ID=1833815809 at x.x.x.x UA='Synway/5.3.2.1'
May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Setting '2972427000 at x.x.x.x' as initiating network-provided CLI - R=sip:428355 at x.x.x.x ID=1833815809 at x.x.x.x UA='Synway/5.3.2.1'
May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Rewriting called party '428355' to '542972428355' - R=sip:428355 at x.x.x.x ID=1833815809 at x.x.x.x UA='Synway/5.3.2.1'
May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Callee is not local - R=sip:542972428355 at x.x.x.x ID=1833815809 at x.x.x.x UA='Synway/5.3.2.1'
May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Call to unknown user - R=sip:542972428355 at x.x.x.x ID=1833815809 at x.x.x.x UA='Synway/5.3.2.1'
May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Setting acc source-leg for uuid '0': '0|2972427000|x.x.x.x|2972427000|||0|||0|call|127.0.0.1|1683727207.068303||||||||||||2972427000||||' - R=sip:542972428355 at x.x.x.x ID=1833815809 at x.x.x.x UA='Synway/5.3.2.1'

Thank you in advance!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20230510/d8d428d0/attachment.html>

From matthias.hohl at telematica.at  Wed May 10 12:53:35 2023
From: matthias.hohl at telematica.at (Matthias Hohl)
Date: Wed, 10 May 2023 18:53:35 +0200 (CEST)
Subject: [Spce-user] re-route inbound call
In-Reply-To: <RO2P152MB69045DD81D051E8E8A7AB117B1779@RO2P152MB6904.LAMP152.PROD.OUTLOOK.COM>
References: <RO2P152MB69045DD81D051E8E8A7AB117B1779@RO2P152MB6904.LAMP152.PROD.OUTLOOK.COM>
Message-ID: <968475024.11761238.1683737615332.JavaMail.zimbra@mx>

For sure via LNP this is possible or via ?force inbound call to peer? and create peering rules for it

> Am 10.05.2023 um 16:45 schrieb Marcos Pablo Pytel via Spce-user <spce-user at lists.sipwise.com>:
> 
> ?
> Hello!
> 
> I have 2 sip peerings, one to the PSTN and other to IPBX.
> How I can configure the sipwise to when I receive a call from PSTN, it re route the call to other peer (IPBX)
> 
> 
> May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Call from PSTN - R=sip:428355 at x.x.x.x ID=1833815809 at x.x.x.x UA='Synway/5.3.2.1'
> May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Inbound peering group '1' matched, looking up peer host - R=sip:428355 at x.x.x.x ID=1833815809 at x.x.x.x UA='Synway/5.3.2.1'
> May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Selected peering host id '1' as inbound peer - R=sip:428355 at x.x.x.x ID=1833815809 at x.x.x.x UA='Synway/5.3.2.1'
> May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Dialog managed, lua_dlg_callid:[1833815809 at x.x.x.x] - R=sip:428355 at x.x.x.x ID=1833815809 at x.x.x.x UA='Synway/5.3.2.1'
> May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: User-Provided CLI '2972427000' taken from From-User - R=sip:428355 at x.x.x.x ID=1833815809 at x.x.x.x UA='Synway/5.3.2.1'
> May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Network-Provided CLI '2972427000' taken from From-User - R=sip:428355 at x.x.x.x ID=1833815809 at x.x.x.x UA='Synway/5.3.2.1'
> May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Setting '2972427000 at x.x.x.x' as initiating user-provided CLI - R=sip:428355 at x.x.x.x ID=1833815809 at x.x.x.x UA='Synway/5.3.2.1'
> May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Setting '2972427000 at x.x.x.x' as initiating network-provided CLI - R=sip:428355 at x.x.x.x ID=1833815809 at x.x.x.x UA='Synway/5.3.2.1'
> May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Rewriting called party '428355' to '542972428355' - R=sip:428355 at x.x.x.x ID=1833815809 at x.x.x.x UA='Synway/5.3.2.1'
> May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Callee is not local - R=sip:542972428355 at x.x.x.x ID=1833815809 at x.x.x.x UA='Synway/5.3.2.1'
> May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Call to unknown user - R=sip:542972428355 at x.x.x.x ID=1833815809 at x.x.x.x UA='Synway/5.3.2.1'
> May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Setting acc source-leg for uuid '0': '0|2972427000|x.x.x.x|2972427000|||0|||0|call|127.0.0.1|1683727207.068303||||||||||||2972427000||||' - R=sip:542972428355 at x.x.x.x ID=1833815809 at x.x.x.x UA='Synway/5.3.2.1'
> 
> Thank you in advance!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20230510/484a453c/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2299 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20230510/484a453c/attachment.p7s>

From marcos.pytel at cotesma.com.ar  Wed May 10 13:05:04 2023
From: marcos.pytel at cotesma.com.ar (Marcos Pablo Pytel)
Date: Wed, 10 May 2023 17:05:04 +0000
Subject: [Spce-user] re-route inbound call
Message-ID: <RO2P152MB69045AE6157C128414CF2C08B1779@RO2P152MB6904.LAMP152.PROD.OUTLOOK.COM>

Thanks Matthias!

Yes, I have "force inbound call to peer" = Allways in the domaing preferences and created the peering rules but i I can't get it to work!

I have "outbound peering rules" in the peering to 3CX that contains:

Callee Prefix : 428355
Callee Pattern: ^.+542972428355.+$

Best Regards!
Marcos.

________________________________
De: Matthias Hohl
Enviado: Mi?rcoles, 10 de Mayo de 2023 13:53
Para: Marcos Pablo Pytel
CC: spce-user at lists.sipwise.com
Asunto: Re: [Spce-user] re-route inbound call

For sure via LNP this is possible or via ?force inbound call to peer? and create peering rules for it

Am 10.05.2023 um 16:45 schrieb Marcos Pablo Pytel via Spce-user <spce-user at lists.sipwise.com>:

?
Hello!

I have 2 sip peerings, one to the PSTN and other to IPBX.
How I can configure the sipwise to when I receive a call from PSTN, it re route the call to other peer (IPBX)


May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Call from PSTN - R=sip:428355 at x.x.x.x ID=1833815809 at x.x.x.x UA='Synway/5.3.2.1'
May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Inbound peering group '1' matched, looking up peer host - R=sip:428355 at x.x.x.x ID=1833815809 at x.x.x.x UA='Synway/5.3.2.1'
May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Selected peering host id '1' as inbound peer - R=sip:428355 at x.x.x.x ID=1833815809 at x.x.x.x UA='Synway/5.3.2.1'
May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Dialog managed, lua_dlg_callid:[1833815809 at x.x.x.x] - R=sip:428355 at x.x.x.x ID=1833815809 at x.x.x.x UA='Synway/5.3.2.1'
May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: User-Provided CLI '2972427000' taken from From-User - R=sip:428355 at x.x.x.x ID=1833815809 at x.x.x.x UA='Synway/5.3.2.1'
May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Network-Provided CLI '2972427000' taken from From-User - R=sip:428355 at x.x.x.x ID=1833815809 at x.x.x.x UA='Synway/5.3.2.1'
May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Setting '2972427000 at x.x.x.x' as initiating user-provided CLI - R=sip:428355 at x.x.x.x ID=1833815809 at x.x.x.x UA='Synway/5.3.2.1'
May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Setting '2972427000 at x.x.x.x' as initiating network-provided CLI - R=sip:428355 at x.x.x.x ID=1833815809 at x.x.x.x UA='Synway/5.3.2.1'
May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Rewriting called party '428355' to '542972428355' - R=sip:428355 at x.x.x.x ID=1833815809 at x.x.x.x UA='Synway/5.3.2.1'
May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Callee is not local - R=sip:542972428355 at x.x.x.x ID=1833815809 at x.x.x.x UA='Synway/5.3.2.1'
May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Call to unknown user - R=sip:542972428355 at x.x.x.x ID=1833815809 at x.x.x.x UA='Synway/5.3.2.1'
May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Setting acc source-leg for uuid '0': '0|2972427000|x.x.x.x|2972427000|||0|||0|call|127.0.0.1|1683727207.068303||||||||||||2972427000||||' - R=sip:542972428355 at x.x.x.x ID=1833815809 at x.x.x.x UA='Synway/5.3.2.1'

Thank you in advance!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20230510/76023ccd/attachment-0001.html>

From matthias.hohl at telematica.at  Wed May 10 14:17:18 2023
From: matthias.hohl at telematica.at (Matthias Hohl)
Date: Wed, 10 May 2023 20:17:18 +0200 (CEST)
Subject: [Spce-user] re-route inbound call
In-Reply-To: <RO2P152MB69045AE6157C128414CF2C08B1779@RO2P152MB6904.LAMP152.PROD.OUTLOOK.COM>
References: <RO2P152MB69045AE6157C128414CF2C08B1779@RO2P152MB6904.LAMP152.PROD.OUTLOOK.COM>
Message-ID: <1379278340.11769804.1683742638248.JavaMail.zimbra@mx>

Callee pattern looks wrong formated

> Am 10.05.2023 um 19:05 schrieb Marcos Pablo Pytel <marcos.pytel at cotesma.com.ar>:
> 
> ?
> Thanks Matthias!
> 
> Yes, I have "force inbound call to peer" = Allways in the domaing preferences and created the peering rules but i I can't get it to work!
> 
> I have "outbound peering rules" in the peering to 3CX that contains:
> 
> Callee Prefix : 428355
> Callee Pattern: ^.+542972428355.+$
> 
> Best Regards!
> Marcos.
> 
> De: Matthias Hohl
> Enviado: Mi?rcoles, 10 de Mayo de 2023 13:53
> Para: Marcos Pablo Pytel
> CC: spce-user at lists.sipwise.com
> Asunto: Re: [Spce-user] re-route inbound call
> 
> For sure via LNP this is possible or via ?force inbound call to peer? and create peering rules for it
> 
>>> Am 10.05.2023 um 16:45 schrieb Marcos Pablo Pytel via Spce-user <spce-user at lists.sipwise.com>:
>>> 
>> ?
>> Hello!
>> 
>> I have 2 sip peerings, one to the PSTN and other to IPBX.
>> How I can configure the sipwise to when I receive a call from PSTN, it re route the call to other peer (IPBX)
>> 
>> 
>> May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Call from PSTN - R=sip:428355 at x.x.x.x ID=1833815809 at x.x.x.x UA='Synway/5.3.2.1'
>> May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Inbound peering group '1' matched, looking up peer host - R=sip:428355 at x.x.x.x ID=1833815809 at x.x.x.x UA='Synway/5.3.2.1'
>> May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Selected peering host id '1' as inbound peer - R=sip:428355 at x.x.x.x ID=1833815809 at x.x.x.x UA='Synway/5.3.2.1'
>> May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Dialog managed, lua_dlg_callid:[1833815809 at x.x.x.x] - R=sip:428355 at x.x.x.x ID=1833815809 at x.x.x.x UA='Synway/5.3.2.1'
>> May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: User-Provided CLI '2972427000' taken from From-User - R=sip:428355 at x.x.x.x ID=1833815809 at x.x.x.x UA='Synway/5.3.2.1'
>> May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Network-Provided CLI '2972427000' taken from From-User - R=sip:428355 at x.x.x.x ID=1833815809 at x.x.x.x UA='Synway/5.3.2.1'
>> May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Setting '2972427000 at x.x.x.x' as initiating user-provided CLI - R=sip:428355 at x.x.x.x ID=1833815809 at x.x.x.x UA='Synway/5.3.2.1'
>> May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Setting '2972427000 at x.x.x.x' as initiating network-provided CLI - R=sip:428355 at x.x.x.x ID=1833815809 at x.x.x.x UA='Synway/5.3.2.1'
>> May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Rewriting called party '428355' to '542972428355' - R=sip:428355 at x.x.x.x ID=1833815809 at x.x.x.x UA='Synway/5.3.2.1'
>> May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Callee is not local - R=sip:542972428355 at x.x.x.x ID=1833815809 at x.x.x.x UA='Synway/5.3.2.1'
>> May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Call to unknown user - R=sip:542972428355 at x.x.x.x ID=1833815809 at x.x.x.x UA='Synway/5.3.2.1'
>> May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Setting acc source-leg for uuid '0': '0|2972427000|x.x.x.x|2972427000|||0|||0|call|127.0.0.1|1683727207.068303||||||||||||2972427000||||' - R=sip:542972428355 at x.x.x.x ID=1833815809 at x.x.x.x UA='Synway/5.3.2.1'
>> 
>> Thank you in advance!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20230510/067af99e/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2299 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20230510/067af99e/attachment.p7s>

From mcapetta at sipwise.com  Thu May 11 03:15:33 2023
From: mcapetta at sipwise.com (Marco Capetta)
Date: Thu, 11 May 2023 09:15:33 +0200
Subject: [Spce-user] re-route inbound call
In-Reply-To: <RO2P152MB69045DD81D051E8E8A7AB117B1779@RO2P152MB6904.LAMP152.PROD.OUTLOOK.COM>
References: <RO2P152MB69045DD81D051E8E8A7AB117B1779@RO2P152MB6904.LAMP152.PROD.OUTLOOK.COM>
Message-ID: <e1fdf4bf-eac1-34fe-65c4-47e923e247b8@sipwise.com>

Hi Marcos,

to connect an IPBX system you can also use a simple subscriber, you 
don't need a peer.
You can just assign the root number to the subscriber, then the system 
will locate the subscriber by longest matching prefix.
Please refer to this section of the handbook: 
https://www.sipwise.com/doc/mr11.3.1/spce/ce/mr11.3.1/advancedconfiguration/advancedconfiguration.html#inbound-calls-routing

In case you really need to configure the IPBX as a peer, then consider 
to activate 'kamailio.proxy.allow_peer_relay' param in the config.yml 
file. This will allow to relay calls coming from peers to other peers.

Thanks
Marco


On 10/05/23 16:44, Marcos Pablo Pytel via Spce-user wrote:
> Hello!
>
> I have 2 sip peerings, one to the PSTN and other to IPBX.
> How I can configure the sipwise to when I receive a call from PSTN, it 
> re route the call to other peer (IPBX)
>
>
> May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Call from PSTN - 
> R=sip:428355 at x.x.x.x ID=1833815809 at x.x.x.x UA='Synway/5.3.2.1'
> May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Inbound peering 
> group '1' matched, looking up peer host - R=sip:428355 at x.x.x.x 
> ID=1833815809 at x.x.x.x UA='Synway/5.3.2.1'
> May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Selected peering 
> host id '1' as inbound peer - R=sip:428355 at x.x.x.x 
> ID=1833815809 at x.x.x.x UA='Synway/5.3.2.1'
> May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Dialog managed, 
> lua_dlg_callid:[1833815809 at x.x.x.x] - R=sip:428355 at x.x.x.x 
> ID=1833815809 at x.x.x.x UA='Synway/5.3.2.1'
> May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: User-Provided CLI 
> '2972427000' taken from From-User - R=sip:428355 at x.x.x.x 
> ID=1833815809 at x.x.x.x UA='Synway/5.3.2.1'
> May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Network-Provided 
> CLI '2972427000' taken from From-User - R=sip:428355 at x.x.x.x 
> ID=1833815809 at x.x.x.x UA='Synway/5.3.2.1'
> May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Setting 
> '2972427000 at x.x.x.x' as initiating user-provided CLI - 
> R=sip:428355 at x.x.x.x ID=1833815809 at x.x.x.x UA='Synway/5.3.2.1'
> May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Setting 
> '2972427000 at x.x.x.x' as initiating network-provided CLI - 
> R=sip:428355 at x.x.x.x ID=1833815809 at x.x.x.x UA='Synway/5.3.2.1'
> May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Rewriting called 
> party '428355' to '542972428355' - R=sip:428355 at x.x.x.x 
> ID=1833815809 at x.x.x.x UA='Synway/5.3.2.1'
> May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Callee is not 
> local - R=sip:542972428355 at x.x.x.x ID=1833815809 at x.x.x.x 
> UA='Synway/5.3.2.1'
> May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Call to unknown 
> user - R=sip:542972428355 at x.x.x.x ID=1833815809 at x.x.x.x 
> UA='Synway/5.3.2.1'
> May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Setting acc 
> source-leg for uuid '0': 
> '0|2972427000|x.x.x.x|2972427000|||0|||0|call|127.0.0.1|1683727207.068303||||||||||||2972427000||||' 
> - R=sip:542972428355 at x.x.x.x ID=1833815809 at x.x.x.x UA='Synway/5.3.2.1'
>
> Thank you in advance!
>

-- 
*Marco Capetta *
R&D Manager

Sipwise GmbH | an ALE Company <http://www.sipwise.com>
c/o ALE International ? Austria Branch
Saturn Tower
Leonard-Bernstein-Stra?e 10
1220 Vienna, Austria

Email: mcapetta at sipwise.com
Website: www.sipwise.com <http://www.sipwise.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20230511/89273056/attachment-0001.html>

From oscar.bello at dialapplet.com  Thu May 11 11:42:57 2023
From: oscar.bello at dialapplet.com (=?UTF-8?Q?Oscar_Javier_Bello_P=c3=a9rez?=)
Date: Thu, 11 May 2023 10:42:57 -0500
Subject: [Spce-user] Cannot open connection to redis - CE mr7.5.10
Message-ID: <ef007bf9-750b-253c-03a6-07b05d922172@dialapplet.com>

Hi!

We are getting this Redis error on a server CE mr7.5.10, there is a Know 
bug in this version?

ERROR: db_redis [redis_connection.c:127]: db_redis_connect(): cannot 
open connection to redis://localhost:6379/20: System error
ERROR: db_redis [redis_dbase.c:2771]: db_redis_update(): Failed to 
reconnect to server

Can you please suggest the best way to update this server CE mr7.5.10?

Regards!

-- 
Oscar Bello
Departamento de Telefon?a
Facebook icon <https://www.facebook.com/Dialapplet> LinkedIn icon 
<https://www.linkedin.com/company/dialapplet> Twitter icon 
<https://twitter.com/Dialapplet> Youtube icon 
<https://www.dialapplet.com> Instagram icon <mailto:info at dialapplet.com>
Logo <https://www.dialapplet.com/> 	T: (+57) 601 914 4999
E: oscar.bello at dialapplet.com
W: www.dialapplet.com <https://www.dialapplet.com> 	Colombia
110221 Bogot?, D.C.
Calle 99 No. 10 - 19 Piso 4

AVISO DE CONFIDENCIALIDAD
Le informamos, como destinatario de este mensaje, que el correo 
electr?nico v?a Internet no permite asegurar la confidencialidad de los 
mensajes transmitidos ni su integridad o correcta recepci?n. Si no 
consintiera la utilizaci?n del correo electr?nico v?a Internet, rogamos 
nos lo comunique de forma inmediata. Este mensaje va dirigido de manera 
exclusiva a su destinatario y puede contener informaci?n confidencial 
cuya divulgaci?n est? prohibida por la ley. Si ha recibido este mensaje 
por error, le rogamos nos lo comunique de forma inmediata por esta misma 
v?a y proceda a su eliminaci?n, as? como a la de cualquier documento 
adjunto al mismo. As?mismo, si no es el destinatario del mensaje, se le 
informa de que su lectura, copia, distribuci?n y utilizaci?n, as? como 
la de cualquier documento adjunto, sea cual sea su finalidad, est?n 
prohibidas.
CONFIDENTIALITY WARNING
We hereby inform you, as addressee of this message, that Internet e-mail 
neither guarantees the confidentiality nor the completeness or proper 
receipt of the messages sent. If you do not consent to the use of 
Internet e-mail, please notify us immediately. This message is intended 
exclusively for its addressee and may contain confidential information 
protected from disclosure by law. If you have received this message in 
error, please immediately notify us via e-mail and delete it and any 
attachment. If you are not the addressee indicated in this message, 
please be informed that any reading, copy, distribution or use of it or 
its attachments, for any purpose, is forbidden.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20230511/fac12211/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: lngmhefdepnlohin.png
Type: image/png
Size: 1571 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20230511/fac12211/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jhlfoomlpdockmjo.png
Type: image/png
Size: 1670 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20230511/fac12211/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: cejimdcdaghhkinc.png
Type: image/png
Size: 1873 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20230511/fac12211/attachment-0008.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jaoljjnompaaabng.png
Type: image/png
Size: 1792 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20230511/fac12211/attachment-0009.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gnealemnmljfgajb.png
Type: image/png
Size: 1768 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20230511/fac12211/attachment-0010.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: lgjipgaeinefeflm.png
Type: image/png
Size: 17697 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20230511/fac12211/attachment-0011.png>

From marcos.pytel at cotesma.com.ar  Thu May 11 14:38:30 2023
From: marcos.pytel at cotesma.com.ar (Marcos Pablo Pytel)
Date: Thu, 11 May 2023 18:38:30 +0000
Subject: [Spce-user] re-route inbound call
In-Reply-To: <e1fdf4bf-eac1-34fe-65c4-47e923e247b8@sipwise.com>
References: <RO2P152MB69045DD81D051E8E8A7AB117B1779@RO2P152MB6904.LAMP152.PROD.OUTLOOK.COM>
 <e1fdf4bf-eac1-34fe-65c4-47e923e247b8@sipwise.com>
Message-ID: <RO2P152MB690491E64E0E9EB49E0EA39AB1749@RO2P152MB6904.LAMP152.PROD.OUTLOOK.COM>

Thank you Marco!

Enabling "proxy.allow_peer_relay" works perfectly!

Thank you so much!

Marcos.

________________________________
De: Marco Capetta via Spce-user <spce-user at lists.sipwise.com>
Enviado: jueves, 11 de mayo de 2023 4:15
Para: spce-user at lists.sipwise.com <spce-user at lists.sipwise.com>
Asunto: Re: [Spce-user] re-route inbound call

Hi Marcos,

to connect an IPBX system you can also use a simple subscriber, you don't need a peer.
You can just assign the root number to the subscriber, then the system will locate the subscriber by longest matching prefix.
Please refer to this section of the handbook: https://www.sipwise.com/doc/mr11.3.1/spce/ce/mr11.3.1/advancedconfiguration/advancedconfiguration.html#inbound-calls-routing

In case you really need to configure the IPBX as a peer, then consider to activate 'kamailio.proxy.allow_peer_relay' param in the config.yml file. This will allow to relay calls coming from peers to other peers.

Thanks
Marco


On 10/05/23 16:44, Marcos Pablo Pytel via Spce-user wrote:
Hello!

I have 2 sip peerings, one to the PSTN and other to IPBX.
How I can configure the sipwise to when I receive a call from PSTN, it re route the call to other peer (IPBX)


May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Call from PSTN - R=sip:428355 at x.x.x.x ID=1833815809 at x.x.x.x<mailto:ID=1833815809 at x.x.x.x> UA='Synway/5.3.2.1'
May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Inbound peering group '1' matched, looking up peer host - R=sip:428355 at x.x.x.x ID=1833815809 at x.x.x.x<mailto:ID=1833815809 at x.x.x.x> UA='Synway/5.3.2.1'
May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Selected peering host id '1' as inbound peer - R=sip:428355 at x.x.x.x ID=1833815809 at x.x.x.x<mailto:ID=1833815809 at x.x.x.x> UA='Synway/5.3.2.1'
May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Dialog managed, lua_dlg_callid:[1833815809 at x.x.x.x<mailto:1833815809 at x.x.x.x>] - R=sip:428355 at x.x.x.x ID=1833815809 at x.x.x.x<mailto:ID=1833815809 at x.x.x.x> UA='Synway/5.3.2.1'
May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: User-Provided CLI '2972427000' taken from From-User - R=sip:428355 at x.x.x.x ID=1833815809 at x.x.x.x<mailto:ID=1833815809 at x.x.x.x> UA='Synway/5.3.2.1'
May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Network-Provided CLI '2972427000' taken from From-User - R=sip:428355 at x.x.x.x ID=1833815809 at x.x.x.x<mailto:ID=1833815809 at x.x.x.x> UA='Synway/5.3.2.1'
May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Setting '2972427000 at x.x.x.x<mailto:2972427000 at x.x.x.x>' as initiating user-provided CLI - R=sip:428355 at x.x.x.x ID=1833815809 at x.x.x.x<mailto:ID=1833815809 at x.x.x.x> UA='Synway/5.3.2.1'
May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Setting '2972427000 at x.x.x.x<mailto:2972427000 at x.x.x.x>' as initiating network-provided CLI - R=sip:428355 at x.x.x.x ID=1833815809 at x.x.x.x<mailto:ID=1833815809 at x.x.x.x> UA='Synway/5.3.2.1'
May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Rewriting called party '428355' to '542972428355' - R=sip:428355 at x.x.x.x ID=1833815809 at x.x.x.x<mailto:ID=1833815809 at x.x.x.x> UA='Synway/5.3.2.1'
May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Callee is not local - R=sip:542972428355 at x.x.x.x ID=1833815809 at x.x.x.x<mailto:ID=1833815809 at x.x.x.x> UA='Synway/5.3.2.1'
May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Call to unknown user - R=sip:542972428355 at x.x.x.x ID=1833815809 at x.x.x.x<mailto:ID=1833815809 at x.x.x.x> UA='Synway/5.3.2.1'
May 10 11:00:07 spce proxy[31695]: NOTICE: <script>: Setting acc source-leg for uuid '0': '0|2972427000|x.x.x.x|2972427000|||0|||0|call|127.0.0.1|1683727207.068303||||||||||||2972427000||||' - R=sip:542972428355 at x.x.x.x ID=1833815809 at x.x.x.x<mailto:ID=1833815809 at x.x.x.x> UA='Synway/5.3.2.1'

Thank you in advance!



--
Marco Capetta
R&D Manager

Sipwise GmbH | an ALE Company <http://www.sipwise.com>
c/o ALE International ? Austria Branch
Saturn Tower
Leonard-Bernstein-Stra?e 10
1220 Vienna, Austria

Email:  mcapetta at sipwise.com <mailto:mcapetta at sipwise.com>
Website:  www.sipwise.com <http://www.sipwise.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20230511/77d26936/attachment.html>

From sellvoip49 at gmail.com  Tue May 23 14:39:24 2023
From: sellvoip49 at gmail.com (Sell VoIP)
Date: Tue, 23 May 2023 23:39:24 +0500
Subject: [Spce-user] Billing Profile Fee not working for outbound
Message-ID: <CAGW0Z0AFAZ-PK1EvP=Qu+Fa9qt41FsL-+Ut3pjyXbhaQm+9mOg@mail.gmail.com>

Hi
I have installed Sipwise CE 5 version  mr11.3.1
<https://sip-pbx.cmwy.eu:1443/v2/#/statistics/versions>.
i have setup customer , peer, billing profile exactly as in the Handbook.
from billing profile when i remove billing free for a prefix, even then
outbound call is successful.
when i add billing fee with prefix, the call is successful too but no call
cost (0) seen in customer portal. Call is successful, but billing is not
working. Billing profile is set to postpaid.
can you guide me how to solve this issue?

-- 

*Regards*

*Asim*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20230523/4ddaedab/attachment.html>

From matthias.hohl at telematica.at  Thu May 25 09:07:47 2023
From: matthias.hohl at telematica.at (Matthias Hohl)
Date: Thu, 25 May 2023 15:07:47 +0200 (CEST)
Subject: [Spce-user] how to add additional DNS resolver on spce mr10.5.4?
Message-ID: <1475996861.13570827.1685020067738.JavaMail.zimbra@mx>

Hello,

 

i setup a SPCE and used just 1 DNS Resolver at initial setup and want to add
now a 2nd one.

But in /etc/resolv.conf he told me:

#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN

 

Where I should add the second resolver than?

In the network.yml it is already setup and applied, but I just see one entry
in resolv.conf

 

    neth0:

      dns_nameservers:

      - 8.8.8.8

      - 8.8.4.4

 

Do I miss something?

 

 

Mit freundlichen Gr??en,

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20230525/70a045e1/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5022 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20230525/70a045e1/attachment.p7s>

From edo.ekunwe at gmail.com  Thu May 25 11:29:20 2023
From: edo.ekunwe at gmail.com (Nogie Ekunwe)
Date: Thu, 25 May 2023 10:29:20 -0500
Subject: [Spce-user] Spce-user Digest, Vol 47, Issue 6
In-Reply-To: <mailman.7.1684944004.8340.spce-user_lists.sipwise.com@lists.sipwise.com>
References: <mailman.7.1684944004.8340.spce-user_lists.sipwise.com@lists.sipwise.com>
Message-ID: <9A2BFB52-19DE-4354-AC37-0246C8CB7F31@gmail.com>

Hi, 

I had a similar issue. The resolution of the numbers on the webpage is low so any Money in 0.0009 May still show up as 0 so try increasing the cost (as a test) to see if it will show up on the webpage. Your billing system should get the correct amount with the current resolution though.

Ekunwe

Sent from my iPhone

> On May 24, 2023, at 11:00 AM, spce-user-request at lists.sipwise.com wrote:
> 
> ?Send Spce-user mailing list submissions to
>    spce-user at lists.sipwise.com
> 
> To subscribe or unsubscribe via the World Wide Web, visit
>    http://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com
> or, via email, send a message with subject or body 'help' to
>    spce-user-request at lists.sipwise.com
> 
> You can reach the person managing the list at
>    spce-user-owner at lists.sipwise.com
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Spce-user digest..."
> 
> 
> Today's Topics:
> 
>   1. Billing Profile Fee not working for outbound (Sell VoIP)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Tue, 23 May 2023 23:39:24 +0500
> From: Sell VoIP <sellvoip49 at gmail.com>
> To: spce-user at lists.sipwise.com
> Subject: [Spce-user] Billing Profile Fee not working for outbound
> Message-ID:
>    <CAGW0Z0AFAZ-PK1EvP=Qu+Fa9qt41FsL-+Ut3pjyXbhaQm+9mOg at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
> 
> Hi
> I have installed Sipwise CE 5 version  mr11.3.1
> <https://sip-pbx.cmwy.eu:1443/v2/#/statistics/versions>.
> i have setup customer , peer, billing profile exactly as in the Handbook.
> from billing profile when i remove billing free for a prefix, even then
> outbound call is successful.
> when i add billing fee with prefix, the call is successful too but no call
> cost (0) seen in customer portal. Call is successful, but billing is not
> working. Billing profile is set to postpaid.
> can you guide me how to solve this issue?
> 
> -- 
> 
> *Regards*
> 
> *Asim*
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20230523/4ddaedab/attachment-0001.html>
> 
> ------------------------------
> 
> Subject: Digest Footer
> 
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> http://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com
> 
> 
> ------------------------------
> 
> End of Spce-user Digest, Vol 47, Issue 6
> ****************************************


From pmscpa at gmail.com  Sat May 27 10:30:01 2023
From: pmscpa at gmail.com (=?UTF-8?Q?Pedro_Ant=C3=B3nio?=)
Date: Sat, 27 May 2023 15:30:01 +0100
Subject: [Spce-user] Matching calls with different call-ID
Message-ID: <CANjw8BFGyPa9cvx_yW+54YsnjsHLOTOV8Ad=_UHMH+TCk4Q4Uw@mail.gmail.com>

Greetings.

I have been tasked with implementing rtpengine at my company's kubernetes
cluster. We use Kamailio and have rtpengine running in a separate pod. Now
the main issue is that our calls have 2 legs, one from the caller to our
server, then another from the server to the callee. Naturally this leads to
having two call IDs and this doesn't go very well with rtpengine. Is there
any way I could still match calls that have a different Call-ID? Could I
instead match the To and From fields?

Many thanks for any help.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20230527/b9930943/attachment.html>

From ptakjura at gmail.com  Tue May 30 06:06:27 2023
From: ptakjura at gmail.com (Jiri Ptacnik)
Date: Tue, 30 May 2023 12:06:27 +0200
Subject: [Spce-user] how to add additional DNS resolver on spce mr10.5.4?
In-Reply-To: <1475996861.13570827.1685020067738.JavaMail.zimbra@mx>
References: <1475996861.13570827.1685020067738.JavaMail.zimbra@mx>
Message-ID: <CAKEbq9Hy3Lu+HzUwq6DZ-C4-iizzCfAcnmXk9m5kHjJFObTnQA@mail.gmail.com>

Someone already told me here in mail list:

I assume you still have only one nameserver present in your
/etc/resolv.conf, so this seems to be about /etc/network/interfaces
vs /etc/resolv.conf. If you install the resolvconf package the
dns-nameservers configuration present in /etc/network/interfaces
should get honored.

JP

?t 25. 5. 2023 v 15:08 odes?latel Matthias Hohl
<matthias.hohl at telematica.at> napsal:
>
> Hello,
>
>
>
> i setup a SPCE and used just 1 DNS Resolver at initial setup and want to add now a 2nd one.
>
> But in /etc/resolv.conf he told me:
>
> #     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
>
>
>
> Where I should add the second resolver than?
>
> In the network.yml it is already setup and applied, but I just see one entry in resolv.conf
>
>
>
>     neth0:
>
>       dns_nameservers:
>
>       - 8.8.8.8
>
>       - 8.8.4.4
>
>
>
> Do I miss something?
>
>
>
>
>
> Mit freundlichen Gr??en,
>
>
>
> --
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> http://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com


From mmalkov at sipwise.com  Wed May 31 09:08:38 2023
From: mmalkov at sipwise.com (Mykola Malkov)
Date: Wed, 31 May 2023 15:08:38 +0200
Subject: [Spce-user] =?utf-8?q?New_Sipwise_C5_CE_mr8=2E5=2E11_is_now_avai?=
 =?utf-8?q?lable?=
Message-ID: <5a3c-64774700-11-31459240@12563149>


Hello everyone,

We would like to inform you that a new release of Sipwise C5, version mr8.5.11,
is now available!

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

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

You can find the detailed release plan on our public calendar at
https://www.sipwise.com/releases/

We have uploaded the Install-CD media, Vagrant box, Virtualbox, VMware,
and AMI images. Please refer to the handbook at
https://www.sipwise.com/doc/mr8.5.11/spce for further details.

If you encounter any issues, please report them to this mailing list.
Thank you for being part of our community!
?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20230531/8b697fb9/attachment.html>