Hi Sergey, From the log you provided, it looks like the REGISTER is being processed by the BGCF (which routes calls outside the deployment), not the S-CSCF (which processes registrations). We fixed an issue recently where the BGCF and S-CSCF were both on port 5054 and so sometimes requests would go to the wrong one (https://github.com/Metaswitch/sprout/commit/efd13e91a3e2a16d92b159aa9ec73faf25257935#diff-75af8e842ec03e21817a448de6bdf026R208).
Could you try setting “bgcf=0” (to disable the BGCF) in /etc/clearwater/shared_config, and running “sudo service sprout stop” to restart Sprout? Hopefully that will resolve your issue. By the way, you’re not currently subscribed to the mailing list, which means your posts have to be approved by an administrator before anyone sees them – you can sign up at http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org and avoid that step. Best, Rob From: Clearwater [mailto:[email protected]] On Behalf Of Sergey Kolekonov Sent: 18 April 2016 14:12 To: [email protected] Subject: [Project Clearwater] [Clearwater] Sprout routing problem Hello, I need some help with Sprout issue. I've deployed Clearwater using clearwater-heat [0] on top of OpenStack Mitaka. So the problem is that I'm unable to register/make a call. After some investigations I found the following logs from Sprout [1]. In short, it answers SIP/2.0 404 No route to target when a client tries to register. Results are equal when I use both the real client (Jitsi) and clearwater-live-test [2]. Could you please help to understand what can be wrong? Thank you. [0] https://github.com/Metaswitch/clearwater-heat [1] http://paste.openstack.org/show/494412/ [2] https://github.com/Metaswitch/clearwater-live-test -- Regards, Sergey Kolekonov
_______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
