Quantcast
Channel: VOIP-info.org Wiki Changes
Viewing all articles
Browse latest Browse all 5767

SIP-T28

$
0
0

Auto-provisioning


Some notes on auto-provisioning these phones since the phones are great, but the documentation is nothing short of terrible. I had a lot of trouble finding any documentation so thought I'd share what I've worked out or scraped together. I'm not very good at documentation so feel free to clean this up for me.

In the config examples below, the comments starting with # are what came in the samples I got from a vendor who I believe got them from Yealink. They are not very clear as I don't believe english is the developers first language, if I've been able to make them less ambiguous I've expanded them with a double comment ##.

Configure your dhcp server with the boot/tftp server address, option 66 in windows dhcp server or add something like the following on a *nix box to your dhcpd.conf:

option tftp-server-name "x.x.x.x";
next-server x.x.x.x;

File names on your tftp server, should all be in lower case (assuming its a *nix server, windows tftp server probably wont matter). The phone can be configured with two files on the tftp server. One with the <mac>.cfg and another one called y000000000000.cfg

You should specify all options that will be common to all phones being provisioned in the y000000000000.cfg. My <mac>.cfg only has the "Account" section specified, you can however specify any or all options in either file, if an option is specified in both, it seems to give priority to the <mac>.cfg as you would expect.

You will notice that alot of configuration sections contain an option for 'path' for example:

[ RemotePhoneBook1 ]
path = /yealink/config/Setting/Setting.cfg
URL = http://x.x.x.x/Phonebook1.xml
Name = Phonebook Name

This is where the info specified in this section will be stored on the phone, as the documentation is relatively poor for these phones this comes in handy, as you can set options in the web interface and then telnet into the phone and see how the configuration is saved. The configuration information is stored in the mac or y000000000000.cfg the same way as the phone stores it in the internal configuration file, as in this example above the 'Setting.cfg'. As such if one didn't know the options for "RemotePhoneBook1", you put your phonebook info in the web interface and then telnet in and copy the "RemotePhoneBook1" section out of /yealink/config/Setting/Setting.cfg and put it in the provisioning files to auto provision the phones.

Samples of the phonebook / contact XML's are all the way at the bottom.

Sample Config this is my <mac>.cfg:



[ account ]
path=/yealink/config/voip/sipAccount0.cfg
Enable = 1
Label = 12345
DisplayName = 12345
UserName = 12345
AuthName = 12345
password = Secret
SIPServerHost = my.sip.host.com
SIPServerPort = 5060
SIPListenRandom = 0
SIPListenPort = 5060
Expire = 3600
UseOutboundProxy = 1
OutboundHost = my.sip.host.com
OutboundPort = 5060
EnableEncrypt = 0
BakOutboundHost =
BakOutboundPort = 5060
EnableSTUN = 0
proxy-require =
ptime = 0
srtp_encryption = 0
srtp_encryption_algorithm = 0
BackupSIPServerHost =
BackupSIPServerPort =
Enable 100Rel = 0
precondition = 0
SubsribeRegister = 1
CIDSource = 0
EnableSessionTimer = 1
SessionExpires = 3600
SessionRefresher = 0
EnableUserEqualPhone = 0
BLFList_URI =
SubsribeMWI = 0
AnonymousCall = 0
RejectAnonymousCall = 0



This is my y000000000000.cfg



[ autop_mode ]
path = /yealink/config/Setting/autop. ...

Viewing all articles
Browse latest Browse all 5767

Trending Articles