V.120 Support Network Access Server (NAS) [Cisco IOS Software Releases 12.3 T]

Table Of Contents

V.120 Support for Network Access Server (NAS)

Contents

Information About V.120 Support for MGCP NAS

ITU-T Recommendation V.120 and MGCP NAS

How to Implement V.120 Support for MGCP NAS

Configuration Examples for V.120 Support for MGCP NAS

User Profile for MGCP NAS Authentication: Example

Chat Script for V.120 Connection: Example

debug cdapi detail Command: Example

CDAPI Events Debugging: Example

show cdapi Command Display for V.120 Calls: Example

Additional References

Related Documents

Standards

MIBs

RFCs

Technical Assistance

Command Reference

debug cdapi

show cdapi

V.120 Support for Network Access Server (NAS)

The V.120 Support for Network Access Server (NAS) feature supports the V.120 bit rate adaptation standard, which allows connectivity to slower-bandwidth devices through rate adaption. This feature was developed for the Media Gateway Control Protocol (MGCP) network access server package, and allows ISDN terminal adapters to transfer data.

Release

Modification

12.3(4)T

This feature was introduced.

Feature History for V.120 Support for Network Access Server (NAS)

Finding Support Information for Platforms and Cisco IOS Software Images

Use Cisco Feature Navigator to find information about platform support and Cisco IOS software image support. Access Cisco Feature Navigator at http://www.cisco.com/go/fn. You must have an account on Cisco.com. If you do not have an account or have forgotten your username or password, click Cancel at the login dialog box and follow the instructions that appear.

Contents

•Information About V.120 Support for MGCP NAS

•How to Implement V.120 Support for MGCP NAS

•Configuration Examples for V.120 Support for MGCP NAS

•Additional References

•Command Reference

Information About V.120 Support for MGCP NAS

To use the V.120 Support for Network Access Server (NAS) feature (or the V.120 Support for MGCP NAS feature, as a shorter reference), you need to understand the following concept:

•ITU-T Recommendation V.120 and MGCP NAS

ITU-T Recommendation V.120 and MGCP NAS

International Telecommunication Union Telecommunication Standardization Sector (ITU-T) Recommendation V.120 describes a standard that can be used for adapting terminals with non-ISDN standard network interfaces to an ISDN. It is intended to be used between two terminal adapter (TA) functional groups, between two ISDN terminal (TE1) functional groups, between a TA and a TE1, or between either a TA or TE1 and an interworking facility inside a public or private ISDN. V.120 allows for reliable transport of synchronous, asynchronous, or bit transparent data over ISDN bearer channels.

The V.120 bit rate adaptation standard allows connectivity to slower-bandwidth devices through rate adaption or encapsulation. The V.120 Support for MGCP NAS feature supports the V.120 bit rate adaptation standard for the MGCP NAS package.

The MGCP NAS package implements signals and events to create, modify, and close data calls. The events include signaling the arrival of an outbound call, such as IP to public switched telephone network (PSTN) to the media gateway controller (call agent), reporting carrier loss and call authorization status, and receiving callback requests.

How to Implement V.120 Support for MGCP NAS

No configuration commands are required to use the V.120 Support for MGCP NAS feature. The V.120 Support for MGCP NAS feature adds V.120 bit rate adaption capability to the Cisco IOS Release 12.3(4)T software. A new keyword, v120, is added to the MGCP connection request (CRCX) local connection options. The show cdapi and debug cdapi commands have also been updated with reports about V.120 calls. See the "Configuration Examples for V.120 Support for MGCP NAS" section for a sample chat script and RADIUS profile, and examples of the V.120 call reports.

Configuration Examples for V.120 Support for MGCP NAS

This section provides the following examples for the V.120 Support for MGCP NAS feature:

•User Profile for MGCP NAS Authentication: Example

•Chat Script for V.120 Connection: Example

•debug cdapi detail Command: Example

•CDAPI Events Debugging: Example

•show cdapi Command Display for V.120 Calls: Example

User Profile for MGCP NAS Authentication: Example

