On further examination I am finding that there are different versions
numbers.
 
Non-working installation:
[cw-aio]ubuntu@ims:~$ apt-show-versions sprout
sprout/binary uptodate 1.0-131206.162136

Working installation:
[cw-aio]ubuntu@ims:~$ apt-show-versions sprout
sprout/binary upgradeable from 1.0-131120.153946 to 1.0-131206.162136

It also appears that I can not install a specific version

[cw-aio]ubuntu@ims:~$ sudo DEBIAN_FRONTEND=noninteractive apt-get install
ellis=1.0-131113.121129 --yes -V
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Version '1.0-131113.121129' for 'ellis' was not found


Kevin Heath High
Solution Architect
Tropo, Inc.


From:  Kevin High <[email protected]>
Date:  Sunday, December 15, 2013 at 11:30 PM
To:  <[email protected]>
Subject:  Two identical installations with two different configurations.

I just did two manual installations of Clearwater on one AWS instances on
two different AWS accounts and in two different regions.

The first installation I did on Nov 20th worked wonderfully with the only
exception was that for some reason Clearwater added a line in /etc/hosts
resolving the external hostname to the internal address, which conflicted
with the public hostname setting in /etc/clearwater/config causing the
Contact header to have the wrong IP ­ once I changed the
/etc/clearwater/config to point to the public IP address, then it worked
perfectly and continues to work.

The second installation I did on Dec 6th appears to be setup correctly, but
I am not able to connect the call.  Looking  at the traces the ACK that
would notify the callee that it has successfully answered the phone is not
going back to the client.  Instead it appears to be being sent back to
sprout.  Looking at the Route headers for (comparing against the working
installation) there is an extra Route header for sprout.

On further examination, the processes between the two different
installations also have different sets of parameters being passed, and this
is reflective in the bono init scripts /etc/init.d/bono

These are the parameters for the working installation.  Though it is
perplexing that the sprout ‹public-host parameter has the private ip as the
value  (domain names and ip address redacted on purpose).

bono     27814  0.2  0.5 1092848 45072 ?       Sl   Dec13  10:35
/usr/share/clearwater/bin/bono
--system bono@<first install public ip>
--domain <first install domain>
--localhost <first install private ip>
--public-host <first install public ip>
--alias <first install public ip>
--trusted-port 5058
--untrusted-port 5060
--edge-proxy sprout.<first install domain>:5054:50:600
--sas 0.0.0.0
--pjsip-threads 1
--worker-threads 2 -a /var/log/bono -F /var/log/bono -L 5
--ibcf <first install public ip>
--bono-domain bono.<first install domain>
sprout   27853  0.2  1.0 2124192 83364 ?       Sl   Dec13  10:27
/usr/share/clearwater/bin/sprout
--system sprout@<first install public ip>
--domain <first install domain>
--localhost <first install private ip>
--public-host <first install private ip>
--sprout-domain sprout.<first install domain>
--alias sprout.<first install domain>
--trusted-port 5054
--realm <first install domain>
--memstore /etc/clearwater/cluster_settings
--hss hs.<first install domain>:8888
--xdms homer.<first install domain>:7888
--sas 0.0.0.0
--pjsip-threads 1
--worker-threads 100 -a /var/log/sprout -F /var/log/sprout -L 5

These are the parameters for the non-working installation

bono      1238  0.2  0.2 1240344 42792 ?       Sl   20:28   0:06
/usr/share/clearwater/bin/bono
--system bono@<second install public ip>
--domain <second install domain>
--localhost <second install private ip>
--public-host <second install public ip>
--alias <second install public ip>
--trusted-port 5058
--untrusted-port 5060
--webrtc-port 5062
--routing-proxy sprout.<second install domain>:5054:50:600
--sas 0.0.0.0
--pjsip-threads 1
--worker-threads 4 -a /var/log/bono -F /var/log/bono -L 5
sprout    2747  0.3  0.4 4008468 63376 ?       Sl   20:51   0:03
/usr/share/clearwater/bin/sprout
--system sprout@<second install public ip>
--domain <second install domain>
--localhost <second install private ip>
--public-host <second install private ip>
--sprout-domain sprout.<second install domain>
--alias sprout.<second install domain>
--trusted-port 5054
--realm <second install domain>
--memstore /etc/clearwater/cluster_settings
--hss hs.<second install domain>:8888
--xdms homer.<second install domain>:7888
--sas 0.0.0.0
--pjsip-threads 1
--worker-threads 200
--record-routing-model pcscf
--authentication -a /var/log/sprout -F /var/log/sprout -L 5

No idea why the same install would have completely different settings.  Nor
any idea if it is even related to the extra route header.

Any insight into my issue would be helpful.

Thanks
Kevin

Kevin Heath High
Solution Architect
Tropo, Inc.



_______________________________________________
Clearwater mailing list
[email protected]
http://lists.projectclearwater.org/listinfo/clearwater

Reply via email to