Copyright © 2005 Voice Sistem
| Revision History | |
|---|---|
| Revision $Revision: 4594 $ | $Date: 2008-08-06 12:08:33 +0200 (Wed, 06 Aug 2008) $ |
Table of Contents
List of Examples
rr_store_param parameterfrom_restore_mode parameter
from_passwd parametercredential parameterauth_realm_avp parameterauth_username_avp parameterauth_password_avp parameteruac_replace_from usageuac_replace_from usageuac_restore_from usageuac_auth usageUAC (User Agent Client) module provides some basic UAC functionalities like FROM header manipulation (anonymization) or client authentication.
Known limitations in this version:
authentication does not support qop auth-int, just qop auth;
CSeq not increased during authentication - the response may be rejected.
The following modules must be loaded before this module:
TM - Transaction Module
RR - Record-Route Module, but only if restore mode for FROM URI is set to “auto”.
Name of Record-Route header parameter that will be used to store (encoded) the original FROM URI.
This parameter is optional, it's default value being “vsf”.
There are 3 mode of restoring the original FROM URI:
“none” - no information about original URI is stored; restoration is not possible.
“manual” - all following replies will be restored, but not also the sequential requests - this must be manually updated based on original URI.
“auto” - all sequential requests and replies will be automatically updated based on stored original URI.
This parameter is optional, it's default value being “auto”.
String password to be used to encrypt the RR storing parameter. If empty, no encryption will be used.
Default value of this parameter is empty.
Contains a multiple definition of credentials used to perform authentication.
This parameter is required if UAC authentication is used.
Example 1.4. Set credential parameter
...
modparam("uac","credential","username:domain:password")
...
The definition of an AVP that might contain the realm to be used to perform authentication.
If you define it, you also need to define
“auth_username_avp”
(Section 1.3.6, “auth_username_avp (string)”) and
“auth_username_avp”
(Section 1.3.7, “auth_password_avp (string)”).
The definition of an AVP that might contain the username to be used to perform authentication.
If you define it, you also need to define
“auth_realm_avp”
(Section 1.3.5, “auth_realm_avp (string)”) and
“auth_username_avp”
(Section 1.3.7, “auth_password_avp (string)”).
Example 1.6. Set auth_username_avp parameter
...
modparam("uac","auth_username_avp","$avp(i:11)")
...
The definition of an AVP that might contain the password to be used to perform authentication.
If you define it, you also need to define
“auth_password_avp”
(Section 1.3.7, “auth_password_avp (string)”) and
“auth_username_avp”
(Section 1.3.7, “auth_password_avp (string)”).
Example 1.7. Set auth_password_avp parameter
...
modparam("uac","auth_password_avp","$avp(i:12)")
...
Replace in FROM header the display name and the URI part.
display and URI parameters can include pseudo-variables.
This function can be used from REQUEST_ROUTE.
Example 1.8. uac_replace_from usage
...
# replace both display and uri
uac_replace_from("$avp(s:display)","$avp(s:uri)");
# replace only display and do not touch uri
uac_replace_from("batman","");
# remove display and replace uri
uac_replace_from("","sip:robin@gotham.org");
# remove display and do not touch uri
uac_replace_from("","");
...
Replace in FROM header the URI part without altering the display name.
URI parameter can include pseudo-variables.
This function can be used from REQUEST_ROUTE.
This function will check if the FROM URI was modified and will use the information stored in header parameter to restore the original FROM URI value.
This function can be used from REQUEST_ROUTE.