Following is a sample user profile that would be found on the authentication, authorization and accounting (AAA) RADIUS server:
2000 Password = "cisco"
Service-Type = Outbound,
Cisco:Cisco-Avpair = "preauth:auth-required=1"
Cisco:Cisco-Avpair ="preauth:auth-type=chap"
set l214 "L: b:56, nas/bt:v120, nas/cgn:1000, nas/cdn:2000, nas/v.120:lli-neg=yes;
header=no;multiframe=yes;mode=transparent;assign-lli=yes;asynch{parity=none}\n"
Chat Script for V.120 Connection: Example

Following is a sample chat script for a V.120 call:
chat-script v120-scr ABORT ERROR "" "ATs29=10s57=56000di \T" TIMEOUT 60 CONNECT
Note The V.120 Support for MGCP NAS feature supports only incoming V.120 calls.

debug cdapi detail Command: Example

The following partial example shows V.120 call debugging output for the debug cdapi detail command:
Router# debug cdapi detail
May 14 19:12:25.327:MGCP Packet received from 10.0.44.109:2427-
CRCX 6318 s7/ds1-0/24 MGCP 1.0
C:111
M:nas/data
L:b:64, nas/bt:v.120, nas/cdn:234567
R:nas/au, nas/ax,nas/of, nas/crq
X:101
May 14 19:12:25.327:CDAPI:cdapi_create_msg():CDAPI Pool Count:959, Raw Length = 0
May 14 19:12:25.327:CDAPI Se7/1:23:cdapi_add_entry_callRoutingTbl() -
May 14 19:12:25.327:   Added entry for call 0x7017 for application CSM
May 14 19:12:25.331:CDAPI:cdapi_create_msg():CDAPI Pool Count:958,
router# Raw Length = 0
May 14 19:12:25.331:CDAPI:cdapi_free_msg():Raw Length = 0, freeRaw = 1, Raw Msg = 0x0
May 14 19:12:25.331:CDAPI:cdapi_free_msg():CDAPI Pool Count:959
May 14 19:12:25.331:CDAPI:cdapi_free_msg():Raw Length = 0, freeRaw = 1, Raw Msg = 0x0
May 14 19:12:25.331:CDAPI:cdapi_free_msg():CDAPI Pool Count:960
May 14 19:12:25.331:send_mgcp_msg, MGCP Packet sent to 10.0.44.109:2427 --->
.
.
.
CDAPI Events Debugging: Example

You can enable CDAPI events debugging by issuing both the debug cdapi events and debug mgcp pack commands at the command-line interface. The following example shows the extensive reports displayed when the two debug commands are enabled. Comments for the reports are in <angle brackets>, with command names shown in bold text.
.
.
.
Router# show debug
CDAPI:
  CDAPI events debugging is on
MGCP:
  Media Gateway Control Protocol packets debugging is on
Router#
00:23:34: MGCP Packet received from 10.1.1.2:48004-
CRCX 50 S7/DS1-7/24 MGCP 1.0
X: 49
 M: nas/data
 C: 3
 N: emu@[10.1.1.2]:48004
 L: b:64, nas/bt:v.120, nas/cgn:1000, nas/cdn:2000, 
