Yealink 3CX template errors

Discussion in '3CX Phone System - General' started by giwm, Dec 14, 2017.

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

    giwm New Member

    Joined:
    Sep 27, 2016
    Messages:
    217
    Likes Received:
    36
    The Yealink Factory templates have a few errors in them. The following all should have static. prepended to them:

    network.internet_port.ip =
    network.internet_port.mask =
    network.internet_port.gateway =
    network.primary_dns=
    network.secondary_dns =
    network.dhcp_host_name =

    Finally, this: phone_setting.lock = 0
    Should be this: phone_setting.phone_lock.enable = 0
     
  2. giwm

    giwm New Member

    Joined:
    Sep 27, 2016
    Messages:
    217
    Likes Received:
    36
    Actually, the whole network.X section needs to be reviewed. It looks like they recently switched them all to add the static. up front.
     
  3. cobaltit

    cobaltit Active Member

    Joined:
    Mar 22, 2012
    Messages:
    735
    Likes Received:
    113
    Having not looked at this at all, any chance that the changes you are seeing are for a more recent firmware than what is currently approved by 3CX? That might explain the discrepancy.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
    #3 cobaltit, Dec 14, 2017
    Last edited: Dec 15, 2017
  4. giwm

    giwm New Member

    Joined:
    Sep 27, 2016
    Messages:
    217
    Likes Received:
    36
    @cobaltit: No, I was looking up the template settings for the latest approved firmware. :)

    It seems the static.network stuff works both ways. The phone_lock.enable does not.
     
  5. giwm

    giwm New Member

    Joined:
    Sep 27, 2016
    Messages:
    217
    Likes Received:
    36
    Confirmed: Static. items are currently 'compatible parameters'. So this leaves phone_setting.lock as the only actual incorrect setting. However, the 3CX template should PROBABLY reflect the latest firmware supported.
     
Thread Status:
Not open for further replies.