Abstract. CRK; Reviewed: WCH/JK 9/11/2002. Solution & Interoperability Test Lab Application Notes 2002 Avaya Inc. All Rights Reserved.

Similar documents
Abstract. CRK; Reviewed: WCH/MIC 2/24/2003. Solution & Interoperability Test Lab Application Notes 2003 Avaya Inc. All Rights Reserved.

Configuring devices for the Avaya Disaster Recovery Unit (DRU) Solution Issue 1.0

Configuring the Avaya S8300 Media Server with Avaya G700 Media Gateway in a Stack With Other Avaya P330 Multilayer Stackable Switches Issue 1.

How to Configure an Avaya TM IP600 Server With MultiTECH Systems MVP200 Gateway - Issue 1.0

Application Notes for Telrex CallRex with Avaya IP Office - Issue 1.0

Abstract. WJR; Reviewed: WCH 3/4/2003. Solution & Interoperability Test Lab Application Notes 2003 Avaya Inc. All Rights Reserved.

How to configure an H.323 IP trunk between an Avaya IP600 Internet Protocol Communication Server and Avaya IP Office Server - Issue 1.

Abstract. AM; Reviewed: WCH/JK 2/28/2003. Solution & Interoperability Test Lab Application Notes 2003 Avaya Inc. All Rights Reserved.

Abstract. Avaya Solution and Interoperability Test Lab

Configuring the Avaya SG203 Security Gateway to Support H.323 IP Trunking over Port Network Address Translation (PNAT) - Issue 1.0

Application Notes for the Allot NetEnforcer with Avaya Communication Manager - Issue 1.0

IP Office - Job Aid Connecting an IP600 and IP Office via H323 IP Trunk

Configuring Avaya IP Softphone with Video and Polycom VSX 3000 with Avaya Communication Manager Issue 1.0

Application notes for Algo 8028 SIP Doorphone with Avaya IP Office Release 7.0 Issue 1.0

Application Notes for Configuring 2N Telekomunikace Helios IP to interoperate with Avaya IP Office Issue 1.0

A Configuration of Avaya Communication Manager and a 3COM NBX 100 PBX using QSIG PRI Networking - Issue 1.0

Application Notes for Configuring Computer Instruments e-ivr, as a H.323 endpoint, with Avaya IP Office 500 V2 Issue 1.0

Application Notes for Configuring Computer Instruments e-ivr, as a SIP endpoint, with Avaya IP Office 500 V2 Issue 1.0

Abstract. Avaya Solution & Interoperability Test Lab

Application Notes for the ADTRAN NetVanta 3205 Access Router and Avaya IP Office Using PPP - Issue 1.0

Application Notes for D-Link DES 1526 Power over Ethernet (PoE) Switch with Avaya IP Telephones and Wireless Access Points Issue 1.

Abstract. Avaya Solution & Interoperability Test Lab

A Sample Configuration for Securing Avaya IP Softphone Clients over a Wireless LAN using Avaya VPNremote Software and IP Address Pooling - Issue 1.

Application Notes for Configuring SIP Trunking between the Comdasys Mobile Convergence Solution and an Avaya IP Office Telephony Solution Issue 1.

Application Notes for Empix evolve Fax Server with Avaya IP Office Issue 1.0

Configuring SIP Telephony between Avaya one-x Quick Edition IP Telephones and Avaya Communication Manager with Avaya SIP Enablement Services Issue 1.

Abstract. Avaya Solution & Interoperability Test Lab

Sample Configuration of Avaya Distributed Office s Dynamic Host Configuration Protocol (DHCP) to support Multiple IP Networks Issue 1.

Application Notes for Configuring Cablevision Optimum Voice SIP Trunking with Avaya IP Office - Issue 1.1

Application Notes for Configuring Citel s Portico TVA with Avaya IP Office Issue 1.0

Application Notes for Configuring the ADTRAN NetVanta UC Server with Avaya IP Office 6.1 Issue 1.0

