Abstract. Avaya Solution & Interoperability Test Lab

Avaya Solution & Interoperability Test Lab Configuring an Avaya S8300 Media Server, Avaya G700 Media Gateway, and an Avaya IP Office 403 For Call Display Information via an H.323 Trunk- Issue 1.0 Abstract These Application Notes describe how to configure an Avaya S8300 Media Server and an Avaya IP Office 403 to pass the appropriate identification to populate the telephone display. The sample configurations will show how to configure the servers for additional information to be displayed between the two products connected via an H.323 IP trunk. There are some limitations with respect to the information that is displayed. An account team requested these Application Notes. 1 of 19

1. Introduction These Application Notes describe how to configure an Avaya S8300 Media Server and an Avaya IP Office 403 to pass the appropriate identification to populate the telephone display. The sample configurations will show how to configure the servers for additional information to be displayed between the two products connected via an H.323 IP trunk. With the current release, when calling from IP Office to the S8300 Media Server, only the connected number will appear on the Avaya IP Office Telephone display. Whereas when calling from the Avaya S8300 Media Server to the Avaya IP Office, the connected name will be displayed on the Avaya S8300 Media Server telephone displays. Other call display formats such as redirection displays (call forwarding, call coverage, etc.) are outside the scope of these Application Notes. In Figure 1, an Avaya IP Office 403 and an Avaya Communication Manager (S8300) connect via an H.323 trunk with QSIG supplementary services enabled. The example in this document will show this trunk configured with emphasis placed on call display values. Avaya Communication Manager software supports several independent numbering plans. Because many customers rely not only on call displays, but also on the Path Optimization features offered by QSIG in Avaya Communication Manager, the selection of the correct numbering plan is important. The following scheme ensures the best QSIG Path Optimization: If the customer uses ARS to dial between systems, then Public ISDN numbering is recommended. If the customer uses AAR, then Private ISDN numbering is recommended. If the customer uses UDP (as in this example), then Unknown ISDN numbering is recommended. A route pattern example shows S8300 extension 4XXXX and IP Office 21XXX being able to reach each other. Some things to note: The Avaya P333T Layer 2 Switch is set to factory defaults. No configuration is necessary. Avaya Communication Manager supports QSIG Path Optimization; however, Avaya IP office does not. Path Optimization is discussed here only because it is difficult to discuss call displays without discussing numbering plans, and it is difficult to discuss numbering plans without discussing path optimization. However, path optimization is not the focus of this document. The display options are supported for most types of Digital and IP Telephones. However, some minor variances can occur based upon the display s properties. The Avaya 4620 IP Telephone is registered to Avaya Communication Manager, whereas the 4624 Telephone is registered to the Avaya IP Office 403. The Network Administrator should decide beforehand whether Public, Unknown or Private ISDN numbering is most appropriate for the network. 2 of 19

When a telephone registered to the Avaya S8300 Media Server calls a telephone registered to the Avaya IP Office, the Avaya IP Office telephone will display the calling name and number when the phone rings. The Avaya S8300 Media Server telephones will display the outgoing trunk name and TAC code during ringing and will display the connected name when the call is answered. When a telephone registered to the Avaya IP Office calls a telephone registered to the Avaya S8300 Media Server, the Avaya S8300 Media Server telephone will display the calling party name and number when the phone rings. The Avaya IP Office telephone will display the dialed number, both when the phone rings and when the call is answered. Avaya DCPTelephone 6402D Ext. 41000 Name: ACM FRED Management PC/DHCP Server Phone Manager Pro Registered to IP Office Ext. 29905 Full Name: IPO JOHN Name: IP Softphone 2.150 Avaya P333T Switch 10.1.2.0/24 10.1.2.0/24.50 Avaya IP Office 403 Avaya S8300/G700 Avaya IP Softphone Registered to S8300 Ext. 41100 Name:ACM JIM Avaya 4620 Registered to S8300 Ext. 41102 Name: ACM MIKE Avaya 4624 Registered to IP Office Ext. 29906 Full Name: IPO SAM Name: IP 4624 Avaya DCP Telephone 6408D+ Ext. 29902 Full Name: IPO JOE Name: DCP 6408D+.23 Figure 1: Sample Network used for Call Display 2. Equipment and Software Validated The following equipment and software were used for the sample configuration provided: Equipment Software Avaya S8300 Media Server Avaya Communication Manager 1.3.1 R011X.03.1.532.0 Avaya G700 Media Gateway Processor 20.18.0(A) 16 Avaya IP Office 403 Server 2.09 Avaya 6408D+ Telephone N/A Avaya 6402D Telephone N/A Avaya IP 4620 Telephone 1.81 Avaya IP 4624 Telephone 1.81 Avaya IP Softphone 5.0.4.4 Avaya Phone Manager Pro 2.0.7 3 of 19

