Verifying PSTN Punch Plans

Verifying PSTN Punch Plans

The appearance dial-peer articulation and the appearance dialplan cardinal commands are acclimated to verify

dial affairs on a gateway, as abundant in Table 6-8.

Table 6-8 Commands to Verify PSTN Punch Plans

Command Description

show dial-peer articulation cardinal Displays advice for a specific articulation punch peer

show dial-peer articulation arbitrary Displays a abbreviate arbitrary of anniversary articulation punch peer

show dialplan cardinal dial-string Displays which approachable punch associate is accomplished back a

[carrier identifier] [fax | huntstop accurate blast cardinal is dialed

| voice] [timeout]

Example 6-16 provides sample achievement from the appearance dial-peer articulation arbitrary command.

Notice the achievement shows the authoritative and operational cachet of anniversary dial

peer, anniversary dial-peer’s destination pattern, dial-peer preference, affair ambition (where

applicable), and articulation anchorage (where applicable).

Example 6-16 appearance dial-peer articulation arbitrary Command

Chapter 6: Identifying Punch Plan Characteristics 341

Router#show dial-peer articulation summary

dial-peer coursing 0

AD PRE PASS OUT

TAG TYPE MIN OPER PREFIX DEST-PATTERN FER THRU SESS-TARGET STAT PORT

9 pots up up 9T 0 up 1/0:23

20 voip up up 2... 0 syst ipv4:192.168.1.1

21 voip up up 2... 1 syst ipv4:192.168.1.2

Example 6-17 shows sample achievement from the appearance dialplan cardinal command for a

phone cardinal of 1001.

Example 6-17 appearance dialplan cardinal 1001 Command

Router#show dialplan cardinal 1001

VoiceEncapPeer20001

peer blazon = voice, advice blazon = voice,

description = `’,

tag = 20001, destination-pattern = `1001$’,

answer-address = `’, preference=0,

CLID Restriction = None

CLID Arrangement Cardinal = `’

CLID Second Cardinal sent

CLID Override RDNIS = disabled,

continues

Notice the antecedent achievement indicates the acumen for the aftermost disconnect. Specifically, in

Example 6-17, the aftermost abstract account cipher was 0x10, in hex (16 in decimal). The disconnect

text was “normal alarm clearing.” This is an archetype of a Q.850 account code. As a

reference, Table 6-9 lists accepted Q.850 account codes acclimated for PRI and H.323.

342 Authorized Self-Study Guide: Cisco Articulation over IP (CVOICE)

source carrier-id = `’, ambition carrier-id = `’,

source trunk-group-label = `’, ambition trunk-group-label = `’,

numbering Blazon = `unknown’

group = 20001, Admin accompaniment is up, Operation accompaniment is up,

incoming called-number = `’, connections/maximum = 0/unlimited,

DTMF Relay = disabled,

URI classes:

Destination =

huntstop = enabled,

in apprenticed appliance associated: ‘DEFAULT’

out apprenticed appliance associated: ‘’

dnis-map =

permission :both

incoming COR list:maximum capability

outgoing COR list:minimum requirement

Translation contour (Incoming):

Translation contour (Outgoing):

incoming alarm blocking:

translation-profile = `’

disconnect-cause = `no-service’

advertise 0x40 capacity_update_timer 25 addrFamily 4 oldAddrFamily 4

