Thanks for the detailed response !

Re-running the python script on Ellis, it indicates that the 1000 numbers are 
already present in the database.

Ellis logs indicate "HTTP 599: Timeout" communicating with 
homer.clearwater.<domain> port 7888 and hs.clearwater.<domain> port 8888. The 
first issue here is that these do not exist in DNS. There are only 
homer.<domain> and hs.<domain>. I've added these variants to DNS, using the 
internal IP addresses. The timeout still persists. Telnet from Ellis to 
homer.clearwater.<domain> port 7888 succeeds. Telnet from Ellis to 
hs.clearwater.<domain> port 8888 succeeds.

Looking at the homer and homestead logs confirms that the requests are 
reaching, but there are no responses.

Also, is there an official way to stop /start the various services ? I may be 
missing it in the docs.

Thanks,
James



From: Matt Williams [mailto:[email protected]]
Sent: Friday, May 10, 2013 4:22 AM
To: Jackson, James; Jackson, James; clearwater at lists.projectclearwater.org
Subject: RE: incorrect signup code ?

James,

Well deduced - yes, you're right to use the "signup_key" specified in the 
configuration file during installation rather than "vby77rb7e".  I've fixed up 
the documentation - thanks for pointing this out.

On the "Failed to update server" error, there are two common reasons for this.


*         ellis not having any directory numbers to allocate - This can happen 
if the "python create_numbers.py" script (described at 
https://github.com/Metaswitch/clearwater-docs/wiki/Manual%20Install#ellis) 
failed or wasn't run.  It's safe to re-run, so it's probably worth trying it 
again, just in case.


*         ellis not being able to communicate with homer or homestead - This 
can happen if the domain name or IP address of homer or homestead is 
misconfigured on ellis, or if there is firewall configuration blocking traffic 
on ports 7888 or 8888.  It's worth double-checking your configuration but if 
there's nothing obviously wrong, the /var/log/ellis/ellis-0.log and 
/var/log/ellis/ellis-1.log files will report ellis's interactions with these 
servers and which server it's failing to communicate with.

If neither of these is the cause, it's possible that ellis is successfully 
sending a request to homer or homestead, but that homer or homestead is 
rejecting it.  The /var/log/ellis/ellis-*.log files mentioned above should 
point out which of homer or homestead is doing this.  Once you've established 
this, you can look at the /var/log/homestead/homestead-0.log or 
/var/log/homer/homer-0.log files for more information.  If this doesn't shed 
any light on the problem, please could you share the log files, and I'll take a 
look?

Thanks,

Matt

From: clearwater-bounces at 
lists.projectclearwater.org<mailto:clearwater-bounces at 
lists.projectclearwater.org> 
[mailto:[email protected]] On Behalf Of Jackson, 
James
Sent: 10 May 2013 05:33
To: ATT - James Jackson; clearwater at 
lists.projectclearwater.org<mailto:clearwater at lists.projectclearwater.org>
Subject: Re: [Clearwater] incorrect signup code ?

An API key was specified in a file during installation. Using that key allows 
the account to be created, but there's an error "Failed to update server" when 
trying to add a number.

From: clearwater-bounces at 
lists.projectclearwater.org<mailto:clearwater-bounces at 
lists.projectclearwater.org> 
[mailto:[email protected]] On Behalf Of Jackson, 
James
Sent: Thursday, May 09, 2013 10:43 PM
To: clearwater at lists.projectclearwater.org<mailto:clearwater at 
lists.projectclearwater.org>
Subject: [Clearwater] incorrect signup code ?

I've installed Clearwater (automated install) and I'm trying to setup an 
account as described here:

https://github.com/Metaswitch/clearwater-docs/wiki/Making%20your%20first%20call

It says to use signup code "vby77rb7e", but that comes back as an incorrect 
code.

What should we be using ?

Thanks,
James

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.projectclearwater.org/pipermail/clearwater/attachments/20130510/0323bd71/attachment.html>

Reply via email to