Table A: Version Table 3. Configure Avaya Communication Manager The configuration for the Avaya S8300 Media Server is described in four parts. The first part describes how to configure the stations for call display, the second part describes how to configure IP Trunks, the third part describes how to configure the dialplan and the fourth part describes how to configure ISDN numbering. 3.1. Configure Extensions Step 1: Configure the extensions. Enter the appropriate extension for the IP Telephone as in Figure 2. Enter the type of phone in the Type field. Mismatched telephone types will affect call displays. Enter the user name in the Name field. The information entered in the Name field will be displayed on the called phone as well as the extension number. Change Station 41102 STATION Page 1 of 4 SPE B Extension: 41102 Lock Messages? n BCC: 0 Type: 4620 Security Code: TN: 1 Port: S00010 Coverage Path 1: COR: 4 Name: ACM MIKE Coverage Path 2: COS: 1 Hunt-to Station: STATION OPTIONS Loss Group: 19 Personalized Ringing Pattern: 1 Message Lamp Ext: 41102 Speakerphone: 2-way Mute Button Enabled? y Display Language: english Media Complex Ext: IP SoftPhone? N Figure 2: Configuring an Extension 3.2. Configuring IP Trunks Step 1: Configure IP node names. Assign a name to the far-end IP Office gatekeeper and enter its IP address. Verify the IP address for the Avaya S8300 Media Server interface. This information should have been auto-populated from the initial web server administration See Figure 3. change node-names ip Page 1 of 1 SPE B IP NODE NAMES Name IP Address Name IP Address PROCR 10.1.2.150... IP-Office 10.1.2.50... default 0.0.0.0... Figure 3: Configuring IP Node Names 4 of 19

Step 2: Configure IP Interface. Verify the gateway and subnet mask information for the Avaya S8300 Media Server interface. This information should have been auto-populated from the initial web server administration. Change the network region to the desired number. See Figure 4. change ip-interfaces Page 1 of 19 SPE B Enable IP INTERFACES Eth Pt Type Slot Code Sfx Node Name Subnet Mask Gateway Address Rgn y PROCR 10. 1. 2.150 255.255.255.0 10.1.2.1 6 Figure 4: Configuring IP Interfaces Step 3: Create the signal group. Figure 5 shows the configuration of the associated signaling group parameters for Trunk Group 8. Notice that the field Trunk Group for Channel Selection must be left blank when adding the signaling group, even though this screen shows the value 8. This value will be added in a later step. Verify the Supplementary Service Protocol is set to b. This value will enable QSIG Supplementary Services. change signaling-group 8 Page 1 of 5 SPE B SIGNALING GROUP Group Number: 8 Group Type: h.323 Remote Office? n Max number of NCA TSC: 0 Max number of CA TSC: 0 Trunk Group for NCA TSC: Trunk Group for Channel Selection: 8 Supplementary Service Protocol: b Net Near-end Node Name: procr Far-end Node Name: IP-Office Near-end Listen Port: 1720 Far-end Listen Port: 1720 Far-end Network Region: LRQ Required? n Calls Share IP Signaling Connection? n RRQ Required? n Bypass If IP Threshold Exceeded? n Direct IP-IP Audio Connections? y IP Audio Hairpinning? y Interworking Message: PROGress Figure 5: Configuring IP Signal Group Parameters 5 of 19

Step 4: Create the trunk group. Figure 6 shows IP trunk group 8 configured. Pages 1 and 2 describe trunk type attributes. Page 6 assigns ports to the trunk group where the first 15 of a total 20 ports were assigned for voice over this trunk. When entering the ports on page 6, enter IP and the Avaya S8300 Media Server will automatically assign the T00 port ID for the IP trunk. After assigning channels to signal group to 8 on page 6, go back and set the Trunk Group for Channel Selection field to 8 in the signaling-group. For call displays to work properly, the user has to determine if the numbering scheme is a public ISDN, unknown, or private ISDN scheme. For numbering format choices of unk-pvt and private, use the change ISDN privatenumbering form to create the number, while, for numbering format choices of unknown and public, use the change ISDN public-unknown- numbering form to create the number. In this example UDP unknown (private) numbering is used. For UDP unknown numbering, change the fields to the following: Page 1: Outgoing Display: Y (shows outgoing trunk group until call is answered) Supplementary Service Protocol; b (ISO QSIG supplementary services standard) Page 2 Send Name: y Send Calling Number: y Numbering Format: unk-pvt Send Connected Number: y For ARS Public numbering, change the fields to the following: Page 1: Outgoing Display: Y (shows outgoing trunk group until call is answered) Supplementary Service Protocol; b (ISO QSIG supplementary services standard) Page 2 Send Name: y Send Calling Number: y Numbering Format: Public Send Connected Number: y 6 of 19