type = pots, prefix = `’,

forward-digits 0

session-target = `’, voice-port = `50/0/11’,

direct-inward-dial = disabled,

digit_strip = enabled,

register E.164 cardinal with H323 GK and/or SIP Registrar = TRUE

fax amount = system, burden admeasurement = 20 bytes

supported-language = ‘’

Time delayed back aftermost allowance of articulation alarm statistics never

Connect Time = 0, Charged Units = 0,

Successful Calls = 2, Failed Calls = 0, Incomplete Calls = 0

Accepted Calls = 0, Refused Calls = 0,

Last Abstract Account is “10 “, Aftermost Abstract Text is “normal

call allowance (16)”,

Last Bureaucracy Time = 436050.

Matched: 1001 Digits: 5

Target:

Example 6-17 appearance dialplan cardinal 1001 Command continued

Table 6-9 Q.850 Account Codes

Cause Cipher Definition

HEX DEC

0x1 1 Unallocated number

0x3 3 No avenue to destination

0x6 6 Approach unacceptable

0x7 7 Alarm awarded and actuality delivered in an accustomed channel

0x10 16 Normal alarm clearing

0x11 17 User busy

0x12 18 No user responding

0x13 19 No acknowledgment from user

0x15 21 Alarm rejected

0x16 22 Cardinal changed

0x1A 26 Nonselected user clearing

0x1B 27 Destination out of order

0x1C 28 Invalid cardinal format

0x1D 29 Ability rejected

0x1E 30 Response to a cachet enquiry

0x1F 31 Normal, unspecified

0x22 34 No approach available

0x26 38 Arrangement out of order

0x29 41 Temporary failure

0x2A 42 Switching accessories congestion

0x2B 43 Access advice discarded

0x2C 44 Request approach not available

0x2F 47 Resource not available

0x31 49 Quality of account unavailable

0x32 50 Requested ability not subscribed

0x39 57 Agent adequacy not authorized

0x3A 58 Agent adequacy not anon available

continues

Chapter 6: Identifying Punch Plan Characteristics 343

Table 6-9 Q.850 Account Codes (continued)

Cause Cipher Definition

HEX DEC

0x3F 63 Account or advantage not available

0x41 65 Agent adequacy not implemented

0x42 66 Approach blazon not implemented

0x45 69 Request ability not implemented

0x46 70 Only belted agenda advice agent adequacy is available

0x4F 79 Account or advantage not implemented, unspecified

0x51 81 Invalid alarm advertence value

0x52 82 Identified approach does not exist

0x53 83 Suspended alarm exists, but alarm character does not

0x54 84 Alarm character in use

0x55 85 No alarm suspended

0x56 86 Alarm with the authentic alarm character is cleared

0x58 88 Incompatible destination

0x5B 91 Invalid alteration arrangement selection

0x5F 95 Invalid message, unspecified

0x60 96 Mandatory advice aspect is missing

0x61 97 Bulletin blazon absent or not implemented

0x62 98 Bulletin not accordant with alarm accompaniment or bulletin blazon nonexistent

0x63 99 Advice aspect absent or not implemented

0x64 100 Invalid advice aspect contents

0x65 101 Bulletin not accordant with alarm state

0x66 102 Recovery on timer expiry

0x6F 111 Protocol error, unspecified

0x7F 127 Internetworking, unspecified

Several alter commands are accessible for troubleshooting punch plans, as declared in

Table 6-10.

344 Authorized Self-Study Guide: Cisco Articulation over IP (CVOICE)

Table 6-10 alter Commands for PSTN Punch Plans

Command Description

debug isdn q931 Debugs ISDN Band 3 information, which includes DNIS and ANI

information

debug voip dialpeer Debugs dial-peer matching

debug articulation adaptation Debugs voice-translation-rule operation

Example 6-18 shows sample achievement from a alter isdn q931 command from a alarm setup

procedure for an admission call.

Example 6-18 alter isdn q931 Command–Part 1

Chapter 6: Identifying Punch Plan Characteristics 345

Router#debug isdn q931

RX <- SETUP pd = 8 callref = 0x06

Bearer Adequacy i = 0x8890

Channel ID i = 0x89

Calling Affair Cardinal i = 0x0083, `81012345678902’

TX -> CONNECT pd = 8 callref = 0x86

RX <- CONNECT_ACK pd = 8 callref = 0x06

Use the alter isdn q931 command in advantaged EXEC approach to affectation information

about alarm bureaucracy and teardown of ISDN arrangement access (Layer 3) amid the local

router (user side) and the network. To attenuate debugging output, use the no anatomy of this

command.

The ISDN arrangement band interface that is provided by the router conforms to the user

interface blueprint authentic by ITU-T Recommendation Q.931, supplemented by other

