IMS Usrloc PCSCF Module

The following modules must be loaded before this module:

The following libraries or applications must be installed before running Kamailio with this module loaded:

If the processed message contains neither Expires HFs nor expires contact parameters, this value will be used for newly created S-CSCF usrloc records. The parameter contains number of second to expire (for example use 3600 for one hour). If it is set to a lower value than the min_expires parameter then it will be ignored. This parameter can be modified via ser config framework. A random value in a specific interval can be selected by using the default_expires_range parameter

Default value is 3600.

...
        modparam("ims_registrar_scscf", "default_expires", 3600)
...

This parameter specifies that the expiry used for newly created S-CSCF usrloc records are not fixed(when default_expires applies), but a random value in the intervalrdq [default_expires-default_expires_range%, default_expires+default_expires_range%]. The value is between 0 and 100 and represent the maximim percentage from default_expires that will be substracted or added when computing the value. Default in 0, meaning default_expires is left unmodified. This parameter can be modified via ser config framework.

Default value is 0.

...
        modparam("ims_registrar_scscf", "default_expires_range", 30) # +- 30% from default_expires
...

The minimum expires value of a Contact, values lower than this minimum will be automatically set to the minimum. Value 0 disables the checking. This parameter can be modified via ser config framework.

Default value is 60.

...
        modparam("ims_registrar_scscf", "min_expires", 1800)
...

The maximum expires value of a Contact, values higher than this maximum will be automatically set to the maximum. Value 0 disables the checking. This parameter can be modified via ser config framework.

Default value is 0.

...
        modparam("ims_registrar_scscf", "max_expires", 3600)
...

If the processed message contains neither Expires HFs nor expires contact parameters, this value will be used for newly created subscriptions. The parameter contains number of second to expire (for example use 3600 for one hour). If it is set to a lower value than the subscription_min_expires parameter then it will be ignored. A random value in a specific interval can be selected by using the subscription_expires_range parameter

Default value is 3600.

...
        modparam("ims_registrar_scscf", "subscription_default_expires", 3600)
...

This parameter specifies that the expiry used for newly created subscriptions are not fixed(when subscription_default_expires applies), but a random value in the interval [subscription_default_expires-subscription_expires_range%, subscription_default_expires+subscription_expires_range%]. The value is between 0 and 100 and represent the maximim percentage from subscription_default_expires that will be substracted or added when computing the value. Default in 0, meaning subscription_default_expires is left unmodified.

Default value is 0.

...
        modparam("ims_registrar_scscf", "subscription_expires_range", 30) # +- 30% from subscription_expires_range
...

The minimum expires value of a subscription, values lower than this minimum will be automatically set to the minimum. Value 0 disables the checking.

Default value is 10.

...
        modparam("subscription_min_expires", "min_expires", 1800)
...

The maximum expires value of a subscription, values higher than this maximum will be automatically set to the maximum. Value 0 disables the checking.

Default value is 1000000.

...
        modparam("ims_registrar_scscf", "subscription_max_expires", 3600)
...

DTD to check the user data received in SAA (Server Assignment Answer).

Default value is NULL (none).

...
        modparam("ims_registrar_scscf", "user_data_dtd", "/usr/local/etc/kamailio/CxDataType_Rel7.dtd")
...

XSD to check the user data received in SAA (Server Assignment Answer).

Default value is NULL (none).

...
        modparam("ims_registrar_scscf", "user_data_xsd", "/usr/local/etc/kamailio/CxDataType_Rel7.xsd")
...

indicate support for wildcard PSI is subscription profile (SAA)

Default value is 0.

...
        modparam("ims_registrar_scscf", "support_wildcardPSI", 1)
...

The name of the S-CSCF

Default value is sip:scscf.ims.smilecoms.com:6060.

...
        modparam("ims_registrar_scscf", "scscf_name", "sip:scscf2.ims.smilecoms.com:6060")
...

Should the subscription profile be stored on de-registration

Default value 0.

...
        modparam("ims_registrar_scscf", "store_profile_dereg", 1)
...

Destination realm to be used in Diameter messages

Default value "ims.smilecoms.com"

...
        modparam("ims_registrar_scscf", "cxdx_dest_realm", "my.domain,org")
...

FQDN of Diameter Peer (HSS) to use for communication (SAR). If you use this, the routing defined in your diameter xml configuration file (CDP) will be ignored and as a result you will lose the benefits of load balancing and failover.

Default value NULL (none)

...
        modparam("ims_registrar_scscf", "cxdx_forced_peer", "hss.ims.smilecoms.com")
...

The parameter controls how lookup function processes multiple contacts. If there are multiple contacts for the given username in usrloc and this parameter is set to 1, Request-URI will be overwritten with the highest-q rated contact and the rest will be appended to sip_msg structure and can be later used by tm for forking. If the parameter is set to 0, only Request-URI will be overwritten with the highest-q rated contact and the rest will be left unprocessed. This parameter can be modified via Kamailio config framework.

Default value is 0 (disabled)

...
        modparam("ims_registrar_scscf", "append_branches", 1)
...

Tells if the contact filtering based on supported methods should be performed during lookup. It's enabled only if it has a non zero value.

