[asterisk-users] [OT] Yealink Phones

[Andrew Thomas]

Hi Russell,

Have you seen the 'Action URL' bit yet?  Makes everything almost
key-system like ;)

BTW - one downfall of the Yealink is that it can't send different DND
commands to different accounts (it sends the one command to all
accounts). Not very useful if providers use different commands for DND
(like they tend to).  I know Yealink are working on this though - as I
am one of the 'beta' testers.



-----Original Message-----
From: asterisk-users-bounces at lists.digium.com
[mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Russell
Brown
Sent: 13 April 2011 10:02
To: asterisk-users at lists.digium.com
Subject: Re: [asterisk-users] [OT] Yealink Phones



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?

-- 
 Regards,
     Russell
 --------------------------------------------------------------------
| Russell Brown          | MAIL: russell at lls.com PHONE: 01780 471800 |
| Lady Lodge Systems     | WWW Work: http://www.lls.com              |
| Peterborough, England  | WWW Play: http://www.ruffle.me.uk         |
 --------------------------------------------------------------------

-- _____________________________________________________________________
-- 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


 If you have received this communication in error we would appreciate
you advising us either by telephone or return of e-mail. The contents
of this message, and any attachments, are the property of DataVox,
and are intended for the confidential use of the named recipient only.
If you are not the intended recipient, employee or agent responsible
for delivery of this message to the intended recipient, take note that
any dissemination, distribution or copying of this communication and
its attachments is strictly prohibited, and may be subject to civil or
criminal action for which you may be liable.
Every effort has been made to ensure that this e-mail or any attachments
are free from viruses. While the company has taken every reasonable
precaution to minimise this risk, neither company, nor the sender can
accept liability for any damage which you sustain as a result of viruses.
It is recommended that you should carry out your own virus checks
before opening any attachments. 

Registered in England. No. 27459085.