dies, then it’s possible that
it’s run out of work to do. Normally threads will programmed to run in a loop
handling events until terminated.
Thanks,
Richard
From: yan morris [mailto:morrisyan...@gmail.com]
Sent: 02 September 2016 07:05
To: Richard Whitehouse (projectclearwater.org
Stanislav,
Sorry to hear you are having these problems. We run stress regularly against
Project Clearwater deployments, and we don't see such problems, so it's down to
a difference in your setup.
We wouldn't ever expect to run stress against an all in one node - it's not
designed for any
Aravind,
The maximum expiry time that a subscriber can register for is configurable. By
default, it's 300 seconds, but it can be configured by changing the value of
reg_max_expires which can be shared in Clearwater's shared configuration.
There's further documentation on this at
[mailto:morrisyan...@gmail.com]
Sent: 06 September 2016 05:30
To: Richard Whitehouse (projectclearwater.org)
<richard.whiteho...@projectclearwater.org>
Subject: Re: [Project Clearwater] Is Bono a multi-thread program?
Hi , Richard
Thanks for your help .
I understand the architecture of m
Surender,
I presume you mean 'ellis' instead of 'ebill'?
You can change the default domain by changing the value of the home_domain
configuration option. Changing this is described in the documentation at
.
Richard
From: Clearwater [mailto:clearwater-boun...@lists.projectclearwater.org] On
Behalf Of Richard Whitehouse (projectclearwater.org)
Sent: 08 September 2016 15:10
To: clearwater@lists.projectclearwater.org; Surender Singh <surende...@hcl.com>
Subject: Re: [Project Clearwater] IPPBX Integ
Trey,
The repo keys haven’t changed, however when the last release was cut it was
incorrectly not signed, hence the warning you are seeing. We are looking into
how this happened.
We’ve fixed the signing problem – signing the binaries that were there, so this
error you no longer be present –
Morris,
Yes, Bono is multi-threaded. It’s architected with a transport thread which
handles incoming PJSIP requests and a number of worker threads, which SIP
messages are dispatched onto.
The worker threads are created by thread_dispatcher. By default bono has one
worker thread per CPU core.
Jaafar,
It looks like your etcd cluster isn't able to form as it can't contact the
other nodes in the cluster.
Do you have more than one node running? Have you allowed opened TCP port 4000
on all of your instances to allow traffic to be sent to that node, from all of
the other nodes in your
Jace Liang,
There is no default SIP port for gemini and memento when doing a manual
install. For a Chef install, by default they are configured to use 5055. They
can be configured in shared_config.
If there is no port configured, the Sproutlets which implement gemini and
memento will not be
Surender,
Have you seen the Clearwater docs on IR.92, which is the standard implementing
VoLTE?
Of particular note is
http://clearwater.readthedocs.io/en/stable/IR.92_Supplementary_Services.html
which details which supplementary services Clearwater supports, with respect to
the built in
Jake,
There's quite a lot of configurability involved here, as to which registration
types it should trigger on (initial registration, reregistration or
deregistration) and whether the S-CSCF should include the request/response in
the body.
Here's an example which provides extensive
Hi all,
The release for Project Clearwater sprint "Galadriel" has been cut. The code
for this release is tagged as release-124 in GitHub.
In this release we have enhanced Clearwater's security by changing the way the
Clearwater S-CSCF treats requests from endpoints that authenticate using the
Prashanth,
Project Clearwater supports proxying the Presence messages (SIP SUBSCRIBEs and
SIP NOTIFYs) - see the details in our documentation at
http://clearwater.readthedocs.io/en/stable/SIP_Interface_Specifications.html#presence-event-package-rfc-3856
However, you will need a separate SIP
Matthew,
Sorry to hear you are having problems deploying Clearwater on Docker.
I think that the socket factory error is actually fairly benign.
Does this happen every time you create your deployment?
Can you provide the config map that you are providing when deploying on
Kubernetes?
Can you
Matt,
What version of OpenStack are you running against? – it sounds like there may
be compatibility issues with heat templates.
Can you provide the full command – or at least the set of parameters that you
are provide to stack create?
Richard
From: Clearwater
Anthony,
The reason that the P-Charging-Vector is stripped on the incoming INVITE, is
because the P-CSCF (Bono) doesn’t trust the value received from the UE – which
is required by the IMS standards.
If you want Bono to add a P-Charging-Vector, then yes, you’ll need to configure
a CDF for
Jo,
I think you’ll need to provision some phone numbers in Ellis to proceed – see
http://clearwater.readthedocs.io/en/stable/Manual_Install.html?highlight=available%20numbers#provision-telephone-numbers-in-ellis
You’ll need to run this in your Ellis container using docker exec.
Richard
From:
Anthony,
No, it’s not the originating dialog identifier, or at least not solely the ODI
token. This can’t be used, as the ODI is only added by the S-CSCF when the call
is sent to an application server.
TS 24.229 is the correct spec to use here – see section 5.4.3.1, and it
identifies three
Muhammad,
Homestead supports being configured in two different modes:
- With a HSS
In this case, either hss_realm or hss_hostname, or both will be configured in
/etc/clearwater/shared_config in order to configure the Diameter stack to
communicate with the HSS.
- Without a
Anthony,
Can you explain more about what your application server is doing, and why it’s
responding on the ISC interface in this fashion?
Can you point to anything in the TS specs which suggests that it’s supported
for an AS to behave in this fashion?
From Clearwater’s perspective, we need to
Pushpendra,
Responses inline.
Richard
From: Kumar, Pushpendra [mailto:pushpendra.ku...@intel.com]
Sent: 01 March 2018 10:34
To: Richard Whitehouse (projectclearwater.org)
<richard.whiteho...@projectclearwater.org>
Subject: RE: Problems in manual installation of clearwater
Thanks Ri
Pushpendra,
I think there are two reasons you are hitting problems installing Clearwater:
1) The ellis node that you've created has a user called ellis, which as I
described below is required to be a system user under which the ellis processes
run.
I'd suggest you create the node with a
What user are you running this as? Can you post the full log of the install
process?
Richard
From: Kumar, Pushpendra [mailto:pushpendra.ku...@intel.com]
Sent: 01 March 2018 10:46
To: Richard Whitehouse (projectclearwater.org)
<richard.whiteho...@projectclearwater.org>
Subject: RE: Pr
Hi all,
The release for Project Clearwater sprint "Zamîn" has been cut. The code for
this release is tagged as release-130 in GitHub.
This is a big release for us! Over the last year, we've put a huge amount of
effort into increasing Project Clearwater's quality, as we know that
reliability
13:03
To: Richard Whitehouse (projectclearwater.org)
<richard.whiteho...@projectclearwater.org>
Subject: RE: Problems in manual installation of clearwater
Hi Richard,
I am confusing about DNS configuration, is it need to configure on every node
(bind need to install on every node?)
.
Richard
From: Kumar, Pushpendra [mailto:pushpendra.ku...@intel.com]
Sent: 02 March 2018 07:50
To: Richard Whitehouse (projectclearwater.org)
<richard.whiteho...@projectclearwater.org>
Subject: RE: Problems in manual installation of clearwater
Hi Richard,
I have successfully installed the ellis
...@intel.com]
Sent: 01 March 2018 13:04
To: Richard Whitehouse (projectclearwater.org)
<richard.whiteho...@projectclearwater.org>
Subject: RE: Problems in manual installation of clearwater
Thanks Richard, Now that dpkg problem is solved in ellis. One thing, When I
update using sudo apt-get
28 matches
Mail list logo
