Check if Avaya has support for SIP Path extension: http://www.opensips.org/html/docs/modules/1.7.x/path.html This would be the clean solution.
Alternative solution: replace the IP in Contact header of REGISTER and mirror the registration on opensips. This should trick Avaya to think that opensips is the one registering and Avaya should send all INVITEs to opensips. Second alternative solution: Instruct opensips to register itself on Avaya: http://www.opensips.org/html/docs/modules/1.7.x/uac_registrant.html Handle all registrations from SIP subscribers on opensips (let opensips act as a full registrar). Regards, Ovidiu Sas On Mon, Sep 12, 2011 at 9:44 AM, hart323 <free....@gmail.com> wrote: > Basically what I ask is what methods can i use to force PhoneA to go to > opensips because it is a h.323 phone and there is no way to specify sip > proxy in it or it's only one solution here - b2bua? > > -- > View this message in context: > http://opensips-open-sip-server.1449251.n2.nabble.com/opensips-rtpproxy-and-nat-traversal-for-invite-without-register-tp6775967p6783530.html > Sent from the OpenSIPS - Users mailing list archive at Nabble.com. > > _______________________________________________ > Users mailing list > Users@lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > _______________________________________________ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users