Thanks for your response. Are the multiple Via lines all from the same node, or from different nodes? Which nodes are they from?
You provided the /etc/clearwater/config from bono - please can you confirm that (apart from the Local IP configuration section), the sprout config file is exactly the same? With regard to public or private IP addresses, * home_domain (us-west-2.compute.amazonaws.com) should resolve to the public IP address of bono (only required from outside your deployment) * sprout_hostname (sprout.us-west-2.compute.amazonaws.com) should resolve to the private IP address of sprout * public_hostname (bono.us-west-2.compute.amazonaws.com) must be a "split-horizon" DNS for bono - it should resolve to the public IP address when accessed from outside your deployment and the private IP address when inside. This is documented at https://github.com/Metaswitch/clearwater-docs/wiki/Clearwater%20DNS%20Usage). Note that you have a "bono_hostname" definition in your /etc/clearwater/config file, but I don't believe we use that - I can't see it in our docs. Note also that we haven't tested Clearwater deployed without any DNS (as you're trying to do). In particular, * you'll need to be able to resolve home_domain and public_hostname from your SIP phone - you might be able to set up /etc/hosts on your SIP phone as well - it depends on what platform you're running on * we need DNS for split horizon function - you might be better setting public_hostname to be ec2-54-214-142-56.compute.amazonaws.com (or whatever the Amazon-assigned DNS entry is) as this is inherently split horizon - I'll look at improving our documentation to make this clear. If it's possible to set up proper DNS (e.g. using Amazon's Route 53 service), I think you'll find it easier. Matt ________________________________ From: [email protected] [[email protected]] on behalf of B Ray [[email protected]] Sent: 24 May 2013 16:20 To: [email protected] Subject: Re: [Clearwater] registration failure err=171023 There does appear to be a loop in the messages, multiple via lines etc. I can have the system names resolve to either public or private IPs, depending on what I put in the hosts files. Which is required? The config file from bono is this: # Deployment definitions home_domain=us-west-2.compute.amazonaws.com<http://us-west-2.compute.amazonaws.com> sprout_hostname=sprout.us-west-2.compute.amazonaws.com<http://sprout.us-west-2.compute.amazonaws.com> hs_hostname=hs.us-west-2.compute.amazonaws.com:8888<http://hs.us-west-2.compute.amazonaws.com:8888> xdms_hostname=homer.us-west-2.compute.amazonaws.com:7888<http://homer.us-west-2.compute.amazonaws.com:7888> bono_hostname=bono.us-west-2.compute.amazonaws.com<http://bono.us-west-2.compute.amazonaws.com> mmonit_hostname=localhost mmonit_username= mmonit_password= # Local IP configuration local_ip=10.254.52.157 public_ip=54.214.142.56 public_hostname=bono.us-west-2.compute.amazonaws.com<http://bono.us-west-2.compute.amazonaws.com> # Email server configuration smtp_smarthost= smtp_username= smtp_password= [email protected]<mailto:[email protected]> I'm glad to hear that's got past the previous problem. The error messages we're now seeing only occur if the SIP message we're trying to send is over 4k long. Presumably you're not sending unusually-long REGISTER messages into bono? The common reason for getting long SIP messages is if there is a routing loop - e.g. if bono thinks its connecting to sprout but DNS actually resolves back to itself. The easiest way to debug this is to get low-level trace from bono and sprout. To do this, create a file called /etc/clearwater/user_settings containing the single line "log_level=5". This overrides the default log level (of 2) and gives you much more detailed output in /var/log/bono/sprout*.log and /var/log/sprout/sprout*.log. I'd suggest doing this on both boxes. It would also be useful to see your /etc/clearwater/config files on bono and sprout (although obviously redact the secrets at the end), and what your bono.us-west-2.compute.amazonaws.com<http://bono.us-west-2.compute.amazonaws.com> and sprout.us-west-2.compute.amazonaws.com<http://sprout.us-west-2.compute.amazonaws.com> domain names resolve to - is it the public or private IP addresses? Thanks, Matt On Thu, May 23, 2013 at 10:19 PM, B Ray <[email protected]<mailto:[email protected]>> wrote: Getting closer with a registration. Seeing this in the bono logs. 24-05-2013 03<tel:24-05-2013%2003>:06:23.545 Status connection_pool.cpp: Creating connection pool to sprout.us-west-2.compute.am<http://sprout.us-west-2.compute.am> azonaws.com:5058<http://azonaws.com:5058> 24-05-2013 03<tel:24-05-2013%2003>:06:23.545 Status connection_pool.cpp: connections = 50, recycle time = 600 seconds 24-05-2013 03<tel:24-05-2013%2003>:09:19.114 Status stack.cpp: Listening on port 5058 24-05-2013 03<tel:24-05-2013%2003>:09:19.116 Status stack.cpp: Listening on port 5060 24-05-2013 03<tel:24-05-2013%2003>:09:19.117 Status stack.cpp: Local host aliases: 24-05-2013 03<tel:24-05-2013%2003>:09:19.117 Status stack.cpp: bono.us-west-2.compute.amazonaws.com<http://bono.us-west-2.compute.amazonaws.com> 24-05-2013 03<tel:24-05-2013%2003>:09:19.117 Status stack.cpp: 10.254.52.157 24-05-2013 03<tel:24-05-2013%2003>:09:19.117 Status stack.cpp: 127.0.0.1 24-05-2013 03<tel:24-05-2013%2003>:09:19.117 Status stack.cpp: localhost 24-05-2013 03<tel:24-05-2013%2003>:09:19.117 Status stack.cpp: 54.214.142.56 24-05-2013 03<tel:24-05-2013%2003>:09:19.118 Status main.cpp: Using local store 24-05-2013 03<tel:24-05-2013%2003>:09:19.118 Status connection_pool.cpp: Creating connection pool to sprout.us-west-2.compute.am<http://sprout.us-west-2.compute.am> azonaws.com:5058<http://azonaws.com:5058> 24-05-2013 03:09:19.118 Status connection_pool.cpp: connections = 50, recycle time = 600 seconds 24-05-2013 03:10:28.431 Warning pjsip: tsx0x7f5114218 Temporary failure in sending Request msg REGISTER/cse q=1 (tdta0x7f51142129a0), will try next server: Message too long (PJSIP_EMSGTOOLONG) 24-05-2013 03:10:28.431 Warning pjsip: tsx0x7f5114218 Failed to send Request msg REGISTER/cseq=1 (tdta0x7f5 1142129a0)! err=171023 (Message too long (PJSIP_EMSGTOOLONG)) 24-05-2013 03:13:42.139 Warning pjsip: tsx0x7f5114215 Temporary failure in sending Request msg REGISTER/cse q=1 (tdta0x7f511420fbf0), will try next server: Message too long (PJSIP_EMSGTOOLONG) 24-05-2013 03:13:42.139 Warning pjsip: tsx0x7f5114215 Failed to send Request msg REGISTER/cseq=1 (tdta0x7f5 11420fbf0)! err=171023 (Message too long (PJSIP_EMSGTOOLONG)) 24-05-2013 03:15:39.011 Warning pjsip: tsx0x7f5114215 Temporary failure in sending Request msg REGISTER/cse q=1 (tdta0x7f511420fd70), will try next server: Message too long (PJSIP_EMSGTOOLONG) 24-05-2013 03:15:39.011 Warning pjsip: tsx0x7f5114215 Failed to send Request msg REGISTER/cseq=1 (tdta0x7f5 11420fd70)! err=171023 (Message too long (PJSIP_EMSGTOOLONG))
_______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/listinfo/clearwater
