Re: [Project Clearwater] Sprout compilation failed on ARM64 platform

Hi Hrishikish, Thank you for your continued support of Project Clearwater. Having a look through the output of the make command it looks as though warnings (which would not usually cause the compilation to abort) are being treated as errors and causing the compiler to stop. This suggests that t

Re: [Project Clearwater] External PCRF/ Rx interface Support

Hi Jobin, Thank you for your interested in Clearwater. Bono, which is part of our open source solution Project Clearwater, does not support an external PCRF. Metaswitch offers a P-CSCF which does support using an external PCRF, this is called Perimeta and you can read more about it here

Re: [Project Clearwater] [Clearwater] AS Configuration and untrusted sources

communication between as1 and as2. In attachment you can find the files /etc/hosts, /etc/dnsmasq.conf and the logs of bono and sprout. Thanks for the help, Michele Il giorno 31 lug 2017, alle ore 11:07, Andrew Edmonds mailto:andrew.edmo...@metaswitch.com>> ha scritto: Hi Michele, Could I ge

Re: [Project Clearwater] [Clearwater] AS Configuration and untrusted sources

ed_config files. Referring the previous message, my SIP client does use the same port for both REGISTER and SUBSCRIBE. Thank you for your support, Michele Il giorno 25 lug 2017, alle ore 15:40, Andrew Edmonds mailto:andrew.edmo...@metaswitch.com>> ha scritto: Hi Michele, I’ve spoken t

Re: [Project Clearwater] [Clearwater] AS Configuration and untrusted sources

rejected can be found at line 72104, while the rejection is at 72399. I had to censor part of contents and some headers of the messages, so there may be some inconsistencies. Thanks, Michele Il giorno 24 lug 2017, alle ore 11:53, Andrew Edmonds mailto:andrew.edmo...@metaswitch.com>&

Re: [Project Clearwater] [Clearwater] AS Configuration and untrusted sources

, while the rejection is at 72399. I had to censor part of contents and some headers of the messages, so there may be some inconsistencies. Thanks, Michele Il giorno 24 lug 2017, alle ore 11:53, Andrew Edmonds mailto:andrew.edmo...@metaswitch.com>> ha scritto: Hi Michele, Thank you fo

Re: [Project Clearwater] Sprout S-CSCF Forking disable

Hi Aravind, Thank you for your question. If you do have more than one UE registered to an IMS-Core network with the same IMPI and IMPU the S-CSCF needs some way to determine which endpoint to send the call to. The only way to do this with the standard Project Clearwater deployment is to have t

Re: [Project Clearwater] [Clearwater] AS Configuration and untrusted sources

Hi Michele, Thank you for your question. It may be the case that you need to update your firewall rules to allow traffic from your SIP client to reach the Application Server. However in order to verify this I will need the Bono logs from the time which you attempted to contact the AS. Could yo

Re: [Project Clearwater] Using Ellis to program call diversion isn't working

Hi Jake, Many thanks for updating your issue with the diagnosis, I will raise it on my end and hopefully it will also be of some help to future readers of the mailing list. Project Clearwater offers varying levels of support for the IR.92 supplementary call services

Re: [Project Clearwater] aarch64 build

Hi Martin, If we have a look at the Dockerfile we can see that the debian package required is clearwater-management (not clearwater-manager). clearwater-management is built by the

Re: [Project Clearwater] restund_process Execution failed on bono

Hi Hrishikesh, Thank you for your question and the detailed logs you have provided. The issues appears to be caused by your shared config, in the manual installation instructions you’ll see that we advise that the entries in share

Re: [Project Clearwater] aarch64 build

Hi Martin, Thank you for your interest in Clearwater. Our Clearwater-docker repository (which you can access through GitHub here) should have everything you need to deploy Project Clearwater using Docker. It contains instructions as well as the

Re: [Project Clearwater] Fail to test Clearwater with clearwater-live-test

une.ba...@gmail.com] Sent: Tuesday, June 27, 2017 3:13 PM To: Andrew Edmonds Subject: Re: [Project Clearwater] Fail to test Clearwater with clearwater-live-test Hi Andrew, Yo can find the logs in bono server. In fact there icscf is present in at least one config file. Regards [1] https://docs.goog

Re: [Project Clearwater] Fail to test Clearwater with clearwater-live-test

BA [mailto:alioune.ba...@gmail.com] Sent: Thursday, June 22, 2017 1:07 PM To: Andrew Edmonds Subject: Re: [Project Clearwater] Fail to test Clearwater with clearwater-live-test I forget to say also I have this log error in bono node: 22-06-2017 12:00:00.335 UTC Error sip_connection_pool.cpp:189

