Cisco CP-7940 phone unable to register to the server:
Aug 21 21:38:52 freepbx in.tftpd[16853]: Client 192.168.168.65 File not found SEP00070E36404B.cnf.xml
Aug 21 21:38:52 freepbx in.tftpd[16854]: RRQ from 192.168.168.65 filename SIP00070E36404B.cnf
Aug 21 21:38:52 freepbx in.tftpd[16854]: Client 192.168.168.65 finished SIP00070E36404B.cnf
Aug 21 21:38:52 freepbx in.tftpd[16855]: RRQ from 192.168.168.65 filename SIPDefault.cnf
Aug 21 21:38:52 freepbx in.tftpd[16855]: Client 192.168.168.65 finished SIPDefault.cnf
Aug 21 21:39:03 freepbx in.tftpd[16904]: RRQ from 192.168.168.65 filename CTLSEP00070E36404B.tlv
Aug 21 21:39:03 freepbx in.tftpd[16904]: Client 192.168.168.65 File not found CTLSEP00070E36404B.tlv
Aug 21 21:39:04 freepbx in.tftpd[16905]: RRQ from 192.168.168.65 filename SEP00070E36404B.cnf.xml
Aug 21 21:39:04 freepbx in.tftpd[16905]: Client 192.168.168.65 File not found SEP00070E36404B.cnf.xml
Aug 21 21:39:04 freepbx in.tftpd[16906]: RRQ from 192.168.168.65 filename XMLDefault.cnf.xml
Aug 21 21:39:04 freepbx in.tftpd[16906]: Client 192.168.168.65 File not found XMLDefault.cnf.xml
Checked the /tftpboot directoryβ¦I can find these files created by the EPM:
dialplan-00070E36404B.xml
SIPDefault.cnf
SIP00070E36404B.cnf
It seem the phone is looking for different files to perform the provisioning.
Please helpβ¦
The SEP Config file is for the SCCP load. The phoneβs way underpowered so making smart choices is really not in the cards.
Iβve never seen a 7940 look for a MAC Specific dialplan file, There wouldnβt be anything in it that you wouldnβt be able to put into the SIPDefault.cnf.xml, though, so that might be part of the issue. This phone is also not looking for that file, so unless itβs referenced in the config someplace, I donβt think ifβs going to find it.
Thank for your reply.
The only xml file generated by the epm is dialplan-00070E36404B.xml.
http_proxy_addr: ββ
http_proxy_port: 80
remote_party_id: 0[root@freepbx tftpboot]# cat dialplan-00070E36404B.xml
Updateβ¦
I renamed the files:
SIP00070E36404B.cnf to SEP00070E36404B.cnf.xml and
SIPDefault.cnf to XMLDefault.cnf.xml
The provisioning seems to have moved forwardβ¦
Aug 22 16:05:10 freepbx in.tftpd[13050]: RRQ from 192.168.168.65 filename SEP00070E36404B.cnf.xml
Aug 22 16:05:10 freepbx in.tftpd[13050]: Client 192.168.168.65 finished SEP00070E36404B.cnf.xml
Aug 22 16:05:17 freepbx in.tftpd[13051]: RRQ from 192.168.168.65 filename CTLSEP00070E36404B.tlv
Aug 22 16:05:17 freepbx in.tftpd[13051]: Client 192.168.168.65 File not found CTLSEP00070E36404B.tlv
If I can find the file: CTLSEP00070E36404B.tlv, I think it will work.
Dave @cynjut please correct me if Iβm wrong, the SEPnnnnnnnnnB.cnf.xml file is (as he said) for SCCP load, which I believe points to the required SIP info for uploading the SIP firmware. I removed those files from the /tftpboot folder to prevent the phones reloading the SIP firmware each time they were booted.
As for the .tlv file I donβt think it is needed, thus maybe your problem is not there.
The TLV file is specifically for connection to CUCMβs License Validation service. Cisco SIP service has nothing even close. It is not required and is completely useless in a SIP context.
I donβt like the SIP load. I donβt. I never recommend it. The phones are too underpowered to do everything they do reasonably well as an SCCP endpoint. Regardless, this phone is the hardest to get working of all of the phones on the market. The money you save on them is offset by the pain in the neck that they cause when you go to configure them.
Totally with you there Dave. The only reason I got some a few years ago was because they were cheap and wanted to self-learn FreePBX/Asterisk. Once I was content enough to deploy a system at my business I upgraded to Sangoma S series phones and free EPM. @kyiu the time you spend on these phones would be better spent on decent modern phones. Looks like you bought EPM so you have plenty of vendors endpoints to choose from.
Good luck!