Application Notes for Convergys Intervoice Media Server with Avaya Aura TM Communication Manager and Avaya Aura TM SIP Enablement Services - Issue 1.

Abstract. Avaya Solution & Interoperability Test Lab

Application Notes for the RedSky Technologies E-911 Manager with Avaya Communication Manager - Issue 1.0

Application Notes for Cantata SR140 with Avaya Communication Manager - Issue 1.0

Application Notes for Configuring Sonexis ConferenceManager with Avaya IP Office using a SIP trunk Issue 1.0

Application Notes for the LifeSize Phone with Avaya Communication Manager and Avaya SIP Enablement Services Issue 1.0

Application Notes for Infoblox DNSone in an Avaya IP Office IP Telephony Infrastructure Issue 1.0

Application Notes for Configuring Windstream SIP Trunking with Avaya IP Office - Issue 1.0

Application Notes for Configuring NovaLink NovaTax with Avaya IP Office Issue 1.0

Application Notes for Resource Software International Visual Rapport with Avaya IP Office Issue 1.0

Application Notes for Multi-Tech FaxFinder IP with Avaya IP Office Issue 1.0

Application Notes for Konftel 300 Conference Unit with Avaya Communication Manager - Issue 1.0

Application Notes for the Aculab GroomerII with Avaya Communication Manager Issue 1.0

Abstract. KT/FS; Reviewed: WCH 6/3/2003. Solution & Interoperability Test Lab Application Notes 2003 Avaya Inc. All Rights Reserved.

Application Notes for Firetide Wireless Mesh Network with an Avaya IP Telephony Infrastructure - Issue 1.0

Application Notes for the Aculab GroomerII with Avaya SIP Enablement Services 3.1 and Avaya Communication Manager Issue 1.

Application Notes for the Grandstream Networks SIP Telephones with Avaya Communication Manager and Avaya SIP Enablement Services Issue 1.

Application Notes for DiVitas Mobile Unified Communications with Avaya Communication Manager and Avaya SIP Enablement Services Issue 1.

Abstract. Avaya Solution & Interoperability Test Lab

Sample Configuration for SIP Trunking between Avaya IP Office and Cisco Unified Communications Manager 7.0 Issue 1.0

Application Notes for Intego Systems ProNet.net Nurse Call System with Avaya Communication Manager using Avaya SIP Enablement Services Issue 1.

Abstract. Avaya Solution & Interoperability Test Lab

Application Notes for Phonect SIP Trunk Service and Avaya IP Office 7.0 Issue 1.0

Abstract. Avaya Solution & Interoperability Test Lab

Application Notes for Configuring Tidal Communications tnet Business VoIP with Avaya IP Office using SIP Registration - Issue 1.0

Application Notes for 911 ETC CrisisConnect for Softphones and CrisisConnect for VoIP with Avaya IP Office Issue 1.0

Abstract. Avaya Solution & Interoperability Test Lab

Abstract. Avaya Solution & Interoperability Test Lab

Application Notes for Avaya IP Office Release 8.0 with AT&T Business in a Box (BIB) over IP Flexible Reach Service Issue 1.0

Application Notes for MVOX Electronics MV100 and MV900 with Avaya IP Softphones - Issue 1.0

Abstract. Avaya Solution & Interoperability Test Lab

Application Notes for Configuring SIP Trunking between CenturyLink SIP Trunk (Legacy Qwest) Service and Avaya IP Office R8.0 (16) Issue 1.

Application Notes for TAS FEP-IP Flush-mounting Telephone with Avaya Communication Manager and Avaya SIP Enablement Services Issue 1.

Application Notes for OrecX s Oreka Total Recorder with Avaya Aura Communication Manager and Avaya Aura Application Enablement Services Issue 0.

Application Notes for Empix evolve v3.1 Skypetophone with Avaya IP Office 7.0 Issue 1.0

Abstract. Avaya Solution & Interoperability Test Lab

