{"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\/cs\/blog\/news\/voip-zoopark-provisioning","title":{"rendered":"VoIP zoo \u2013 Provisioning","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\u00davod<\/h4>\n

\nJednou veden\u00ed schv\u00e1lilo experiment s implementac\u00ed IP telefonie v na\u0161\u00ed kancel\u00e1\u0159i. Proto\u017ee moje zku\u0161enosti v t\u00e9to oblasti byly minim\u00e1ln\u00ed, \u00fakol ve mn\u011b vyvolal obrovsk\u00fd z\u00e1jem a pono\u0159il jsem se do studia r\u016fzn\u00fdch aspekt\u016f t\u00e9to problematiky. Po ukon\u010den\u00ed sv\u00e9ho studia jsem se rozhodl sd\u00edlet z\u00edskan\u00e9 znalosti \u2014 v nad\u011bji, \u017ee se n\u011bkomu budou hodit. Tak\u017ee\u2026<\/p>\n

Vstupn\u00ed data<\/h4>\n

\nJako IP-\u00daSTEDNA byl vybr\u00e1n a rozvinut Asterisk. Telefonn\u00ed park se skl\u00e1d\u00e1 z p\u0159\u00edstroj\u016f Cisco 7906g, Panasonic UT-KX123B, Grandstream GXP1400 a Dlink DPH-150S(E)\/F3, Yealink T19 a T21. Takov\u00fd rozptyl je d\u00e1n t\u00edm, \u017ee v r\u00e1mci experimentu bylo rozhodnuto vyzkou\u0161et v\u0161echny tyto mo\u017enosti, abychom si mohli vytvo\u0159it vlastn\u00ed n\u00e1zor na pom\u011br cena\/kvalita\/u\u017eivatelsk\u00fd komfort.<\/p>\n

\u00dakol<\/h4>\n

\nMaxim\u00e1ln\u011b zjednodu\u0161it a unifikovat proces nastaven\u00ed nov\u00fdch p\u0159\u00edstroj\u016f. V\u0161echny telefony mus\u00ed b\u00fdt synchronizov\u00e1ny podle \u010dasu, m\u00edt telefonn\u00ed seznam, kter\u00fd se nahr\u00e1v\u00e1 z serveru<\/a> a poskytovat p\u0159\u00edstup k nastaven\u00edm pro administr\u00e1tora.<\/p>\n

\u0158e\u0161en\u00ed tohoto \u00fakolu je jednoduch\u00e9 \u2014 realizovat automatick\u00e9 nastaven\u00ed telefon\u016f, tzv. Provisioning. O m\u00e9 realizaci t\u00e9to skv\u011bl\u00e9 funkce bude \u0159e\u010d.
\n<\/a><\/noindex><\/p>\n

Nastaven\u00ed tftpd, dhcpd<\/h4>\n

\nPro distribuci nastaven\u00ed telefon\u016fm jsem vybral tftp jako univerz\u00e1ln\u00ed variantu, podporovanou v\u0161emi platformami, kter\u00e1 je jednoduch\u00e1 na nastaven\u00ed a spr\u00e1vu.<\/p>\n

Speci\u00e1ln\u00ed nastaven\u00ed pro tftp nebylo pot\u0159eba. Nainstaloval jsem standardn\u00ed tftpd a um\u00edstil v\u0161echny pot\u0159ebn\u00e9 soubory do jeho ko\u0159enov\u00e9ho adres\u00e1\u0159e.
\nSoubory s nastaven\u00edm jsem um\u00edstil do adres\u00e1\u0159\u016f podle v\u00fdrobce telefonu. Pravda, za\u0159\u00edzen\u00ed od Cisco se do sv\u00e9 slo\u017eky tak n\u011bjak nedostalo, musel jsem je dr\u017eet v ko\u0159enov\u00e9m adres\u00e1\u0159i.<\/p>\n

Abych telefon\u016fm ur\u010dil um\u00edst\u011bn\u00ed tftp-serveru, pou\u017eil jsem option-66. Nav\u00edc jsem je rozd\u011blil do samostatn\u00fdch t\u0159\u00edd podle v\u00fdrobce. Ka\u017ed\u00e1 t\u0159\u00edda dostala vlastn\u00ed segment adres, a individu\u00e1ln\u00ed slo\u017eku pro konfigura\u010dn\u00ed soubory. Mimochodem, za\u0159\u00edzen\u00ed od D-link jsem musel ur\u010dit podle MAC adres, proto\u017ee informace o v\u00fdrobci v dhcp dotazu neposkytuj\u00ed.<\/p>\n

Fragment 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
Telefony bylo nutn\u00e9 n\u00e1siln\u011b vylou\u010dit z celkov\u00e9ho fondu. Jinak se necht\u011bly dostat do sv\u00e9ho \"\u017eabn\u00edku\".
\nP\u0159\u00edklad nastaven\u00ed pods\u00edt\u011b<\/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
Po restartu v\u0161ech zapojen\u00fdch slu\u017eeb se telefony spolehliv\u011b obr\u00e1tily na ur\u010den\u00fd tftp-server pro nastaven\u00ed. Z\u016fst\u00e1v\u00e1 jen je tam um\u00edstit.<\/p>\n
Cisco 7906<\/h4>\n
\nTyto za\u0159\u00edzen\u00ed jsem dostal v tov\u00e1rn\u00edm balen\u00ed. Musel jsem je p\u0159eprogramovat, aby fungovaly s asteriskem. Ale to je jin\u00e1 historie. V konkr\u00e9tn\u00edm p\u0159\u00edpad\u011b jsem pro nastaven\u00ed za\u0159\u00edzen\u00ed podle pokyn\u016f vytvo\u0159il v ko\u0159enov\u00e9m adres\u00e1\u0159i tftp-serveru soubor SEPAABBCCDDEEFF.cnf.xml. Kde AABBCCDDEEFF je MAC adresa za\u0159\u00edzen\u00ed.<\/p>\n
O nastaven\u00ed telefon\u016f Cisco u\u017e bylo naps\u00e1no mnohokr\u00e1t, tak\u017ee zde jednodu\u0161e nech\u00e1m funk\u010dn\u00ed soubor s nastaven\u00edm.
\nNastaven\u00ed pro cisco<\/b><\/p>\n
\ntrue\n SIP\n root\n ADMIN_PWD\n\n \n D-M-Y\n Centr\u00e1ln\u00ed pacifick\u00fd standardn\u00ed \u010das\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 U\u017eivatel #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 Ru\u0161tina_Rusk\u00e1_Federace\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
\nPokud pl\u00e1nujete zakoupit telefon t\u00e9to \u0159ady, dejte si pozor, automatick\u00e9 nastaven\u00ed je podporov\u00e1no pouze u telefon\u016f 150S\/F3. U za\u0159\u00edzen\u00ed 150S\/F2, kter\u00e9 jsem m\u011bl k dispozici, jsem tuto funkci nena\u0161el.<\/p>\n
Konfigura\u010dn\u00ed soubor m\u016f\u017ee b\u00fdt bu\u010f ve form\u00e1tu xml, nebo v b\u011b\u017en\u00e9m textov\u00e9m form\u00e1tu. U xml existuje jedno po\u017eadavek: tag mus\u00ed b\u00fdt na za\u010d\u00e1tku \u0159\u00e1dku, jinak ho parser ignoruje a hodnota p\u0159\u00edslu\u0161n\u00e9ho parametru se nezm\u011bn\u00ed.<\/p>\n
Pro nastaven\u00ed telefonu se pou\u017e\u00edvaj\u00ed dva soubory. f0D00580000.cfg \u2014 pro ukl\u00e1d\u00e1n\u00ed nastaven\u00ed v\u0161ech telefon\u016f a 00112233aabb.cfg (MAC adresa mal\u00fdmi p\u00edsmeny) pro individu\u00e1ln\u00ed nastaven\u00ed. Individu\u00e1ln\u00ed nastaven\u00ed maj\u00ed samoz\u0159ejm\u011b vy\u0161\u0161\u00ed prioritu.<\/p>\n
Celkov\u00fd soubor nastaven\u00ed obsahuje v\u00edce ne\u017e tis\u00edc \u0159\u00e1dk\u016f; abych \u010dl\u00e1nek nezat\u011b\u017eoval, pop\u00ed\u0161u minim\u00e1ln\u00ed nezbytnou sadu nastaven\u00ed. <\/p>\n
Povinn\u00e9 jsou ko\u0159enov\u00fd uzel VOIP_CONFIG_FILE<\/b> a vlo\u017een\u00fd uzel version<\/b>. Nastaven\u00ed budou aplikov\u00e1na pouze tehdy, pokud bude verze souboru vy\u0161\u0161\u00ed ne\u017e aktu\u00e1ln\u00ed nastaven\u00ed v za\u0159\u00edzen\u00ed. Toto hodnotu lze zjistit p\u0159es webov\u00e9 rozhran\u00ed telefonu v sekci \u00fadr\u017eba (syst\u00e9mov\u00e9 \u0159\u00edzen\u00ed). U za\u0159\u00edzen\u00ed s tov\u00e1rn\u00edmi nastaven\u00edmi je v obou p\u0159\u00edpadech hodnota 2.0002. Krom\u011b toho mus\u00ed b\u00fdt verze individu\u00e1ln\u00edho souboru vy\u0161\u0161\u00ed ne\u017e verze obecn\u00e9ho souboru.<\/p>\n
Nejprve uvedu soubor s obecn\u00fdm nastaven\u00edm pro v\u0161echny telefony. V podstat\u011b uchov\u00e1v\u00e1 v\u0161echna nastaven\u00ed, individu\u00e1ln\u00ed soubor bude odpov\u00eddat pouze za \u010d\u00edslo telefonu a n\u00e1pis na obrazovce. <\/p>\n
V dvou bloc\u00edch uveden\u00fdch n\u00ed\u017ee jsou nastaveny parametry \u010dasov\u00e9 z\u00f3ny a synchronizace \u010dasu, po\u010d\u00e1te\u010dn\u00ed port pro RTP a je zapnut\u00fd s\u00ed\u0165ov\u00fd most mezi WAN a LAN porty za\u0159\u00edzen\u00ed.<\/p>\n
Fragment \u010d. 1<\/b><\/p>\n
\n<GLOBAL_CONFIG_MODULE>\n<WAN_Mode>DHCP<\\\/WAN_Mode>\n<Default_Protocol>2<\\\/Default_Protocol>\n<Enable_DHCP>1<\\\/Enable_DHCP>\n<DHCP_Auto_DNS>1<\\\/DHCP_Auto_DNS>\n<DHCP_Auto_Time>0<\\\/DHCP_Auto_Time>\n<Host_Name>VOIP<\\\/Host_Name>\n<RTP_Initial_Port>10000<\\\/RTP_Initial_Port>\n<RTP_Port_Quantity>200<\\\/RTP_Port_Quantity>\n<SNTP_Server>10.1.1.4<\\\/SNTP_Server>\n<Enable_SNTP>1<\\\/Enable_SNTP>\n<Time_Zone>71<\\\/Time_Zone>\n<Time_Zone_Name>UCT_011<\\\/Time_Zone_Name>\n<Enable_DST>0<\\\/Enable_DST>\n<SNTP_Timeout>60<\\\/SNTP_Timeout>\n<Default_UI>12<\\\/Default_UI>\n<MTU_Length>1500<\\\/MTU_Length>\n<\\\/GLOBAL_CONFIG_MODULE>\n<LAN_CONFIG_MODULE>\n<Enable_Bridge_Mode>1<\\\/Enable_Bridge_Mode>\n<Enable_Port_Mirror>1<\\\/Enable_Port_Mirror>\n<\\\/LAN_CONFIG_MODULE>\n<\/pre>\n
N\u00e1zvy konfigura\u010dn\u00edch parametr\u016f jsou dostate\u010dn\u011b \u201ev\u00fdmluvn\u00e9\u201c, aby je nebylo t\u0159eba podrobn\u011b popisovat.
\nSIP pro jednu linku<\/b><\/p>\n
\n5060\n\n\nSIP1\n10.1.1.50\n5060\n3600\n1\n10.1.1.50\n1\n0\nG711A,G711U,G722\n<\/pre>\n
Nastaven\u00ed vzd\u00e1len\u00e9ho ovl\u00e1d\u00e1n\u00ed<\/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
Nastaven\u00ed telefonu<\/b><\/p>\n
\n123\n123\n\n0\n112\nCompany\n5\n1\n30\n0\n