For AAR Private, follow these steps: Page 1: Outgoing Display; Y (shows outgoing trunk group until call is answered) Supplementary Service Protocol: b (ISO QSIG Standard) Page 2 Send Name: y Send Calling Number: y Numbering Format: private Send Connected Number: y change trunk-group 8 Page 1 of 22 SPE B TRUNK GROUP Group Number: 2 Group Type: isdn CDR Reports: y Group Name: IP Office IP Trunk COR: 1 TN: 1 TAC: 108 Direction: two-way Outgoing Display? y Carrier Medium: IP 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 TRUNK PARAMETERS Codeset to Send Display: 6 Codeset to Send National IEs: 6 Max Message Size to Send: 260 Charge Advice: none Supplementary Service Protocol: b Digit Handling (in/out): enbloc/enbloc Trunk Hunt: cyclical QSIG Value-Added? y Digital Loss Group: 13 Calling Number - Delete: Insert: Numbering Format: Bit Rate: 1200 Synchronization: async Duplex: full Disconnect Supervision - In? y Out? n Answer Supervision Timeout: 0 change trunk-group 8 Page 2 of 22 SPE B 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 Suppress # Outpulsing? N Numbering Format: unk-pvt Outgoing Channel ID Encoding: preferred UUI IE Treatment: service-provider Send UUI IE? y Send UCID? n Send Codeset 6/7 LAI IE? y Replace Restricted Numbers? n Replace Unavailable Numbers? n Send Connected Number: y SBS? n Network (Japan) Needs Connect Before Disconnect? n 7 of 19

change trunk-group 8 Page 6 of 22 SPE B TRUNK GROUP Administered Members (min/max): 1/31 GROUP MEMBER ASSIGNMENTS Total Administered Members: 20 Port Code Sfx Name Night Sig Grp 1: T00109 8 2: T00110 8 3: T00111 8 4: T00112 8 5: T00113 8 6: T00114 8 7: T00115 8 8: T00116 8 9: T00117 8 10: T00118 8 11: T00119 8 12: T00120 8 13: T00121 8 14: T00122 8 15: T00123 8 Figure 6: Pages 1, 2 and 6 of the Change Trunk Group form Step 5: Assign an IP network region. Figure 7 shows the configuration the network region QoS parameters for the IP trunk. Point the network region to the appropriate IP Codec set. change ip-network-region 6 Page 1 of 2 SPE B IP Network Region Region: 1 Name: Audio Parameters Codec Set: 1 Location: UDP Port Range Min: 16384 Max: 32767 Direct IP-IP Audio Connections? y IP Audio Hairpinning? y RTCP Enabled? y RTCP Monitor Server Parameters Use Default Server Parameters? y DiffServ/TOS Parameters Call Control PHB Value: 34 VoIP Media PHB Value: 46 BBE PHB Value: 43 802.1p/Q Enabled? n change ip-network-region 6 Page 2 of 2 SPE B Inter Network Region Connection Management Region (Group Of 32) 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 001-032 1 1 033-064 065-096 097-128 Figure 7: Configuring IP Network Region 8 of 19

Step 6: Choose a codec negotiation list. Assign preferred codecs in descending order. See Figure 8. change ip-codec-set 1 Page 1 of 1 SPE B Codec Set: 1 IP Codec Set Audio Silence Frames Packet Codec Suppression Per Pkt Size(ms) 1: G.711MU n 2 20 2: G.729 n 2 20 3: G.729A n 2 20 4: 5: 6: 7: Figure 8: Configuring IP Codec Set 3.3. Configuring Dial Plans Telephone extensions beginning with 2 are routed to IP Office. These extensions are not defined in the Avaya S8300 Media Server. Instead, they are compared against a Uniform Dialplan Table. If there is a match, digits are analyzed and manipulated in the AAR Analysis Table and are then forwarded to the corresponding trunk group to IP Office, based on the Route Pattern Table. Step 1: Create a Uniform Dialplan for extensions starting with the digit 2. The following configuration will result in calls dialed as 2XXXX to be sent to route pattern 4 and trunk group 8, thereby sending the digits 2XXXX to IP Office. See Figure 9. change uniform-dialplan 2 Page 1 of 2 SPE B UNIFORM DIAL PLAN TABLE Percent Full: 0 Matching Insert Node Matching Insert Node Pattern Len Del Digits Net Conv Num Pattern Len Del Digits Net Conv Num 2 5 1 200 aar n 31228 5 0 ext n Figure 9: Uniform Dial Plan Form 9 of 19

