Cisco Configuring Connection Plar For Voip Gateways
Cisco Configuring Connection Plar For Voip Gateways
Cisco Configuring Connection Plar For Voip Gateways
Table of Contents
Configuring Connection PLAR for VoIP Gateways........................................................................................1
Introduction.............................................................................................................................................1
Before You Begin...................................................................................................................................1
Conventions...............................................................................................................................1
Prerequisites...............................................................................................................................1
Components Used......................................................................................................................1
Background Theory...................................................................................................................1
Connection Modes: PLAR Vs Trunk.........................................................................................2
Connection PLAR Mode Design Considerations and Limitations............................................3
Configure................................................................................................................................................3
Network Diagram......................................................................................................................3
Configurations...........................................................................................................................4
Verify......................................................................................................................................................5
Command Summary..................................................................................................................5
Debug and Show Commands.....................................................................................................6
Sample show Output..................................................................................................................6
Troubleshoot...........................................................................................................................................7
Related Information................................................................................................................................7
i
Configuring Connection PLAR for VoIP Gateways
Introduction
Before You Begin
Conventions
Prerequisites
Components Used
Background Theory
Connection Modes: PLAR Vs Trunk
Connection PLAR Mode Design Considerations and Limitations
Configure
Network Diagram
Configurations
Verify
Command Summary
Debug and Show Commands
Sample show Output
Troubleshoot
Related Information
Introduction
This document provides a sample configuration for connecting PLAR for VoIP gateways.
Prerequisites
There are no specific prerequisites for this document.
Components Used
This configuration was developed and tested using a Cisco 2610 router and a Cisco 3600 router running Cisco
IOS Release 12.1(1) with IP Plus feature set.
The information presented in this document was created from devices in a specific lab environment. All of the
devices used in this document started with a cleared (default) configuration. If you are working in a live
network, ensure that you understand the potential impact of any command before using it.
Background Theory
Private−line automatic ringdown (PLAR) circuits have statically configured endpoints and do not require user
dialing to connect calls. The connection plar command provides a mechanism to create a switched Voice
over IP (VoIP) call without digit dialing. PLAR connections are often referred to as a "bat−phone" type of
application, where a phone (or DS0) goes off−hook and a remote phone rings (or remote DS0 goes off−hook)
•
Providing an Off−Premises eXtension (OPX) from a private branch exchange (PBX). Connection
PLAR would allow remote users on Foreign Exchange Station (FXS) ports to look to a central PBX
like physical extensions.
•
Providing dial−tone from a remote PBX. Many customers want to offer toll−bypass VoIP services
without having the routers providing dial−tone or changing their existing dialplan. This would allow
stations at remote sites to look like they are physically connected stations to a PBX.
•
Cisco 2600 & 3600
•
Cisco 7200/7500
•
Cisco MC3810
•
Connection trunk mode is a permanent connection, the VoIP call is always connected independently
of the plain old telephone service (POTS) port being on−hook or off−hook.
•
Connection PLAR mode is a switched VoIP call, the call is setup on an as−needed basis. With
connection PLAR, no bandwidth is consumed while the phone is on hook. When a phone connected
to a POTS dial peer is taken off−hook, the call is automatically connected and the remote phone
begins to ring.
•
Both Connection Trunk and connection PLAR modes have statically configured endpoints and do not
require user dialing to connect calls.
•
Connection trunk mode allows supplemental call signaling such as hookflash or point−to−point
hoot−n−holler to be passed over the IP network between the two telephony devices.
Note: Connection PLAR can now support hookflash signaling by configuring hookflash relay.
A hookflash indication is a brief on−hook condition that occurs during a call. It is created by quickly pressing
and releasing the hook on your telephone. PBXs and telephone switches are frequently programmed to
intercept hookflash indications and use them as a way to allow a user to invoke supplemental services.
For more information on hoot−n−holler refer to: Cisco Hoot & Holler over IP Solution and Cisco Hoot and
Holler over IP
For more information on Connection Trunk refer to: Voice: Configuring Connection Trunk
•
A connection PLAR can work between any type of signaling (recEive and transMit (E®M;), Foreign
Exchange Office (FXO), and/or FXS), and between any combination of analog and digital interfaces.
•
A connection PLAR for VoIP supports PLAR−OPX (such as is used on the MC3810) after Cisco
IOS® Software Release 12.0(7)XK, 12.1(2)T or later. This feature is used to roll−over the call to
voice−mail if the remote phone does not answer.
•
A connection PLAR does not collect digits from the connected telephony device, so it can be
deployed without changes to the existing dialplan.
•
A connection PLAR can be configured for a single direction (calling in one direction), or in both
directions of the VoIP call legs.
•
A connection PLAR is defined per voice−port. This means that the voice−port can not operate both in
connection trunk mode and collect dialed−digits mode.
Configure
In this section, you are presented with the information to configure the features described in this document.
Note: To find additional information on the commands used in this document, use the Command Lookup
Tool ( registered customers only) .
Network Diagram
This document uses the network setup shown in the diagram below.
maui−slt−01 (2600)
version 12.1
service timestamps debug datetime msec
service timestamps log datetime msec
!
hostname maui−slt−01
!
voice−card 1
!
controller T1 1/0
framing esf
linecode b8zs
!
voice−port 1/0:1
connection plar 2000
! −− This command starts a PLAR switched VoIP call using digits (2000)
! −− to match a VoIP dial−peer when the voice−port 1/0:1 goes off−hook.
!
voice−port 1/0:2
connection plar 2001
!
dial−peer voice 1 pots
destination−pattern 1000
port 1/0:1
!
dial−peer voice 2 pots
destination−pattern 1001
port 1/0:2
!
dial−peer voice 3 voip
destination−pattern 200.
dtmf−relay h245−alphanumeric
session target ipv4:192.168.100.1
!
maui−vgw−01 (3600)
version 12.1
service timestamps debug datetime msec
service timestamps log datetime msec
!
hostname maui−vgw−01
!
voice−card 3
!
voice−port 1/1/0
!
voice−port 1/1/1
!
dial−peer voice 1 pots
destination−pattern 2000
port 1/1/0
!
dial−peer voice 3 pots
destination−pattern 2001
port 1/1/1
!
dial−peer voice 2 voip
destination−pattern 100. dtmf−relay h245−alphanumeric
session target ipv4:192.168.100.2
! −− When the router receives digits from a POTS peer that starts with
! −− 100 and is follow one more string characters (0−9, A−Z,*,# or .),
! −− it creates a VoIP call to the router with IP address: 192.168.100.2
!
interface Serial0/0
ip address 192.168.100.1 255.255.255.0
clockrate 256000
Verify
This section provides information you can use to confirm your configuration is working properly.
Command Summary
•
•
dtmf−relay [cisco−rtp] [h245−signal] [h245−alphanumeric] − Since the router will not interpret
digits from a telephony device, by default, all digits will be passed through the compressed VoIP
audio−path. Low−bitrate coder−decoders (CODECs) such as G.729 and G.723.1 are highly optimized
for voice patterns, and tend to distort dual tone multifrequency (DTMF) tones. The dtmf relay
command solves this problem by transporting DTMF tones out of band, or separate from the encoded
voice stream. For more information on dtmf−relay and its options refer to: H.323 Version 2 Support.
•
show voice port − This commands displays information about the voice port configuration. Use this
command to verify that the port is up, connection PLAR is enabled, and the connection PLAR string
is correct.
•
show call active voice − This command displays the contents of the active call table, which shows all
of the calls currently connected through the router.
•
debug voip ccapi inout − This command is useful to troubleshoot end−to−end VoIP calls.
For more information on troubleshooting VoIP calls refer to: Troubleshoot & Debug VoIP Calls − the Basics
and VoIP Debug Commands.
Troubleshoot
There is currently no specific troubleshooting information available for this configuration.
Related Information
• Troubleshoot & Debug VoIP Calls − the Basics
• VoIP Debug Commands
• Voice, Telephony and Messaging TAC eLearning Solutions
• Technical Support − Cisco Systems
All contents are Copyright © 1992−2002 Cisco Systems, Inc. All rights reserved. Important Notices and Privacy Statement.