nas/v.120:lli-neg=yes;header=yes;multiframe=no;mode=transparent;assign-lli=no;asynch{parit
y=none}
< The preceding report is from the debug mgcp packet command. The report "nas/bt:v.120" >
< means that the Bearer type is V.120 and that this is a V120 call. >
00:23:34: mgcp_parse_v110_asynch_parms: proc_buff=none
00:23:34: Se7/7:23 CDAPI: TX -> CDAPI_MSG_CONNECT_IND to CSM call = 0x7717
00:23:34:       From Appl/Stack = XCSP
00:23:34:       Call Type    = V.120
< The preceding report is from the debug cdapi events command. The report "Call Type = >
< V.120" is the call type for which CDAPI is sending the CONNECT_IND to CSM. For modem >
< calls, the call type would be Modem. For V.110 calls, the call type would be V.110. >
00:23:34:       B
Router# Channel    = 23
00:23:34:       dslId        = 7
00:23:34:       Idb          = 0
00:23:34:       BChanIdb     = 6512FE14
00:23:34:       Handle       = 644C0AE4
00:23:34:       RPA          = 63FE9570
00:23:34:       Cause        = 0
00:23:34:       ApplCause    = 0
00:23:34:       ApplSpecData = 0
00:23:34:       Calling Party Number = 1000
00:23:34:       Called Party Number = 2000
00:23:34:       Overlap = 0
00:23:34: Se7/7:23 CDAPI: TX -> CDAPI_MSG_CONNECT_RESP to XCSP call = 0x7717
00:23:34:       From Appl/Stack = CSM
00:23:34:       Call Type    =
Router# MODEM
00:23:34:       B Channel    = 23
00:23:34:       dslId        = 7
00:23:34:       Idb          = 0
00:23:34:       BChanIdb     = 6512FE14
00:23:34:       Handle       = 644C0AE4
00:23:34:       RPA          = 0
00:23:34:       Cause        = 0
00:23:34:       ApplCause    = 0
00:23:34:       ApplSpecData = 0
00:23:34:       Overlap = 0
00:23:34: send_mgcp_msg, MGCP Packet sent to 10.1.1.2:48004 --->
00:23:34: 200 50  Alert
I: 6513A54C
<---
00:23:34: Se7/7:23 CDAPI: TX -> CDAPI_MSG_CONN_ACT_REQ to XCSP call = 0x7717
00:23:34:       Fr
Router#om Appl/Stack = CSM
00:23:34:       Call Type    = MODEM
00:23:34:       B Channel    = 23
00:23:34:       dslId        = 7
00:23:34:       Idb          = 0
00:23:34:       BChanIdb     = 6512FE14
00:23:34:       Handle       = 644C0AE4
00:23:34:       RPA          = 0
00:23:34:       Cause        = 0
00:23:34:       ApplCause    = 0
00:23:34:       ApplSpecData = 0
00:23:34:       Overlap = 0
show cdapi Command Display for V.120 Calls: Example

The following is sample output from the show cdapi command that indicates that the modem is registering a V.120 call:
Router# show cdapi
Registered CDAPI Applications/Stacks
====================================
Application: CSM
        Application Type(s) : Modem V110 V120 
        Application Level   : Basic
        Application Mode    : Enbloc
Signaling Stack: XCSP
Signaling Stack: ISDN
        Interface: Se7/1:23
Application: TSP CDAPI Application Voice
        Application Type(s) : Voice Data Facility Signaling V110 V120 
        Application Level   : Tunnel
        Application Mode    : Enbloc
Application: TSP CDAPI Application COT
        Application Type(s) : Cot 
        Application Level   : Tunnel
        Application Mode    : Enbloc
Signaling Stack: ISDN
        Interface: Se7/4:23
Signaling Stack: ISDN
        Interface: Se7/5:23
Signaling Stack: ISDN
        Interface: Se7/6:23
Signaling Stack: ISDN
        Interface: Se7/7:23
Active CDAPI Calls
==================
CDAPI Message Buffers
=====================
Free Msg Buffers: 960
Free Raw Buffers: 960
Free Large-Raw Buffers: 360
Additional References

The following sections provide references related to V.120 Support for MGCP NAS.

Related Documents

Related Topic

Document Title

MGCP NAS

•Configuring Network Access Server Package for Media Gateway Control Protocol feature module

•Cisco IOS Voice Configuration Library; refer to the "Media Gateway Control Protocol (MGCP)" section

•Cisco IOS Voice Command Reference, Release 12.3 T

Cisco-supported modem features and configuration

•Cisco IOS Dial Technologies Configuration Guide; refer to the chapter "Configuring and Managing Integrated Modems," in part 2

•Cisco IOS Dial Technologies Command Reference, Release 12.3 T

Standards

Standards

Title

V.120 bit rate adaption

ITU-T Recommendation V.120

MIBs

MIBs

MIBs Link

None

To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:

http://www.cisco.com/go/mibs

RFCs

RFCs

Title

None

—

Technical Assistance

Description

Link

Technical Assistance Center (TAC) home page, containing 30,000 pages of searchable technical content, including links to products, technologies, solutions, technical tips, and tools. Registered Cisco.com users can log in from this page to access even more content.

http://www.cisco.com/public/support/tac/home.shtml

Command Reference

This section documents the following modified commands. All other commands used with this feature are documented in the Cisco IOS Release 12.3 T command reference publications.

•debug cdapi

•show cdapi

debug cdapi