Re: [Project Clearwater] [Clearwater] Manual Install Instructions Shared Configuration error

017 10:51 AM To: clearwater@lists.projectclearwater.org; Andrew Edmonds Subject: Re: [Project Clearwater] [Clearwater] Manual Install Instructions Shared Configuration error Hi Andrew, Thank you for your response. [ellis]ubuntu@test-1:~$ sudo monit summary Monit 5.18.1 uptime: 15h 25m Servic

Re: [Project Clearwater] [Clearwater] Manual Install Instructions Shared Configuration error

Hi Bader, Thank you for your question. Clearwater-etcd is the component responsible for forming a cluster across your Clearwater nodes to allow configuration to be shared. If there is a problem with uploading shared config, clearwater-etcd is usually a good place to start diagnosing the issue.

Re: [Project Clearwater] Sipp stress test problem - 400 Bad Request

Hi Eric, Thank you for your question. Since we have updated our node types the bulk-provisioning commands should be run on the vellum nodes. Can you check that you get a successful output when you run the stress

Re: [Project Clearwater] Fail to test Clearwater with clearwater-live-test

Hi Alioune, Thank you for your question and for the detailed logs you have provided. When HTTP requests are sent to Ellis in order to provision subscribers they pass through nginx. nginx is a generic HTTP web server that should forward these HTTP requests on to Ellis. However if we look at the

Re: [Project Clearwater] CW Issue, while registering numbers (using Zoiper client)

Hi Ravi, Thank you for your question. The majority of the DNS requests that are required for a registration are done by the Clearwater VMs. There is only one DNS request that the external clients in Scenario B will need to do: if you have provided your Zoiper client with a hostname for the out

Re: [Project Clearwater] Failed to register an account at Zoiper & X-Lite

Hi Mahibul, Thank you for your question and the helpful screenshots you have provided. I can see that the configuration in your Zoiper client is missing a few crucial settings. You can follow the guide here to see how you

Re: [Project Clearwater] old OVF version

Hi Wassim, We have just run a series of tests against the May 22nd all-in-one OVA and have not found any issues with it. Could you please provide details of the problems you are hitting and if possible some relevant diagnostics. This will help us investigate things on our end. Thanks, Andrew

Re: [Project Clearwater] Clearwater Digest, Vol 49, Issue 8

----- From: Andrew Edmonds Sent: Friday, May 19, 2017 9:56 AM To: 'Astha Sharma' Subject: RE: Clearwater Digest, Vol 49, Issue 8 Hi Astha, Thank you for your question. I can see from your shared config that the parameters in the angle brackets have not been filled in correctly, in sc

Re: [Project Clearwater] /etc/clearwater/local_settings configured before packages install?

Hi Ahmed, Thank you for your question. The file containing the etcd_cluster config setting is /etc/clearwater/local_config (not /etc/clearwater/local_settings). We don’t have a documented process to produce pre-packaged images for our open source produce Project Clearwater. However our commerc

Re: [Project Clearwater] 403 forbidden on registering sip over UDP

rom: Astha Sharma [mailto:astha.sha...@aricent.com] Sent: Friday, May 12, 2017 9:50 AM To: Andrew Edmonds Subject: Re: 403 forbidden on registering sip over UDP Hi Andrew, Thanks for quick response. I have followed following steps: In /etc/clearwater/shared_config set or update the

Re: [Project Clearwater] Call between two Clearwater Deployment

Hi Eric, Thank you for your question. A call between two different Clearwater deployments is an off-net call. Both have their own sets of subscribers so you can think of them as belonging to two different mobile operators. After you have configured

Re: [Project Clearwater] using CW-AIO deployment

