Avaya VF 3000 Manual Do Utilizador

 

TC; Reviewed: 
PV 04/24/2006 

Avaya – Proprietary 

Use as authorized only pursuant to your signed agreement or 

Avaya policy. No other disclosure is permitted or authorized. 

3 of 61 

HT3-LSP-VF.doc 

 

 
These Application notes provide instructions on how to configure Local Survivable Processor 
(LSP) with the Juniper VF 3000 SBC in an Avaya Hosted IP Telephony (HIPT) R3.0 Solution 
Environment. The solution described in this document requires the addition of an extra network 
element, a Network Address Translation (NAT) device at the edge of the service provider’s data 
center if customers with LSPs are to be supported.  This document covers the configuration of 
the NAT device, as well as the other components of the solution. 

 

 
The Session Border Controller (SBC) function is an essential component of the two Avaya On 
Demand/Hosted offers. The base offers for the Avaya HIPT R3.0/3.1 and Hosted Contact Center 
(HCC) R3.0 will make use of the Juniper VF 3000 SBC from the Juniper VF-Series product line.  
The Juniper VF 3000 SBC provides the Application Layer Gateway (ALG) and Network 
Address Translation (NAT) functions for the Avaya VoIP network components. The Juniper VF 
3000 SBC is deployed at the service provider’s data center and is shared amongst multiple 
enterprise customers.  The Juniper VF 3000 SBC segregates incoming traffic from different 
customers and forwards the traffic to the associated Avaya Communication Manager. All 
communication from components (i.e. endpoints, and media gateways) that passes through the 
Juniper VF 3000 SBC will appear to Avaya Communication Manager as having a Juniper VF 
3000 SBC IP address.  These components also see Avaya Communication Manager as having a 
Juniper VF 3000 SBC IP address.  The Juniper VF 3000 SBC acts as a proxy in both directions.  
The side of the Juniper VF 3000 SBC that is exposed to the Wide Area Network (WAN) is often 
referred to as the “outside” interface – the untrusted side.  The other side, the “inside” interface, 
is the trusted side and is exposed to Avaya Communication Manager and the data center 
network. 
 
Figure 1 shows the high-level network architecture for a typical Avaya On Demand/Hosted 
solution.  The data center is owned and operated by the service provider.  In this case the hosts in 
the data center are in a private address space owned and managed by the service provider.  The 
individual customer networks include Avaya G250, G350 and G700 H.248 Media Gateways and 
H.323 phones at the enterprise sites.  The media gateways may include a Local Survivable 
Processor (LSP) to support local survivability.  The enterprise site is characterized by a private 
IP address space owned and managed by the enterprise customer.  Although not shown in the 
diagram, each enterprise customer could have multiple, diversely located sites, any or all of 
which may have MGs and LSPs in addition to endpoints.  The IP address spaces in these sites are 
independent, and could overlap.  Transport between the enterprise sites and the data center in this 
example occurs over the public addressed WAN.  A NAT function is therefore required at the