Inhaltszusammenfassung zur Seite Nr. 1
Avaya Solution & Interoperability Test Lab
Application Notes for Algo 8028 SIP Doorphone with Avaya
Aura® Session Manager and Avaya Aura® Communication
Manager - Issue 1.0
Abstract
These Application Notes describe the steps required to integrate the Algo 8028 SIP Doorphone
with Avaya Aura® Session Manager and Avaya Aura® Communication Manager configured
as an Evolution Server. The 8028 SIP Doorphone provides hands-free intercom capability and
entrance sec
Inhaltszusammenfassung zur Seite Nr. 2
1. Introduction These Application Notes describe the steps required to integrate the Algo 8028 SIP Doorphone with Avaya Aura® Session Manager and Avaya Aura® Communication Manager configured as an Evolution Server. The 8028 SIP Doorphone provides hands-free intercom capability and entrance security with door unlock control. It is a SIP compliant device that registers with Session Manager. The 8028 Doorphone includes a Control Unit and Door Station. A visitor can press the call button
Inhaltszusammenfassung zur Seite Nr. 3
3. Reference Configuration Figure 1 illustrates a sample configuration with an Avaya SIP-based network that includes Session Manager, Communication Manager running on an Avaya S8800 Server with a G650 Media Gateway, and the Algo 8028 SIP Doorphone. Communication Manager was configured as an Evolution Server and the 8028 SIP Doorphone registered with Session Manager. LAN SIP device registered Avaya Aura® Session Manager with Session Manager (10.32.24.235) Algo 8028 SIP SIP Doorphone Avaya
Inhaltszusammenfassung zur Seite Nr. 4
4. Equipment and Software Validated The following equipment and software were used for the sample configuration provided: Hardware Component Version Avaya S8800 Server and G650 Media Avaya Aura® Communication Manager 6.0.1 Gateway SP 3 (R016x.00.1.510.1 w/Patch 19009) Avaya Aura® Session Manager 6.1 (6.1.2.0-612004) Avaya Aura® System Manager 6.1 (6.1.0.07345-6.1.5.106) Avaya 9600 Series IP Telephones 3.1 (H.323) 2.6.4 (SIP) Algo 8028 SIP Doorphone 1.4 5. Configure Avaya
Inhaltszusammenfassung zur Seite Nr. 5
In the IP Network Region form, the Authoritative Domain field is configured to match the domain name configured on Session Manager. In this configuration, the domain name is avaya.com. By default, IP-IP Direct Audio (shuffling) is enabled to allow audio traffic to be sent directly between IP endpoints without using media resources in the Avaya G650 Media Gateway. The IP Network Region form also specifies the IP Codec Set to be used for calls routed over the SIP trunk to Session Manager.
Inhaltszusammenfassung zur Seite Nr. 6
Prior to configuring a SIP trunk group for communication with Session Manager, a SIP signaling group must be configured. Configure the signaling group form as follows: Set the Group Type field to sip. Set the IMS Enabled field to n. The Transport Method field was set to tcp. In a production network, TLS transport may also be used. Specify the C-LAN board and the Session Manager as the two ends of the signaling group in the Near-end Node Name field and the Far-end Node Name
Inhaltszusammenfassung zur Seite Nr. 7
Configure the Trunk Group form as shown below. This trunk group is used for calls to the SIP Phones. Set the Group Type field to sip, set the Service Type field to tie, specify the signaling group associated with this trunk group in the Signaling Group field, and specify the Number of Members supported by this SIP trunk group. Configure the other fields in bold and accept the default values for the remaining fields. add trunk-group 50 Page
Inhaltszusammenfassung zur Seite Nr. 8
5.2. Configure Station Use the add station command to add station for the 8028 SIP Doorphone. Use 9640SIP for the Station Type. The Name field is optional. Use the default values for the other fields. The SIP station can also be configured automatically by Session Manager as described in Section 6.7. add station 78300 Page 1 of 6 STATION Extension: 78300 Lock Messages? n
Inhaltszusammenfassung zur Seite Nr. 9
6. Configure Avaya Aura® Session Manager This section provides the procedures for configuring Session Manager. The procedures include adding the following items: SIP domain Logical/physical Locations that can be occupied by SIP Entities SIP Entities corresponding to Session Manager and Communication Manager Entity Links, which define the SIP trunk parameters used by Session Manager when routing calls to/from SIP Entities Define Communication Manager as Administrable Entity
Inhaltszusammenfassung zur Seite Nr. 10
6.1. Specify SIP Domain Add the SIP domain for which the communications infrastructure will be authoritative. Do this by selecting Domains on the left and clicking the New button (not shown) on the right. The following screen will then be shown. Fill in the following: Name: The authoritative domain name (e.g., avaya.com) Notes: Descriptive text (optional). Click Commit. Since the sample configuration does not deal with any other domains, no additional domains need to be a
Inhaltszusammenfassung zur Seite Nr. 11
6.2. Add Locations Locations can be used to identify logical and/or physical locations where SIP Entities reside for purposes of bandwidth management. To add a location, select Locations on the left and click on the New button (not shown) on the right. The following screen will then be shown. Fill in the following: Under General: Name: A descriptive name. Notes: Descriptive text (optional). Under Location Pattern: IP Address Pattern: A pattern used to logically identi
Inhaltszusammenfassung zur Seite Nr. 12
6.3. Add SIP Entities In the sample configuration, a SIP Entity is added for Session Manager and the C-LAN in the G650 Media Gateway. 6.3.1. Session Manager A SIP Entity must be added for Session Manager. To add a SIP Entity, select SIP Entities on the left and click on the New button (not shown) on the right. The following screen is displayed. Fill in the following: Under General: Name: A descriptive name. FQDN or IP Address: IP address of the signaling interface on Sessio
Inhaltszusammenfassung zur Seite Nr. 13
JAO; Reviewed: Solution & Interoperability Test Lab Application Notes 13 of 29 SPOC 11/3/2011 ©2011 Avaya Inc. All Rights Reserved. Algo-8028-SM
Inhaltszusammenfassung zur Seite Nr. 14
6.3.2. Communication Manager A SIP Entity must be added for the Communication Manager. To add a SIP Entity, select SIP Entities on the left and click on the New button (not shown) on the right. The following screen is displayed. Fill in the following: Under General: Name: A descriptive name. FQDN or IP Address: IP address of the signaling interface (e.g., C-LAN board) on the telephony system. Type: Select CM. Location: Select the location defined previously.
Inhaltszusammenfassung zur Seite Nr. 15
6.4. Add Entity Link The SIP trunk from Session Manager to Communication Manager is described by an Entity link. To add an Entity Link, select Entity Links on the left and click on the New button (not shown) on the right. Fill in the following fields in the new row that is displayed: Name: A descriptive name (e.g., devcon13 Link). SIP Entity 1: Select the Session Manager. Protocol: Select the appropriate protocol. Port: Port number to which the other system sends SIP re
Inhaltszusammenfassung zur Seite Nr. 16
6.5. Define Communication Manager as Managed Element Before adding SIP users, Communication Manager must be added to System Manager as a managed element. This action allows System Manager to access Communication Manager over its administration interface. Using this administration interface, System Manager will notify Communication Manager when new SIP users are added. To define Communication Manager as a managed element, select Elements Inventory Manage Elements on the left and click
Inhaltszusammenfassung zur Seite Nr. 17
In the Attributes tab: Login / Password: Enter the login and password used for administration access. Is SSH Connection: Enable SSH access. Port: Enter the port number for SSH administration access (5022). Defaults can be used for the remaining fields. Click Commit to save the settings. JAO; Reviewed: Solution & Interoperability Test Lab Application Notes 17 of 29 SPOC 11/3/2011 ©2011 Avaya Inc. All Rights Reserved. Algo-8028-SM
Inhaltszusammenfassung zur Seite Nr. 18
6.6. Add Application Sequence To define an application for Communication Manager, navigate to Elements Session Manager Application Configuration Applications on the left and select New button (not shown) on the right. Fill in the following fields: Name: Enter name for application. SIP Entity: Select the Communication Manager SIP entity. CM System for SIP Entity Select the Communication Manager managed element. Click Commit to save the Application definition. JAO;
Inhaltszusammenfassung zur Seite Nr. 19
Next, navigate to Elements Session Manager Application Configuration Application Sequences to define the Application Sequence for Communication Manager as shown below. Provide a Name (e.g., DEVCON App Sequence) for the Application Sequence and under Available Applications, click on the plus ( ) sign by DEVCON-APP to add it under the Application in this sequence section. Verify a new entry is added to the Applications in this Sequence table and the Mandatory column is as shown bel
Inhaltszusammenfassung zur Seite Nr. 20
6.7. Add SIP User Add a SIP user for the 8028 SIP Doorphone. The following configuration will automatically create the SIP station on Communication Manager Evolution Server. To add new SIP users, navigate to Users User Management Manage Users from the left and select New button (not shown) on the right. Enter values for the following required attributes for a new SIP user in the Identity tab of the new user form. Last Name: Enter the last name of the user. First Nam