Configuring Extreme Networks Summit WM20 WLAN Switch to support Avaya Wireless IP Telephones Issue 1.0

Application Notes for 911 ETC CrisisConnect for Softphones and CrisisConnect for VoIP with Avaya IP Office Issue 1.0

Application Notes for Empirix Hammer FX-IP with Avaya Communication Manager using the H.323 IP Trunk Interface Issue 1.0

Abstract. Avaya Solution & Interoperability Test Lab

Application Notes for MultiTech CallFinder CF220 with Avaya IP Office - Issue 0.1

Application Notes for Revolabs FLX UC 1000 with Avaya Aura Communication Manager and Avaya Aura Session Manager Issue 1.0

Abstract. Avaya Solution & Interoperability Test Lab

Application Notes for Verint Systems Audiolog with Avaya Communication Manager using Avaya Application Enablement Services Issue 1.

Application Notes for the CTI Data Solutions Proteus Office 5.0 with Avaya Communication Manager - Issue 1.0

Application Notes for Configuring Objectworld CallAttendant Office Analog Integration with Avaya IP Office - Issue 1.0

Application Notes for Mirage Networks Endpoint Controller in an Avaya IP Telephony Infrastructure Issue 1.0

Application Notes for the SDC IntelliSPEECH with Avaya Communication Manager - Issue 1.0

Application Notes for Configuring Firetide HotPort 3103 Wireless Mesh Nodes to Support Avaya VoIP Communication via a Wireless Mesh Network Issue 1.

Application Notes for the Packeteer PacketShaper with Avaya Communication Manager - Issue 1.0

Application Notes for VXi BlueParrott Bluetooth Headsets with Avaya one-x Agent - Issue 1.0

Abstract. Avaya Solution & Interoperability Test Lab

Application Notes for Configuring the Wavelink Mobile Manager to Manage Avaya AP-3 and AP-4/5/6 Wireless Access Points - Issue 1.0

Application Notes for Noble Systems with Avaya Aura TM SIP Enablement Services and Avaya Aura TM Communication Manager Issue 1.1

Application Notes for MultiTech FaxFinder with Avaya IP Office Issue 1.0

Application Notes for the ISI Telemanagement Solutions Infortel Select with Avaya Communication Manager - Issue 1.0

Abstract. Avaya Solution & Interoperability Test Lab

Application Notes for Configuring Avotus ICM Usage Management with Avaya Aura Communication Manager and Avaya Aura Session Manager Issue 1.

Application Notes for MultiTech FaxFinder IP with Avaya IP Office Issue 1.0

Application Notes for Infoblox DNSone in an Avaya Communication Manager Wireless IP Telephony Infrastructure Issue 1.0

Abstract. Avaya Solution & Interoperability Test Lab

FREUND SIP SW - V SIP-server setup

Application Notes for Tri-Line TIM Enterprise with Avaya Communication Manager - Issue 1.0

Application Notes for OneAccess-Telstra Business SIP with Avaya IP Office Release 11 SIP Trunking - Issue 1.0

Application Notes for Objectworld UC Server with Avaya IP Office Using TAPI Analog Integration Issue 1.0

Abstract. Avaya Solution & Interoperability Test Lab

Abstract. Avaya Solution & Interoperability Test Lab

Application Notes CommView CPE with Avaya Communication Manager Issue 1.0

Application Notes for Konftel 300IP with Avaya Communication Manager - Issue 1.0

Transcription:

Configuring T1 / PPP Connectivity using Avaya IP Office, Avaya IP600 Internet Protocol Communication Server, Lucent Access Point Router 1000, and Avaya P330R Multilayer Stackable Switch with X330WAN Module Issue 1.0 Abstract These Application Notes describe the setup and configuration of the following devices in a T1 / PPP Network Configuration: Avaya IP600 Internet Protocol Communications Server, Avaya IP403 Office Server, Avaya Call Processing Platforms, Lucent AP1000, Avaya IP Telephones, Avaya IP Softphone, Avaya IP Phone Manager for IP403 Office, Avaya P130 Workgroup Ethernet Switch, and Avaya P333R Switch with X330W-2DS1 WAN module. 1 of 22

