Unity Networking with Other Voice-Mail Systems
Unity can network with other voice-mail systems if they coexist in the network. Understanding the existing voice-mail systems and the support of networking protocols helps you to design the system such that it meets the customer requirements. Use Table G-6 to collect information about the existing voice-mail system and networking requirements.
No. | Question | Answer |
---|---|---|
1 | What are your existing voice-mail systems? | Vendor: Model: Software version: Site: License expiration date:Number of ports/sessions:Number of subscribers:Vendor: Model: Software version: Site: License expiration date: |
2 | Are these voice-mail systems currently networked?If yes, what is the protocol used for networking? | |
3 | If you have an Avaya/Octel voice-mail system, do you want to network between the Unity system and the Avaya/Octel system? | |
4 | If you have multiple sites, where will Unity be deployed? In which locations will the Octel system continue to exist?This information helps you to identify the Unity Bridge server location. Unity Bridge is required to enable the networking between the Unity system and an Avaya/Octel system. Having Unity Bridge nearer to Octel reduces the communication costs incurred in transferring the voice-mail messages between the two systems. | Provide the attachment. |
5 | Provide the networking configuration information for the existing voice-mail systems. | VPIM node IDs:AMIS node IDs:OctelNet node IDs:Avaya Interchange node IDs: |
6 | Provide the number of subscribers in each voice-mail node. | VPIM subscribers AMIS subscribers OctelNet subscribers Avaya Interchange subscribersInternet subscribers |
Comments/Notes
When you are deploying a new voice-mail system into an existing network, the customer often wants to network the legacy and new voice-mail systems so users from either system can address messages to users on the other system. You can use Table G-7 to capture the Unity networking requirements.