On Thu, Oct 17, 2013 at 11:35:21, Jean Deruelle wrote: > Subject: Re: [Clearwater] Clearwater and Mobicents Integration > > 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.
I think it depends on which network interface you're binding to. - If you're running the softphones on your host PC and it's the network interface of your host PC, I think this should be OK. - If you're running softphones on the guest VM and it's the network interface of your guest VM that you're binding to, I'm not sure this will work either - it's possible, and it could be worth a try, but I think Clearwater will assume that if the request URI contains its own IP address (i.e. either 127.0.0.1 or its network interface's IP address), it should handle it, even if the Route headers say otherwise. This is due to Clearwater matching the request URI before doing Route header processing, when it should do them in the other order. As Mike has commented on https://github.com/Metaswitch/sprout/issues/75, this was actually fixed very recently but hasn't made it into the stable build yet. Incidentally, I think that configuring external IP access on VirtualBox isn't too difficult - we set our all-in-one OVF images up to do this. You should be able to set the network adapter type to NAT and then open up port-forwarding for ports 22, 80 and 5060 from your local PC. Then you can run softphones on your host PC (with its own IP address) and the guest VM will have its own (completely private) IP address. Cheers, Matt _______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/listinfo/clearwater
