
Chapter 1 Networking in Cisco Unity
Comparison of AMIS, Bridge, and VPIM Networking
Table | Spoken Name Confirmation |
| ||
|
|
|
| |
AMIS |
| Bridge | VPIM | |
|
|
| ||
Available when a recorded voice | Available when a recorded voice name | Cisco Unity includes support for the | ||
name exists for the AMIS subscriber. | exists for the Bridge subscriber. | automatic creation of VPIM subscribers. | ||
Voice names for AMIS subscribers | Voice names for Bridge subscribers can | Therefore, the text and recorded voice | ||
names of senders on remote VPIM | ||||
must be recorded individually in the | be recorded individually in the | |||
systems can be derived from incoming | ||||
Cisco Unity Administrator. | Cisco Unity Administrator. However, | |||
VPIM messages, and VPIM subscribers | ||||
Voice names for AMIS subscribers | because the Bridge supports directory | |||
can be automatically created in the | ||||
information sharing, the text and | ||||
can be imported by using the | Cisco Unity directory with the derived | |||
recorded voice names of Octel | ||||
Cisco Unity Bulk Import utility. | text and voice names. | |||
subscribers are retrieved on a usage basis, | ||||
|
| |||
|
| and Bridge subscribers can be | Available when a recorded voice name | |
|
| automatically created in the Cisco Unity | exists for the VPIM subscriber. | |
|
| directory with the retrieved text and voice | Voice names for VPIM subscribers can be | |
|
| names. Similarly, the text and voice | recorded individually in the Cisco Unity | |
|
| names of Cisco Unity subscribers are | ||
|
| Administrator. | ||
|
| retrieved by the Octel servers on a usage | ||
|
| Voice names for VPIM subscribers can be | ||
|
| basis, and directory entries are | ||
|
| automatically created on the Octel servers | imported by using the Cisco Unity Bulk | |
|
| with the retrieved text and voice names. | Import utility. | |
|
| Voice names for Bridge subscribers can |
| |
|
| be imported by using the Cisco Unity |
| |
|
| Bulk Import utility. |
| |
|
|
|
| |
Table | Audio Formats Supported1 |
| ||
|
|
|
| |
AMIS |
| Bridge | VPIM | |
|
|
| ||
The AMIS protocol is not dependent | Octel Analog Networking is not | The VPIM Version 3 Specification | ||
on audio format. |
| dependent on audio format. | includes support for the following audio | |
Any codec supported for use with | The Cisco Unity servers must use either | formats: G.711, G.726, and GSM 6.10. | ||
| ||||
Cisco Unity can be used. | the G.711 or the G.729a codec in order to | Any codec supported for use with | ||
|
| communicate with the Cisco Unity | Cisco Unity can be used. | |
|
| Bridge servers. | Outbound VPIM messages can be | |
|
|
| ||
|
|
| converted to G.726 or sent in the format | |
|
|
| in which they were recorded. | |
|
|
| Incoming VPIM messages can be | |
|
|
| converted to G.711, G.729a, or GSM | |
|
|
| 6.10, or remain in the format in which | |
|
|
| they were sent. | |
|
|
|
|
1.For a list of audio formats supported by Cisco Unity, see the Audio Codecs and Cisco Unity white paper, at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_white_papers_list.html.
Networking Guide for Cisco Unity Release 5.x (With Microsoft Exchange)
| ||
|