Des,

Yes, that config looks correct.  A few questions...

*         Is sprout running ("ps -eaf | grep sprout")?

*         Has it opened port 5054 ("sudo netstat -anp | grep :5054")?

*         If so, do you see anything in sprout's logs?

Please let me know.

Matt

From: [email protected] 
[mailto:[email protected]] On Behalf Of Des Hartman
Sent: 26 June 2013 09:01
To: [email protected]
Subject: Re: [Clearwater] Client REGISTER gets 405 error

Is this correct:


Bono

DAEMON_ARGS="--system $NAME@$public_hostname --domain $home_domain --localhost 
$public_hostname --alias $public_ip --trusted-port 5058 --untrusted-port 5060 
--edge-proxy 
$sprout_hostname:5054:$upstream_connections:$upstream_recycle_connections --sas 
$sas_server --pjsip-threads $num_pjsip_threads --worker-threads 
$num_worker_threads -a $log_directory -F $log_directory -L $log_level"

Sprout

 DAEMON_ARGS="--system $NAME@$public_hostname --domain $home_domain --localhost 
$public_hostname --sprout-domain $sprout_hostname --alias 
$sprout_hostname,$public_ip --trusted-port 5054 --auth $auth_type --realm 
$home_domain --memstore $memcached_servers --hss $hs_hostname --xdms 
$xdms_hostname --enum $enum_server $enum_suffix_arg $enum_file_arg --sas 
$sas_server --pjsip-threads $num_pjsip_threads --worker-threads 
$num_worker_threads -a $log_directory -F $log_directory -L $log_level"


If it is, then something else is wrong, because I am getting a HUGE amount of 
connection refused in the log

