show voice port - Tecnológico de Costa Rica
show voice port - Tecnológico de Costa Rica show voice port - Tecnológico de Costa Rica
Configure Dial Peers Create a Peer Configuration Table Configure POTS Peers 2-18 There is specific data relative to each dial peer that needs to be identified before you can configure dial peers in Voice over IP. One way to do this is to create a peer configuration table. Using the example in Figure 2-2, Router 1, with an IP address of 10.1.1.1, connects a small sales branch office to the main office through Router 2. There are three telephones in the sales branch office that need to be established as dial peers. Access Server 2, with an IP address of 10.1.1.2, is the primary gateway to the main office; as such, it needs to be connected to the company’s PBX. There are four devices that need to be established as dial peers in the main office, all of which are basic telephones connected to the PBX. Figure 2-2 shows a diagram of this small voice network. Table 2-2 shows the peer configuration table for the example illustrated in Figure 2-2. Table 2-2 Peer Configuration Table for Sample Voice Over IP Network Commands Dial Peer Tag Access Server 1 Ext Dest-Pattern Type Voice Port Session-Target CODEC QoS 1 6.... +1408526.... POTS 10 Access Server 2 +1729422.... VoIP IPV4 10.1.1.2 G.729 Best Effort 11 +1408526.... VoIP IPV4 10.1.1.1 G.729 Best Effort 4 2.... +1729422.... POTS Once again, POTS peers enable incoming calls to be received by a particular telephony device. To configure a POTS peer, you need to uniquely identify the peer (by assigning it a unique tag number), define its telephone number(s), and associate it with a voice port through which calls will be established. Under most circumstances, the default values for the remaining dial-peer configuration commands will be sufficient to establish connections. To enter the dial-peer configuration mode (and select POTS as the method of voice-related encapsulation), use the following command in global configuration mode: Command Purpose dial-peer voice number pots Enter the dial-peer configuration mode to configure a POTS peer. The number value of the dial-peer voice pots command is a tag that uniquely identifies the dial peer. (This number has local significance only.) Voice over IP for the Cisco 3600 Series Software Configuration Guide
Configure POTS Peers To configure the identified POTS peer, use the following commands in dial-peer configuration mode: Step Command Purpose 1 destination-pattern string Define the telephone number associated with this POTS dial peer. 2 port controller number:D Associate this POTS dial peer with a specific logical dial interface. Outbound Dialing on POTS Peers When a router receives a voice call, it selects an outbound dial peer by comparing the called number (the full E.164 telephone number) in the call information with the number configured as the destination pattern for the POTS peer. The router then strips out the left-justified numbers corresponding to the destination pattern matching the called number. If you have configured a prefix, the prefix will be put in front of the remaining numbers, creating a dial string, which the router will then dial. If all numbers in the destination pattern are stripped-out, the user will receive (depending on the attached equipment) a dial tone. For example, suppose there is a voice call whose E.164 called number is 1(310) 767-2222. If you configure a destination-pattern of “1310767” and a prefix of “9,” the router will strip out “1310767” from the E.164 telephone number, leaving the extension number of “2222.” It will then append the prefix, “9,” to the front of the remaining numbers, so that the actual numbers dialed is “9, 2222.” The comma in this example means that the router will pause for one second between dialing the “9” and the “2” to allow for a secondary dial tone. For additional POTS dial-peer configuration options, refer to the “Voice over IP Commands for the Cisco 3600 Series” section. Direct Inward Dial for POTS Peers Direct inward dial (DID) is used to determine how the called number is treated for incoming POTS call legs. As shown in Figure 2-7, incoming means from the perspective of the router. In this case, it is the call leg coming into the access server to be forwarded through to the appropriate destination pattern. Figure 2-7 Incoming and Outgoing POTS Call Legs PBX Incoming call leg AS5300 IP cloud Outgoing call leg AS5300 PBX Unless otherwise configured, when a call arrives on the access server, the server presents a dial tone to the caller and collects digits until it can identify the destination dial peer. After the dial peer has been identified, the call is forwarded through the next call leg to the destination. There are cases where it might be necessary for the server to use the called-number (DNIS) to find a dial peer for the outgoing call leg—for example, if the switch connecting the call to the server has already collected the digits. DID enables the server to match the called-number with a dial peer and then directly place the outbound call. With DID, the server does not present a dial tone to the caller and does not collect digits; it forwards the call directly to the configured destination. 10369 Configuring Voice over IP for the Cisco 3600 Series 2-19
- Page 121 and 122: Anexo 2: Configuración de VoIP en
- Page 123 and 124: 2 Voice over IP Quick Start Guide
- Page 125 and 126: Installing Voice Network Modules an
- Page 127 and 128: Installing Voice Network Modules an
- Page 129 and 130: Voice Port Numbering Voice Port Num
- Page 131 and 132: Entering Configuration Mode Enterin
- Page 133 and 134: Configuring the IP Network for Real
- Page 135 and 136: Configuring the IP Network for Real
- Page 137 and 138: Configuring FXS Interfaces Configur
- Page 139 and 140: Configuring FXS Interfaces 18 Voice
- Page 141 and 142: Configuring FXS Interfaces Wild Car
- Page 143 and 144: Configuring FXS Interfaces 22 Voice
- Page 145 and 146: Configuring FXO Interfaces Configur
- Page 147 and 148: Configuring E&M Interfaces Configur
- Page 149 and 150: Configuring E&M Interfaces 28 Voice
- Page 151 and 152: List of Terms List of Terms This se
- Page 153 and 154: Cisco Connection Online Cisco Conne
- Page 155 and 156: CHAPTER Configuring Voice over IP f
- Page 157 and 158: Prerequisites Tasks Prerequisites T
- Page 159 and 160: Configuration Tasks To configure Vo
- Page 161 and 162: Configure RSVP for Voice Enable RSV
- Page 163 and 164: You should configure Multilink PPP
- Page 165 and 166: Enable RTP Header Compression on a
- Page 167 and 168: Frame Relay for Voice over IP Confi
- Page 169 and 170: Table 2-1 Sample Number Expansion T
- Page 171: Figure 2-5 Outgoing Calls from the
- Page 175 and 176: Configure VoIP Peers Verify Tips Co
- Page 177 and 178: • Call progress tone using the cp
- Page 179 and 180: Fine-Tune FXO and FXS Voice Ports T
- Page 181 and 182: Validation Tips Step Command Purpos
- Page 183 and 184: Step Command Purpose Fine-Tune E&M
- Page 185 and 186: Configure CODEC and VAD for Dial Pe
- Page 187 and 188: Step 8 Click the Up button until th
- Page 189 and 190: Limit TCP Transactions Limit TCP Tr
- Page 191 and 192: Establish Queueing and Congestion S
- Page 193 and 194: Establish Queueing and Congestion S
- Page 195 and 196: Establish Queueing and Congestion S
- Page 197 and 198: Modify the System Buffer Size To di
- Page 199 and 200: Performance Management Examples The
- Page 201 and 202: 4-2 • output attenuation • port
- Page 203 and 204: Command Syntax Conventions Command
- Page 205 and 206: acc-qos 4-6 Example The following e
- Page 207 and 208: answer-address 4-8 Example The foll
- Page 209 and 210: comfort-noise comfort-noise 4-10 To
- Page 211 and 212: cptone cptone 4-12 To configure a v
- Page 213 and 214: description description To include
- Page 215 and 216: destination-pattern 4-16 Related Co
- Page 217 and 218: dial-peer voice dial-peer voice 4-1
- Page 219 and 220: echo-cancel coverage echo-cancel co
- Page 221 and 222: echo-cancel enable echo-cancel enab
Configure POTS Peers<br />
To configure the i<strong>de</strong>ntified POTS peer, use the following commands in dial-peer configuration mo<strong>de</strong>:<br />
Step Command Purpose<br />
1 <strong>de</strong>stination-pattern string Define the telephone number associated with this POTS<br />
dial peer.<br />
2 <strong>port</strong> controller number:D Associate this POTS dial peer with a specific logical dial<br />
interface.<br />
Outbound Dialing on POTS Peers<br />
When a router receives a <strong>voice</strong> call, it selects an outbound dial peer by comparing the called number<br />
(the full E.164 telephone number) in the call information with the number configured as the<br />
<strong>de</strong>stination pattern for the POTS peer. The router then strips out the left-justified numbers<br />
corresponding to the <strong>de</strong>stination pattern matching the called number. If you have configured a prefix,<br />
the prefix will be put in front of the remaining numbers, creating a dial string, which the router will<br />
then dial. If all numbers in the <strong>de</strong>stination pattern are stripped-out, the user will receive (<strong>de</strong>pending<br />
on the attached equipment) a dial tone.<br />
For example, suppose there is a <strong>voice</strong> call whose E.164 called number is 1(310) 767-2222. If you<br />
configure a <strong>de</strong>stination-pattern of “1310767” and a prefix of “9,” the router will strip out “1310767”<br />
from the E.164 telephone number, leaving the extension number of “2222.” It will then append the<br />
prefix, “9,” to the front of the remaining numbers, so that the actual numbers dialed is “9, 2222.” The<br />
comma in this example means that the router will pause for one second between dialing the “9” and<br />
the “2” to allow for a secondary dial tone.<br />
For additional POTS dial-peer configuration options, refer to the “Voice over IP Commands for the<br />
Cisco 3600 Series” section.<br />
Direct Inward Dial for POTS Peers<br />
Direct inward dial (DID) is used to <strong>de</strong>termine how the called number is treated for incoming POTS<br />
call legs. As <strong>show</strong>n in Figure 2-7, incoming means from the perspective of the router. In this case, it<br />
is the call leg coming into the access server to be forwar<strong>de</strong>d through to the appropriate <strong>de</strong>stination<br />
pattern.<br />
Figure 2-7 Incoming and Outgoing POTS Call Legs<br />
PBX<br />
Incoming<br />
call leg<br />
AS5300<br />
IP<br />
cloud<br />
Outgoing<br />
call leg<br />
AS5300 PBX<br />
Unless otherwise configured, when a call arrives on the access server, the server presents a dial tone<br />
to the caller and collects digits until it can i<strong>de</strong>ntify the <strong>de</strong>stination dial peer. After the dial peer has<br />
been i<strong>de</strong>ntified, the call is forwar<strong>de</strong>d through the next call leg to the <strong>de</strong>stination.<br />
There are cases where it might be necessary for the server to use the called-number (DNIS) to find<br />
a dial peer for the outgoing call leg—for example, if the switch connecting the call to the server has<br />
already collected the digits. DID enables the server to match the called-number with a dial peer and<br />
then directly place the outbound call. With DID, the server does not present a dial tone to the caller<br />
and does not collect digits; it forwards the call directly to the configured <strong>de</strong>stination.<br />
10369<br />
Configuring Voice over IP for the Cisco 3600 Series 2-19