Cisco Softphone For Mac
This document outlines the basic steps required to install and configure Cisco IP Communicator with Cisco CallManager 4.x/5.x/6.x through manual setup. For autoregistration setup or wide-scale deployments, refer to. Cisco IP Communicator version 2.1 supports Session Initiation Protocol (SIP) as well as the Cisco Unified Communications Manager Skinny Client Control Protocol (SCCP). Note: Cisco IP Communicator is supported in Cisco CallManager 3.3(4). But, this document focuses on Cisco CallManager 4.x/5.x/6.x.
Multiline is a much-needed feature and Cisco should keep advancing Jabber to offer all of the call features available in the obsolescent IP Communicator softphone. Hunt Group & Pickup on the iPhone is now my #1 need. Android also would be good, but iPhone is essential.
- Call control (Bluetooth) with softphones Benjamin Schmidt February 22, 2018 14:13. For MAC Cisco JabberTM for MAC version 11.7 features support for entire portfolio of Sennheiser USB headsets and speakerphones offering fully integrated call-control functionality. If your softphone is not listed as a supported softphone, this doesn't mean.
- No Cisco softphones are available for the Macintosh that would work with the UC520. Cisco has the Unified Personal Communicator that will work with the Mac,.
Cisco recommends that you have knowledge of Cisco CallManager 4.x/5.x/6.x. The information in this document is based on these software versions:. Cisco IP Communicator version 1.1 and 2.x.
Cisco CallManager 4.x/5.x/6.x Note: Refer to for more information on how to find Cisco IP Communicator support for Microsoft Windows Vista. Note: Cisco IP Communicator is supported with Cisco Unified CallManager Express 3.3 and later with Cisco IOS ® Software Release 12.4 Mainline, but when used simultaneously with Cisco Unified Video Advantage, Cisco Unified Communications Manager Express 4.0 (or later) is required.
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command. Refer to for more information on document conventions. Cisco IP Communicator requires:. Cisco Unified Communications Manager 5.0 and later versions when you use Cisco IP Communicator with SIP call-control protocol.
Cisco Unified CallManager Express 3.3 when you use Cisco IOS Software Release 12.4 Mainline. Cisco Unified Communications Manager Express 4.0 and later versions when you use Cisco IP Communicator with Cisco Unified Video Advantage. Cisco Unified Video Advantage 2.0 or later support video telephony. Ensure your camera is supported by video advantage, and refer to for more information. x86-based processors that run a 32-bit OS; currently 64-bit OSs are not supported. Cisco IP Communicator supports SRST with Cisco Unified Survivable Remote Site Telephony 3.3 with mainline or 4.0 and later versions (SCCP only). Cisco Unified Video Advantage gets supported on Cisco IP Communicator from Cisco Unified Communications Manager Version 4.x.
Note: Cisco IP Manager Assistant can be loaded as an application on the same PC as Cisco IP Communicator, but it does not work in the Cisco IP Communicator interface or application. In order to set up Cisco IP Communicator in Cisco CallManager 4.x, you must make sure that your CallManager version is no earlier than 4.0(1)sr2.
Go to the main menu window, choose Help About Cisco CallManager, and then click Details to check your Cisco CallManager version. If your Cisco CallManager version is not at least 4.0(1)sr2, make sure you download the ciscocm.4-0-1-sr2.exe patch from the ( customers only) and apply it to Cisco CallManager.
The section describes this process. Caution: Application of the sr2 patch to Cisco CallManager should be performed during non-business hours, because this process results in interruption of all CallManager services and a server reboot. In order to add Cisco IP Communicator as a phone from the device list, you must have Cisco CallManager 4.0(1)sr2. You can apply the sr2 patch directly to 4.0(1) or 4.0(1)sr1 to take you to 4.0(1)sr2. After you download the sr2 patch, copy the file to a temporary directory on your Cisco CallManager server.
If you do not have direct access to Cisco CallManager, use the in order to connect to the Cisco CallManager from a client PC that runs VNC Viewer. From the directory to which you copied sr2, double-click the executable file. This window appears:.
Click Next and complete the instructions on the window in order to complete the steps to update Cisco CallManager to 4.0(1)sr2. After the server is rebooted, verify that the Cisco CallManager version is 4.0(1)sr2.
See the section. Note: Run CiscoIPCommunicatorAdminToolSetup.exe and install on the TFTP server or Cisco CallManager Publisher. This tool installs the DirectoryWizard tool for configuring the Quick Search and Dialing Rules features. You can download the ( customers only). Note: In this setup, the default Calling Search Space and partitions are used.
Only required fields are filled out, which leaves everything else at default except the Owner User ID. In a typical IP phone network, several partitions and Calling Search Spaces are defined. Complete these steps in order to configure Cisco IP Communicator:. Go to the main menu window, choose Device Phone Add a New Phone, and then select Cisco IP Communicator from the Phone type pull-down menu. Click Next in order to get to the Phone Configuration window. Fill out the required details, such as the MAC address of the phone.
This address should typically be a fixed network interface card (NIC) where Cisco IP Communicator is installed. Click Insert. This message appears:. Click OK in order to get to the Directory Number Configuration window. Fill out the required fields. This message appears:.
Click OK. You have now completed the configuration for Cisco CallManager.
Note: In order to install Cisco IP Communicator in a Laptop/PC that runs Microsoft Windows Vista, it is necessary to connect the headset to the sound card first in order to activate it and then proceed to install the Cisco IP Communicator. Cisco IP Communicator version 2.1 supports Session Initiation Protocol (SIP) as well as the Cisco Unified Communications Manager Skinny Client Control Protocol (SCCP). Cisco IP Communicator 2.1 is supported with Cisco Unified Communications Manager 4.1(3) SR4 and later versions. Cisco IP Communicator supports SIP protocol only with Cisco Unified CallManager 5.x and 6.x.
Complete these steps:. Double-click the CiscoIPCommunicatorSetup.exe icon to run the Install Wizard.
This window appears:. Click Next and follow the instructions. Once the installation is complete, this window appears:. Check the Launch the program check box and click Finish. The Audio Tuning Wizard window appears:.
Click Next. The Select Audio Devices window appears:. Choose the appropriate devices from the pull-down lists and click Next.
Now you must adjust the listening volume. Complete the instructions in order to adjust the listening volume, and then click Next.
The Adjust the Microphone Volume window appears:. Complete the instructions in order to adjust the Microphone Volume, and then click Next. The last window appears:.
Click Finish. If your TFTP setup is incorrect, you get this error:. Click OK. This window appears automatically:.
Click Use these TFTP servers and type in the IP address of the Cisco CallManager if you use a TFTP server on the Cisco CallManager. You must also choose the correct Network Adaptor and Device Name, or this error appears:. The next window asks for your username and password. Enter your username and password and click OK. After a few seconds, the Cisco IP Communicator Launch window appears: In order to avoid choppy voice issues, you need to make sure that you have enabled 802.1p QOS on the PC Network Adapter. Right-click on the connection that you use and choose Properties. For the PC Network Adapter, click Configure and choose the Advanced tab.
Choose 802.1p QOS and then choose Enable The default value for the 802.1p QOS is Disable. Note: The Cisco CallManager sends keepalive acknowledge messages to the registered devices once every 30 seconds.
If Cisco IP Communicator is behind a firewall, or if there is some Access Control List(ACL) configured in the network, the keepalive traffic between the Cisco CallManager and IP Communicator is blocked. In this case, make sure that the firewall/ACL is configured to pass TFTP and RTP traffic using the appropriate. Drag-and-drop dialing. Copy-and-paste dialing. Alphanumeric translation. Keyboard shortcuts for starting and ending calls.
Non-intrusive call notification. Support for Cisco CallManager Express. Cisco CallManager 4.0/4.1 call features (privacy line key, extended services on line keys, multiple calls per line appearance, and so forth) Remote users who use IP Communicator with low bandwidth connections can experience better audio quality with a low-bandwidth codec. Choose Preferences Audio from the Cisco IP Communicator right-click menu, and check Optimize for low bandwidth in order to specify low-bandwidth codec (G.729). Note: When you use Optimize for low bandwidth, it is difficult to connect to some applications that use a different codec other than G.729.
For example, Cisco Conference Connection can only use G.711 codec, thus Cisco IP Communicator is unable to dial a MeetMe Conference number. You should see a similar IP phone bootup sequence, followed shortly by the phone lines that you configured. Your phone is now ready to dial or receive calls. The default Cisco IP Communicator template uses buttons one and two for lines and assigns buttons three through eight as speed dial. Modify your phone button template for IP Communicator in order to configure all eight lines. Complete these steps in order to modify a template:. Choose Device Device Settings Phone Button Template from the Cisco CallManager Administration web application.
Click Find. Click on the copy sign next to Default IP Communicator Template. Fill in a new Button Template Name, for example, IP Communicator eight lines. Change buttons three through eight to Line.
Change the template to IP Communicator eight lines in the Phone Button Template field in the Cisco CallManager Administration Phone Configuration page in order to assign a template to a device. You can configure Quick Search to Access a Personal Address Book with Windows-Based Cisco Unified Communications Managers.
Refer to for more information. Cisco Unified IP Phone Address Book Synchronizer Utility allows you to synchronize Microsoft Outlook and Outlook Express address book entries with the directory in Cisco Unified Communications Manager.
Install the Cisco Unified IP Phone Address Book Synchronizer utility in order to synchronize with Microsoft Outlook. Choose Application Plugins from Cisco Unified CallManager Administration, then locate and click Cisco Unified IP Phone Address Book Synchronizer in order obtain this software for distribution. IP Communicator is the same as normal IP phone, so it uses these ports:. TFTP (UDP 69)—In order to obtain phone configuration and software.
SCCP (TCP 2000)—For skinny (SCCP) signaling. HTTP (TCP 80)—In order to access IP Phone services. RTP (UDP 8)—For audio One-way audio problems are reported while calls are made through the Cisco IP communicator. If you experience occasional one-way audio, try to hold and resume the call while the symptom occurs. This can resolve the problem. If you experience one way audio while you make calls through Cisco IP Communicator, you need to check the connectivity between the IP Communicator and the gateway. If you cannot ping the gateway from the system on which IP communicator is installed, it can be due to some configuration issue, for example, Routing, Access-list and so forth, or due to some firewall configuration.
If there is a firewall between IP Communicator and the gateway, make sure that the ports mentioned in the previous section are opened in the firewall. Refer to for more information on the PIX firewall configuration in order to open the ports.
Note: If you are have a one way audio issue with a Cisco IP Communicator 2.1(2), upgrade to version 2.1(3). Refer to for more information. If the remote party cannot hear the person who placed the call on a Cisco IP Communicator, it can be for one of these reasons:. The Cisco IP Communicator party has muted the recording device. The Cisco IP Communicator party has plugged the headset and speaker plugs into the wrong ports on the PC. The Cisco IP Communicator party is running another application that uses the microphone, such as a sound recorder or another software-based phone.
The Cisco IP Communicator audio settings are incorrect. See the User Guide for Cisco IP Communicator for more information. If the Cisco IP Communicator party cannot hear the remote party, it can be for these reasons:. The Cisco IP Communicator user relies on an unsupported VPN. You must set up a web reflector page or manually specify the IP address in the Network Audio Settings window in order to resolve this issue.
Right-click and choose Audio tab Network button. The Cisco IP Communicator user relies on an unsupported VPN, and Cisco IP Communicator is integrated with a Linux-based Cisco Unified Communications Manager (Release 5.x and later). Run the Cisco IP Communicator Administration Tool on a Windows serverin order to resolve the audio IP address auto-detection problem. If Cisco IP Communicator is behind a firewall, use the appropriate port range and make sure that the firewall is configured to pass TFTP and RTP traffic. IP Communicator users are unable to view corporate directory while connected remotely to the Cisco CallManager.
Complete these steps in order to resolve this issue:. Download Cisco JTAPI from the Cisco CallManager Admin Page and install in the PC where IP Communicator is installed. Choose Install Plugins from Application drop-down menu. Choose Cisco JTAPI Plugins, save in a local folder and install. Download the latest version of IP Communicator from this location of. Choose Service Service Parameters. Choose the Cisco CallManager server and choose Service Cisco TFTP.
Click Advanced and set false to these parameters and update it. Enable Caching of Constant and Bin Files at Startup. Enable Caching of Configuration Files.
Note: For Cisco CallManager 5.x/6.x, choose Service Parameters from the System menu in order to change these parameters. Disable if any windows internal firewall exists. If multiple interfaces are used, disable all other interfaces except the interface which is associated with the IP communicator. Restart the Cisco TFTP service and verify that corporate directory appears in the IP Communicator.
You get the Registration Rejected Error DBConfig error message when IPC connects to Cisco CallManager 5.x. When you try to register an IP communicator to a Cisco CallManager, ensure the Device Name parameter of the Device menu value has the word SEP followed by the MAC address of the PC in which the IP communicator is running.
Complete these steps in order to resolve this error: Choose Phone from the Device menu and then choose Add New and IP Communicator from the Phone Type drop down list. Next, enter SEP in the Device Name field and Save it.
So, first let’s level things out: Versions and Other Information I’m running a rev or two behind in my lab when compared to Bill. Recently, I’ve been focused quite heavily on working with Cisco Unity Connection for large enterprise deployments so my CUCM version is running on 184.108.40.20601-1. What SIP clients are out there for the iPhone? There are a number of them. They come in various names and flavors. Most tout how many different providers they’ve been tested to work with and some even mention Cisco or generically an “enterprise IP PBX”. If there are free SIP clients in the App Store, I didn’t find any myself.
So, since they run anywhere from $4 to $8 each, I chose to test two based on three criteria – research, reviews, and word of mouth. I ended up with: Acrobits Softphone 3.0 WeePhone 1.4.8 Both are available from the iPhone App Store and do not require anything out of the ordinary (like a “jail-broken” phone). Configure CUCM I’m not going to rehash the CUCM configurations in detail because Bill already outlined them in his. You can refer to it for specifics. I’ll provide a brief recap:.
Create a Phone Security Profile for basic 3rd-party SIP devices and enable Digest Authentication. Add a 3rd-Party SIP (Basic) phone and configure it as you would any other phone but under Protocol Specific Information specify the new phone security profile with digest authentication enabled (from Step 1) and set the profile to Standard SIP profile. Also, note that the MAC address is insignificant when you configure endpoints of this type. Create an End User (or a Digest User as it is referred to by some applications and in the device configuration). Make sure you set the Digest Credentials for this user.
[R-SIG-Mac] [R] tcltk installation problem in R (Mac OS X version) [R-SIG-Mac] [R] problem with the installation of r commander on a mac [R-SIG-Mac] problem checking packages with R 2.13.0 [R-SIG-Mac] Problem Installing 2.6.0 on Mac [R-SIG-Mac] First time installation problem [R-SIG-Mac] tkrplot installation problem [R-SIG-Mac] Package. R for Mac OS X This directory contains binaries for a base distribution and packages to run on Mac OS X (release 10.6 and above). Mac OS 8.6 to 9.2 (and Mac OS X 10.1) are no longer supported but you can find the last supported release of R for these systems (which is R 1.7.1) here. Follow instructions in the MacOSX FAQ, section 7(!). (The '9' in the warning is a relic from an older FAQ document.) If you need further guidance open up Terminal.app and tell us what is your equivalent of.
This is the only “password” that matters in this configuration. Associate the SIP device and the Primary Extension to the user. In the 3rd-Party SIP device configuration, set the Digest User to the appropriate End User and save the configuration. Allow me to save you some trouble before proceeding To quote Bill’s, he says “.the resources I have found on-line, including CounterPath’s own write up (which is a bit dated) and an article on Cisco’s “community” collaboration site, were just too light on details.
The examples would have things like this: Account Setup Display Name: 1234 User Name: 1234 Authorized User Name: 1234 I ask you, what am I supposed to do with that if I try to deploy this application in the real world? Now, I am not saying that I am going to cover all bases adequately in this example. Every one of us has a slightly different environment that we operate in. But, I hope to provide some examples to give you a better feel for how to add 3rd Party SIP endpoints to the CUCM.” So, in Bill’s example the End User that he configures as the Digest User has an alphanumeric user ID (ex: bbellsip). Makes sense, right?
A lot of companies configure user ID’s to be indicative of the user’s actual name. Well, unfortunately I have found that this doesn’t really work in my testing of SIP clients for the iPhone. In our setup and testing, we are managing users and authentication directly within CUCM (no LDAP). So, I can safely say that if you are operating in this type of environment and you wish to use either of the SIP applications for iPhone that I tested, then you need to configure your End User such that the User ID = the primary extension assigned to the 3rd-Party SIP device. For example, my End User configuration for Acrobits Softphone looks as follows:. User ID:.
Password: cisco. PIN: 12345. Last Name: Acrobits. First Name: Softphone. Digest Credentials: strongpassword!
Likewise, when you select the Digest User on the 3rd-Party SIP device the user will be. With that said, I must note that I have not yet tested either Acrobits or WeePhone interoperability with a CUCM that is enabled for LDAP integration and authentication. I’ll save that for another blog at some point. Configure the SIP Client for iPhone Depending on which application you use, the configuration screens vary slightly but they ultimately have the following settings that need to be configured as follows: User Name/SIP User: Password: strongpassword! Server/Domain: X.X.X.X (IP address of the server) The Application Reviews My personal preference is the Acrobits Softphone client.
I found it to have an intuitive interface and a sleek, professional design. Virgilio “BONG” dela Cruz Jr. CCDP, CCNA V, CCNP, Cisco IPS Express Security for AM/EE Field Solutions Architect, Tech Data Virgilio “Bong” has sixteen years of professional experience in IT industry from academe, technical and customer support, pre-sales, post sales, project management, training and enablement. He has worked in Cisco Technical Assistance Center (TAC) as a member of the WAN and LAN Switching team. Bong now works for Tech Data as the Field Solutions Architect with a focus on Cisco Security and holds a few Cisco certifications including Fire Jumper Elite. John Cavanaugh CCIE #1066, CCDE #20070002, CCAr Chief Technology Officer, Practice Lead Security Services, NetCraftsmen John is our CTO and the practice lead for a talented team of consultants focused on designing and delivering scalable and secure infrastructure solutions to customers across multiple industry verticals and technologies.
Previously he has held several positions including Executive Director/Chief Architect for Global Network Services at JPMorgan Chase. In that capacity, he led a team managing network architecture and services. Prior to his role at JPMorgan Chase, John was a Distinguished Engineer at Cisco working across a number of verticals including Higher Education, Finance, Retail, Government, and Health Care. He is an expert in working with groups to identify business needs, and align technology strategies to enable business strategies, building in agility and scalability to allow for future changes. John is experienced in the architecture and design of highly available, secure, network infrastructure and data centers, and has worked on projects worldwide.
He has worked in both the business and regulatory environments for the design and deployment of complex IT infrastructures.