22-06-2013 07:35:21.575 Verbose pjsip: tcpc0x7fea2003 TCP client transport 
created
22-06-2013 07:35:21.575 Verbose pjsip: tcpc0x7fea2003 TCP transport 
172.16.6.170:42957 is connecting to 172.16.6.170:5054...
22-06-2013 07:35:21.575 Debug connection_pool.cpp:229: Created transport 
tcpc0x7fea20031788 in slot 2224 (172.16.6.170:42957 to 172.16.6.170:5054)
22-06-2013 07:35:21.576 Verbose pjsip: tcpc0x7fea2023 TCP client transport 
created
22-06-2013 07:35:21.576 Verbose pjsip: tcpc0x7fea2023 TCP transport 
172.16.6.170:59828 is connecting to 172.16.6.170:5054...
22-06-2013 07:35:21.576 Debug connection_pool.cpp:229: Created transport 
tcpc0x7fea2023feb8 in slot 2225 (172.16.6.170:59828 to 172.16.6.170:5054)
22-06-2013 07:35:21.576 Verbose pjsip: tcpc0x7fea2024 TCP client transport 
created
22-06-2013 07:35:21.576 Verbose pjsip: tcpc0x7fea2024 TCP transport 
172.16.6.170:39584 is connecting to 172.16.6.170:5054...
22-06-2013 07:35:21.576 Debug connection_pool.cpp:229: Created transport 
tcpc0x7fea202424c8 in slot 2226 (172.16.6.170:39584 to 172.16.6.170:5054)
22-06-2013 07:35:21.576 Verbose pjsip: tcpc0x7fea2024 TCP client transport 
created
22-06-2013 07:35:21.576 Verbose pjsip: tcpc0x7fea2024 TCP transport 
172.16.6.170:47708 is connecting to 172.16.6.170:5054...
22-06-2013 07:35:21.576 Debug connection_pool.cpp:229: Created transport 
tcpc0x7fea20244ad8 in slot 2227 (172.16.6.170:47708 to 172.16.6.170:5054)
22-06-2013 07:35:21.577 Verbose pjsip: tcpc0x7fea2024 TCP client transport 
created
22-06-2013 07:35:21.577 Verbose pjsip: tcpc0x7fea2024 TCP transport 
172.16.6.170:43165 is connecting to 172.16.6.170:5054...
22-06-2013 07:35:21.577 Debug connection_pool.cpp:229: Created transport 
tcpc0x7fea202470e8 in slot 2228 (172.16.6.170:43165 to 172.16.6.170:5054)
22-06-2013 07:35:21.577 Verbose pjsip: tcpc0x7fea200e TCP client transport 
created
22-06-2013 07:35:21.577 Verbose pjsip: tcpc0x7fea200e TCP transport 
172.16.6.170:57200 is connecting to 172.16.6.170:5054...
22-06-2013 07:35:21.577 Debug connection_pool.cpp:229: Created transport 
tcpc0x7fea200e7d08 in slot 2229 (172.16.6.170:57200 to 172.16.6.170:5054)
22-06-2013 07:35:21.577 Verbose pjsip: tcpc0x7fea200e TCP client transport 
created
22-06-2013 07:35:21.577 Verbose pjsip: tcpc0x7fea200e TCP transport 
172.16.6.170:43269 is connecting to 172.16.6.170:5054...
22-06-2013 07:35:21.577 Debug connection_pool.cpp:229: Created transport 
tcpc0x7fea200ea318 in slot 2230 (172.16.6.170:43269 to 172.16.6.170:5054)
22-06-2013 07:35:21.578 Verbose pjsip: tcpc0x7fea200e TCP client transport 
created
22-06-2013 07:35:21.578 Error pjsip: tcpc0x7fea200b TCP connect() error: 
Connection refused [code=120111]
22-06-2013 07:35:21.578 Debug connection_pool.cpp:320: Transport 
tcpc0x7fea200b3c88 in slot 2109 has failed
22-06-2013 07:35:21.578 Verbose pjsip: tcpc0x7fea200e TCP transport 
172.16.6.170:40562 is connecting to 172.16.6.170:5054...
22-06-2013 07:35:21.578 Error pjsip: tcpc0x7fea203f TCP connect() error: 
Connection refused [code=120111]
22-06-2013 07:35:21.578 Debug connection_pool.cpp:320: Transport 
tcpc0x7fea203fb4e8 in slot 2110 has failed
22-06-2013 07:35:21.578 Error pjsip: tcpc0x7fea201b TCP connect() error: 
Connection refused [code=120111]
22-06-2013 07:35:21.578 Debug connection_pool.cpp:320: Transport 
tcpc0x7fea201bd748 in slot 2111 has failed
22-06-2013 07:35:21.578 Error pjsip: tcpc0x7fea200a TCP connect() error: 
Connection refused [code=120111]
22-06-2013 07:35:21.578 Debug connection_pool.cpp:320: Transport 
tcpc0x7fea200a1068 in slot 2112 has failed
22-06-2013 07:35:21.578 Error pjsip: tcpc0x7fea2022 TCP connect() error: 
Connection refused [code=120111]
22-06-2013 07:35:21.578 Debug connection_pool.cpp:320: Transport 
tcpc0x7fea20220cf8 in slot 2113 has failed
22-06-2013 07:35:21.578 Error pjsip: tcpc0x7fea2027 TCP connect() error: 
Connection refused [code=120111]
22-06-2013 07:35:21.578 Debug connection_pool.cpp:320: Transport 
tcpc0x7fea20271e78 in slot 2114 has failed
22-06-2013 07:35:21.578 Error pjsip: tcpc0x7fea2027 TCP connect() error: 
Connection refused [code=120111]
22-06-2013 07:35:21.578 Debug connection_pool.cpp:320: Transport 
tcpc0x7fea202790a8 in slot 2115 has failed
22-06-2013 07:35:21.578 Error pjsip: tcpc0x7fea202a TCP connect() error: 
Connection refused [code=120111]
22-06-2013 07:35:21.578 Debug connection_pool.cpp:320: Transport 
tcpc0x7fea202a6258 in slot 2116 has failed
22-06-2013 07:35:21.578 Error pjsip: tcpc0x7fea201d TCP connect() error: 
Connection refused [code=120111]
22-06-2013 07:35:21.578 Debug connection_pool.cpp:320: Transport 
tcpc0x7fea201d25a8 in slot 2117 has failed
22-06-2013 07:35:21.578 Error pjsip: tcpc0x7fea2024 TCP connect() error: 
Connection refused [code=120111]
22-06-2013 07:35:21.578 Debug connection_pool.cpp:320: Transport 
tcpc0x7fea2024d918 in slot 2118 has failed
22-06-2013 07:35:21.578 Error pjsip: tcpc0x7fea2020 TCP connect() error: 
Connection refused [code=120111]
22-06-2013 07:35:21.578 Debug connection_pool.cpp:320: Transport 
tcpc0x7fea2020ed68 in slot 2119 has failed
22-06-2013 07:35:21.578 Error pjsip: tcpc0x7fea201f TCP connect() error: 
Connection refused [code=120111]
22-06-2013 07:35:21.578 Debug connection_pool.cpp:320: Transport 
tcpc0x7fea201f3808 in slot 2120 has failed
22-06-2013 07:35:21.578 Error pjsip: tcpc0x7fea2012 TCP connect() error: 
Connection refused [code=120111]
22-06-2013 07:35:21.578 Debug connection_pool.cpp:320: Transport 
tcpc0x7fea2012ca68 in slot 2121 has failed


