
by this info type. The value of this field should be treated as opaque string; it
is maintained and used only by Presence services.
specFlags:This field is empty for regular info types, but for special info
types it contains a comma separated list of keywords that identify these types. In
this version only FULL that represents full presence information is supported.
-->
<presenceUserACL>
<infoTypeAccess>
<infoType>
<label>ALL</label>
<filter>filter</filter>
<specFlags>FULL</specFlags>
</infoType>
<access>BLOCK</access>
</infoTypeAccess>
<watcherLoginName>admin</watcherLoginName>
</presenceUserACL>
<!--PresUserCLDefault:This is a personal rule that is set by presentities to
define how much presence information can be shown to watchers that belong to the
users contact list. There may be one User Contact List Default rule per presentity
(Person) or none.
-->
<presenceUserCLDefault>
<infoTypeAccess>
<infoType>
<label>Telephony</label>
<filter>filter</filter>
<specFlags>FULL</specFlags>
</infoType>
<access>BLOCK</access>
</infoTypeAccess>
</presenceUserCLDefault>
<!--commProfileSet:A user will have a default commprofile set.A commprofile set can
exist without any handles or commprofiles referencing it. I.e. you can create a
commprofile set without needing to also create either a handle or a commprofile.A
commprofile set can contain multiple commprofiles, but only one of each specific
type. This is enforced by having the CommProfile uniqueness constraint include type,
commprofile_set_id.
HandleName: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.Note, the handle plus domain can be
used to construct a users Address of Record.
handleType:The value reflecting the type of handle this is. Possible values are
sip,smtp,ibm,and xmpp.
handleSubType:This is an additional qualify on the handle type to help specify
which private subsystem this handle belongs to.Possible values are e
164,username,msrtc,googletalk,jabber,ibmsametime,lotousnotes,msexchage.
domainName:The text name of the domain.
-->
<commProfileSet>
<commProfileSetName>Primary</commProfileSetName>
<isPrimary>true</isPrimary>
<handleList>
<handle>
<handleType>sip</handleType>
<handleSubType>msrtc</handleSubType>
</handle>
</handleList>
<!--The below is extended communication profile-->
<!--
<commProfileList>
<commProfile xsi:type="ext:ASMCommProfile" xmlns:ext="http://xml.avaya.com/
Managing bulk importing and exporting
Administering Avaya Aura
®
Session Manager November 2010 129
Comentários a estes Manuais