Feedback
|
Table Of Contents
Configuring the Voice Interface
Auto-Configuration on the Cisco VG202, Cisco VG202XM, Cisco VG204, and Cisco VG204XM Voice Gateways
Restriction for Configuring Auto-Configuration
Auto-Configuration With a DHCP Server
Auto-Configuration Without a DHCP Server
Configuring the Voice Interface for Cisco Unified Communications Manager
Configuring the MAC Address Convention
Configuring Voice
This chapter explains how to configure voice interfaces and ports, which convert telephone voice signals for transmission over an IP network.
This chapter presents the following major topics:
•
Configuring the Voice Interface
VoIP enables your Cisco VG202, Cisco VG202XM, Cisco VG204, and Cisco VG204XM voice gateways to carry live voice traffic (for example, telephone calls and faxes) over an IP network. VoIP offers the following benefits:
•
Toll bypass
•
Unified voice and data trunking
•
Plain old telephone service (POTS)-Internet telephony gateways
For more information on understanding and configuring VoIP, see Configuring Voice over IP.
Prerequisites
Before you can configure your Cisco voice gateway to use VoIP, you must first do the following:
•
Establish a working IP network.
•
Implement a dial plan, including the following tasks:
–
Complete your company's dial plan. That is, decide what patterns of dialed numbers will access what telephony endpoints.
–
Establish a working telephony network based on your company's dial plan.
–
Integrate your dial plan and telephony network into your existing IP network topology.
Configuring the Voice Interface
Whenever you install a new interface or want to change the configuration of an existing interface, you must configure the interface.
Note
The Cisco VG202, Cisco VG202XM, Cisco VG204, and Cisco VG204XM voice gateways are fixed voice gateways and do not support interface cards.
Before you configure an interface, have the following information available:
•
Protocols you plan to route on the new interface
•
IP addresses, subnet masks, network numbers, zones, or other information related to the routing protocol
Timesaver
Obtain this information from your system administrator or network plan before you begin configuring your voice gateway.
To configure a voice interface, you must use configuration mode (manual configuration). In this mode, you can enter Cisco IOS commands through the CLI.
Procedure
Step 1
Connect a console to the voice gateway as described in the Cisco VG202, Cisco VG202XM, Cisco VG204, and Cisco VG204XM Voice Gateways Hardware Installation Guide.
Step 2
Power on the voice gateway. If the current configuration is no longer valid, after about one minute you see the following prompt:
Would you like to enter the initial dialog? [yes/no]:Answer no. You now enter the normal operating mode of the voice gateway.
Note
If the current configuration is valid, you enter the normal operating mode automatically.
Step 3
After a few seconds, you see the user EXEC prompt (VG>). Type enable and the password to enter enable mode:
VG> enablePassword: <password>The prompt changes to the privileged EXEC (enable) prompt (VG#):
VG#Step 4
Enter the configure terminal command to enter configuration mode:
VG# configure terminalVG(config)#The voice gateway enters global configuration mode, indicated by the VG(config)# prompt.
Step 5
If you have not configured the voice gateway before, or you want to change the configuration, use Cisco IOS commands to configure global parameters, passwords, network management, and routing protocols. In this example, IP routing is enabled:
VG(config)# ip routingFor complete information about global configuration commands, see the Cisco IOS configuration guides and command references.
Step 6
To configure another interface, enter the exit command to return to the VG(config)# prompt.
Step 7
To configure the voice gateway for voice traffic, see the VoIP references in the "Prerequisites" section.
Step 8
To exit configuration mode and return to the enable prompt, when you finish configuring interfaces, press Ctrl-Z. To see the current operating configuration, including any changes you just made, enter the show running-config command:
VG# show running-configTo see the configuration currently stored in NVRAM, enter the show startup-config command at the enable prompt:
VG# show startup-configStep 9
The results of the show running-config and show startup-config commands differ if you have made changes to the configuration but have not yet written them to NVRAM. To write your changes to NVRAM and make them permanent, enter the copy running-config startup-config command at the enable prompt:
VG# copy running-config startup-configBuilding configuration. . .[OK]VG#The Cisco voice gateway is now configured to boot in the new configuration.
Auto-Configuration on the Cisco VG202, Cisco VG202XM, Cisco VG204, and Cisco VG204XM Voice Gateways
To configure auto-configuration on the Cisco VG202, Cisco VG202XM, Cisco VG204, and Cisco VG204XM voice gateways, follow these guidelines and procedures.
•
Restriction for Configuring Auto-Configuration
•
Auto-Configuration on the Cisco VG202, Cisco VG202XM, Cisco VG204, and Cisco VG204XM Voice Gateways
•
Configuring the Voice Interface for Cisco Unified Communications Manager
•
Configuring the MAC Address Convention
Restriction for Configuring Auto-Configuration
Before you can connect the voice gateway to the network, you must provision the Cisco Unified Communications Manager (CUCM) with the voice gateway information.
Auto-Configuration With a DHCP Server
When the Dynamic Host Configuration Protocol (DHCP) server is available, the voice gateway sends a DHCP server request to provide the IP address for the Fast Ethernet 0/0 interface, and the TFTP server's IP address using the DHCP option 150. When the DHCP server provides the information, the voice gateway provisions itself with the CUCM configuration using Skinny Call Control Protocol (SCCP). Analog ports which have been pre-configured on CUCM automatically register on CUCM as SCCP-controlled ports.
To provision the voice gateway with auto-configuration when a DHCP server is available, use the following commands.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface type slot/port
4.
ip address dhcp
5.
sccp local interface-type interface-number port port-number
6.
ccm-manager sccp local interface-type interface-number
7.
ccm-manager sccp
8.
voice service voip
9.
fax protocol t38 [nse[force]]
10.
exit
DETAILED STEPS
Auto-Configuration Without a DHCP Server
When the DHCP server is not available, use the following commands to provision the voice gateway with the CUCM configuration.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface type slot/port
4.
ip address static ip subnet mask
5.
sccp local interface-type interface-number port port-number
6.
voice service voip
7.
fax protocol t38 [nse[force]]
8.
ccm-manager sccp local interface-type interface-number
9.
ccm-manager config server tftp_ip_address
10.
ccm-manager sccp
11.
exit
DETAILED STEPS
Configuring the Voice Interface for Cisco Unified Communications Manager
To configure voice ports to a CUCM server and set various parameters, including IP address, port number, and version number, use the following commands.
Note
The following steps are required only when the voice interface is configured manually and not through auto-configuration.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
stcapp ccm-group group-id
4.
stcapp
5.
stcapp feature access-code
6.
stcapp feature speed-dial
7.
voice-port slot-number/port
8.
timeouts initial seconds
9.
timeouts interdigit seconds
10.
timeouts ringing seconds infinity
11.
voice-port slot-number/port
12.
ccm-manager fax protocol [protocol cisco]
13.
ccm-manager config [server] ip-address name seconds
14.
ccm-manager sccp local interface-type interface-number
15.
ccm-manager sccp
16.
sccp local interface-type interface-number port port-type
17.
sccp
18.
sccp ccm group group-number
19.
associate ccm identifier-number priority priority-number
20.
dial-peer voice tags pots
21.
service stcapp
22.
port port-number
23.
exit
DETAILED STEPS
Configuring the MAC Address Convention
The voice gateways use the MAC address of the SCC local interface to define unique MAC addresses for each voice port by using the last 9 digits of the SCCP local interface of the voice gateway.
For example, if the source interface MAC address is 000C.8639.5833, the MAC address of the voice port MAC address will be C863.9583.3XXX. In the preceding example, the last 9 digits of the SCCP of the local voice gateway become the first 9 digits of the voice port MAC address after dropping the leading 000.
The last 3 digits of the voice port MAC address is the slot number (3-bit) + subunit number (2-bit) + port number (7-bit) in hexadecimal format. You combine the digits to get the last three MAC address digits.
For example, the voice-port 0/0 is slot number 0 (000): subunit 0 (00) and port number 0 (0000000). By stringing the digits together, you get the following: 0000 0000 0000 = 0 0 0. This means that if the source interface MAC address is 001f.cac3.b3f8, the MAC address of voice port 0/0 will be 1FCAC3b3f8000.
Table 4-1 shows the voice port to MAC address conversion table.
Table 4-1 Voice Port to MAC Address Conversion Chart
Port Number Last Three Digits of the MAC Address0/0
000
0/1
001
0/2
002
0/3
003
Configuring Calls
Call Transfer
The voice gateways blind-call transfer functionality allows the transfer of a call from the party you call to a destination caller without and call commit from the original person called. For example, party A (transferee) calls party B (transferor). The transferor wants to transfer the call to party C (transfer-target) and uses hookflash (softkey transfer) to get a dial tone, and then dials party C's number. When CUCM/CUCME gets party C's number, it transfers the party A call to party C without the need of committment from party B.
The voice gateways consultation call transfer functionality allows happens after a call is established between a transferor and transferee. The transferor wants to transfer the call to a transfer target by using a softkey transfer by getting a dialtone then dialing the transfer-target's phone number. When the call between the transferor and transfer-target is established, the transferor hangs up the phone to commit the transfer. The CUCM/CUCME connects the call between the transferee and the transfer-target.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
dial-peer voice tags pots
4.
service stcapp
5.
port port-number
6.
exit
DETAILED STEPS
Call Waiting
If a calling party places a call to another party and the other party is engaged in a call, and the called party has call waiting, the party receiving the call can suspend the current telephone call and switch to the incoming call. For example, when caller A is engaged in a call with Caller B, a second call coming in to caller A from caller C will cause caller A to hear the call-waiting tone (one tone with 300ms duration), which indicates a second call. Caller A should be able to use the softkey transfer button to answer the waiting call and then use softkey transfer to switch between the two calls.
To configure call waiting on the voice gateways, use the same commands and configuration shown in "Call Transfer" section.
Three-Party Conferencing
Three-party conferencing provides a three-way conversation between three call parties. The voice gateways along with CUCM support three-party conferencing using Cisco IOS software to perform G.711 (ITU-T standard for audio companding) software mixing for up to three Real-time Transport Protocol (RTP) streams
To configure three-party conferencing on the voice gateways, use the same commands and configuration shown in the "Call Transfer" section.
Caller ID
Caller ID transmits a caller's number to the called party's telephone during the ringing signal.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
voice-port slot-number/port
4.
caller-id enable [type [1|2]]
5.
voice-port slot-number/port
6.
caller-id enable [type [1|2]]
7.
exit
DETAILED STEPS
Feedback
