Hi Daniele,
I don't know the answer to your question without investigating further.
Unfortunately my team are busy for the next couple of week trying to meet a
release deadline, so will not be able to look at this until this is complete.
Maybe someone else on the mailing list will be able to
Hi Prabhakaran,
Sorry you are still having problems.
The config you have for the WebRTC looks OK according to
https://clearwater.readthedocs.io/en/stable/WebRTC_support_in_Clearwater.html
You haven't said what WebRTC client you are using. The first thing to check is
that you are using a
Hi Gabriel,
It is theoretically possible to run the MMTEL AS over a separated container but
this is not something we have ever tested.
As to the questions of how to turn on MMTEL services, this is possible using
the Ellis Web UI. There should be a tab (or button) in the UI which will give
Hi Prabhakaran,
Looking through
https://clearwater.readthedocs.io/en/stable/Making_your_first_call.html and
your client config my initial thought is that you have configured your client
incorrectly.
You have Server address (under topology) configured to example.com.
However the docs state
Hi Jake,
Sorry you are having problems getting the USSI working. I'm afraid we don't
have any USSI SIP dialog captures available.
There may be others on the list who've investigated this before, so may be able
to help.
Do let us know if you get this working.
Thanks,
Anne
Hi Aravind,
If you are using BONO for your P-CSCF then public_hostname in local_config is
used in the record_route. This can be set to public_ip if necessary.
However the S-CSCF used the '_uri' in the Record-Route header where
we recommend that you do not set this yourself but use the defaults
Hi Gabriel,
You will find information on scaling out nodes at
https://clearwater.readthedocs.io/en/stable/Clearwater_Elastic_Scaling.html?highlight=scaling
The same process can be followed for all node types.
I hope this helps.
Cheers,
Anne
___
Hi Michael,
Have you looked at our call latency stats - this will give you average call
latency over a 5 second period. Details of our stats are at
https://clearwater.readthedocs.io/en/stable/Clearwater_SNMP_Statistics.html?highlight=snmp%20stats,
and there are some scripts at
Hi Gabriel,
To upload shared configuration between nodes you need to have a healthy etcd
cluster.
You can run clearwater-etcdctl cluster-health on a node to check on this.
When you install the first set of nodes in a Project Clearwater deployment, you
need to make sure that each of the nodes
Hi Gabriel,
To upload shared configuration between nodes you need to have a healthy etcd
cluster.
You can run clearwater-etcdctl cluster-health on a node to check on this.
When you install the first set of nodes in a Project Clearwater deployment, you
need to make sure that each of the nodes
Hi Nishank,
Glad you got it sorted.
Regards
Anne
___
Clearwater mailing list
Clearwater@lists.projectclearwater.org
http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
Hi Nishank,
A 408 Request Timeout could be coming from Clearwater (because its requests
upstream are timing out) or from Zoiper (because its requests to Clearwater are
timing out).
To help tell which is the case, could you turn on debug logging on Bono, by
following the steps here:
Hi Mike,
Project Clearwater doesn't run in Ubuntu 18.04. You need to use Ubuntu 14.04.
Anne
___
Clearwater mailing list
Clearwater@lists.projectclearwater.org
http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
Hi Gabriel,
I think the key issue is that you the Cassandra node keeps failing and without
that you won't be able to get the Homestead-prov service running.
Can you confirm that you have got your etcd cluster up and running healthily.
Are you following our setup steps from the README. If not,
Hi Amir,
Clearwater does not get involved with the media flows in a deployment, only the
SIP signalling.
Yours,
Anne
___
Clearwater mailing list
Clearwater@lists.projectclearwater.org
Hi Mario,
First, I would like to confirm that Project Clearwater should work with WebRTC
when using sipml5.
The first thing to check is that you are using a browser that supports the
sipml5 demo using websockets. We have found that calls do not work when we use
Chrome, but they do work with
Hi Aravind,
That sounds like an interesting topology to try out.
You might be able to configure this by setting upstream_hostname and
upstream_port options on Bono (see Clearwater Configuration Options Reference
doc), but this isn't a scenario we've tested. Let us know how you get on!
I hope
17 matches
Mail list logo