Skip to main content
Biamp Systems

Cisco CallManager configuration for Audia VoIP-2

Biamp’s VoIP-2 card allows Biamp AudiaFLEX digital signal processors to make and receive phone calls over any Voice-over-IP (VoIP) system that adheres to the SIP (Session Initiation Protocol) standard. This document details the steps required to configure a Cisco CallManager VoIP system to work with Biamp’s VoIP-2 card.

Preliminary steps

AudiaVoIPproperties.jpg

Before configuring the CallManager system, there is some information that needs to be obtained. First, note the MAC address of the VoIP-2 card. To do this, first connect to the configured Audia® system using the Audia software. Then, double-click on the VoIP Console block and click on the “Advanced” button. Navigate to the Status page to find the MAC Address of the VoIP-2 card. Note that the MAC Address will only appear here if you are connected live to the Audia system.

 

Cisco changed license policy from version 9.0 onwards, so the below is not relevant for newer versions. But older versions required that  the CallManager system has enough licenses available to handle a VoIP-2. From CallManager’s perspective, the VoIP-2 card appears as a third party SIP endpoint. Cisco required that a sufficient quantity of licenses be purchased from them before a third party SIP endpoint can be integrated into the CallManager system. To confirm this, log in to the CallManager system, and go to System—>Licensing—>License User Report. If you plan to use the VoIP-2 card for a single extension, you will need 3 available licenses. If you plan to use the VoIP-2 card for two separate extensions, you will need 6 available licenses.

Cisco configuration

First, we'll focus on setting up the Cisco CallManager server.

Security Profile

The first step to setting up the CallManager system is to create a Security Profile. If your CallManager system already has an existing Security Profile that you'd like to use, you may be able to skip this step, although you should confirm that the existing Security Profile has the settings described below. Follow the steps below to create a Security Profile:

cisco-audia-securityprofile.jpg

  1. Go to System—>Security Profile—>Phone Security Profile.
  2. Click the "Add New" button.
  3. Select the Phone Security Profile Type
    1. If you plan to use the VoIP-2 card for a single extension, choose Third-party SIP Device (Basic).
    2. If you plan to use the VoIP-2 card for two separate extensions, choose Third-party SIP Device (Advanced).
  4. Click the "Next" button.
  5. Enter a name and a description for the new Security Profile.
  6. Leave the Nonce Validity Time at its default value of 600.
  7. Set the Transport Type to UDP.
  8. Click the checkbox to Enable Digest Authentication.
  9. Leave the SIP Phone Port at its default value of 5060 unless your particular situation requires SIP traffic to be transmitted on a different port. If this is the case, you'll need to specify this port in the VoIP-2 card as well.
  10. Click the "Save" button.

Add a new user

Once a suitable Security Profile has been created, a new user must be created. Follow the steps below to create a new user:cisco-audia-newuser.jpg

  1. Go to User Management—>End User.
  2. Click the "Add New" button.
  3. Enter a user ID. Take note of this username, as it will be used later as the "Proxy Username" in the VoIP-2 card.
  4. The password and PIN number are not required.
  5. Enter a Last Name (this name is for internal descriptive purposes only).
  6. Enter a password in Digest Credentials. Take note of this password, as it will be used later as the “Proxy Password” in the VoIP-2 card.
  7. Enter the same password in “Confirm Digest Credentials”.
  8. The remaining fields on this page can be left either blank or at their default values. Click the “Save” button.

Add a new device

Once a new user has been created, a new device must be created. This device will link to the Security Profile and the user created in earlier steps. Follow the steps below to create a new device:

Steps 3-8 cisco-audia-newdevice.jpg
Steps 9-13 cisco-audia-newdevice2.jpg
Step 15 cisco-audia-associationinfo.jpg
Steps 16-18

