Table of Contents

I Tables To Know

-Stdprtct

-fgd1

-spr2

-bk27

-sal1

-many customers with private dialing plans (vpn)

-Inwtrans

-Iexclude

-0

-200

-Hnpacont

-sub hnpacode

-sub rteref

-Clli

-Cllicdr

-Cllimtce

-Trkgrp

-Trksgrp

-Trkmem

-Authcodu

-Acscrn2

-Ltcpsinv

-Carrmtc

-Special isdn tables and sample data-fill

-ltdef

-ltmap

-ltcalls

-callattr

-checking iid in table ltcpsinv

-Aniscusp

II Commands To Know

-Format pack

-Profiles

-listsf all

-printing a file

-reading a file

-adding profile to login

-Traver

-short

-long

-Cdr search

-searching via web page

-regular active file

-regular active file by block

-searching retired file

-Omshows

-trk

-ds1carr

-Carrier level

-Pradch level

-Clliref search

-Account codes

-qacct list xx

-qacct idx xx

III Things To Know

-Login

-ip address

-Manuals

-post on trk

-observe state (idl, mb, inb, rmb, lo, sb)

-lockouts being caused by trunk-conditioning

-Check for winks

-Doing ICOT and CVTESTs for SS7 trunks

-Checking lexm

-Tpart

-Resporg

-Fm

-Helmsman

-Checking for loops on t1 carrier

-loss e

-checking omshows for glare

-Recordings

-Treatments

-N00test and lds database

-Reroutes to pots#

-Change dnis

-Deluxe data re-route

-Ani delivery option

-Hset

-Outpulsing on trk

-Digit grabber to verify dnis

-Must have dnis on isdn-pri trkgrp

TABLE STDPRTCT (STanDard PRe-Translator ConTrol)

This is the first table that the DMS250 uses for translations. Each trunk-group in the DMS250 is assigned a standard pre-translator. When an incoming call enters the switch on a trunk-group, the switch checks the standard pre-translator assigned to that trunk-group and matches the digits dialed to the appropriate tuple in that table. Almost every toll-free number that enters the Milwaukee DMS250 will enter the switch on trunk-groups that use a standard pre-translator of 'fgd1', 'spr2', or 'bk27'. This table basically hands the call off to another table or process within the switch. The vast majority of toll-free calls will be handed off to TABLE INWTRANS where a manual routing entry is placed. A very small percentage of calls are handed off to SACREMOT which instructs the DMS250 to query a remote database in Monroe, LA for further routing information.

It is important to note how the FROMDIGS and TODIGS fields work in the DMS tables. It is best to imagine all entries in both fields are expanded to 10 digits. Any missing digits on the FROMDIGS are padded to be '0's and any missing digits on the TODIGS are padded with '9's. So, for example (this is not an actual tuple in the switch),

>pos 855700

FROMDIGS TODIGS PRETRTE

-----------------------

855700 855700 ES INWTRANS 10 10 0 $

really means that any digits dialed between 8557000000 and 8557009999 will cause the switch to send all 10 digits of the dialed number to TABLE INWTRANS for further routing information.

Here is a list of 6 actual tuples from the Milwaukee DMS250:

>table stdprtct

TABLE: STDPRTCT

>pos fgd1

FGD1 (1) (0)

>sub stdprt

WARNING: CHANGES IN TABLE STDPRT MAY ALTER OFFICE

BILLING. CALL TYPE DEFAULT IS NP. PLEASE REFER TO

DOCUMENTATION.

>pos 8002363013

8002363013 8002364346 ES INWTRANS 10 10 0 $

>lis 5

FROMDIGS TODIGS PRETRTE

-----------------------

8002369269 8002369269 ES SACREMOT $

800236927 80023696 ES INWTRANS 10 10 0 $

8002369701 8002369790 ES INWTRANS 10 10 0 $

8002369791 8002369793 ES SACREMOT $

8002369794 8002369795 ES INWTRANS 10 10 0 $

>

Some customers have a custom built standard-pretranslator placed on their dedicated trunk-group. This is usually referred to as a VPN (Virtual Private Network) or on-net dialing plan. Some customers who have different locations that all have trunk-groups into the same switch have dialing-plans setup so they can do 4-digit dialing between sites without needing tie lines or needing to send the calls through their local lines.

Note that this is a very powerful table and most people don't have access to change it. There is a good reason for this, since an error in this table can cause massive amounts of traffic to be mis-routed. Be very careful!

TABLE INWTRANS

Most toll-free traffic from the standard-pretranslators are forwarded onto TABLE INWTRANS where manual routing entries are located. The manual routing entries in this table are very simple.

• Terminating a toll-free number to a POTS#:

1. The switch locates the dialed number in TABLE INWTRANS.

2. The switch checks the IEXCINDX field to see if any incoming calls should be blocked.

In switch-24, you will usually only see '0' or '200' in the IEXCINDX field.

'0' means do not block the call no matter where it originated from.

'200' means to block the call if it originated in Canada.

For more information on this, refer to TABLE IEXCLUDE.

1. The switch translates the originally dialed toll-free number to the POTS# located in the TRANSDIG field.

2. From this point on, the call is handled as if a regular (non-toll-free) number was dialed.

3. All POTS# translations are handled in STS (Serving Translation Scheme) 001 and, so, the STS field must be set to '001'.

Example:

>table inwtrans

>pos 8002363013

INWATDIG IEXCINDX STS TRANSDIG EFTINDEX OPTIONS

-----------------------------------------------

8002363013 0 001 4142246700 0 $

• Terminating a toll-free number to a dedicated trunk-group:

1. The switch locates the dialed number in TABLE INWTRANS.

2. The switch checks the IEXCINDX field to see if any incoming calls should be blocked.

In switch-24, you will usually only see '0' or '200' in the IEXCINDX field.

'0' means do not block the call no matter where it originated from.

'200' means to block the call if it originated in Canada.

For more information on this, refer to TABLE IEXCLUDE.

1. A '$' will be located in the TRANSDIG field because we need the originally dialed toll-free number to be sent to another table for further translations.

2. The switch sends the originally dialed toll-free number to the appropriate STS.

3. In Switch 24, dedicated toll-free translations are located in STS 800, 802, 803, 805, 807, 808 and 855.

Example:

>table inwtrans

>pos 8002616733

INWATDIG IEXCINDX STS TRANSDIG EFTINDEX OPTIONS

-----------------------------------------------

8002616733 0 800 $ 0 $

TABLE IEXCLUDE

This table contains the indices that one can place in TABLE INWTRANS to block incoming toll-free numbers based on the originating NPAs. IEXCINDX 200 is used to block incoming calls from Canada. It does this by placing all Canadian NPAs in the index.

For example:

>table iexclude

>pos 200

IEXCINDX IEXCNPAS

-----------------

200 (17)

>sub iexcnpas

>lis all

NPA IEXCSTAT IEXCNXXS

---------------------

204 BLOCKED (0)

250 BLOCKED (0)

306 BLOCKED (0)

403 BLOCKED (0)

416 BLOCKED (0)

418 BLOCKED (0)

506 BLOCKED (0)

514 BLOCKED (0)

519 BLOCKED (0)

604 BLOCKED (0)

613 BLOCKED (0)

705 BLOCKED (0)

709 BLOCKED (0)

807 BLOCKED (0)

819 BLOCKED (0)

902 BLOCKED (0)

905 BLOCKED (0)

BOTTOM

>

TABLE HNPACONT (Home Numbering Plan Area CONTrol)

SUB HNPACODE (Home Numbering Plan Area CODE)

SUB RTEREF (RouTE REFerence)

TABLE HPNACONT contains the STSs (Serving Translation Schemes) which the DMS uses to route blocks of numbers to route references, which in turn contain your route choices. Keep in mind that each STS is completely independent of each other. This means that STS 001 has its own SUBtable HNPACODE and RTEREF. Likewise, STS 800 has its own SUBtable HNPACODE and RTEREF. STS 001 contains all POTS# translations. Only routing should change STS 001.