specifications such as for about-face blazon VN4. The router advance activities that action only

on the user side, not the arrangement side, of the arrangement connection. The alter isdn q931

command achievement is bound to commands and responses that are exchanged during peerto-

peer advice and agitated over the abstracts approach (D channel). This alter information

does not accommodate abstracts beatific over the agent channels (B channels), which are also

part of the ISDN interface of the router. The aeon (network layers) acquaint with

each added via an ISDN about-face over the D channel.

A router can be the calling affair or the alleged affair of the ISDN Q.931 networkconnection

call bureaucracy and teardown procedures. If the router is the calling party, the

command displays advice about an approachable call. If the router is the alleged party,

the command displays advice about an admission call.

Example 6-19 shows sample achievement from the alter isdn q931 command of a alarm setup

procedure for an approachable call.

Example 6-19 alter isdn q931 Command—Part 2

346 Authorized Self-Study Guide: Cisco Articulation over IP (CVOICE)

Router#debug isdn q931

TX -> SETUP pd = 8 callref = 0x04

Bearer Adequacy i = 0x8890

Channel ID i = 0x83

Called Affair Cardinal i = 0x80, `4085552001’

RX <- CALL_PROC pd = 8 callref = 0x84

Channel ID i = 0x89

RX <- CONNECT pd = 8 callref = 0x84

TX -> CONNECT_ACK pd = 8 callref = 0x04....

Success amount is 0 percent (0/5)

You can use the alter isdn q931 command with the alter isdn accident and alter isdn

q921 commands at the aforementioned time. The displays will be intermingled. Use the service

timestamps alter datetime msec command in all-around agreement approach to accommodate the

time with anniversary message.

To affectation advice about the articulation punch peers, use the alter voip dialpeer command

in advantaged EXEC mode. Archetype 6-20 shows an accident that identifies the admission dial

peer and shows that it has been matched.

Example 6-20 alter voip dialpeer Command

Router#debug voip dialpeer

*Apr 18 21:07:35.291: //-1/xxxxxxxxxxxx/DPM/MatchNextPeer:

Result=Success(0); Admission Dial-peer=1 Is Matched

*Apr 18 21:07:35.291: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:

Match Rule=DP_MATCH_INCOMING_DNIS; Alleged Number=83103

*Apr 18 21:07:35.291: //-1/xxxxxxxxxxxx/DPM/dpMatchPeertype:

Is Incoming=TRUE, Cardinal Expansion=FALSE

*Apr 18 21:07:35.291: //-1/xxxxxxxxxxxx/DPM/dpMatchCore:

Dial String=83103, Expanded String=83103, Calling Number=

Timeout=TRUE, Is Incoming=TRUE, Associate Info Type=DIALPEER_INFO_FAX

*Apr 18 21:07:35.291: //-1/xxxxxxxxxxxx/DPM/dpMatchCore:

Result=-1

*Apr 18 21:07:35.291: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:

Match Rule=DP_MATCH_ANSWER; Calling Number=4085550111

*Apr 18 21:07:35.291: //-1/xxxxxxxxxxxx/DPM/dpMatchPeertype:

Is Incoming=TRUE, Cardinal Expansion=FALSE

*Apr 18 21:07:35.291: //-1/xxxxxxxxxxxx/DPM/dpMatchCore:

Dial String=, Expanded String=, Calling Number=4085550111T

Timeout=TRUE, Is Incoming=TRUE, Associate Info Type=DIALPEER_INFO_FAX

To appearance articulation adaptation aphorism information, use the alter articulation adaptation command.

Example 6-21 shows sample achievement from the alter articulation adaptation command for the

following adaptation rule:

voice translation-rule 1001

rule 1 /^.*/ /5551212/

Example 6-21 alter articulation adaptation Command

Chapter 6: Identifying Punch Plan Characteristics 347

*Apr 18 21:07:35.291: //-1/xxxxxxxxxxxx/DPM/dpMatchCore:

Result=-1

*Apr 18 21:07:35.291: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:

Match Rule=DP_MATCH_ORIGINATE; Calling Number=4085550111

*Apr 18 21:07:35.291: //-1/xxxxxxxxxxxx/DPM/dpMatchPeertype:

Is Incoming=TRUE, Cardinal Expansion=FALSE

*Apr 18 21:07:35.291: //-1/xxxxxxxxxxxx/DPM/dpMatchCore:

Dial String=, Expanded String=, Calling Number=4085550111T

Timeout=TRUE, Is Incoming=TRUE, Associate Info Type=DIALPEER_INFO_FAX

*Apr 18 21:07:35.295: //-1/xxxxxxxxxxxx/DPM/dpMatchCore:

Result=-1

Router#debug articulation translation

00:51:56:regxrule_get_profile_from_trunkgroup:Voice anchorage 0x64143DA8

does not accord to any block group

00:51:56:regxrule_get_profile_from_trunkgroup:Voice anchorage 0x64143DA8

does not accord to any block group

00:51:56:regxrule_stack_pop_RegXruleNumInfo:stack=0x63DECAF4; count=1

00:51:56:regxrule_stack_push_RegXruleNumInfo:stack=0x63DECAF4; count=0

This achievement shows the capacity of the aboriginal cardinal following

“regxrule_profile_translate”.

00:51:56:regxrule_profile_translate:number=4088880101 type=unknown

plan=unknown numbertype=calling

Following “regxrule_profile_match”, the achievement shows that aphorism 1 in

the adaptation aphorism 1001 was a bout and the capacity of the SED

substitution are shown.

00:51:56:regxrule_profile_match:Matched with aphorism 1 in ruleset 1001

00:51:56:regxrule_profile_match:Matched with aphorism 1 in ruleset 1001

00:51:56:sed_subst:Successful substitution; pattern=4088880101

matchPattern=^.* replacePattern=5551212 replaced pattern=5551212

00:51:56:regxrule_subst_num_type:Match Blazon = none, Replace Blazon = none

Input Blazon = unknown

00:51:56:regxrule_subst_num_plan:Match Plan = none, Replace Plan = none

Input Plan = unknown

Then the achievement shows the capacity of the translated cardinal following

“regxrule_profile_translate”.

00:51:56:regxrule_profile_translate:xlt_number=5551212 xlt_type=unknown

xlt_plan=unknown

00:51:56:regxrule_profile_translate:number= type=UNKNOWN plan=UNKNOWN

numbertype=redirect-called

00:51:56:regxrule_get_RegXrule:Invalid adaptation ruleset tag=0

In this example, because there was no alleged cardinal or alter number

translation that was configured on the adaptation profile, corresponding

errors were generated with a bulletin that no bout was found.

00:51:56:regxrule_profile_match:Error:ruleset for redirect-called

number not found

00:51:56:regxrule_profile_translate:No match:number= type=UNKNOWN plan=UNKNOWN

00:51:56:regxrule_profile_translate:number=5108880101 type=unknown

plan=unknown numbertype=called

00:51:56:regxrule_get_RegXrule:Invalid adaptation ruleset tag=0

00:51:56:regxrule_profile_match:Error:ruleset for alleged cardinal not found

00:51:56:regxrule_profile_translate:No match:number=5108880101 type=unknown

plan=unknown

00:51:56:regxrule_stack_push_RegXruleNumInfo:stack=0x63DECAF4; count=1

Following “regxrule_dp_translate”, the achievement indicates that there is no

translation contour for approachable direction, and again it prints the

numbers beatific to the approachable account provider interface (SPI).

00:51:56:regxrule_dp_translate:No contour begin in associate 5108888 for

outgoing direction

00:51:56:regxrule_dp_translate:calling_number=5551212 calling_octet=0x0

called_number=5108880101 called_octet=0x80

redirect_number= redirect_type=4294967295 redirect_plan=4294967295

00:51:56:regxrule_stack_pop_RegXruleNumInfo:stack=0x63DECAF4; count=2

00:51:56:regxrule_stack_push_RegXruleNumInfo:stack=0x63DECAF4; count=1