To display information about the Call Distributor Application Programming Interface (CDAPI), use the debug cdapi command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug cdapi {detail | events}
no debug cdapi {detail | events}
Syntax Description

detail

Displays when applications register or become unregistered with CDAPI, when calls are added or deleted from the CDAPI routing table, and when CDAPI messages are created and freed.

events

Displays the events passing between CDAPI and an application or signaling stack.

Defaults

Debugging output is disabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(6)T

This command was introduced.

12.1(5)XM2

This command was implemented on the Cisco AS5350 and Cisco AS5400.

12.3(2)T

This command was integrated into Cisco IOS Release 12.3(2)T. This command was enhanced to show V.110 call types..

12.3(4)T

This command was enhanced to show V.120 call types.

Usage Guidelines

The detail keyword is useful for determining if messages are being lost (or not freed). It is also useful for determining the size of the raw messages passed between CDAPI and other applications to ensure that the correct number of bytes is being passed.

The events keyword is useful for determining if certain ISDN messages are not being received by an application and if calls are not being directed to an application.

The following bandwidths are supported by this command and will appear in the debug reports:

•56 kbps

•64 kbps

Examples

The following Media Gateway Control Protocol (MGCP) packet received example shows V.110 call debugging output for the debug cdapi detail command. In this example, the modem is not yet in STEADY_STATE.
Router# debug cdapi detail
Sep 26 19:12:25.327:MGCP Packet received from 10.0.44.109:2427-
CRCX 6318 s7/ds1-0/24 MGCP 1.0
C:111
M:nas/data
L:b:64, nas/bt:v.110, nas/cdn:234567
R:nas/au, nas/ax,nas/of, nas/crq
X:101
Sep 26 19:12:25.327:CDAPI:cdapi_create_msg():CDAPI Pool Count:959, Raw Length = 0
Sep 26 19:12:25.327:CDAPI Se7/1:23:cdapi_add_entry_callRoutingTbl() -
Sep 26 19:12:25.327:   Added entry for call 0x7017 for application CSM
Sep 26 19:12:25.331:CDAPI:cdapi_create_msg():CDAPI Pool Count:958,
router# Raw Length = 0
Sep 26 19:12:25.331:CDAPI:cdapi_free_msg():Raw Length = 0, freeRaw = 1, Raw Msg = 0x0
Sep 26 19:12:25.331:CDAPI:cdapi_free_msg():CDAPI Pool Count:959
Sep 26 19:12:25.331:CDAPI:cdapi_free_msg():Raw Length = 0, freeRaw = 1, Raw Msg = 0x0
Sep 26 19:12:25.331:CDAPI:cdapi_free_msg():CDAPI Pool Count:960
Sep 26 19:12:25.331:send_mgcp_msg, MGCP Packet sent to 10.0.44.109:2427 --->
Sep 26 19:12:25.331:200 6318  Alert
I:64524608
Sep 26 19:12:25.339:CDAPI:cdapi_crea
router#te_msg():CDAPI Pool Count:959, Raw Length = 0
Sep 26 19:12:25.339:CDAPI:cdapi_free_msg():Raw Length = 0, freeRaw = 1, Raw Msg = 0x0
Sep 26 19:12:25.339:CDAPI:cdapi_free_msg():CDAPI Pool Count:960
router#
Sep 26 19:12:33.223:MGCP Packet received from 10.0.44.109:2427-
DLCX 6319 s7/ds1-0/24 MGCP 1.0
Sep 26 19:12:33.223:CDAPI:cdapi_create_msg():CDAPI Pool Count:959, Raw Length = 0
Sep 26 19:12:33.223:CDAPI:cdapi_create_msg():CDAPI Pool Count:958, Raw Length = 0
Sep 26 19:12:33.223:CDAPI:cdapi_free_msg():Raw Length = 0, freeRaw = 1, Raw Msg = 0x0
Sep 26 19:12:33.223:CDAPI:cdapi_free_msg():CDAPI Pool Count:959
Sep 26 19:12:33.227:CDAPI:cdapi_create_msg():CDAPI Pool Count:958, Raw
router# Length = 0
Sep 26 19:12:33.227:CDAPI Se7/1:23:cdapi_del_entry_callRoutingTbl() -
Sep 26 19:12:33.227:   Deleted entry for call 0x7017
Sep 26 19:12:33.227:CDAPI:cdapi_free_msg():Raw Length = 0, freeRaw = 1, Raw Msg = 0x0
Sep 26 19:12:33.227:CDAPI:cdapi_free_msg():CDAPI Pool Count:959
Sep 26 19:12:33.227:CDAPI:cdapi_free_msg():Raw Length = 0, freeRaw = 1, Raw Msg = 0x0
Sep 26 19:12:33.227:CDAPI:cdapi_free_msg():CDAPI Pool Count:960
Sep 26 19:12:33.227:send_mgcp_msg, MGCP Packet sent
router#to 10.0.44.109:2427 --->
Sep 26 19:12:33.227:200 6319 OK
The following partial example shows V.120 call debugging output for the debug cdapi detail command:
Router# debug cdapi detail
May 14 19:12:25.327:MGCP Packet received from 10.0.44.109:2427-
CRCX 6318 s7/ds1-0/24 MGCP 1.0
C:111
M:nas/data
L:b:64, nas/bt:v.120, nas/cdn:234567
R:nas/au, nas/ax,nas/of, nas/crq
X:101
May 14 19:12:25.327:CDAPI:cdapi_create_msg():CDAPI Pool Count:959, Raw Length = 0
May 14 19:12:25.327:CDAPI Se7/1:23:cdapi_add_entry_callRoutingTbl() -
May 14 19:12:25.327:   Added entry for call 0x7017 for application CSM
May 14 19:12:25.331:CDAPI:cdapi_create_msg():CDAPI Pool Count:958,
router# Raw Length = 0
May 14 19:12:25.331:CDAPI:cdapi_free_msg():Raw Length = 0, freeRaw = 1, Raw Msg = 0x0
May 14 19:12:25.331:CDAPI:cdapi_free_msg():CDAPI Pool Count:959
May 14 19:12:25.331:CDAPI:cdapi_free_msg():Raw Length = 0, freeRaw = 1, Raw Msg = 0x0
May 14 19:12:25.331:CDAPI:cdapi_free_msg():CDAPI Pool Count:960
May 14 19:12:25.331:send_mgcp_msg, MGCP Packet sent to 10.0.44.109:2427 --->
.
.
.
The following MGCP packet received example shows V.120 call debugging output for the debug cdapi events command:
Router# debug cdapi events
Sep 26 19:14:39.027:MGCP Packet received from 10.0.44.109:2427-
CRCX 6322 s7/ds1-0/24 MGCP 1.0
C:111
M:nas/data
L:b:64, nas/bt:v.120, nas/cdn:234567
R:nas/au, nas/ax,nas/of, nas/crq
X:101
Sep 26 19:14:39.027:Se7/0:23 CDAPI:TX -> CDAPI_MSG_CONNECT_IND to CSM call = 0x7017
Sep 26 19:14:39.027:   From Appl/Stack = XCSP
Sep 26 19:14:39.027:   Call Type    = V.120
Sep 26 19:14:39.027:   B Channel    = 23
Sep 26 19:14:39.027:   dslId        = 0
Sep 26 19:14:39.027:   Idb          = 0
Sep
router#26 19:14:39.027:   BChanIdb  = 64519A14
Sep 26 19:14:39.027:   Handle       = 63CB8DF4
Sep 26 19:14:39.027:   RPA          = 6388506C
Sep 26 19:14:39.027:   Cause        = 0
Sep 26 19:14:39.027:   ApplCause    = 0
Sep 26 19:14:39.027:   ApplSpecData = 0
Sep 26 19:14:39.027:   Calling Party Number =
Sep 26 19:14:39.027:   Called Party Number = 234567
Sep 26 19:14:39.027:   Overlap = 0
Sep 26 19:14:39.027:Se7/0:23 CDAPI:TX -> CDAPI_MSG_CONNECT_RESP to XCSP call = 0x7017
Sep 26 19:14:39.027:   From Appl
router#/Stack = CSM
Sep 26 19:14:39.027:   Call Type    = MODEM
Sep 26 19:14:39.027:   B Channel    = 23
Sep 26 19:14:39.027:   dslId        = 0
Sep 26 19:14:39.027:   Idb          = 0
Sep 26 19:14:39.027:   BChanIdb     = 64519A14
Sep 26 19:14:39.027:   Handle       = 63CB8DF4
Sep 26 19:14:39.027:   RPA          = 0
Sep 26 19:14:39.027:   Cause        = 0
Sep 26 19:14:39.027:   ApplCause    = 0
Sep 26 19:14:39.027:   ApplSpecData = 0
Sep 26 19:14:39.027:   Overlap = 0
Sep 26 19:14:39.031:send_mgcp_msg, MGCP Pa
router#cket sent to 10.0.44.109:2427 --->
Sep 26 19:14:39.031:200 6322  Alert
I:64524608
Sep 26 19:14:39.039:Se7/0:23 CDAPI:TX -> CDAPI_MSG_CONN_ACT_REQ to XCSP call = 0x7017
Sep 26 19:14:39.039:   From Appl/Stack = CSM
Sep 26 19:14:39.039:   Call Type    = MODEM
Sep 26 19:14:39.039:   B Channel    = 23
Sep 26 19:14:39.039:   dslId        = 0
Sep 26 19:14:39.039:   Idb          = 0
Sep 26 19:14:39.039:   BChanIdb     = 64519A14
Sep 26 19:14:39.039:   Handle       = 63CB8DF4
Sep 26 19:14:39.039:   R
router#PA          = 0
Sep 26 19:14:39.039:   Cause        = 0
Sep 26 19:14:39.039:   ApplCause    = 0
Sep 26 19:14:39.039:   ApplSpecData = 0
Sep 26 19:14:39.039:   Overlap = 0
router#
Sep 26 19:14:48.959:MGCP Packet received from 10.0.44.109:2427-
DLCX 6323 s7/ds1-0/24 MGCP 1.0
Sep 26 19:14:48.963:Se7/0:23 CDAPI:TX -> CDAPI_MSG_DISCONNECT_IND to CSM call = 0x7017
Sep 26 19:14:48.963:   From Appl/Stack = XCSP
Sep 26 19:14:48.963:   Call Type    = V.120
Sep 26 19:14:48.963:   B Channel    = 23
Sep 26 19:14:48.963:   dslId        = 0
Sep 26 19:14:48.963:   Idb          = 0
Sep 26 19:14:48.963:   BChanIdb     = 64519A14
Sep 26 19:14:48.963:   Handle       = 63CB8DF4
Sep 26 19:14
router#:48.963:        RPA          = 6388506C
Sep 26 19:14:48.963:   Cause        = 0
Sep 26 19:14:48.963:   ApplCause    = 0
Sep 26 19:14:48.963:   ApplSpecData = 0
Sep 26 19:14:48.963:   Overlap = 0
Sep 26 19:14:48.963:Se7/0:23 CDAPI:TX -> CDAPI_MSG_SUBTYPE_RELEASE_REQ to XCSP call = 
0x7017
Sep 26 19:14:48.963:   From Appl/Stack = CSM
Sep 26 19:14:48.963:   Call Type    = MODEM
Sep 26 19:14:48.963:   B Channel    = 23
Sep 26 19:14:48.963:   dslId        = 0
Sep 26 19:14:48.963:   Idb          = 0
Sep 26 19:14:48
router#.963:           BChanIdb     = 64519A14
Sep 26 19:14:48.963:   Handle       = 63CB8DF4
Sep 26 19:14:48.963:   RPA          = 0
Sep 26 19:14:48.963:   Cause        = 0
Sep 26 19:14:48.963:   ApplCause    = 1
Sep 26 19:14:48.963:   ApplSpecData = 0
Sep 26 19:14:48.963:   Overlap = 0
Sep 26 19:14:48.963:Se7/0:23 CDAPI:TX -> CDAPI_MSG_SUBTYPE_REL_COMP_IND to CSM call = 
0x7017
Sep 26 19:14:48.963:   From Appl/Stack = XCSP
Sep 26 19:14:48.963:   Call Type    = V.120
Sep 26 19:14:48.963:   B Channel    = 23
Sep 26 19:
router#14:48.963:      dslId        = 0
Sep 26 19:14:48.963:   Idb          = 0
Sep 26 19:14:48.963:   BChanIdb     = 64519A14
Sep 26 19:14:48.963:   Handle       = 63CB8DF4
Sep 26 19:14:48.963:   RPA          = 6388506C
Sep 26 19:14:48.963:   Cause        = 0
Sep 26 19:14:48.963:   ApplCause    = 0
Sep 26 19:14:48.963:   ApplSpecData = 0
Sep 26 19:14:48.963:   Overlap = 0
Sep 26 19:14:48.963:send_mgcp_msg, MGCP Packet sent to 10.0.44.109:2427 --->
Sep 26 19:14:48.963:200 6323 OK
Table 1 describes the significant fields shown in the reports.