cisco-audia-directorynumber.jpg

  1. Go to Device—>Phone.
  2. Click the “Add New” button.
  3. Select the Phone Type.
    1. If you plan to use the VoIP-2 card for a single extension, choose Third-party SIP Device (Basic).
    2. If you plan to use the VoIP-2 card for two separate extensions, choose Third-party SIP Device (Advanced). Note that the Third-party SIP Device (Advanced) setting allows up to 8 lines, but the VoIP-2 card uses a maximum of 2 lines. This results in a "partially registered" message from Call Manager. This is normal and not a cause for concern.
  4. Click the "Next" button.
  5. Input the MAC Address of the VoIP-2 card. Note that the colons should not be included in the MAC Address.
  6. The Description field will auto-populate once the MAC Address has been entered.
  7. Select the desired Device Pool in which this device should be included. Ensure that the codec used by this device pool is supported by the VoIP-2 card (the VoIP-2 card supports the following codecs: G.722, G.711μ, G.711A, G.729AB, and G.723.1).
  8. The remaining fields under the “Device Information” heading can be left at their default values.
  9. For the Device Security Profile, choose the Security Profile created earlier.
  10. For SIP Profile, choose Standard SIP Profile.
  11. For the Digest User, select the User created earlier.
  12. The remaining fields under the “Protocol Specific Information” and “MLPP Information” headings can be left at their default values.
  13. Click the “Save” button.
  14. Once your information is saved, you will be brought back to the configuration page for the device you just created. The only difference will be that there is an new “Association Information” section in the top left corner. If you’re in Basic (single extension) mode, you should see one line here. If you’re in Advanced (two extensions) mode, you should see up to 8 lines here.
  15. Click on “Line [1] - Add a new DN”.
  16. Enter the directory number for this extension. Take note of this number, as it will be used as the “Subscriber Number” in the VoIP-2 card settings.
  17. The remaining fields on this page can be left at their default values.
  18. Click the “Save” button.
  19. If you’re setting up a 2-line configuration, click on the “Line [2] - Add a new DN” and repeat steps 16-18 above. Otherwise, the CallManager setup is complete.

Audia configuration

Next, we'll focus on setting up the AudiaFlex configuration to match the settings that were used in CallManager.

VoIP Console

Biamp VoIP-2   Cisco Call Manager
Subscriber Number = Directory Number
Proxy Username = User ID
Proxy Password = Digest Credentials
  1. Open the Audia software, and open the .dap file for your project. Do not connect to the Audia system yet, because the information below cannot be entered while you are connected to the Audia system.
  2. Double-click on the VoIP Console block and click on the “Advanced” button. In the Advanced Settings window, select the Network page.
    1. cisco-audia-voipconsole-network.jpg
  3. If the VoIP-2 card is connected via a tagged VLAN, then click the “Enable VLAN” check box and enter the VLAN ID.  If the VoIP-2 card is on an untagged VLAN (or no VLAN), leave the "Enable VLAN" check box unchecked.
  4. If the VoIP-2 card is intended to obtain its networking information via DHCP, click on the “Use DHCP” check box. Otherwise, manually enter the networking information into the fields below. If you’re not sure what information to enter for steps 3 and 4, contact the IT administrator who manages the VoIP network.
  5. Select the Protocol page.
    1. cisco-audia-voipconsole-protocol-equals.jpg
  6. Enter the Subscriber number (the same number entered under “Add a New Device”, step 16).
  7. Enter the Proxy Username and Password (the same information entered under “Add a New User”, steps 3 and 6).
  8. For Proxy Address, enter the IP address of the Cisco CallManager server. If the VoIP port is different than the standard port of 5060, enter it under Proxy Port.  If you have separate Subscriber and Publisher servers, enter the IP address of the server that will act as the active registrar for endpoint devices.  It is also worth stating that at this time Audia devices do not support Cisco server redundancy and will only register to a single server.  If a failover occurs the Audia VoIP device will continuously register to the primary Cisco unit and will and the connection will heal upon this devices return.
  9. If your system has a separate proxy server for outbound traffic, enter its IP address under “Outbound Proxy Address”. Otherwise, leave it blank.

Steps 10-11 only apply if your VoIP network prioritizes traffic using Quality of Service (QoS). If your VoIP network doesn’t use QoS, skip to step 12.

  1. Select the QoS page.
    1. cisco-audia-voipconsole-qos.jpg
  2. Enter the appropriate L2 (Layer 2) and/or L3 (Layer 3) QoS parameters for your network.

Note: The VoIP-2 card defines QoS parameters based on the ToS (Type of Services) code. If your network defines QoS parameters based on the DiffServ code, please refer to this conversion table to convert DiffServ to ToS.

  1. Close the VoIP Advanced Settings window, and send the system configuration to the Audia    (File—>Network—>Send System Configuration). Once the file is loaded, the VoIP card will attempt to register with the proxy server. Various status messages will appear in the top left of the VoIP Console window (above the dial pad) to let you know where the VoIP card is in the registration process. If a status message is displayed in the VoIP console, this indicates there is a problem with the registration process. See VoIP-2 status messages for a description of the possible status messages and their meanings.

Further reading

  • If you've followed these steps and the VoIP card isn't registering, check to see if a VoIP-2 status message is indicating a problem.
  • If you need to input Quality of Service (QoS) settings, but only have those settings in a DiffServ format, see the DiffServ to ToS conversion table.
  • Was this article helpful?