Avaya 9611G Button Configuration via 46xxsettings.txt

[Brett Power]

I am re-configuring some of my 9611G sets to work with in a non-Avaya SIP environment. I have the phones working; they authenticate to the SIP provider and can make/receive calls. I am using firmware 96x1-IPT-SIP-R7_0_1_4-020917.

I know how to resolve my issues using Avaya Manager, however, in a non-Avaya environment it isn't possible.

My only issues are as follows:
[ol]
[li]I can't seem to find a way to configure the buttons via 46xxsettings.txt. I've tried "SET PHONEKEY" but that isn't taking hold; nothing happens with it.[/li]
[li]The SIP username is somehow applied to 3 line selection buttons on the right side, which I don't want. (see attached image)[/li]
[li] Is there a way to make the voicemail button call the user that is logged in? I ask this because IF I can configure the buttons via 46xxsettings.txt then I can't just hard-code a number in and have it work for all users.[/li]
[/ol]

SET LOGOS Cefla=

https://i.imgur.com/0hWihoY.png

SET CURRENT_LOGO "Cefla"
SET LOGOSTAT 1
SET SIPDOMAIN xxx.xx.com
SET SIP_CONTROLLER_LIST xxx.xx.xxx.xxx:5060;transport=tcp
SET SIPSIGNAL 1
SET SIPPORT 5060
SET SNTPSRVR 129.6.15.28
SET ENABLE_AVAYA_ENVIRONMENT 0
SET GMTOFFSET -5:00
SET PHNSCRALL 1
SET PHNNUMOFSA 3
SET DISPLAY_NAME_NUMBER 1
SET PHONEKEY "Key=5;Type=autodial;Name=autodial;attr1=6837"
SET ENABLE_SIP_USER_ID 1
SET FBONCASCREEN 1
SET DIALPLAN [5]xxxx|1xxxxxxxxxx
SET PHNDPLENGTH 4
SET ENABLE_PRESENCE 1

 

[Brett Power]

I just found this regarding the exclamation mark showing on the display. This might be the hint I've been searching for.....


"Cause
The exclamation mark shows up when a PPM/AST download has failed on the IP Phone. IP Phones in the AST mode (registered to Session Manager, with an off PBX station on Communication Manager) receive CM features and buttons via SIP subscribe and notify messages. When a subscribe/notify fails and the IP Phone displays the exclamation mark on the phone screen.

This was tested in a Communication Manager and Session Manager environment in an Avaya services lab.

Two common reasons for this issue are -

- Origination and Termination Application Sequences are not configured in the Session Manager Profile section of the User Profile administration in System Manager.

- The Communication Manager is missing an entry (Ext length, Ext Code, SIP Trunk Group and Total Length) in the private/public-unknown numbering form. This is generally the case when a specific series of extension have the problem.

Solution
- Set appropriate Origination and Termination Application Sequences in the Session Manager Profile section of the User Profile administration in System Manager.

- Configure the private/public-unknown numbering form on Communication Manager to send the extension number correctly over the SIP trunk.

 

[janni78]

The PHONEKEY parameter is only supported on J100 SIP R4.0.1.0 and later (J169/J179 only).

Any tips on how to fine-tune Avaya phones on other phone systems are probably better answered by their support/forums.


"Trying is the first step to failure..." - Homer

 

[gwebster]

Avaya supports the J100-series on non-Avaya platforms. There are configuration guides for Broadsoft, Asterisk, 3CX, and FreeSWITCH on the support portal.