Hi!
I have problems understanding the uri module.
As far as I understand I can map aliases to subscribers - e.g. my main identity is klaus@mydomain, but I also want to use nickname@cooldomain in From: header with a single SIP account (single subscriber)
Thus I can use uri_db module and uri table to check if klaus@mydomain is allowed to use nickname@cooldomain.
Thus, what do I enter in the uri table? The definition is:
id | username | domain | uri_user | last_modified ----+----------+--------+----------+---------------
In which column do I have to put which values?
thanks klaus
Hi Klaus,
uri_db module is intended to allow a user to use a different username for credentials than for SIP.
For example, when you do authentication, you actually check if the username from credentials presented the correct password (so the subscriber table is actually a credentials table).
now, after auth, you usually check if the auth username is the same as the SIP username (check_to/from) - 1:1 mapping-, but via uri table to can create a m:n mapping (what auth usernames a SIP username can use)
the module was thought to be used in cases where the realm (auth) equals the SIP domain (from).
Ex: From: nickname@mydomain Cred: klaus@mydomain
regards, Bogdan
Klaus Darilion wrote:
Hi!
I have problems understanding the uri module.
As far as I understand I can map aliases to subscribers - e.g. my main identity is klaus@mydomain, but I also want to use nickname@cooldomain in From: header with a single SIP account (single subscriber)
Thus I can use uri_db module and uri table to check if klaus@mydomain is allowed to use nickname@cooldomain.
Thus, what do I enter in the uri table? The definition is:
id | username | domain | uri_user | last_modified ----+----------+--------+----------+---------------
In which column do I have to put which values?
thanks klaus