Hi Masood,

It looks like Sprout is sending x-lite a ‘404 – No route to target’ response:

--start msg--

SIP/2.0 404 No route to target
Via: SIP/2.0/TCP 
192.168.211.12:52287;rport=52287;received=192.168.211.12;branch=z9hG4bKPjO61SVsPgGy3JNZ5GjcfAhUGhue.Rt-lt
Via: SIP/2.0/UDP 
192.168.2.18:59190;rport=59190;received=192.168.2.18;branch=z9hG4bK-524287-1---1a816c6de2183a5e
Call-ID: 79961MzZiMGM4MWUwMmZlOTljMTljN2FhNDk5OWI2NjBmNzM
From: "2010000006" <sip:[email protected]>;tag=961aa033
To: "2010000006" 
<sip:[email protected]>;tag=z9hG4bKPjO61SVsPgGy3JNZ5GjcfAhUGhue.Rt-lt
CSeq: 2 REGISTER
Content-Length:  0

--end msg--

I think the tell-tale logs are the following:

28-04-2016 11:46:06.672 UTC Debug sproutletproxy.cpp:124: Find target Sproutlet 
for request
28-04-2016 11:46:06.672 UTC Debug sproutletproxy.cpp:163: Found next routable 
URI: sip:sprout.xflowims.com:5054;transport=TCP;lr;orig
28-04-2016 11:46:06.672 UTC Debug sproutletproxy.cpp:334: Possible service name 
- sprout
28-04-2016 11:46:06.672 UTC Debug sproutletproxy.cpp:340: Hostname - 
xflowims.com
28-04-2016 11:46:06.672 UTC Debug sproutletproxy.cpp:334: Possible service name 
- sprout
28-04-2016 11:46:06.672 UTC Debug sproutletproxy.cpp:340: Hostname - 
xflowims.com
28-04-2016 11:46:06.672 UTC Debug sproutletproxy.cpp:334: Possible service name 
- sprout
28-04-2016 11:46:06.672 UTC Debug sproutletproxy.cpp:340: Hostname - 
xflowims.com
28-04-2016 11:46:06.672 UTC Debug sproutletproxy.cpp:195: No Sproutlet found 
using service name or host
28-04-2016 11:46:06.672 UTC Debug sproutletproxy.cpp:201: Find default service 
for port 5054
28-04-2016 11:46:06.672 UTC Verbose sproutletproxy.cpp:1159: Created Sproutlet 
bgcf-0x7efd9c066a40 for Request msg REGISTER/cseq=2 (tdta0x7efd9c06fe00)

Sprout is attempting to figure out which service it needs to apply to your 
register messge: I-CSCF, S-CSCF, or BGCF. It does that by looking at the URI 
sip:sprout.xflowims.com:5054;transport=TCP;lr;orig, and trying to find a 
sproutlet which is configured to handle requests to that URI. Your URI doesn’t 
match one of the configured sproutlet URIs, so it tries to match on the port. 
The first sproutlet that it finds running on port 5054 is the BGCF sproutlet, 
so it sends the request to the BGCF. The BGCF can’t route this request, so it 
sends a 404 response.

This behaviour has changed recently, and there are some changes that you will 
need to make to your shared configuration to allow your subscribers to register.

  *   Remove the scscf_uri setting from /etc/clearwater/shared_config, and run 
/usr/share/clearwater/clearwater-config-manager/upload_shared_config to 
propagate this change across your deployment
  *   Set up a DNS record for your S-CSCF URI – this should have the form 
scscf.<your sprout hostname>, and reference all your Sprout nodes that provide 
S-CSCF function
  *   If you have I-CSCF function enabled in your deployment as well, then 
you’ll also need to change the default S-CSCF for the I-CSCF. Edit the 
/etc/clearwater/s-cscf.json file to reference scscf.<your sprout hostname>, and 
run /usr/share/clearwater/clearwater-config-manager/upload_scscf_json to 
propagate this change across your deployment.

For the full sproutlet options reference, see 
http://clearwater.readthedocs.io/en/stable/Clearwater_Configuration_Options_Reference.html#sproutlet-options.

We’ve had a few people hit this issue now. Out of interest, are you upgrading 
from an old deployment? If not, how are you building your shared configuration? 
Is there something wrong in our documentation that we can fix up so that other 
people don’t hit this issue?

Yours,

Chris

From: [email protected] [mailto:[email protected]]
Sent: 28 April 2016 13:22
To: [email protected]; Eleanor Merry 
<[email protected]>; Chris Elford (projectclearwater.org) 
<[email protected]>; Robert Day (projectclearwater.org) 
<[email protected]>
Cc: 'Muhammad Ali' <[email protected]>
Subject: sip client authentication issue error 408

Hi all,

I have manually deployed the Clearwater IMS with 6 nodes and dns. I have 
provisioned the users in homestead and homer using the bulk create script.
I am unable to register the client, where bono forwards the request to the 
sprout and sprout asks the homestead for authentication vector it can be seen 
from the logs

I have attached the debug logs of homestead and sprout also I have attached the 
homestead cache from impi and impu where we can see the xml is present and 
users are registered with correct relam
I have also attached the monit logs form homestead

Any guidance would be most appreciated. waiting for your response

regards,
Tahir

​

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

Reply via email to