For Example:

>table hnpacont

>pos 800

800 Y 1023 0 (905) (1) (0) $

>sub hnpacode

>pos 8002616733

FROMDIGS TODIGS CDRRTMT

-----------------------

8002616733 8002616733 FRTE 948

>ret

800 Y 1023 0 (905) (1) (0) $

>sub rteref

>pos 948

948 (N D MIEMILWX75SI 10 6700 N) $

From our previous example we saw that TABLE INWTRANS told 8002616733 to go to STS 800. Once inside STS 800, the DMS goes into the SUBtable HNPACODE and sees which tuple contains that number. In this example, all numbers from 8002616733 to 8002616733 (in other words only that one number) are sent to FRTE (Foreign RouTE) 948. The DMS leaves this SUBtable (a human does this by typing 'ret' or 'return') and goes into SUBtable RTEREF. Once inside this SUBtable, the switch looks for FRTE 948. The FRTE contains the route choices. In this example, there is only one route choice. There are many ways the route references can be built, but this example contains the most common way. A closer look into this route reference is needed to see what is happening.

(N D MIEMILWX75SI 10 6700 N)

N = non-standard digit manipulation is going to be used

D = this field is not used so must be datafilled to D

MIEMILWX75SI = the CLLI to which translations is routed

10 = the digits deleted (so all 10 digits of the originally dialed

number are deleted, note the digits are removed from the beginning of

the dialed number)

6700 = the digits prefixed (since all 10 digits were removed, and 6700 was

prefixed, that means the DMS will send '6700' to the customer's trunk-

group as DNIS digits)

N = not used in the DMS250, so N must be entered to satisfy the switch

A few more examples of route references follow.

Example 1:

(N D MDEHOCAWC1SC 10 5599 N)(RT 001 DD NLCL 6083557956 N N $) $

In this example, there are 2 entries in the route reference. The first one causes the switch to outpulse '5599' to the customer's dedicated trunk-group MDEHOCAWC1SC. If the

first route choice is busy or failed for whatever reason, all of the calls will overflow to the next choice. The next choice in this case is overflow to a pots# of 6083557956. Note, the DMS actually does this by changing the number to 6083557956 and sending it to STS 001.

Example 2:

(N D MDECHMPIM2SC 10 N N) (TRMT BUSY) $

In this example, the switch deletes all 10 digits of the dialed number and sends the call to the customer. Since the terminating trunk-group happens to be loop-start, we do not send DNIS. If the first route choice is busy or failed for whatever reason, the switch treats the call as a regular busy. Note, loop-start and ground-start trunk-groups don't outpulse DNIS digits to CPE.

Example 3:

(N D MDECHAMB11SO 6 N N) (RT 001 DD NLCL 6087522723 N 0 $) $

In this example, the dialed number has the first six-digits removed and nothing else prefixed to the number, therefore, the last four digits are outpulsed as DNIS to CPE. If the first route choice is busy or failed for whatever reason, the call overflows to a pots# of 6087522723.

Example 4:

(N D MDIISDNI11SC 0 N N) (N D MDIISDNI13SC 0 N N) (N D MDIISDNI16SC 0 N N) (TRMT BUSY) $

In this example, there are three route-choices before the call is treated with a busy signal. In this case, since '0' digits are removed, all 10 digits sent to CPE.

TABLE CLLI

When creating a new CLLI in the switch, this table is always the first to be datafilled. It contains the CLLI's ADNUM which is pretty much only used by the switch when sorting reports. It also contains a field which specifies the maximum size of the trunk-group. If the customer ever decides to increase the size of their trunk-group, this field will usually have to be manually increased. The final field is the ADMININF field which contains any text you may wish to add to be helpful, such as circuit Ids, address, etc.

>table clli

>pos plexus_3463

CLLI ADNUM TRKGRSIZ ADMININF

----------------------------

PLEXUS_3463 231 24 PLEXUS

TABLE CLLIMTCE

When one creates the tuple in TABLE CLLI, a corresponding tuple in TABLE CLLIMTCE is automatically created. This contains the SCLLI (short clli) which can be used in the 'manual' level of the switch as a short-cut to post the trunk-group. It also contains the thresholds for minor, major and critical alarms. So, in this example, if 75% or more of the trunks were failed, this would be considered a critical alarm. Likewise, if 50-74% of the trunks were failed, it would be considered a major alarm.

>table cllimtce

>pos paychex_1949

CLLI SCLLI MINALM MAJALM CRITALM SYNCTYPE TSTNOIND MWIDX SIGTST PRFXDIGS DIAGDATA

------------------------------------------------------------------------

PAYCHEX_1949 S1949 25 50 75 NSS 0 0 N N (24)

TABLE CLLICDR

This table maps the trunk-group number to the CLLI. On all of the CDRs that the switch creates (and eventually downloaded by the billing department) it is the trunk-group number that is on the CDR, not the CLLI. This value is also how the trunk-group is tracked in LEXM.

>table cllicdr

>pos FABCO_1700

CLLINAME EXTNUM

---------------

FABCO_1700 1700

TABLE TRKGRP

This defines settings that, obviously, affect the entire trunk-group. These include the type of trunk-group, level-padding, selection sequence, authorization code, bearer capability and many other options.

Example:

>table trkgrp

>pos mderobert1sc

MDEROBERT1SC DAL 0 9IN04 NCRT 0 2W SAL1 MIDL 40 7 40 16 C 7 NIL NIL 0 4 1

NONE 414 0 749211 NONE 0 SPEECH N STANDARD 0 N Y NONE 00 160 (OPNOAUTH ) $

This example defines this trunk-group as a DAL trunk-group (Dedicated Access Line). Other types of trunk-groups include EANT (Equal Access Network Trunk-group is equivilant to a feature-group D trunkgroup), IMT, ISDN, etc.

The field '9IN04' defines the padding for this trunk-group. TABLE PADDATA creates is where these 'pad groups' are defined. The DMS uses the 'pad group' of the incoming and outgoing trunk-group to determine the loss in dB of the call. This is what is used to adjust the signal strength of the talk path. It also can be a useful tool to control echo.

SAL1 is the standard pre-translator used for this trunk-group. SAL1 is used on the majority of dedicated trunk-groups. It provides a generic dialing-plan that is acceptable for the majority of our customers. Remember, some customers use a custom-built standard pretranslator which allows them to do special things including 4 digit dialing to another dedicated trunk-group within the same switch.

MIDL is the selection sequence. This means that when the DMS sends a call to the customer's trunk-group, it will always select the Most IDLe trunk in the trunk-group. Other options include LIDL (Least IDLe), ASEQ, DSEQ, etc.

749211 is the authorization code. If the customer wants account codes, then the index containing the account codes is found within the authorization code definition. The authorization code is defined in TABLE AUTHCODU.

SPEECH is the bearer capability of the trunk-group. This means that only SPEECH grade calls can originate and terminate on this trunkgroup. SPEECH includes regular voice-grade, fax and modem calls. Other options include 56KDATA, 64KDATA, VOICE_DATA, etc.

A popular option that you'll see at the end of some trunk-groups is ACPROMPT which simply provides an audible account-code prompt to the customer. Another one is CPIALLOW CPNPREF which causes the DMS to outpulse the ANI to the CPE. When this option is enabled, the DMS will outpulse: * ANI * DNIS * .

TABLE TRKSGRP

This is where the signalling is defined. Each trunk-group can have up to two sub-groups. This includes sub-group 0 and sub-group 1. But, since usually all trunk-members within a trunk-group share the same signalling, sub-group 0 is usually the only one datafilled. Some types of signalling include loop-start, ground-start, E&M wink, E&M immediate, SS7, ISDN-PRI etc.

Examples:

>table trksgrp

>pos mderobert1sc 0

SGRPKEY CARDCODE SGRPVAR SGRPVAR

--------------------------------

MDEROBERT1SC 0 FXSLS STD 2W DT LS N 15 11 DT LS 7 0 N NO NO N N N M 75 UNEQ $

