Thanks for all your responses. The proxy is not acting as a B2BUA. I think the secure access model described here makes the most sense for my scenario.
Ill explore more and update if I find something new. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kedar Karmarkar Sent: Monday, April 03, 2006 6:18 AM To: Niranjan Gopalakrishnan Cc: [email protected] Subject: Re: [Sip-implementors] Multi homed Proxy Perhaps there is a separation of functionality like secure access/authentication provided in the external proxy which is not required for the internal proxy to make calls within the local domain which can be handled by seperating the functionality into two proxies, but also supports a "feature" which can run both proxies in a single instance? On 3/31/06, Niranjan Gopalakrishnan <[EMAIL PROTECTED]> wrote: > > Im working with an implementation of a Multi homed proxy - uses 2 > interfaces, I presume one external and one internal. On receiving a > request on one interface, it forwards it to itself on the destination > interface, eventually adding itself twice in the Record-Route header > (with r2 parameter) before forwarding the request. Response is > processed similarly. > > Why is such a behaviour required? If this is to seperate the netowrk > topology (external, internal) the same can be achieved by an IP > gateway. > > I am sure there is only one instance of the Proxy running on the host. > > This behaviour is not affecting our functionality. But I need to > understand the reason behind it. > > Any pointers appreciated. > > Thanks. > Niranjan Gopalakrishnan > Senior Engineer, Call Control, Veraz Networks. [EMAIL PROTECTED] > > _______________________________________________ > 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
