Hi

Thanks for your reply.

Yes in fact, the registrar is some sort of a billing application that enforce AAA.

The only problem is , it does not handle NAT traversal. That's why we need OpenSer to act as an SBC.

El Domingo, 8 de Junio de 2008, sylver_b escribió:
> Hello,
>
> We would like to evaluate OpenSER to test interoperability with our
> sip registrar platform - as our registrar does not handle NAT Traversal
> we would like to use OpenSER as a mirror proxy . Basically we would like
> OpenSER to act as an Upper Registrar proxy where all the sip messages would
> be forwarded to our registrar, based on the
 domain name used in the
> Register. ie: REGISTER 111 at domain1.com  -> forward to -> registrar_ip1
> REGISTER 222 at domain2.com -> forward to -> registrar_ip2
> and so on...

Take a look to "t_replicate" function of "tm" module.


> If a call is initiated, OpenSER should transparently handle NAT traversal
> functionalities while forwarding the INVITE request to the proper registrar
> server.

Do you mean that an INVITE should be forwarded to a registrar server? maybe 
the registrar is also a proxy/PBX?

Please, explain a little more your escenario.

Regards.

-- 
Iñaki Baz Castillo