
givenName:The first name of the contact.
initials:Initials of the contact
middleName:The middle name of the contact.
preferredGivenName:The nick name of the contact.
preferredLanguage:The individuals preferred written or spoken language. Values
will conform to rfc4646 and the reader should refer to rfc4646 for syntax. This
format uses the ISO standard Language ISO639 and region ISO3166 codes In the absence
of a value the clients locale should be used, if no value is set, en-US should be
defaulted.
isPublic:Defines if the contact is public or personal. Default = false.
source:Free format text field that identifies the entity that created this user
record. The format o this field will be either a IP Address/Port or a name
representing an enterprise LDAP or Avaya.
sourceUserKey:The key of the user from the source system. If the source is an
Enterprise Active Directory server, this value with be the objectGUID.
suffix:The text appended to a name e.g. Jr., III.
surname:The users last name, also called the family name.
title:The job function of a person in their organizational context.Examples:
supervisor, manager
ContactAddress:Represents a contacts address.
addresses:A fully qualified URI for interacting with this contact. Any addresses
added to this table should contain a qualifier e.g. sip, sips, tel, mailto. The
address should be syntactically valid based on the qualifier. It must be possible
to add via the GUI and Interface. The application must do validation.
-->
<ownedContacts>
<contact>
<company>ABC</company>
<description>Company ABC description</description>
<displayName>Phil Bath</displayName>
<displayNameAscii></displayNameAscii>
<dn>dc=acme,dc=org</dn>
<givenName>John</givenName>
<initials>Mr</initials>
<middleName>M</middleName>
<preferredGivenName>Phil</preferredGivenName>
<preferredLanguage>English</preferredLanguage>
<isPublic>false</isPublic>
<source>ldap</source>
<sourceUserKey>123546</sourceUserKey>
<suffix>Jr.</suffix>
<surname>Bath</surname>
<title>Manager</title>
<!--
type:The value reflecting the type of handle this is. Possible values are
username, e164, and privatesubsystem
category:The value representing a further qualification to the contact
address. Possible values inlcude Office, Home, Mobile.
handle:This is the name given to the user to allow communication to be
established with the user. It is an alphanumeric value that must comply with the
userinfo related portion of a URI as described in rfc2396. However, it is further
restricted as ASCII characters with only the + prefix to signify this is an E.164
handle and _ and . special characters supported.The handle and type together are
unique within a specific domain. Note, the handle plus domain can be used to
construct a users Address of Record.
label:A free text description for classifying this contact.
altLabel:A free text description for classifying this contact. This is
similar to ContactLabel, but it is used to store alternate language representations.
-->
<ContactAddress>
<address>+44-1234568</address>
<altLabel>Phone</altLabel>
<contactCategory>OFFICE</contactCategory>
<contactType>PHONE</contactType>
Managing bulk importing and exporting
Administering Avaya Aura
®
Session Manager November 2010 127
Comentários a estes Manuais