Table Of Contents
Enhanced Voice Services for Japan for Cisco 800 Series Routers
Configuring Enhanced Voice Services for Japan Cisco IOS Features
Enhanced Voice Services for Japan for Cisco 800 Series Routers
This feature module describes the Enhanced Voice Services for Japan Cisco IOS features, including INS-NET-64 voice features. It describes the benefits of the new features, supported platforms, configuration, related documents, and provides command-reference information.
This document includes the following sections:
•
Configuring Enhanced Voice Services for Japan Cisco IOS Features
Feature Overview
The Enhanced Voice Services for Japan Cisco IOS features consist of the following voice capabilities for the Cisco 800 series routers:
•
Provides analog Caller ID support for Japanese-language display, Caller ID- equipped, analog telephones. The Cisco 800 series router receives the Caller ID information from the INS-NET-64 switch. The router software prepares the Caller ID with a tone, transmits the Caller ID to plain old telephone service (POTS) port 1 or 2 on the router, and displays the Caller ID on the telephone.
•
Allows Cisco 800 series routers to reject an incoming voice call, based on local directory number (LDN) Caller IDs. Using the command-line interface (CLI), you can configure blocking for up to ten Caller ID numbers for each LDN.
•
Notifies you with a call-waiting tone of an incoming call while you are already connected to a telephone call. You can place the first call on hold by pressing the on-and-off-hook button (flash), connect to the second call, and then return to the first call after finishing with the second.
The feature uses both B channels of the ISDN line, enabling local call-waiting support on the router. Unlike standard ISDN call waiting, local call waiting does not require a subscription to call waiting from a service provider.
•
Conceals the caller ID of the outgoing call from the receiving device. To activate the feature, dial 184 before dialing the number of the receiving device, as specified in the Nippon Telegraph and Telephone (NTT) Communications Corporation user manual. This feature is specific to NTT Communications Corporation switches and is offered free of charge. The router handles this feature as a regular outgoing call and requires no special operation.
•
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 routers support the registration, activation, and deactivation requests for devices attached to the PHONE 1 or 2 port. The forwarding function itself is performed by the INS-NET-64 switch. This feature can be deactivated after its registration and activation phases.
During the registration phase of the device, you can:
–
–
–
During the activation phase, you determine whether calls are redirected all the time or only if the receiving device is busy or does not answer within the specified no-answer time period. You can use the telephone keypad dialing sequence as specified in the NTT user manual for any of the operations described above and to hear the Voice Warp registration details for a local device.
•
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. You can use the telephone keypad dialing sequence as specified in the NTT user manual for any of the Voice Select Warp feature operations and to hear the Voice Warp registration details for a local device.
•
Checks for Caller IDs that you register (using the telephone keypad for each LDN) and presents a distinctive ring to the telephone port receiving the incoming call if a match is detected. The routers provide three different ring cadences that you can set for calls from both registered and unregistered callers.
The default ring cadence setting is ring 1 for registered callers and ring 0 for unregistered callers. The on-and-off period for normal ringing signals (ring 0) and ringing signals for Nariwake service (ring 1) are defined in the NTT user manual.
The number of Caller IDs you can register for each LDN at one time is defined by the INS-NET-64 switch, 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. You can use the telephone keypad dialing sequence as specified in the NTT Communications Corporation user manual for any of the Nariwake feature operations and to hear the Nariwake registration details for a local device.
•
Also described as nuisance telephone call refusal service by INS Net. The network rejects all incoming calls to a particular telephone number from a troublesome caller. You do not have to specify the actual telephone number of the caller.
When activated, the caller hears a standard telephone announcement and a disconnect message. For information about the announcement or message, see the NTT user manual.
You are not automatically notified of incoming call attempts. However, to confirm call blocking results, you can listen to an announcement listing the number of incoming calls from blocked telephone numbers during the previous two months.
The number of callers that you can block is defined by the service provider at the time the service is activated. If you request an additional telephone number to block beyond the defined limit, the oldest number is discarded (unblocked) before the new number is registered.
To add a new number, you must hang up the telephone, go off-the-hook, and dial the call-blocking telephone keypad sequence within 60 seconds. When the feature is activated, you receive a recorded announcement indicating whether or not the activation is successful.
The feature can be turned off for either the last added (blocked) number or for all call-blocked numbers. A recorded announcement indicates the changes after they are made.
•
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 are routed through the same subscriber line to the terminal device attached to the target port.
•
Supports the POTS dial feature for Japanese telephones. Using a dial application on your workstation, you can dial a telephone number for the POTS port on the router.
If the telephone is on the hook when you issue the dial command, the router rings the telephone, waits until the telephone is taken off the hook, and then dials the requested number. If the telephone is off the hook when you issue the command, the router dials the requested number.
•
Disconnects a telephone number from the POTS port on the router.
Benefits
•
•
•
•
•
•
•
•
•
•
•
Restrictions
You must subscribe to the NTT services to use the Enhanced Voice Services for Japan Cisco IOS features. Therefore, except for the Call Blocking on Caller ID feature and Local Call Waiting, support is limited to telephone service inside Japan.
The following limitations also apply:
•
–
–
•
–
–
–
•
–
–
–
•
–
–
–
–
•
•
–
–
–
•
–
–
–
•
Related Documents
Release Notes and Caveats
•
•
Cisco 811 and 813 Routers
•
•
Cisco 800 Series Routers
•
•
•
Cisco 805 Routers
•
•
•
Supported Platforms
•
•
Prerequisites
Before using the Enhanced Voice Services for Japan Cisco IOS features, use the Cisco IOS command pots country jp to configure the router telephone ports to Japanese standards. The following requirements must also be met:
•
•
•
•
•
Configuring Enhanced Voice Services for Japan Cisco IOS Features
Many of the Enhanced Voice Services for Japan Cisco IOS features were developed for other Cisco routers before they were ported to Cisco 800 series routers. In some cases, CLI commands were created or modified to allow the features to run on Cisco 800 series routers. The following sections provide step instructions for configuring only those features that require new or changed Cisco IOS commands specifically created or modified to run on Cisco 800 series routers.
The Local Call Waiting feature is enabled by a single command in global configuration mode; see the section "pots call-waiting" for command syntax. The features POTS Dial and POTS Disconnect are also single commands in Exec mode; see the sections "test pots dial" and "test pots disconnect" for command examples.
The features E Ya Yo, Voice Warp, Voice Select Warp, and Trouble Call Blocking require no new or changed Cisco IOS commands to run on Cisco 800 series routers. To configure these features, see the Cisco 800 Series Routers Software Configuration Guide.
Caller ID
The following procedure provides step instructions for configuring the Caller ID feature:
Call Blocking on Caller ID
The following procedure provides step instructions for configuring the Call Blocking on Caller ID feature:
Nariwake
The following procedure provides step instructions for configuring the Nariwake feature:
I Number
The following procedure provides step instructions for configuring the I Number feature:
Configuration Examples
See the "Examples" headings in the sections "Command Reference" and "Debug Commands" for commands samples.
Command Reference
This section documents new or changed commands for the Enhanced Voice Services for Japan Cisco IOS features. All other commands used with these commands are documented in the Cisco IOS Release 12.1 configuration and command-reference publications.
caller-id
To enable Caller ID, use the dial-peer configuration caller-id command.
caller-id
no caller-id
The no form of the caller-id command disables Caller ID.
Syntax Description
This command contains no arguments or keywords.
Defaults
Caller ID is disabled.
Command Modes
Dial-peer configuration.
Command History
Cisco IOS Release 12.1.(2)XF
The command caller-id was introduced on the Cisco 800 series routers.
Usage Guidelines
This command is available on Cisco 800 series routers that have POTS ports. The command is effective only if you subscribe to Caller ID service. If you enable Caller ID on a router without subscribing to the Caller ID service, Caller ID information does not appear on the telephone display.
The configuration of Caller ID must match the device connected to the POTS port. That is, if a telephone supports the Caller ID feature, use the command caller-id to enable the feature or if the telephone does not support the Caller ID feature, use the command default or disable the Caller ID feature. Odd ringing behavior might occur if the Caller ID feature is disabled when it is a supported telephone feature or enabled when it is not a supported telephone feature.
Examples
The following example enables a router to use the Caller ID feature.
router(config)# dial-peer voice 1 potsrouter(config-dial-peer)# caller-idrouter(config-dial-peer)#Related Commands
block-caller number
Configure Call Blocking on Caller ID.
debug pots csm csm
Activate events from which an application can determine and display the status and progress of calls to and from POTS ports.
Configure several terminal devices to use one subscriber line.
Enable local call waiting on a router.
Configure the Nariwake service registered caller ring cadence.
block-caller
To configure Call Blocking on Caller ID, use the dial-peer configuration block-caller command.
block-caller number
no block-caller number
The no form of the block-caller command disables Call Blocking on Caller ID.
Syntax Description
Defaults
Call blocking is disabled; the router does not block any calls for any LDNs based on Caller ID numbers.
Command Modes
Dial-peer configuration.
Command History
Cisco IOS Release 12.1.(2)XF
The command block-caller was introduced on the Cisco 800 series routers.
Usage Guidelines
This command is available on Cisco 800 series routers that have POTS ports. For each dial-peer, you can enter up to ten Caller ID numbers to block. The routers do not accept additional Caller ID numbers if ten numbers already exist. In this case, a number must be removed before another Caller ID number can be added for blocking.
If you do not specify the block-caller command for a local directory, all voice calls to that local directory are accepted. If you specify the block-caller command for a local directory, the router verifies that the incoming calling-party number does not match any Caller ID numbers in that local directory before processing or accepting the voice call. Each specified Caller ID number and incoming calling-party number is compared from right to left, up to the number of digits in the specified Caller ID number or incoming calling-party number, whichever has less digits.
This command is effective only if you subscribe to Caller ID service. If you enable call blocking on Caller ID without subscribing to the Caller ID service, the routers do not perform the verification process on calling-party numbers and do not block any calls.
Examples
The following example configures a router to block calls from a caller whose Caller ID number is 408-555-1234.
router(config)# dial-peer voice 1 potsrouter(config-dial-peer)# block-caller 4085551234router(config-dial-peer)#Related Commands
Identify incoming calls with Caller ID.
debug pots csm csm
Activate events from which an application can determine and display the status and progress of calls to and from POTS ports.
Configure several terminal devices to use one subscriber line.
Enable local call waiting on a router.
Configure the Nariwake service registered caller ring cadence.
isdn i-number
To configure several terminal devices to use one subscriber line, use the global configuration isdn i-number command.
isdn i-number n ldn
Syntax Description
n
Subscriber line 1, 2 or 3, as specified in the NTT specification.
ldn
LDN assigned to the router POTS port.
Defaults
The default is each terminal device uses one subscriber line.
Command Modes
Interface BRI0 configuration.
Command History
Cisco IOS Release 12.1.(2)XF
The command isdn i-number was introduced on the Cisco 800 series routers.
Usage Guidelines
Enter the command interface bri before entering the command isdn i-number.
Examples
The following example shows screen output for two LDNs configured under interface BRI0:
router(config)# interface bri0router(config-if)# isdn i-number 1 5551234router(config-if)# isdn i-number 2 5556789router(config-if)# exitrouter(config)# dial-peer voice 1 potsrouter(config-dial-peer)# destination-pattern 5551234router(config-dial-peer)# exitrouter(config)# dial-peer voice 2 potsrouter(config-dial-peer)# destination-pattern 5556789router(config-dial-peer)# exitrouter(config)#Related Commands
pots call-waiting
To enable the Local Call Waiting feature on a Cisco 800 series router, use the global configuration pots call-waiting command.
pots call-waiting [ local | remote ]
no pots call-waiting [ local | remote ]
Syntax Description
local
Enable call waiting on a local basis for the routers.
remote
Rely on the network provider service instead of the router to hold calls.
Defaults
The call waiting default is remote if the Call Waiting feature is not configured. In that case, the call holding pattern follows the settings of the service provider rather than those of the router.
Command Modes
Global configuration.
Command History
Cisco IOS Release 12.1.(2)XF
The command pots call-waiting was introduced on the Cisco 800 series routers.
Usage Guidelines
To display the call waiting setting, use the command show run or show pots status. The ISDN call waiting service is used if it is available on the ISDN line connected to the router even if local call waiting is configured on the router. That is, if the ISDN line supports call waiting, the local call waiting configuration on the router is ignored.
Examples
The following example enables local call waiting on a router:
router(config)# pots call-waiting localrouter(config)#Related Commands
registered-caller ring
To configure the Nariwake service registered caller ring cadence, use the dial-peer configuration registered-caller ring command.
registered-caller ring cadence
Syntax Description
Defaults
The default Nariwake service registered caller ring cadence is Ring 1.
Command Modes
Dial-peer configuration.
Command History
Cisco IOS Release 12.1.(2)XF
The command registered-caller ring was introduced on the Cisco 800 series routers.
Usage Guidelines
If your ISDN line is provisioned for the I Number or dial-in services, you must also configure a dial-peer by using the command destination-pattern not-provided. Either port 1 or 2 can be configured under this dial-peer. The router then forwards the incoming call to the voice port 1. See the "Examples" section for details.
If more than one dial-peer is configured with destination-pattern not-provided, the router uses the first configured dial-peer for the incoming calls. To display the Nariwake ring cadence setting, use the show run command.
Examples
The following example sets the ring cadence for registered callers to 2.
router(config)# pots country jprouter(config)# dial-peer voice 1 potsrouter(config-dial-peer)# registered-caller ring 2router(config-dial-peer)#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-providedrouter(config-dial-peer)#show pots csm
To show the current state of calls and the most recent event received by the call switching module (CSM) on the Cisco 800 series router, use the Exec show pots csm command.
show pots csm port
Syntax Description
Command Modes
Exec.
Command History
Cisco IOS Release 12.1.(2)XF
The command show pots csm was introduced on the Cisco 800 series routers.
Examples
The following is an example of show pots csm command output:
router# show pots csm 1POTS PORT: 1CSM Finite State Machine:Call 0 - State: idle, Call Id: 0x0Active: noEvent: CSM_EVENT_NONE Cause: 0Call 1 - State: idle, Call Id: 0x0Active: noEvent: CSM_EVENT_NONE Cause: 0Call 2 - State: idle, Call Id: 0x0Active: noEvent: CSM_EVENT_NONE Cause: 0router#Related Commands
Dial a telephone number for the POTS port on the router by using a dial application on your workstation.
Disconnect a telephone call for the POTS port on the router.
test pots dial
To dial a telephone number for the POTS port on the router by using a dial application on your workstation, use the Exec test pots dial command.
test pots port dial number[#]
If the telephone is on the hook when you issue the dial command, the router rings the telephone, waits until the telephone is taken off the hook, and then dials the requested number. If the telephone is off the hook and providing a dial tone when you issue the command, the router dials the requested number.
Syntax Description
Command Modes
Exec.
Command History
Cisco IOS Release 12.1.(2)XF
The command test pots port dial was introduced on the Cisco 800 series routers.
Examples
The following POTS dial command dials the telephone number 408-555-1234:
router# test pots 1 dial 4085551234#router#For an example of the command test pots port dial with debug output, see the command-reference section "debug pots csm."
Related Commands
Show the current state of calls and the most recent event received by the CSM on the router.
Disconnect a telephone call for the POTS port on the router.
test pots disconnect
To disconnect a telephone call for the POTS port on the router, use the Exec test pots disconnect command.
test pots port disconnect
Syntax Description
Command Modes
Exec.
Command History
Cisco IOS Release 12.1.(2)XF
The command test pots port disconnect was introduced on the Cisco 800 series routers.
Examples
The following POTS disconnect command disconnects a telephone call from POTS port 1:
router# test pots 1 disconnectrouter#For an example of the command test pots port disconnect command with debug output, see the command-reference section "debug pots csm."
Related Commands
Debug Commands
This section documents new debug command.
debug pots csm
To activate events from which an application can determine and display the status and progress of calls to and from POTS ports, use the Exec debug pots csm command.
debug pots csm
Syntax Description
csm
Call switching module. See the section "Usage Guidelines" for details.
Command Modes
Exec.
Command History
Cisco IOS Release 12.1.(2)XF
The command debug pots csm was introduced on the Cisco 800 series routers.
Usage Guidelines
To see debug messages, enter Configuration mode command logging console as follows:
router(config) # logging consolerouter(config) # exit
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??Each format element is defined as follows:
hh:mm:ss
Timestamp in hours, minutes, and seconds.
CSM_STATE
One of the call CSM states listed in Table 1.
CSM_EVENT
One of the CSM events listed in Table 2.
call id
Hexadecimal value from 0x00 to 0xFF.
port
Telephone port 1 or 2.
EVENT_FROM_ISDN
A CSM event. Table 2 shows a list of CSM events.
dchan_idb
Internal data structure address.
ces
Connection end point suffix used by ISDN.
bchan
Channel used by the call. A value of 0xFFFFFFFF indicates that a channel is not assigned.
event
A hexadecimal value that is translated into a CSM event. Table 3 shows a list of events and the corresponding CSM events.
cause
A hexadecimal value that is given to call-progressing events. Table 4 shows a list of cause values and definitions.
CSM States
Table 1 shows the values for CSM states.
CSM Events
Table 2 shows the values for CSM events.
Events
Table 3 shows the values for events that are translated into CSM events.
Cause
This table shows cause values that are assigned only to call-progressing events.
Examples
This section provides debug output examples for three call scenarios, displaying the sequence of events that occur during a POTS dial call or POTS disconnect call.
•
In this example call scenario, port 1 is on the hook, the application dial is set to call 4085552221, and the far-end successfully connects.
router# debug pots csmrouter# test pots 1 dial 4085552221#router#The following screen output shows an event indicating that port 1 is being used by the dial application:
01:58:27: CSM_PROC_IDLE: CSM_EVENT_VDEV_APPLICATION_CALL, call id = 0x0, port = 1The 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 = 101:58:27: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 101:58:27: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 101:58:27: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 101:58:27: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 101:58:27: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 101:58:27: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 101:58:27: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 101:58:27: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 101:58:27: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1The following screen output shows that the telephone connected to port 1 is off the hook:
01:58:39: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_OFFHOOK, call id = 0x0, port = 1The 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=0x001:58:40: CSM_PROC_ENBLOC_DIALING: CSM_EVENT_ISDN_PROC, call id =0x8004, port = 1The 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=0x001:58:40: CSM_PROC_ENBLOC_DIALING: CSM_EVENT_ISDN_CALL_PROGRESSING, call id = 0x8004, port = 1The 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=0x001:58:48: CSM_PROC_CONNECTING: CSM_EVENT_ISDN_CONNECTED, call id = 0x8004, port = 1The following screen output shows a call-progressing event pair indicating that the telephone at the far end has hung up and that 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 bchan=0xFFFFFFFF, event=0x5, cause=0x1001:58:55: CSM_PROC_CONNECTED: CSM_EVENT_ISDN_CALL_PROGRESSING, call id = 0x8004, port = 1The 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 = 1The 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=0x001:58:57: CSM_PROC_NEAR_END_DISCONNECT: CSM_EVENT_ISDN_DISCONNECTED, call id = 0x8004, port = 1813_local#•
In this example scenario, port 1 is on the hook, the application dial is set to call 4085552221, and the destination number is busy.
router# debug pots csmrouter# test pots 1 dial 4085552221#router#The following screen output shows that port 1 is used by the dial application:
01:59:42: CSM_PROC_IDLE: CSM_EVENT_VDEV_APPLICATION_CALL, call id = 0x0, port = 1The 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 = 101:59:42: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 101:59:42: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 101:59:42: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 101:59:42: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 101:59:42: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 101:59:42: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 101:59:42: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 101:59:42: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 101:59:42: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1The following screen output shows an event indicating that the telephone connected to port 1 is off the hook:
01:59:52: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_OFFHOOK, call id = 0x0, port = 1The 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=0x1101:59:52: CSM_PROC_ENBLOC_DIALING: CSM_EVENT_ISDN_PROC, call id = 0x8005, port = 1The 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=0x001:59:58: CSM_PROC_ENBLOC_DIALING: CSM_EVENT_ISDN_CALL_PROGRESSING, call id = 0x8005, port = 1The 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 = 1The following screen output shows an event pair indicating that the call has been terminated:
02:00:05: EVENT_FROM_ISDN:dchan_idb=0x280AF38, call_id=0x8005, ces=0x1 bchan=0xFFFFFFFF, event=0x0, cause=0x002:00:05: CSM_PROC_NEAR_END_DISCONNECT: CSM_EVENT_ISDN_DISCONNECTED, call id = 0x8005, port = 1•
In this example call scenario, port 1 is on the hook, the application dial is set to call 408-666-1112, the far end successfully connects, and the command test pots disconnect terminates the call.
router# debug pots csmrouter# test pots 1 dial 4086661112router#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 = 11d03h: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 11d03h: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 11d03h: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 11d03h: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 11d03h: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 11d03h: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 11d03h: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 11d03h: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 11d03h: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 11d03h: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 11d03h: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_OFFHOOK, call id = 0x0, port = 11d03h: EVENT_FROM_ISDN:dchan_idb=0x2821F38, call_id=0x8039, ces=0x1bchan=0x0, event=0x3, cause=0x01d03h: CSM_PROC_ENBLOC_DIALING: CSM_EVENT_ISDN_PROC, call id = 0x8039, port = 11d03h: EVENT_FROM_ISDN:dchan_idb=0x2821F38, call_id=0x8039, ces=0x1bchan=0xFFFFFFFF, event=0x5, cause=0x01d03h: CSM_PROC_ENBLOC_DIALING: CSM_EVENT_ISDN_CALL_PROGRESSING, call id = 0x8039, port = 1router# test pots 1 disconnectThe test pots disconnect command disconnects the call before you physically have to put the telephone back on the hook.
1d03h: CSM_PROC_CONNECTING: CSM_EVENT_VDEV_APPLICATION_HANGUP_CALL, call id = 0x8039, port = 11d03h: EVENT_FROM_ISDN:dchan_idb=0x2821F38, call_id=0x8039, ces=0x1bchan=0xFFFFFFFF, event=0x0, cause=0x01d03h: CSM_PROC_DISCONNECTING: CSM_EVENT_ISDN_DISCONNECTED, call id = 0x8039, port = 11d03h: CSM_PROC_DISCONNECTING: CSM_EVENT_TIMEOUT, call id = 0x8039, port = 1