AudiaFLEX Voice-over-IP Interface. Preliminary Steps. Configuring a Cisco CallManager system to work with Biamp s VoIP-2 card

Transcription

1 Configuring a Cisco CallManager system to work with Biamp s VoIP-2 card AudiaFLEX Voice-over-IP Interface Biamp s VoIP-2 card allows Biamp AudiaFLEX digital signal processors to make and receive calls over any 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. The steps below were written based on CallManager version , however the configuration of other versions of CallManager should be similar or identical. Preliminary Steps 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 (see Figure 1 below). Note that the MAC Address will only appear here if you are connected live to the Audia system. The second preliminary step is to verify that the CallManager system has enough licenses available. From CallManager s perspective, the VoIP-2 card appears as a third party SIP endpoint. Cisco requires 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. Figure 1 MS-1 VoIP Properties Screen 1 of 6

2 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: 1. Go to System >Security Profile >Phone Security Profile. 2. Click the "Add New" button. 3. Select the Phone Security Profile Type (see Figure 2) a. If you plan to use the VoIP-2 card for a single extension, choose Third-party SIP Device (Basic). b. 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 (see Figure 3). 6. Leave the Nonce Validity Time at its default value of 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. Figure 2 New Phone Security Profile screen Figure 3 Phone Security Profile Information screen 2 of 6

3 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: 1. Go to User Management >End User. 2. Click the "Add New" button. 3. Enter a user ID. This username will be used as the "Proxy Username" in the VoIP-2 card. (see Figure 4) 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. This password will be used 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. 9. Click the Save button. Figure 4 Add New User screen 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: 1. Go to Device >Phone. 2. Click the Add New button. 3. Select the Phone Type. a. If you plan to use the VoIP-2 card for a single extension, choose Third-party SIP Device (Basic). b. 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. Input the MAC Address of the VoIP-2 card. Note that the colons should not be included in the MAC Address. (see Figure 5) 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. Figure 5 Top section of Add New Device screen 3 of 6

4 9. For the Device Security Profile, choose the Security Profile created earlier. (see Figure 6) 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. (see Figure 7) 15. Click on Line [1] - Add a new DN. 16. Enter the directory number for this extension. This directory number will be used as the Subscriber Number in the VoIP-2 card settings. (see Figure 8) 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 above. Otherwise, the CallManager setup is complete. Figure 6 Bottom section of Add New Device screen Figure 7 Association Information section Figure 8 Configuring a new extension 4 of 6

5 Configure VoIP-2 Card Finally, after all CallManager settings have been entered, follow the steps below to set up the VoIP-2 card: 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. (see Figure 9) 3. If the VoIP-2 card is connected via a VLAN, then click the Enable VLAN check box and enter the VLAN ID. 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. (see Figure 10) 6. Enter the Subscriber number (the same number entered on page 4, Add a New Device, step 16). 7. Enter the Proxy Username and Password (the same information entered on page 3, 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. 9. If your system has a separate proxy server for outbound traffic, enter its IP address under Outbound Proxy Address. Otherwise, leave it blank. Figure 9 VoIP-2 Card Advanced Settings Network Page Figure 10 VoIP-2 Card Advanced Settings Protocol Page 5 of 6

6 Steps only apply if your VoIP network prioritizes traffic using Quality of Service (QoS). If your VoIP network doesn t use QoS, skip to step Select the QoS page. (see Figure 11) 11. 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 use the table in Figure 12 to convert to ToS. 12. 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 other than Idle is displayed, this indicates there is a problem with the registration process. See below for a description of the possible status messages and their meanings: Not Connected Audia software is not connected live to the Audia device. Network is Down A valid Ethernet connection has not been sensed on the VoIP-2 card s Ethernet port. Network is Up A valid Ethernet connection has been sensed on the VoIP-2 card s Ethernet port, however communication with the proxy server has not been established. DHCP In Progress The VoIP-2 card has been set to obtain an IP address via DHCP, and is currently requesting an address from the DHCP server. Local Address Not Configured Indicates a problem with the information provided on the Protocol page of the Advanced VoIP Settings. If the Subscriber Number, Proxy Username, or Proxy Password is left blank, this message will appear. Proxy Is Not Configured All attempts to locate and establish communication with a valid proxy server have been exhausted. Registering The VoIP-2 card has established contact with the proxy server and is currently trying to register. If this status message doesn t go away, then a problem has occurred within the proxy registration process (i.e. bad username or password). Idle VoIP-2 card has successfully registered and is ready to make a call. Figure 11 VoIP-2 Card Advanced Settings QoS Page DiffServ DiffServ L3 Precedence L3 RTP Min L3 RTP Max L3 Max PHB DSCP Delay Throughput Reliability Default 0 0 Off Off Off CS1 8 1 Off Off Off AF Off ON Off AF ON Off Off AF ON ON Off CS Off Off Off AF Off ON Off AF ON Off Off AF ON ON Off CS Off Off Off AF Off ON Off AF ON Off Off AF ON ON Off CS Off Off Off AF Off ON Off AF ON Off Off AF ON ON Off CS Off Off Off EF 46 5 ON ON Off CS Off Off Off CS Off Off Off Figure 12 DiffServ to ToS conversion table 6 of 6