Page 1
Abstract These Application Notes describe the configuration steps required to integrate Grandstream GXV3240 and GXV3275 Multimedia IP Phones for Android™ with Avaya Aura® Session Manager and Avaya Aura® Communication Manager. Readers should pay attention to Section 2, in particular the scope of testing as outlined in Section 2.1 as well as the observations noted in Section 2.2, to ensure that their own use cases...
Page 2
DevConnect Compliance Testing is not intended to substitute full product performance or feature testing performed by DevConnect members, nor is it to be construed as an endorsement by Avaya of the suitability or completeness of a DevConnect member’s solution.
“isfocus” feature tag. This feature tag indicates that the URI in the Contact header field is a conference URI. Avaya phones update their display to show the conference URI display information (e.g. Conference 2) which indicates the number of other parties in the conference.
The configuration consists of an Avaya Aura® Communication Manager Server with an Avaya G450 Media Gateway providing connectivity to the PSTN via an ISDN-PRI trunk, Avaya Aura® System Manager, and Avaya Aura® Session Manager. Avaya Aura® Messaging was used as the voicemail system.
Avaya 2400 Series Digital Telephones Avaya 1600 Series IP Deskphones 1.3.6 Avaya E129 SIP Deskphones Avaya E169 Media Station Avaya 9600 Series IP Deskphone (96x1 – SIP and H.323) Avaya one-X® Communicator (SIP and 6.2.5 H.323) Avaya Communicator (for Windows, 2.1 (Windows and Android)
5. Configure Avaya Aura® Communication Manager These Application Notes assume that basic Communication Manager administration has already been performed, including the configuration needed to establish a SIP trunk to Session Manager. Consult Reference [1] for further details if necessary. All configuration in this section is administered using the System Access Terminal (SAT).
Page 8
5.2. Verify Station Configuration It is assumed all Avaya endpoints have already been configured. The stations used for the Grandstream endpoints do not need to be configured via the SAT. Rather, stations will be automatically created in Communication Manager when the SIP Users are added in Section 6.1.
6. Configure Avaya Aura® Session Manager Configuration of Avaya Aura® Session Manager is performed via Avaya Aura® System Manager. These Application Notes assume that basic System Manager and Session Manager administration has already been performed, including the configuration needed to establish a SIP trunk to Communication Manager.
6.1. Configure Users This document assumes all Users for Avaya SIP endpoints have already been provisioned in System Manager. Add a User for each Grandstream phone. Navigate to Home Users User Management Manage Users. Click the New button.
Page 13
Click the Communication Profile tab. Enter the Communication Profile Password, and then enter it again in Confirm Password. Click the New button under Communication Address. Select Avaya SIP for Type. Enter the Full Qualified Address for the user and then click the Add button.
Page 15
Communication Manager station Extension (e.g. 53108). From the Template drop-down menu, select 9641SIP_DEFAULT_CM_6_3. Enter the desired value for the station Security Code. For Voice Mail Number, enter the Avaya Aura® Messaging pilot number. Click the Endpoint Editor button next to Extension field.
Avaya. Note: Only the configuration steps required to integrate the Grandstream GXV3240 phone model with Avaya are shown in the sub-sections below; however the same steps are required and applicable to the Grandstream GXV3275 phone model. 7.1. Web Interface Access the phone web interface by opening a web browser and entering the following URL: http://ip-address, where ip-address is the IP address of the phone.
SIP Authentication Password: Enter the password for the User created in Section 6.1. Voice Mail UserID: Enter the Avaya Aura® Messaging pilot number. Configuration of Avaya Aura® Messaging is outside the scope of this document. The mailboxes for the Grandstream phones are configured the same and Avaya phones).
By default, the Grandstream phones support packetization mode set to 1. At the time of testing, the Avaya video endpoints did not support packetization mode set to 1. Therefore, the packetization mode value on the Grandstream phones was changed to 0.