The release for Project Clearwater sprint "Rapidash" has been cut. The code for
this release is tagged as release-111 in GitHub.
This release includes the following bug fixes:
* Sprout handlers don't have a load monitor
(https://github.com/Metaswitch/sprout/issues/1586)
* poll_s
Ali Al Massry,
If you want to install an older version, you can set the repo URL in
/etc/apt/sources.list.d/clearwater.list to the version you want, e.g:
deb http://repo.cw-ngv.com/archive/repo106 binary/
The version number you need can be found in the release note (e.g. release 106
was the Mi
Hi,
Thanks for getting in touch. In answer to your questions:
1) Project Clearwater doesn’t integrate directly with an MRF, but you can
configure an AS that can control the MRF, and we’ve successfully integrated
with MRFs via an AS in the past.
2)
a. See above – once you have an A
Hi,
Project Clearwater’s built-in MMTEL TAS can do various types of call
forwarding, including Call Forwarding on Busy. See
http://clearwater.readthedocs.io/en/latest/IR.92_Supplementary_Services.html
for the list of services that the MMTEL TAS can provide.
As for voicemail – we don’t provide
The release for Project Clearwater sprint "Sandslash" has been cut. The code
for this release is tagged as release-112 in GitHub.
This release includes the following bug fixes:
* Sprout will incorrectly fail AKA authentication if the RES/XRES
contains an 0x00 byte (https://github.com/Met
Hi,
For the first issue (the cassandra hostname not being resolvable) - from what
you've written it sounds like your homestead pod is unable to get a DNS record
for "cassandra" from your DNS server (10.96.0.10). Have you tried testing the
DNS resolution from the homestead pod manually (using so
Hi,
in answer to your questions:
“So what is a suitable TAS…”
We don’t recommend a TAS to integrate with an MRF, but (as you point out) the
docs at
http://clearwater.readthedocs.io/en/latest/SIP_Interface_Specifications.html#mrfc-control-rfc-4240-rfc-5552-rfc-6230-rfc-6231-rfc-6505
should hope
Hi Pratap,
The easiest way to diagnose what’s going wrong will be to turn on debug logging
for sprout on your node and take a look at the logs you get.
The steps for turning on debug logging are (as detailed here:
http://clearwater.readthedocs.io/en/latest/Troubleshooting_and_Recovery.html#spro
Hi,
If you want to compile sprout from source, you can find the instructions here:
https://github.com/Metaswitch/sprout/blob/dev/docs/Development.md. This should
give you what you need to get started.
But you talk about changing a config file too – if it’s just configuration
options that you w
No, you can’t use that config file to route requests to a different S-CSCF
based on the request method, as the S-CSCF is selected on a per-subscriber
basis (using the info provided by the HSS).
What are you trying to achieve by doing this? It may be that there’s some other
way to do what you’re
Hi,
This is probably caused by a bug in Sprout, tracked under
https://github.com/Metaswitch/sprout/issues/1656, which can cause Sprout to
attempt to use the wrong port.
The workaround for this is to remove the “chronos_hostname” option from the
shared_config. Instructions on how to edit shared
Hi,
As mentioned in response to another report of the same problem, this is
probably caused by a bug in Sprout, tracked under
https://github.com/Metaswitch/sprout/issues/1656, which can cause Sprout to
attempt to use the wrong port.
The workaround for this is to remove the "chronos_hostname" o
Hi,
As you’ve noticed, VirtualBox uses NAT on the local IP address, which is
probably why your client configured with STUN could connect correctly but the
one without could not.
For configuring SIP clients, have you looked at the instructions here:
http://clearwater.readthedocs.io/en/latest/Ma
Hi,
No, that is not expected behaviour – the identities you created should have
persisted over a restart.
When you say that “the identities are gone”, what exactly do you mean? Do you
meant that SIP clients that you’ve registered to the node can no longer
register after the restart has complet
Hi,
This is expected behaviour if your client's registration in Step 3 is from the
same IP address and port when using UDP (which it is in this case). When
successive messages are received from the same IP/port, only the first message
is challenged.
If your client was sending the REGISTER in s
address/port.
Best regards,
Gilles
De : Clearwater [mailto:clearwater-boun...@lists.projectclearwater.org] De la
part de Sebastian Rex
Envoyé : jeudi 5 janvier 2017 17:07
À :
clearwater@lists.projectclearwater.org<mailto:clearwater@lists.projectclearwater.org>
Objet : Re: [Project Clearwat
Hi,
Sorry this isn't working for you.
Just to confirm first - have you set the scscf_node_uri in local_config on all
of your sprout nodes?
I can see from the log lines you included that your running on an older version
of clearwater. A lot of the code around this area has changed since the rel
Hi,
Currently, it’s not possible to configure Clearwater to use AKA when you’re
deploying without an external HSS. You can use AKA with an external HSS, but
(as mentioned in another email) Bono doesn’t support AKA authentication.
I’ll update the readthedocs pages to make them clearer on this.
Hi,
Yes, it is possible to use a pre-installed sprout node snapshot, and that
should speed up the scale-up time.
You would need a "clean" sprout node snapshot, and would need a way to
configure the local_config file on the new nodes. Once that's configured, the
sprout node should join the clus
Hi,
I just want to check: when you say “a subsequent INVITE first tries to resolve
DNS for scscf.cw-aio”, do you mean that the SIP client you’re using tries to do
this DNS lookup?
If so, what SIP client are you using?
As mentioned here:
http://clearwater.readthedocs.io/en/latest/All_in_one_Im
Hi,
Clearwater doesn’t ever look at the “user=phone” parameter on a From: or To:
URI. However, it does look at that parameter if it’s on the Request-URI. Am I
correct in thinking that the “user=phone” parameter also appears on the
Request-URI?
The user=phone parameter on a sip: Request-URI tel
Hi Steve,
It looks like the Sprout health monitoring script (possibly erroneously) thinks
that Sprout is in a bad state and is killing it.
Could you send us the monit logs from a time covering a crash? That should
allow us to check whether that’s the case. They’re at /var/log/monit.log
Also, d
also be a good idea
to try upgrading to at least that release.
Seb.
From: Clearwater [mailto:clearwater-boun...@lists.projectclearwater.org] On
Behalf Of Sebastian Rex
Sent: 20 January 2017 09:44
To: clearwater@lists.projectclearwater.org
Subject: Re: [Project Clearwater] Sprout regularly
nstallation, so whatever default metrics you define for
this.
Regards,
Steve
On 20 January 2017 at 10:15, Sebastian Rex
mailto:sebastian@metaswitch.com>> wrote:
Steve,
Further to the below, we’ve also fixed a couple of bugs in this area recently,
most notably https://github.
The release for Project Clearwater sprint "Vulpix" has been cut. The code for
this release is tagged as release-115 in GitHub.
This release includes the following bug fixes:
* Log spam leading to 3GB log file and maybe crashes: Error (Net-SNMP):
Use snmp_sess_select_info2() for process
Hi,
Would you mind also telling us what release of Project Clearwater you’re
running on?
Thanks,
Seb.
From: Clearwater [mailto:clearwater-boun...@lists.projectclearwater.org] On
Behalf Of Faustinoni Fabrizio
Sent: 24 January 2017 14:49
To: clearwater@lists.projectclearwater.org
Subject: [Proj
Hi,
Were you trying to remove them using the process documented here:
http://clearwater.readthedocs.io/en/latest/Clearwater_Elastic_Scaling.html?
i.e. did you run
sudo service clearwater-etcd decommission
on the Ralf nodes that you were decommissioning?
Regardless, it looks like the Ral
HI,
Quiescing Bono will take a long time to finish, as it must wait for all active
registrations to timeout. So if you have a re-registration time of 10 minutes,
it can take up to 10 minutes (20 if using UDP) for the bono quiesce command to
complete. So I suspect that you didn't wait long enoug
On Jan 25, 2017, at 4:43 PM, Faustinoni Fabrizio
mailto:fabrizio.faustin...@usi.ch>> wrote:
Hi Sebastian,
I;ve subscribed to the mailing list.
How can I know the clearwater versione? I’ve installed it just a couple of days
ago.
On Jan 25, 2017, at 10:38 AM, Sebastian Rex
mailto:seba
stin...@usi.ch]
Sent: 27 January 2017 13:16
To: Sebastian Rex
Cc: clearwater@lists.projectclearwater.org
Subject: Re: Unable to restart bono
Yes you are right, I waited only a couple of minutes.
A question:
If I run the sip-stress-test, it will register 15000 users.
For all active user there will be a
Hi Amutha,
What statistic are you trying to poll? I think that the one that you want is
chronosCallInstantaneousCount, as described in
https://github.com/Metaswitch/clearwater-snmp-handlers/blob/master/PROJECT-CLEARWATER-MIB
If that is the stat that you're polling, then it's worth checking that
The release for Project Clearwater sprint "Wartortle" has been cut. The code
for this release is tagged as release-116 in GitHub.
This release includes the following bug fixes:
* Sprout became unresponsive, apparently due to a deadlock when
processing CANCELs (https://github.com/Metasw
Hi,
Have you had a look at the sprout logs? Could you follow the instructions here:
http://clearwater.readthedocs.io/en/latest/Troubleshooting_and_Recovery.html#sprout
to turn on debug logging on sprout, and then repro the problem?
You’ll then see a lot more info in /var/log/sprout/sprout_curre
Hi,
As you’ve seen, there is no clearwater-sip-stress-coreonly package for repo84,
but the latest version of the clearwater-sip-stress-coreonly package should
work fine against an otherwise repo84 deployment. Therefore, you have a few
options:
1. upgrade your deployment to the “stable”
Hi,
Is there any more information in the /var/log/cassandra/system.log? It sounds
like cassandra is failing to start, which is causing the homestead errors
you’re seeing.
If possible, could you share with us the contents of
/var/log/cassandra/system.log and /etc/cassandra/cassandra.yaml? That
Hi,
Thanks for that. We upgraded the version of Cassandra that’s used from 2.0.14
to 2.1.15 in the Quilava release (as per the release note:
http://www.projectclearwater.org/sprint-quilava-release-note). Were you
upgrading from an older release than Quilava? It looks like something has gone
wr
can’t find the “stress_provision.sh” in the homestead node of repo84.
Is there any alternative way to do that on repo84?
Thank you.
From: Clearwater [mailto:clearwater-boun...@lists.projectclearwater.org] On
Behalf Of Sebastian Rex
Sent: Tuesday, February 14, 2017 8:28 PM
To:
clearwater
Hi,
We’ve spotted this email, which I presume was meant to go to the mailing list?
In future, you’re more likely to get a response if you send the email to the
mailing list.
What release are you trying to install? Also, what do you see if you try to run:
apt-get install clearwater-tcp-scalabil
Hi,
It looks like you’re getting a 200 OK to the REGISTER request, but you’re
getting a 408 to a subsequent SUBSCRIBE request (you can see this in the packet
capture you attached). So the client should be registered correctly. Are calls
working?
The SUBSCRIBE message appears to be for:
“appl
Hi,
The overload point of a single sprout node will depend on the size of the node,
amongst other factors, and so we don't provide a predefined overload point. 50
calls/second is probably quite close to the limit already for a single CPU
sprout node.
As a general rule, if you want to see wheth
Hi,
Are you not signed up to the mailing list? I've attached the response from
Wednesday, but that was sent to the mailing list so if you're not signed up
then you probably won't have seen it.
In order to ensure you see future responses, I'd recommend signing up by
clicking the "Mailing List S
Hi,
If you’re using an external HSS, then Homestead just acts as a cache for the
HSS data. The actual authentication processing is handled by Sprout.
The reason that you’re not seeing SIP messages between Sprout and Homestead is
that the interface between the two is HTTP, not SIP. When Sprout r
Hi,
First off – it doesn’t look like you’re signed up to the mailing list. We
recommend you sign up to the list by clicking the “Mailing List Signup” link
from here: http://www.projectclearwater.org/community.
As for your problem – are you saying that the file
“usr/share/clearwater/cassandra-s
5445 520d 0a43 6f6e 7465 6e74 EGISTER..Content
0x01a0: 2d4c 656e 6774 683a 2020 300d 0a0d 0a-Length:..0
22:09:54.807608 IP (tos 0x0, ttl 61, id 40399, offset 0, flags [none], proto
TCP (6), length 40)
2017-03-01 1:31 GMT-08:00 Sebastian Rex
mailto:sebastian@metaswitch.c
Hi,
It looks like you're still not signed up to the mailing list. We recommend you
sign up to the list by clicking the “Mailing List Signup” link from here:
http://www.projectclearwater.org/community to help your questions be answered
more quickly.
From your logs, it looks like the reason that
med Eldeeb [mailto:ahmed.eld...@4gtss.com]
Sent: 14 March 2017 16:27
To: Sebastian Rex
Subject: Re: [Project Clearwater] Hello
hi seb,
When trying to restart clearwater-etcd service via terminal it shows
runs the etcd process. If you run “ls -al
/var/lib/ | grep "clearwater-etcd”, what output do you see?
Have you tried to run clearwater-etcd manually as root at any point?
Seb.
From: Ahmed Eldeeb [mailto:ahmed.eld...@4gtss.com]
Sent: 14 March 2017 16:55
To: Sebastian Rex
Subject: Re: [Pr
You should only include your Project Clearwater nodes, not your DNS server.
Seb.
From: Ahmed Eldeeb [mailto:ahmed.eld...@4gtss.com]
Sent: 15 March 2017 12:40
To: Sebastian Rex
Subject: Re: [Project Clearwater] Hello
hi seb,
Ok in my deployment i created 3 virtual machines for the 6 nodes in
The release for Project Clearwater sprint "Boromir" has been cut. The code for
this release is tagged as release-119 in GitHub.
This release includes the following bug fixes:
* bgcf.json and enum.json are inconsistent in whether they allow visual
separators in numbers (https://github.c
The release for Project Clearwater sprint "Celebrimbor" has been cut. The code
for this release is tagged as release-120 in GitHub.
This release includes the following bug fixes:
* A fresh checkout of Ellis doesn't build first time
* Unable to unregister subscriber with wildcar
The release for Project Clearwater sprint "Helm Hammerhand" has been cut. The
code for this release is tagged as release-125 in GitHub.
This release includes a change to the way the PROJECT-CLEARWATER-MIB is
generated. It is now built from MIB fragments in the clearwater-snmp-handlers
repositor
The release for Project Clearwater sprint "Ilúvatar" has been cut. The code for
this release is tagged as release-126 in GitHub.
This release includes the following bug fixes:
· Excess line breaks between Sprout logs
· Dummy iFCs work on INVITEs but not on REGISTERs
·
Hi Jasper,
I’m not aware of anyone who’s tried running clearwater-sip-stress or
clearwater-sip-stress-coreonly against Clearwater running under Docker, so we
don’t have any pre-written guidelines on how to do it. Obviously, the level of
load that the deployment will be able to handle will depen
Anthony,
Without seeing the trace for myself, I can’t really say.
Did you take this capture from the docker host, or from the Sprout node? If it
was from the docker host, then it’s likely that what you’re seeing is:
· Sprout sends a message to the Docker host at 192.168.43.94
·
54 matches
Mail list logo
