Cisco Router 800 Series Software Configuration Guide

							CHAPTER
 
5-1
Cisco 800 Series Software Configuration Guide
78-5372-06
5
Configuring Remote CAPI
Overview of CAPI
The Common Application Programming Interface (CAPI) is an application 
programming interface standard used to access ISDN equipment connected to 
Basic Rate Interfaces (BRIs) and Primary Rate Interfaces (PRIs). Remote 
Common Application Programming Interface (RCAPI) is the CAPI feature 
configured remotely from a PC client. CAPI provides the following features:
A standardized interface through which application programs use ISDN 
drivers and controllers. One application can use one or more controllers. 
Several applications can share one or more controllers.
A selection mechanism that supports applications that use protocols at 
different levels and standardized network access. To provide this support, an 
abstraction from different protocol variables is performed by the software. 
All connection-related data, such as connection state and display messages, 
is available to the applications at any time.
The framing protocols supported by CAPI include High-Level Data Link Control 
(HDLC), HDLC inverted, bit transparent (speech), and V.110 
synchronous/asynchronous. CAPI integrates the following data link and network 
layer protocols: 
Link Access Procedure on the D-channel (LAPD), in accordance with Q.921 
for X.25 D-channel implementation
Point-to-Point Protocol (PPP)
ISO 8208 (X.25 DTE-DTE)
X.25 DCE, T.90NL, and T.30 (fax Group 3) 
						

							 
Chapter 5      Configuring Remote CAPI
CAPI Features
5-2
Cisco 800 Series Software Configuration Guide
78-5372-06
CAPI Features
CAPI supports the following features:
Basic call features, such as call setup and tear-down
Multiple B channels for data and voice connections
Multiple logical data link connections within a physical connection
Selection of different services and protocols during connection setup and on 
answering incoming calls
Transparent interface for protocols above Layer 3
One or more BRIs as well as PRI on one or more Integrated Services Digital 
Network (ISDN) adapters
Multiple applications
Operating-system-independent messages
Operating-system-dependent exchange mechanism for optimum operating 
system integration
Asynchronous event-driven mechanism, resulting in high throughput
Well-defined mechanism for manufacturer-specific extensions
Multiple supplementary services
CAPI and RVS-COM
The router supports the ISDN Device Control Protocol (ISDN-DCP) from 
RVS-COM. ISDN-DCP allows a workstation on the LAN or router to use legacy 
dial computer telephony integration (CTI) applications. These applications 
include placing and receiving telephone calls and transmitting and receiving 
faxes. 
Using ISDN-DCP, the router acts as a DCP server. By default, the router listens 
for DCP messages on TCP port number 2578 (the Internet-assigned number for 
RVS-COM DCP) on its LAN port.
When the router receives a DCP message from a DCP client (connected to the 
LAN port of the router), the router processes the message and acts on it. The 
router can send confirmations to the DCP clients and ISDN packets through the 
BRI port of the router.  
						

							 
5-3
Cisco 800 Series Software Configuration Guide
78-5372-06
Chapter 5      Configuring Remote CAPI
Supported B Channel Protocols
When the router receives packets destined for one of the DCP clients on its BRI 
port, the router formats the packet as a DCP message and sends it to the 
corresponding client. The router supports all of the DCP messages in the 
ISDN-DCP specifications defined by RVS-COM.
Supported B Channel Protocols
The router provides two 64-kbps B channels to CAPI clients. Each B channel can 
be configured separately to work in either HDLC mode or bit transparent mode. 
For CAPI support, layers B2 through B7 protocols are transparent to the 
applications using these B channels.
The ISDN core engine of RVS-COM supports the following B-channel protocols:
CAPI layer B1
–64 kbps with HDLC framing
–64 kbps bit transparent operation with byte framing from the network
–T.30 modem for fax Group 3
–Modem with full negotiation 
CAPI layer B2
–V. 1 2 0
–Transparent
–T.30 modem for fax Group 3
–Modem with full negotiation 
CAPI layer B3
–Transparent
–T.90NL with compatibility to T.70NL according to T.90 Appendix II
–ISO 8208 (X.25 DTE-DTE) module 8 and windows size 2, no multiple 
logical connections
–T.30 for fax Group 3
–Modem with full negotiation 
						

							 
Chapter 5      Configuring Remote CAPI
Supported D Channel Protocols
5-4
Cisco 800 Series Software Configuration Guide
78-5372-06
T.30 for fax Group 3 (SFF file format [default], sending and receiving up to 
14400 bits/sec with ECM option, modulations V.17, V.21, V.27ter, V.29)
Analog modem (sending and receiving up to 14,400 bits/sec, modulations 
V. 2 1 ,  V. 2 2 ,  V. 2 2 b i s ,  V. 2 3 ,  V. 3 2 ,  V. 3 2 b i s )
Supported D Channel Protocols
CAPI support is available only for the ISDN switch type Net3. 
Supported Applications 
ISDN-DCP supports CAPI and non-CAPI applications. Applications are 
supported that use one or two B channels for data transfer, different HDLC-based 
protocols, Euro file transfer, or G4 fax; also supported are applications that send 
bit-transparent data such as A/Mu law audio, group 3 faxes, analog modem, or 
analog telephones. 
Requirements
Before you can enable the RCAPI feature on the Cisco 800 series router, the 
following requirements must be met:
Cisco 800 series software with RCAPI support is installed on the router.
CAPI commands are properly configured on the router.
Both the CAPI local device console and RCAPI client devices on the LAN 
are correctly installed and configured with RVS-COM client driver software. 
						

							 
5-5
Cisco 800 Series Software Configuration Guide
78-5372-06
Chapter 5      Configuring Remote CAPI
Remote CAPI Default Setting
Remote CAPI Default Setting
The default setting is disabled. To enable this feature, use the Cisco IOS rcapi 
server port command in global configuration mode:
rcapi server port number
no rcapi server port
where number is an optional parameter for the port number. If you do not enter a 
port number, the default port 2578 is used.
For more information, see the “Configuring Remote CAPI” chapter in the
Cisco 800 Series Software Configuration Guide.
Configuring RCAPI
The following procedure provides step-by-step instructions for configuring 
RCAPI on the Cisco 800 series router:
Step 1At the local device console, change to global configuration mode.
router# configure terminal
router(config)#
Step 2Set the switch type. In the following example, the switch type is set to European 
Telecommunication Standards Institute (ETSI).
router(config)# isdn switch-type basic-net3
Step 3Enter the RCAPI directory number assigned by the ISDN provider for the device. 
For example:
router(config)# rcapi number 12345
Step 4Optional. Perform this step only if you wish to specify a port number for RCAPI 
functions. Otherwise, the default port 2578 is used. Configure the same number 
on both the router and client PC. For example:
router(config)# rcapi server port 2000
Step 5Exit from global configuration mode to interface configuration mode.
router(config)# int bri0 
						

							 
Chapter 5      Configuring Remote CAPI
Configuring RCAPI
5-6
Cisco 800 Series Software Configuration Guide
78-5372-06
Step 6Set the switch type for the BRI0 interface. In the following example, the switch 
type is set to ETSI.
router(config-if)# isdn switch-type basic-net3
Step 7Set the modem as the default handler for incoming voice calls.
router(config-if)# isdn incoming-voice modem
Step 8Change to privileged EXEC mode either by pressing Ctrl-Z or by entering exit 
twice, once at the interface mode prompt and again at the global configuration 
mode prompt.
router(config-if)# exit
router(config)# exit
router#
Step 9Optional. Enter the following if you wish to display RCAPI status.
router# show rcapi status
Step 10Optional. In privileged EXEC mode, start the debug program to run in the 
background.
router# debug rcapi events
Step 11If required, at each remote device console, change to global configuration mode. 
Repeat Step 2 through Step 10 to configure that device. 
						

							CHAPTER
 