Hi Rajesh, Thanks for getting in touch with your question. In order to see why registrations aren’t working when using Bridged networking it would be helpful to have some more information. Can you try registering a subscriber again, as you do so can you take a packet capture of your AIO node (

Re: [Project Clearwater] images and flavors for clearwater components

Hi Wassim, Thanks for your question. Details about the various different installation methods Clearwater supports can be found here. You can follow the links at the bottom of this page for more detailed installation in

Re: [Project Clearwater] Unable to register using Zoiper client with AIO

Hi Hrishikesh, Thank you for your question. The HTTP client reporting an error code of 404 suggests that the subscriber you are attempting to register has not been found in the HSS. There are a few potential causes of this: · You may not have entered the subscriber information correct

Re: [Project Clearwater] Sprout processing time

Hi Chess, There is a config option “target_latency_us” which is maximum time for Sprout to process requests, after which Sprout will start rejecting some requests. This defaults to 100 milliseconds. You could change this though by entering into /etc/clearwater/shared_config the line: target_la

Re: [Project Clearwater] All-in-one Images setup supports I-CSCF functionality ?

Hi Aravind, Thank you for your question. To understand why the I-CSCF processing does not happen on an All-in-one Clearwater deployment it would help to think about what the role of the I-CSCF is. The I-CSCF is responsible for finding which S-SCSF is serving the requested subscriber. A real W

Re: [Project Clearwater] Sprout scratch

_file=/etc/clearwater/enum.json #billing_realm=ims02.as20650.net #cdf_identity=192.169.38.56 root@cw-sprout1:/etc/clearwater# Juan From: Clearwater [mailto:clearwater-boun...@lists.projectclearwater.org] On Behalf Of Andrew Edmonds Sent: lundi 24 avril 2017 20:37 To: clearwater@lists.projectclearw

Re: [Project Clearwater] Sprout scratch

Hi Juan Thank you for your questions and the diagnostics you have provided. I think there are two different bits of configuration here that are incorrect which are causing the symptoms you are seeing. Looking through the Sprout log file you sent me I can see on line 773 "Signal 6 caught" after

Re: [Project Clearwater] Sprout failed: Error: No local site registration store specified

nks in advance, Silvestro Ciampoli Da: Clearwater mailto:clearwater-boun...@lists.projectclearwater.org>> per conto di Andrew Edmonds mailto:andrew.edmo...@metaswitch.com>> Inviato: mercoledì 12 aprile 2017 17:47:03 A: clearwater@lists.projectclearwater.org<mailto:clearwater@

Re: [Project Clearwater] Sprout failed: Error: No local site registration store specified

Hi Silvestro, Thank you for your question and the information you have provided. You were right to point out the error "Error main.cpp:1678: No local site registration store specified". This will be the cause of your Sprout process failing to start. In order to specify a local site registration

Re: [Project Clearwater] Clearwater IMS homers failed to start..

Hi Salman, Thanks for your question. In order to better understand what is going on here could I please ask you to provide some more details about the deployment you are using: * What version of Clearwater are you using? * What topology are you using? What nodes make up your d

Re: [Project Clearwater] CDIV with MRF Invite message bounce-back to TAS

Hi Aravind, Thanks for your email. In order to diagnose the issue I need to understand a little more about your deployment. Could you please answer: * What does your deployment look like? What node types are you using and what are the IP addresses of your TAS and MRF node? *

Re: [Project Clearwater] Registration failed (Internal Server Error (500))

Hi Ahmed, Thank you for your continued use of Clearwater, we appreciate the feedback and logs you have provided here. A 500 error typically means that something has gone wrong with a node's internal processing. I've confirmed that this is the case by having a look through the Sprout logs you ha

Re: [Project Clearwater] 403 forbidden on registering

Hi Ahmed, Thanks for your question and the logs you have provided. A 403 error typically means that the password Zoiper has provided does not match the password provisioned in Ellis. I've confirmed this is the case by looking at the Sprout logs: 21-03-2017 08:22:36.428 UTC Error authentication

[Project Clearwater] Onix release note

The release for Project Clearwater sprint "Onix" has been cut. The code for this release is tagged as release-108 in github. In this release: * We've enhanced clearwater-docker so that storage services are run in their own containers (bringing us closer in line with standard microservi

[Project Clearwater] Missingno release note

The release for Project Clearwater sprint "Missingno" has been cut. The code for this release is tagged as release-106 in github. In this release we have been working towards increasing the robustness of our IPv6 solution. This release includes the following bug fixes: * Privacy heade

[Project Clearwater] Kangaskhan release note

The release for Project Clearwater sprint "Kangaskhan" has been cut. The code for this release is tagged as release-104 in github. This release includes the following bug fixes: * Sprout will challenge registrations repeatedly if memcached is down, rather than returning a 5xx error (

[Project Clearwater] Charizard release note

The release for Project Clearwater sprint "Charizard" has been cut. The code for this release is tagged as release-96 in github. This release includes the following bug fixes: * Sprout rejects calls with 503, reports that it is due to overload control in SAS (https://github.com/Metaswi

[Clearwater] Rob Roy Release Note

The release for sprint "Rob Roy" has been cut. The code for this release is tagged as release-85 in github. This release introduces active expiry of any subscriptions to registration events. This uses the same infrastructure as for expiring registrations - Sprout now sets Chronos timers to pop