Table 1 debug cdapi Field Descriptions

Field

Description

L:b:64, nas/bt

The bearer type parameter includes v.110 and v.120 for V.110 and V.120 calls.

Call Type

Call types are V.110, V.120, and modem.

Related Commands

Command

Description

debug mgcp packet

Displays the MGCP signaling message received and sent the Called agent.

debug voip rawmsg

Displays the raw message owner, length, and pointer.

show cdapi

To display the Call Distributor Application Programming Interface (CDAPI), use the show cdapi command in privileged EXEC mode.

show cdapi
Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(7)T

This command was introduced on the Cisco AS5300.

12.3(4)T

This command was enhanced to display V.120 call types registering with the modem.

Usage Guidelines

CDAPI is the internal application programming interface (API) that provides an interface between signaling stacks and applications.

Examples

The following is sample output from the show cdapi command. The reports are self-explanatory and display the following information:

•Signaling stacks that register with CDAPI

•Applications that register with CDAPI

•Active calls

•Call type of each active call

•Message buffers in use

Enbloc is the mode where all call establishment information is sent in the setup message (opposite of overlap mode, where additional messages are needed to establish the call). Cot is the Continuity Test (COT) subsystem that supports the Continuity Test required by the Signaling System 7 (SS7) network to conduct loopback and tone check testing on the path before a circuit is established.
Router# show cdapi
Registered CDAPI Applications/Stacks
====================================
Signaling Stack: ISDN
        Interface: Se6/0:23
