Hello everyone,
I am trying to figure out how to provision phone configurations, p12 certificate files and a root ca certificate file to 1120e Avaya phones. I work for a DoD agency and I’m trying to develop guidance with how to properly implement PKI and I’m kind of at a road block here. I’ve been searching through Avaya documentation and the only information that I can find with how to use the provisioning client service is documented in the Using the Provisioning Client manual. That informs you that you need to manually place the 1120eSIP.cfg and 1120e.cfg files to /var/mcp/media/prov_pa_installs/sipphone directory. However I’m not so concerned about basic device settings as they are already configured, but it also says that the SIPDefaultConfig.dat, dialplan.txt, banner.txt and secpolicy.txt files should be present and is provided by Avaya, which might contain information that I need. Well those files that are apparently provided by Avaya and I assume copied there when you do the AS 5300 software installation are not in that directory. So first where can I get those files, is there a process through the AS 5300 server that will build those files. Also, I have created a SIP Client device using the mac address of the phone that also allows you to upload a p12 certificate file for the phone. I would like to use this feature so the phone will download and install the device certificate and root ca certificate. I read in the manual that this is stored in the database and not the /var/mcp/media/prov_pa_installs/sipphone directory. So if these settings are stored in the database/application how do I tell the phone to pull the configuration and p12 file from the application? Also, when I look on the phone where you specify the provisioning url there is a device ID and Password section. Well when you create the SIP client device with the mac address there is no place to enter a password for the device, so what account would I use here? Any information that can help fill in the gap between manually configuring the device over tftp vs using the provisioning client service would be extremely helpful!!! Thanks!!!
I am trying to figure out how to provision phone configurations, p12 certificate files and a root ca certificate file to 1120e Avaya phones. I work for a DoD agency and I’m trying to develop guidance with how to properly implement PKI and I’m kind of at a road block here. I’ve been searching through Avaya documentation and the only information that I can find with how to use the provisioning client service is documented in the Using the Provisioning Client manual. That informs you that you need to manually place the 1120eSIP.cfg and 1120e.cfg files to /var/mcp/media/prov_pa_installs/sipphone directory. However I’m not so concerned about basic device settings as they are already configured, but it also says that the SIPDefaultConfig.dat, dialplan.txt, banner.txt and secpolicy.txt files should be present and is provided by Avaya, which might contain information that I need. Well those files that are apparently provided by Avaya and I assume copied there when you do the AS 5300 software installation are not in that directory. So first where can I get those files, is there a process through the AS 5300 server that will build those files. Also, I have created a SIP Client device using the mac address of the phone that also allows you to upload a p12 certificate file for the phone. I would like to use this feature so the phone will download and install the device certificate and root ca certificate. I read in the manual that this is stored in the database and not the /var/mcp/media/prov_pa_installs/sipphone directory. So if these settings are stored in the database/application how do I tell the phone to pull the configuration and p12 file from the application? Also, when I look on the phone where you specify the provisioning url there is a device ID and Password section. Well when you create the SIP client device with the mac address there is no place to enter a password for the device, so what account would I use here? Any information that can help fill in the gap between manually configuring the device over tftp vs using the provisioning client service would be extremely helpful!!! Thanks!!!
