Hi Ken, This sounds like the terminating user isn't registered, so the call is rejected with a 480.
Can you check that the Homestead nodes have been clustered correctly? If you run 'nodetool status' on each homestead node I'd expect you to see both Homestead nodes owning 100%, roughly equal load and in the UN state. Can you also check the Sprout clustering? Each Sprout node should have the file /etc/clearwater/cluster_settings, and it should have a single line of the form "servers=<Sprout-1 IP address:11211>,<Sprout-2 IP address:11211>,...". The order of the Sprouts should be identical between the Sprout nodes. If these are OK, then can you please send the logs (for a single call attempt) as well? Thanks, Ellie -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Antonio Ken Iannillo Sent: 02 December 2014 11:30 To: [email protected] Subject: [Clearwater] 480 Temporarily Unavailable Dear All, Dear Eleonor, I resolve the previous problem, thought I think it just needed time for the dns name propagation. However I came up with another issue that is, after the first INVITE and the 100 response, the reception of an unexpected message. 480 Temporarily Unavailable This is totally random and it is not associated to a particular user. In the deployment there are two copy of each node (but Ellis) on two different servers. In the log of the sprout nodes I found that - sprout node gets the state registered in hs for user 2010000001 - memcached fetches result for key reg\\sip:2010000001@..., CAS=9828 - data store returns the record - then scscf (from sproutletproxy) send the 408 response Thanks for your help, Ken _______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/listinfo/clearwater _______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/listinfo/clearwater
