telephone number
Click on the red underlined text to get to the source
... When present, the vPIMUser object contains information useful for
verifying that the dialed telephone number corresponds to the
intended recipient. This object also provides capability information
and mailbox ...
... vPIMTelephoneNumber is the full E.164 form of the
telephone number [E164], including any sub-addressing portion. The
...
... SYNTAX 1.3.6.1.4.1.1466.115.121.1.44{20} )
Example: A North American telephone number with the sub address of 12
would be represented as "+12145551212+12".
...
... vPIMTelephoneNumber is, by default, a multi-valued
attribute. But if an entry has multiple values for this attribute,
those values MUST be distinct from each other in the telephone number
portion. It is expected that each submailbox of a single telephone
number will have its own vPIMUser ...
... those values MUST be distinct from each other in the telephone number
portion. It is expected that each submailbox of a single telephone
number will have its own vPIMUser entry.
...
... address. In most cases, these values will be the same.
The telephone number is stored with no parenthesis, spaces, dots, or
hyphens. The leading '+' and the '+' delineating the submailbox are
required markup.
...
... of the voice mailbox associated with a given telephone number. It is
defined as a distinct attribute to distinguish it from the
rfc822Mailbox attribute that may be used for other purposes.
...
... This attribute indicates the presence of sub-mailboxes for the
queried telephone number. This information may be used to provide a
post-dial sub-addressing menu to the sender ...
... especially in this time of local phone competition. Service
providers require maximum flexibility to protect this data.
Because of the dense nature of telephone number assignments, this
data is subject to "go fish" queries ...