C.1.8 callPreferenceURIObject (H.350.6)

OID: 0.0.8.350.1.1.8.2.1

objectclasses: (0.0.8.350.1.1.8.2.1

NAME 'callPreferenceURIObject'

DESC 'callPreference object'

SUP top AUXILIARY

MAY ( callPreferenceURI )

)

DEFINITION & USE:

 
The callPreferenceURI is a URI consisting of two parts, a URI and a label. Because it is its own unique object class, the directory can be searched for the presence of this attribute.

C.1.8.1 callPreferenceURI

OID: 0.0.8.350.1.1.8.1.1

attributetypes: (0.0.8.350.1.1.8.1.1

NAME 'callPreferenceURI'

DESC 'Labeled URI format to point to forwarded address and type of forwarding'

EQUALITY caseExactMatch

SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )

DEFINITION & USE:

 
The value of the attribute found at the URI target is the address to which calls should be forwarded. When representing more than one call forwarding behaviors, use a separate callPreferencesURI for each (one for no answer, another for busy, etc.). The URI portion is merely a pointer that points to an address at which can be found the desired call forwarding address. In the most basic case, the URI will be an LDAP URI that points to another H.350 entry elsewhere in the same H.350 directory. For example, if an H.323 entry is described by an h323IdentitydialedDigits attribute, its callPreferenceURI may point to another h323IdentitydialedDigits attribute elsewhere in the same directory. In this case, the URI is an LDAP URI.
 
It is possible to represent more complex call preference behavior if the URI points to an object outside the H.350 directory. For example, the URI could be a 'mailto:' URI of the form 'mailto:user@host.domain', which would tell a call server to interpret the desired call preference behavior to initiative an electronic mail message. Similarly, a callPreferenceURI could be a URL pointing to a web page that contained a web form for the calling party to fill out and submit, or even a game to play. A more advanced scenario may be supported if the URL target represents an XML document or Call Processing Language script which describes conditional call preferences.
 
Note that it is the responsibility of the implementer to ensure that the data populating the directory is able to be interpreted by the call server that will be accessing that data.
 
The label portion of callPreferenceURI contains an indication of the type of call forwarding for simple forwarding types. The form of the label is 'type:argument' where 'type' is a string indicating the type of call forwarding and 'argument' is a string indicating the time in milliseconds after which the call forwarding should occur. The two values are delimited by a colon.

Type	Type Description
b	Forward on busy
n	Forward on no answer
u	Forward unconditionally
f	Forward on destination not found

For example, a label of 'n:4000' indicates that calls should be forwarded to the target URI after 4 seconds if the called endpoint does not answer. Similarly, 'f:250' indicates that the call should be forward to the target URI after 250 milliseconds if the destination is not located.

NUMBER OF VALUES:

 
multi

INDEXING PROFILE:

 
equality

EXAMPLE APPLICATION USING ATTRIBUTE:

 
A user desires that if he does not answer, calls should be forwarded to a different number. However, if the user is busy (i.e. on the phone) then the calling party should be directed to a 'mailto:' link, which will cause an electronic mail application to open on the calling party's application.

EXAMPLE (LDIF FRAGMENT):

 
callPreferenceURI: ldap://directory.acme.com/dc=acme,dc=com??sub? 
(h323IdentitydialedDigits=1234) b:2000 // Forward on busy after 2 seconds