MDEMEINMN1SC 0 FXSGS STD 2W DT GS N 15 11 DT GS 7 0 Y NO NO N N N M 75 UNEQ $

MDEVBMDMD1SC 0 DS1SIG STD 2W DT WK N 15 11 DT WK 7 0 Y NO NO N N N M 75 UNEQ $

MDEHVTSPR1SC 0 DS1SIG STD 2W DT IM N 15 11 DT IM 7 0 Y NO NO N N N M 75 UNEQ $

MC7DALLAS1TC 0 DS1SIG C7UP 2W N N UNEQ ACTIVEA UCP THRH 11 ROCHAC $ NIL SGRPYLD Y

MDIDDMWWI2SC 0 DS1SIG ISDN 15 11 87Q931 2 N STAND NETWORK PT_PT LOCALEO N

UNEQ 255 N DEFAULT DTCI 39 5 24 64K HDLC $ $

These examples define sub-group 0 as loop-start, ground-start, E&M wink-start, E&M immediate, SS7 and ISDN-PRI respectively.

TABLE TRKMEM

This table defines the trunk-members, or sometimes just called trunks or ports. This definition tells the switch where the trunk-member is going to 'live' in the switch and which sub-group you want the trunk to belong to. Remember that you can add a trunk-member to sub-group 0 or sub-group 1.

Example:

>table trkmem

>pos mderobert1sc 1

MDEROBERT1SC 1 0 DTC 0 5 7

>lis 6

CLLI EXTRKNM SGRP MEMVAR

------------------------

MDEROBERT1SC 1 0 DTC 0 5 7

MDEROBERT1SC 2 0 DTC 0 5 20

MDEROBERT1SC 3 0 DTC 0 5 21

MDEROBERT1SC 4 0 DTC 0 5 22

MDEROBERT1SC 5 0 DTC 0 5 23

MDEROBERT1SC 6 0 DTC 0 5 24

The fields in this table are: CLLI, member number, sub-group number and then where you want the trunk to 'live' in the switch.

TABLE AUTHCODU

This table defines the attributes of the authorization code. The authorization code is then usually assigned to the trunk-group. The authorization code could be used for billing purposes if the billing department wanted, but we pretty much just use it for accounting codes on customer's dedicated trunk-groups.

To locate the authorization code in TABLE AUTHCODU, you must post on "A" + the authorization code.

Example:

If the authorization code from table trkgrp is 394929, then you can view it by typing:

>table authcodu

>pos A394929

AUTHCODE STATUS ACCTLEN ACSCRIDX OPART TPART PINDIGS MLTCOSID HOTLINE PVSINDEX SATRES FLDONLY AUTHTRAP ACCTVAL SPLASHBK TRVALLOW PININDEX PINLEN OPTIONS

--------------------------------------------------------------------------

A394929 VALID 0 0 1 1 0 30 $ 0 N Y N N 0 Y 0 0 $

VALID tells us that this code is valid and the next '0' tells us that the length of account code is '0' digits. In other words there are no account codes.

Example:

A396544 VALID 5 0 1 1 $ 1 $ 0 N N N N 0 Y 0 0 $

This example has 5 digit non-verified account codes. The field 'ACCTVAL' is either Y or N. Since this example has it data-filled as N, then these codes are not verified.

Example:

A400165 VALID 2 121 1 1 $ 1 $ 0 N N N Y 0 Y 0 0 $

This example has 2 digit verified account codes. Index 121 contains a list of all valid account-codes.

TABLE ACSCRN2

This table contains the account-codes that each index contains. It is a very simple table.

From the example above, 12 is a valid account-code under index 121.

Example:

>table acscrn2

>pos 121 12

DBIDX

-----

121 12

TABLE LTCPSINV (Line Trunk Controller P-Side Inventory)

This table determines the line coding and framing of each T1 port in the DMS. A DTC (Digital Trunk Controller) can handle 20 T1 ports. Keep in mind that ISDN-PRIs must be defined on DTCIs. These 20 ports are counted from 0-19.

'Profiles' are created in TABLE CARRMTC and this profile is assigned to the T1 port in TABLE LTCPSINV. Each DMS can be setup differently, but in the Milwaukee DMS250:

Coding/Framing Profile Name

AMI/D4 DEFAULT or AMI

B8ZS/D4 B8ZS

B8ZS/ESF EB8ZS

>table ltcpsinv

>pos dtc 35

DTC 35 N (0 DS1 B8ZS N) (1 DS1 EB8ZS N) (2 DS1 EB8ZS N)

(3 DS1 EB8ZS N) (4 DS1 DEFAULT N) (5 DS1 DEFAULT N)

(6 DS1 DEFAULT N) (7 DS1 DEFAULT N) (8 DS1 DEFAULT N)

(9 DS1 DEFAULT N) (10 DS1 DEFAULT N) (11 DS1 DEFAULT N)

(12 DS1 DEFAULT N) (13 DS1 DEFAULT N) (14 DS1 EB8ZS N)

(15 DS1 DEFAULT N) (16 DS1 B8ZS N) (17 DS1 EB8ZS N)

(18 DS1 DEFAULT N) (19 DS1 EB8ZS N) $

>

