Show\Hide Navigation Product Description: Public and Private Voice Networks
Up Down Back Forwards Print Synch call us

Internetworking with Other Avaya Products

IP Office will support the most appropriate way for communication with any other existing PBX's in a customer network, whether TDM or IP-based. With Avaya DEFINITY, MultiVantage, Avaya Integral Enterprise or Avaya Communication Manager (ACM), the protocols used will be QSIG or H.323 over T1, E1 or IP links

VoIP networking using H.323

IP Office (since release 1.1 in US and release 1.2 in EMEA) has been successfully tested to be interoperable over IP trunks with Avaya Communication Manager (ACM). The protocol supported is H.323 using industry-standard compression codecs (types G.711A, G.711MU, G.729A and G.723.1-6K3). The features currently supported are as follows:

Desk to desk dialing (basic voice call)
Calling/Connected Party ID number
Calling/Connected Name Presentation
Call Hold
Call Transfer

definity_ip

These features allow for simple networking needs between IP Office remote branches to a DEFINITY/ACM at the main site.

QSIG networking using T1/E1 links (TDM)

Alternatively QSIG may be favored as the chosen signaling standard within multiple vendor environments and provides the following supplementary services which are also available between IP Office and DEFINITY / MultiVantage/ I55 /ACM (equipped with the relevant RFA licenses):

definity_pri

Simple Telephony Call/Basic call (ETS 300 171/172)
Circuit Switched Data Call/Basic call (ETS 300 171/172)
Calling/Connected Line Identity Presentation (ETS 300 173)
Calling/Connected Name Presentation (ETS 300 237/238)
Message Waiting Indication (ETS 301 260/255)

Messaging Networking

There are 2 options available today to provide messaging interoperability between IP Office and Definity / MultiVantage / ACM. The first option provides Centralized Voicemail while the second allows Avaya voicemail systems to be networked.  The requirements, functionality and restrictions are summarized below:

IP Office to DEFINITY / MultiVantage / ACM connected to Intuity AUDIX™ over a QSIG link (E1/T1 or IP)

definity audix1

No local Voicemail required on remote branch IP Office but AUDIX license required on every IP Office
Requires Intuity Audix 4.4+ connected via C-LAN to DEFINITY 9.5+ (see IP Office Offer Announcement dated August 2003 for more information on compatibility)
Maximum of 19 IP Offices can be supported on 1 INTUITY AUDIX™ server (20 total with DEFINITY/ACM occupying one slot)
Requires QSIG and Private Networking licenses on DEFINITY / MultiVantage / ACM
User mailbox with Message Waiting Light support
Forward voicemails between users
No auto attendant (enhancement currently being investigated)
No call recording
No queuing at remote sites
No Fax over IP to AUDIX™
No Small Community Networking support when AUDIX™ is configured on IP Office.

Avaya IP Office VoiceMail Pro networked to Avaya Modular Messaging / Octel / Intuity AUDIX™ via Interchange / S3210

definity audix2

Requires local VoiceMail Pro on every branch IP Office licensed with VoiceMail Pro Networked Messaging RFA
Requires Avaya Interchange/S3210 on Modular Messaging, Octel or Intuity Audix
Provides 2,000 remote mailboxes per VoiceMail Pro server i.e. per branch office (to be extended to 10,000 remote mailboxes by next VoiceMail Pro maintenance release)
User mailbox with Message Waiting Light support
Forward voicemails between known remote users
Fully-featured VoiceMail Pro at every branch office
VoiceMail Pro Networked Messaging will only accept an incoming voicemail message for a local mailbox. It will NOT forward it to a remote Voicemail server. If required, this facility is available through Avaya Interchange.
VoiceMail Pro Networked Messaging is limited to Avaya Messaging Servers (not third-party messaging platforms).

© 2010 AVAYA
15-601041 Issue 20.f.-
18:14, 25 February 2010
(internetworking_with_other_avaya_products.htm)

Performance figures, data and operation quoted in this document are typical and must be specifically confirmed in writing by Avaya before they become applicable to any particular order or contract. The company reserves the right to make alterations or amendments at its own discretion. The publication of information in this document does not imply freedom from patent or any other protective rights of Avaya or others.

All trademarks identified by (R) or TM are registered trademarks or trademarks respectively of Avaya Inc. All other trademarks are the property of their respective owners.

Last Modified: 25/01/2010