Default value is 0 (disabled)

...
        modparam("ims_registrar_scscf", "method_filtering", 1)
...

If specified this will make the S-CSCF always request user data from HSS.

Default value is 0 (disabled)

...
        modparam("ims_registrar_scscf", "user_data_always", 1)
...

The function processes a REGISTER message. It can add, remove or modify usrloc records depending on Contact and Expires HFs in the REGISTER message. On success and when called from the REQUEST_ROUTE, 200 OK will be returned listing all contacts that are currently in usrloc. On an error, error message will be sent with a short description in reason phrase. In case of internal errors the function will return FALSE, otherwise a force to exit the cfg is file is actioned by returning 0 (asynchronous processing)

Meaning of the parameters is as follows:

This function can be used from REQUEST_ROUTE, ONREPLY_ROUTE

...
if (!impu_registered("location")) {
   save("PRE_REG_SAR_REPLY","location");
}
...

This function extract the IMPU from the Request-URI and tries to find all registered contacts in usrloc. If there are no such contacts, -1 is returned. If there are, Request-URI will be rewritten with the contact that has the highest q value. The rest of the contacts will be appended to the sip msg structure (if append_branches is set) and can be later used by TM module for forking for example...

If the method filtering option is enabled, the lookup function will only return contacts that support the method of the request being processed (see allows header)

Meaning of the parameters is as follows:

Return codes:

This function can be used from REQUEST_ROUTE, FAILURE_ROUTE

...
lookup("location");
switch ($retcode) {
    case -1:
    case -3:
        sl_send_reply("404", "Not Found");
        exit;
    case -2:
        sl_send_reply("405", "Not Found");
        exit;
};
...

This function take a URI and tries to find the contact in usrloc. If the contact is found and has a path set, then a path header is added to the SIP message so it can be loose routed.

Meaning of the parameters is as follows:

Return codes:

This function can be used from REQUEST_ROUTE, FAILURE_ROUTE

...
lookup_path_to_contact($ruri);
...

This function will remove all bindings for the IMPU found in the Request-URI.

Meaning of the parameters is as follows:

This function can be used in REQUEST_ROUTE, FAILURE_ROUTE

...
unregister("location");
...

TBD

used in REQUEST_ROUTE

This function checks if the IMPU in the To header is registered in usrloc.

Meaning of the parameters is as follows:

Return codes:

This function can be used in REQUEST_ROUTE, FAILURE_ROUTE

...
impu_registered("location");
switch ($retcode) {
    case -1:
        sl_send_reply("404", "Not Found");
        exit;
    case 1:
        #true, continue with normal processing
};
...

This function checks if the IMPU in the Request-URI is registered in usrloc.

Meaning of the parameters is as follows:

Return codes:

This function can be used in REQUEST_ROUTE, FAILURE_ROUTE

...
term_impu_registered("location");
switch ($retcode) {
     case -1:
          sl_send_reply("404", "Not Found");
          exit;
     case 1:
          #true, continue with normal processing
};
...

The function fetches the contacts for 'uri' from table 'domain' to pseudo-variable $imssulc(profile) [imssulc = ims scscf ulc].

Meaning of the parameters is as follows:

This function can be used in REQUEST_ROUTE, FAILURE_ROUTE

...
reg_fetch_contacts("location", "$ru", "callee");
reg_fetch_contacts("location", "sip:user@kamailio.org", "caller");
...

The function frees the contacts from pseudo-variable $ulc(profile). Should be called to release the content of a profile. Anyhow, fetching a new contact addresses set over a profile will release any existing data in that profile.

Meaning of the parameters is as follows:

This function can be used in REQUEST_ROUTE, FAILURE_ROUTE

...
reg_free_contacts("callee");
...

This function checks to see that a SUBSCRIBE request is authorised to subscribe to the particular identity. Only 3 entities can subscribe:

Meaning of the parameters is as follows:

This function can be used in REQUEST_ROUTE

...
if (can_subscribe_to_reg("location")){
     $var(ret)= subscribe_to_reg("location");
}
...

Save the subscription to the REG event for the UAC or the appropriate P-CSCF (in the path to the UAC).

Meaning of the parameters is as follows:

This function can be used in REQUEST_ROUTE

...
if (can_subscribe_to_reg("location")){
     $var(ret)= subscribe_to_reg("location");
}
...

This function checks to see that a PUBLISH request is authorised to publish for a particular identity. Only 3 entities can publish:

Meaning of the parameters is as follows:

This function can be used in REQUEST_ROUTE

...
if (can_publish_reg("location")){
    $var(ret)= publish_reg("location"); 
}
...

Save the publish to the REG event for the UAC or the appropriate P-CSCF (in the path to the UAC).

Meaning of the parameters is as follows:

This function can be used in REQUEST_ROUTE

...
if (can_publish_reg("location")){
    $var(ret)= publish_reg("location"); 
}
...

Status of pcscf_usrloc, AORs, max slots, etc.

Number of AOR contacts in registered state - cannot be reset.

Number of IMPUs - cannot be reset.

Number of expired contacts - can be reset.