T42 /T46 provisinng

Nicki

Any luck finding the Yealink files?

I've pretty much finished writing the T42G, just a few little things to iron out

The T46G is a little different. Yealink haven't been overly consistent with their provisioning template across the T4x range.

I'll pop up a ZIP file once I've finished them.

Cheers,

Greg

Hi Greg,

I managed to get the Yealink T42G provisioned via TL, although when I modify the config file in
/etc/asterisk/provisioning
with variables ${EXTENSION} and ${DISPLAY_NAME} these don't get passed to the created provisioning file.

My models.txt uses following config:
[yealink-t42g]
label=Yealink T42G
lines=2
repeat_registrations=1
line_template=yealink42g_line.cfg
output=${mac}.cfg
input_1=yealink42g_line.cfg
output_1=${mac}_new.cfg

I get an empty file in format 'MAC'.cfg and full config file called 'MAC'_new.cfg copied from contents of yealink42g_line.cfg.

Please could you post your config files, even if they are not fully tested/working including the entry in models.txt? I'd like to see what am I doing wrong. As I get the provisioning file created with extension number, password and server IP, but its missing extension number and display name.

Excerpt from yealink42g_line.cfg

#Enable or disable the accountX, 0-Disabled (default), 1-Enabled;
account.1.enable = 1
account.2.enable = 1

#Configure the label displayed on the LCD screen for accountX.
account.1.label = ${EXTENSION}
account.2.label = ${EXTENSION}

#Enable or disable to use the alert info URL; 0-Disabled, 1-Enabled (default);
account.1.alert_info_url_enable =
account.2.alert_info_url_enable =

#Configure the display name of accountX.
account.1.display_name = ${DISPLAY_NAME}
account.2.display_name = ${DISPLAY_NAME}

#Configure the username and password for register authentication.
account.1.auth_name = ${USERID}
account.1.password = ${PASSWORD}
account.2.auth_name = ${USERID}
account.2.password = ${PASSWORD}

#Configure the register user name.
account.1.user_name = ${USERID}
account.2.user_name = ${USERID}

#Configure the SIP server address.
#account.X.sip_server_host =
account.1.sip_server.1.address = ${SERVER}
account.2.sip_server.1.address = ${SERVER}

#Specify the port for the SIP server. The default value is 5060.
#account.X.sip_server_port =
account.1.sip_server.1.port = 5060
account.1.sip_server.1.expires = 3600
account.2.sip_server.1.port = 5060
account.2.sip_server.1.expires = 3600

And my output 'MAC'_new.cfg

#Enable or disable the accountX, 0-Disabled (default), 1-Enabled;
account.1.enable = 1
account.2.enable = 1

#Configure the label displayed on the LCD screen for accountX.
account.1.label = LABEL IS MISSING
account.2.label = LABEL IS MISSING

#Enable or disable to use the alert info URL; 0-Disabled, 1-Enabled (default);
account.1.alert_info_url_enable =
account.2.alert_info_url_enable =

#Configure the display name of accountX.
account.1.display_name = DISPLAY NAME IS MISSING
account.2.display_name = DISPLAY NAME IS MISSING

#Configure the username and password for register authentication.
account.1.auth_name = 6657-company
account.1.password = 1m8393234
account.2.auth_name = 6657-company
account.2.password = 1m8393234

#Configure the register user name.
account.1.user_name = 6657-company
account.2.user_name = 6657-company

#Configure the SIP server address.
#account.X.sip_server_host =
account.1.sip_server.1.address = 'SERVER IP'
account.2.sip_server.1.address = 'SERVER IP'

#Specify the port for the SIP server. The default value is 5060.
#account.X.sip_server_port =
account.1.sip_server.1.port = 5060
account.1.sip_server.1.expires = 3600
account.2.sip_server.1.port = 5060
account.2.sip_server.1.expires = 3600

Kind regards,

Patrik

Can anyone send me files for Autoprovisoning via TFTP server for 42G and 46G.

kosmac(at)gmail.com

Thank you

Hello everyone,

I have managed to make Yealink T42,T46,T48 provisioning work with freepbx and asterisk. It is not perfect but it will get the job done.I can share it with anyone who is interested to make it better. Also for some reason phone only reads the mac oriented .cfg and not reading y0000000000.cfg.

mpasha at ringmor dot com

Thank you
Rob

File structure inconsistencies across different models and different firmware versions was the biggest reason I hated fooling with yealink. First it was text based, then still text based but different headings and dotted variables, then XML.

They should have taken a lesson from Polycom and standardized the firmware and configs across all models of phones. If a config changes, only do it at a firmware version jump and do it for all phones that will be running that version.

The t4x series solved a lot of physical issues with the older models. They just need to think more efficiently in terms of mass deployment provisioning.