{"id":30399,"date":"2019-10-31T21:35:20","date_gmt":"2019-10-31T18:35:20","guid":{"rendered":"https:\/\/prohoster.info\/blog\/voip-zoopark-provisioning\/"},"modified":"2019-10-31T21:35:20","modified_gmt":"2019-10-31T18:35:20","slug":"voip-zoopark-provisioning","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/voip-zoopark-provisioning","title":{"rendered":"VoIP Zoo - Provisioning","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Introduction<\/h4>\n

\nOnce, the management approved an experiment to implement IP telephony in our office. Since my experience in this area was minimal, the task sparked significant interest in me, and I delved into the study of various aspects of the issue. After my deep dive, I decided to share the knowledge I gained, hoping it would be useful to someone. So...<\/p>\n

Source Data<\/h4>\n

\nAsterisk was chosen and deployed as the IP PBX. The phone fleet consists of Cisco 7906g, Panasonic UT-KX123B, Grandstream GXP1400, Dlink DPH-150S(E)\/F3, Yealink T19, and T21 devices. Such a variety was chosen to experiment with different options and create my perspective on the price\/quality\/convenience ratio.<\/p>\n

Task<\/h4>\n

\nMaximally simplify and unify the process of setting up new devices. All phones should be synchronized by time, have a phonebook loaded from server<\/a> and provide access to settings for the administrator.<\/p>\n

The solution to this task is straightforward \u2014 implement automatic phone configuration, known as Provisioning. In fact, this article will focus on my implementation of this wonderful feature.
\n<\/a><\/noindex><\/p>\n

Configuring tftpd, dhcpd<\/h4>\n

\nTo distribute settings to the phones, I chose tftp as a universal option, supported by all platforms, easy to set up and manage.<\/p>\n

No specific setup for tftp was required. I installed the standard tftpd and placed all necessary files in its root directory.
\nI organized the configuration files by directories according to the phone manufacturer. However, the Cisco device didn\u2019t access its folder, so it had to be stored in the root.<\/p>\n

To indicate to the phones the location of the tftp server, I used option-66. Additionally, I divided them into separate classes by manufacturer. Each class received its segment of addresses and an individual folder for configuration files. By the way, devices from D-link had to be identified by MAC addresses since they do not provide manufacturer information in the dhcp request.<\/p>\n

Fragment of dhcpd.conf<\/b><\/p>\n

# \u0423\u043a\u0430\u0437\u044b\u0432\u0430\u0435\u043c \u043d\u0435\u043e\u0431\u0445\u043e\u0434\u0438\u043c\u044b\u0435 \u043e\u043f\u0446\u0438\u0438 \noption option-66 code 66 = text;\n\nclass "panasonic" {\n\tmatch if substring (option vendor-class-identifier,0,9) = "Panasonic";\n\toption option-66 "10.1.1.50\/panasonic\/";\n}\nclass "cisco" {\n\tmatch if substring (option vendor-class-identifier,0,36) = "Cisco Systems, Inc. IP Phone CP-7906";\n\toption option-66 "10.1.1.50\/cisco\/";\n}\n\nclass "grandstream" {\n match if substring (option vendor-class-identifier,0,11) = "Grandstream";\n option option-66 "10.1.1.50\/grandstream\/";\n}\n\nclass "dlink" {\n\tmatch if (binary-to-ascii (16,8,":",substring(hardware,1,4)) = "c8:d3:a3:8d") or\n\t(binary-to-ascii (16,8,":",substring(hardware,1,4)) = "90:94:e4:72");\n\toption option-66 "10.1.1.50\/dlink\/";\n}\n\nclass "yealink" {\n                match if substring (option vendor-class-identifier,0,7) = "Yealink";\n                option option-66 "10.1.1.50\/yealink\/";\n        }\n\n<\/pre>\n
Phones had to be forcibly excluded from the general pool. Otherwise, they refused to go to their 'frog pond'.
\nSubnet configuration example<\/b><\/p>\n
\nsubnet 10.1.1.0 netmask 255.255.255.0 {\n        option routers 10.1.1.1;\n        pool {\n                deny members of \"cisco\";\n                deny members of \"panasonic\";\n                deny members of \"dlink\";\n                range 10.1.1.230 10.1.1.240;\n        }\n        pool {\n                allow members of \"cisco\";\n                range 10.1.1.65 10.1.1.69;\n        }\n        pool {\n                allow members of \"panasonic\";\n                range 10.1.1.60 10.1.1.64;\n        }\n        pool {\n                allow members of \"dlink\";\n                range 10.1.1.55 10.1.1.59;\n        }\n}\n<\/pre>\n
After restarting all involved services, the phones confidently directed their settings to the designated tftp server. All that was left was to place them there.<\/p>\n
Cisco 7906<\/h4>\n
\nI received these devices in factory packaging. I had to reflash them to get them to work with Asterisk. But that's a different story. In this specific case, to configure the device, I created a file SEPAABBCCDDEEFF.cnf.xml in the root of the TFTP server, according to the instructions. Where AABBCCDDEEFF is the device's MAC address.<\/p>\n
There have been many writings about configuring Cisco phones, so I will simply leave the working configuration file.
\nSettings for Cisco<\/b><\/p>\n
\ntrue\n SIP\n root\n ADMIN_PWD\n\n \n D-M-Y\n Central Pacific Standard Time\n     \n         \n             10.1.1.4\n              Unicast\n          \n     \n \n\n   \n 10.1.1.50\n \n 2000\n 5060\n 5061\n \n 10.1.1.50\n   \n \n\n Disable\n\n\n120\n \n\n \n true\n x-cisco-serviceuri-cfwdall\n x-cisco-serviceuri-pickup\n x-cisco-serviceuri-opickup\n x-cisco-serviceuri-gpickup\n x-cisco-serviceuri-meetme\n x-cisco-serviceuri-abbrdial\n false\n 2\n true\n true\n 2\n 2\n 0\n true\n false\n \n \n 6\n 10\n 180\n 3600\n 5\n 120\n 120\n 5\n 500\n 4000\n 70\n true\n None\n \n1\n false\n true\n false\n false\n none\n 101\n 3\navt\n 3\n false\n false\n Cisco Phone\n 2\n false\n 15000\n10\n true\n false\n 16384\n 32766\n\n \n 9\n 10.1.1.50\n 5060\n  2 \n 3\n false\n 3\n \n 4\n 5\n \n true\n true\n false\n true\n \n\n User #103\n 103\n 103\n SIP_PWD\n \n \n$num\n5060\n 184\n 0\n dialplan.xml\n \n\n *0#\n true\n 2\n \n\n\n false\n false\n 1\n 0\n 1\n 0\n 0\n 0\n 1\n 0\n 1,7\n 09:00\n 12:00\n 01:00\n 1\n 2\n 10.1.1.50\n 0\n 100\n 50\n \n 0\n 0\n 5\n 1\n 10.1.1.50\n 0\n 0\n 0\n 0\n 0\n 0\n 1\n 1\n \n1143565489-a3cbf294-7526-4c29-8791-c4fce4ce4c37\n\n Russian_Russian_Federation\n ru_RU\n \n utf-8\n \n\n \n \n \n \n1\n 0\n \n http:\/\/10.1.1.50\/provisioning\/cisco-services.xml\n \n \n \n \n http:\/\/10.1.1.50\/provisioning\/cisco-services.xml\n 96\n 0\n 96\n 2\n 0\n 0\n \n 3804\n <!-- 10.1.1.50 -->\n  \n\n false\n 1\n<\/pre>\n
<\/p>\n
D-Link DPH-150S\/F3<\/h4>\n
\nIf you're about to purchase a phone from this series, be cautious, as auto-configuration is supported only in the 150S\/F3 model. In the 150S\/F2 device that came into my hands, I did not find such functionality.<\/p>\n
The configuration file can be in either xml format or plain text. For xml, there is one requirement: the tag must be at the beginning of the line; otherwise, the parser will ignore it and the corresponding parameter value will not change.<\/p>\n
To configure the phone, two files are used. f0D00580000.cfg \u2014 to store the settings for all phones, and 00112233aabb.cfg (MAC address in lowercase) for individual settings. Individual settings, of course, take precedence.<\/p>\n
The complete set of settings contains more than a thousand lines; to avoid cluttering the article, I will describe the minimum sufficient set of settings. <\/p>\n
The mandatory elements are the root node VOIP_CONFIG_FILE<\/b> and the embedded node version<\/b>. Settings will be applied only if the file version is higher than the current settings in the device. This value can be found through the web interface of the phone in the maintenance section (system management). For factory-default phones, in both cases, this is 2.0002. Additionally, the version of the individual file must be higher than the version of the general file.<\/p>\n
First, I will present the file with the general configuration for all phones. Essentially, it contains all settings; the individual file will only manage the phone number and the display text. <\/p>\n
In the two blocks below, the time zone and time synchronization parameters are set, the initial port for RTP is established, and a network bridge between the WAN and LAN ports of the device is enabled.<\/p>\n
Fragment #1<\/b><\/p>\n
\nDHCP\n2\n1\n1\n0\nVOIP\n10000\n200\n10.1.1.4\n1\n
\n5060\n\n\nSIP1\n10.1.1.50\n5060\n3600\n1\n10.1.1.50\n1\n0\nG711A,G711U,G722\n<\/pre>\n
Remote management settings<\/b><\/p>\n
\n23\n80\n0\n443\n1\n0\n\n\n\nItem1\n10.1.1.152\n10.1.1.160\n\n\n\n\nAccount1\nadmin\nADMIN_PWD\n10\n\n\nAccount2\nguest\nGUEST_PWD\n5\n<\/pre>\n
Phone settings<\/b><\/p>\n
\n123<\/menu>\n123\n\n0\n112\nCompany\n5\n1\n30\n0\n