1 2 3 4 5 6 7 8 9 * 8 # 1 2 3 4 5 6 7 8 9 * 8 # 1. Introduction These Application Notes describe the setup and configuration of the following devices that are included in a T1/PPP network: Avaya IP600 Server, Avaya IP403 Office Server, Lucent AP1000, Avaya IP Telephones, Avaya IP Softphone, Avaya IP Phone Manager for IP403 Office, Avaya P130 Switch, and Avaya P333R Switch with X330W-2DS1 WAN module. A detailed illustration of the configurations tested along with a list of test equipment is contained herein. The diagram depicted in Figure 1 represents the verified network topology. T1 / PPP was used between the IP Office WAN module and routers. The IP Office WAN module was used in bridge mode. The AP1000 and P330R routers are not connected at the same time. Hammer Chariot Server Smartbits Digital Phone.101 FAX 1 IP Telephone 1 Analog Phone.201 IP Phone Manager Sniffer IP Office Server.2 Controller.199 Office Manager T1/PPP AP1000.1.1 P333R.1.1 P330R / WAN P130 Switch.201 IP Softphone.101 IP Telephone 2 C-LAN.23.24 MEDPRO Analog Phone IP600 Server FAX 2 Digital Phone 192.16.5.0 / 24 192.16.20.0 / 24 Figure 1: Network Configuration The IP addresses in the table below were used in the network configuration shown in Figure 1. Device Name IP Address Comments Avaya IP403 (Controller) 192.16.5.2 Default Gateway is 192.16.5.1 Avaya IP600 (C-LAN) 192.16.20.23 Default Gateway is 192.16.20.1 (MEDPRO) 192.16.20.24 Avaya X330W_2DS1 2 of 22

Device Name IP Address Comments T1 Fast Ethernet 134.1.5.1 134.1.20.1 AP 1000 T1 Eth 11 134.1.5.1 134.1.20.1 For T1/ PPP configuration Subnet for IP600 IP Office T1 WAN module - Unnumbered / Bridged mode Avaya P130 - IP Telephone-1 192.16.5.101 IP Telephone-2 192.16.20.101 IP Office Manager 192.16.5.199 IP Phone Manager 192.16.5.201 IP Softphone 192.16.20.201 2. Equipment and Software Validated The following software/firmware versions were used during the testing: Equipment Avaya IP600 Internet Protocol Communication Server Avaya IP403 IP Office Firmware Avaya IP Phone Manager 1.2.4 Avaya P130 2.5.3 Avaya P333R 3.9.1 Avaya X330W_2DS1 module 3.9.7 Avaya IP Telephone(s) 1.6 Version R011c.01.0.037.2 3.1(25) 1.1 (27) Avaya IP Softphone(s) 3.2.3 Lucent AP 1000 2.5.0.R3.1 QVPN 3. IP600 Communication Server Configuration An assumption was made that IP600 Communication Server was installed correctly before configuring the devices. The basic administration task order is as follows: Setup udp (Uniform Dialing Plan) Setup ip-network-region Setup ip-codecs Setup node-names ip Setup ip-interfaces Setup data-module Setup signal-group 3 of 22

Setup trunk-group Setup aar (Automatic Alternate Routing) Setup route-pattern 1 Configure the Uniform Dial Plan In this configuration a 5-digit dial plan was used with the following extension ranges: IP600 Local: 400xx for analog phone, digital phone and IP Telephone 2xxxx for Data Modules IP Office Site: 7xxxx for all phones, mapped to AARCode 700 The routing configuration to the IP Office Site will be shown in later steps. It should be noted that the dial plan and routing configuration to the IP Office Site is dependent on what is already configured at the IP Office Site. This is an example of what was used to verify the configuration. At the prompt, type change dialplan. Match the parameters of the screen shown below, then hit Enter to apply the changes. This configures the five-digit dial plan. At the prompt, type change udp 7. Enter AARCode 700 as shown below and hit Enter to apply the changes. 4 of 22

