Abstract. Avaya Solution & Interoperability Test Lab

Transcription

1 Avaya Solution & Interoperability Test Lab Provisioning the Teldat VyDa-M SIP Router/Gateway to Provide SIP Registration and Proxy Functionality to Avaya 9600 Series Telephones running Avaya one-x Deskphone Edition (SIP) Software - Issue.0 Abstract These Application Notes describe provisioning of the Teldat VyDa-M SIP Router/Gateway to provide SIP registration and proxy functionality to Avaya 9600 Series Telephones running Avaya one-x Deskphone Edition (SIP) Software, provisioned for an Avaya environment. In addition, provisioning the Teldat VyDa-M SIP Router/Gateway to provide SIP to BRI gateway functionality to an Avaya G250 Media Gateway is also discussed. These Application Notes were written in response to a customer Proof Of Concept request. of 30

2 . Introduction Equipment and Software Validated Teldat VyDa-M Platform Teldat VyDa-M Platform Front Panel Teldat VyDa-M Hardware Rear Panel Console Interface Fast Ethernet Interfaces BRI Interfaces G729 Codec Preferences Configuring the Teldat VyDa-M SIP Router/Gateway Teldat VyDa-M Command Line Interface (CLI) Rebooting the VyDa-M Navigating Between Processes Displaying the VyDa-M Configuration Teldat VyDa-M Provisioning Global Dial Profile Telephony Dial Peers Network Ethernet Interface Network BRI Avaya Certificates DHCP Configuring the Avaya 96xx SIP Telephones Configuring Avaya Communication Manager/Avaya G250-BRI Media Gateway Prerequisites BRI Trunk BRI Board BRI Trunk Call Routing AAR Feature Access Code AAR Analysis Route Pattern Codecs Verification s BRI Trunk Status DHCP and SIP Registration Telephony Teldat VyDa-M SIP Protocol Analyzer Conclusion Appendix References Teldat Avaya Teldat VyDa-M Configuration of 30

3 . Introduction This document describes using Avaya 9600 Series Telephones running Avaya one-x Deskphone Edition (SIP) Software, operating in the default Avaya SIP environment configuration, with a Teldat VyDa-M SIP Router/Gateway (VyDa-M). SIP telephone registration, basic SIP telephony, as well as BRI trunking is described. The VyDa-M functions as a SIP registrar, a SIP Proxy, and as a SIP Gateway. The SIP registrar function was tested by having the Avaya 9600 SIP Telephones register to the VyDa-M. The SIP proxy function is tested by defining a dial plan on the VyDa-M and placing calls between the Avaya 9600 SIP Telephones. Call Hold/Release and Attended/Unattended Transfer was also tested. The VyDa-M supports TLS and SRTP. Avaya certificates are installed on the VyDa-M SIP for interoperability with the Avaya 9600 SIP Telephones. Use of encryption for transport and media is verified. The VyDa-M also supports a BRI interface. The BRI interface is used to test the SIP gateway function. Note - The VyDa-M does not do SIP registration/authentication. Therefore the Avaya 9600 SIP Telephone user may submit any value when entering Username and Password on the Avaya 9600 SIP Telephones. However the Username value must be a digit string matching the dial plan provisioned in the VyDa-M. The test environment is comprised of two locations, Location A and Location B. Location A contains the VyDa-M and the Avaya 9600 SIP Telephones. The VyDa-M provides SIP registration and proxy functions in lieu of an Avaya SIP Enablement Services server (SES). Location A also contains a Windows XP PC operating as an HTTP server. The HTTP server contains the Avaya 9600 SIP Telephones settings file (see Section 5) that directs the Avaya 9600 SIP Telephones to their SIP proxy (the VYDa-M). Location B contains an Avaya S8300 Server, running Avaya Communication Manager, an Avaya G250-BRI Media Gateway, and Avaya H.323 and analog phones. No SIP processing is performed in this location. A BRI circuit is provisioned between the VyDa-M in Location A and the Avaya G250-BRI Media Gateway in Location B. The reference configuration is shown in Figure. 3 of 30

