Thanks to both for your answer. I may come back to you regarding this issue.
Meanwhile I keep using the solution sending REGISTER messages to test each interface. Also it is not bullet proof. Regards, Pascal On Thu, Jun 12, 2008 at 11:02 PM, Paul Kyzivat <[EMAIL PROTECTED]> wrote: > What Dale said. I have nothing to add. > > Thanks, > Paul > > [EMAIL PROTECTED] wrote: > > From: "Pascal Maugeri" <[EMAIL PROTECTED]> > > > > My concern is to make my application to discover the right local > binding > > that will give me access to the remote SIP platform. I don't want the > user > > to choose manually which network adapter should be used. > > > > The device has to resolve the domain's URI (proxy/registrar) into an > > IP address, and presumably it has a "routing table" to instruct it > > which interface to use to contact any particular IP address. The > > routing table should identify the correct IP address to use to contact > > the proxy/registrar. > > > > Indeed, the problem is more difficult, since the device may wish to > > use different interfaces to contact different SIP agents. But in > > general, SIP presumes global routing, since an agent has to choose a > > contact URI before sending a request, with no knowledge of where the > > destination is located. > > > > Dale > > _______________________________________________ > > Sip-implementors mailing list > > [email protected] > > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > > > _______________________________________________ > Sip-implementors mailing list > [email protected] > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
