3cx-newb. I have used these phones a lot on SIP systems. Here are some pointers and some may be repeats from others here.
The best version of Cisco SIP loads is 8.5.4 as 3CX support said. It is not just an arbitrary comment. Older versions has issues and every time Cisco fixed one, they created another. I don't think they really want to be industry standard. 8.5.4 was the first version that did not break something when they fixed something.
When a Cisco is factory defaulted 123456789*0# it will look for the term61.loads file which is the first part of booting to its firmware. From memory the .loads file is a text file pointing to the relevant binary files. If you unpack a 8.5.4 sip archive, that file along with other version specific files will be preset. I can't give you exact file names as I am on holidays away from the office.
A good way to get the firmware on outside of the 3CX environment is to use tftpd32 as your tftp server. Configure your dhcp scope option 66 to the ip address of your tftpd32 machine. Put your Cisco binaries into a directory and configure tftpd32 to point to that directory. When you default the phone, you should see it downloading the files via tftp from the directory. It boots several times during this process. When it it booted it will say unprovisioned (from memory) which sounds like you have got this far. You can then go into the phone menu to set things manually. Everything is readonly. To switch to readwrite (once again from memory) press *#. You should see the padlock icon on screen open. You can then manually configure settings to at least see if you are going to be able to get things going. Once the phone is registered and received calls, you will need to build a dialplan.xml file that allows you to call out.
Avoid using the hard reset command. If you have not already done so, this can brick you phone. It should only be used in emergencies as a last resort. 123456789*0# will get it back to factory. Sometimes the firmware update procedure can be painfully long.
I have never set up a 7941, or 7961 on 3CX, but I have done it many times on other SIP systems. I have even written my own provisioning file and software. I don't like using these phones on good systems. I much prefer Yealink and these work brilliantly on 3CX. However, there are many Ciscos around and sometimes getting them to work is the decider to get a Cisco call manager replacement deal over the line. If the Cisco sip firmware is installed and you have a good dialplan.xml file, it should work fine.
The best version of Cisco SIP loads is 8.5.4 as 3CX support said. It is not just an arbitrary comment. Older versions has issues and every time Cisco fixed one, they created another. I don't think they really want to be industry standard. 8.5.4 was the first version that did not break something when they fixed something.
When a Cisco is factory defaulted 123456789*0# it will look for the term61.loads file which is the first part of booting to its firmware. From memory the .loads file is a text file pointing to the relevant binary files. If you unpack a 8.5.4 sip archive, that file along with other version specific files will be preset. I can't give you exact file names as I am on holidays away from the office.
A good way to get the firmware on outside of the 3CX environment is to use tftpd32 as your tftp server. Configure your dhcp scope option 66 to the ip address of your tftpd32 machine. Put your Cisco binaries into a directory and configure tftpd32 to point to that directory. When you default the phone, you should see it downloading the files via tftp from the directory. It boots several times during this process. When it it booted it will say unprovisioned (from memory) which sounds like you have got this far. You can then go into the phone menu to set things manually. Everything is readonly. To switch to readwrite (once again from memory) press *#. You should see the padlock icon on screen open. You can then manually configure settings to at least see if you are going to be able to get things going. Once the phone is registered and received calls, you will need to build a dialplan.xml file that allows you to call out.
Avoid using the hard reset command. If you have not already done so, this can brick you phone. It should only be used in emergencies as a last resort. 123456789*0# will get it back to factory. Sometimes the firmware update procedure can be painfully long.
I have never set up a 7941, or 7961 on 3CX, but I have done it many times on other SIP systems. I have even written my own provisioning file and software. I don't like using these phones on good systems. I much prefer Yealink and these work brilliantly on 3CX. However, there are many Ciscos around and sometimes getting them to work is the decider to get a Cisco call manager replacement deal over the line. If the Cisco sip firmware is installed and you have a good dialplan.xml file, it should work fine.