4 Figure : Teldat VyDa-M Test Reference Configuration 2. Equipment and Software Validated The following equipment and software were used for the sample configuration provided: Equipment Software Avaya Communication Manager R04x (4.0.) Avaya G250-BRI Media Gateway 27.2 Avaya 9620 Telephone Avaya one-x Deskphone Edition (SIP) Software (20) Avaya 9630 Telephone Avaya one-x Deskphone Edition (SIP) Software (20) Avaya 9640 Telephone Avaya one-x Deskphone Edition (SIP) Software (20) Avaya 462 H.323 telephone a20d0b2_8.bin Avaya 2500 analog telephone - Teldat VyDa-M SIP Router/Gateway with 3 port BRI Interface. 4 of 30

5 3. Teldat VyDa-M Platform The VyDa-M SIP Router/Gateway platform used in the reference configuration is shown in Figures 2 and Teldat VyDa-M Platform Front Panel The front panel of the VyDa-M contains interface status indicators. It also has a slot for a Smart-Card. The Smart-Card is used to save the configuration. By default, when the Smart- Card is present, the configuration is saved in the Smart-Card and also in the VyDa-M flash memory. If the Smart-Card is not present, the configuration is only saved in the VyDa-M flash memory. Teldat VyDa-M Front Panel Figure 2 5 of 30

6 3.2. Teldat VyDa-M Hardware Rear Panel The rear panel contains the various network interfaces. Teldat VyDa-M Rear Panel Figure Console Interface The console interface is labeled CONF. The connection is 9600, 8, N,, and no flow control. A DB9 console cable is supplied with the VyDa-M. All of the provisioning described in these Application Notes is performed via the console connection. The VyDa-M also supports access via Telnet. Access via SSH is not supported at this time. The VyDa-M does not support a web interface at this time Fast Ethernet Interfaces The two Fast Ethernet interfaces are labeled FE0 and FE. These interfaces support auto speed and duplex negotiation BRI Interfaces The VoIP BRI interface card is located in Slot. The BRI interface card has three interfaces. The BRI interfaces are labeled and 2. The center BRI interface is a bypass interface for BRI interface only. The bypass interface can be used if the VyDa-M loses power. The BRI interfaces can be configured as an NT or TE interfaces. If a BRI interface is configured as TE, a BRI cross-over cable is required to connect to an NT device. If the BRI interface is configured as NT, the interface provides the cross-over connection internally. The VyDa-M uses the Euro-ISDN BRI standard (see Section 4.2.4). 6 of 30

7 The VyDa-M keeps the BRI interface powered off until it detects a call therefore even though the physical connections may be in place, the green LED status indicator will remain off until a call is detected. Normally this is not an issue since the BRI interface is connected to a central office. However if the VyDa-M BRI interface is connected directly to Avaya Communication Manager, the Avaya BRI trunk will be out-of-service. Alternatively the BRI interface may be activated manually (see Section ). By default the BRI interface is configured to use G7U and G723 codecs. This can be changed to G7U and G729(B) by entering the dsp-firmware g729-g7 command for the appropriate BRI VoIP interface (see Section ). If the system configuration displays the entry dspfirmware g729-g7, then the BRI interface is G7U/G729. If no dsp-firmware line is displayed then the BRI interface is G7U/G723. Note There is a single BRI interface located next to the CONF interface. This BRI interface is for an ISDN BRI device such as a phone. A switch labeled Term activates or deactivates the isdn bus termination resistance as required G729 Codec Preferences The VyDa-M supports the G.729B codec (annexb=yes). It does not support G.729A (annexb=no). When specifying G729 codec, the VyDa-M does not specify the annexb=yes/no parameter in the SIP SDP header. Therefore recipients must interpret this as G729B. For SIP to SIP calls the VyDa-M will leave the endpoints to negotiate codecs between themselves. However if the VyDa-M originates a SIP call (e.g. BRI to SIP gateway function), it will specify G729(B) in its codec list. The Avaya 9600 SIP Telephones support either the G729A (default) or G729B codec. Therefore if the Avaya 9600 SIP Telephones are in their default configuration, and the VyDa-M only specifies G729B codec, the Avaya 9600 SIP Telephone will clear the call (codec mismatch). Care must be taken when defining VyDa-M dial-peers (see Section 4.2.2) to request codecs that will match the Avaya 9600 SIP Telephones default codec list. Alternatively, the Avaya 9600 SIP Telephones can be configured to accept the G729B codec but at the exclusion of G729A. See Section Configuring the Teldat VyDa-M SIP Router/Gateway Note - All commands were entered via the VyDa-M console interface. 4.. Teldat VyDa-M Command Line Interface (CLI) The VyDa-M CLI uses several modes or processes to determine which commands are available and how they will be applied to the VyDa-M. All commands available in each mode can be listed by entering?. The Tab key can be used to complete partially typed commands. All saved commands are written to the system flash and to the Smart-Card if installed. The modes used in testing the reference configuration are as follows: 7 of 30

