[Project Clearwater] hello
I have recently installed clearwater folloiwng the manual installation instructions on 7 virtual machines running ubuntu. After installation and running the machines i tried to sign in using zoiper application but i recieved 403 forbidden response through wireshark traces so i tried to check each node i found that the homestead node status is not running and the current log ( var/log/homestead/homestead_current.txt ) of node shows that : - 08-03-2017 10:19:25.525 UTC Status load_monitor.cpp:105: Constructing LoadMonitor 08-03-2017 10:19:25.525 UTC Status load_monitor.cpp:106:Target latency (usecs) : 10 08-03-2017 10:19:25.525 UTC Status load_monitor.cpp:107:Max bucket size : 1000 08-03-2017 10:19:25.525 UTC Status load_monitor.cpp:108:Initial token fill rate/s: 100.00 08-03-2017 10:19:25.525 UTC Status load_monitor.cpp:109:Min token fill rate/s: 10.00 08-03-2017 10:19:25.525 UTC Status dnscachedresolver.cpp:150: Creating Cached Resolver using servers: 08-03-2017 10:19:25.525 UTC Status dnscachedresolver.cpp:160: 127.0.0.1 08-03-2017 10:19:25.525 UTC Status a_record_resolver.cpp:54: Created ARecordResolver 08-03-2017 10:19:25.525 UTC Status a_record_resolver.cpp:54: Created ARecordResolver 08-03-2017 10:19:25.525 UTC Status cassandra_store.cpp:181: Configuring store connection 08-03-2017 10:19:25.525 UTC Status cassandra_store.cpp:182: Hostname: 127.0.0.1 08-03-2017 10:19:25.525 UTC Status cassandra_store.cpp:183: Port: 9160 08-03-2017 10:19:25.525 UTC Status cassandra_store.cpp:211: Configuring store worker pool 08-03-2017 10:19:25.525 UTC Status cassandra_store.cpp:212: Threads: 10 08-03-2017 10:19:25.525 UTC Status cassandra_store.cpp:213: Max Queue: 0 08-03-2017 10:19:25.526 UTC Error main.cpp:756: Failed to initialize the Cassandra cache with error code 1. 08-03-2017 10:19:25.526 UTC Status main.cpp:757: Homestead is shutting down and the file "/var/log/homestead/homestead_err.log" contains -- TSocket::open() error on socket (after THRIFT_POLL) Port: 9160>Connection refused -- although the cassandra is running but the schemas created by homestead (homestead_cache) seems to be doesnot exist so could you please sent me these scripts ___ Clearwater mailing list Clearwater@lists.projectclearwater.org http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
Re: [Project Clearwater] Sprout and third-party registrations
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 behaviour, for an AS which is contacted on TCP, using SRV records, with a domain name of "sample-as.test", sending on all registration types, and including as much information as possible. 0 0 0 0 REGISTER 0 1 2 sip:sample-as.test;transport=TCP 0 Richard From: Clearwater [mailto:clearwater-boun...@lists.projectclearwater.org] On Behalf Of Jake Brown Sent: 02 March 2017 04:08 To: clearwater@lists.projectclearwater.org Subject: [Project Clearwater] Sprout and third-party registrations I am looking for a IFC example that would induce the behavior described in the manual where the S-CSCF would pass a third party registration onto an AS: >From the online manual: AS invocation also occurs on REGISTER - this is called third-party registration (3GPP TS 24.229 s5.4.1.7 and 7A): * When a UE registers with Sprout, if the iFCs require it, it passes a third-party registration onto an AS. * Message body handling for third-party registration, per 3GPP TS 24.229 s5.4.1.7A: including optionally service info, a copy of the registration, and a copy of the response. * Network-initiated deregister. If the third-party registration fails and the iFC requests it, we must deregister the UE. Thank You Jake ___ Clearwater mailing list Clearwater@lists.projectclearwater.org http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
Re: [Project Clearwater] About Clearwater Register Processing
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 receives the REGISTER request, it gets authentication data from Homestead over HTTP, and then Sprout uses the authorization data on the REGISTER to allow/forbid the user. The full flow for a REGISTER can be seen in the “Mainline Flows” section here: http://www.projectclearwater.org/technical/call-flows/ I hope that helps, Seb. From: Clearwater [mailto:clearwater-boun...@lists.projectclearwater.org] On Behalf Of ??? Sent: 08 March 2017 08:29 To: clearwater@lists.projectclearwater.org Subject: [Project Clearwater] About Clearwater Register Processing Dear All, I have some questions about Clearwater Register flow between Homestead and Sprout, according to http://www.projectclearwater.org/technical/clearwater-architecture/, I find the following descriptions, Sprout The Sprout nodes act as a horizontally scalable, combined SIP registrar and authoritative routing proxy, and handle client authentication. The Sprout cluster includes a redundant memcached cluster storing client registration data and other long-lived state. Homestead Homestead provides a Web services interface to Sprout for retrieving authentication credentials and user profile information. So, Homestead is just a interface between Sprout and HSS to help Sprout get user profile from HSS ,and doesn't process message for client authentication? The mainly component being charged of authentication is Sprout? I had set icscf with Sprout, called sprout(i), and when I use wireshark capture the packets of registration, I find that packets didn't pass through Sprout cluster, and just pass through my sprout(i). Does my sprout(i) deal with user authentication or the homestead do? Thanks, Eric ___ Clearwater mailing list Clearwater@lists.projectclearwater.org http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
[Project Clearwater] About Clearwater Register Processing
Dear All, I have some questions about Clearwater Register flow between Homestead and Sprout, according to http://www.projectclearwater.org/technical/clearwater-architecture/, I find the following descriptions, Sprout The Sprout nodes act as a horizontally scalable, combined SIP registrar and authoritative routing proxy, and handle client authentication. The Sprout cluster includes a redundant memcached cluster storing client registration data and other long-lived state. Homestead Homestead provides a Web services interface to Sprout for retrieving authentication credentials and user profile information. So, Homestead is just a interface between Sprout and HSS to help Sprout get user profile from HSS ,and doesn't process message for client authentication? The mainly component being charged of authentication is Sprout? I had set icscf with Sprout, called sprout(i), and when I use wireshark capture the packets of registration, I find that packets didn't pass through Sprout cluster, and just pass through my sprout(i). Does my sprout(i) deal with user authentication or the homestead do? Thanks, Eric ___ Clearwater mailing list Clearwater@lists.projectclearwater.org http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
