Table Of Contents
Private Line Automatic Ringdown for Trading Turrets
Restrictions for Private Line Automatic Ringdown for Trading Turrets
Configuration of Both Endpoints
Information About Private Line Automatic Ringdown for Trading Turrets
Private-Line Automatic Ringdown
Connection Modes: PLAR vs Trunk
How to Configure Private Line Automatic Ringdown for Trading Turrets
Configuring Private Line Automatic Ringdown for Trading Turrets
Configuration Examples for Private Line Automatic Ringdown for Trading Turrets
T1 E&M to T1 E&M PLAR Connection: Example
Analog FXS to Analog FXS PLAR Connection: Example
T1 E&M to Analog FXS PLAR Connection: Example
Private Line Automatic Ringdown for Trading Turrets
The Private Line Automatic Ringdown for Trading Turrets feature improves connection service for turrets in the financial industry—primarily for corporations and enterprises that use turrets and POTS telephones for trading. Implementation of this feature ensures that a call between traders on a private line automatic ringdown (PLAR) connection will be maintained if one of the traders goes on-hook or on-hold. This new capability also ensures that bandwidth is used only when needed.
Feature History for Private LIne Automatic Ringdown for Trading Turrets
Feature History Release Modification12.2(15)ZJ
This feature was introduced.
12.3(4)T
This feature was integrated into Cisco IOS Release 12.3(4)T.
Finding Support Information for Platforms and Cisco IOS Software Images
Use Cisco Feature Navigator to find information about platform support and Cisco IOS software image support. Access Cisco Feature Navigator at http://www.cisco.com/go/fn. You must have an account on Cisco.com. If you do not have an account or have forgotten your username or password, click Cancel at the login dialog box and follow the instructions that appear.
Contents
•Restrictions for Private Line Automatic Ringdown for Trading Turrets
•Information About Private Line Automatic Ringdown for Trading Turrets
•How to Configure Private Line Automatic Ringdown for Trading Turrets
•Configuration Examples for Private Line Automatic Ringdown for Trading Turrets
Restrictions for Private Line Automatic Ringdown for Trading Turrets
The following restrictions apply to the Private Line Automatic Ringdown for Trading Turrets:
•Configuration of Both Endpoints
Minimum Cisco IOS Release
Before you can run the Private Line Automatic Ringdown for Trading Turrets feature, you must install an IP Plus image (minimum) of Cisco IOS Release 12.2(15)ZJ or a later release.
Configuration Information
This feature is supported only for FXS loop-start ports and digital ear & mouth (E&M) immediate-start ports. When a voice port is configured with an incorrect destination number that may or may not be a valid number, the call may not perform as expected. There is no cross-checking for turret PLAR from the origination voice port, but there is a check on the terminating voice port to prevent accepting a call from a calling party that is not preconfigured.
Configuration of Both Endpoints
To work properly, this feature must be configured at both endpoints in the connection (either FXS loopstart port or digital E&M immediate-start port).
Information About Private Line Automatic Ringdown for Trading Turrets
To use this feature, you should understand the following concepts:
•Private-Line Automatic Ringdown
•Connection Modes: PLAR vs Trunk
Private-Line Automatic Ringdown
Private-line automatic ringdown (PLAR) circuits have statically configured endpoints and do not require 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 useful where a telephone (or DS0) goes off-hook and a remote telephone rings (or remote DS0 goes off-hook) without digits being dialed. This feature is useful for:
•Providing an Off-Premises eXtension (OPX) from a private branch exchange (PBX). Connection PLAR would allow Foreign Exchange Station (FXS) ports to look to a central PBX like physical extensions.
•Providing dial-tone from a remote PBX. This provides toll-bypass VoIP services without having the routers providing dial-tone or changing the existing dialplan. Stations at remote sites look like they are physically connected stations to a PBX.
Connection Modes: PLAR vs Trunk
The following are the main similarities and differences between connection PLAR mode and connection trunk mode:
•Connection trunk mode is a permanent connection, the VoIP call is always connected independent 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 set up 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 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 means to invoke supplemental services.
How to Configure Private Line Automatic Ringdown for Trading Turrets
This section describes the following tasks used to configure the Private Line Automatic Ringdown for Trading Turrets feature:
•Configuring Private Line Automatic Ringdown for Trading Turrets
Configuring Private Line Automatic Ringdown for Trading Turrets
Perform this task to enable the Private Line Automatic Ringdown for Trading Turrets.
SUMMARY STEPS
1. enable
2. configure terminal
3. controller t1 slot/port
4. framing {sf | esf}
5. clock source {line | internal}
6. linecode {ami | b8zs}
7. ds0-group ds0-group-number timeslots timeslot-list type {e&m-delay-dial | e&m-fgd | e&m-immediate-start | e&m-wink-start | ext-sig | fgd-eana | fgd-os | fxo-ground-start | fxo-loop-start | fxs-ground-start | fxs-loop-start | none}
8. voice-port slot/port:ds0-group-number
9. timeouts wait-release {seconds | infinity}
10. timing hookflash-input milliseconds
11. connection {{plar [tied] | tie-line | plar-opx} digits | trunk digits [answer-mode]}
12. exit
13. dial-peer voice tag {pots | vofr | voip}
14. destination-pattern [+] string [T]
15. session target ipv4: destination-ip-address
16. no vad
17. exit
DETAILED STEPS
Configuration Examples for Private Line Automatic Ringdown for Trading Turrets
This section provides samples for three types of configuration:
•T1 E&M to T1 E&M PLAR Connection: Example
•Analog FXS to Analog FXS PLAR Connection: Example
•T1 E&M to Analog FXS PLAR Connection: Example
T1 E&M to T1 E&M PLAR Connection: Example
This section provides a sample configuration for a PLAR connection between two T1 E&M voice ports. Note that this is a sample configuration only, provided for references purposes.
This sample configuration is for the first router (endpoint):
enableconfigure terminalcontroller t1 1/0framing esfclock source internallinecode b8zsds0-group 0 timeslots 1 type e&m-immediate-start!voice-port 1/0:0timeouts wait-release 3timing hookflash-in 150connection plar tied 2000!dial-peer voice 1000 potsdestination-pattern 1000port 1/0:0!dial-peer voice 2000 voipdestination-pattern 200session target ipv4: 10.1.1.2This sample configuration is for the second router (endpoint):
enable
configure terminal
controller t1 2/0
framing esfclock source internallinecode b8zsds0-group 0 timeslots 1 type e&m-immediate-start!voice-port 2/0:0
timeouts wait-release 3
timing hookflash-in 150connection plar tied 1000
!dial-peer voice 2000 pots
destination-pattern 2000
port 2/0:0
!dial-peer voice 1000 voip
destination-pattern 100
session target ipv4: 10.1.1.1
no vad
Analog FXS to Analog FXS PLAR Connection: Example
This section describes a sample configuration for an analog FXS to analog FXS PLAR connection.
This sample configuration is for the first router (endpoint):
enable
configure terminal
voice-port 1/0/0
timeouts wait-release 3
connection plar tied 1000
!dial-peer voice 2000 pots
destination-pattern 2000
port 1/0/0
!dial-peer voice 1000 voip
destination-pattern 100
session target ipv4: 10.1.1.1
no vad
This sample configuration is for the second router (endpoint):
enable
configure terminal
voice-port 1/0/0
timeouts wait-release 3
connection plar tied 2000
!dial-peer voice 1000 pots
destination-pattern 1000
port 1/0/0
dial-peer voice 2000 voip
destination-pattern 200
session target ipv4: 10.1.1.2
T1 E&M to Analog FXS PLAR Connection: Example
This section describes a sample configuration for a T1 E&M to analog FXS PLAR connection.
This sample configuration is for the first router (endpoint):
enable
configure terminal
voice-port 1/0/0
timeouts wait-release 3
connection plar tied 2000
!dial-peer voice 1000 pots
destination-pattern 1000
port 1/0/0
!dial-peer voice 2000 voip
destination-pattern 200
session target ipv4: 10.1.1.2
This sample configuration is for the second router (endpoint):
enable
configure terminal
controller t1 2/0
framing esfclock source internallinecode b8zsds0-group 0 timeslots 1 type e&m-immediate-start!voice-port 2/0:0
timeouts wait-release 3
timing hookflash-in 150connection plar tied 1000
!dial-peer voice 2000 pots
destination-pattern 2000
port 2/0:0
!dial-peer voice 1000 voip
destination-pattern 100
session target ipv4: 10.1.1.1
no vad
!Additional References
The following sections provide references related to the Private Line Automatic Ringdown for Trading Turrets feature.
Related Documents
Related Topic Document TitleGeneral information about Voice over IP
Cisco IOS Voice over IP Overview
Information about Cisco IOS commands
Cisco IOS Voice Command Reference
Standards
RFCs
MIBs
Technical Assistance
Command Reference
This section documents the modified connection command. All other commands used with this feature are documented in the Cisco IOS Release 12.3 T command reference publications.
connection
To specify a connection mode for a voice port, use the connection command in voice-port configuration mode. To disable the selected connection mode, use the no form of this command.
connection {{plar [tied] | tie-line | plar-opx} digits | trunk digits [answer-mode]}
no connection {{plar | tie-line | plar-opx} digits | trunk digits [answer-mode]}
Syntax Description
Defaults
No connection mode is specified.
Command Modes
Voice-port configuration
Command History
Usage Guidelines
Use the connection command to specify a connection mode for a specific interface. For example, use the connection plar command to specify a PLAR interface. The string you configure for this command is used as the called number for all incoming calls over this connection. The destination peer is determined by the called number.
Use the connection trunk command to specify a permanent tie-line connection to a PBX. VoIP simulates a trunk connection by creating virtual trunk tie lines between PBXs connected to Cisco devices on each side of a VoIP connection. In configuring virtual trunk connections in Voice over IP, the following restrictions apply:
•Use only the following voice port combinations:
–Ear and mouth (E&M) to E&M (same type)
–Foreign Exchange Station (FXS) to FXO
–FXS to FXS (with no signaling)
•Do not perform number expansion on the destination pattern telephone numbers configured for trunk connection.
•Configure both end routers for trunk connections.
•Connect Cisco routers that are Cisco 2600 or Cisco 3600 series routers only.
To configure one of the devices in the trunk connection to act as slave and only receive calls, use the answer-mode keyword with the connection trunk command when configuring that device.
Note Because virtual trunk connections do not support number expansion, the destination patterns on each side of the trunk connection must match exactly.
Note When using the connection trunk command, you must enter the shutdown command followed by the no shutdown command on the voice port.
VoIP establishes the trunk connection immediately after it is configured. Both ports on either end of the connection are dedicated until you disable trunking for that connection. If for some reason the link between the two switching systems goes down, the virtual trunk reestablishes itself after the link comes back up.
Use the connection tie-line command when the dial plan requires that digits be added before any digits dialed by the PBX and that the combined set of digits be used to route the call onto the network. The operation is similar to the connection plar command operation, but in this case the tie-line port waits to collect digits from the PBX. The tie-line digits are automatically stripped by a terminating port.
If the connection command is not configured, the standard session application outputs a dial tone when the interface goes off-hook until enough digits are collected to match a dial peer and complete the call.
Examples
The following example shows PLAR selected as the connection mode on a Cisco 3600 series router, with a destination telephone number of 555-0100:
voice-port 1/0/0connection trunk 5550100The following example shows the tie-line selected as the connection mode on a Cisco MC3810, with a destination telephone number of 555-0100:
voice-port 1/1connection tie-line 5550100The following example specifies a PLAR OPX connection on a Cisco 3600 series router, with a destination telephone number of 555-0100:
voice-port 1/0/0connection plar-opx 5550100The following example shows configuration of a Cisco 3600 series router for a trunk connection and specifies that it will establish the trunk only when it receives an incoming call:
voice-port 1/0/0connection trunk 5550100 answer-mode
The following examples show configuration of the routers on both sides of a VoIP connection to support trunk connections:
Router A Configuration
voice-port 1/0/0connection trunk +15105550100dial-peer voice 10 potsdestination-pattern +13085550101port 1/0/0dial-peer voice 100 voipsession-target ipv4: 172.20.10.10destination-pattern +15105550100Router B Configuration
voice-port 1/0/0connection trunk +13085551000dial-peer voice 20 potsdestination-pattern +15105554001port 1/0/0dial-peer voice 200 voipsession-target ipv4: 172.19.10.10destination-pattern +13085550500Related Commands
Glossary
CAS—channel-associated signaling.
CSU—channel service unit.
DSP—digital signal processor.
DSU—data service unit.
E&M—ear and mouth. Connection to a PBX or key system trunk line.
E1—European equivalent of T1, 32 channels of 64 kHz each, 1 for framing, 1 for signaling.
ESF—Extended Superframe, 24 frames per ESF, includes additional signaling.
FAS—frame align signal.
FDL—facilities data link.
FXO—Foreign Exchange Office.
FXS—Foreign Exchange Station.
H.323—ITU-T standard that defines a set of call control, channel setup, and codec specifications for sending real-time voice and video over networks that do not offer guaranteed quality of service.
HDLC—High-Level Data Link Control protocol.
MIB—Management Information Base.
PLAR—private line automatic ringdown.
POTS—plain old telephone service.
PRI—Primary Rate Interface.
SF—superframe, or D4 framing, 12 frames per super frame for in-band signaling extraction.
T1—North American channelized TDM with 24 channels of 64 kHz each plus 8 kHz frame.
VAD—voice activity detection.
Note Refer to the Internetworking Terms and Acronyms for terms not included in this glossary.
Copyright © 2003 Cisco Systems, Inc. All rights reserved.