8 Console Management Process This is the base mode when the CLI is first accessed. This mode is identified by the * prompt. The VyDa-M can be rebooted in this mode by entering Restart. Config Process This mode allows changes to be made to the VyDa-M configuration. This mode is entered by typing config at the * prompt, and is identified by the Config> prompt. After entering configuration commands in this mode, the user must enter save. However the changes will not take effect until the VyDa-M has been rebooted. Running Config Process This mode is entered by typing running-config at the * prompt, and is identified by the Config$ prompt. This mode is very similar to the Config process mentioned above. However once the save command has been entered changes are applied to the system without the need for a reboot Rebooting the VyDa-M Connect to the CONF interface. 2 At the * prompt, enter restart and the VyDa-M will reboot Navigating Between Processes. Connect the VyDa-M serial cable to the CONF interface. 2 At the console * prompt enter config and receive a Config> prompt. 3 Enter? to list command options. 4 Enter protocol sip to enter the sip protocol configuration, and prompt will change to SIP Config>. 5 Enter? to list SIP protocol command options To return to the main config process enter and the prompt will change to Config>. To return to the main console prompt enter end and the prompt will change to *. To navigate to the running config process, repeat the same steps but enter run and press the Tab key in 2. 8 of 30

9 4..3. Displaying the VyDa-M Configuration. This following command will display the entire configuration of the VyDa-M including the software version. 2 At the console * prompt enter run and receive a Config$ prompt. Enter show all to list the VyDa-M configuration. Note Entering ctrl+p at any time will stop the output of this command Teldat VyDa-M Provisioning See Section 9. for the complete VyDa-M configuration. VyDa-M default parameters are not described in these application notes. A four digit dial plan was used in the VyDa-M. Inbound and outbound dialing is controlled by dial-peers (see Section 4.2.2). The Avaya 9600 SIP Telephones in Location A called the telephones in Location B by dialing their five digit extension (see Section 6.3). Note All commands described in this section were entered via the running-config process Global Dial Profile The Teldat manual Dm 732-I Call Profiles was used for this configuration. 2 3 From the Config$ prompt enter global-profiles dial and the prompt will change to Dial Profiles Config$. Enter profile <name> inout where <name> is a name for the profile (e.g audio). Enter profile <name> isdn-type audio where <name> is the name specified in 2. 4 Enter to return to the Config$ prompt and enter save. 9 of 30

10 Telephony Dial Peers The Teldat manual Dm 722-I Telephony Over IP was used for this configuration. In this section,a dial-peer is created for the three Avaya 9600 SIP Telephones that are registered to the VyDa-M as well as dial-peers for outbound BRI trunk calls to Location B. A four digit dial plan is used in the reference configuration for the Avaya 9600 SIP Telephones registered to the VyDa-M (e.g., x9630). A voice class is also provisioned that specifies a group of codecs that the dial-peers will use. In this example, G7u and G729 codecs are specified. 2 From the Config$ prompt enter telephony and the prompt will change to Telephony Config$. Enter voice-class <number> where <number> is a number identifying the class (e.g., 0). The prompt will change to voice class 0 config$. 3 Enter codec-preference g7ulaw. 4 Enter codec-preference g729 (Note The VyDa-M supports only annexb=yes. It does so by not specifying the annexb parameter in the SIP SDP header). 5 Enter to return to the Telephony Config$ prompt. 6 7 Enter dial-peer <name> sip where <name> is a string to identify the SIP dial peer (e.g., 9620 for the Avaya 9620 SIP telephone). The prompt will change to dial-peer 9620 config $. Enter the following: destination pattern <pattern> where <pattern> are the dialed digits to be routed to the 9620 phone (e.g. 9620) target dynamic voice-class 0 (from 2 above) 8 Enter to return to the Telephony Config$ prompt. 9 Repeat s 6 through 8 to define dial-peers for the Avaya 9630 and 9640 SIP telephones. 0 of 30

