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 and sprout.us-west-2.compute.amazonaws.com 
domain names resolve to - is it the public or private IP addresses?

Thanks,

Matt

From: [email protected] 
[mailto:[email protected]] On Behalf Of B Ray
Sent: 24 May 2013 04:20
To: [email protected]
Subject: [Clearwater] registration failure err=171023

Getting closer with a registration.  Seeing this in the bono logs.
24-05-2013 03: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:06:23.545 Status connection_pool.cpp:   connections = 50, recycle 
time = 600 seconds
24-05-2013 03:09:19.114 Status stack.cpp: Listening on port 5058
24-05-2013 03:09:19.116 Status stack.cpp: Listening on port 5060
24-05-2013 03:09:19.117 Status stack.cpp: Local host aliases:
24-05-2013 03: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:09:19.117 Status stack.cpp:  10.254.52.157
24-05-2013 03:09:19.117 Status stack.cpp:  127.0.0.1
24-05-2013 03:09:19.117 Status stack.cpp:  localhost
24-05-2013 03:09:19.117 Status stack.cpp:  54.214.142.56
24-05-2013 03:09:19.118 Status main.cpp: Using local store
24-05-2013 03: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

Reply via email to