Step 2: Create an AAR Analysis entry. Create the AAR analysis entry for the seven-digit number of 200XXXX. Specify a maximum and total of 7 digits. Route pattern 4 is assigned for further processing in the Route Pattern Table. change aar analysis 200 Page 1 of 2 SPE B AAR DIGIT ANALYSIS TABLE Percent Full: 5 Dialed Total Route Call Node ANI String Min Max Pattern Type Num Reqd 200 7 7 4 aar n Figure 10: AAR Analysis Form Step 3: Create Route Pattern 4. Route Pattern 4 has one entry associated with it. The entry corresponds to trunk group 8 that was previously created. The digits will be forwarded to the trunk. Before the seven digits are forwarded, the first three digits, 200, will be stripped off and the digit 2 will be added so that only the original five digits will be sent. See Figure 11. The Numbering Format field on this form should be set as follows: unk-unk for UDP networks (shown in Figure 11). For AAR networks, the numbering format field can be left blank if the Call Type on the AAR Analysis form is lev0, lev1, or lev2. If the AAR Call Type is aar (the default), then the numbering format field should be set to lev0-pvt, lev1-pvt, or lev2-pvt, respectively. For ARS networks, the numbering format field can be left blank if the Call Type on the ARS Analysis form is one of the usual values (fnpa, natl, etc.) change route-pattern 4 Page 1 of 3 SPE B Pattern Number: 20 Grp FRL NPA Pfx Hop Toll No. Inserted DCS/ IXC No Mrk Lmt List Del Digits QSIG Dgts Intw 1: 8 0 0 3 2 n user 2: n user 3: n user 4: n user 5: n user 6: n user BCC VALUE TSC CA-TSC ITC BCIE Service/Feature BAND No. Numbering LAR 0 1 2 3 4 W Request Dgts Format Subaddress 1: y y y y y n n rest unk-unk none 2: y y y y y n n rest none 3: y y y y y n n rest none Figure 11: Route Pattern Form for Private ISDN Numbering 10 of 19

3.4. Configuring ISDN Numbering Either ISDN Public unknown numbering or ISDN Private numbering is used. Choose the appropriate numbering scheme and enter accordingly. 3.4.1. Configuring ISDN Public-Unknown-Numbering In the Ext Len column, enter the length of the station. For example, 5-digit dialplan for extension 29902 would be 5. In the Ext code column, enter the leading digit of the extension. So if the extension is 29902, then enter 2. The Trk grp field can be left blank or put the trunk group that the extension is going out over. In this case, it is blank. The CPN prefix field contains inserted digits. If the administrator wants to send the 5-digit extension, then leave it blank. Otherwise, if the administrator wants to send a 10-digit number, then enter the leading 5 digits, for example 73285. This would send 732-852-9902. See Figure 12. The Total CPN Len field must match the total digits that are sent, for example 5 or 10. change isdn public-unknown-numbering Page 1 of 8 SPE B ISDN NUMBERING - PUBLIC/UNKNOWN FORMAT Total Total Ext Ext Trk CPN CPN Ext Ext Trk CPN CPN Len Code Grp(s) Prefix Len Len Code Grp(s) Prefix Len 5 2 73285 10 Figure 12: Public Unknown ISDN Numbering Form 3.4.2. Configuring ISDN Private or Unknown-Private Numbering If ISDN Private or Unknown-Private (e.g., UDP) numbering is used, type the parameters shown in Figure 13. This assumes the customer wants to send the extension "as is", which is normal in a UDP network. If the customer has an AAR network, other options would be needed. For example, the customer might need to fill in the PBX Identifier, or set the Network Level to 1 or 2. change isdn private-numbering Page 1 of 1 SPE B Network Level: 0 ISDN NUMBERING - PRIVATE FORMAT PBX Identifier: Level 2 Code: Deleted Digits: 0 Level 1 Code: Figure 13: Private ISDN Numbering Form 11 of 19