11 0 Enter dial-peer <name> voice-port where <name> is a string to identify the BRI trunk dial peer (e.g., 5 for the 5xxx dial plan in the Location B Avaya Communication Manager). The prompt will change to dial-peer 5 config $. Enter the following: destination pattern <pattern> where <pattern> are the dialed digits to be routed the Location B Avaya Communication Manager (e.g., 5000.) over the BRI trunk. In this example specifying means a match will occur if the dialed digits are 5000 with any fifth digit (the. is a wild-card). target voice-port voip /0 (This identifies the BRI voice port to use. voice-class 0 (from 2 above) 2 Enter twice to return to the Config$ prompt and enter save Network Ethernet Interface The Teldat manual Dm 709-I LAN Interfaces was used for this configuration. 2 From the Config$ prompt enter network Ethernet 0/0 and the prompt will change to ethernet0/0 config$. Enter ip address <address> <mask> where <address> is the IP address of the interface and <mask> is the IP mask (e.g ). 3 Enter to return to the Config$ prompt and enter save Network BRI Note The following commands must be entered from the Config> prompt. After saving the configuration, the VyDa-M must be rebooted. of 30

12 BRI Physical Interface The manual used for this configuration - Dm 729-I BRI ISDN Interface. Note - The VyDa-M uses the EURO-ISDN protocol standard for its BRI interfaces. This cannot be modified to other standards (e.g., 5ESS). From the Config> prompt enter network bri /0 and the prompt will change to bri/0 config> 2 Enter set global emulate network 3 Enter set global plan-type isdn-telephony 4 Enter to return to the Config> prompt and enter save. 5 Continue to Section or enter end to return to the * prompt and enter restart to reboot the VyDa-M Activating the BRI Physical Interface As described in Section 3.2.3, the VyDa-M will not activate the BRI interface until it detects a call. In the reference configuration, the VyDa-M is connected directly to an Avaya G250-BRI Media gateway. The Avaya Communication Manager BRI trunk will be out-of-service (OOS) until the VyDa-M activates the BRI interface. Since the Avaya Communication Manager BRI trunk is OOS, any BRI calls originating from Location B will be blocked. To alleviate this issue, the BRI interface on the VyDa-M may be activated manually. 2 3 From the * prompt enter monitor and the prompt will change to +. Enter network bri/0 and the prompt will change to bri /0 BRI+. Enter activate and the BRI/0 green LED will go on indicating that the BRI interface is up. 4 Enter to return to the + prompt. 5 Enter ctrl+p to return to the * prompt. 2 of 30

13 BRI VoIP Interface The Teldat Dm 770-I VoIP Interfaces manual was used for this configuration. Note See Section for information on the BRI interface codecs. 2 From the Config> prompt, enter network voip/0 and the prompt will change to voip/0 config>. Enter base-interface and the prompt will change to voip/0 Base IFC config>. 3 Enter base-interface bri/0 255 link. 4 Enter base-interface bri/0 255 profile audio. 5 Enter base-interface bri/0 255 number-of-circuits all. 6 Enter and the prompt will change to voip/0 config>. 7 OPTIONAL - Enter dsp-firmware g729-g7 if G7U/G729 must be used instead of the default codecs (G7U/G723). 8 Enter to return to the Config> prompt and enter save. 9 Enter end to return to the * prompt and enter restart to reboot the VyDa-M Avaya Certificates The Teldat Dm 739-I IPSEC manual was used for this configuration. As described in Section, the Avaya 9600 SIP Telephones registered to the VyDa-M as though it was an Avaya environment (e.g., Avaya Communication Manager/SES). For this to occur, the VyDa-M must have Avaya TLS and SRTP certificates/keys installed. Note Only the commands are shown below. Valid certificates and keys and their associated files must be obtained from Avaya. 3 of 30

14 From the Config$ prompt, enter protocol ip and the prompt will change to IP config$. 2 Enter ipsec and the prompt will change to IPSEC config$ Enter key rsa file add <key string> where <key string> is the key. Repeat this step until all of the keys are entered, then enter. From the IPSEC config$ prompt, enter cert and the prompt will change to CERTIFICATES config$. Enter file new <name> where <name> is the name of a new certificate file you are creating (e.g. Avaya). Enter file add <text> where <text> is the certificate information. Repeat this step until all of the certificates are entered for the file specified in 5. Repeat s 5 and 6 for any additional certificate files and their associated certificates. At the CERTIFICATES config$ prompt, enter certificate <name> load, where <name> is the certificate file name created in 5. Repeat this step for any additional certificate files created in 7. Enter three times to return to the Config$ prompt and enter save. Enter end to return to the * prompt, and enter restart to reboot the VyDa-M DHCP The Teldat Dm 730-I DHCP Protocol manual was used for this configuration. Note The following commands must be entered from the Config> prompt. After saving the configuration, the VyDa-M must be rebooted. The VyDa-M may be used as a DHCP server to provide IP addressing to the Avaya 9600 SIP Telephones as well as to direct them to the IP address of their Proxy and HTTP server. Note The VyDa-M only accepts DHCP option entries in hex format. 4 of 30

15 From the Config> prompt, enter protocol dhcp and the prompt will change to DHCP config$. Enter server and the prompt will change to DHCP-Server config>. Enter shared <id> where <id> is a number identifying the shared network or pool (e.g., ). Enter shared <subnet name> <shared network ID> network <network IP address> <network mask>, where: <subnet name> = A identifying name for this subnet. <shared network ID> = The shared network ID specified in 3. <network IP address> = The IP address of the network used for this subnet. <network mask> = The IP mask of the network used for this subnet. This defines the IP domain for the pool. For example entering shared Avaya , creates a subnet called Avaya shared ID for network /24. Enter shared <subnet name> <shared network ID> range <network IP address range start> <network IP address range end> where: <subnet name> = A identifying name for this subnet from 4. <shared network ID> = The shared network ID specified in 3. <network IP address start> = The starting IP address of the network pool used for this subnet. <network IP address end> = The ending IP address of the network pool used for this subnet. This creates the IP pool range. For example entering shared Avaya , creates a subnet pool called Avaya shared ID with an address pool of through of 30

16 6 7 8 Enter shared <subnet name> <shared network ID> <subnetmask> where: <subnet name> = A identifying name for this subnet from 4. <shared network ID> = The shared network ID specified in 3. <subnet-mask> = The IP mask of the network pool defined in 5. This creates the IP pool subnet mask. For example entering shared Avaya creates a subnet pool called Avaya shared ID with an address pool mask of Enter shared <subnet name> <shared network ID> router <IP address> where: <subnet name> = A identifying name for this subnet from 4. <shared network ID> = The shared network ID specified in 3. <IP address> = The IP address of the default router. This creates the IP pool gateway. For example entering shared Avaya creates a subnet pool called Avaya shared ID with an address pool mask of Enter shared <subnet name> <shared network ID> option <option number> hex <value> where: <subnet name> = A identifying name for this subnet from 4. <shared network ID> = The shared network ID specified in 3. <option number > = The DHCP option number. <value> = The DHCP option in hex. For example the DHCP entry, DHCP option 242 ascii SIPSRVRADDR=0.0.0.,HTTPADDR= would be entered on the VyDA-M as: shared Avaya option 242 hex 0x f d3302e3302e3302e32c d3302e3302e3302e Enter enable. 6 of 30

17 0 Enter two times to return to the Config> prompt and enter save. Enter end to return to the * prompt and enter restart to reboot the VyDa-M. 5. Configuring the Avaya 96xx SIP Telephones. No configuration of the Avaya 9600 SIP Telephones is required. Default phone values were used including the Avaya Environment = Yes parameter (see Section ). However, the Avaya 96xx configuration file (46xxsettings.txt) was modified as follows to direct the Avaya 9600 SIP Telephones to register to the VyDa-M. SET SIPPROXYSRVR "0.0.0." This parameter directs the Avaya 9600 SIP Telephones to register to the VyDa-M. **OPTIONAL** SET ENABLE_G729 2 This parameter directs the Avaya 9600 SIP Telephones to request/accept G729B codec (at the exclusion of the default G729A value). See Section Configuring Avaya Communication Manager/Avaya G250- BRI Media Gateway. 6.. Prerequisites These Application Notes assume the following Avaya Communication Manager tasks are completed. Avaya Communication Manager is installed and licensed. Five digit dial plan with 5xxxx as valid extensions. The Avaya G250-BRI Media Gateway is provisioned and registered. An Avaya H.323 telephone is provisioned and registered as extension An analog telephone is provisioned as extension BRI Trunk BRI Board The Avaya G250-BRI Media Gateway has its BRI interfaces located in slot V4. 7 of 30

18 Log into the Avaya Communication Manager SAT console. 2 3 Enter add bri-trunk-board xxv4, where xx is the Media Gateway ID, and the BRI trunk form will open. On Page of the form enter the following interface = user protocol = etsi These values match the VyDa-M which is set to NT (network) and that the VyDa-M uses the EURO ISDN standard (see Section ). Leave all other values as default. 4 Save and the form. add bri-trunk-board 02v4 Page of 2 ISDN-BRI TRUNK CIRCUIT PACK Location: 002V4 Name: To_TELDAT Interface Companding: a-law DCP/Analog Bearer Capability: 3.kHz T3 Timer Length (sec): 5 Port Interface Side Cntry/Peer TEI Layer Detect Protocol Stable? Slips? : user etsi 0 y n 2: 0 y n BRI Trunk 2 From the SAT console enter add trunk x, where x is the trunk number, and the Trunk form will open. On Page of the form set the following Group Type = isdn TAC = (enter a TAC code based on the dialplan) Carrier Medium = PRI/BRI Service Type = tie Leave all other values as default. 8 of 30

19 3 On page two of the form set the following Send Name = y Send Calling Number =y Let all other values default. On page five of the form set the following Group Port = 002v40 4 Group 2 Port = 002v402 Let all other values default. 5 Save and the form. add trunk-group 5 Page of 2 TRUNK GROUP Group Number: 5 Group Type: isdn CDR Reports: y Group Name: To_TELDAT COR: TN: TAC: *05 Direction: two-way Outgoing Display? n Carrier Medium: PRI/BRI Dial Access? n Busy Threshold: 255 Night Service: Queue Length: 0 Service Type: tie Auth Code? n TestCall ITC: rest Far End Test Line No: TestCall BCC: 4 add trunk-group 5 Page 3 of 2 TRUNK FEATURES ACA Assignment? n Measured: none Wideband Support? n Internal Alert? n Maintenance Tests? y Data Restriction? n NCA-TSC Trunk Member: Send Name: y Send Calling Number: y Used for DCS? n Send EMU Visitor CPN? n Suppress # Outpulsing? n Format: public Outgoing Channel ID Encoding: preferred UUI IE Treatment: service-provider Replace Restricted Numbers? n Replace Unavailable Numbers? n Send Connected Number: n Hold/Unhold Notifications? n Send UUI IE? y Modify Tandem Calling Number? n Send UCID? n Send Codeset 6/7 LAI IE? y Ds Echo Cancellation? n Apply Local Ringback? n Show ANSWERED BY on Display? y Network (Japan) Needs Connect Before Disconnect? n add trunk-group 5 Page 5 of 2 TRUNK GROUP Administered Members (min/max): /2 GROUP MEMBER ASSIGNMENTS Total Administered Members: 2 Port Code Sfx Name Night Sig Grp : 002V40 2BRIIM 2: 002V47 2BRIIM 9 of 30

20 6.3. Call Routing Automatic Alternate Routing (AAR) is used to route outbound calls over the BRI trunk. The following call routing provisioning is performed in the reference configuration. An AAR access code of 8. A seven digit dial string with the format 555+xxxx, where xxxx is an Avaya 96xx SIP telephone extension. An AAR table entry matching on 555xxxx. A Route Pattern directing the call to the BRI trunk after stripping off three digits. For example, to call the Location A Avaya 96xx SIP telephone x9630, the Location B Avaya Communication Manager telephones would dial The 8 routes the call to the AAR table. The 555 is matched in the AAR table and sent to route pattern 5. Route pattern 5 strips off the 555 and forwards the 9630 to BRI trunk 5 for transmission to the VyDa-M. These digits will match the dial-peer defined in the VyDa-M in Section 4.2.2, AAR Feature Access Code From the SAT console enter change feature-access-codes, and the feature-access-code form will open. 2 Set Auto Alternate Routing (AAR) Access Code = 8. 3 Save and the form. change feature-access-codes Page of 5 FEATURE ACCESS CODE (FAC) Answer Back Access Code: Attendant Access Code: Auto Alternate Routing (AAR) Access Code: 8 Auto Route Selection (ARS) - Access Code : 9 Access Code 2: 20 of 30

21 AAR Analysis From the SAT console enter change aar analysis 5, and the AAR analysis form will open. Enter the following: Dial String = 555 Total Min = 7 2 Total max = 7 Route Pattern - aar Let all other values default. 3 Save and the form. change aar analysis 5 Page of 2 AAR DIGIT ANALYSIS TABLE Percent Full: 3 Dialed Total Route Call Node ANI String Min Max Pattern Type Num Reqd aar n aar n aar n Route Pattern From the SAT console enter change route-pattern 5, and the route-pattern form will open. Enter the following: Grp No = 5 2 FRL = 0 No. Del Dgts = 3 Let all other values default. 3 Save and the form. change route-pattern 5 Page of 3 Pattern Number: 5 Pattern Name: To_Teldat SCCAN? n Secure SIP? n Grp FRL NPA Pfx Hop Toll No. Inserted DCS/ IXC No Mrk Lmt List Del Digits QSIG Dgts Intw : n user 2: n user 2 of 30

22 6.4. Codecs As decribed in Section , by default the VyDa-M uses G7U/G723 codecs for its BRI interface. If these default values are used, then Avaya Communication Manager must be configured to accept at least one of these two codecs. If the VyDa-M is configured to use G7U/G729B (the other possible option), then the Avaya Communication Manager codec selection must be modified accordingly. Therefore, it is best to define all three codecs in Avaya Communication Manager. 2 3 From the SAT console, enter display media-gateway x, where x is the ID of the Avaya G250-BRI Media Gateway. Make a note of the network-region used by the Media Gateway. Exit the form. From the SAT console, enter display ip-network-region x, where x is the ID of the network-region used by the Media Gateway displayed in. Make a note of the codec-set specified for that ip-network-region. Exit the form. From the SAT console, enter change ip-codec-set x, where x is codec-set number used by the network-region displayed in 2. Enter the following Audio Codec = G.7MU Audio Codec = G K (or G K) Audio Codec = G.729B Note Additional codec may be specified. 4 Save and the form. display media-gateway 2 MEDIA GATEWAY Number: 2 Registered? y Type: g250-bri FW Version/HW Vintage: /4 Name: G250_BRI IP Address: Serial No: 03IS Controller IP Address: Encrypt Link? y MAC Address: 00:04:0d:6d:73:b5 Network Region: Location: Site Data: Recovery Rule: none Slot Module Type Name V: S8300 ICC MM V2: V3: T+2L-Integ-Analog ANA IMM V4: 2-Port-Integ-BRI BRI IMM 22 of 30

23 display ip-network-region Page of 9 IP NETWORK REGION Region: Location: Authoritative Domain: Name: MEDIA PARAMETERS Intra-region IP-IP Direct Audio: yes Codec Set: Inter-region IP-IP Direct Audio: yes UDP Port Min: 2048 IP Audio Hairpinning? n UDP Port Max: 3329 DIFFSERV/TOS PARAMETERS RTCP Reporting Enabled? y Call Control PHB Value: 46 RTCP MONITOR SERVER PARAMETERS Audio PHB Value: 46 Use Default Server Parameters? y Video PHB Value: 26 change ip-codec-set Page of 2 Codec Set: IP Codec Set Audio Silence Frames Packet Codec Suppression Per Pkt Size(ms) : G.7MU n : G k n : G.729B n Verification s 7.. BRI Trunk Status Open a SAT session to Avaya Communication Manager in Location B and verify that the BRI trunk is in service by entering: status trunk x, where x is the BRI trunk number created in Section status trunk 5 TRUNK GROUP STATUS Member Port Service State Mtce Connected Ports Busy 0005/00 002V40 in-service/idle no 0005/ V47 in-service/idle no 23 of 30

24 7.2. DHCP and SIP Registration 2 Connect the Avaya 96xx SIP Telephones to the network and verify that they obtain IP addresses from the VyDa-M as well as directed to the HTTP server. When the Avaya 9600 SIP Telephones request a Username and Password, enter the appropriate extension provisioned in the VyDa-M dial-peers (see Section 4.2.2) and any password. Verify that the Avaya 9600 SIP Telephones register Telephony 2 3 From Location A Avaya 9630 SIP telephone, call Avaya 9640 SIP telephone by dialing 9640 and verify 2-way audio. Verify via a protocol analyzer that the audio is sent directly between the two phones. From Location A Avaya 9630 SIP telephone, call Location B Avaya H.323 telephone by dialing Verify 2-way audio. From Location B Avaya H.323 telephone, call Location A Avaya 9630 SIP telephone by dialing Verify 2-way audio Teldat VyDa-M SIP Protocol Analyzer Since the connection between the Avaya 9600 SIP Telephones and the VyDA-M is using the TLS protocol, a protocol analyzer will not be able to decode the SIP protocol headers. The VyDa-M provides a SIP protocol trace function that decodes the SIP transactions it is processing. From the * prompt enter monitor and the prompt will change to +. 2 Enter protocol sip and the prompt will change to SIP Mon+. 3 Enter log clear to clear the log table. 4 Enter log start to enable SIP logging. 24 of 30

25 5 Place the call. 6 Enter log stop to stop the SIP logging. 7 Enter log print to print the SIP log on the console. 8 Enter to return to the + prompt. 9 Enter cntrl+p to return to the * prompt. 8. Conclusion The Teldat VyDa-M SIP Router/Gateway provides SIP registrar and proxy functionality to Avaya 9600 SIP Telephones operating in Avaya Environment mode. BRI trunk interoperability with the Avaya G250-BRI Media Gateway was verified. In addition, the Teldat VyDa-M SIP Router/Gateway provided DHCP functionality to the Avaya 9600 SIP Telephones. 25 of 30

26 9. Appendix 9.. References 9... Teldat These manuals are available from after obtaining an account.. Dm 732-I Call Profiles. 2. Dm 722-I Telephony Over IP. 3. Dm 709-I LAN Interfaces. 4. Dm 729-I BRI ISDN Interface. 5. Dm 770-I VoIP Interfaces. 6. Dm 739-I IPSEC. 7. Dm 730-I DHCP Protocol Avaya These manuals are available from the Avaya support web site Administrator Guide for Avaya Communication Manager, , Issue 3., February Avaya one-x Deskphone SIP for 9600 Series IP Telephones Administrator Guide, Release , Issue, May Administration for the Avaya G250 and Avaya G350 Media Gateways, , Issue 3, February Teldat VyDa-M Configuration Config$show all Showing Menu and Submenus Configuration for access-level 5... VyDa-2M Router 7 98 Version log-command-errors no configuration global-profiles dial -- Dial Profiles Configuration -- profile audio inout profile audio isdn-type audio telephony -- Telephony configuration of 30

27 voice-class 0 codec-preference g7ulaw codec-preference g729 dial-peer 9620 sip destination-pattern 9620 target dynamic voice-class 0 dial-peer 9630 sip destination-pattern 9630 target dynamic voice-class 0 dial-peer 9640 sip destination-pattern 9640 target dynamic voice-class 0 dial-peer 5 voice-port destination-pattern target voice-port voip/0 voice-class 0 network ethernet0/0 -- Ethernet Interface User Configuration -- ip address network voip/0 -- VoIP interface Configuration -- dsp-firmware g729-g7 base-interface -- Base Interface Configuration -- base-interface bri/0 255 link base-interface bri/0 255 profile audio 27 of 30

28 base-interface bri/0 255 number-of-circuits all network bri/0 -- BRI ISDN Configuration -- set global emulate network set global plan-type isdn-telephony protocol ip -- Internet protocol user configuration -- ipsec -- IPSec user configuration -- key rsa file add 0x (valid keys must be obtained from Avaya) cert -- Cert user configuration -- file new SAMPLE.CER file add 0x (valid certificates must be obtained from Avaya) * * * file new TELDATCA.CER file add 0x..(valid certificates must be obtained from Avaya) * * * file new AVAYACA.CER file add 0x.(valid certificates must be obtained from Avaya) * * * certificate SAMPLE.CER load certificate TELDATCA.CER load certificate AVAYACA.CER load 28 of 30

29 protocol dhcp -- DHCP Configuration -- server -- DHCP Server Configuration -- shared subnet avaya network subnet avaya range subnet avaya router subnet avaya subnet-mask subnet avaya option 242 hex 0x f d3302e3302e3302e32c d3302e330 2e3302e3633 enable protocol sip -- SIP protocol configuration -- application address application gateway application server default crypto signaling default ca teldatca.cer crypto signaling default ca avayaca.cer crypto signaling default user sample.cer realm teldat.com transport tls end Config$ 29 of 30

30 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 any questions or comments pertaining to these Application Notes along with the full title name and filename, located in the lower right corner, directly to the Avaya Solution & Interoperability Test Lab at 30 of 30