You can add SER2 IP to the trusted table and in SER2 use allow_trusted function to check, whether you need to authorize incoming INVITE or not (take a look at onsip.org document for details).
Nevertheless, it only makes sence to authorize outgoing requests at SER1. SER2 is not concerned with authorizing SER1's domain users.
Good luck.
Andrey.
On 6/7/06, Chahn John Kim johnk@koreanet.us wrote:
Hi all, Need you experts' help on SIP design.
I've setup a testbed composed of two SER Registrar/Proxies in two different realm/domain(s) as below;
<--Internal Private(192.168.x.0----><----External Public(x.x.x.0)---------> UA1<-----------------> SER1 <---------------------> SER2 <------------> UA2 Mydomain.org Registrar/Proxy Theirdomain.org Registrar/Proxy
What is the right way to pass the user credential of UA1 to SER2 so that "INVITE" to UA2 will be accepted at SER2, knowing that UA1 user has its login ID/password to SER2 but it is locally "REGISTER"ed at SER1 in private domain?
I guess I am having trouble understanding working mechanism of "inter" SIP realm or domain.
Any comments will be appreciated.
John Kim email: johnk@koreanet.us johnk@netcomusa.us
Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers