Table Of Contents
Configuring Telephone Interfaces
Physical Characteristics
Configuring Physical Characteristics
Tones for NET3 Switch
REN
Creating Dial Peers
What You Need to Know About SPIDs
Forwarding Incoming ISDN Voice Calls to Connected Devices
Configuring Advanced Telephone Features
ISDN Voice Priority
Data over Voice Bearer Service
Distinctive Ringing
Caller Identification
How to Use Telephones Connected to Cisco 800 Series Routers
Making a Basic Call
Disabling Pound Key End-of-Call Function
Using Supplementary Services
Call Holding and Retrieving
Call Waiting
Three-Way Conference Call
Call Transfer
Call Forwarding
POTS Dial Feature (Japan Only)
Activating the POTS Dial Feature
Displaying POTS Call State
Output Example
Disconnecting a POTS Call
POTS Debug Command
Debug Message Formats
CSM States
CSM Events
Events
Cause Values
Call Scenarios for the POTS Dial Feature
Call Scenario 1
Call Scenario 2
Call Scenario 3
Cisco 813 Router Enhanced Voice Features
(Japan Only)
General Requirements and Restrictions
Caller ID Display
Requirements for Activating Caller ID Display
Configuring Caller ID Display
Call Blocking on Caller ID
Requirements for Activating Call Blocking on Caller ID
Configuring Call Blocking on Caller ID
Local Call Waiting
Requirements for Activating Local Call Waiting
Configuring Local Call Waiting
E Ya Yo
Requirements for Activating E Ya Yo
Configuring E Ya Yo
Voice Warp
Requirements for Activating Voice Warp
Configuring Voice Warp
Voice Select Warp
Requirements for Activating Voice Select Warp
Configuring Voice Select Warp
Nariwake
Requirements for Activating Nariwake
Configuring Nariwake
Trouble-Call Blocking
Requirements for Activating Trouble-Call Blocking
Configuring Trouble-Call Blocking
I Number
Requirements for Activating I Number
Configuring I Number
Silent Fax Calls
Configuring Silent Fax Calls
Example of Silent Fax Calls Configuration
Example of Silent Fax Calls Configuration Output
Supplementary Telephone Services for the Net3 Switch
Requirements for Supplementary Telephone Services Support
Configuring Caller ID for the Net3 Switch
Call Forwarding for the Net3 Switch
Configuring the Call Forwarding Method
Configuring the Call Forwarding Service
Displaying POTS Status
Configuring CLIR
Debug POTS Commands
Cisco 804 and 813 Routers Enhanced Voice Features
Prefix Dialing
Configuring a Prefix Number
Configuring a Prefix Filter
Calling Between Telephone Ports
Activating the Calling Between Telephone Ports Feature
Calling Between Telephone Ports Scenarios
Redial
Activating the Redial Feature
Redial Feature Scenarios
Call Transfer
Activating the Call Transfer Feature
Call Transfer Feature Scenarios
Volume Adjustments
Volume Adjustment Configuration Example
Volume Adjustment Configuration Output Example
Distinctive Ringing Based on Caller ID
Configuring Distinctive Ringing Based on Caller ID
Distinctive Ringing Scenarios
Distinctive Ringing Configuration Example
Distinctive Ringing Configuration Output Example
Subaddresses for POTS Ports
Configuring Subaddresses for POTS Ports
Subaddressing Scenarios
Subaddressing Configuration Example
Subaddressing Configuration Output Example
Caller ID on the Cisco 813 Router
Debug POTS Commands
Local Call Forwarding
Configuring Local Call Forwarding
Local Call Forwarding Scenarios
Local Call Forwarding Configuration Example
Local Call Forwarding Configuration Output Example
Support for PIAFS
Configuring PIAFS
PIAFS Scenarios
PIAFS Status
PIAFS Configuration Output Example
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.
| |
Command
|
Purpose
|
Step 1
|
pots country country
|
Enter 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 2
|
pots 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 3
|
pots 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 4
|
pots 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 5
|
pots 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.
|
Step 6
|
pots 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.
|
Step 7
|
pots ringing-freq {20Hz | 25Hz | 50Hz}
|
Optional. Set the frequency at which telephone ports ring.
|
Step 8
|
pots disconnect-time interval
|
Optional. 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 9
|
pots silence-time interval
|
Optional. 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 10
|
pots distinctive-ring-guard- time milliseconds
|
Optional. 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.
|
Step 11
|
show pots status
|
Optional. Display settings of physical characteristics as well as other information on telephone interfaces.
|
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.
Note
This 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.
| |
Command
|
Purpose
|
Step 1
|
dial-peer voice tag pots
|
Set up tag number (1 through 6) for dial peer.
|
Step 2
|
destination-pattern ldn
|
Specify local ISDN directory number assigned to telephone interface. Do not specify an area code.
|
Step 3
|
port port-number
|
Specify number (1 or 2) associated with telephone port.
|
Step 4
|
no call-waiting
|
Optional. Disable call waiting.
|
Step 5
|
ring cadence-number
|
Optional. Set up distinctive ring (0 through 2). For more information, see the "Distinctive Ringing" section.
|
Step 6
|
show dial-peer voice [tag]
|
Optional. Display all or a particular dial-peer configuration (1 through 6).
|
For example, if you have connected one voice device (555-1111) to port 1 and another (555-2222) to port 2, you can create two dial peers. The following output example shows two dial peers:
dial-peer voice 1 pots
destination-pattern 5551111
port 1
no call-waiting
ring 0
dial-peer voice 2 pots
destination-pattern 5552222
port 2
no call-waiting
ring 0
When a caller dials 555-1111, the call is routed to port 1. When a caller dials 555-2222, the call is routed to port 2. If the dial peers are not created, calls to both numbers are routed to port 1.
Note
Make sure that all ISDN directory numbers associated with a service profile identifier (SPID) are associated with one port. For example, if both 555-1111 and 555-2222 are associated with SPID 1 and you associate 555-1111 to port 1 and 555-2222 to port 2, you will not be able to make calls on ports 1 and 2 simultaneously.
What You Need to Know About SPIDs
North America uses SPIDs to identify subscribed services. The SPID format is generally an ISDN telephone number with several numbers added to it, such as 40855511110101. Your ISDN line could be assigned zero, one, or two SPIDs.
You must associate a SPID with an ISDN directory number and a telephone port number by using the isdn spid1 and isdn spid2 commands in global configuration mode and the port command in dial peer configuration mode. Make sure that you specify all the ISDN directory numbers provided by your telephone service provider in the isdn spid1 and isdn spid2 commands. Also make sure that all ISDN directory numbers associated with a SPID are associated with the same telephone port. For information on using the port command while setting up a dial peer, see the "Creating Dial Peers" section.
Forwarding Incoming ISDN Voice Calls to Connected Devices
Starting from global configuration mode, follow these steps:
| |
Command
|
Purpose
|
Step 1
|
interface bri0
|
Specify parameters for the WAN interface.
|
Step 2
|
isdn incoming-voice modem
|
Specify that incoming ISDN voice calls are forwarded to devices connected to telephone ports.
|
Note
If you do not enter the isdn incoming-voice modem command, the router rejects incoming ISDN voice calls.
Configuring Advanced Telephone Features
This section describes advanced telephone features and how to configure them.
ISDN Voice Priority
The ISDN voice priority feature controls the priority of data and voice calls for telephones or fax machines connected to the router telephone ports. If an ISDN circuit endpoint is busy with a data call or calls and either a voice call comes in (incoming) or you attempt to place a voice call (outgoing), the data call is handled per the voice priority setting.
You can configure the router so that data calls are handled in one of the following ways:
•
A voice call always supercedes ("bumps") a data call. This is the default setting.
•
A voice call supercedes a data call only if there are more than one call to the same destination.
•
A voice call never supercedes a data call.
Use the following command to reconfigure the priority.
| |
Command
|
Purpose
|
| |
isdn voice-priority local-directory-number {in | out} {always | conditional | off}
|
Configure ISDN voice priority for each ISDN directory number.
|
If you have multiple ISDN directory numbers associated with a SPID, then the outgoing voice priority that you set for any of these directory numbers applies to the other numbers.
For example, if you enter the following command, the outgoing voice priority for all directory numbers specified in the isdn spid1 command is set to conditional:
router(config-if)# isdn spid1 0 4085551111 4085552222 4085553333
router(config-if)# isdn voice-priority 5551111 out conditional
Table 6-1 describes the possible data call scenarios, what happens when a voice call comes in, and what happens when you place an outgoing voice call with a particular configuration.
Table 6-1 Incoming and Outgoing ISDN Voice Priority Scenarios
Scenario
|
Always
|
Conditional
|
Off
|
Two data channels to destination A.
|
Bump one data channel when you pick up handset to answer incoming voice call or to place outgoing voice call.
|
Bump one data channel when you pick up handset to answer incoming voice call or to place outgoing voice call.
|
No bump; voice caller receives busy signal.
|
One data channel to destination A; one data channel to destination B.
|
Bump one data channel when you pick up handset to answer incoming voice call or to place outgoing voice call.
|
No bump; voice caller receives busy signal.
|
No bump; voice caller receives busy signal.
|
The setting of the pots dialing-method command determines whether you hear a busy signal if a data call cannot be bumped when you are trying to make an outgoing call. If the setting is overlap, you hear a busy signal when you pick up the handset. If the setting is enblock, you hear a dial tone initially, then a busy signal.
Data over Voice Bearer Service
Note
This section applies only to analog telephone services in the U.S.
In some tariff areas, voice calls are less expensive than data calls. If this is the case in your tariff area, the Cisco 800 series routers support incoming and outgoing data over voice (DOV) calls. DOV calls are data calls made over the ISDN line using voice bearer capability (VBC).
The router recognizes the difference between a data call and a voice call. Incoming data calls are routed to the LAN over the Ethernet port. If a telephone interface has been configured for DOV, incoming data calls made with VBC are routed to the LAN over the Ethernet port. Figure 6-1 and Table 6-2 illustrate a data call being routed to the LAN.
Incoming voice calls are forwarded to the analog device over the analog telephone port, as shown in Figure 6-2 and Table 6-3.
Figure 6-1 Data Call over VBC Line
Table 6-2 Key for Data Call over VBC Line
Callout Number
|
Description
|
1
|
Analog telephone
|
2
|
ISDN BRI line with VBC
|
3
|
Central office switch
|
4
|
Ethernet LAN
|
Figure 6-2 Voice Call over VBC Line
Table 6-3 Key for Voice Call over VBC Line
Callout Number
|
Description
|
1
|
Analog telephone
|
2
|
ISDN BRI line with VBC
|
3
|
Router
|
4
|
Ethernet LAN
|
Note
When the router is configured for DOV, ISDN BRI calls are made with VBC, which has a data rate of 56 kbps, instead of the usual ISDN BRI data rate of 64 kbps.
Use the following command to configure the router to accept incoming DOV calls:
isdn incoming-voice data 56
Follow these steps to configure the router to place outgoing DOV calls:
| |
Command
|
Purpose
|
Step 1
|
class voice number
|
Create a dialer map.
|
Step 2
|
map-class dialer voice
|
Define a class of shared configuration parameters for outgoing calls.
|
Step 3
|
dialer voice-call
|
Configure router to make outgoing DOV calls.
|
Step 4
|
dialer isdn speed 56
|
Specify bit rate used on B channel associated with specified map class.
|
Distinctive Ringing
A ringing cadence is a pattern of a ringing and a quiet period. There are two types of ringing cadences: a primary ringing cadence and distinct ringing. The primary cadence is determined by the country where your router is located. In addition to the primary cadence, you can configure up to two distinctive rings on a telephone port.
Because the router associates a distinctive ring with the ISDN directory number assigned to an interface, you must configure a distinctive ring with a dial peer. For information on dial peers and how to configure them, see the "Creating Dial Peers" section.
Note
Generally your telephone service provider assigns one ISDN directory number for each SPID. You must have one ISDN directory number for each distinctive ring that you set up. Therefore, if you want to set up two distinctive rings, you must request an additional ISDN directory number from your telephone service provider.
To configure the ringing cadence, insert the following commands into a dial-peer configuration:
ring cadence-number
where cadence-number can be 0, 1, or 2.
•
Type 0 is a primary ringing cadence—default ringing cadence for country your router is located in.
•
Type 1 is a distinctive ring—0.8 seconds on, 0.4 seconds off, 0.8 seconds on, 4 seconds off.
•
Type 2 is a distinctive ring—0.4 seconds on, 0.2 seconds off, 0.4 seconds on, 0.2 seconds off, 0.8 seconds on, 4 seconds off.
By default, the ring cadence is set to 0, which means that the interface uses the primary ringing cadence.
You can also insert the following command syntax into a dial-peer configuration:
pots distinctive-ring-guard-time milliseconds
where milliseconds can be a number from 50 to 1000. This command configures the delay, in milliseconds, before a telephone port can be rung after a previous call is disconnected. The default is no delay.
Caller Identification
In addition to an analog telephone or fax machine, North American users can connect a caller ID device to the router telephone ports. This device displays the telephone numbers of incoming callers. The Cisco 800 series routers support the following caller ID devices:
•
AT&T 25
•
AT&T 85 Plus
•
CIDCO
•
Fans Callscreener
•
GE Caller ID with phone
•
GE Caller ID without phone
•
Northwestern Bell Phone, Bell Phone
•
Radio Shack Caller ID System 350
The Cisco 800 series routers do not support the following devices:
•
Southwestern Bell Freedom Phone
•
TTY System
How to Use Telephones Connected to Cisco 800 Series Routers
This section describes how to make a basic call and how to use the supplementary services that you ordered from your telephone service provider.
Making a Basic Call
To make a basic telephone call, pick up the handset, and dial the number of the desired party.
To make a basic call if your router is connected to a Nippon Telegraph and Telephone (NTT) switch, follow these steps:
Step 1
Dial the telephone number.
You must enter each digit within 12 seconds of entering the previous digit. If you wait longer than 12 seconds, an incomplete set of digits is sent to the switch.
Step 2
Send the entire set of digits to the switch by using one of the following methods:
•
Press the pound key (#) on the telephone keypad.
•
Wait 12 seconds without entering any digits. After 12 seconds, the router sends the set of digits to the switch.
Disabling Pound Key End-of-Call Function
You can disable the end-of-call function (initiated by pressing the pound key [#]) by entering the following command on the telephone keypad:
**98#
Note
This command applies only to ISDN lines connected to an NTT switch.
You can disable this function if a telephone number you are dialing requires the pound key (#) as one of the digits. After entering the **98# command, wait for a dial tone and then enter the digits, including the pound key. To send the digits to the switch, wait 6 seconds without entering any digits.
The end-of-call function automatically resumes for the next call.
Using Supplementary Services
This section describes how to use the following supplementary services:
•
Call Holding and Retrieving
•
Call Waiting
•
Three-Way Conference Call
•
Call Transfer
•
Call Forwarding
Call Holding and Retrieving
For this feature to work, you must request it when you order your ISDN line. For information on ordering your ISDN line, see Appendix D, "Provisioning an ISDN Line." However, you do not need to configure the router to make this feature work.
You can put an active voice call on hold, make a second call, and toggle between the two calls. Follow these steps:
Step 1
Put the active call on hold, and get a dial tone by quickly pressing the telephone receiver (flash) button once, and then entering **95# on the telephone keypad.
Step 2
Make the second call.
Step 3
Toggle between the two calls by quickly pressing the flash button.
If you hang up with a call still on hold, the phone rings to remind you of the outstanding call. Pick up the handset to reconnect to the call.
Call Waiting
For this feature to work, you must request it when you order your ISDN line. For information on ordering your ISDN line, see Appendix D, "Provisioning an ISDN Line."
By default, call waiting is enabled. You can disable it permanently by using the no call-waiting command. (You might want to disable it for fax machines.) Because the router associates call waiting with the ISDN directory number assigned to a telephone interface, you should disable call waiting at the same time that you are configuring a dial peer. For information on dial peers and how to configure them, refer to the "Creating Dial Peers" section.
To disable call waiting on a per-call basis, enter **99# on the telephone keypad.
During an active voice call, a call-waiting tone sounds if another call comes in. Subsequent tones sound at 10-second intervals until the incoming caller hangs up or until you answer the call. During this time, the incoming caller hears ringing.
When you hear the call-waiting tone, you can do one of the following:
•
Put the current call on hold, and answer the incoming call
•
Hang up the current call, and answer the new call.
To put the current call on hold and answer the incoming call, quickly press the telephone receiver (flash) button once. Press this button again to go back to the current call.
Three-Way Conference Call
For this feature to work, you must request it when you order your ISDN line. For information on ordering your ISDN line, see Appendix D, "Provisioning an ISDN Line."
If you are connected to a National ISDN-1 (NI1) or a Northern Telecom DMS-100 custom switch, you might need to activate this feature by using the following command syntax:
isdn conference-code range
The range is from 0 to 999. The default code is 60. Your telephone service provider should provide a code when you order this feature; if a code other than 60 is provided, you need to reconfigure the code using the isdn conference-code command.
Otherwise, you do not need to configure the router to make this feature work.
You can talk simultaneously with two other parties. To create a conference call, follow these steps:
Step 1
Put the first party on hold and get a dial tone by quickly pressing the telephone receiver (flash) button once.
Step 2
Dial the second party.
Step 3
Add the first party to the call by quickly pressing the flash button.
Call Transfer
For this feature to work, you must request it when you order your ISDN line. For information on ordering your ISDN line, see Appendix D, "Provisioning an ISDN Line."
If you are connected to a National ISDN-1 (NI1) or a Northern Telecom DMS-100 Custom switch, you might need to activate this feature, using the following command syntax:
isdn transfer-code range
The range is from 0 to 999. The default code is 61. Your telephone service provider should provide a code when you order this feature; if a code other than 61 is provided, you need to reconfigure the code by using the isdn transfer-code command.
Otherwise, you do not need to configure the router to make this feature work.
You can transfer an incoming or outgoing voice call to another party. To transfer a call, do the following:
Note
If you are connected to an NTT switch, you will not be able to transfer an outgoing call.
Step 1
Put the first party on hold, and get a dial tone by quickly pressing the telephone receiver (flash) button once.
Step 2
Dial the second party to which you want to transfer the call.
Step 3
While still connected to the second party, hang up.
Hanging up connects the first and second parties. Instead of doing Step 3, you can also create a three-way call conference by quickly pressing the flash button once.
If the call to the second party fails, you can return to the first party by doing one of the following:
•
Quickly pressing the telephone receiver (flash) button once
•
Hanging up
If you hang up, the telephone rings to indicate that the first party is still on hold.
Call Forwarding
The call forwarding feature works for Sweden and Finland only. For this feature to work, you must request it when you order your ISDN line. For information on ordering your ISDN line, see Appendix D, "Provisioning an ISDN Line."
The router supports the following call forwarding features:
•
Call forwarding unconditional (CFU)—you can forward all incoming calls to another telephone number.
•
Call forwarding no reply (CFNR)—you can forward incoming calls that are not answered within a defined period to another telephone number.
•
Call forwarding busy (CFB)—you can forward incoming calls that get a busy signal to another telephone number.
To make sure that the router accepts the activation and deactivation of the call forwarding features using the telephone keypad, use the pots country country command in global configuration mode. The country variable is the country that your router is in. Enter the pots country ? command to get a list of supported countries and the code you must enter to indicate a particular country.
To activate call forwarding unconditional, call forwarding no reply, or call forwarding busy, follow these steps:
Step 1
Pick up the telephone handset.
Step 2
Enter the following on the telephone keypad:
*feature-number *telephone-number-to-forward-to#
Your telephone service provider should provide the number for each call forwarding feature. For example, to forward a call to 408-555-2222, enter the following:
Step 3
Hang up the handset.
To deactivate call forwarding unconditional, call forwarding no reply, or call forwarding busy, follow these steps:
Step 1
Pick up the telephone handset.
Step 2
Enter the following on the telephone keypad:
Your telephone service provider should provide the number for each call forwarding feature. For example, to deactivate call forwarding, enter the following:
Step 3
Hang up the handset.
Note
In the U.S., the call forwarding variable (CFV) feature is available with the NI1 capability package EZ-1. With CFV, you can forward incoming calls. You can turn this feature on or off through access codes supplied by your telephone service provider.
POTS Dial Feature (Japan Only)
The Cisco 813 router supports the plain old telephone service (POTS) dial feature for Japanese telephones. This feature can be activated by a dial application on your workstation that dials a telephone number for the POTS port on the Cisco 813 router. The telephone connected to the port can be on- or off-hook when the dial command is issued. If the telephone is on-hook, the router rings the telephone, waits until the telephone is taken off hook, then dials the number requested. If the telephone is off-hook when the command is issued, the router dials the number requested, provided that the telephone is receiving a dial tone.
Activating the POTS Dial Feature
Each time you wish to activate this feature on the router for use by the dial application, enter the following Cisco IOS command in EXEC mode:
test pots port dial number [#]
where port is the port number 1 or 2, and number is the telephone number to dial.
Note
The router does not turn off dual tone multifrequency (DTMF) detection from the telephone when you enter the POTS dial command. If you do not terminate the number variable with a pound (#) character, you can complete the call by using the telephone key pad.
The following example shows the POTS dial command:
router# test pots 1 dial 4085551234#
Displaying POTS Call State
To show the current state of POTS calls and the most recent event received by the call switching module (CSM), use the show pots csm command in EXEC mode.
where port is port number 1 or 2.
Output Example
The following is an example of the show pots csm command screen output:
CSM Finite State Machine:
Call 0 - State: idle, Call Id: 0x0
Event: CSM_EVENT_NONE Cause: 0
Call 1 - State: idle, Call Id: 0x0
Event: CSM_EVENT_NONE Cause: 0
Call 2 - State: idle, Call Id: 0x0
Event: CSM_EVENT_NONE Cause: 0
Disconnecting a POTS Call
To disconnect a telephone call for the POTS port on the router, use the test pots port disconnect command in EXEC mode:
test pots port disconnect
where port is the port number 1 or 2.
The following example disconnects a telephone call from POTS port 1:
router# test pots 1 disconnect
POTS Debug Command
To display the status of calls made to and from the POTS ports, enter the following command in EXEC mode:
Entering this command activates events by which your dial application can determine the progress of calls to and from the ports.
Debug Message Formats
Debug messages are displayed in one of two formats that are relevant to the POTS dial feature:
hh:mm:ss: CSM_STATE: CSM_EVENT, call id = ??, port = ?
or
hh:mm:ss: EVENT_FROM_ISDN:dchan_idb=0x???????, call_id=0x????, ces=?
bchan=0x????????, event=0x?, cause=0x??
where:
•
hh:mm:ss is a timestamp in hours, minutes, and seconds.
•
CSM_STATE is one of the call switching module (CSM) states listed in Table 6-4.
•
call id is a hexadecimal value from 0x00 to 0xFF.
•
port is telephone port 1 or 2.
•
EVENT_FROM_ISDN is a CSM event. Table 6-5 shows a list of CSM events.
•
dchan_idb is an internal data structure address.
•
ces is the connection end point suffix used by ISDN.
•
bchan is the channel used by the call. A value of 0xFFFFFFFF indicates that a channel is not assigned.
•
event is represented by a hexadecimal value that is translated into a CSM event. Table 6-6 shows a list of events and the corresponding CSM events.
•
cause is represented by a hexadecimal value that is given to call-progressing events. Table 6-7 shows a list of cause values and definitions.
CSM States
Table 6-4 shows the values for CSM states.
Table 6-4 CSM States
CSM State
|
Description
|
CSM_IDLE_STATE
|
Telephone on hook
|
CSM_RINGING
|
Telephone ringing
|
CSM_SETUP
|
Setup for outgoing call in progress
|
CSM_DIALING
|
Dialing number of outgoing call
|
CSM_IVR_DIALING
|
Interactive voice response (IVR) for Japanese telephone dialing
|
CSM_CONNECTING
|
Waiting for carrier to connect the call
|
CSM_CONNECTED
|
Call connected
|
CSM_DISCONNECTING
|
Waiting for carrier to disconnect the call
|
CSM_NEAR_END_DISCONNECTING
|
Waiting for carrier to disconnect the call
|
CSM_HARD_HOLD
|
Call on hard hold
|
CSM_CONSULTATION_HOLD
|
Call on consultation hold
|
CSM_WAIT_FOR_HOLD
|
Waiting for carrier to put call on hard hold
|
CSM_WAIT_FOR_CONSULTATION_HOLD
|
Waiting for carrier to put call on consultation hold
|
CSM_CONFERENCE
|
Waiting for carrier to complete call conference
|
CSM_TRANSFER
|
Waiting for carrier to transfer call
|
CSM_APPLIC_DIALING
|
Call initiated from Cisco IOS command-line interface (CLI)
|
CSM Events
Table 6-5 shows the values for CSM events.
Table 6-5 CSM Events
CSM Events
|
Description
|
CSM_EVENT_INTER_DIGIT_TIMEOUT
|
Time waiting for dial digits has expired
|
CSM_EVENT_TIMEOUT
|
Near or far end disconnect timeout
|
CSM_EVENT_ISDN_CALL
|
Incoming call
|
CSM_EVENT_ISDN_CONNECTED
|
Call connected
|
CSM_EVENT_ISDN_DISCONNECT
|
Far end disconnected
|
CSM_EVENT_ISDN_DISCONNECTED
|
Call disconnected
|
CSM_EVENT_ISDN_SETUP
|
Outgoing call requested
|
CSM_EVENT_ISDN_SETUP_ACK
|
Outgoing call accepted
|
CSM_EVENT_ISDN_PROC
|
Call proceeding and dialing completed
|
CSM_EVENT_ISDN_CALL_PROGRESSING
|
Call being received in band tone
|
CSM_EVENT_ISDN_HARD_HOLD
|
Call on hard hold
|
CSM_EVENT_ISDN_HARD_HOLD_REJ
|
Hold attempt rejected
|
CSM_EVENT_ISDN_CHOLD
|
Call on consultation hold
|
CSM_EVENT_ISDN_CHOLD_REJ
|
Consultation hold attempt rejected
|
CSM_EVENT_ISDN_RETRIEVED
|
Call retrieved
|
CSM_EVENT_ISDN_RETRIEVE_REJ
|
Call retrieval attempt rejected
|
CSM_EVENT_ISDN_TRANSFERRED
|
Call transferred
|
CSM_EVENT_ISDN_TRANSFER_REJ
|
Call transfer attempt rejected
|
CSM_EVENT_ISDN_CONFERENCE
|
Call conference started
|
CSM_EVENT_ISDN_CONFERENCE_REJ
|
Call conference attempt rejected
|
CSM_EVENT_ISDN_IF_DOWN
|
ISDN interface down
|
CSM_EVENT_ISDN_INFORMATION
|
ISDN information element received (used by Nippon Telegraph and Telephone [NTT] IVR application)
|
CSM_EVENT_VDEV_OFFHOOK
|
Telephone off hook
|
CSM_EVENT_VDEV_ONHOOK
|
Telephone on hook
|
CSM_EVENT_VDEV_FLASHHOOK
|
Telephone hook switch has flashed
|
CSM_EVENT_VDEV_DIGIT
|
DTMF digit has been detected
|
CSM_EVENT_VDEV_APPLICATION_CALL
|
Call initiated from Cisco IOS command-line interface (CLI)
|
Events
Table 6-6 shows the values for events that are translated into CSM events.
Table 6-6 Event Values and Corresponding CSM Events
Hexadecimal Value
|
Event
|
CSM Event
|
0x0
|
DEV_IDLE
|
CSM_EVENT_ISDN_DISCONNECTED
|
0x1
|
DEV_INCALL
|
CSM_EVENT_ISDN_CALL
|
0x2
|
DEV_SETUP_ACK
|
CSM_EVENT_ISDN_SETUP_ACK
|
0x3
|
DEV_CALL_PROC
|
CSM_EVENT_ISDN_PROC
|
0x4
|
DEV_CONNECTED
|
CSM_EVENT_ISDN_CONNECTED
|
0x5
|
DEV_CALL_PROGRESSING
|
CSM_EVENT_ISDN_CALL_PROGRESSING
|
0x6
|
DEV_HOLD_ACK
|
CSM_EVENT_ISDN_HARD_HOLD
|
0x7
|
DEV_HOLD_REJECT
|
CSM_EVENT_ISDN_HARD_HOLD_REJ
|
0x8
|
DEV_CHOLD_ACK
|
CSM_EVENT_ISDN_CHOLD
|
0x9
|
DEV_CHOLD_REJECT
|
CSM_EVENT_ISDN_CHOLD_REJ
|
0xa
|
DEV_RETRIEVE_ACK
|
CSM_EVENT_ISDN_RETRIEVED
|
0xb
|
DEV_RETRIEVE_REJECT
|
CSM_EVENT_ISDN_RETRIEVE_REJ
|
0xc
|
DEV_CONFR_ACK
|
CSM_EVENT_ISDN_CONFERENCE
|
0xd
|
DEV_CONFR_REJECT
|
CSM_EVENT_ISDN_CONFERENCE_REJ
|
0xe
|
DEV_TRANS_ACK
|
CSM_EVENT_ISDN_TRANSFERRED
|
0xf
|
DEV_TRANS_REJECT
|
CSM_EVENT_ISDN_TRANSFER_REJ
|
Cause Values
Table 6-7 shows cause values that are assigned only to call-progressing events.
Table 6-7 Cause Values and Definitions
Hexadecimal Value
|
Cause Definitions
|
0x01
|
UNASSIGNED_NUMBER
|
0x02
|
NO_ROUTE
|
0x03
|
NO_ROUTE_DEST
|
0x04
|
NO_PREFIX
|
0x06
|
CHANNEL_UNACCEPTABLE
|
0x07
|
CALL_AWARDED
|
0x08
|
CALL_PROC_OR_ERROR
|
0x09
|
PREFIX_DIALED_ERROR
|
0x0a
|
PREFIX_NOT_DIALED
|
0x0b
|
EXCESSIVE_DIGITS
|
0x0d
|
SERVICE_DENIED
|
0x10
|
NORMAL_CLEARING
|
0x11
|
USER_BUSY
|
0x12
|
NO_USER_RESPONDING
|
0x13
|
NO_USER_ANSWER
|
0x15
|
CALL_REJECTED
|
0x16
|
NUMBER_CHANGED
|
0x1a
|
NON_SELECTED_CLEARING
|
0x1b
|
DEST_OUT_OF_ORDER
|
0x1c
|
INVALID_NUMBER_FORMAT
|
0x1d
|
FACILITY_REJECTED
|
0x1e
|
RESP_TO_STAT_ENQ
|
0x1f
|
UNSPECIFIED_CAUSE
|
0x22
|
NO_CIRCUIT_AVAILABLE
|
0x26
|
NETWORK_OUT_OF_ORDER
|
0x29
|
TEMPORARY_FAILURE
|
0x2a
|
NETWORK_CONGESTION
|
0x2b
|
ACCESS_INFO_DISCARDED
|
0x2c
|
REQ_CHANNEL_NOT_AVAIL
|
0x2d
|
PRE_EMPTED
|
0x2f
|
RESOURCES_UNAVAILABLE
|
0x32
|
FACILITY_NOT_SUBSCRIBED
|
0x33
|
BEARER_CAP_INCOMPAT
|
0x34
|
OUTGOING_CALL_BARRED
|
0x36
|
INCOMING_CALL_BARRED
|
0x39
|
BEARER_CAP_NOT_AUTH
|
0x3a
|
BEAR_CAP_NOT_AVAIL
|
0x3b
|
CALL_RESTRICTION
|
0x3c
|
REJECTED_TERMINAL
|
0x3e
|
SERVICE_NOT_ALLOWED
|
0x3f
|
SERVICE_NOT_AVAIL
|
0x41
|
CAP_NOT_IMPLEMENTED
|
0x42
|
CHAN_NOT_IMPLEMENTED
|
0x45
|
FACILITY_NOT_IMPLEMENT
|
0x46
|
BEARER_CAP_RESTRICTED
|
0x4f
|
SERV_OPT_NOT_IMPLEMENT
|
0x51
|
INVALID_CALL_REF
|
0x52
|
CHAN_DOES_NOT_EXIST
|
0x53
|
SUSPENDED_CALL_EXISTS
|
0x54
|
NO_CALL_SUSPENDED
|
0x55
|
CALL_ID_IN_USE
|
0x56
|
CALL_ID_CLEARED
|
0x58
|
INCOMPATIBLE_DEST
|
0x5a
|
SEGMENTATION_ERROR
|
0x5b
|
INVALID_TRANSIT_NETWORK
|
0x5c
|
CS_PARAMETER_NOT_VALID
|
0x5f
|
INVALID_MSG_UNSPEC
|
0x60
|
MANDATORY_IE_MISSING
|
0x61
|
NONEXISTENT_MSG
|
0x62
|
WRONG_MESSAGE
|
0x63
|
BAD_INFO_ELEM
|
0x64
|
INVALID_ELEM_CONTENTS
|
0x65
|
WRONG_MSG_FOR_STATE
|
0x66
|
TIMER_EXPIRY
|
0x67
|
MANDATORY_IE_LEN_ERR
|
0x6f
|
PROTOCOL_ERROR
|
0x7f
|
INTERWORKING_UNSPEC
|
Call Scenarios for the POTS Dial Feature
This section describes three call scenarios and shows examples of the Cisco IOS command output for each scenario. The output examples for the debug and disconnect commands show the sequence of events that occur during a POTS dial call.
Call Scenario 1
In this call scenario, port 1 is on-hook, the application dial is set to call 4085552221, and the far end successfully connects. The following example shows the Cisco IOS command:
router# test pots 1 dial 4085552221#
The following screen output shows an event indicating that port 1 is being used by the dial application:
The following screen output shows events indicating that the CSM is receiving the application digits of the number to dial:
01:58:27: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
01:58:27: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
01:58:27: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
01:58:27: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
01:58:27: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
01:58:27: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
01:58:27: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
01:58:27: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
01:58:27: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
01:58:27: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
The following screen output shows that the telephone connected to port 1 is off hook:
01:58:39: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_OFFHOOK, call id = 0x0, port = 1
The following screen output shows a call-proceeding event pair indicating that the router ISDN software has sent the dialed digits to the ISDN switch:
01:58:40: EVENT_FROM_ISDN:dchan_idb=0x280AF38, call_id=0x8004, ces=0x1 bchan=0x0,
event=0x3, cause=0x0
01:58:40: CSM_PROC_ENBLOC_DIALING: CSM_EVENT_ISDN_PROC, call id = 0x8004, port = 1
The following screen output shows the call-progressing event pair indicating that the telephone at the far end is ringing:
01:58:40: EVENT_FROM_ISDN:dchan_idb=0x280AF38, call_id=0x8004, ces=0x1 bchan=0xFFFFFFFF,
event=0x5, cause=0x0
01:58:40: CSM_PROC_ENBLOC_DIALING: CSM_EVENT_ISDN_CALL_PROGRESSING, call id = 0x8004, port
= 1
The following screen output shows a call-connecting event pair indicating that the telephone at the far end has answered:
01:58:48: EVENT_FROM_ISDN:dchan_idb=0x280AF38, call_id=0x8004, ces=0x1 bchan=0xFFFFFFFF,
event=0x4, cause=0x0
01:58:48: CSM_PROC_CONNECTING: CSM_EVENT_ISDN_CONNECTED, call id = 0x8004, port = 1
The following screen output shows a call-progressing event pair indicating that the telephone at the far end has hung up, and the calling telephone is receiving an in-band tone from the ISDN switch:
01:58:55: EVENT_FROM_ISDN:dchan_idb=0x280AF38, call_id=0x8004, ces=0x1 01:58:55:
CSM_PROC_CONNECTED: CSM_EVENT_ISDN_CALL_PROGRESSING,
call id = 0x8004, port = 1
The following screen output shows that the telephone connected to port 1 has hung up:
01:58:57: CSM_PROC_CONNECTED: CSM_EVENT_VDEV_ONHOOK, call id = 0x8004, port = 1
The following screen output shows an event pair indicating that the call has been terminated:
01:58:57: EVENT_FROM_ISDN:dchan_idb=0x280AF38, call_id=0x8004, ces=0x1 bchan=0xFFFFFFFF,
event=0x0, cause=0x0
01:58:57: CSM_PROC_NEAR_END_DISCONNECT: CSM_EVENT_ISDN_DISCONNECTED, call id = 0x8004,
port = 1
Call Scenario 2
In this scenario, port 1 is on-hook, the application dial is set to call 4085552221, and the destination number is busy. The following example shows the Cisco IOS command:
router# test pots 1 dial 4085552221#
The following screen output shows that your dial application is using port 1:
01:59:42: CSM_PROC_IDLE: CSM_EVENT_VDEV_APPLICATION_CALL, call id = 0x0, port = 1
The following screen output shows the events indicating that the CSM is receiving the application digits of the number to call:
01:59:42: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id =
0x0, port = 1
01:59:42: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
01:59:42: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
01:59:42: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
01:59:42: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
01:59:42: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
01:59:42: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
01:59:42: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
01:59:42: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
01:59:42: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
The following screen output shows an event indicating that the telephone connected to port 1 is off-hook:
01:59:52: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_OFFHOOK, call id = 0x0, port = 1
The following screen output shows a call-proceeding event pair indicating that the telephone at the far end is busy:
01:59:52: EVENT_FROM_ISDN:dchan_idb=0x280AF38, call_id=0x8005, ces=0x1 bchan=0x0,
event=0x3, cause=0x11
01:59:52: CSM_PROC_ENBLOC_DIALING: CSM_EVENT_ISDN_PROC, call id = 0x8005, port = 1
The following screen output shows a call-progressing event pair indicating that the calling telephone is receiving an in-band busy tone from the ISDN switch:
01:59:58: EVENT_FROM_ISDN:dchan_idb=0x280AF38, call_id=0x8005, ces=0x1 bchan=0xFFFFFFFF,
event=0x5, cause=0x0
01:59:58: CSM_PROC_ENBLOC_DIALING: CSM_EVENT_ISDN_CALL_PROGRESSING, call id = 0x8005, port
= 1
The following screen output shows an event indicating that the calling telephone has hung up:
02:00:05: CSM_PROC_ENBLOC_DIALING: CSM_EVENT_VDEV_ONHOOK, call id = 0x8005, port = 1
The following screen output shows an event pair indicating that the call has terminated:
02:00:05: EVENT_FROM_ISDN:dchan_idb=0x280AF38, call_id=0x8005, ces=0x1 bchan=0xFFFFFFFF,
event=0x0, cause=0x0
02:00:05: CSM_PROC_NEAR_END_DISCONNECT: CSM_EVENT_ISDN_DISCONNECTED, call id = 0x8005,
port = 1
Call Scenario 3
In this call scenario, port 1 is on-hook, the application dial is set to call 4086661112, the far end successfully connects, and the command test pots disconnect terminates the call.
router# test pots 1 dial 4086661112
The following screen output follows the same sequence of events as shown in Call Scenario 1:
1d03h: CSM_PROC_IDLE: CSM_EVENT_VDEV_APPLICATION_CALL, call id = 0x0, port = 1
1d03h: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
1d03h: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
1d03h: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
1d03h: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
1d03h: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
1d03h: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
1d03h: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
1d03h: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
1d03h: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
1d03h: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
1d03h: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_OFFHOOK, call id = 0x0, port = 1
1d03h: EVENT_FROM_ISDN:dchan_idb=0x2821F38, call_id=0x8039, ces=0x1
bchan=0x0, event=0x3, cause=0x0
1d03h: CSM_PROC_ENBLOC_DIALING: CSM_EVENT_ISDN_PROC, call id = 0x8039, port = 1
1d03h: EVENT_FROM_ISDN:dchan_idb=0x2821F38, call_id=0x8039, ces=0x1
bchan=0xFFFFFFFF, event=0x5, cause=0x0
1d03h: CSM_PROC_ENBLOC_DIALING: CSM_EVENT_ISDN_CALL_PROGRESSING, call id = 0x8039,
port = 1
router# test pots 1 disconnect
The test pots disconnect command disconnects the call before you have to put the telephone back on hook.
1d03h: CSM_PROC_CONNECTING: CSM_EVENT_VDEV_APPLICATION_HANGUP_CALL, call id = 0x8039,
port = 1
1d03h: EVENT_FROM_ISDN:dchan_idb=0x2821F38, call_id=0x8039, ces=0x1
bchan=0xFFFFFFFF, event=0x0, cause=0x0
1d03h: CSM_PROC_DISCONNECTING: CSM_EVENT_ISDN_DISCONNECTED, call id = 0x8039,
port = 1
1d03h: CSM_PROC_DISCONNECTING: CSM_EVENT_TIMEOUT, call id = 0x8039, port = 1
Cisco 813 Router Enhanced Voice Features
(Japan Only)
The Cisco 813 router supports the enhanced voice features in addition to the standard voice features of the Ciso 800 series routers. The enhanced voice features were developed to work with the INS-NET-64 switch used by Nippon Telephone and Telegraph (NTT).
Support for these features is limited to Japanese telephones, with the exception of the call blocking on caller ID feature. For more information about each feature, see the following topics:
•
General Requirements and Restrictions
•
Caller ID Display
•
Call Blocking on Caller ID
•
Local Call Waiting
•
E Ya Yo
•
Voice Warp
•
Voice Select Warp
•
Nariwake
•
Trouble-Call Blocking
•
I Number
General Requirements and Restrictions
The following is a list of requirements for activating the enhanced voice features on the Cisco 813 router:
•
Subscription to the NTT INS-NET-64 switch type.
•
Configuration of the router telephone ports to the Japanese standards by using the Cisco IOS command pots country jp.
Caller ID Display
This feature displays the caller ID information provided by the INS-NET-64 switch on analog telephones connected to the PHONE 1 or 2 port of the Cisco 813 router.
Requirements for Activating Caller ID Display
The following is a list of requirements for activating this feature:
•
Subscription to the caller ID service
•
Subscription to the INS-NET-64 switch
•
Configuration of the router using the Cisco IOS command pots country jp
Note
The caller ID display feature works only on Japanese language display telephones.
Configuring Caller ID Display
By default, this feature is disabled. To configure this feature, use the Cisco IOS caller-id enable command in the dial-peer configuration command mode.
Call Blocking on Caller ID
This feature can reject an incoming voice call based on the caller ID information presented to the Cisco 813 router from the INS-NET-64 switch. This feature can block calls for up to ten caller IDs for each local directory number (LDN).
Requirements for Activating Call Blocking on Caller ID
The following requirements must be met before activating this feature:
•
Subscription to the caller ID service on the INS-NET-64 switch. If this feature is enabled on the router without the caller ID subscription, the router will neither verify telephone numbers from callers nor block their calls.
•
Configuration of the router using the Cisco IOS command pots country jp.
Configuring Call Blocking on Caller ID
By default, this feature is disabled. To configure this feature, use the Cisco IOS block-caller command in the dial-peer configuration command mode.
where number is the telephone number to block. You can use a period (.) as a wildcard to substitute for one or more numbers to block. For example, to block all numbers ending in the number 5, you can enter the following:
You can enter up to ten caller ID numbers for each LDN. However, you cannot exceed the maximum of ten numbers. You must remove one or more numbers before you can add any new numbers to block.
If no caller ID numbers are specified for a particular LDN, all voice calls to that LDN are accepted.
Example of Caller ID Blocking Configuration
The following example configures the router to block calls from the caller whose caller ID number is 4085551234:
router(config)# pots country jp
router(config)# dial-peer voice 1 pots
router(config-dial-peer)# block-caller 4085551234
Example of Caller ID Blocking Output
To display caller IDs entered for call blocking, use the show run command. The following is an example of caller ID configuration output:
no forward-to-unused-port
Local Call Waiting
This feature notifies you of an incoming call while you are connected to an external telephone call (by issuing a call waiting tone). You can choose to place the first call on hold by pressing flash, connect to the second call, then return to the first call after finishing with the second.
Local call waiting on the Cisco 813 router differs from standard ISDN call waiting in that this enhanced voice feature does not require a subscription to call waiting from the service provider. This feature uses both B channels of the ISDN line, enabling local call waiting support on the router rather than from the service provider.
This feature is not supported if any of the interactive voice response (IVR) features (such as voice warp, voice select warp, and Nariwake) are in use.
Requirements for Activating Local Call Waiting
The following requirements must be met before activating this feature:
•
Subscription to any telephone service provider switch
•
Configuration of the router using the Cisco IOS command pots country jp
Configuring Local Call Waiting
To configure this feature, use the Cisco IOS pots call-waiting command:
pots call-waiting [local|remote]
The call waiting defaults to remote if this feature is not configured. In that case, the call holding pattern follows the settings of the service provider rather than those of the router.
To display the call waiting setting, use the show run or show pots status command.
Note
The ISDN call waiting service will be used if it is available on the ISDN line connected to the router even if local call waiting is configured on the router. If ISDN call waiting is used, the local call waiting configuration on the router is ignored.
Example of Local Call Waiting Configuration
The following example configures the call waiting style to follow the local call holding pattern that is set on the router:
router(config)# pots country jp
router(config)# pots call-waiting local
E Ya Yo
This feature conceals the caller ID of the outgoing call from the receiving device.
Requirements for Activating E Ya Yo
The following requirements must be met before activating this feature:
•
Subscription to the E Ya Yo service
•
Subscription to the INS-NET-64 switch
•
Configuration of the router using the Cisco IOS command pots country jp
Configuring E Ya Yo
According to the NTT specification, dialing the prefix 184 followed by the destination device number will render your caller ID invisible to the receiving party.
Voice Warp
The voice warp feature on the INS-NET-64 switch forwards all incoming calls for a terminal device to another device. Voice warp registration, activation, and deactivation requests are sent to the switch for each LDN. The Cisco 813 router supports the registration, activation, and deactivation requests for any device attached to the PHONE 1 or 2 port. The forwarding function itself is performed by the INS-NET-64 switch.
During the registration phase of the device, you can:
•
Create a list of forwarding destination numbers and to select one as the active destination.
•
Specify whether an announcement will be made to the caller or forwarding device, or both, at the time the call is forwarded.
•
Set the no-answer timer parameter from 5 to 60 seconds at 5-second intervals. This setting affects the redirection of calls once the voice warp feature is activated.
During the activation phase of this feature, you determine whether calls are redirected all the time or only if the receiving device is busy or does not answer within the no-answer time period specified during registration.
This feature can be deactivated after its registration and activation phases.
Note
The Cisco 813 router supports this feature for one LDN only. If more than one LDN is configured, only the primary LDN can be used with this feature.
Requirements for Activating Voice Warp
The following requirements must be met before activating this feature:
•
Subscription to the voice warp and caller ID services
•
Subscription to the INS-NET-64 switch
•
Configuration of the router using the Cisco IOS command pots country jp
Note
Activating the voice warp feature disables the support for the call waiting feature for both local and network calls.
Configuring Voice Warp
This feature is configured using the interface on the telephone as specified in the NTT user manual.
To hear the voice warp registration details of a device, use the keypad dialing sequence specified in the NTT user manual. Information is transmitted only by voice.
Voice Select Warp
This feature is an enhanced version of the voice warp feature. You can create a list of incoming caller IDs that is used in call redirection, either by redirecting incoming calls only from matching caller IDs, or by redirecting all calls except those from matching caller IDs.
Note
The Cisco 813 router supports this feature for one LDN only. If more than one LDN is configured, only the primary LDN can be used with this feature.
Requirements for Activating Voice Select Warp
The following requirements must be met before activating this feature:
•
Subscription to the voice select warp and caller ID services
•
Subscription to the INS-NET-64 switch
•
Configuration of the router using the Cisco IOS command pots country jp
Note
Activating the voice select warp feature disables the support for the call waiting feature for both local and network calls.
Configuring Voice Select Warp
This feature is configured using the interface on the telephone as specified in the NTT user manual.
To get voice warp registration details of a device, use the keypad dialing sequence specified in the NTT user manual. Information is transmitted only by voice.
Nariwake
Nariwake checks for caller IDs that you register for each LDN and presents a distinctive ring to the telephone port receiving the incoming call if a match is detected. The Cisco 813 router provides three different ring cadences that you can set for calls from registered and unregistered callers. The number of caller IDs you can register for each LDN at one time is defined by the INS-NET-64 switch and not by the router.
You can register this feature with the list of caller IDs for each LDN, cancel the registration for the LDN, or get registration information from the INS-NET-64 switch.
Note
The Cisco 813 router supports this feature for one LDN only. If more than one LDN is configured, only the primary LDN can be used with this feature.
Requirements for Activating Nariwake
The following requirements must be met before activating this feature:
•
Subscription to the Nariwake feature
•
Subscription to the INS-NET-64 switch
•
Configuration of the router using the Cisco IOS command pots country jp
Note
Activating the Nariwake feature disables support for the call waiting feature for both local and network calls.
Configuring Nariwake
To configure the ring cadence for this feature, use the registered-caller ring command in the dial-peer configuration mode:
registered-caller ring cadence
where cadence is a value of 0, 1, or 2. The default ring cadence for registered callers is 1 and for unregistered callers is 0.
The on/off periods of ring 0 (normal ringing signals) and ring 1 (ringing signals for the Nariwake service) are defined in the NTT user manual.
Note
If your ISDN line is provisioned for the I Number or dial-in services, you must also configure a dial-peer using the Cisco IOS command destination-pattern not-provided. Either port 1 or 2 can be configured under this dial-peer. The router will then forward the incoming call to the voice port 1 using the default cadence 0. See the "Example of Nariwake Configuration" section for details.
If more than one dial-peer is configured with destination-pattern not-provided, the router uses only the first dial-peer for the incoming calls.
To hear the caller ID registration details, use the keypad dialing sequence specified in the NTT user manual. Information is transmitted only by voice.
Example of Nariwake Configuration
The following example sets the ring cadence for registered callers to 2.
router(config)# pots country jp
router(config)# dial-peer voice 1 pots
router(config-dial-peer)# registered-caller ring 2
Add the destination-pattern not-provided command if you also subscribe to the I Number and dial-in services.
router(config-dial-peer)# destination-pattern not-provided
Example of Nariwake Configuration Output
To display the Nariwake ring cadence setting, use the show run command. The following is an example of screen output for Nariwake configuration:
no forward-to-unused-port
destination-pattern not-provided
Trouble-Call Blocking
The trouble-call blocking feature causes all future incoming calls from a particular telephone number to be rejected by the network if the recipient activates this feature after the initial call. As the recipient of the call, you are not required to specify the telephone number of the caller and will not be notified of subsequent connection attempts from that telephone number. When this feature is activated, the caller will hear a standard telephone announcement and a disconnect message. For information about the announcement or message, see your NTT user manual.
The number of callers that you can block is defined by the service provider at the time the service is provisioned. If you request an additional telephone number to block after having reached the limit, the oldest number is discarded (unblocked) before the latest telephone number is registered for blocking.
Requirements for Activating Trouble-Call Blocking
The following requirements must be met before activating this feature:
•
Subscription to the trouble-call blocking feature
•
Subscription to the INS-NET-64 switch
•
Configuration of the router using the Cisco IOS command pots country jp
Configuring Trouble-Call Blocking
You can activate, cancel, or request confirmation of the results of your trouble-call blocking by using the keypad dialing sequence specified in the NTT user manual.
Note
To activate this feature, you must dial the keypad sequence within 60 seconds after you hang up from the call. You will be notified over the telephone whether or not the activation is successful.
You can disable this feature for only the last registered number or for all numbers registered for blocking. You will be notified over the telephone whether or not the cancellation is successful.
You can request to hear the results of the trouble-call blocking. You will hear the number of attempted calls that were blocked for the past two months.
I Number
This feature supports the use of multiple terminal devices with one subscriber line. The telephone numbers of the subscriber line and router ports are assigned by the service provider. Calls coming into any of the assigned numbers will route through the same subscriber line to the terminal device attached to the target port.
Requirements for Activating I Number
The following requirements must be met before activating this feature:
•
Subscription to the I number feature
•
Subscription to the INS-NET-64 switch
•
Configuration of the router using the Cisco IOS command pots country jp
Configuring I Number
To configure this feature, perform the following steps:
Step 1
Use the isdn i-number command in the BRI interface configuration mode to configure the I number:
where number is a value from 1 to 3 (based on NTT specifications) and ldn is your local directory number configured under the dial-peer. The number variable maps the I number to one of the LDNs.
Step 2
Use the destination-pattern command to set the dial-peer destination pattern to the corresponding LDN:
Example of I Number Configuration
The following example shows screen output for two LDNs configured under interface BRI0:
router(config)# interface bri0
router(config-if)# isdn i-number 1 5551234
router(config-if)# isdn i-number 2 5556789
router(config)# dial-peer voice 1 pots
router(config-dial-peer)# destination-pattern 5551234
router(config-dial-peer)# exit
router(config)# dial-peer voice 2 pots
router(config-dial-peer)# destination-pattern 5556789
Silent Fax Calls
The silent fax calls feature enables you to configure your router port to send a silent fax tone instead of a ring alert, which is recognized by fax machines with silent fax recognition capability (Smart Fax type 2). With the silent fax feature, the fax machine does not ring but the fax call get connected. If a phone is connected instead of a fax machine, the phone will not ring.
Configuring Silent Fax Calls
To configure your telephone port as a silent fax type 2, use the Cisco IOS silent-fax command in dial-peer configuration mode:
By default, this feature is disabled.
Example of Silent Fax Calls Configuration
The following is an example of a silent fax call configuration:
router# configure terminal
router(config)# dial-peer voice 1 pots
router(config-dial-peer)# silent-fax
Example of Silent Fax Calls Configuration Output
The following is an example of the silent fax configuration output:
no forward-to-unused-port
destination-pattern 7773000
no forward-to-unused-port
destination-pattern 7773100
Supplementary Telephone Services for the Net3 Switch
The Cisco 800 series routers now support the following plain old telephone service (POTS) features for the European Telecommunications Standards Institute (ETSI) Net3 switch type:
•
Caller ID presentation and restriction are available for Denmark and Finland. For more information, see the "Configuring Caller ID for the Net3 Switch" section.
•
Calling line identification restriction (CLIR) temporarily prevents your calling ID from being presented to the destination number for an outgoing call. You must configure CLIR before each call that you wish to restrict.
•
Call forwarding is enabled by using Cisco IOS and dual tone multifrequency (DTMF) commands. For more information, see the "Call Forwarding for the Net3 Switch" section.
•
Call transfer enables you to connect two call destinations. The request for this service must originate from an active, outgoing call.
Requirements for Supplementary Telephone Services Support
You must subscribe to the following Net3 switch services for these supplementary telephone services to work:
•
Calling line identification presentation (CLIP)
•
CLIR in temporary mode
•
Call holding
•
Call transfer
•
Call forwarding
•
Call waiting
Configuring Caller ID for the Net3 Switch
To enable caller ID on the Net3 switch, configure the country type by using the Cisco IOS pots country command in global configuration mode:
Note
Caller ID for the Net3 switch is always enabled, provided that the POTS country type is correctly defined. Caller ID cannot be disabled using the Cisco IOS command-line interface (CLI).
To verify whether caller ID is enabled, use the show pots status command. The following is an example of the output from that command:
POTS Global Configuration:
Dialing Method:Overlap, Tone Source:Local, CallerId Support:YES
Call Forwarding for the Net3 Switch
The following types of call forwarding services (for voice calls only) are supported on the Net3 switch:
•
Call forward unconditional (CFU) redirects your calls without restrictions and takes precedence over other call forwarding types.
•
Call forward busy (CFB) redirects your call to another number if your number is busy.
•
Call forward no reply (CFNR) forwards your call to another number if your number does not answer within a specified period of time.
You can select one or more call forwarding services at a time. However, CFU has the highest precedence, CFB the next highest, and CFNR the lowest. The default setting is that no forwarding type is selected.
Note
If you had configured call forwarding for a POTS port and the router finds that a dial peer is also configured for that port, call forwarding works only for the number defined in the destination-pattern dial-peer command and ignores all other numbers for that telephone. If the router does not find a dial peer, or if the destination pattern is not defined, call forwarding works for all numbers allocated to the ISDN line.
To enable and configure this feature, follow these steps:
Step 1
Enable and select the call forwarding method. See the "Configuring the Call Forwarding Method" section.
Step 2
Configure your call forwarding service, depending on which method you previously selected:
•
Functional method—Enter DTMF commands on the telephone keypad. For more information, see the "Configuring the Call Forwarding Service" section.
•
Keypad method—Follow the instructions in your Net3 switch documentation.
Configuring the Call Forwarding Method
You can select the method by which the call forwarding feature is controlled:
•
Functional method gives control to the router. If you select this method, use the DTMF commands documented in the "Configuring the Call Forwarding Service" section.
•
Keypad method gives control to the Net3 switch.
To enable the call forwarding method, use the Cisco IOS pots forwarding-method command in global configuration mode:
pots forwarding-method {functional | keypad}
no pots forwarding-method
Note
Use the pots forwarding-method command to configure only Net3 switch types. This command does not work for other switch types. This feature is disabled in the default setting.
The following example configures the call forwarding feature to give control to the router:
router# configure terminal
router(config)# pots forwarding-method functional
Configuring the Call Forwarding Service
Table 6-8 shows the DTMF keypad command sequence that you enter to configure the call forwarding service.
Table 6-8 Configuring the Call Forwarding Service
Task
|
DTMF Keypad Command
|
Activate CFU
|
where number is the telephone number to which your calls are forwarded
|
Deactivate CFU
|
|
Activate CFNR
|
where number is the telephone number to which your calls are forwarded
|
Deactivate CFNR
|
|
Activate CFB
|
where number is the telephone number to which your calls are forwarded
|
Deactivate CFB
|
|
You should hear a dial tone after you enter the DTMF commands if the call forwarding service is successfully configured. If you hear a busy signal, the command is invalid or the switch does not support that service.
Displaying POTS Status
Use the show pots status command to display details of the call forwarding type. This status is not stored when you reboot. The following is an example of the screen output:
POTS Global Configuration:
Dialing Method:Overlap, Tone Source:Local, CallerId Support:YES
Forwarding Method:functional method
-------------------------------------
The Forwarding Method Enabled is CFU
The forwarded to Address is :33236877
The served user Number(s) are :33795742
The Forwarding Method Enabled is CFB
The forwarded to Address is :33236877
The served user Number(s) are :
ALL -> Will work for all numbers allocated to the terminal.
Configuring CLIR
Configure CLIR by following these steps:
Step 1
Ensure that CLIR in temporary mode is enabled in the Net3 switch.
Step 2
Remove the handset and enter **31# on the keypad.
Step 3
Listen for the dial tone, and make your call.
Step 4
Repeat Steps 2 and 3 for each outgoing call for which you wish to restrict your calling identification.
Debug POTS Commands
Use the following commands to debug problems with caller ID configuration:
•
debug pots driver
•
debug pots csm
Use the following commands for problems configuring other supplementary telephone features:
•
debug pots csm
•
debug isdn event
•
debug isdn q931
For more information about using debug commands, refer to the Cisco IOS documentation.
Cisco 804 and 813 Routers Enhanced Voice Features
The Cisco 804 and 813 routers support the following enhanced voice features. For information on each feature, see the following topic:
•
Prefix Dialing
•
Calling Between Telephone Ports
•
Redial
•
Call Transfer
•
Volume Adjustments
•
Distinctive Ringing Based on Caller ID
•
Subaddresses for POTS Ports
•
Caller ID on the Cisco 813 Router
Prefix Dialing
Cisco 803 and Cisco 804 routers support prefix dialing. You can add a telephone prefix and create a prefix filter to the dialed number for analog telephone calls. When a telephone number is dialed through the telephone port, the router checks for prefix filters. If the router finds a match, no prefix is added to the dialed number. If no filter match is found, the router adds the user-defined prefix to the called number.
Configuring a Prefix Number
To set a prefix to be added to a telephone number called, use the Cisco IOS pots prefix number command in global configuration mode:
pots prefix number number
where number is a prefix number from 1 to 5 digits in length. Only one prefix can be configured at a time, and configuring a new number will overwrite the existing one.
The following example sets the prefix number to 12345:
router# configure terminal
router(config)# pots prefix number 12345
Configuring a Prefix Filter
You can configure a prefix filter that is compared to the digits that you dial. If a match occurs, the prefix number is not added to the called number. To create a prefix filter, use the pots prefix filter command in global configuration mode:
pots prefix filter number
no pots prefix filter number
where number is a prefix filter from 1 to 8 digits in length. You can define up to ten filters for your router. If you have reached the maximum number of filters defined, no new filter configurations are accepted until you remove at least one existing filter number using the no pots prefix filter number command.
The following are examples of how to set prefix filters:
router# configure terminal
router(config)# pots prefix filter 192
router(config)# pots prefix filter 1
router(config)# pots prefix filter 9
router(config)# pots prefix filter 0800
router(config)# pots prefix filter 08456
Calling Between Telephone Ports
The calling between telephone ports voice feature enables a connection between the two telephone ports of your router. This voice call is handled by the router and does not affect any data calls handled on the B channels. However, the following restrictions apply:
•
During a call between ports, an incoming voice call cannot supersede the data calls. The router sends a disconnect message to the network for incoming voice calls.
•
If voice priority is set on the router and two data calls are in progress, an attempted call between ports takes precedence over one of the data calls. This applies to the overlap mode of dialing.
•
The call waiting tone is not activated for the local telephone ports even if call waiting is enabled locally or at the switch. An external calling party hears a busy tone if the telephone ports are engaged.
Activating the Calling Between Telephone Ports Feature
To make a call between telephone ports, press **0# on your telephone handset.
Calling Between Telephone Ports Scenarios
Table 6-9 shows scenarios for calling between telephone ports.
Table 6-9 Scenarios for Calling Between Telephone Ports
POTS 1
|
POTS 2
|
B1 Channel
|
B2 Channel
|
Command
|
Result
|
IDLE
|
IDLE
|
Free
|
Free
|
Press **0# from POTS 1 or POTS 2
|
Intercom call is established.
|
IDLE
|
IDLE
|
Data call in progress
|
Free
|
Press **0# from POTS 1 or POTS 2
|
Intercom call is established.
|
IDLE
|
IDLE
|
Data call in progress
|
Data call in progress
|
Press **0# from POTS 1 or POTS 2
|
Intercom call is established. But in overlap mode, one data call is bumped
|
IDLE
|
IDLE
|
Data call in progress
|
Data call in progress
|
Press **0# from POTS 1 or POTS 2
|
Intercom call is established successfully in enblock mode. User gets busy tone in overlap mode.
|
IDLE
|
IDLE
|
Data call in progress
|
Data call in progress
|
Press **0# from POTS 1 or POTS 2
|
Telephone port call is established successfully in enblock mode. In overlap mode, if both the calls aredestined for same location, then one data call is bumped to establish the intercom mode successfully. Otherwise, the user at POTS 1 or 2 hears a busy tone.
|
Intercom
|
Intercom
|
Free
|
Free
|
Press flash and any key at POTS 1
|
During the intercom call flashhook/keys is not detected.
|
Intercom
|
Intercom
|
Free/data call
|
Free/data call
|
An external voice call comes to POTS 1
|
No call waiting tone is generated and the external user hears a busy tone. Data calls are not bumped.
|
IDLE
|
External voice call
|
Voice call
|
Free
|
Press **0# from POTS 1
|
Intercom fails and user hears a busy tone.
|
IDLE
|
External voice call
|
Voice call
|
Data call in progress
|
Press **0# from POTS 1
|
Intercom fails and the user hears a busy tone. In overlap mode, the data call is bumped.
|
IDLE
|
External voice call
|
Voice call
|
Data call in progress
|
Press **0# from POTS 1
|
Intercom fails and the user hears a busy tone.
|
Redial
This feature enables you to redial the last number called on either telephone
port 1 or 2. The following conditions apply:
•
This feature recalls only the last digits dialed, to a maximum of 65.
•
The router does not store feature access codes starting with an asterisk (*), interactive voice response (IVR) digits, or the pound (#) key.
Activating the Redial Feature
To redial the last number called, press **4# on your telephone handset.
Redial Feature Scenarios
Table 6-10 shows scenarios for the redial feature.
Table 6-10 Scenarios for Redial Feature
Event/Condition
|
Command
|
Result
|
User dialed external number from POTS 1 or POTS 2.
|
Press **4# from POTS 1 or POTS 2.
|
The last number dialed from POTS port 1 or POTS port 2 is called again.
|
User invoked a DTMF function for POTS 1 or POTS 2 on a per call basis and then pressed the actual number for a dialing connection.
|
Press **4# from POTS 1 or POTS 2.
|
Only the actual called number gets redialed and not the input for the DTMF function.
|
The previous call was between POTS ports on the same router. Now the user dials the required digits for IVR.
|
Press **4# from POTS 1 or POTS 2
|
No number is stored for redial. No number is dialed, and the user only hears a dial tone.
|
Call Transfer
The call transfer feature enables you to transfer an external call from one telephone port to the other. Call transfer does not require any subscription from the switch.
Activating the Call Transfer Feature
To transfer an incoming voice call from one port to another, press the flash hook switch, then **0# on the telephone handset.
Call Transfer Feature Scenarios
Table 6-11 shows scenarios for call transfer.
Table 6-11 Scenarios for Call Transfer
Event/Condition
|
Called Port
|
Command
|
Result
|
External caller dialed POTS 1 or POTS 2 port and the user decides to transfer the call to the other port.
|
IDLE
|
Press flash hook switch and **0# from POTS 1 or POTS 2.
|
The connection is established between the external caller and POTS 1 or POTS 2 when the handset connected to the other POTS port goes to onhook.
|
External caller dialed POTS 1 or POTS 2 port. POTS 1 or POTS 2 decides to transfer the call to the other port, but that port is busy with a call.
|
BUSY
|
Press FLASH **0# from POTS 1 or POTS 2.
|
No connection is established between POTS 1 and POTS 2. The connection between the external call and called POTS port is still valid, so the user can resume conversation with the external called by pressing FLASH.
|
External caller dialed POTS 1 or POTS 2. The user decides to transfer the call to the other port and keep the phone on hook without checking the availability of the port.
|
IDLE
|
Press FLASH **0# from POTS 1 or POTS 2
|
This is an example of an unsupervised call and is not supported. No connection will be made between the external caller and the port to which they are being transferred.
|
Volume Adjustments
The volume adjustment features enables you to adjust the receiver volume of the POTS ports.
To configure the telephone receiver volume on each port, use the Cisco IOS volume command in the dial-peer configuration mode:
where number is a numeric value from 1 to 5 representing the volume setting
ranging from -12 to 0 decibels (dB). The default setting is 3.
Table 6-12 lists the values and definitions of the number variable.
Table 6-12 Volume Adjustment Number Variable Definitions
Number
|
Volume Setting in dB
|
1
|
-12
|
2
|
-9
|
3
|
-6
|
4
|
-3
|
5
|
0
|
Volume Adjustment Configuration Example
The following example configures the volume of the receiver on the router telephone ports 1 and 2:
router# configure terminal
router(config)# dial-peer voice 1 pots
router(config-dial-peer)# volume 4
router(config-dial-peer)# dial-peer voice 2 pots
router(config-dial-peer)# volume 2
Volume Adjustment Configuration Output Example
The following is an example of the volume adjustment configuration output from the show running-config command:
destination-pattern 5551111
destination-pattern 5552222
Distinctive Ringing Based on Caller ID
The distinctive ringing feature enables you to configure the ring cadence for incoming calls based on the caller ID. You can choose from three ring cadences to associate with each telephone number and store up to twenty numbers per dial peer. You can configure a total of six dial peers but only one dial peer per port can be active at one time.
Note
The distinctive ringing feature does not require subscription to any special service on the ISDN switch. However, if the Nariwake subscription is already active, then Nariwake takes precedence over this feature.
Configuring Distinctive Ringing Based on Caller ID
To enable and configure distinctive ringing based on caller ID, use the following Cisco IOS command in dial-peer configuration mode:
caller number ring cadence
no caller number ring cadence
where number is the caller ID number of the incoming call, and cadence is the setting for ring cadence and duration. By default, this feature is disabled.
If you have configured the maximum number of twenty per dial peer, disable the numbers by using the no caller number ring cadence command.
Table 6-13 shows the available ring cadence settings.
Table 6-13 Ring Cadence Settings
Cadence
|
Description
|
1
|
1 sec on, 2 sec off (NTT defined regular ring)
|
2
|
0.25 sec on, 0.2 sec off, 0.25 sec on, 2.3 sec off (NTT defined non-regular ring)
|
3
|
0.5 sec on, 0.25 sec off, 0.25 sec on, 2 sec off (Cisco defined non-regular ring)
|
Distinctive Ringing Scenarios
Table 6-14 shows scenarios for distinctive ringing.
Table 6-14 Scenarios for Distinctive Ringing
Condition
|
Event
|
Result
|
ISDN line is provisioned with Nariwake service. The user sets the same caller ID number that is set for Nariwake to distinctive ringing supported locally at the router.
|
An incoming voice call comes from the configured caller ID for POTS 1 or POTS 2.
|
The Nariwake service takes precedence over distinctive ringing based on caller ID.
The user at POTS 1 or POTS 2 hears the same ring cadence as that of the Nariwake service.
|
User configures distinctive ringing for POTS 1 or POTS 2, based on caller ID supported locally by the router. The user also sets the country group, which has a different ring cadence.
|
An incoming voice call comes from the caller ID number configured for POTS 1 or POTS 2.
|
Distinctive ringing takes precedence over the ring cadence set by the pots country group command.
The incoming call rings at POTS 1 or POTS 2 with the ring cadence specified in distinctive ringing based on caller ID.
|
User configures distinctive ringing based on caller ID supported locally by the router for POTS 1 or POTS 2. The user also configures a different ring cadence for the port by entering the ring command.
|
An incoming voice call comes from that caller ID number configured for POTS 1 or POTS 2.
|
Distinctive ringing based on caller ID takes precedence over the ring cadence set by the ring command.
The incoming call rings at POTS 1 or POTS 2 with the ring cadence specified in the distinctive ringing based on caller ID.
|
Distinctive Ringing Configuration Example
The following is an example of the distinctive ringing configuration:
cisco801# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
cisco801#(config)#dial-peer voice 1 pots
cisco801#(config-dial-peer)#caller-number 11111 ring 1
cisco801#(config-dial-peer)#caller-number 22222 ring 2
cisco801#(config-dial-peer)#caller-number 33333 ring 1
Distinctive Ringing Configuration Output Example
The following is an example of the output for the distinctive ringing feature from the show running-config command:
!
no forward-to-unused-port
caller-number 11111 ring 1
caller-number 22222 ring 2
caller-number 33333 ring 1
no forward-to-unused-port
caller-number 11111 ring 1
caller-number 33333 ring 1
caller-number 22222 ring 2
Subaddresses for POTS Ports
The subaddressing feature enables you to assign an ISDN subaddress to each POTS port so that an external call can be directly connected to the number dialed.
Configuring Subaddresses for POTS Ports
To configure the subaddress for a POTS port, use the Cisco IOS subaddress command in dial-peer configuration mode:
where number is the subaddress of a POTS port. Only one subaddress can be configured for each port. By default, no subaddresses are configured.
Subaddressing Scenarios
Table 6-15 shows scenarios for subaddresses for a POTS port.
Table 6-15 Subaddress Scenarios
Condition
|
Event
|
Result
|
User configures a destination pattern and a subaddress in a POTS 1 or POTS 2 dial peer.
|
An external voice call comes in with a called number and subaddress to the router.
|
The router accepts the incoming call and routes it to POTS or POTS 2 if the called number matches the destination pattern configured for the POTS dial peer.
|
User configures a destination pattern and subaddress in a POTS 1 or POTS 2 dial peer.
|
An external voice call comes in with a subaddress to the router but without a called number.
|
The router accepts the incoming call and routes it to POTS 1 or POTS 2 if the subaddress matches the subaddress configured for the POTS dial peer. This happens in the case of a point-to-point ISDN line.
|
User configures only the subaddress in a POTS 1 or POTS 2 dial peer.
|
An external voice call comes in with a subaddress to the router.
|
The router accepts the incoming call and routes it to POTS 1 or POTS 2 if the subaddress matches the subaddress configured for the POTS dial peer. This happens in the case of a point-to-point ISDN line.
|
User configures only the destination pattern in a POTS 1 or POTS 2 dial peer and doesn't configure a subaddress for any of the POTS ports.
|
An external voice call comes in with a called number and a subaddress to the router.
|
The router accepts the incoming call and routes it to POTS 1 or POTS 2 if the subaddress matches the subaddress configured for the POTS dial peer.
|
Subaddressing Configuration Example
The following is an example of the subaddresses configuration:
router# configure terminal
router(config)# dial-peer voice 1 pots
router(config-dial-peer)# destination-pattern 5551111
router(config)# dial-peer voice 2 pots
router(config-dial-peer)# destination-pattern 5552222
router(config-dial-peer)# subaddress 10
Subaddressing Configuration Output Example
The following is an example of the output for configuring subaddresses of the POTS ports:
destination-pattern 5551111
destination-pattern 5552222
Caller ID on the Cisco 813 Router
The correct information is as follows:
By default, the caller ID feature is disabled. To enable this feature, use the Cisco IOS caller-id command in the dial-peer configuration command mode.
Debug POTS Commands
Use the following commands to debug problems with caller ID configuration:
•
debug pots driver
•
debug pots csm
Use the following commands for problems configuring other supplementary telephone features:
•
debug pots csm
•
debug isdn event
•
debug isdn q931
For more information about using debug commands, refer to the Cisco IOS documentation.
Local Call Forwarding
The local call forwarding feature enables you to forward an incoming voice call to an external telephone number if that call is not answered within a certain number of ring cycles. Highlights of this feature are as follows:
•
If the telephone is picked up at the forwarded destination, the router connects the incoming call to the new destination.
•
If the forwarded destination does not pick up the call within the timeout period, the router disconnects the call.
•
If either party hangs up after a successful connection, the router disconnects the call.
Note
The call forwarding feature uses the B channels to forward the voice call and to connect the caller and the forwarded destination. If one or both B channels are busy with data calls, the incoming voice call supersedes the data calls.
Configuring Local Call Forwarding
To configure local call forwarding on your router, use the following Cisco IOS command in dial-peer configuration mode:
forward number after number of rings
no forward number after number of rings
where number is the external telephone number to forward an incoming voice call, and number of rings is the maximum number of ring cycles (from 0 to 7) before the router forwards the call. By default, this feature is disabled.
Local Call Forwarding Scenarios
Table 6-16 shows scenarios for local call forwarding:
Table 6-16 Scenarios for Local Call Forwarding
Condition
|
B1 Channel
|
B2 Channel
|
Event
|
Result
|
The feature is enabled through the command-line interface.
|
Free.
|
Free.
|
An external voice call comes in to POTS 1 or POTS 2.
|
The call is forwarded to the external destination number specified, and both B channels are busy with call forwarding. If the forwarded destination is busy, the router sends a disconnect signal to the incoming call.
|
The feature is enabled through the command-line interface.
|
Data call in progress.
|
Data call in progress.
|
An external voice call comes in to POTS 1 or POTS 2.
|
The router waits for the specified number of rings and then bumps a data call to make a call to the forwarding destination. If the forwarded destination responds with a connect, then the router bumps the second data call and connects to the incoming call. The external caller and the forwarded destination will be able to converse. If the forwarding destination is busy, the router sends a disconnect to the incoming external call and the second data call is not bumped.
|
The feature is enabled through the command-line interface.
|
Data call in progress.
|
Free.
|
An external voice call comes in to POTS 1 or POTS 2.
|
The router waits for the specified number of rings and then makes a call to the forwarding destination. If the forwarded destination responds with a connect, the router bumps the data call and connects to the external incoming call. Now the external caller and the forwarded destination will be able to converse. If the forwarding destination is busy, the router sends a disconnect to the incoming call and the existing data call is not bumped.
|
The feature is enabled through the command-line interface.
|
Voice call in progress.
|
Voice call in progress.
|
An external voice call comes in to POTS 1 or POTS 2.
|
The router waits for the specified number of rings and then verifies that both the B channels are free. If the voice call from POTS 1 or POTS 2 is active, the router sends a disconnect signal to the incoming call.
|
The feature is not enabled.
|
Local call forwarding is on.
|
Local call forwarding is on.
|
An external voice call comes in to POTS 1 or POTS 2.
|
Call waiting is not supported in this case. The router sends a disconnect signal to the incoming voice call.The caller hears a busy tone.
|
The feature is not enabled.
|
Local call forwarding is on.
|
Local call forwarding is on.
|
The user at POTS 1 or POTS 2 makes an outgoing call.
|
The user at POTS 1 or POTS 2 cannot make an external call.
|
Local Call Forwarding Configuration Example
The following is an example of configuring the local call forwarding feature:
router# configure terminal
router(config)# dial-peer voice 1 pots
router(config-dial-peer)# forward 8765432 after 0
router(config)# dial-peer voice 2 pots
router(config-dial-peer)# forward 1234567 after 3
Local Call Forwarding Configuration Output Example
The following is an example of the output for local call forwarding configuration:
destination-pattern 5551111
destination-pattern 5552222
Support for PIAFS
Personal Handy-Phone System (PHS) Internet Access Forum Standard (PIAFS) is a standard error-correction protocol for cellular data communication that is designed to pass data over the Personal Handy-Phone System (PHS) of cellular system. It also provides transmission control procedures (comparable to OSI reference model layer 2) for high-quality data transmission. Both PIAFS version 2.0 and version 2.1 are supported on the Cisco 800 series routers.
The following common applications are supported using PIAFS in PHS data communications:
•
E-mail service
This enables the user to send and receive e-mail messages. E-mail is a basic service of the PHS multimedia communications menu.
•
Fax service
This enable faxing of data stored in a Personal Digital Assistant (PDA).
•
Internet access
Internet access has influenced PHS in that many users want to be able to obtain necessary information in a timely manner when they are outdoors. It is also projected that PHS will be used extensively to form intranets for in-house communications by facilitating the expansion of office LAN access points.
•
Photograph transmission service
This service can be realized by transmitting the signals of a digital still camera directly or through the medium of a personal computer. This can be regarded as another variation of data transmission service that can use the PHS for transmission.
•
Mobile office service
The spread of groupware recently has led to frequent instances where groups share common data bases in carrying out or supporting the execution of collaborative work. There are demands to extend this collaborative environment even to outside locations through the use of mobile communications. This is made possible by the use of PHS data communications.
The Cisco 800 series routers will accept incoming PIAFS calls from a peer supporting PIAFS 2.2 and will behave as speed variable type 2 devices. The Cisco 800 series routers will not request speed change but will respond to the speed change requests from the peer. See Table 6-17 below.
Table 6-17 PIAFS Protocol for Request and Response
PIAFS Peer Request Protocol (Data Link Initiation Side)
|
800 PIAFS Subsystem Response Protocol (Data Link Reception Side)
|
Fixed speed
|
Fixed speed
|
Speed variable type 1
|
Speed variable type 2
|
Speed variable type 2
|
Speed variable type 2
|
Speed variable type 3
|
Speed variable type 2
|
The table indicates that the Cisco 800 series routers will act only as a PIAFS speed variable type 2 device for all the peers supporting PIAFS 2.2.
Configuring PIAFS
This feature is available by default in all images. It is enabled when the ISDN switch type is set to INS (NTT) and PPP encapsulation is configured on the ISDN interface.
PIAFS Scenarios
Table 6-18 shows scenarios for PIAFS. The feature is activated when the ISDN switch type is set to INS(NTT) and PPP encapsulation is configured on the ISDN interface.
Table 6-18 Scenarios for PIAFS
B1 Channel
|
B2 Channel
|
Event
|
Result
|
Free
|
Free
|
An incoming PIAFS call comes in to the router.
|
The router negotiates the data transmission protocol and accepts the PIAFS call. The PIAFS peer runs the PHS application.
|
Data or voice call in progress
|
Free
|
An incoming PIAFS call comes in to the router.
|
The router negotiates the data transmission protocol and accepts the PIAFS call. The PIAFS peer runs the PHS application.
|
Data or voice call in progress
|
Data or voice call in progress
|
An incoming PIAFS call comes in to the router.
|
The router does not bump a data or voice call for a PIAFS call, therefore does not accept the PIAFS call.
|
Free
|
Free
|
The router is handling a 64 kbps PIAFS call, with a current speed of 32 kbps. During the course of the call, the remote end requests a rate change to 64 kbps.
The router is handling a 64 kbps PIAFS call. During the course of the call, the remote end requests a rate change to 32 kbps.
|
The router successfully changes the speed of the PIAFS call from 32 kbps to 64 kbps.
The router successfully changes the speed of the PIAFS call from 64 kbps to 32 kbps.
|
Free
|
Free
|
The router is handling a 64 kbps PIAFS 2.0 call. During handover, the new cell is not able to allocate two channels for maintaining 64 kbps, so it requests the router to decrease the speed of the PIAFS call from 64 kbps to 32 kbps.
The router is handling a 64 kbps PIAFS 2.1 call. During handover, the new cell is not able to allocate two channels for maintaining 64 kbps, so it requests the router to decrease the speed of the PIAFS call from 64 kbps to 32 kbps.
|
Since PIAFS 2.0 supports only fixed rate PIAFS call, the router does not accept the PIAFS call.
Since PIAFS 2.1 supports best effort connection, the speed of the current PIAFS call is successfully decreased from 64 kbps to 32 kbps.
|
Free
|
PIAFS call in progress
|
The router is handling a PIAFS 2.0 call with the caller supporting PIAFS 2.0. A new PIAFS call comes from a caller supporting PIAFS 2.1
The router is handling a PIAFS 2.1 call with the caller supporting PIAFS 2.1. A new PIAFS call comes from a caller supporting PIAFS 2.0
|
The router simultaneously handles both PIAFS 2.0 and 2.1 calls.
The router simultaneously handles both PIAFS 2.0 and 2.1 calls.
|
PIAFS Status
The status of the PIAFS calls on the router can be checked by using the following command in privileged mode:
PIAFS Configuration Output Example
The following is an example of the output for PIAFS configuration:
Number of active calls = 1
Call Direction is - INCOMING
The Bchan assigned for this call is - B1 CHAN
First PPP Frame Detected - YES
Piafs main FSM state - PIAFS_DATA