{"id":238,"date":"2023-03-22T12:35:03","date_gmt":"2023-03-22T12:35:03","guid":{"rendered":"https:\/\/jazchye.com\/?p=238"},"modified":"2023-03-22T12:35:04","modified_gmt":"2023-03-22T12:35:04","slug":"good-practices-on-the-zero-config-feature-in-the-grandstream-ucm-series","status":"publish","type":"post","link":"https:\/\/jazchye.com\/index.php\/2023\/03\/22\/good-practices-on-the-zero-config-feature-in-the-grandstream-ucm-series\/","title":{"rendered":"Good practices on the Zero Config feature in the Grandstream UCM series"},"content":{"rendered":"\n
  1. Do not mass provision devices (>30 units) in one go. Users often made a mistake by displaying more than 30 devices on a page, selecting all devices in Zero Config, and clicking on \u2018Update Config\u2019 button. This is not recommended as UCM will consume more time to process and send SIP NOTIFY to each IP phone. This entire process might take several minutes to a few hours, depending on the number of your devices. Do perform provisioning by batch, with each batch consisting of 30 devices.<\/li><\/ol>\n\n\n\n
    \"\"<\/figure>\n\n\n\n
    • Do not click on \u2018Update\u2019 icon every so often on one particular device. Spamming \u2018Update\u2019 will add tons of loads to the UCM and might result in a longer provisioning time for the device. Click once or twice will do.<\/li><\/ul>\n\n\n\n
      \"\"<\/figure>\n\n\n\n
      • After clicking on \u2018Update Config\u2019 button or \u2018Update\u2019 icon, check if there is a new date\/time stamp generated on the \u2018CREATE CONFIG\u2019 column. If the provisioning success, there should be a new date\/time stamp on this column.<\/li><\/ul>\n\n\n\n
        \"\"<\/figure>\n\n\n\n
        • If (3) is performed but there is no new date\/ time stamp being generated, it means that the provisioning might have failed. We will then proceed to check if the device\u2019s IP address is included under UCM web UI > Other Features > Zero Config Settings > Network Settings > Subnet Whitelist.<\/li><\/ul>\n\n\n\n
          \"\"<\/figure>\n\n\n\n
          • If we have confirmed that the device\u2019s IP address is in the subnet whitelist, we will proceed to check from the device\u2019s side (IP Phone). Make sure that \u2018Use Random Port\u2019 is set to \u2018No\u2019. Certain phone models have this setting configured to \u2018Yes\u2019 as default. If \u2018Use Random Port\u2019 is set to \u2018Yes\u2019, what happens is that the UCM will not be able to send SIP NOTIFY to the phone\u2019s correct port and zero config will fail. However, if we try to have the phone requests the config from UCM\u2019s zero config, it will work. But still, it is a good practice to have \u2018Use Random Port\u2019 set to \u2018No\u2019.<\/li><\/ul>\n\n\n\n
            \"\"<\/figure>\n","protected":false},"excerpt":{"rendered":"

            Do not mass provision devices (>30 units) in one go. Users often made a mistake by displaying more than 30 devices on a page, selecting…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4,5],"tags":[],"class_list":["post-238","post","type-post","status-publish","format-standard","hentry","category-ippbx","category-troubleshooting"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t