IVM
Click on the red underlined text to get to the source
... voicemail server.
The definition in this document is based on the IVM Requirements
document [GOALS ...
... When creating a voice message from a client supporting IVM, the
message header MUST indicate a message context ...
... interoperability with clients not
explicitly supporting IVM, a recipient MUST NOT require its presence
in order to correctly process voice messages.
...
... MAY be indicated via a Criticality of IGNORE.
When forwarding IVM messages, clients MUST preserve the content type
...
... Interoperability between VPIM v2 systems and IVM systems can take a
number of different forms. While a thorough investigation of how
full interoperability ...
... number of different forms. While a thorough investigation of how
full interoperability might be provided between IVM and VPIM v2
systems is beyond the scope of this document; three key alternatives
...
... Handling VPIM v2 Messages in an IVM Client ...
... acceptable.
A conformant IVM implementation MUST NOT send a non-VPIM v2 message
to something it knows to be a VPIM v2 ...
... and so you may only reply with a VPIM v2 compliant message (unless
you know by some other means that the system supports IVM).
In addition, it should be noted that an IVM client ...
... IVM).
In addition, it should be noted that an IVM client may not fully
conform to VPIM v2, even if it supports playing a G.726 message
...
...
A VPIM v2 system could be extended to also be able to support IVM
compliant messages, and an IVM conformant client ...
... VPIM v2 system could be extended to also be able to support IVM
compliant messages, and an IVM conformant client could be extended to
implement VPIM v2 ...
... gateway linking a set of VPIM v2
users with a set of IVM users. This gateway would implement the
semantics ...
... For example, VPIM v2 messages with a Sensitivity of Private might be
rejected instead of forwarded to an IVM recipient, because it might
not implement the semantics of a Private message, while an IVM ...
... IVM recipient, because it might
not implement the semantics of a Private message, while an IVM
message containing content not supported in VPIM v2 (e.g., a PNG ...