Thanks
Des Hartman

From: Matt Williams 
<[email protected]<mailto:[email protected]>>
Date: Wednesday, 26 June 2013 5:37 PM
To: 
"[email protected]<mailto:[email protected]>"
 
<[email protected]<mailto:[email protected]>>
Subject: Re: [Clearwater] Client REGISTER gets 405 error

Des,

Glad to hear you've got your installation upgraded OK.  In case you haven't 
already, note that you'll have to upgrade ellis, homer and homestead as well as 
bono and sprout.

The changes you've made are almost correct.  You've changed the 
"--trusted-port" value on bono as well as sprout - you should actually only 
change this on sprout.  To fix this, you'll need to change your bono file back 
to "--trusted-port 5058".

What we're trying to do here is configure

*         bono to listen on untrusted port 5060 (as it always did)

*         bono to listen on trusted port 5058 (as it always did)

*         sprout to listen on trusted port 5054 (via the --trusted-port 
parameter on sprout)

*         bono to connect to sprout on port 5054 (via the --edge-proxy 
parameter on bono)

*         (sprout will connect back to bono on port 5058 because bono will tell 
it to do so over SIP).
Does that make sense?

Please let me know how you get on.

Thanks,

Matt

From: 
[email protected]<mailto:[email protected]>
 [mailto:[email protected]] On Behalf Of Des 
Hartman
Sent: 26 June 2013 01:12
To: 
[email protected]<mailto:[email protected]>
Subject: Re: [Clearwater] Client REGISTER gets 405 error

Matt,

Changed to latest, did the update, changed the two files to 5054, but still get 
this in monit. Looks like there is still a reference to 5058 somewhere?

Here are my changes in bono and sprout

"DAEMON_ARGS="--system $NAME@$public_hostname --domain $home_domain --localhost 
$public_hostname --alias $public_ip --trusted-port 5054 --untrusted-port 5060 
--edge-proxy 
$sprout_hostname:5054:$upstream_connections:$upstream_recycle_connections --sas 
$sas_server --pjsip-threads $num_pjsip_threads --worker-threads 
$num_worker_threads -a $log_directory -F $log_directory -L $log_level""

"DAEMON_ARGS="--system $NAME@$public_hostname --domain $home_domain --localhost 
$public_hostname --sprout-domain $sprout_hostname --alias 
$sprout_hostname,$public_ip --trusted-port 5054 --auth $auth_type --realm 
$home_domain --memstore $memcached_servers --hss $hs_hostname --xdms 
$xdms_hostname --enum $enum_server $enum_suffix_arg $enum_file_arg --sas 
$sas_server --pjsip-threads $num_pjsip_threads --worker-threads 
$num_worker_threads -a $log_directory -F $log_directory -L $log_level""


Error I get

Process 'bono'
  status                            Connection failed
  monitoring status                 Monitored
  pid                               0
  parent pid                        0
  uptime                            0m
  children                          0
  memory kilobytes                  0
  memory kilobytes total            0
  memory percent                    0.0%
  memory percent total              0.0%
  cpu percent                       0.0%
  cpu percent total                 0.0%
  port response time                0.000s to 
localhost:5058monit@localhost:5058 [SIP via TCP]
  data collected                    Sat, 22 Jun 2013 09:33:13


Thanks
Des Hartman

From: Matt Williams 
<[email protected]<mailto:[email protected]>>
Date: Wednesday, 26 June 2013 3:05 AM
To: 
"[email protected]<mailto:[email protected]>"
 
<[email protected]<mailto:[email protected]>>
Subject: Re: [Clearwater] Client REGISTER gets 405 error

sudo service clearwater-infrastructure restart
_______________________________________________
Clearwater mailing list
[email protected]
http://lists.projectclearwater.org/listinfo/clearwater

Reply via email to