PLEASE HELP! Yealink T46S custom config not pushing out to phone

Discussion in '3CX Phone System - General' started by dlaborde002, Feb 9, 2018.

Tags:
Thread Status:
Not open for further replies.
  1. dlaborde002

    Joined:
    Feb 9, 2018
    Messages:
    8
    Likes Received:
    0
    Please HELP!!! I have been unsuccessful with pushing out a custom template to my Yealink T46S ip phone, paired with an EXP40 expansion module. I am able to effect the time zone with my changes. However, I can not get my line keys or expansion module values to push out. I feel like there must be a trigger that I am missing.
    I am running 3CX version 15.5. Yealink T46S has firmware version 66.81.0.110.

    Here was my process:

    1. Made a copy of the yealinkT4x.ph.xml template provided by 3CX, named it "yealinkT4x_Custom.ph.xml"

    2. Ensured that the model names from lines 494-512 matched the model names from lines 10-27, and replaced all "y0000000000" with "y1000000000" for the cfg files.

    Code:
    10   <model ua="SIP-T19P_E2">Yealink T19P E2-yealinkT4x_Custom</model>
          <model ua="SIP-T19_E2">Yealink T19 E2-yealinkT4x_Custom</model>
          <model ua="SIP-T21P_E2">Yealink T21P E2-yealinkT4x_Custom</model>
          <model ua="SIP-T21_E2">Yealink T21 E2-yealinkT4x_Custom</model>
          <model ua="SIP-T23P">Yealink T23P-yealinkT4x_Custom</model>
          <model ua="SIP-T23G">Yealink T23G-yealinkT4x_Custom</model>
          <model ua="SIP-T27P">Yealink T27P-yealinkT4x_Custom</model>
          <model ua="SIP-T27G">Yealink T27G-yealinkT4x_Custom</model>
          <model ua="SIP-T29G">Yealink T29G-yealinkT4x_Custom</model>
          <model ua="SIP-T40P">Yealink T40P-yealinkT4x_Custom</model>
          <model ua="SIP-T41S">Yealink T41S-yealinkT4x_Custom</model>
          <model ua="SIP-T41P">Yealink T41-yealinkT4x_Custom</model>
          <model ua="SIP-T42S">Yealink T42S-yealinkT4x_Custom</model>
          <model ua="SIP-T42G">Yealink T42-yealinkT4x_Custom</model>
          <model ua="SIP-T46S">Yealink T46S-yealinkT4x_Custom</model>
          <model ua="SIP-T46G">Yealink T46-yealinkT4x_Custom</model>
          <model ua="SIP-T48S">Yealink T48S-yealinkT4x_Custom</model>
    27   <model ua="SIP-T48G">Yealink T48-yealinkT4x_Custom</model>
    
    492      <field name="Name">Yealink T4X</field>
          <deviceconfig filename="y100000000029.cfg">
            <filename>
              <model name="Yealink T19 E2-yealinkT4x_Custom" filename="y100000000053.cfg" />
              <model name="Yealink T19P E2-yealinkT4x_Custom" filename="y100000000053.cfg" />
              <model name="Yealink T21 E2-yealinkT4x_Custom" filename="y100000000052.cfg" />
              <model name="Yealink T21P E2-yealinkT4x_Custom" filename="y100000000052.cfg" />
              <model name="Yealink T27P-yealinkT4x_Custom" filename="y100000000045.cfg" />
              <model name="Yealink T27G-yealinkT4x_Custom" filename="y100000000069.cfg" />
              <model name="Yealink T29G-yealinkT4x_Custom" filename="y100000000046.cfg" />
              <model name="Yealink T23P-yealinkT4x_Custom" filename="y100000000044.cfg" />
              <model name="Yealink T23G-yealinkT4x_Custom" filename="y100000000044.cfg" />
              <model name="Yealink T40P-yealinkT4x_Custom" filename="y100000000054.cfg" />
              <model name="Yealink T41-yealinkT4x_Custom" filename="y100000000036.cfg" />
              <model name="Yealink T41S-yealinkT4x_Custom" filename="y100000000068.cfg" />
              <model name="Yealink T42-yealinkT4x_Custom" filename="y100000000029.cfg" />
              <model name="Yealink T42S-yealinkT4x_Custom" filename="y100000000067.cfg" />
              <model name="Yealink T46-yealinkT4x_Custom" filename="y100000000028.cfg" />
              <model name="Yealink T46S-yealinkT4x_Custom" filename="y100000000066.cfg" />
              <model name="Yealink T48-yealinkT4x_Custom" filename="y100000000035.cfg" />
              <model name="Yealink T48S-yealinkT4x_Custom" filename="y100000000065.cfg" />
    512        </filename><![CDATA[#!version:1.0.0.1
    3. Changed time zone to "-6" United States-Central Time
    4. Added personalized Line Key values.
    Code:
    {IF ua=SIP-T46S}
    #Configure Line Key1
    linekey.1.line = 1
    linekey.1.value =
    linekey.1.pickup_value =
    linekey.1.type = 15
    linekey.1.label = %%extension_first_name%% %%extension_last_name%%
    
    #Configure Line Key2                    
    linekey.2.line = 1                    
    linekey.2.value =                      
    linekey.2.pickup_value =                
    linekey.2.type = 15                                  
    linekey.2.label = %%extension_first_name%% %%extension_last_name%%
    
    #Configure Line Key3
    {IF blf1}
    linekey.3.line = 1                  
    linekey.3.value = SP1                
    linekey.3.pickup_value =      
    linekey.3.type = 10                                  
    linekey.3.label = SP 1
    linekey.3.extension =
    {ELSE}
    linekey.3.type =  0
    {ENDIF}                
    
    {IF blf2}
    linekey.4.line = 1                    
    linekey.4.value = SP2                    
    linekey.4.pickup_value =          
    linekey.4.type = 10                                  
    linekey.4.label = SP 2
    linekey.4.extension =
    {ELSE}
    linekey.4.type =  0
    {ENDIF}                      
    
    {IF blf3}
    linekey.5.line = 1                      
    linekey.5.value = SP3                    
    linekey.5.pickup_value =                
    linekey.5.type = 10                                  
    linekey.5.label = SP 3
    linekey.5.extension =
    {ELSE}
    linekey.5.type =  0
    {ENDIF}                      
    
    {IF blf4}
    linekey.6.line = 1                      
    linekey.6.value = SP4                    
    linekey.6.pickup_value =              
    linekey.6.type = 10                                  
    linekey.6.label = SP 4
    linekey.6.extension =
    {ELSE}
    linekey.6.type =  0
    {ENDIF}
    
    {IF blf5}
    linekey.7.line = 1                    
    linekey.7.value = 1234567890                  
    linekey.7.pickup_value =              
    linekey.7.type = 3                                  
    linekey.7.label = X Cell
    linekey.7.extension =
    {ELSE}
    linekey.7.type =  0
    {ENDIF}  
    
    {IF blf6}
    linekey.8.line = 1                      
    linekey.8.value = 1234567890              
    linekey.8.pickup_value =            
    linekey.8.type = 3                            
    linekey.8.label = X Cell
    linekey.8.extension =
    {ELSE}
    linekey.8.type =  0
    {ENDIF}  
    
    {IF blf7}
    linekey.9.line = 1              
    linekey.9.value = 1234567890                  
    linekey.9.pickup_value =            
    linekey.9.type = 3                                  
    linekey.9.label = X Cell
    linekey.9.extension =
    {ELSE}
    linekey.9.type =  0
    {ENDIF}    
    5. Added personalized expansion module key values that have both transfer and BLF functions (keys 1-40).

    Code:
    {IF ua=SIP-T46S}
    #Expansion module1 key1
    {IF blf20}
    expansion_module.1.key.1.type = 16
    expansion_module.1.key.1.line = 1
    expansion_module.1.key.1.value = 123
    expansion_module.1.key.1.pickup_value = 123
    expansion_module.1.key.1.label = X
    expansion_module.1.key.1.extension = 123
    expansion_module.1.key.1.xml_phonebook =
    {ELSE}
    expansion_module.1.key.1.type = 37
    expansion_module.1.key.1.label = List 1
    {ENDIF}
    
    #Expansion module1 key2
    {IF blf21}
    expansion_module.1.key.2.type = 3
    expansion_module.1.key.2.line = 1
    expansion_module.1.key.2.value = *98123
    expansion_module.1.key.2.pickup_value = 123
    expansion_module.1.key.2.label = X VoiceMail
    expansion_module.1.key.2.extension =
    expansion_module.1.key.2.xml_phonebook =
    {ELSE}
    expansion_module.1.key.2.type = NA
    {ENDIF}
    and so on.....

    I then added the Yealink T46S phone to 3CX, applied the custom template, and assigned it to an extension. Then provisioned the phone, but only my time settings were affected. I am able to edit the line keys and expansion module keys through the phone UI. But I need to be able to create one template to push out to multiple Yealink T46S phones. I have spun my wheels all week trying to push these settings so any advice will be much appreciated!
     
    #1 dlaborde002, Feb 9, 2018
    Last edited: Feb 9, 2018
  2. jimbo59

    jimbo59 Member

    Joined:
    Nov 17, 2017
    Messages:
    357
    Likes Received:
    77
    I have similar problem. I had to modify all the BLF by UI and disable updating by 3CX.

    I have 48G
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. dlaborde002

    Joined:
    Feb 9, 2018
    Messages:
    8
    Likes Received:
    0
    I saw the option to disable protect personalized configuration settings even after auto provisioning. But that seems to be very tedious if one has a large number of phones to push out.
     
  4. us1

    us1

    Joined:
    Oct 19, 2015
    Messages:
    80
    Likes Received:
    21
    Don't set them up via web gui. You'll spend all your time doing that. Let's work on the templates.

    Try the following:

    Get rid of the {if} {else} statements for the buttons you are configuring. These are used by 3cx in their code for creating the configurations on the fly. Since you're doing them manually, make a section look like this (using your code as an example):

    Code:
    #Configure Line Key3
    linekey.3.line = 1                
    linekey.3.value = SP1              
    linekey.3.pickup_value =    
    linekey.3.type = 10                                
    linekey.3.label = SP 1
    linekey.3.extension =  
    Make those adjustments, factory reset a phone and then reprovision it to see if that helps you out.
     
  5. cobaltit

    cobaltit Active Member

    Joined:
    Mar 22, 2012
    Messages:
    928
    Likes Received:
    147
    You may also want to update your firmware as that is not the supported version.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  6. dlaborde002

    Joined:
    Feb 9, 2018
    Messages:
    8
    Likes Received:
    0
    I followed your suggestion, but still no luck. I also updated to the latest supported firmware. The strange thing is that line keys 1-6 push out to the phone, but none of the rest will work even though they look exactly the same. As far as the expansion module, I have not been able to effect it through the template at all. The Yealink T46S is the only yealink phones that we have, so the other models listed throughout the template are unnecessary for now, but I thought I would leave it there for future purposes. The template changes now look like this:

    Code:
    Line Keys
    
    {IF blf4}
    linekey.6.line = 1                      
    linekey.6.value = SP4                    
    linekey.6.pickup_value =              
    linekey.6.type = 10                                  
    linekey.6.label = SP 4
    linekey.6.extension =
    
    {IF blf5}
    linekey.7.line = 1                    
    linekey.7.value = 1234567890              
    linekey.7.pickup_value =              
    linekey.7.type = 3                                  
    linekey.7.label = X Cell
    linekey.7.extension =
    
    
    Expansion Module
    
    {IF ua=SIP-T46S}
    {IF blf20}
    #Expansion module1 key1
    expansion_module.1.key.1.type = 16
    expansion_module.1.key.1.line = 1
    expansion_module.1.key.1.value = 123
    expansion_module.1.key.1.pickup_value = 123
    expansion_module.1.key.1.label = Bill
    expansion_module.1.key.1.extension = 123
    expansion_module.1.key.1.xml_phonebook =
    
    #Expansion module1 key2
    {IF blf21}
    expansion_module.1.key.2.type = 3
    expansion_module.1.key.2.line = 1
    expansion_module.1.key.2.value = *98123
    expansion_module.1.key.2.pickup_value = 123
    expansion_module.1.key.2.label = X VM
    expansion_module.1.key.2.extension =
    expansion_module.1.key.2.xml_phonebook =
     
    #6 dlaborde002, Feb 12, 2018
    Last edited: Feb 12, 2018
Thread Status:
Not open for further replies.