1.1. Example H.350 commObject LDAP Entry The Kamailio H350 module enables a Kamailio SIP proxy server to access SIP account data stored in an LDAP [RFC4510] directory containing H.350 [H.350] commObjects. ITU-T Recommendation H.350 standardizes LDAP object classes to store Real-Time Communication (RTC) account data. In particular, H.350.4 [H.350.4] defines an object class called sipIdentity that includes attribute specifications for SIP account data like SIP URI, SIP digest username/password, or service level. This allows to store SIP account data in a vendor neutral way and lets different entities, like SIP proxies, provisioning, or billing applications, access the data in a standardized format. The ViDe H.350 Cookbook [vide-h.350-cb] is a good reference for deploying an H.350 directory. Besides general information on H.350, LDAP, and related standards, this document explains how to set up an H.350/LDAP directory and discusses different deployment scenarios. The H350 module uses the Kamailio LDAP module to import H.350 attribute values into the Kamailio routing script variable space. The module exports functions to parse and store the H.350 attribute values from the Kamailio routing script. It allows a script writer to implement H.350 based SIP digest authentication, call forwarding, SIP URI alias to AOR rewriting, and service level parsing. 1.1. Example H.350 commObject LDAP Entry The following example shows a typical H.350 commObject LDAP entry storing SIP account data. Ex
| Parámetro | Tipo | Descripción |
|---|---|---|
| ldap_session | string | 3.2. base_dn (string) 3.3. search_scope (string) |
| base_dn | string | 3.3. search_scope (string) |
| search_scope | string | 3.1. ldap_session (string) |
| ldap_session | string | Name of the LDAP session to be used for H.350 queries, as defined in the LDAP module configuration file. |
| base_dn | string | Base LDAP DN to start LDAP search for H.350 entries. For best performance, this should be set to the direct ancestor of the H.350 objects. |
| search_scope | string | LDAP search scope for H.350 queries, one of "one", "base", or "sub". |
4.2. h350_auth_lookup(auth_username, "username_avp_spec/pwd_avp_spec") 4.3. h350_result_call_preferences(avp_name_prefix) 4.4. h350_result_service_level(avp_name_prefix)
4.3. h350_result_call_preferences(avp_name_prefix) 4.4. h350_result_service_level(avp_name_prefix)
4.4. h350_result_service_level(avp_name_prefix)
4.1. h350_sipuri_lookup(sip_uri)
This function performs an LDAP search query for an H.350 commObject with a SIPIdentitySIPURI of sip_uri. The sip_uri parameter first gets escaped according the rules for LDAP filter strings. The result of the LDAP search is stored internally and can
This function performs an LDAP search query for SIP digest authentication credentials in an H.350 directory. The H.350 directory is searched for a commObject with SIPIdentityUserName of auth_username. If such a commObject is found, the SIP digest aut
This function parses the callPreferenceURI attribute of an H.350 commObject, which must have been fetched through h350_*_lookup or ldap_search. callPreferenceURI is a multi-valued attribute that stores call preference rules like e.g. forward-on-busy
Directory services architecture for SIP [H.350.4] defines a multi-valued LDAP attribute named SIPIdentityServiceLevel, which can be used to store SIP account service level values in an LDAP directory. This function parses the SIPIdentityServiceLevel
Copyright © 2007 University of North Carolina