For DTCIs, the table looks a bit different. The IID (Interface Identifier) is also defined in this table for ISDN-PRIs. The IID is just a tag used to identify which T1 is which in an ISDN-PRI trunk-group that contains multiple T1 carriers. The IIDs start at 0 and for each additional span in that trunk-group, the number increments. For example, if there were 3 T1s in an ISDN-PRI trunk-group, all 3 spans must be on the same DTCI and would have IIDs of 0,1 and 2 respectively. DTCIs do not support SS7 trunks, but can handle regular in-band type trunk-groups (although that wouldn't be an efficient use of a DTCI).

>table ltcpsinv

>pos dtci 39

DTCI 39 N (0 DS1PRA EB8ZS N 0 NIL $) (1 DS1PRA DEFAULT N 0 NIL $)

(2 DS1PRA EB8ZS N 0 NIL $) (3 DS1PRA DEFAULT N 0 NIL $)

(4 DS1PRA EB8ZS N 0 NIL $) (5 DS1PRA EB8ZS N 0 NIL $)

(6 DS1PRA EB8ZS N 1 NIL $) (7 DS1PRA EB8ZS N 0 NIL $)

(8 DS1PRA 64K N 0 NIL $) (9 DS1PRA EB8ZS N 1 NIL $)

(10 DS1PRA EB8ZS N 0 NIL $) (11 DS1PRA EB8ZS N 0 NIL $)

(12 DS1PRA EB8ZS N 0 NIL $) (13 DS1PRA EB8ZS N 0 NIL $)

(14 DS1PRA EB8ZS N 0 NIL $) (15 DS1PRA EB8ZS N 0 NIL $)

(16 DS1PRA EB8ZS N 0 NIL $) (17 DS1PRA EB8ZS N 2 NIL $)

(18 DS1PRA EB8ZS N 0 NIL $) (19 DS1 AMI N) $

TABLE CARRMTC

This table creates the 'profiles' that are used in TABLE LTCPSINV. It creates a name for the profile and then defines the card type, line coding, framing, acceptable alarm thresholds and a few other characteristics. In the Milwaukee DMS250, the standard settings for a DTC are:

DTC DEFAULT 255 255 DS1 NT6X50AA MU_LAW SF ZCS BPV NILDL N 250 1000 50 50

150 1000 3 6 864 100 17 511 4 255

DTC AMI 255 255 DS1 NT6X50AB MU_LAW SF ZCS BPV NILDL N 250 1000 50 50 150

1000 3 6 864 100 17 511 4 255

DTC B8ZS 255 255 DS1 NT6X50AB MU_LAW SF B8ZS BPV NILDL N 250 1000 50 50 150

1000 3 6 864 100 17 511 4 255

DTC EB8ZS 255 255 DS1 NT6X50AB MU_LAW ESF B8ZS BPV NILDL N 250 1000 50 50

150 1000 3 6 864 100 17 511 4 255

If the DTC is using integrated echo-canceller cards, then the profiles are:

DTC X50EC_AMI 255 255 DS1 NT6X50EC MU_LAW SF ZCS BPV NILDL N 250 1000 50 50

150 1000 3 6 864 100 17 511 4 255 NETWORK

DTC X50EC_B8ZS 255 255 DS1 NT6X50EC MU_LAW SF B8ZS BPV NILDL N 250 1000 50

50 150 1000 3 6 864 100 17 511 4 255 NETWORK

DTC X50EC_EB8ZS 255 255 DS1 NT6X50EC MU_LAW ESF B8ZS CRC NILDL N 250 1000 50

50 150 1000 3 6 864 100 17 511 4 255 NETWORK

For DTCIs, the profiles are:

DTCI DEFAULT 255 255 DS1 NT6X50AB MU_LAW SF B8ZS BPV NILDL N 250 1000 50 50

150 1000 3 6 864 100 17 511 4 255

DTCI EB8ZS 255 255 DS1 NT6X50AB MU_LAW ESF B8ZS BPV NILDL N 250 1000 50 50

150 1000 3 6 864 100 17 511 4 255

• You may have other definitions in TABLE CARRMTC that basically do the same thing except use a different 'profile name'.

ISDN SPECIFIC TABLES and DATAFILL EXAMPLE

ISDN-PRI trunk-groups use a few unique tables in the DMS250. Here is sample data-fill for an ISDN-PRI trunk-group.

Table clli:

MDIISDNIV4SC 437 23 414_224_S_N_N_N_WI

Table cllicdr:

MDIISDNIV4SC 2663

Table trkgrp:

MDIISDNIV4SC PRA250 36 IN04 NCRT UCS MIDL NIL 0 414 (ISDN 6) $ 0 4 VOICE_DATA 160 (RLT ) $

Table trksgrp:

MDIISDNIV4SC 0 DS1SIG ISDN 15 11 87Q931 2 N YIELD NETWORK PT_PT LOCALEO N

UNEQ 100 Y DEFAULT DTCI 40 3 24 64K HDLC $ $

Table ltdef:

ISDN 6 B PRA 46 46 23 23 NTNAPRI V1 NIL (NOPMD ) $

Table ltcalls:

ISDN 6 PUB XLAIEC 2 $ $

ISDN 6 PVT XLAIEC 2 $ $

Table callattr:

2 UCS SAL1 0 NONE 1 AUTH 0 172132 0 4142747500 (ANIDELV CPNPREF) $

Table ltmap:

ISDN 6 CLLI MDIISDNIV4SC (TEI 0) $

Table cllimtce:

MDIISDNIV4SC S2663 25 50 75 NSS 0 0 N N (23)

Table trkmem:

MDIISDNIV4SC 1 0 DTCI 40 3 1

MDIISDNIV4SC 2 0 DTCI 40 3 2

MDIISDNIV4SC 3 0 DTCI 40 3 3

MDIISDNIV4SC 4 0 DTCI 40 3 4

MDIISDNIV4SC 5 0 DTCI 40 3 5

MDIISDNIV4SC 6 0 DTCI 40 3 6

MDIISDNIV4SC 7 0 DTCI 40 3 7

MDIISDNIV4SC 8 0 DTCI 40 3 8

MDIISDNIV4SC 9 0 DTCI 40 3 9

MDIISDNIV4SC 10 0 DTCI 40 3 10

MDIISDNIV4SC 11 0 DTCI 40 3 11

MDIISDNIV4SC 12 0 DTCI 40 3 12

MDIISDNIV4SC 13 0 DTCI 40 3 13

MDIISDNIV4SC 14 0 DTCI 40 3 14

MDIISDNIV4SC 15 0 DTCI 40 3 15

MDIISDNIV4SC 16 0 DTCI 40 3 16

MDIISDNIV4SC 17 0 DTCI 40 3 17

MDIISDNIV4SC 18 0 DTCI 40 3 18

MDIISDNIV4SC 19 0 DTCI 40 3 19

MDIISDNIV4SC 20 0 DTCI 40 3 20

MDIISDNIV4SC 21 0 DTCI 40 3 21

MDIISDNIV4SC 22 0 DTCI 40 3 22

MDIISDNIV4SC 23 0 DTCI 40 3 23

A few things special about ISDN-PRI circuits:

• TABLE LTDEF defines the D-channel protocol. The choices are:

• U449PRI (also known as AT&T 4ess protocol)

• U459PRI (also known as AT&T 5ess protocol)

• NTNAPRI (also known as Nortel DMS protocol)

• NI (also known as National ISDN, the Milwaukee DMS250 does not support this)

• If the customer has a Nortel SL1 switch, then be sure to use the SL1PROFL.

• The authorization code is located in TABLE CALLATTR.

• It is best to data-fill both PUB (public) and PVT (private) tuples in TABLE LTCALLS.

• The bearer capability should be set to VOICE_DATA in TABLE TRKGRP. This allows customers to originate and terminate speech (speech includes voice, fax and modem calls) and 64KDATA calls on their trunk-group.

• Toll-free traffic that terminates to an ISDN-PRI trunk-group must have DNIS. Otherwise the calls will fail to treatment 68 (feature_not_allowed)

• If there is more than one T1 in the ISDN-PRI trunk-group, then all T1s must be on the same DTCI.

• The IID (Interface Identifiers) must be properly assigned in TABLE LTCPSINV (0,1,2..etc).

• If a back-up d-channel is desired, it will be defined in TABLE TRKSGRP.

• Usually if the CPE is a NORTEL product, the GLARE field should be set to STAND, otherwise it should be set to YIELD.

• The T1 carriers are usually setup as B8ZS/ESF and the d-channels are usually 64 Kb/s.

TABLE ANISCUSP

This is where all of the ANIs are kept and verified in the DMS. The Milwaukee DMS250 is not a casual switch, so the ANI must be properly datafilled in TABLE ANISCUSP otherwise switched customers will receive a "MESSAGE 101" recording which is due to ANI Database Failure.

For Example:

>pos 2622503080;lis 10

2622503080 SUB AL 3 Y 3_1KHZ 1 1 N 0 0 $ 1 ALWAYS (ACCTIDX 3287) $

KEY ANITYPE REFAREA

-------------------

2622503080 SUB AL 3 Y 3_1KHZ 1 1 N 0 0 $ 1 ALWAYS (ACCTIDX 3287) $

2622503081 SUB AL 3 Y 3_1KHZ 1 1 N 0 0 $ 1 ALWAYS (ACCTIDX 3287) $

2622503082 SUB AL 3 Y 3_1KHZ 1 1 N 0 0 $ 1 ALWAYS (ACCTIDX 3287) $

2622503083 SUB AL 0 N 3_1KHZ 1 1 N 0 0 $ 1 ALWAYS $

2622503084 SUB AL 3 Y 3_1KHZ 1 1 N 0 0 $ 1 ALWAYS (ACCTIDX 3287) $

2622503085 SUB AL 3 Y 3_1KHZ 1 1 N 0 0 $ 1 ALWAYS (ACCTIDX 3287) $

2622503086 SUB AL 3 Y 3_1KHZ 1 1 N 0 0 $ 1 ALWAYS (ACCTIDX 3287) $

2622503087 SUB AL 3 Y 3_1KHZ 1 1 N 0 0 $ 1 ALWAYS (ACCTIDX 3287) $

2622503088 SUB AL 3 Y 3_1KHZ 1 1 N 0 0 $ 1 ALWAYS (ACCTIDX 3287) $

2622503089 SUB AL 3 N 3_1KHZ 1 1 N 0 0 $ 1 ALWAYS $

>pos 2622508976;lis 10

2622508976 SUB DA 0 N 3_1KHZ 1 1 N 0 0 $ 1 ALWAYS $

KEY ANITYPE REFAREA

-------------------

2622508976 SUB DA 0 N 3_1KHZ 1 1 N 0 0 $ 1 ALWAYS $

2622508977 SUB DA 0 N 3_1KHZ 1 1 N 0 0 $ 1 ALWAYS $

2622508978 SUB DA 0 N 3_1KHZ 1 1 N 0 0 $ 1 ALWAYS $

2622508979 SUB AL 0 N 3_1KHZ 1 1 N 0 0 $ 1 ALWAYS $

2622509171 SUB AL 0 N 3_1KHZ 1 1 N 0 0 $ 1 ALWAYS $

2622509252 SUB AL 0 N 3_1KHZ 1 1 N 0 0 $ 1 ALWAYS $

2622509257 SUB AL 0 N 3_1KHZ 1 1 N 0 0 $ 1 ALWAYS $

2622509451 SUB AL 0 N 3_1KHZ 1 1 N 0 0 $ 1 ALWAYS $

2622509513 SUB AL 0 N 3_1KHZ 1 1 N 0 0 $ 1 ALWAYS $

2622509517 SUB AL 0 N 3_1KHZ 1 1 N 0 0 $ 1 ALWAYS $

Some important things to note are whether the tuple is AL or DA. AL causes the DMS to allow calls from this ANI, and the DA causes the DMS to disallow the call. This status should correspond to the status in LEXM. Also, this table determines whether there are no account codes, non-verified account-codes or verified account-codes. If there are verified account codes, it assigns the screening index to the ANI.

When displaying data in tables, the DMS unfortunately spreads the fields out in a very ugly manner. To view the fields in an easier to read format, use the FORMAT PACK command once inside a table.

>format pack

<line length>: 76 columns can be output per line.

<pack mode>: Pack mode is ON.

<indent column>: Indented lines will begin in column 1.

<first column>: The first column of output is column 1.

PROFILES

To save time in the DMS, one can add profiles to their login. So every time you login, the switch automatically reads a file which contains dozens of user-friendly shortcut commands. Once you are familiar with the full commands, any user can create their own shortcut commands and have the switch read them every time you login. To add a profile to your login type:

>listsf all [This command lists all files stored in the DMS]

COMMANDS

FILENAME

>

command qa(quit all)

command tsys(table dirpssys;pos occ;ver off)

command pris(mapci;mtc;trks;ttp;level pradch)

.

.

This list has been edited to save space

.

.

command dkt0(dskut;listvol d000par0 all)

command dkt1(dskut;listvol d010par1 all)

command par0(table dirppool;pos 57;cha 5 $;pos 57;cha 5 d000par0)

command par1(table dirppool;pos 57;cha 5 $;pos 57;cha 5 d010par1)

command kk(tgen 404 00)

>

TRAVER

This stands for TRAnslation VERification. When a call enters the switch on a specific trunk-group, this command will tell you where the translations will cause the call to terminate.

Example using the 'nt' (NO TRACE) option:

>traver tr MC7CHCGALCD8 8002616733 nt

STS USED FOR TRAVER IS: 800

DIGIT TRANSLATION ROUTES

1 MIEMILWX75SI 6700 ST

TREATMENT ROUTES. TREATMENT IS: GNCT

1 GNCTANN

2 T60

This example shows that when the DMS receives an incoming call of 8002616733 on trunk-group MC7CHCGALCD8, the call uses STS 800 and that there is only one route choice of MIEMILWX75SI with DNIS digits of 6700. If that route choice is busy, then the call fails to treatment of GNCT (Generalized No Circuit).

Example using the 't' (TRACE) option:

>traver tr MC7CHCGALCD8 8002616733 t

STS USED FOR TRAVER IS: 1

TABLE STSTOPAR

001 01 1

TABLE TRKGRP

MC7CHCGALCD8 EANT 26 IN06 NCOT 0 2W SPR2 MIDL 100 7 100 7 EQ27 7 7 414 UCS2EAEO

NIL 414 1 NONE 0 NONE 0 0 SPEECH 160 (CASUALU ) (ANIDIGS )

(TMANIDLV ALWAYS) (OPNOAUTH ) $

TABLE STDPRTCT

SPR2 ( 1) ( 0) 4

. SUBTABLE STDPRT

WARNING: CHANGES IN TABLE STDPRT MAY ALTER OFFICE

BILLING. CALL TYPE DEFAULT IS NP. PLEASE REFER TO

DOCUMENTATION.

. 800261 8002673725 ES INWTRANS 10 10 0 $

WARNING: CHANGES IN TABLE STDPRT MAY ALTER OFFICE

BILLING. CALL TYPE DEFAULT IS NP. PLEASE REFER TO

DOCUMENTATION.

TABLE INWTRANS

8002616733 0 800 $ 0 $

TABLE HNPACONT

800 Y 1023 0 ( 909) ( 1) ( 0) ( 0) 7 $

. SUBTABLE HNPACODE

. 8002616733 8002616733 FRTE 948

. SUBTABLE RTEREF

. 948 N D MIEMILWX75SI 10 6700 N

. EXIT TABLE RTEREF

EXIT TABLE HNPACONT

+++ TRAVER: SUCCESSFUL CALL TRACE +++

This example gives all tables used by the switch to determine translations.

CDR SEARCHES

The DMS250 is constantly generating CDRs that are being written to a billing file. When the active billing file reaches a certain size, that file is closed (or retired) and a new one is opened. Then the billing server automatically FTPs each retired billing file to the billing server where the number crunching occurs. Keeping this in mind, there are 4 different ways we'll go over locating CDRs to troubleshoot a problem. Also keep in mind that the 'cda' short-cut command is equivilant to typing:

mapci nodisp;mtc;appl;oamap;fcdrsrch

1 Searching a retired file via the IOMENU web page.

-Select 'CDR SEARCH' from the OPTIONS drop-down menu.

-Select 'OCC' from BILLING TYPES drop-down menu. OCC is the type of billing file used

for long-distance CDRs in the DMS switch.

-Select 'mks.0024' from LOCATIONS drop-down menu.

-Click on SUBMIT.

-Everything beyond this point is self-explanatory.

-Keep in mind that you may have to do an ADVANCED SEARCH to narrow your search further.

2 Searching an active file inside the DMS250.

-One can search the entire active billing file. For example:

>cda

MAPCI:

MTC:

APPL:

OAMAP:

FCDRSRCH:

>srch occ act

waiting on file to open

waiting on file to open

successful file open

>setk dialedno 8002363013

>exec

SEARCH COMPLETE

====== ========

The search was successful!

Use the STATUS and DISPLAY commands to see the results.

>stat

Number of records searched = 116364

Number of records output = 1

>disp [this command will display all of the CDRs located]

3 Searching an active file inside the DMS250 using the 'BLOCK' command. This is used to pull CDRs from the DMS250 very quickly. This is handy when you have the customer on the line and they can make test calls immediately. If done correctly, one can find the CDR within seconds.

-Find out which block the active billing file is by typing 'ddirp'

[mapci nodisp;mtc;iod;dirp;query occ;time] For example:

>ddirp

MAPCI:

MTC:

IOD:

DIRP:

SSNAME SSNO SEQNO ROTATES POOLNO PARLPOOL EMERGENCY

OCC 7 1 1528 3 57 NO

REGULAR

FILE(S) STATE VOLUME RECCOUNT BLOCK E V V_B VLID FNUM FRN#

ACTIVE AVAIL D010OCC2 113149 9430 0 19 NO 2822 002A 3021

STANDBY1 AVAIL D020AMA0 0 0 0 16 NO 2840 0036 305C

PARALLEL

FILE STATE VOLUME BLOCK E V V_B VLID FNUM FRN#

B010317161151OCC AVAIL S01DPAR1 1146 0 5 NO 8446 0001 7062

Time is 16:57:11

>

-Have the customer complete a test call and then have them hang-up.

-Wait 30-60 seconds to guarantee the switch is completely finished creating the CDR.

-Since the customer placed a recent test call, we know it is in the active billing file

and it is AFTER block 9430 (as discovered by the 'ddirp' command).

-Enter the CDR level and search the active file after BLOCK 9430. For example:

>cda

MAPCI:

MTC:

APPL:

OAMAP:

FCDRSRCH:

>srch occ act

waiting on file to open

waiting on file to open

successful file open

>block 9430

>setk dialedno 8002363013

>exec

SEARCH COMPLETE

====== ========

The search was successful!

Use the STATUS and DISPLAY commands to see the results.

>stat

Number of records searched = 756

Number of records output = 1

>disp [this command will display all of the CDRs located]

4 Searching a retired file directly in the DMS250.

• Go into TABLE DIRPHOLD to locate recently retired billing files. For example:

>table dirphold

TABLE: DIRPHOLD

>lis all

TOP

HOLDNO SSYSNAME FILENAME VOLSER COUNT

------------------------------------------------------

96 OCC U010316180013OCC D000AMA3 77510

98 OCC U010317000019OCC D010OCC4 12435

99 OCC U010317060028OCC D000AMA0 132530

BOTTOM

>

• This will list all recently retired billing files, which volume they are inside, as well as how many records are in each file. The billing file name is actually the date and time that the file was opened. So, if we need to locate a call that was placed between midnight on 17 March 2001 and 05:59 am on 17 March 2001, we would need to search the file U010317000019OCC. This file is located inside volume D010OCC4.

• Go into DSKUT and list all of the files in the volume. For example:

>dskut;listvol D010OCC4 all

• Enter the CDR search level of the DMS250 by typing 'cda'

For example:

>cda

MAPCI:

MTC:

APPL:

OAMAP:

FCDRSRCH:

• Enter the file to be searched and then the search parameters. For example:

>srch U010317000019OCC ucs

waiting on file to open

waiting on file to open

successful file open

>setk dialedno 8002526246

>exec

SEARCH COMPLETE

====== ========

The search was successful!

Use the STATUS and DISPLAY commands to see the results.

>stat

Number of records searched = 703

Number of records output = 1

>disp [this command will display all of the CDRs located]

A few tips about pulling CDRs in the DMS250.

• The DMS250 in Milwaukee only allows two CDR searches at any given time. So as soon as you are done with your search, be sure to type 'quit all'.

• Toll-free traffic will only reach the Milwaukee DMS250 if the RESPORG is SDR01 and all of the CPs are set to TPART 4 and set to route back to itself. TPART 14 is also used to split Deluxe Data Traffic between the Milwaukee DMS250 and the Kansas City DMS500.

• If the toll-free number isn't reaching the Milwaukee DMS250, then SMS definitely needs to be checked and the record may need to be rebuilt.

• The DMS250 in Milwaukee only allow a maximum of 200 CDRs to be found on any given search. So be sure to be specific enough in your searches to find only the calls you need.

• One can use an asterisk as a wild-card. This is helpful since a lot of business customers dial from a pool of different lines which may use different ANIs. For example:

• setk anisp '414224*

• setk anisp '41422467*

• Failed calls, including ones that go to recordings or busy signals, should have a call duration of 0 seconds. So, when troubleshooting toll-free troubles, one may do this:

• setk dialedno '8002363013

• setk calldur '00000000

OMSHOWS

Omshows are used to hold office-measurements within the DMS. The command can be done on a trunk-group, ds1carrier, SS7 link and different pieces of hardware within the DMS. We are going to only be concerned with checking trunk-groups and ds1 carriers.

Example of OMSHOW on a trunk-group:

>omshow trk dayml mderobert1sc

TRK

CLASS: DAYML

START:2001/03/17 00:00:00 SAT; STOP: 2001/03/17 17:30:00 SAT;

SLOWSAMPLES: 630 ; FASTSAMPLES: 6300 ;

KEY (COMMON_LANGUAGE_NAME)

INFO (OM2TRKINFO)

INCATOT PRERTEAB INFAIL NATTMPT

NOVFLATB GLARE OUTFAIL DEFLDCA

DREU PREU TRU SBU

MBU OUTMTCHF CONNECT TANDEM

AOF ANF TOTU ANSWER

INVAUTH BLKCTRK MAXBU TRU2WIN

NCTPASS NCTFAIL ACCCONG NOANSWER

NPQUERY NPRESP NPBDRTF

941 MDEROBERT1SC

2W 6 6

45 5 2 59

0 0 0 0

0 0 122 0

0 0 59 40

0 0 122 57

0 0 30 37

0 0 0 0

0 0 0

NATTMPT is the number of calls the DMS250 send to the customer.

INCATOT is the number of calls the DMS250 received from the customer.

NOVFLATB is the number of calls that overflowed from this trunk-group to the next route

choice because all trunks in this trunk-group were busy or failed.

Refer to Helmsman Documentation for further information on each field.

Example of OMSHOW on a DS1CARRIER:

>omshow ds1carr dayml 'HOST DTC 68 2 C

DS1CARR

CLASS: DAYML

START:2001/03/17 00:00:00 SAT; STOP: 2001/03/17 18:00:00 SAT;

SLOWSAMPLES: 648 ; FASTSAMPLES: 6480 ;

INFO (DS1OMINF)

DS1LCGA DS1RCGA DS1LOF DS1SLP

DS1SBU DS1MBU DS1PBU DS1CBU

DS1BER DS1ES DS1SES DS1UAS

DS1AIS DS1ECF

1142

HOST DTC 68 2 C

0 0 0 0

0 0 0 0

0 0 0 0

0. 0

LCGA - Local Carrier Group Alarm (Red Alarm)

SBU - System Busy Usage

BER - Bit Error Rate Exceeded

AIS - Alarm Indication Signal (Blue Alarm or 'unframed all ones')

RCGA - Remote Carrier Group Alarm (Yellow Alarm)

MBU - Manual Busy Usage

LOF - Loss of Frame

SLP - Slip (caused by frequency deviations - have customer check timing source!)

Be sure that everything after the 'tick' mark is in CAPITOL LETTERS!

CHECKING THE DS1 CARRIER

To check the DS1 status on a DS1 port in the switch, type 'carriers' from the CI prompt. The 'carriers' short-cut command is equivilant to 'mapci;mtc;trks;ttp;carrier'. Then, post on the desired ds1 carrier. For example:

>carriers;post dtc 23 4

CM MS IOD Net PM CCS Trks Ext APPL

. . . . . . . . .

POST CLASS ML OS ALRM SYSB MANB UNEQ OFFL CBSY PBSY INSV

0 Quit_ TRUNKS 6 5 16 1 0 0 138 0 0 1419

2 Post_ TIMING 0 0 0 0 0 0 0 0 0 2

3 DS1

4 N CLASS SITE DTC CK D ALRM SLIP FRME BER ES SES STATE

5 Loop_ 0 TRUNKS HOST 23 4 C 0 0 < 1.0 0 0 INSV

6 Tst_ SIZE OF POSTED SET : 1

7 Bsy_

8 RTS_

9 OffL_

10 DispOpt_

11 Disp_

12 Next CARRIER:

13 POST:

14 Detail_

15

16

17

18

Time 11:38 >

Note the STATE. Currently this DS1CARRIER is in-service. Other states are MB (Manually Busy), SYSB-T (System-Busy means the T1 is in CGA Alarm), OFFL (Off-Line) etc.

Then, to see more options on this particular DS1CARRIER, typing 'dispopt 0' will give us:

DispOpt 0

NT6X50AA, VoiceLaw=MU_LAW, ff=SF, zlg=ZCS

berb=BPV, dlk=NILDL, iat=N, action=N

rtsml=255, rtsol=255, berml=1.0E-6, berol=1.0E-3

frameml=17, frameol=511, slipml=4, slipol=255

lcgast=250, lcgacl=1000, rcgast=50, rcgacl=50

aisst=150, aiscl=1000, es= 864, ses= 100

This gives us useful information such as ff (Framing Format: SF or ESF) and the zlg (Zero LoGic: either ZCS or B8ZS - NOTE, ZCS is the same as AMI line coding)

CHECKING THE D CHANNEL ON AN ISDN-PRI TRUNKGROUP

Type 'pris' at the CI prompt. This is the same as typing 'mapci;mtc;trks;ttp;level pradch'.

Then post on the d-channel by trunk-group by typing 'post gd CLLI'. For example:

>pris

>post gd MDIFSWAWI1SC

CM MS IOD Net PM CCS Trks Ext APPL

. . . . . . . . .

PRADCH

0 Quit POST DELQ BSYQ DIG

2 Post_ TTP 27-0621

3 CKT TYPE PM NO. COM LANG STA S R DOT TE RESULT

4 2W IS IS DTCI 67 1 24 MDIFSWAWI1SC D1 STB

5 DTCI 67 2 24 MDIFSWAWI1SC D2 INS R

6

7 BSY

8 RTS

9 SWACT

10

11 HOLD post gd MDIFSWAWI1SC

12 Next SHORT CLLI IS: S514

13 OK,CKT POSTED

14

15 CONT

16 LOOPBK

17

18 LEVEL_

Time 12:23 >

This tells us that this trunk-group has 2 d-channels (D1 and D2). Only one d channel can in-service at a time, the other is in stand-by mode. Besides INS (In Service) and STB (Stand-by), you may see the d-channel in LO (lock-out), this is usually caused by protocol mis-match or by the CPE being faulty. The DMS's T1 port could also be faulty. When having d-channel problems, it is best to verify options between the DMS and the CPE and if still having trouble, then put an ISDN-PRI protocol analyzer on the d-channel and check for proper messaging between the DMS and CPE.

CLLIREF SEARCH

This command is used to find all tuples that contain a particular CLLI. You can also narrow down the search to a specific table. For example, to find all of the tuples inside TABLE HNPACONT that contain the CLLI of MDEROBERT1SC, type:

>clliref search mderobert1sc hnpacont

CLLI "MDEROBERT1SC" occurs in the following tuples:

Table Key: Sub Tuple

-------- -------> --------------------------------------------------------

HNPACONT 800: RTEREF

86 (N D MDEROBERT1SC 10 N N)

(RT 001 DD NLCL 9208722281 N 0 $) $

MDEROBERT1SC occurs in 1 tuples in table HNPACONT

If we wanted to find ALL tuples in the switch, do not include a table name after the CLLI.

For Example:

>clliref search mderobert1sc

CLLI "MDEROBERT1SC" occurs in the following tuples:

Table Key: Sub Tuple

-------- -------> --------------------------------------------------------

CLLI MDEROBERT1SC 941 12 920_872_S_N_N_N_WI

TRKGRP MDEROBERT1SC DAL 0 9IN04 NCRT 2W SAL1 MIDL 40 7 40 16 C

7 NIL NIL 0 4 1 NONE 414 0 749211 NONE 0 SPEECH N

STANDARD 0 N Y NONE 00 160 (OPNOAUTH ) $

CLLICDR MDEROBERT1SC 941

TRKSGRP MDEROBERT1SC 0 FXSLS STD 2W DT LS N 15 11 DT LS 7 0 N NO

NO N N N M 75 UNEQ $

TRKMEM MDEROBERT1SC 1 0 DTC 0 5 7

TRKMEM MDEROBERT1SC 2 0 DTC 0 5 20

TRKMEM MDEROBERT1SC 3 0 DTC 0 5 21

TRKMEM MDEROBERT1SC 4 0 DTC 0 5 22

TRKMEM MDEROBERT1SC 5 0 DTC 0 5 23

TRKMEM MDEROBERT1SC 6 0 DTC 0 5 24

TRKNAME 941 MDEROBERT1SC

TRKGRP1 MDEROBERT1SC DAL NPRT NOLOOK N Y Y 0 NIL 0 0

CLLIMTCE MDEROBERT1SC S941 25 50 100 NSS 0 0 N N (6)

HNPACONT 800: RTEREF

86 (N D MDEROBERT1SC 10 N N)

(RT 001 DD NLCL 9208722281 N 0 $) $

=====================

Total of 14

occurrences of MDEROBERT1SC

ACCOUNT CODES

For dedicated trunk-groups, the account-code index is assigned to the authorization code. Then the authorization code is assigned to the trunk-group. For a switched ANI, the account-code index is assigned directly to the ANI in TABLE ANISCUSP. The individual account-codes are assigned to the index in TABLE ACSCRN2. To find out what account-codes are inside a given index, there are 2 useful commands. If we know we are using account-code index 355, for example:

>qacct idx 355

Account Code Database Index : 355

Account Code Length : 3

Number of Acct Codes : 18

This tells us that index 355 contains 18 3-digit account codes.

>qacct list 355

Account Code Database Index : 355

Account Code Length : 3

Number of Acct Codes : 18

Entry : 111

Entry : 112

Entry : 113

Entry : 114

Entry : 115

Entry : 116

Entry : 117

Entry : 118

Entry : 222

Entry : 275

Entry : 345

Entry : 305

Entry : 432

Entry : 567

Entry : 678

Entry : 713

Entry : 789

Entry : 876

This lists all 18 of the account-codes contained within index 355.

LOGGING IN

Once a login is obtained through the appropriate channels, to login to the Milwaukee DMS250, just telnet to xxx.xxx.xxx.xxx and enter your login and password.

MANUAL LEVEL

At the MANUAL level of the DMS, one can check the status of individual trunks, obvserve incoming calls. One can also direct select a trunk and outpulse digits on it. Type the short-cut command 'manuals' at the CI prompt. The short-cut command is equivilant to:

'mapci;mtc;trks;ttp;manual'. One can post by trunkgroup:

>manuals;post g mderobert1sc

CM MS IOD Net PM CCS Trks Ext APPL

. . . . . . . . .

MANUAL

0 QUIT POST 5 DELQ BSYQ DIG

2 Post_ TTP 27-0621

3 LOSS CKT TYPE PM NO. COM LANG STA S R DOT TE RESULT

4 TGEN 2W DT DT DTC 0 5 7 MDEROBERT1SC 1 IDL

5 BSY

6 RTS

7 TST

8 Noise

9 OP_

10 TDet

11 Hold

12 NEXT

13 RLS

14 HSet SHORT CLLI IS: S941

15 Jack_ POSITION RESTARTED

16 SGNL TTP:

17 MANUAL:

18 CallTrf

Time 12:55 >

Or one can also post by the entire DTC by typing 'post d dtc 34 4'.

Different STATES of the trunks include:

IDL Idle The trunk is idle and ready for a call

CPB Call-Processing Busy The trunk has an active call on it.

CFL Carrier Fail The T1 port is either OFFL or in CGA.

MB Man-Busy The trunk has been manually busied by somebody.

RMB Remote Man-Busy The far-end switch has this trunk manually-busied.

SB System Busy The switch detects trouble on this trunk and busies it out.

UTR Universal Tone-Receiver The switch is ready to detect digits from the customer.

LO Lock-out We're seeing a permanent seizure on the line *, or for

SS7/ISDN trunks, there are signaling troubles.

Once posted on an IDL or MB trunk, one can type "hset;op xxxx" and the switch will connect that trunk to the head-set and outpulse the appropriate digits to the customer. This is used to manually test an SS7/ISDN trunk or to verify DNIS works inside the customer's PBX on a dedicated trunk-group. Note, that for SS7/ISDN trunks, the switch doesn't really outpulse the numbers, it creates an IAM/SETUP message and sends it to the far-end switch. Also, Lock-outs can be caused by trunk-conditioning in a 1:0 DCS in response to a T1 failure.

CHECKING FOR WINKS

When the DMS sends a call to an E&M Wink-Start trunk-group, there are several steps:

1. The DMS selects an idle trunk in the first available route-choice.

2. The DMS goes off-hook.

3. The CPE 'winks'. This is nothing more than a momentary off-hook.

4. The DMS recognizes the 'wink' as a proceed to send DNIS (if there are DNIS)

5. The DMS out-pulses DNIS to the CPE.

6. The CPE checks it routing tables and rings the called person's phone.

7. The person picks up.

8. The CPE returns an off-hook (answer-supervision) to the DMS.

9. The DMS cuts through the talk path in both direction.

A very common trouble occurs when an error happens and the CPE does not 'wink' back at the DMS. The DMS will wait a moment and if it doesn't see a 'wink', it will select another available trunk in that same route-choice. If the second trunk doesn't 'wink' either, then the DMS will completely skip that route-choice and go to the next available route-choice.

To check for winks, one can go to the 'manuals' level and type mm;mm;mm;mm to watch for the 'wink' or momentary off-hook from the customer. The 'mm' command causes the DMS to go on-hook or off-hook depending on the current status of the trunk.

Here is an idle trunk in the manual level:

CKT TYPE PM NO. COM LANG STA S R DOT TE RESULT

2W DT DT DTC 34 4 1 MDEMIWATT1SC 1 IDL

>mm [This causes the DMS to go off-hook. You can tell the DMS is off-hook because

of the '+' under the S (Send). If the CPE winks, you should see a

momentary '+' under the R (Receive). The wink won't last long, and should

then return back to a '.' Which indicates an on-hook from CPE]

CKT TYPE PM NO. COM LANG STA S R DOT TE RESULT

2W DT DT DTC 34 4 1 MDEMIWATT1SC 1 SZD + .

P_IDL

>mm [This causes the DMS to return to an on-hook condition]

CKT TYPE PM NO. COM LANG STA S R DOT TE RESULT

2W DT DT DTC 34 4 1 MDEMIWATT1SC 1 SZD . .

P_IDL

>frls;rts [Puts the trunk back in an IDL condition]

CKT TYPE PM NO. COM LANG STA S R DOT TE RESULT

2W DT DT DTC 34 4 1 MDEMIWATT1SC 1 IDL

• You may want to do OMSHOWS on the trunk-group for the ACTIVE time period while placing a test call if you suspect you are not getting winks from the customer. If there is no wink from the CPE, you will see the NATTMPT increment 2 times for every failed call. This is because the DMS tries 2 trunks in each route choice before going to the next route-choice.

• You can also check "trk 121" logs in the LOGUTIL level to view no wink-troubles.

SS7 TRUNKS

To test ss7 trunks, go to the MAPCI;MTC;TRKS;TTP;C7TTP level and do the CVTEST and TST ICOT commands. The CVTEST verifies that the CIC is built and active in the far-end switch and the TST ICOT command verifies there is continuity between the 2 switches.

Also, from this level, you can type 'CIC' when you are posted on a trunk and the DMS will tell you which CIC that trunk is using.

You can also type 'ROUTESET'. The DMS will display the route-set being used by this trunk-group. Then go to TABLE C7RTESET and position on it and you will find the point-code of the far-end switch.

>mapci;mtc;trks;ttp;c7ttp

CM MS IOD Net PM CCS Trks Ext APPL

. . . . . . . . .

C7TTP

0 Quit POST 1463 DELQ BSYQ DIG

2 Post_ TTP 27-0621

3 Seize CKT TYPE PM NO. COM LANG STA S R DOT TE RESULT

4 2W S7 S7 DTC 41 1 1 MC7CHCGALCD8 1 IDL

5 Bsy R

6 RTS

7 Tst

8

9

10

11 HOLD

12 Next

13 Rls

14 CVTest SHORT CLLI IS: S3025

15 TrkQry POSITION RESTARTED

16 QrySig TTP:

17 RouteSet C7TTP:

18 CIC

Time 14:06 >

Sample data-fill of important tables for an SS7 trunk-group:

>table trkgrp;pos MC7CHCGALCD8

MC7CHCGALCD8 EANT 26 IN06 NCOT 0 2W SPR2 MIDL 100 7 100 7 EQ27 7 7 414 UCS2EAEO NIL 414 1 NONE 0 NONE 0 0 SPEECH 160 (CASUALU ) (ANIDIGS ) (TMANIDLV ALWAYS) (OPNOAUTH ) $

>table trksgrp;pos MC7CHCGALCD8 0

MC7CHCGALCD8 0 DS1SIG C7UP 2W N N UNEQ ACTIVEA UCP THRH 0 ROCHAC $ NIL SGRPYLD Y

>table isupdest;pos MC7CHCGALCD8 0

MC7CHCGALCD8 0 C7RTCHCGALC

>table c7rteset;pos C7RTCHCGALC

C7RTCHCGALC C7NETWRK0 N ANSI7 (242) (1) (8) $ (SCIAMILW 0) (SCIACDRR 0) $

>table trkmem;pos MC7CHCGALCD8 1

MC7CHCGALCD8 1 0 DTC 41 1 1

>table c7trkmem;pos MC7CHCGALCD8 1

MC7CHCGALCD8 1 1

CHECKING FOR LOOPS ON A T1 CARRIER

Looped T1 carriers are sometimes difficult to detect because they will make some trunks appear idle. Luckily there are some ways to detect looped carriers.

If the OMSHOW shows GLARE, then suspect a looped carrier. GLARE is when both the DMS and the far-end equipment both attempt to seize the line and send a call at exactly the same time. A looped carrier will simulate GLARE.

If you suspect glare, go to the manual level and do a 'loss e' command. If the ERL (Echo Return Loss) is between 0 and -0.5 then suspect a loop. For example:

>manuals;post g mdebuelow1sc;loss e

CM MS IOD Net PM CCS Trks Ext APPL

. . . . . . . . .

MANUAL

0 QUIT POST DELQ BSYQ DIG

2 Post_ TTP 27-0621

3 LOSS CKT TYPE PM NO. COM LANG STA S R DOT TE RESULT

4 TGEN 2W DT DT DTC 3 1 17 MDEBUELOW1SC 1 SZD . . ERL -.1

5 BSY P_IDL LS -.3HS 0.0

6 RTS

7 TST EML 0.0 DB

8 Noise PAD PC - TE 0

9 OP_

10 TDet

11 Hold LOSS E

12 NEXT OK, CONNECTION SET

13 RLS

14 HSet

15 Jack_

16 SGNL

17

18 CallTrf

Time 14:25 >

>frls;rts [to return the trunk to service]

Switch 24 Recordings

Message 101: We're sorry, the phone number you are calling from is not in our database.

[Treatment '085' or '076' Ani Database Failure]

Message 102: We're sorry, all circuits are busy now.

[Treatment '058' Generalized, No Circuit Available]

Message 103: We're sorry, the authorization code you have dialed is invalid. Please try your call again.

[Treatment '053' Invalid Authorization Code]

Message 104: We're sorry, not enough digits have been received to process your call. Please try your call again.

[Treatment '002' Insufficient Number of Digits Received]

Message 105: We're sorry, not enough digits have been received to process your call. Please veify your dialing sequence and try your call again.

[Treatment '003' No Digits Detected at 400 Hz Tone]

Message 106: We're sorry, you have dialed an invalid account code. Please try your call again.

[Treatment '004' Invalid Account Code]

Message 107: We're sorry, you have dialed an invalid speed number or an unrecognizable exchange.

[Treatment '065' Vacant Speed Number]

Message 108: We're sorry, the area code and exchange you have dialed is invalid.

[Treatment '006' Vacant Code]

Message 109: We're sorry, all circuits are busy now.

[Treatment '001' No Service Circuit]

Message 110: Were sorry, the authorization code you have dialed is not in service.

[Treatment '054' Temporarily Invalid Auth Code]

Message 111: We're sorry, your call cannot be completed at this time.

[Treatment '063' Restricted Date/Time on Auth Code[

Message 112: If you want to place an AT&T credit card, operator assisted, or international call, please hang up and dial 10288 at the beginning of your dialing sequence.

Message 113: We're sorry, you have dialed an invalid security code.

[Treatment '110' Invalid Pin Digits Dialed]

Message 114: We're sorry, your international call cannot be completed.

Message 119: We're sorry, you have dialed an 800 number that is not available from your calling area.

Message 120: Thank you for choosing Schneider Communications as your long distance carrier

[Dialing 700-555-4141 to confirm LD carrier]