Thanks Matt for the fast turnaround and quality of the reply ! So if I bind my SIP Phone to the network interface, that should work right ? No need to setup a different machine and modify all the IP Addresses in ClearWater so it's accessible remotely. If the fix comes in a week or 2 and another VirtualBox Image is ready (including both the ENUM and the localhost routing issue) that's fine by me as well.
Thanks Best Regards Jean On Thu, Oct 17, 2013 at 10:59 AM, Matt Williams < [email protected]> wrote: > On Thu, Oct 17, 2013 at 09:21:23, Jean Deruelle wrote: > > To: [email protected] > > Subject: [Clearwater] Clearwater and Mobicents Integration > > > > Hi all, > > > > I have been testing integration of Mobicents Restcom > > (http://www.restcomm.org/, Twilio in a box based on Mobicents) as a > > SIP Application Server in Clearwater IMS Core. The result is pretty > > positive so far. > > Hi Jean, it sounds like you've made some good progress! > > > I succeeded to integrate our RestComm project as SIP AS in Clearwater > > IMS Core and receive calls from the SIP SoftPhone however I have a > > problem on the BYE sent by RestComm which is replied by a 404 by > > ClearWater See this document (with the intent to make a blog post out > > of it later down the road) > > https://docs.google.com/document/d/1MKZFQ45HUJMIUV4O6sCIAB- > > WTw7Z7eJaLDmb > > MczlyfQ/edit?usp=sharing > > I added some notes at the end, Section Issues Noticed where the > > subsequent BYE from our SIP AS gets a 404 from Clearwater and is not > > routed to the SIP UA (I added the log of the messages from the SIP AS > > POV). Can you help me figure it out ? > > I think the issue here is that the softphones are on the same host as the > Clearwater deployment and there's a bug in Clearwater ( > https://github.com/Metaswitch/sprout/issues/75) which means it misroutes > messages if the request URI specifies a host of 127.0.0.1. To unblock your > testing, would it be possible to run your softphones on a different host? > I'll also look into fixing the issue, but there'll be a week or so of > delay before this fix makes it into a stable release. > > > It's unclear which logs you would need from the various clearwater > > nodes, so feel free to guide me on which logs I should attach here to > > help on making the integration complete. > > The logs you provided were very useful in this case. If I had needed more > logs, I probably would have asked for those described in > https://github.com/Metaswitch/clearwater-docs/wiki/Troubleshooting-and-Recovery, > in particular the /var/log/bono/bono*.txt and /var/log/sprout/sprout*.txt > logs described under the bono and sprout sections. > > Incidentally, your write-up mentions that the ENUM look-ups were failing. > I suspect this is because we're doing the ENUM query onto the public > Internet and the DNS server is not responding. We saw this issue and fixed > it recently (but probably not in the software version you're running) by > simply disabling ENUM by default (rather than querying public DNS, which > seems to be the wrong thing to do). If you have a private ENUM server, you > can set it as the enum_server parameter in your /etc/clearwater/config file > and then restart the sprout software, as described at > https://github.com/Metaswitch/clearwater-docs/wiki/Modifying-Clearwater-settings > . > > I hope that helps - please let me know if this doesn't fix it or you have > further issues. > > Cheers, > > Matt >
_______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/listinfo/clearwater
