| |||||||||
![]() | | ||||||||
| |||||||||||||||
| |||||||||||||||
| Meridian Systems Welcome to the Nortel Meridian Forums Including Meridian Options 11-81C CS1000M Meridian Mail Call Pilot Companion and Sucession Hospitality OTM MAT MICB RAN NetGateway ..., and all other Applications |
| Tags: broadcast, callpilot, message, octel, translation |
![]() |
| | LinkBack | Thread Tools | Display Modes |
| | #1 (permalink) | ||||||||
| Guest
| Octel to Callpilot broadcast messages I have an interface requirement where our offices around the world use Octel and Avaya PBX's, however, our country uses CallIplot and Nortel PBX's. We are very happy with the Nortel products locally, but wish to obtain a smart way to broadcast messages between older Octel systems and Callpilot 2 in both directions. Our OS offices often send broadcast VM messages which we would like to receive also. We would also like to send broadcast messages to the rest of the world via Callpilot to be received by their Octel systems. What we would like is some kind of interface or translator that allowed CallPilot to receive a single copy of the message from the OS Octel system, and rebroadcast it internally a single time to our Callpilot users. I am told by Nortel that the only way to do this is with AMIS, which apparently would result in a call being set up for each mailbox. For Australia to send messages to the rest of the world would then be slow and costly. Is there a smart and easy way to acheive this? Is there an AMIS to IP product out there? Is VPIM the answer? Any clues appreciated. Regards Sal | ||||||||
|
| | #2 (permalink) | ||||||||
| Junior Member ![]()
Location: Chlt-NC Rep Power: 7 ![]() | WIth call pilot you can purchase the VPIM feature. VPIM=Voice Profile for Internet Messaging. It will allow networking over TCP?IP. My experience with AMIS between a Nortel and Octel or Avaya product has not been too spectacular. Octel for instance does not support VPIM. If you have the dollars to spend I would look at two things 1.) add VPIM to the Call Pilot, 2.) Purchase an Avaya Interchange Server. The Interchange will address your needs. The Interchange has a great feature called enterprise lists, think of huge distribution lists. The nice thing is you don't have to add every mailbox, just a "machine name", which is actually a name given to an end point voice messaging system. The Interchange is not cheap, but there is not anything else out there that compares. Avaya has also releases a skinnyed down version that goes by the S3210 nomenclature. It will do protocol conversions between systems,but will not support enterprise lists. It may meet your needs, I would suggest contacting your Avaya rep. Also, with the Interchange or S3210 your voice messaging network becomes a hub & spoke as opposed to a meshed network. This is a big benefit if you have alot of messaging systems. | ||||||||
| | |
| | #3 (permalink) | ||||||||
| Junior Member ![]()
Location: Chlt-NC Rep Power: 7 ![]() | WIth call pilot you can purchase the VPIM feature. VPIM=Voice Profile for Internet Messaging. It will allow networking over TCP?IP. My experience with AMIS between a Nortel and Octel or Avaya product has not been too spectacular. Octel for instance does not support VPIM. If you have the dollars to spend I would look at two things 1.) add VPIM to the Call Pilot, 2.) Purchase an Avaya Interchange Server. The Interchange will address your needs. The Interchange has a great feature called enterprise lists, think of huge distribution lists. The nice thing is you don't have to add every mailbox, just a "machine name", which is actually a name given to an end point voice messaging system. The Interchange is not cheap, but there is not anything else out there that compares. Avaya has also releases a skinnyed down version that goes by the S3210 nomenclature. It will do protocol conversions between systems,but will not support enterprise lists. It may meet your needs, I would suggest contacting your Avaya rep. Also, with the Interchange or S3210 your voice messaging network becomes a hub & spoke as opposed to a meshed network. This is a big benefit if you have alot of messaging systems. | ||||||||
| | |
![]() |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| Display Modes | |
| |
Similar Threads | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Meridian Opt. 11 and Octel issues. Cant reply to message. | mholden | NORTEL | 1 | 09-26-2006 07:39 PM |
| Call Pilot 4.04 | gauravgirdhar | Meridian Systems | 5 | 07-27-2006 02:49 AM |
| 2.24.26G ITG to BCM 3.0 | markj39k | Meridian Systems | 2 | 09-16-2003 09:05 AM |
| Say what? | Sherrill | Off Topic - Humor/Jokes | 2 | 03-07-2003 12:15 PM |