----- Original Message -----
>
> I've just started deploying these (well the T28P model) after years
> of
> Snom issues and they look pretty good (although the documentation is
> execrable; if you thought the Snom stuff was obtuse Yealink have got
> them knocked into a cocked hat!).
>
> Anyway, for provisioning I use HTTP with a DHCP entry like:-
>
> #
> # Yealink Phones
> #
> group {
> #
> # The phone should pickup the
> # model config file (y0000000000000.cfg for the
> # T28P) first and then the MAC.cfg file
> #
> # Yes tftp-server-name to set the DHCP option
> but
> # the http:// tells the phone to get it's files
> via
> # http.
> option tftp-server-name
> "http://192.168.1.13/yealink";;
> #
> host yealinkT28P {
> hardware ethernet 00:15:65:1b:d9:12;
> fixed-address 192.168.1.33;
> option host-name "yealinkT28P";
> }
> }
>
> As the comments say, the phone's first pick up the model dependant
> config file (y0000000000000.cfg for the T28P model) and then the
> MAC.cfg file.
>
> This is nice as you have one model.cfg file for the site-wide config
> and
> then fine tune specific phones (setup different BLF keys and,
> obviously,
> SIP logins for each device) in the MAC.cfg files.
>
> In the y0000000000000.cfg file I have:-
>
> #
> # Auto Provision
> [ autoprovision ]
> path = /config/Setting/autop.cfg
> server_address = http://192.168.1.13/yealink
> [ autop_mode ]
> path = /config/Setting/autop.cfg
> # Mode 7 = at Power On and Weekly
> mode = 7
> # Sunday between 0100 and 0500
> schedule_dayofweek=0
> schedule_time = 01:00
> schedule_time_end = 05:00
> #
>
>
> Re non-web based access. Obviously the config files are on your
> DHCP/Apache/Asterisk server so you can edit them however you like.
>
> You can also enable telnet access to the phones with a 'hidden'
> config option of:-
>
> #
> [ telnet ]
> path=/config/Network/Network.cfg
> telnet_enable=1
> #
>
> but the login/password are the admin defaults so a bit of a security
> hole there. Not really found much useful telnetting into the phone
> but
> I've not played around with it much.
>
> One other useful tip: If you play around in the web interface, set
> the
> phone up and then export the config, you end up with a config.bin
> file
> which is just tar of the config files. A quick diff and you can
> easily
> find out what you need to tweak in your Autoprovision config files.
>
> Hope that helps.
>
> PS - anyone else with useful Yealink tips?
>
We are looking to switch to Yealink from SNOM and that last tip for saving the
configuration is one I have recently asked them about. All sounds very
promising and we hope to get some eval units soon :)
--
Thanks, Phil
--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
http://www.asterisk.org/hello
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
