Hi Nick, Can you please send me the debug logs from Sprout for these problems? You can turn on debug logging by creating/editing the file /etc/clearwater/user_settings, adding log_level=5 and then restarting Sprout (service sprout stop – it’s automatically restarted by monit). The logs are output in /var/log/sprout/sprout_<date>.
Ellie From: Clearwater [mailto:[email protected]] On Behalf Of [email protected] Sent: 03 September 2015 07:41 To: [email protected] Subject: [Clearwater] Call problems Hi community, I follow the manual installation guide to install six ubuntu14.04-server-x64 VMs, and they work successfully. I try the IMS with use X-Lite-free(2 sets) and Zoiper-Biz(2 sets) in Win7-64bit environment. However, there are some problems that I want to clarify : 1. The call（or video call） is able to run about 30 seconds, then it will be automatically terminated by callee . 2. The caller has already called, but the callee sometimes does not receive any call. 3. The status of friends in the contact show incorrectly. （For example, both A and B register already, and they can make a call. However, either A or B shows offline/waiting for response in their each contact.） The problems occur in both X-Lite and Zoiper. Here is a proportion of Sprout log : 02-09-2015 08:35:59.232 UTC Status memcached_config.cpp:109: servers= 02-09-2015 08:35:59.232 UTC Status memcachedstore.cpp:145: Updating memcached store configuration 02-09-2015 08:35:59.232 UTC Status memcachedstore.cpp:166: Finished preparing new view, so flag that workers should switch to it 02-09-2015 08:36:11.469 UTC Status load_monitor.cpp:237: Maximum incoming request rate/second increased to 829.906738 (based on a smoothed mean latency of 602 and 0 upstream overload responses) 02-09-2015 08:36:29.484 UTC Status memcached_config.cpp:70: Reloading memcached configuration from '/etc/clearwater/cluster_settings' 02-09-2015 08:36:29.485 UTC Status memcached_config.cpp:109: servers=100.64.119.89:11211 02-09-2015 08:36:29.485 UTC Status memcachedstore.cpp:145: Updating memcached store configuration 02-09-2015 08:36:29.485 UTC Status memcachedstore.cpp:166: Finished preparing new view, so flag that workers should switch to it 02-09-2015 08:36:29.485 UTC Status bgcfservice.cpp:68: No BGCF configuration (file ./bgcf.json does not exist) 02-09-2015 08:36:29.485 UTC Status memcached_config.cpp:70: Reloading memcached configuration from '/etc/clearwater/remote_cluster_settings' 02-09-2015 08:36:29.485 UTC Status memcached_config.cpp:109: servers= 02-09-2015 08:36:29.485 UTC Status memcachedstore.cpp:145: Updating memcached store configuration 02-09-2015 08:36:29.485 UTC Status memcachedstore.cpp:166: Finished preparing new view, so flag that workers should switch to it 02-09-2015 08:38:12.153 UTC Status bgcfservice.cpp:68: No BGCF configuration (file ./bgcf.json does not exist) 02-09-2015 08:38:12.154 UTC Status memcached_config.cpp:70: Reloading memcached configuration from '/etc/clearwater/remote_cluster_settings' 02-09-2015 08:38:12.154 UTC Status memcached_config.cpp:109: servers= 02-09-2015 08:38:12.154 UTC Status memcachedstore.cpp:145: Updating memcached store configuration 02-09-2015 08:38:12.154 UTC Status memcachedstore.cpp:166: Finished preparing new view, so flag that workers should switch to it 02-09-2015 08:38:12.154 UTC Status memcached_config.cpp:70: Reloading memcached configuration from '/etc/clearwater/cluster_settings' 02-09-2015 08:38:12.154 UTC Status memcached_config.cpp:109: servers=100.64.119.89:11211 02-09-2015 08:38:12.154 UTC Status memcachedstore.cpp:145: Updating memcached store configuration 02-09-2015 08:38:12.154 UTC Status memcachedstore.cpp:166: Finished preparing new view, so flag that workers should switch to it 02-09-2015 08:39:18.023 UTC Status load_monitor.cpp:237: Maximum incoming request rate/second increased to 839.810730 (based on a smoothed mean latency of 960 and 0 upstream overload responses) 02-09-2015 08:42:01.224 UTC Status load_monitor.cpp:237: Maximum incoming request rate/second increased to 849.721008 (based on a smoothed mean latency of 897 and 0 upstream overload responses) 02-09-2015 08:42:48.717 UTC Status load_monitor.cpp:237: Maximum incoming request rate/second increased to 859.164612 (based on a smoothed mean latency of 5564 and 0 upstream overload responses) 02-09-2015 08:42:54.878 UTC Status load_monitor.cpp:237: Maximum incoming request rate/second increased to 868.879700 (based on a smoothed mean latency of 2849 and 0 upstream overload responses) 02-09-2015 08:43:25.608 UTC Status load_monitor.cpp:237: Maximum incoming request rate/second increased to 878.729309 (based on a smoothed mean latency of 1504 and 0 upstream overload responses) 02-09-2015 08:48:36.669 UTC Error httpconnection.cpp:743: cURL failure with cURL error code 0 (see man 3 libcurl-errors) and HTTP error code 404 02-09-2015 08:48:36.669 UTC Error hssconnection.cpp:593: Could not get subscriber data from HSS 02-09-2015 08:48:37.105 UTC Error httpconnection.cpp:743: cURL failure with cURL error code 0 (see man 3 libcurl-errors) and HTTP error code 404 02-09-2015 08:48:37.105 UTC Error hssconnection.cpp:593: Could not get subscriber data from HSS 02-09-2015 08:49:25.694 UTC Status load_monitor.cpp:237: Maximum incoming request rate/second increased to 927.229126 (based on a smoothed mean latency of 5085 and 0 upstream overload responses) 02-09-2015 08:49:43.593 UTC Status load_monitor.cpp:237: Maximum incoming request rate/second increased to 937.088806 (based on a smoothed mean latency of 1403 and 0 upstream overload responses) 02-09-2015 08:50:10.339 UTC Error httpconnection.cpp:743: cURL failure with cURL error code 0 (see man 3 libcurl-errors) and HTTP error code 404 02-09-2015 08:50:10.339 UTC Error hssconnection.cpp:593: Could not get subscriber data from HSS 02-09-2015 08:50:11.039 UTC Error httpconnection.cpp:743: cURL failure with cURL error code 0 (see man 3 libcurl-errors) and HTTP error code 404 02-09-2015 08:50:11.039 UTC Error hssconnection.cpp:593: Could not get subscriber data from HSS 02-09-2015 08:50:46.380 UTC Status load_monitor.cpp:237: Maximum incoming request rate/second increased to 943.146790 (based on a smoothed mean latency of 39420 and 0 upstream overload responses) My deployment definition lists below : home_domain=ccma.org sprout_hostname=100.64.119.89 hs_hostname=100.64.119.92:8888 hs_provisioning_hostname=100.64.119.92:8889 ralf_hostname=100.64.119.90:10888 xdms_hostname=100.64.119.91:7888 I appreciate any suggestion or direction. Best Wish :D , Nick 本信件可能包含工研院機密資訊，非指定之收件者，請勿使用或揭露本信件內容，並請銷毀此信件。 This email may contain confidential information. Please do not use or disclose it in any way and delete it if you are not the intended recipient.
_______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
