Minded Systems » system consultation and software development group. December 1. 6th, 2. Tyler Winfield. With Vo. IP technology growing so rapidly, the marketplace so too has an ever growing selection of hardware options available for system implementations.
Thanks for the great write up. I have everything up and running just as written in the article, but get no audio when calling from a 3CX extension to anything on the.
The Cisco IP Phone series has solidified its position in the community as the leader of high quality and reliable hardware with feature rich firmware and a good range of supported protocols. Superb call quality, a large easy- to- read display screen and user- friendly button layouts/designs make the Cisco phone models of old and late some of the best hardware available for IP- based phone systems.
However, for all their outstanding advantages, configuring these phones to work with a non- Cisco managed Vo. IP network can be a bit of a chore. To further complicate this task, the information available on configuring the newer and more user- preferred devices (touch screens, color backlit display, etc.) is extremely sparse and largely unconfirmed. After heading up the deployment of 3 small Asterisk based PBX deployments, all of which were to make use of various different Cisco IP Phone models; a great deal of information about these phones has been collected. From that information, the steps to configure the following phone models has been confirmed: 7. Communicator (softphone).
A Cisco 7. 97. 5 was not available for testing, however, the 7. X5 models have standardized configuration templates and the information for these units should apply (We are still trying to acquire one to confirm this). One of the most valuable and available resources in setting up systems has been peer communities.
- UpdateStar is compatible with Windows platforms. UpdateStar has been tested to meet all of the technical requirements to be compatible with Windows 10, 8.1, Windows 8.
- 3CX is a software PBX that’s easy to install & manage. It includes integrated softphones, WebRTC conferencing and essential add-ons out of the box, at no additional.
Hi Behind a Zywall USG 100 firewall I am trying to access a CalDAV resource via https://posteo.de:8443/ . Most of the time, the connection times out and the. Minded Systems, enterprise & open source systems specialists and custom application software development.
Both local and online resources will assist in working the kinks out of your system. Also, bookmark voip- info. A large number of Asterisk / Cisco configuration issues are identified and often fixed here. I’d also like to give a special thanks to Sean Walberg for suggesting Wireshark (tshark) for helping to debug connection and other TCP/IP issues (along with an immense amount of guidance and other troubleshooting tips) and to Angel Castaneda for always providing helpful suggestions to get me pointed in the right direction. Now, with the introduction out of the way, let’s begin.
Asterisk. The first component of the system will obviously be the Asterisk IP PBX server. For the sake of this guide I’m going to assume that this has been installed on a server with default settings. If assistance is required in getting an Asterisk server setup or configured with defaults, please consult one of the several sites on Asterisk assistance. The system that was used for the making of this guide is a turn- key installation package as distributed by Asterisk.
NOW. The Asterisk. NOW install is a complete installation package available for free that runs off of the Cent. OS Linux distribution. It comes pre- configured with a working asterisk installation (with all major / common libraries installed) and the Free.
PBX GUI for administering the Asterisk server via a web interface. For more information on this customized distribution, please see the Asterisk. NOW Homepage. 2) TFTP Server. A TFTP (Trivial File Transfer Protocol) Server is not normally required for the setup of an Asterisk IP PBX.
The Cisco IP Phones require configuration files downloaded from a TFTP server for their internal settings. We will get into the configuration files later, for now we will just be setting up the TFTP server. The first step is to connect to the Asterisk server via SSH as root.
Once connected to the server, install the TFTP software: yum install tftp- server. The TFTP server is an . By default, the folder used by the TFTP server is /tftpboot. Changing this is not necessary. Once installed run the following commands to ensure that both xinetd and the TFTP server are initialized on server startup: chkconfig xinetd on. NOTE: The TFTP server for the Cisco IP Phones can be located on a different server if desired.
I chose to install it on the same server as Asterisk for 1) simplicity, and 2) to ensure the system was self- contained. If the TFTP is on a different address, ensure that the appropriate IP address is used when referring to the TFTP server for the remainder of the process. Cisco IP Phones using SIP firmware will use DHCP- option (port) 6. TFTP server and obtaining its configuration. Phones loaded with firmware that makes use of a Cisco Call Manager application (usually SCCP or MGCP) may look for configuration information on port 1.
TFTP port used by the CCM). Firmware. All Cisco IP Phones have several different types of firmware available. Each type of firmware is programmed to support a different Vo. IP protocol. The three supported protocols are SCCP or .
The protocols that are most commonly seen in system deployments are SIP or SCCP. The firmware that is distributed by Cisco is a licensed software product, and as a result, Cisco requires that a license be purchased and verified before allowing downloads.
Although not “legally” permitted other firmware downloads can often be found through creative internet searching. In addition to the three supported protocols, there are also several different versions of each firmware. In most cases it is recommended that the most recent version of firmware for the needed protocol be used. Older firmware will usually work, but often with limited functionality.
A helpful note when phones have issues upgrading their firmware; downgrading the firmware before upgrading will often load the newest versions when direct upgrades fail (eg. Phone currently with SCCP 8. SIP 8. x directly, loading SIP 7. SCCP 7. x before upgrading to SIP 8. Multiple downgrades / upgrades may be needed to load the proper firmware version. The Cisco IP Phone firmware is organized differently depending on the model of phone being used.
XML configured devices (7. The un- archived firmware consists of several files with varying extensions. All firmware will have an application loader file that directs the downloading of the software.
It is identified by the protocol it provides, the phone model it is for, and the version of its firmware with a . SIP7. 0. 8- 4- 2. S. loads: SIP = protocol, 7. S). The second format of firmware is for the 7. XML phones. These devices make use of a pair of files for its firmware. The files are named by similar convention; identifying protocol and version.
This firmware format is not device specific so the same firmware can be used on both the 7. P0. S3- 8- 1. 2- 0. S = SIP, 8- 1. 2- 0. All of the firmware files that are going to be used will need to be placed in the directory being used for the TFTP server (usually /tftpboot). It is recommended that firmware in . This can be done by simply renaming the . Once all the necessary firmware for the phones being used has been placed on the TFTP server, configuration files will complete the setup.
Global Configuration Files. Anyone setting up an Asterisk PBX with Cisco IP Phones will quickly discover that there are several different models available. In this guide a variety of models will be discussed, all of which have been successfully configured and confirmed as working. To my knowledge, all of the major Cisco IP Phone models are able to work with an Asterisk server in some capacity.*DISCLAIMER: only confirmed working units will be discussed, ability of other models to work is pure speculation. In searching the internet for information on configuring Asterisk with Cisco IP Phones, a great deal of the information available is for the Cisco 7.
These seem to be the most commonly used models with Asterisk IP PBX servers. Both of these models use the same firmware and near identical configuration files. The Cisco 7. 96. 0 provides 6 programmable lines where the 7.
The Cisco 7. 91. 4 is an expansion module available for the. Currently a 7. 91. Current information indicates that this should work without. Although seen less commonly, the Cisco 7. Cisco 7. 94. 5 are similar in physical appear with some more advanced functionality and a full color display screen. Additionally, these models make use of more advanced XML configuration templates instead of text based data. Specifics on these configuration methods will be discussed later.
Last are the Cisco 7. IP Communicator. The Cisco 7. Asterisk deployments. The 7. 97. 0 offers a full color touch screen display, 5 soft keys (1 more than its predecessors), and 8 programmable lines.
The Cisco IP Communicator is the software phone that is compatible with the Cisco IP Phone networks. The Communicator software is modeled after the 7. Each group of phone models is slightly different although the main functions provided by all units are the same. It should also be pointed out that the SIP firmware for these phones is NOT perfect.
The firmware does have limitations, although new versions seem to have near complete functionality. Regardless of the model(s) of phones used in the deployment, there will be a few files required for configuration.
In general, most Cisco IP Phones will require an application loader (txt) file, a generic configuration file, a dialling plan, a ringer list, and a phone settings file. The application loader file, generic configuration file, dialling plan and ringer list can all be re- used for every phone on the system to simplify deployment. For the sake of this guide, we will assume these files are being re- used. OS7. 9xx. txt. OS7.
Cisco 7. 96. 0 or 7. The one line of text contained in this file is the filename of the firmware that these phones are to make use for connection.
This file is not used for any of the phones that make use of XML configuration files. XMLDefault. cnf. xml. The XMLDefault. cnf.
Cisco IP Phones to be used. This file will also contain the general information on firmware to use for the various different IP phone models.
An example file is as follows: The main section of this generic configuration file is its application loader assistance. The various different < load. Information>. SIPDefault.