Similarly type the change udp 2 and change udp 4 to assign Local to Ext Code 2xxxx and 4xxxx. 2 Configure the IP Network Region. At the prompt, type change ip-network-region 1. Match the parameters of the screens shown below, then hit Enter to apply the changes. 5 of 22

3 Select the codecs to be used. At the prompt, type change ip-codec-set 1. The codec(s) that are available are listed here. 4 Assign node names and IP address to each node in the network. At the prompt, type change node-names ip. Create node names and IP addresses for each board as shown below, then hit Enter to apply the changes. Note that an IP address for the IP Office Controller board has also been created. Refer to Figure 1. 6 of 22

5 Define the IP interfaces for C-LAN and MEDPRO boards. At the prompt, type change ip-interfaces and enter the type, slot location, name, gateway address, and network region for each IP interface board. Then hit Enter to apply the changes. Note: The slots have to match. If the C-LAN and MEDPRO boards are not in the same slots shown below, you have to change the slot parameter on the ip-interface screen to match your physical board location. 6 Configure a Link on an Ethernet Data Module for the C-LAN. At the prompt, type add data-module 20001 and match the parameters of the screen shown below. The port has to match with the physical C-LAN slot in the IP600. 01A04 indicates the location of the C-LAN board, and 17 is the required port #. 7 Configure a signaling group. At the prompt, type add signaling-group 7. The following information should be created / changed to match your network settings. Group Type = h.323 Near-end Node Name = 18D1CLAN10 7 of 22

Far-end Node Name = IP400CLAN Far-end Listen Port = 1720 Calls Share IP Signaling Connection = y (This statement is needed to receive multiple calls from IP Office. When IP Office sends multiple calls, they share a signaling connection.) The field Trunk Group for Channel Selection must be left blank when adding the signaling group. Hit Enter to apply the changes and continue with the next step to add trunk group 7. When the trunk group is completed, issue the change signalinggroup 7 command, type 7 in the Trunk Group for Channel Selection field and hit Enter to apply the changes. 9 Configuring a trunk group. At the prompt, type add trunk-group 7. The following information should be created / changed to match the network settings. On page 1 of 10: Group Type = isdn TAC =100 (could be 1xx) Group Name = Call to IP400 (any name) Service Type = Tie Carrier Medium = IP 8 of 22

On page 2 of 10: Send Name = y Send Calling Number = y Send Connected Number = y On page 4 of 10: Port = ip Sig Grp = 7 Note: On the Port field type ip. After the configuration is applied, the virtual IP port 9 of 22

that was assigned (e.g.t00001), as shown below, can be seen if the display or change trunk-group 7 commands are issued. The number of ports entered determines the # of simultaneous calls that will be allowed over the trunk. Hit Enter to apply the changes. The Trunk Group for Channel Selection field, in the signaling-group must now be set to 7. The first step is to take the link out of service by typing busy signalinggroup 7. Type change signaling-group 7, and set the Trunk Group for Channel Selection field to 7. Hit Enter to apply the change. Then, type release signalinggroup 7 to bring it into service. 10 Set AAR to route calls to IP Office. As stated before, the extensions in the IP Office were assigned in the 7xxxx range and mapped to AARCode 700 At the prompt, type change aar analysis 700. Match the parameters show below for the dialed string 700. Seven (7) was selected as the route pattern used to route the calls. 11 Create a route pattern for routing to IP Office. At the prompt, type change route-pattern 7. Set the Group No to match the Trunk Group previously configured (7). Set the FRL to 0. Set the No Del Dgts (number of 10 of 22

