Avaya Session Border Controller For Enterprise; Voip Faq - Avaya IP Office 8.1 Product Description

Avaya Session Border Controller for Enterprise

The Avaya Session Border Controller for Enterprise is a flexible, fit-for-purpose solution that includes a set of
standard security features. This Session Border Control (SBC) provides all of the functionality required for
Small-Medium enterprises to terminate SIP trunks without the complexity and higher price associated with
typical SBCs. The Avaya SBCE scales up to 150 simultaneous sessions per Portwell server (2,000 with other
server options) and is fully supported within Avaya IP Office Release 8.1.
Enterprise-Class functionality at SME Pricing
· Blocks toll fraud
· Blocks DoS, DDos and Call Walking attacks
· GUI driven
· Scalable to largest IP Office environments
· A fraction of the overall solution cost
Easily upgradable to the Avaya Session Border Controller for Advanced
· VPN-less SIP remote worker protection
· Enhanced Toll Fraud and DoS protection
The Avaya Session Border Controller for Enterprise will be included in the GSSCP reference architecture for IP
Office, as a recommended option to complement the base reference architecture, where appropriate to the
specific customer requirements.
For more information about Avaya's Session Border Controller for Enterprise, please navigate to the following
URLs:
https://enterpriseportal.avaya.com/ptlWeb/gs/products/P0996
·
https://enterpriseportal.avaya.com/ptlWeb/gs/products/P0997
·

VoIP FAQ

Network Requirements
Quality of Service (QoS) is a measure of the performance of a network that reflects the availability of network
service and the quality of network transmissions. The term itself refers to a number of networking technologies
and techniques and does not necessarily restrict itself to any single protocol or standard.
There are a number of measures that can be taken on the LAN and WAN to make them 'good enough' to carry
voice traffic. Some of these are the implementation of standards based QoS protocols while are simply a matter
of network architecture and good network management practices.
The term 'good enough' is intentional. Every customer will have different expectations and different budgets to
work to. Some will be willing to upgrade their networks to use the best possible equipment and practices. To
others the additional expense may be viewed as unnecessary.
Examples of standards based Quality of Service protocols include DiffServ and 802.1p/q.
What are Voice Compression Modules (VCM's) for?
VCM's are required to support the following scenarios:
Internal phone calls between an IP device and a non-IP device.
·
Analog/digital telephones to IP trunks (SIP/H.323) including managed Frame Relay and managed IP
·
VPN (provides echo cancellation).
IP telephones to ISDN or PSTN trunks (convert IP to TDM and vice-versa).
·
IP device to IP device
Call progress tones (for example dial tone, secondary dial tone, etc) do not require voice compression channels
with the following exceptions:
Short code confirmation, ARS camp on and account code entry tones require a voice compression
·
channel.
Devices using G.711, G.722, or G.723 require a voice compression channel for all tones except call
·
waiting.
Product Description
IP Office 8.1
© 2012 AVAYA All rights reserved.
(for future releases)
(Avaya SBCAE)
(Avaya SBCE)
Issue 26.k.- (16 August 2012)
Page 272