Hi David, Yes, that sounds like a client issue - I'd expect all requests to go through the P-CSCF. I don't use Linphone, so I can't say whether that's normal, but Blink and X-Lite work quite well for me when I test with softphones - if you use one of those, you should have better luck.
If you continue to see 503 errors, feel free to send the Sprout logs and I'll see if I can spot anything odd. Best, Rob -----Original Message----- From: David Salvador [mailto:[email protected]] Sent: 18 April 2016 16:10 To: Robert Day (projectclearwater.org) <[email protected]> Subject: Re: [Project Clearwater] CW-AIO IPv6 INVITE getting 403 Response Hi Robert, Thanks for the response to both emails. The cassandra issue we found later that it was a missing symlik. the cassandra.yaml was locate in /usr/share/... (can't remember the full path), but was not located in /etc/cassandra/ Also, we've tried a new approach, that is to install CW manual installation (several VMs). In this approach we also found the cassandra.yaml issue, but that was easily fixed with the above solution. Now we are facing a different issue, instead of 403, we are getting 503 to Call Invite. We are using Linphone, and we still don't know if it is a client issue, because it has a odd behaviour: 1- Register goes through Bono 2- Invite goes directly to Sprout. (I know that on 200 OK to Register it's given a Service-Route, but still, client should always forward SIP Requests through P-CSCF right?) Again, Thanks for the help. Best Regards, David Salvador On 18/04/2016, Robert Day (projectclearwater.org) <[email protected]> wrote: > Hi David, > > Thanks for raising this! I've reopened > https://github.com/Metaswitch/sprout/issues/1029 to cover the hostname > problem, but your config change sounds good. > > On the Bono issue, it's difficult to debug the issue without full logs > - for example, you have the log saying "Find flow for transport > tcpsxxx (130), remote address [2520::d33:7c78:8ae1:a3c3]:49541", but I > can't see whether it successfully finds that flow, or whether such a flow has > ever been created. > Could you get the full Bono log off the machine somehow (perhaps with > a USB > stick?) and send it? > > By the way, it sounds like you have got subscribers registering on the > IPv6 node now - does this mean you've resolved the Cassandra issue > from your previous email? > > Best, > Rob > > > -----Original Message----- > From: Clearwater > [mailto:[email protected]] On Behalf Of > David Salvador > Sent: 14 April 2016 16:59 > To: [email protected] > Subject: [Project Clearwater] CW-AIO IPv6 INVITE getting 403 Response > > Hi All, > > I'm trying to get the last version of OVF AIO working at IPv6, but > i've faced a few issues: > > Sprout was unable to start the Registrar using the default configs, > the workaround was to change the sprout_hostname at > /etc/clearwater/shared_config to "cw-aio" and then add the > "scscf.cw-aio" to /etc/hosts (to the ipv6 of the VM) > > At this point, clients are able to register but when i try to send an > INVITE (also tried with MESSAGE) I get a 403 response. > > I've increased Bono log level and i can see the following (I'll copy > only the relevant data because i don't have internet on the machine > were I'm running tests): > > ... uri_classifier.cpp:197 Classified URI as 4 ... bono.cpp:279: Proxy > RX request ... pjutils.cpp:674: Cloned Request msg INVITE/cseq=20 (...) to ... > ... bono.cpp:803: Request received on non-trusted port 5060 ... > bono.cpp:1043: Perform access proxy routing for INVITE request ... > uri_classifier.cpp:197 Classified URI as 5 ... pjutils.cpp:509: Found > Route header, URI = sip:scscf.cw-aio;transport=TCP;lr;orig > ... bono.cpp:1180: Message Received on non-trusted port 5060 ... > flowtable.cpp:136: Find flow for transport tcpsxxx (130), remote > address > [2520::d33:7c78:8ae1:a3c3]:49541 ... bono.cpp:1370: Rejecting request > from untrusted source ... bono.cpp:757: Reject INVITE request with 403 > status code > > Anyone has any ideas what is wrong ? > > Best Regards, > David > > _______________________________________________ > Clearwater mailing list > [email protected] > http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.p > rojectclearwater.org > _______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
