Dismiss Notice
We would like to remind you that we’re updating our login process for all 3CX forums whereby you will be able to login with the same credentials you use for the Partner or Customer Portal. Click here to read more.

T38G Call Park on Memory Key Lights not working

Discussion in '3CX Phone System - General' started by myfastback.com, Nov 22, 2014.

Thread Status:
Not open for further replies.
  1. myfastback.com

    Joined:
    Nov 21, 2014
    Messages:
    3
    Likes Received:
    0
    I am running 3cx v12 with 30 x yealink t38g's. All phone are running Firmware 38.70.1.33. This is my first install of 3cx and just activated my license. I have changed the provisioning template to the below to map the first 9 memory keys to call park extensions. All phone function properly by parking a call on the designated park number, and also picks the call back up when you press the correct memory key. My issue is the Lights do not turn on at all to specify which call parks are open, or in use. I do have an expansion model (EXT39) on one of the t38g's and when I map a Call Park to on of the keys on the expansion module the lights function properly.

    I searched a few forums and thought at first the fact that I was using an unlicensed demo was my issue. But after I activated the software, restarted the services, and even re-provisioned a phone they still do not work. At this point I don't know if I have an issue with the provisioning template, or a setting or????

    I have also tried the "Subscribe Register" check box on and off the I have read about.

    Any help or thoughts would be greatly appreciated.

    Jason



    Snippet from my modified provisioning template (I am sure I have an issue or two here, as this is my first attempt).
    {IF blf1}
    # Configure Memory Key1
    memorykey.1.line = %%Line%%
    memorykey.1.value = %%blf1%%
    memorykey.1.pickup_value = %%PickupValue%%
    memorykey.1.type = %%DKtype%%
    memorykey.1.xml_phonebook =
    memorykey.1.sub_type = %%type%%
    {ELSE}
    memorykey.1.line = 0
    memorykey.1.value = SP0
    memorykey.1.type = 10
    {ENDIF}
     
  2. craigreilly

    craigreilly Well-Known Member

    Joined:
    Feb 1, 2012
    Messages:
    3,575
    Likes Received:
    303
    memorykey.1.line = 1
    memorykey.1.value = SP1
    memorykey.1.type = 10

    Try changing the Line to 1.
    I know you want them to work on all lines - but I think it will.
    I think the 0 is causing issue.

    Glad to see someone trying SP0. It confused my users. They couldn't understand base 0.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.