Wlan Ip Telephony Manager 2245 In A Nat Environment - Avaya Communication Server 1000 Installation And Commissioning Manual

interface. Therefore, Avaya recommends that you do not use the network design shown in
Figure 21: Not recommended VoWLAN design
Figure 21: Not recommended VoWLAN design
If you deploy the VPN feature of the WLAN Handset 2212 in a mixed network where WLAN
Handsets 2211/2210s are also in use, the design recommendation becomes a little more
complex. If you place a WLAN IP Telephony Manager in the subnet with the WLAN Handsets
2210/2211, and place a WLAN IP Telephony Manager in the subnet with the VPN Router to
support the WLAN Handset 2212, admission control problems for the telephony WLAN can
occur. Each WLAN IP Telephony Manager counts the number of their own devices placing
calls over APs, but does not count the number of calls controlled by the other WLAN IP
Telephony Manager. This creates a blind spot for each device, and it is possible to
oversubscribe an AP by up to 2:1. The best solution to this problem is to have the WLAN
Handsets 2210/2211 handsets use the same WLAN IP Telephony Manager as the WLAN
Handset 2212 (VPN). This WLAN IP Telephony Manager is on the other (remote) side of the
VPN Router from the handsets, that is, over a routed hop.

WLAN IP Telephony Manager 2245 in a NAT environment

The IP Telephony Manager 2245 must be in constant communication with the handsets to
ensure handset functionality. Since the IP Telephony Manager 2245 must be on the same
subnet as the handsets, the IP Telephony Manager 2245 must be located on the private side
Avaya WLAN IP Telephony Installation and Commissioning
on page 95 as a design for the VPN feature.
NAT
November 2010 95