Hi,
in the standard nathelper.cfg (8.1.12 CVS Stable) there is the following code:
-- if (uri==myself) {
if (method=="REGISTER") { save("location"); break; };
lookup("aliases"); ---
Why arent the aliases not lookuped just after you save the location like:
-- if (uri==myself) {
if (method=="REGISTER") { save("location"); lookup("aliases"); break; }; --
best regards,
Arnd
Arnd Vehling wrote:
Hi,
in the standard nathelper.cfg (8.1.12 CVS Stable) there is the following code:
-- if (uri==myself) {
if (method=="REGISTER") { save("location"); break; }; lookup("aliases");
Why arent the aliases not lookuped just after you save the location like:
-- if (uri==myself) {
if (method=="REGISTER") { save("location"); lookup("aliases"); break; };
--
I don't think this makes sense. You need to know the aliases when you are doing an INVITE, not when you are REGISTERING. So for example if you call user 111 which is also an alias for 222, then SER needs to know that alias when an INVITE is heading for either 111 or 222, not when the user is registering.
best regards,
Arnd
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Andres wrote:
I don't think this makes sense. You need to know the aliases when you are doing an INVITE, not when you are REGISTERING. So for example if you call user 111 which is also an alias for 222, then SER needs to know that alias when an INVITE is heading for either 111 or 222, not when the user is registering.
ok, i thought the command would load all aliases for the current subscriber into SERS "alias" memory table so they would be available when processing an INVITE.
-- Arnd
On 16-02 06:33, Arnd Vehling wrote:
Andres wrote:
I don't think this makes sense. You need to know the aliases when you are doing an INVITE, not when you are REGISTERING. So for example if you call user 111 which is also an alias for 222, then SER needs to know that alias when an INVITE is heading for either 111 or 222, not when the user is registering.
ok, i thought the command would load all aliases for the current subscriber into SERS "alias" memory table so they would be available when processing an INVITE.
No, "location" and "alises" are completely independend tables. save("location") will store contacts into the location table, lookup("aliases") will retrieve (another) set of contacts from the aliases table, rewrite the Request-URI with the first one and the rest (if any) will be appended as branches.
Jan.