Application: TSP CDAPI Application Voice
        Application Type(s) : Voice Data Facility Signaling V110 V120 
        Application Level   : Tunnel
        Application Mode    : Enbloc
Application: TSP CDAPI Application COT
        Application Type(s) : Cot 
        Application Level   : Tunnel
        Application Mode    : Enbloc
Application: CSM
        Application Type(s) : Modem V110 V120 
        Application Level   : Basic
        Application Mode    : Enbloc
Signaling Stack: XCSP
Application: dialer
        Application Type(s) : Data 
        Application Level   : Basic
        Application Mode    : Enbloc
Active CDAPI Calls
==================
        Se7/7:23 Call ID = 0x7717, Call Type = V.120, Application = CSM
CDAPI Message Buffers
=====================
Free Msg Buffers: 320
Free Raw Buffers: 320
Free Large-Raw Buffers: 120
Related Commands

Command

Description

debug cdapi

Displays information about the CDAPI.

Copyright © 2003 Cisco Systems, Inc. All rights reserved.

Cisco IOS Software Releases 12.3 T

V.120 Support Network Access Server (NAS)

Hierarchical Navigation

Downloads

Table Of Contents

V.120 Support for Network Access Server (NAS)

Contents

Information About V.120 Support for MGCP NAS

ITU-T Recommendation V.120 and MGCP NAS

How to Implement V.120 Support for MGCP NAS

Configuration Examples for V.120 Support for MGCP NAS

User Profile for MGCP NAS Authentication: Example

Chat Script for V.120 Connection: Example

debug cdapi detail Command: Example

CDAPI Events Debugging: Example

show cdapi Command Display for V.120 Calls: Example

Additional References

Related Documents

Standards

MIBs

RFCs

Technical Assistance

Command Reference

debug cdapi

Syntax Description

Defaults

Command Modes

Command History

Usage Guidelines

Examples

Related Commands

show cdapi

Syntax Description

Command Modes

Command History

Usage Guidelines

Examples

Related Commands

Copyright © 2003 Cisco Systems, Inc. All rights reserved.

Technology Trends