Solved Custom config file doesn't respect "SP1"

Discussion in '3CX Phone System - General' started by engin411, Mar 6, 2017.

Thread Status:
Not open for further replies.
  1. engin411

    engin411 New Member

    Joined:
    Jul 3, 2009
    Messages:
    172
    Likes Received:
    0
    3cx latest version with Yealink T46G phones, latest firmware. I'm editing the default Yealink template to include some features we use, specifically shared park. Below is my values/etc for this, and while the buttons show on the phone, the shared parks show as unregistered and they don't work. Pressing a shared park button during a call does nothing.

    Ideas? Here's what I'm using in the custom template:
    linekey.6.line = 0
    linekey.6.value = SP1
    linekey.6.pickup_value =
    linekey.6.type = 10
    linekey.6.label = Park 11
    linekey.6.extension =
     
  2. craigreilly

    craigreilly Well-Known Member

    Joined:
    Feb 1, 2012
    Messages:
    3,407
    Likes Received:
    274
    I thought the lines were now not ZERO based.
    Perhaps try that..

    Here is mine:
    Code:
    linekey.14.type = 10
    linekey.14.value = SP3
    linekey.14.line = 1
    linekey.14.label = SP 3
    linekey.14.xml_phonebook = 0
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
    engin411 likes this.
  3. CentrexJ

    CentrexJ Member

    Joined:
    May 5, 2009
    Messages:
    442
    Likes Received:
    73
    Yes line must be 1 not 0.

    The best way when in doubt is to have 3CX create a provisioning file for an extension with some Shared Parks and then look at the file that is created (you will have to browse in v15 as the files don't go in the provisioning folder).
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
    engin411 likes this.
  4. engin411

    engin411 New Member

    Joined:
    Jul 3, 2009
    Messages:
    172
    Likes Received:
    0
    That was it, shared parks are working now, thanks guys!
     
Thread Status:
Not open for further replies.