Hi, I just want to check: when you say “a subsequent INVITE first tries to resolve DNS for scscf.cw-aio”, do you mean that the SIP client you’re using tries to do this DNS lookup?
If so, what SIP client are you using? As mentioned here: http://clearwater.readthedocs.io/en/latest/All_in_one_Images.html#capabilities-and-restrictions, as restriction of the AIO node (which doesn’t apply to a regular Clearwater deployment) is that you must have an outbound proxy configured. We expect that SIP clients will send *all* messages to the outbound proxy, irrespective of the contents of the Service-route header. The SIP clients mentioned here: http://clearwater.readthedocs.io/en/latest/Making_your_first_call.html should do so. So I suspect that either you’ve not got an outbound proxy set, or that your client is behaving differently to what we expect. If it’s the latter, I suggest you try using one of the clients listed on that page. Hope that helps, Seb. From: Clearwater [mailto:[email protected]] On Behalf Of Francesco Lamonica Sent: 17 January 2017 13:35 To: [email protected] Subject: [Project Clearwater] Service-Route header and aio image Hello all, i have a question about aio images, when i get a succesfull register from aio image in the 200 OK there is a Service-Route header, now, if i read rfc 3608 correctly that header might be used to handle any subsequent request from the UA. Is this correct? because a subsequent INVITE first tries to resolve DNS for scscf.cw-aio and that miserably fail. Is this correct behaviour? if so is there a way to configure what sprout gives back in the register response Service-Route header? thanks. P.S. if i add an entry to localhost in /etc/hosts for scscf.cw.aio and port forward 5054 to the virtualbox vm would it be enough?
_______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