3.5. Configuring IP Office Step 1: Configure a user. Under the User option in IP Office Manager Enter the User information. Particularly the Name, Full Name and Extension fields should be entered, as these fields will be displayed at times during the calling process. In this example, the Full Name field will be the name field that will be displayed to the called party. Figure 14: Configuring User Information 12 of 19

Step 2: Enter telephony options. The form in Figure 15 captures the most common telephony options. Figure 15: Configuring Telephony Options 13 of 19

Step 3: Configure Line options. Enter information as in Figure 16. The Telephone Number field is for information only and is not displayed on any telephone. Figure 16: Configuring H.323 Line Options 14 of 19

Step 4: Enter VoIP information. Enter the information as shown in Figure 17 for proper H.323 trunk operation. Selecting H450 support to QSIG chooses QSIG supplementary Services Protocol. This is the same as Supplementary Service Protocol b on the Avaya S8300 end. Figure 17: Configuring IP Office VoIP settings 15 of 19

Step 5: Configure Shortcode. Configure the shortcode so Avaya S8300 Media Server dial plan digits will be forwarded to the Avaya IP Office H.323 trunk as in Figure 18. Figure 18: Configuring IP Office Shortcodes to Forward Digits to the Avaya S8300 Media Server Step 6: Save and reboot. Save the configuration changes and reboot the IP Office. 16 of 19

4. Verification Steps Log into Avaya S8300 Media Server and type status trunk 8. The trunk status should be in service/idle as in Figure 19. If not, recheck the configuration. status trunk 8 Page 1 SPE B TRUNK GROUP STATUS Member Port Service State Mtce Connected Ports Busy 008/001 T00011 in-service/idle no 008/002 T00012 in-service/idle no 008/003 T00013 in-service/idle no Figure 19: Displaying the Status of the Trunk 4.1. Sample Call Displays The maximum possible combination of information displayed varies between types of phones. However, when calling from the IP Office to the S8300, only the connected number will appear on the Avaya IP Office Telephone display. Whereas, when calling from the Avaya S8300 Media Server to the Avaya IP Office, the connected name will be displayed on the Avaya S8300 Media Server telephone displays. Please note that other call display formats such as redirection displays (call forwarding, call coverage, etc.) are important, but are outside the scope of these Application Notes. Table B shows a sample call display table from an Avaya 6402D Digital Telephone that is registered to the Avaya S8300 Media Server to all the telephone sets that are registered to the Avaya IP Office. Please note the following: The call display for ringing phones is different than answered phones. The results for Avaya IP Softphone display are given for the picture of a 4624 telephone. The <nl> symbol means the information to the right of the symbol appears on a new line. Calling Called Ringing Ext Type Display Ext Type Display 41000 6402D IP Office IP Trunk 108 29902 6408D+ 41000>DCP 29902 IP Office IP Trunk 108 29905 PM Pro From: 41000 To:IP Softphone 2 IP Office IP Trunk 108 29906 4624 41000>IP 4624 Answer Ext Type Display Ext Type Display 41000 6402D a=dcp 6408D+ 29902 6408D+ DCP 6408D+<nl>41000 a=ip Softphone 2 29905 PM Pro From: 41000 To:IP Softphone 2 a=ip 4624 29906 4624 IP 4624<nl>41000 Table B: Call Display Samples When 6402D Rings Various Telephones 17 of 19

Table C is a sample call display table from a 6408D+ that is registered to the IP Office to all the telephone sets that are registered to the S8300. Calling Called Ringing Ext Type Display Ext Type Display 29902 6408D+ Call41000 41000 6402D DCP 6408D+<nl>29902 Call41100 41100 Sft Phn DCP 6408D+<nl>29902 Call41102 41102 4620 DCP 6408D+29902 Answer Ext Type Display Ext Type Display 29902 6408D+ 41000<nl>41000 41000 6402D a=dcp 6408D+<nl>29902 41100<nl>41100 41100 Sft Phn a=dcp 6408D+<nl>29902 41102<nl>41102 41102 4620 DCP 6408D+ 29902 Table C: Call Display Samples When 6408D+ is in Conversation with Various Telephones 5. Conclusion After completing the configurations as described above, telephones registered to the Avaya S8300 Media Server will properly display calling and called information when interacting with telephones registered to an Avaya IP Office. 18 of 19

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 name and filename, located in the lower right corner, directly to the Avaya Solution & Interoperability Test Lab at interoplabnotes@list.avaya.com 19 of 19