Thanks Matt it was excellent info. Specially for new people like me to troubleshoot and deploy clear water as i know now that where the hostname matching is being performed from checking route header and where dns query is being generated. Thanks
Sent from my iPad > On 07-Apr-2014, at 2:46 pm, Matt Williams <[email protected]> > wrote: > > Schahzad, > > When bono receives a message, it looks at the top Route header and decides > whether this corresponds to itself. If it does, it strips it off. It > decides whether the route header corresponds to itself by parsing the domain > out of the URI and comparing it with the value of the "public_hostname" field > - it does not perform DNS resolution at this stage. > > It then tries to route the message on. It does this by looking at the new > top Route header. It performs DNS resolution and sends the message on. It > does not check at this point that the resolved IP address ends up belonging > to itself. > > As a result, both the public_hostname and DNS must be correct. > > Does that make sense... and answer your question? > > Matt > > From: Schahzad Zafar [mailto:[email protected]] > Sent: 07 April 2014 10:35 > To: Matt Williams; [email protected] > Subject: Re: [Clearwater] Sip truking > > Hi Matt, > Just a question poped in, if IBCF is not recognizing "IBCF" in header, how > ibcf node is doing the name to ip lookup. My understanding is it would do dns > look up and as we are using dns masquerading so if ibcf is resolvable via dns > it should word. Previously ibcf was only resolving via host file, was that > the issue or we must use public_hostname parameter? > Thanks
_______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/listinfo/clearwater