deleted digits) to 3. Set the Inserted Digits to 7. The Inserted Digits (7) must match the leading digit of the 5-digit number; in this example the digit happens to be 7. If a 4-digit dial plan is being used, then there is no need to insert any digits. 12 Create stations. Note that the add station command is used to add a new station, and the change station command is used to make changes after a station is created. Included are screens of two IP station forms. DCP and Analog stations are added in a similar manner, but the Type and Port they are connected to must be specified. Create an IP Softphone station: At the prompt, type add station 40060. Provide following information. Name = (Choose any name) Type = 4624 Security Code = 1234 (This is needed for the IP Softphone to register) IP Softphone? = y 11 of 22

Create an IP Telephone station: At the prompt, type add station 40040. Provide following information. Name = (Choose any name) Type = 4624 (This must match the IP Telephone type used) Security Code = 1234 (This is needed for the IP Telephone to register) For analog and DCP stations, the type of the phone and its port need to be provided. 8. IP Office Communication Server Configuration The following steps were used to configure the IP400 Server. 1 Select Start! Programs! IP Office! Manager Provide the password. 2 Select File! Open Provide the password for entering the controller card. Click OK 12 of 22

3 Double click System on the main menu to setup the Controller card. On the System tab, provide the following information: o TFTP Server IP address = 192.16.5.199 (IP Office Manager IP address) On the LAN1 tab, provide the following information: o IP address (controller) = 192.16.5.2 o IP Mask = 255.255.255.0 o Click disabled on DHCP Mode. On the Gatekeeper tab, do the following: o Un-click Auto-create Extn Enable o Click OK 4 s 4 through 7 are for configuring T1 / PPP connection parameters. Select Line on the main menu. Edit the Line 05 by double clicking it. Select Line Sub Type to T1 13 of 22

Select Channel Allocation to 1! 24 Select Type value to Clear Channel 64K by double clicking each channel. Click OK 5 Select Service from the main menu. With the right mouse button, select New. o On the Type of Service menu, click WAN Service. Click OK On the WAN Service menu, provide the following information. o On the Service tab, create the name wan_link. o On the PPP tab, click IP Header Compression, and Multilink. Select Disable for Compression Mode and Callback Mode. Click OK Note: An IP address was not specified for the WAN port. Therefore, the WAN port is being used as a bridge. 6 Select WANPort on the main menu. With the right mouse button, select New and provide the following information. o Name = LINE5.0 o Speed = 64000 (This is the bandwidth setting at the IP Office side) o Mode = SyncPPP o RAS Name = wan_link Click OK 7 Select Line on the main menu. With the right mouse button, select New. Provide the following information. o Incoming Group ID = 7 o Outgoing Group ID = 7 On the VOIP tab, provide the IP600 C-LAN IP address, which is 192.16.20.23 in this example. Click OK 8 Select Extension on the Main menu. Create 3 extensions (IP Telephone, analog phone and DCP station) With the right mouse button, select New. On the Extn tab, provide the following information. o Extension ID = 8001 o Extension = 70101 (This is the extension for the IP phone) 14 of 22

Click OK Repeat this step to create more IP Telephones. 9 Click extension ID 74. This extension will be used for setting up an analog phone. On the Extn tab, provide the following information. o Extension = 70201 (This is the extension for the analog phone) Click OK Click extension ID 63. (This extension will be used for setting up a DCP station) On the Extn tab, provide the following information. o Extension = 70203 (This is the extension for the DCP station) Click OK 10 Select User on the main menu Using the right mouse button, select New. Create a name for each phone. This screen illustrates how to change the associated phone name (analog, digital and IP Telephone). For the IP Telephone, a password also needs to be provided. 15 of 22

11 Select IP route on the main menu. With the right mouse button, select New for a static route. The following screen shows the default gateway route. 12 Select HuntGroup on the Main Menu. With the right mouse button, select New. Provide the following information. o Name= Main o Hunt Type = Group o Extension = 70000 Click OK 13 Select Short Code from the Main Menu. With the right mouse button, select New. Provide the following information. o Short Code = 4xxxx (dialing plan for IP600) 16 of 22