6-1
Cisco 800 Series Software Configuration Guide
78-5372-06
6
Configuring Telephone Interfaces
The term telephone port refers to the physical port on the router back panel. The 
term telephone interface refers to a logical interface that you must configure to 
make an analog telephone or fax connected to a telephone port work properly.
This chapter describes how to configure standard and advanced features of the 
those Cisco 800 series routers supporting telephone features (Cisco 803, 804, and 
813 routers). These routers support push-button analog telephones only; the Cisco 
routers do not support rotary telephones. This chapter also describes how to use 
the connected devices.
Physical Characteristics
This section discusses the following:
Physical characteristics that you must configure
Tones that some users might need to configure
Ringer equivalent number (REN)
Configuring Physical Characteristics
Starting in global configuration mode, use these steps to configure physical 
characteristics. For information on the commands used in this table, refer to the 
Cisco IOS documentation set. 
						

							 
Chapter 6      Configuring Telephone Interfaces
Physical Characteristics
6-2
Cisco 800 Series Software Configuration Guide
78-5372-06
Command Purpose
Step 1pots country countryEnter the pots country ? command to get a 
list of supported countries and the code you 
must input to indicate a particular country. 
By specifying a country, you are 
configuring your telephone to use 
country-specific default settings for each 
physical characteristic. If you need to 
change a country-specific default setting, 
you can use the optional commands 
described in this table.
Step 2pots line-type 
{type1 | type2 | type3}Optional. Set the line type. Line type 1 runs 
at 600 ohms, line type 2 runs at 900 ohms, 
and line type 3 runs at 300 or 400 ohms. 
Lines in the U.S. typically run at 600 ohms 
(line type 1).
Step 3pots dialing-method 
{overlap | enblock}Optional. Set the dialing method. If you 
select overlap, the router transmits each 
digit dialed in a separate message. If you 
select enblock, the router collects all digits 
dialed and transmits in one message. To 
interrupt collection and transmission of 
dial-string digits, enter pound sign (#) or 
stop dialing digits until a timer runs out.
Step 4pots disconnect-supervision
{osi | reversal}Optional. Set how the router notifies the 
connected device when calling party has 
hung up. Japan typically uses the reversal 
option. Most other countries use the osi 
option.
Step 5pots encoding {alaw | ulaw} Optional. Set the pulse code modulation 
(PCM) encoding scheme. Europe typically 
uses the alaw option. North America 
typically uses the ulaw option. 
						

							 
6-3
Cisco 800 Series Software Configuration Guide
78-5372-06
Chapter 6      Configuring Telephone Interfaces
Physical Characteristics
Step 6pots tone-source 
{local | remote}Optional. Set who supplies dial, ringback, 
and busy tones. If you select local, the 
router supplies the tones. If you select 
remote, the telephone switch provides the 
tones. For more information, refer to the 
“Tones for NET3 Switch” section on 
page 6-4.
Step 7pots ringing-freq 
{20Hz | 25Hz | 50Hz}Optional. Set the frequency at which 
telephone ports ring.
Step 8pots disconnect-time intervalOptional. If a connected device, such as an 
answering machine, fails to detect that a 
calling party has hung up, you can adjust 
the interval at which selected disconnect 
supervision method is applied. Interval is 
from 50 to 2000 milliseconds.
Step 9pots silence-time intervalOptional. If a connected device, such as an 
answering machine, fails to detect that a 
calling party has hung up, you can adjust 
the interval of silence after a hang-up. 
Interval is from 0 to 10 seconds.
Step 10pots distinctive-ring-guard-
time millisecondsOptional. Set the delay, in milliseconds (0 
to 1000), before a telephone port can be 
rung after a previous call is disconnected. 
For more information, refer to the 
“Distinctive Ringing” section on 
page 6-11.
Step 11show pots statusOptional. Display settings of physical 
characteristics as well as other information 
on telephone interfaces. Command Purpose 
						

							 
Chapter 6      Configuring Telephone Interfaces
Creating Dial Peers
6-4
Cisco 800 Series Software Configuration Guide
78-5372-06
Tones for NET3 Switch
By default, the Cisco 800 series routers are configured so that the telephone 
switch supplies tones, such as dial, ringback, and busy tones. However, NET3 
switches, which are used in Europe, do not provide these tones. You can use the 
pots tone-source local command from global configuration mode to configure 
the router instead of the telephone switch to provide these tones.
NoteThis command applies only to ISDN lines connected to a NET3 switch.
If the pots dialing-method command is set to enblock, the router provides the 
internal dial tone.
REN
You can connect multiple devices (analog telephone or fax machine) to a router 
telephone port. The number of devices that you can connect depends on the 
following:
REN of the telephone port (five).
REN of each device that you plan to connect. (You can usually find the REN 
on the bottom of a device.) 
If the REN of each device you plan to connect is one, then you can connect a 
maximum of five devices to that particular telephone port. 
Creating Dial Peers
You can create a dial peer to determine how incoming calls are routed to the 
telephone ports. You can create a total of six dial peers for the two telephone 
ports. There are no restrictions on how many dial peers you can create per port; 
for example, you can create six dial peers for port 1 and zero on port 2. 
Starting from global configuration mode, use the steps below to create a dial peer.