Hi Ariel,
It looks you are signed up to the mailing list with the address
[email protected] but the emails are coming from
[email protected], which is causing them to get blocked. Is it
possible to send mails from the address you have signed up with, or to sign up
with the address the mails are being sent from?
Onto the actual issue you've raised...
I've taken a look at the sprout logs. The REGISTER to extend the registration
(line 13172) has the following authorization header:
Authorization: Digest username="[email protected]",
realm="example.com", nonce="0c33c4666854eb37", uri="sip:example.com",
response="61412e9b2c9fab2dd0b55b7e63f2dc03", algorithm=MD5,
cnonce="gaN4CrWEQoVX", opaque="640d35d70302aea9", qop=auth,
nc=00000002,integrity-protected=ip-assoc-yes
- The integrity-protected parameter is added by bono. I has seen that the
REGISTER has come from an IP address and port that is currently REGISTERED. It
adds this parameter to tell sprout to trust the REGISTER and not challenge it.
However sprout ignores the parameter because the header contains a "response"
parameter. This is probably a sprout bug.
- Once sprout has decided to ignore the integrity-protected parameter it
checks the response, which fails. I think this is because MTS is re-using the
nonce (despite the fact it's incrementing the nonce count). Sprout does not
support this. This behaviour is not something we have seen in the clients we've
tested with - most clients just send a REGISTER without an Authorization
header, which is challenged just like the initial REGISTER.
I have raised https://github.com/Metaswitch/sprout/issues/833 to cover the fact
that sprout ignores the integrity-protected parameter.
Until this is fixed, you might be able to get your test working if you are able
to stop the MTS from sending credentials on its reREGISTER. I'm afraid we have
never tested with this tool, so I don't know if that's possible.
Hope this helps,
Alex.
-----Original Message-----
From: Ariel Otilibili-Anieli [mailto:[email protected]]
Sent: 27 October 2014 12:59
To: Alex Hockey; Eleanor Merry; [email protected]
Subject: Re: [Clearwater] Clearwater stays on "Please wait: Loading..."
Hi, Alex, thanks for the reminder,
I sent back a subscription to the mailing list, and received an e-mail saying
I'm already in the list. Can you, from your side, see that I'm in it?
Herewith are the logs from Sprout; you can see, in sprout_20141027T100000Z.txt,
that my client asks a REGISTER to Clearwater (line 12861), which is answered by
401 with the credentials of the digest (12926), to which the client sends
another REGISTER (12947); which is accepted by 200 OK (13084) and, to extend
the expiration time, the client says again REGISTER with the digest credentials
(13172). But, this time, Clearwater says
403 (request understood, but not processed; line 13273).
Thanks again for your help,
Ariel
On 10/24/2014 07:48 PM, Alex Hockey wrote:
> Hi Ariel,
>
> It's not immediately obvious to me what's causing this. The 403 response
> suggests an authentication issue (like a bad password) but you say you have
> successfully registered once. I'm not sure why the second attempt would fail.
>
> Would you be able to share your sprout logs? The logs are produced in
> /var/log/sprout/sprout*.txt. By default the logging level is set to log level
> 2, which only includes errors and very high level events. To enable debug
> logs, change the log level to 5 by writing log_level=5 to
> /etc/clearwater/user_settings (creating it if it doesn't exist already), and
> restart sprout (using service sprout stop - monit automatically restarts it).
>
> One final thing. I've noticed you're not signed up to the mailing
> list. This means that we have to manually verify your mail before it
> can be sent to the list. Would you be able to sign up to the mailing
> list please? You can sign up by following the link from here:
> http://www.projectclearwater.org/community/
>
> Thanks,
> Alex.
>
> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]] On Behalf Of
> Ariel Otilibili-Anieli
> Sent: 24 October 2014 13:32
> To: Eleanor Merry; [email protected]
> Subject: Re: [Clearwater] Clearwater stays on "Please wait: Loading..."
>
> Thanks for helping, Ellie, I could work it around, In /etc/clearwater/config
> I willingly put wrong IP addresses for Homestead, and restarted Homestead and
> Cassandra; then, put the right values back, and again restarted them. And it
> did work.
>
> Now I am across another problem; I use Multi-protocol test suite (MTS,
> a suite built for IP protocols, including SIP and Diameter; more on it
> here: http://mts.arm-tool.com/) and, using it as client, I ask a
> REGISTER (that goes fine: REGISTER to Clearwater, that answers 401
> with the credentials of the digest, to which MTS sends another
> REGISTER; which is accepted by 200 OK) and, to extend the expiration
> time, I ask it again with the digest credentials. But, this time,
> Clearwater says
> 403 (request understood, but not processed).
>
> I looked into the logs, and checked again the SIP passwords. I cannot find
> where is the problem.
>
>
>
> Could you, Ellie, help me on that?
> Kindest regards, and good afternoon.
>
> On 10/17/2014 09:43 PM, Eleanor Merry wrote:
>> Hi,
>>
>> Thanks for raising this!
>>
>> There are a couple of possible causes for this.
>>
>> The first is that the Homestead schema hasn't been properly installed. You
>> can check this by running "cqlsh -3", then "use homestead_cache;", and
>> finally "describe tables;" - this should report the impu, impi and
>> impi_mapping tables. If any of these steps fail (for example, because the
>> homestead_cache keyspace is missing), then you'll need to recreate they
>> keyspace. You can do this most simply by removing and reinstalling the
>> homestead package.
>>
>> The second is that there's a potential race condition when homestead-prov
>> starts up, which can mean it can't connect to Cassandra properly. Can you
>> check if cassandra is running correctly? You can check this by running
>> 'monit status', and getting the uptime of the Cassandra process.
>>
>> If it is still broken, then can you try stopping and starting the services?
>> You can do this by running the following commands:
>>
>> monit stop ellis
>> monit stop homestead-prov
>> monit stop cassandra
>> monit start cassandra
>>
>> (please then wait for cassandra to have fully restarted) monit start
>> homestead-prov monit start ellis
>>
>> Can you let me know if any of the above fixes it? We'll also look at fixing
>> this properly in the OVF.
>>
>> Thanks,
>>
>> Ellie
>>
>> -----Original Message-----
>> From: [email protected]
>> [mailto:[email protected]] On Behalf Of
>> Ariel Otilibili-Anieli
>> Sent: 10 October 2014 13:10
>> To: [email protected]
>> Subject: [Clearwater] Clearwater stays on "Please wait: Loading..."
>>
>> Hello,
>> I set up Clearwater on VMware ESXi (running upon Ubuntu 12.04.2 LTS,
>> GNU/Linux 3.5.0-23-generic x86_64) and, as I register a user by the webpage,
>> it keeps on displaying "Please wait: Loading..."
>>
>> Also, at the registration, it does not give back the SIP password, contrary
>> to the manual. Where should I look for? Where may the problem come from?
>>
>> Thanks a lot in advance.
>>
>> --
>> Ariel Otilibili Anieli
>> 55 route de Saint Antoine de Ginestière, 06200 Nice, France
>> +33 (0)6‒2811‒8730
>> _______________________________________________
>> Clearwater mailing list
>> [email protected]
>> http://lists.projectclearwater.org/listinfo/clearwater
>>
>
--
Ariel Otilibili Anieli
25 rue Robert Latouche - AB1437, 06200 Nice
+33 (0)6‒2811‒8730
_______________________________________________
Clearwater mailing list
[email protected]
http://lists.projectclearwater.org/listinfo/clearwater