o Telephone Number = 4NJ (4N indicates to send the entire digit string, J bypasses the need to append # after the digits) o Line Group = 7 Click OK 9. Configuring the Avaya IP Telephone 2 manually. 1. During the normal start up process of the IP Telephone o Hit the star key (*) when prompted, OR o While the IP Telephone is on-hook and idle, press Mute 2337# to access the address information programming. 2. On the Keypad o Enter the IP Address for the IP Telephone 192.16.20.101 followed by #. o Enter the IP address of the gatekeeper/call server (C-LAN board) 192.16.20.23 followed by #. o Enter Port number 1719 followed by #. o Enter the IP address of the gateway/router 192.16.20.1 followed by #. o Enter the subnet mask of the gateway/router 255.255.255.0 followed by #. o Press pound (#) to save changes or star (*) to discard changes. 10. Configuring the Avaya IP Softphone 1. Start the IP Softphone by double-clicking the IP Softphone icon. 2. On the <Login> window, enter the following information: o Extension 40060 o Password 1234 o Server Address 192.16.20.23(C-LAN IP Address) o Bandwidth Setup Local Area Network Note: The extension and password has to match what was configured on the IP600 Server. Click Login Verify calls can be placed 3. On the <Avaya IP Softphone 40060> window, enter the following information: o Extension 40040 (IP Telephone extension) Press Return The Digital extension (x40040) will ring. When the phone is answered, the call is established between the IP Softphone (x40060) and the IP Telephone extension (x40040). 17 of 22

11. Configuring the Avaya X330W-2DS1 WAN module Ensure that the latest version of firmware is installed in the Avaya P330R switch and WAN module. It should at least be what is shown in section 2. 1 Start a HyperTerminal session to the WAN module " Bits per second 9600 " Data bits 8 " Parity None " Stop bits 1 " Flow control None 2 Enter User Name and Password. 3 Go to configuration mode by typing config. " X330WAN-2DS1-1 (super)# config The prompt will change. " X330WAN-2DS1-1 (configure)# 4 Add an IP address for the FastEthernet interface. " X330WAN-2DS1-1 (configure)# interface FastEthernet1 " X330WAN-2DS1-1 (config-if:fastethernet1)# ip address 192.16.20.1 255.255.255.0 " X330WAN-2DS1-1 (config-if:fastethernet1)#exit 5 Add an IP address for T1 interface. " X330WAN-2DS1-1 (configure)# interface serial 1:0 " X330WAN-2DS1-1 (config-if:serial1:0)# ip address 192.16.5.1 255.255.255.0 Turn on RTP Header Compression. " X330WAN-2DS1-1 (config-if:serial1:0)# ip rtp header-compression " X330WAN-2DS1-1 (config-if:serial1:0)# ip rtp compression-connections 500 Assign the bandwidth. " X330WAN-2DS1-1 (config-if:serial1:0)# bandwidth 64000 (The bandwidth setting on the X330WAN module has to match with the IP Office bandwidth for PPP negotiation to be successful.) " X330WAN-2DS1-1 (config-if:serial1:0)#exit Configure the T1 physical parameters " X330WAN-2DS1-1 (configure)# controller t1 1 " X330WAN-2DS1-1 (config-controller)# linecode b8zs " X330WAN-2DS1-1 (config-controller)# framing esf " X330WAN-2DS1-1 (config-controller)# clock source internal " X330WAN-2DS1-1 (config-controller)# channel-group 0 timeslots 1 speed 64 " X330WAN-2DS1-1 (config-controller)# exit Set the arp timeout to 120 seconds. If the default arp timeout is used, calls from the IP600 Server to IP Office consistently drop after 10 minutes. With an arp timeout of 120 seconds, the calls do not drop. " X330WAN-2DS1-1 (configure)# arp timeout 120 Save the configuration " X330WAN-2DS1-1 (configure)#copy run start 18 of 22

12. Configuring the AP1000 Router 1 One fast Ethernet interface and one T1 interface were used. The T1 interface was connected to the Avaya IP Office WAN (T1 / PPP) module. 2 Change the T1 setting to PPP. " > stack slot.1.1 cbq.1 t1.1 ppp.1 ip.1 3 Create an IP address for each interface. " > add ip.1 address.192.16.5.1 net-mask 255.255.255.0 " > add ip.11 address.192.16.20.1 net-mask 255.255.255.0 Use the show command to verify the IP configuration. 4 Match the T1 parameters with the T1 setting on the Avaya X330W_2DS1 module. " > config t1.1 physical-layer data-link-facilities dsx1fdl-none line-type t1esf line-coding b8zs interface-type t1csu00dba clock-source internal timeslot 1-1 Use the show command to verify the T1 physical configuration. 19 of 22

13. Configuring the Avaya IP Phone Manager To run IP Phone manager for IP403 Office, a Dongle and a License key are needed. The Dongle needs to be attached to the parallel port of the IP Office Manager PC. The license needs to be installed in the IP Office manager. In the verification of this configuration the IP phone manager was installed in a laptop computer. Installing the Software 1 " Install the software by running setup.exe " Click Finish on the installation wizard " Click Next on the InstallShield Wizard " Provide a destination location and click Next " Click Next on the Select Components page " Click Next " Click Finish Configuring the PBX information 2 " Select Start! Programs! IP Office! PhoneManager " Select Config! PBX " On the Configuration Window, provide the following information. o User Name = Extn102 o Password = 1234 (must match the PBX configuration) o PBX Address = 192.16.5.2 (Controller IP address) " Click OK In IP Office Manager, a user name and extension for each IP PhoneManager must be created. 3 " To make a call, select Functions! Call or Call icon. " On the Call window: o Enable Show Users o Enable Show Hunt Group o Enable Show Directory These directory features make it easier to place calls. 20 of 22

" To place the call select a user or provide an extension and click Call. 14. Configuring the Avaya IP Telephone 1 1 " During the normal start up process of the IP Telephone o Hit the star key (*) when prompted, OR o While the IP Telephone is on-hook and idle, press Mute 73738# to RESET system initialization values to defaults and/or RESET the telephone. 2 " On the Keypad o Enter the IP Address of phone 192.16.5.101 followed by pound (#). o Enter the IP address of the gatekeeper/call server (Controller board) 192.16.5.2 followed by pound (#). o Enter the CallSvPort number 1719 followed by pound (#). o Enter the IP address of the gateway/router 192.16.5.1 followed by pound (#). o Enter the subnet mask of the gateway/router 255.255.255.0 followed by pound (#). o Enter the IP address of the file server (TFTP) 192.16.5.199 followed by (#) o Press pound (#) to save changes or star (*) to discard changes. o The phone will re-initialize. o After the re-initialization, you will be prompted for an extension. Provide the following information. Extension = 70101 Followed by (#) Password = 1234 followed by (#) Note: Since the download process takes more than one initialization, be patient and the phone should be operational in 3-5 minutes. 15. Conclusion After the procedures described in these application notes are followed, the user will be able to place calls and send data between both sides of the network. Each configuration section has a verification step where appropriate. These Application Notes will help engineers who need to configure IP Office in a T1 network using Point-to-Point Protocol (PPP). They show that IP Office is a suitable solution for a small or regional office to connect to the central office using T1. 21 of 22

Avaya and the Avaya Logo are trademarks of Avaya Inc. All trademarks identified by and are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners. The information provided in these Application Notes is subject to change without notice. The configurations, technical data, and recommendations provided in these Application Notes are believed to be accurate and dependable, but are presented without express or implied warranty. Users are responsible for their application of any products specified in these Application Notes. Please e-mail any questions or comments pertaining to these Application Notes along with the full title and filename, located in the lower right corner, directly to the Avaya Solution & Interoperability Test Lab at interoplabnotes@list.avaya.com 22 of 22