nn10275 909v14 12.01 cvm16 c20 fault management logs alarms ref

C20 Converged Softswitch

Logs and Alarms Reference,Volume 14Release: CVM16 and upDocument Revision: 12.01

www.genband.com

NN10275-909v14

C20 Converged SoftswitchRelease: CVM16 and upPublication: NN10275-909v14Document status: StandardDocument release date: 06 October 2011

Copyright © 2011 GENBAND. All rights reserved. Use of this documentation and its contents is subject to theterms and conditions of the applicable end user or software license agreement, right to use notice, and all relevantcopyright protections.

GENBAND, the GENBAND corporate logo and tagline, and certain of GENBAND's product and solution namesare registered trademarks of GENBAND and its affiliates.

While the information in this document is believed to be accurate and reliable, except as otherwise expresslyagreed to in writing GENBAND AND/OR ITS LICENSORS PROVIDES THIS DOCUMENT "AS IS" WITHOUTWARRANTY OR CONDITION OF ANY KIND, EITHER EXPRESS OR IMPLIED. The information and/or productsdescribed in this document are subject to change without notice.

THE INFORMATION CONTAINED HEREIN IS THE PROPERTY OF GENBAND OR ITS LICENSORS ANDMUST NOT BE DISCLOSED, OTHER THAN TO EMPLOYEES OF GENBAND OR CUSTOMERS WITH NEED-TO-KNOW, WITHOUT THE PRIOR WRITTEN CONSENT OF GENBAND OR ITS LICENSORS. THEINFORMATION MUST NOT BE DISCLOSED TO SUBCONTRACTORS OR REGULATORY AUTHORITIES. GENBAND MUST BE NOTIFIED OF ANY REQUEST OR ORDER FOR DISCLOSURE PRIOR TO SUCHDISCLOSURE.

Software and documentation owned by or under license with Nortel Networks included in this Release or in anydocument provided with this Release is Copyright © 2010 Nortel Networks or its licensors. All rights reserved. Useof this software and/or documentation and its contents is subject to the terms and conditions of the applicable enduser or software license agreement, right to use notice, and all relevant copyright protections. The product names remain as Carrier VoIP and CS 2000 in Canada and France pending regulatory approvals for a name change.

Contents

New in this release 47DMS_Intl 47

Logs and alarms fundamentals 49

DMS_Intl alarms and logs reference 51AMAB117 51

Remedial action 51Attributes 51Format 51Selected field descriptions 52Active message example 52Clear message example 53Associated OM registers 53

AP312 53Remedial action 53Attributes 53Format 53Selected field descriptions 54Active message example 54Clear message example 55Associated OM registers 55

APS1XX 55Remedial action 55Attributes 55Format 55Selected field descriptions 56Active message example 56Clear message example 57Associated OM registers 57

AUD397 57Remedial action 57Attributes 57Format 57Selected field descriptions 58Active message example 58Clear message example 58Associated OM registers 58

AUD512 58

3

C20 Converged SoftswitchLogs and Alarms Reference, Volume 14

NN10275-909v14 12.01 06 October 2011

Copyright © 2011 GENBAND. All Rights Reserved.





AUDT120 62Remedial action 62Attributes 63Format 63Selected field descriptions 63Active message example 63Clear message example 64Associated OM registers 64


AUDT122 65Remedial action 65Attributes 65

4


NN10275-909v14 12.01 06 October 2011


Format 66Selected field descriptions 66Active message example 66Clear message example 66Associated OM registers 67



C7TU108 69Remedial action 69Attributes 69Format 69Selected field descriptions 69Active message example 69Clear message example 70Associated OM registers 70

C7UP124 70Remedial action 70Attributes 72Format 72Selected field descriptions 73Active message example 74Clear message example 74Associated OM registers 74

C7UP602 74Remedial action 74Attributes 75Format 75Selected field descriptions 75Active message example 75Clear message example 76Associated OM registers 76

C7UP603 76Remedial action 76Attributes 76Format 76Selected field descriptions 77

5


NN10275-909v14 12.01 06 October 2011


Active message example 77Clear message example 77Associated OM registers 78

CCHK100 78Remedial action 78Attributes 78Format 78Selected field descriptions 78Active message example 78Clear message example 79Associated OM registers 79

CCS800 79Remedial action 79Attributes 79Format 79Selected field descriptions 79Active message example 80Clear message example 80Associated OM registers 80




CCS804 82Remedial action 83Attributes 83Format 83Selected field descriptions 83Active message example 83Clear message example 83

6


NN10275-909v14 12.01 06 October 2011


Associated OM registers 83CCS805 83



CDR268 85Remedial action 86Attributes 86Format 86Selected field descriptions 86Active message example 88Clear message example 88Associated OM registers 88

CDR269 Format 1 88Remedial action 88Attributes 89Format 89Selected field descriptions 90Active message example 92Clear message example 94Associated OM registers 94


CDR600 98Remedial action 98Attributes 98Format 98Active message example 99Clear message example 99Associated OM registers 99

CDR601 99Remedial action 99

7


NN10275-909v14 12.01 06 October 2011


Attributes 100Format 100Selected field descriptions 101Active message example 103Clear message example 105Associated OM registers 105






CDR607 123Remedial action 125Attributes 125Format 125Selected field descriptions 127Active message example 129Clear message example 131

8


NN10275-909v14 12.01 06 October 2011


Associated OM registers 131CDR608 131

Remedial action 131Attributes 132Format 132Active message example 132Clear message example 132Associated OM registers 132






CDR614 157Remedial action 158Attributes 158Format 158

9


NN10275-909v14 12.01 06 October 2011




CEPT100 168Remedial action 168Attributes 168Format 168Selected field descriptions 168Active message example 169Clear message example 169Associated OM registers 169

CEPT101 169Remedial action 169Attributes 170Format 170Selected field descriptions 170Active message example 170Clear message example 171Associated OM registers 171

CFW107 171Remedial action 171Attributes 171Format 172Selected field descriptions 172Active message example 172Clear message example 173Associated OM registers 173

CFW109 173Remedial action 173Attributes 173Format 173Selected field descriptions 173Active message example 174Clear message example 174Associated OM registers 174

CFW110 174Remedial action 174Attributes 174Format 174Selected field descriptions 175Active message example 175Clear message example 175

10


NN10275-909v14 12.01 06 October 2011


Associated OM registers 175CFW111 175


CLBK600 176Remedial action 177Attributes 177Format 177Selected field descriptions 177Active message example 182Clear message example 182Associated OM registers 182



CLIS100 189Remedial action 189Attributes 190Format 190Selected field descriptions 190Active message example 190Clear message example 191Associated OM registers 191

CLIV100 191Remedial action 191Attributes 191Format 191Selected field descriptions 192Active message example 192Clear message example 192Associated OM registers 192

CNN100 192

11


NN10275-909v14 12.01 06 October 2011



CNN101 194Remedial action 194Attributes 194Format 194Selected field descriptions 195Active message example 195Clear message example 195Associated OM registers 195

CNN102 195Remedial action 195Attributes 195Format 195Selected field descriptions 196Active message example 196Clear message example 196Associated OM registers 196

CSFJF 196Remedial action 196Attributes 196Format 196Selected field descriptions 197Active message example 197Clear message example 199Associated OM registers 199

CTFP600 199Remedial action 199Attributes 199Format 199Selected field descriptions 200Active message example 200Clear message example 201Associated OM registers 201

DCME100 201Remedial action 201Attributes 201Format 201Selected field descriptions 201Active message example 202Clear message example 202Associated OM registers 202

DCME101 202Remedial action 202Attributes 202

12


NN10275-909v14 12.01 06 October 2011








DFIL139 208Remedial action 208Attributes 208Format 208Selected field descriptions 209

13


NN10275-909v14 12.01 06 October 2011



DFIL157 209Remedial action 210Attributes 210Format 210Selected field descriptions 210Active message example 210Clear message example 211Associated OM registers 211





DFIL600 217Remedial action 217Attributes 217Format 217Selected field descriptions 218Active message example 218Clear message example 218

14


NN10275-909v14 12.01 06 October 2011


Associated OM registers 218DFIL607 218

Remedial action 218Attributes 218Format 219Active message example 219Clear message example 219Associated OM registers 219

DFIL608 219Remedial action 219Attributes 219Format 219Active message example 220Clear message example 220Associated OM registers 220





DMCT100 226Remedial action 226Attributes 226

15


NN10275-909v14 12.01 06 October 2011



DMCT101 227Remedial action 227Attributes 227Format 227Selected field descriptions 228Active message example 228Clear message example 228Associated OM registers 228

DMCT102 228Remedial action 228Attributes 228Format 229Selected field descriptions 229Active message example 229Clear message example 230Associated OM registers 230

DNC100 230Remedial action 230Attributes 230Format 230Selected field descriptions 230Active message example 230Clear message example 231Associated OM registers 231

DPNS400 231Remedial action 231Attributes 231Format 231Selected field descriptions 231Active message example 231Clear message example 231Associated OM registers 232


DPNS402 233Remedial action 233Attributes 234Format 234Selected field descriptions 234

16


NN10275-909v14 12.01 06 October 2011




DPNT101 235Remedial action 236Attributes 236Format 236Selected field descriptions 236Active message example 237Clear message example 237Associated OM registers 237




DPNT105 242Remedial action 243Attributes 243Format 243Selected field descriptions 243Active message example 244Clear message example 244

17


NN10275-909v14 12.01 06 October 2011


Associated OM registers 244DPNT106 244







DPNT206 255

18


NN10275-909v14 12.01 06 October 2011



DRM602 257Remedial action 258Attributes 258Format 258Selected field descriptions 258Active message example 258Clear message example 259Associated OM registers 259

DRM603 259Remedial action 259Attributes 259Format 259Selected field descriptions 259Active message example 260Clear message example 260Associated OM registers 260

DRT100 260Remedial action 260Attributes 260Format 260Selected field descriptions 261Active message example 261Clear message example 261Associated OM registers 261

EIN301 261Remedial action 262Attributes 262Format 262Selected field descriptions 263Active message example 265Clear message example 266Associated OM registers 266


EIN310 270Remedial action 270Attributes 270

19


NN10275-909v14 12.01 06 October 2011







EMD100 291Remedial action 292Attributes 292Format 292Selected field descriptions 292Active message example 293Clear message example 293Associated OM registers 294

EMD101 294Remedial action 294Attributes 294Format 294Selected field descriptions 294

20


NN10275-909v14 12.01 06 October 2011



ESV120 296Remedial action 296Attributes 296Format 296Selected field descriptions 296Active message example 297Clear message example 297Associated OM registers 297

FEAT400 297Remedial action 297Attributes 297Format 297Selected field descriptions 298Active message example 298Clear message example 298Associated OM registers 298

FPS100 298Remedial action 298Attributes 298Format 298Selected field descriptions 299Active message example 299Clear message example 299Associated OM registers 299

FRB100 299Remedial action 299Attributes 300Format 300Selected field descriptions 300Active message example 300Clear message example 300Associated OM registers 300

IBN134 300Remedial action 300Attributes 301Format 301Selected field descriptions 301Active message example 302Clear message example 302Associated OM registers 302

IBN138 302Remedial action 302Attributes 303Format 303Selected field descriptions 303Active message example 303Clear message example 304

21


NN10275-909v14 12.01 06 October 2011


Associated OM registers 304INH105 304


ISDN310 305Remedial action 306Attributes 306Format 306Selected field descriptions 307Active message example 307Clear message example 308Associated OM registers 308

ISDN310 Format 2 308Remedial action 309Attributes 309Format 309Selected field descriptions 309Active message example 310Clear message example 311Associated OM registers 311

ITN202 311Remedial action 311Attributes 311Format 311Selected field descriptions 312Active message example 312Clear message example 312Associated OM registers 312

IWUC 312Remedial action 312Attributes 313Format 313Selected field descriptions 313Active message example 313Clear message example 314Associated OM registers 314

LINE124 314Remedial action 314Attributes 314Format 314Selected field descriptions 315Active message example 315Clear message example 316Associated OM registers 316

LINE124 Format 2 316

22


NN10275-909v14 12.01 06 October 2011




LINE129 Format 2 320Remedial action 321Attributes 321Format 321Selected field descriptions 322Active message example 322Clear message example 322Associated OM registers 323

LINE129 Format 3 323Remedial action 323Attributes 323Format 323Selected field descriptions 324Active message example 324Clear message example 325Associated OM registers 325



LINK300 330Remedial action 330Attributes 330

23


NN10275-909v14 12.01 06 October 2011



LNG101 332Remedial action 332Attributes 332Format 332Selected field descriptions 333Active message example 333Clear message example 333Associated OM registers 333

LOGT900 333Remedial action 334Attributes 334Format 334Selected field descriptions 335Active message example 335Clear message example 335Associated OM registers 336

MCID100 336Remedial action 336Attributes 336Format 336Selected field descriptions 337Active message example 337Clear message example 338Associated OM registers 338



MCID110 342Remedial action 342Attributes 342Format 342Selected field descriptions 343

24


NN10275-909v14 12.01 06 October 2011



MCT104 344Remedial action 344Attributes 344Format 344Selected field descriptions 345Active message example 345Clear message example 345Associated OM registers 346


MCT105 Format 2 347Remedial action 348Attributes 348Format 348Selected field descriptions 348Active message example 349Clear message example 349Associated OM registers 349


MML300 Format 1 352Remedial action 353Attributes 353Format 353Selected field descriptions 354Active message example 354Clear message example 354Associated OM registers 354

MML300 Format 2 354Remedial action 355Attributes 355Format 356Selected field descriptions 356Active message example 356Clear message example 356

25


NN10275-909v14 12.01 06 October 2011


Associated OM registers 356MML301 356


MML310 358Remedial action 359Attributes 360Format 360Selected field descriptions 360Active message example 360Clear message example 361Associated OM registers 361





MML610 370

26


NN10275-909v14 12.01 06 October 2011







MS304 377Remedial action 377Attributes 377Format 377Selected field descriptions 377Active message example 378Clear message example 378Associated OM registers 379

MTR100 379Remedial action 379Attributes 379

27


NN10275-909v14 12.01 06 October 2011



MTR107 380Remedial action 380Attributes 380Format 380Selected field descriptions 380Active message example 380Clear message example 380Associated OM registers 381





MTR157 385Remedial action 386Attributes 386Format 386Selected field descriptions 386

28


NN10275-909v14 12.01 06 October 2011





MTRS100 389Remedial action 390Attributes 390Format 390Selected field descriptions 390Active message example 390Clear message example 390Associated OM registers 390

MTRS101 390Remedial action 391Attributes 391Format 391Selected field descriptions 391Active message example 391Clear message example 391Associated OM registers 392

NAOC200 392Remedial action 392Attributes 392Format 392Selected field descriptions 392Active message example 393Clear message example 393Associated OM registers 393

NAOC210 393Remedial action 393Attributes 393Format 394Selected field descriptions 394Active message example 394Clear message example 394

29


NN10275-909v14 12.01 06 October 2011


Associated OM registers 394NAOC220 394





NWM601 400Remedial action 400Attributes 401Format 401Selected field descriptions 401Active message example 401Clear message example 402Associated OM registers 402

NWM602 402Remedial action 402Attributes 402Format 402Selected field descriptions 403Active message example 403Clear message example 403Associated OM registers 403

NWM603 403

30


NN10275-909v14 12.01 06 October 2011



OCC213 405Remedial action 406Attributes 406Format 406Selected field descriptions 406Active message example 406Clear message example 406Associated OM registers 406

OCC230 406Remedial action 406Attributes 407Format 407Selected field descriptions 407Active message example 407Clear message example 408Associated OM registers 408

PTP100 408Remedial action 408Attributes 408Format 408Selected field descriptions 409Active message example 409Clear message example 409Associated OM registers 409

PTP101 409Remedial action 409Attributes 410Format 410Selected field descriptions 410Active message example 410Clear message example 410Associated OM registers 410

QSIG100 410Remedial action 410Attributes 410Format 410Selected field descriptions 411Active message example 411Clear message example 411Associated OM registers 411

QSIG101 411Remedial action 411Attributes 411

31


NN10275-909v14 12.01 06 October 2011








QSIG107 417Remedial action 417Attributes 417Format 418Selected field descriptions 418

32


NN10275-909v14 12.01 06 October 2011





RBP100 420Remedial action 420Attributes 420Format 420Selected field descriptions 421Active message example 421Clear message example 421Associated OM registers 421

SFPS100 421Remedial action 421Attributes 422Format 422Selected field descriptions 422Active message example 422Clear message example 422Associated OM registers 422

SM21300 422Remedial action 422Attributes 423Format 423Selected field descriptions 423Active message example 423Clear message example 423Associated OM registers 424

SM21500 424Remedial action 424Attributes 424Format 424Selected field descriptions 424Active message example 425Clear message example 425

33


NN10275-909v14 12.01 06 October 2011


Associated OM registers 425SM21501 425


SM21502 426Remedial action 426Attributes 426Format 426Selected field descriptions 427Active message example 427Clear message example 427Associated OM registers 427

SMDR100 427Remedial action 427Attributes 428Format 428Selected field descriptions 428Active message example 429Clear message example 429Associated OM registers 430

SPL101 430Remedial action 430Attributes 430Format 430Selected field descriptions 430Active message example 430Clear message example 430Associated OM registers 431

TEST101 431Remedial action 432Attributes 432Format 432Selected field descriptions 432Active message example 432Clear message example 432Associated OM registers 433

TIV102 433Remedial action 433Attributes 433Format 433Selected field descriptions 433Active message example 434Clear message example 434Associated OM registers 434

TIV103 434

34


NN10275-909v14 12.01 06 October 2011





TKCV101 441Remedial action 441Attributes 442Format 442Selected field descriptions 442Active message example 442Clear message example 442Associated OM registers 443

TKCV102 443Remedial action 443Attributes 443Format 443Selected field descriptions 444Active message example 444Clear message example 444Associated OM registers 444

TOPS303 444Remedial action 444Attributes 445Format 445Selected field descriptions 445Active message example 445Clear message example 445Associated OM registers 445

TOPS614 445Remedial action 445Attributes 445

35


NN10275-909v14 12.01 06 October 2011



TRK255 447Remedial action 447Attributes 447Format 447Selected field descriptions 448Active message example 448Clear message example 448Associated OM registers 448



TRK601 Format 2 452Remedial action 453Attributes 453Format 453Selected field descriptions 453Active message example 454Clear message example 454Associated OM registers 454

TRK601 Format 3 454Remedial action 455Attributes 455Format 455Selected field descriptions 456Active message example 456Clear message example 457Associated OM registers 457

TRK602 457Remedial action 457Attributes 457Format 457Selected field descriptions 458

36


NN10275-909v14 12.01 06 October 2011




TRST100 460Remedial action 461Attributes 461Format 461Selected field descriptions 461Active message example 462Clear message example 462Associated OM registers 462

TSTK910 462Remedial action 463Attributes 463Format 463Active message example 463Clear message example 463Associated OM registers 463

TSTK911 463Remedial action 463Attributes 464Format 464Selected field descriptions 465Active message example 465Clear message example 466Associated OM registers 466



37


NN10275-909v14 12.01 06 October 2011








TSTK944 482Remedial action 482

38


NN10275-909v14 12.01 06 October 2011



TUPL608 484Remedial action 485Attributes 485Format 485Selected field descriptions 486Active message example 486Clear message example 487Associated OM registers 487

V5101 487Remedial action 487Attributes 487Format 488Selected field descriptions 488Active message example 488Clear message example 489Associated OM registers 489




V5105 494Remedial action 494Attributes 494Format 494

39


NN10275-909v14 12.01 06 October 2011


Selected field descriptions 494Active message example 495Clear message example 495Associated OM registers 495






V5111 501Remedial action 501Attributes 502Format 502Selected field descriptions 502Active message example 502

40


NN10275-909v14 12.01 06 October 2011


Clear message example 502Associated OM registers 502







41


NN10275-909v14 12.01 06 October 2011







V5255 526Remedial action 527Attributes 527Format 527Clear message example 527Associated OM registers 527

V5256 527Remedial action 527Attributes 527Format 527

42


NN10275-909v14 12.01 06 October 2011


Selected field descriptions 528Active message example 529Clear message example 529Associated OM registers 529






VIP101 537Remedial action 538Attributes 538Format 538Selected field descriptions 538Active message example 538

43


NN10275-909v14 12.01 06 October 2011


Clear message example 538Associated OM registers 538

VIP102 538Remedial action 538Attributes 539Format 539Selected field descriptions 539Active message example 539Clear message example 539Associated OM registers 539



VML101 541Remedial action 542Attributes 542Format 542Selected field descriptions 542Active message example 542Clear message example 542Associated OM registers 543



44


NN10275-909v14 12.01 06 October 2011








VML110 551Remedial action 552

45


NN10275-909v14 12.01 06 October 2011




VML112 553Remedial action 553Attributes 553Format 554Active message example 554Clear message example 554Associated OM registers 554

WTNP101 554Remedial action 554Attributes 554Format 555Selected field descriptions 555Active message example 555Clear message example 555Associated OM registers 555

WTNP102 555Remedial action 556Attributes 556Format 556Selected field descriptions 556Active message example 556Clear message example 557Associated OM registers 557

XAC400 XA-Core Summary Report 557Remedial action 557Attributes 557Format 557Selected field descriptions 558Active message example 560Clear message example 561Associated OM registers 561

46


NN10275-909v14 12.01 06 October 2011


New in this release

The following sections detail what's new in the following network elementsand applications for the CORE13 release.

DMS_IntlNo Changes for this device

47


NN10275-909v14 12.01 06 October 2011


48 New in this release


NN10275-909v14 12.01 06 October 2011


Logs and alarms fundamentals

A log report is a message about an important conditions or events relatedto component(s) performance. Log reports include, but are not restrictedto, the following information:

• state and activity reports

• changes in state

• hardware or software errors

• test results

• other events or conditions that affect performance

Both system actions and manual overrides can generate log reports.

Attention: This document uses multiple volumes to describe logs thatthe C20 network components can generate. Not all components apply toevery solution.

Attention: In systems which include an Integrated ElementManagement System (IEMS), clearing of manually clearable alarmsthrough OMI (or a System Management GUI) is reflected in the IEMS.However, acknowledgement of alarms through OMI (or a SystemManagement GUI) is NOT reflected in the IEMS.

49


NN10275-909v14 12.01 06 October 2011


50 Logs and alarms fundamentals


NN10275-909v14 12.01 06 October 2011


DMS_Intl alarms and logs reference

This section provides a reference for the DMS_Intl alarms and logs for theCORE13 release.

AMAB117The Automatic Message Accounting (AMA) subsystem generates thisreport for non-Integrated Services Digital Network (ISDN) calls wheneveran AMA record is produced, provided option LOGAMA is activated in tableAMAOPTS.

Remedial actionn/a

AttributesAttribute Value

Severity Warning

FormatAMAB117 mmmdd hh:mm:ss ssdd INFO AMA RECORD DATA

STRUCTURE CODE = aaaaaCALL CODE = bbb

CONNECT DATE = cccccCONNECT TIME = hhmmssd

ELAPSED TIME = ssssssssANSWERED = YES/NO

CALLING DN = dn

ORIG AGENT = CKT clli

CALLED DN = dn

TERM AGENT = CKT clli

51


NN10275-909v14 12.01 06 October 2011


Selected field descriptionsField Value Fixed or

VariableDescription

STRUCTURE CODE Integers Variable Identifier that defines the content andorder of the AMA record.

CALL CODE Integers Variable Indicates the call code. BellcoreFormat Automatic MessageAccounting Reference Guide ,297-1001-830, contains the call codesfor BCFMT office.

CONNECT DATE Integers Variable Gives the date when the connectionfor this call was set up. The format isyymmdd (y=year, m=month, d=day).

CONNECT TIME Integers Variable Gives the time when the connectionfor this call was set up. First andsecond digits indicate hours, third andfourth digits indicate minutes, fifth andsixth digits indicate seconds, and thelast digit indicates milliseconds

ELAPSED TIME Integers Variable Duration of call. The first five digitsindicate minutes (up to 4320 minutes),the sixth and seventh digits indicateseconds and the eight indicates tenthsof a second.

ANSWERED YES or NO Variable Indicates if the call was answered.

CALLING DN Symbolic text, up to18 digits

Variable Indicates calling number.

ORIG AGENT Symbolic text Variable Identifies the CLLI and circuit numberfor the originating circuit. Theoriginating agent can also be a line,identified by LEN and DN, attendantconsole, which is identified bycustomer group and console name, ora VFG identified by name andmember number.

CALLED DN Symbolic text, up to18 digits

Variable Identifies called number.

TERM AGENT Symbolic text Variable Identifies the CLLI and circuit numberfor the terminating circuit. This fieldcan also contain a line equipmentnumber (LEN) and a directory number(DN).

Active message exampleAMAB117 JUL04 14:23:35 6900 INFO AMA RECORD DATA

52 DMS_Intl alarms and logs reference


NN10275-909v14 12.01 06 October 2011


STRUCTURE CODE = 40510 CALL CODE = 006

CONNECT DATE = 70704 CONNECT TIME = 1423344

ELAPSED TIME = 00098182 ANSWERED = YES

CALLING DN = 9197828826

ORIG AGENT = LEN HOST 30 0 04 00 DN 8114007

CALLED DN = 800555121212121212121212121212

TERM AGENT = CKT KNGA200BTBWE

Clear message examplen/a

Associated OM registers

AP312This log is generated when there is a fault with a port card in the node.

Remedial actionPerform the action stated in the user action field. If a port test failed,replace the card as soon as possible because all reads from the faultyaddress will fail.


Severity • Critical

• Major

Format<alrm>AP312 mmmdd hh:mm:ss ssdd TBL Port Test Fault

Location: <node> <card description>

Status: <trouble_status>

Trouble: <trouble_code>

Action: <user_action>

Detailed Reason: <reason_text>

AP312 53


NN10275-909v14 12.01 06 October 2011


Cardlist:

<list of cards>


VariableDescription

alrm ** Variable This field indicates the alarm for thisevent. This field always indicates amajor alarm

node FP n or AP n Variable This field indicates the supportoperating system (SOS) duplex nodethat failed the port test. The letter nindicates the number of the node inthe applicable inventory table.

trouble_status Alarm raised Variable This field indicates the trouble status.This field is always "Alarm raised" forthis report.

trouble_code alpha Variable This field indicates nature of theproblem being reported.

user_action alpha Variable This field indicates the actionoperating company personnel shouldtake.

reason_text alpha Variable This field indicates the reason forfailure to synchronize.

List of cards alphanumeric Variable This field indicates the list of cards tobe replaced.

Active message example**AP312 SEP02 12:34:10 2351 TBL Port Test Fault

Location: FP 0 Plane 1 Port Card 1

Status: Alarm raised

Trouble: Hardware test failed

Action: Replace the following cards in the order listed

Critical threshold exceeded: MPLH ndev 0 Code violation

Critical threshold exceeded: MPLH ndev 0 Loss of Idle

Non-Critical threshold exceeded: MPLH ndev 0 Wait for sendtimeout



NN10275-909v14 12.01 06 October 2011


Cardlist:

Site Flr RPos Bay_id Shf Description Slot EqPEC Side

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

HOST 00 A00 FP:00 00 Port 15 9X86AA FRNT

HOST 00 A00 FP:00 00 Port 15 9x62AA BACK



APS1XXThe DMS log device generates the Attendant paystation (APS) outputformat APSLOG, which can be specified instead of the auto quote printerAQHTL or voice quote printer VQHTL entries in the device field of tableTDBCLASS. APSLOG generates an APS1XX log, in which XX is aparameter specified in table TDBCLASS.

Each APS1XX log can be assigned a log class, and each log class can beprinted to any physical log device. This is done by entering datafill in tablesLOGCLASS and LOGDEV appropriately. Table LOGDEV allows theentering of datafill of an alternate log device in which the alternate logdevice is used if the primary log device fails. For any attendant paystation(APS) call that does not have a device assigned to it, an APS100 log isgenerated. Additionally, if table DNSCRN is not entered with datafillcorrectly, the APS call generates APS100 logs. If the local or toll call isbusy or unanswered and the table DNSCRN is not entered with datafillcorrectly, no log is generated.

Remedial actionn/a


Severity Warning

FormatAPS1XX mmmdd hh:mm:ss ssdd INFO APS LOG ENTRY

MSG COUNT= <Msg Count>

APS1XX 55


NN10275-909v14 12.01 06 October 2011


CALLING DN= <Calling no>

CALLED DN= <Called no>

DATE= <Date>

ANSWER TIME= <Answer time>

DURATION= <Duration>

CHARGES= <Chg>

BOOTH= <Booth>


VariableDescription

mmmdd alphanumeric string Variable Indicates the first three characters ofthe month plus the day of the month ofthe log.

hh:mm:ss two-digit numericstring

Variable Indicates the time (hours, minutes,seconds) of the log.

ssdd four-digit numericstring

Variable Indicates the log sequence number.

MSG COUNT numeric string Variable Indicates the message count.

CALLING DN numeric string Variable Indicates the DN from which the callwas made.

CALLED DN numeric string Variable Indicates the DN to which the call wasmade.

DATE numeric string Variable Indicates the date on which the callwas made.

ANSWER TIME numeric string Variable Indicates the time (hours:minutes) atwhich the call was answered.

DURATION numeric string Variable Indicates the duration of the call inminutes.

CHARGES numeric string Variable Indicates the call charge. At ISN04(TDM) (feature 59033834) the fieldrange of CHARGES is extended from10 to 12 digits.

BOOTH numeric string Variable Indicates the booth number (alwayszero for direct-dialed calls).

Active message exampleAPS100 APR18 18:43:05 6505 INFO APS LOG ENTRY



NN10275-909v14 12.01 06 October 2011


MSG COUNT= 4

CALLING DN= 1027835475

CALLED DN= 1027835482

DATE= 04/18

ANSWER TIME= 18:43

DURATION= 1

CHARGES= 655340000

BOOTH= 0



AUD397The Audit (AUD) subsystem generates log report AUD397 when the callprocessing base software detects one of the following:

• the abnormal termination of a call process

• a distinct problem with a call encapsulator (ENCAP)

If an abnormal termination of a call process occurs, the logs CCB dump(AUD395) and CDB dump (AUD398) can come with the AUD397 log.

Remedial actionn/a


Severity Warning

FormatAUD397 mmmdd hh:mm:ss ssdd INFO ENCAP DUMP

CALLID: <callid>

hhhh hhhh hhhh hhhh hhhh hhhh hhhh hhhh hhhh ....

AUD397 57


NN10275-909v14 12.01 06 October 2011



VariableDescription

INFO ENCAP DUMP Constant Fixed Indicates this report is a data dump ofENCAP.

CALLID Symbolic text Variable Provides the sequence number of thecall process affected. The value is 000if there was no call associated with theAUD397 log.

hhhh 0000 - FFFF Variable Indicates a dump of the callencapsulator in hex format.

Active message exampleAUD397 JUN02 19:09:44 4016 INFO ENCAP DUMP

CALLID: 0000 0000

4213 4674 0000 0001 001F FDCE 7BCD FDFD FDFD FDFD

FDFD FDFD FDFD FDFD FDFD FDFD FD07 FFFF 0000 FDFD

FDFD FDFD FDFD FDFD FDFD FDFD FDFD FDFD FDFD FDFD

FDFD FDFD FFFF 0000 FD00 FFFF 0000 FFFF 0000 0000

FDFC FDFD FDFD FDFD FDFD FDFD FDFD FDFD



AUD512This log is generated when a call death occurs during a calling card call.The log contains the contents of the office parameterMCCS_FEATURE_EXT etension block at the time of the call death.

Remedial actionWhen log AUD512 is generated, a customer service report is issued.


Severity Warning



NN10275-909v14 12.01 06 October 2011


FormatAUD512 mmmdd hh:mm:ss ssdd INFO EXT DUMP <callid>

<data>


VariableDescription

data 0 to FFFF Variable Contents of theMCCS_FEATURE_EXT extensionblock

Active message exampleAUD 512 MAY 7 20:31:19 4100 INFO EXT DUMP 0007 0010

FFFF 0000 8694 FDCI FDC2 FDFD FDFD



AUD616The Audit (AUD) subsystem generates this report whenever a call isfinished abnormally while holding an emergency extension block.Emergency extension blocks are allocated on indirect Calling Line Identity(CLI) two-stage calls and direct access account code calls, to determine ifan attempt is being made to route to an emergency number. This allocationis by the office parameter ALLOC_EMERGENCY_EXT_BLK.

Emergency extension blocks may be attached to:

• Indirect access two-stage CLI service calls. Indirect access is via thenetwork or another operator.

• Direct calls that access the account code feature using the Auto Line(AUL) SERVORD option, or using a feature activation code. Directaccess can be via Digital Private Network Signaling System (DPNSS),centrex Integrated Business Network (IBN) lines or Mercury ExchangeLine (MEL) trunks or lines.

Remedial actionThis log should be saved and used as additional information if the cause oftrap or failure of the call is not apparent, and is to be investigated. Anyother logs or traps output at the same time as this log should also bestored.

AUD616 59


NN10275-909v14 12.01 06 October 2011


The existence of the emergency extension block indicates that this couldbe an emergency call that has failed. This possibility should be pursued.


Severity Warning

FormatAUD616 mmmdd hh:mm:ss <seqno> INFO EXT DUMP <callid>

<hex data> .....


VariableDescription

Date Integers Variable Indicates the date the log is output

Time Integers Variable Indicates the time the log is output

seqno Integer Variable Indicates the sequence number of thelog

callid Integer Variable Indicates the identification of the call

hex data String, maximum sixwords

Variable Hexadecimal data for the contents ofthe emergency extension block at thetime the call was terminated

Active message exampleUKC4105AG AUD616 JAN24 14:32:15 2400 INFO EXT DUMP 0122 0002

FFFF 0000 9480 0019 0982 0000



AUD671The switch generates an AUD671 log report when a call is taken downabnormally and an XLAS extension block is held. Calls that use XLASextension blocks involve calling party category (CPC) routing or callednumber (CDN) translations.



NN10275-909v14 12.01 06 October 2011


Remedial actionSave the log report contents if you need to analyze the cause of the trap orcall failure. Also save the contents of other logs generated at the sametime.


Severity Warning

FormatAUD671 mmmdd hh:mm:ss ssdd INFO EXT DUMP

<call id> <data>


VariableDescription

call id numeric Variable Call identification.

data hexadecimal data Variable Hexadecimal contents of theXLAS_EXT_BLK when the call failed.

Active message exampleAUD671 OCT12 15:37:00 2600 INFO EXT DUMP

0122 0002 FFFF 0000 9480 0019 0982 0000



AUD677The Audit subsystem generates an AUD677 log report when a call is takendown abnormally and it is holding an indirect access extension block.

Indirect access extension blocks are attached to these types of indirectaccess call: Authcode calls (MONA), CLI screened calls (one-stage calls),account code calls and Registered Site Access calls (RSA).

Remedial actionSave the log report contents if you need to analyze the cause of the trap orcall failure. Also save the contents of other logs generated at the sametime.

AUD677 61


NN10275-909v14 12.01 06 October 2011



Severity Warning

FormatAUD677 mmmdd hh:mm:ss ssdd INFO EXT DUMP

<call id> <data>


VariableDescription

call id numeric Variable Identifies the call.

data hexadecimal string,maximum of six words

Variable Hexadecimal contents of the indirectaccess extension block when the callwas terminated.

Active message exampleAUD677 MAR25 08:52:14 9865 INFO EXT DUMP 5F9E 001E

FFFF 0000 D184 AAAA AAAA 00AA 0000 AAAA FDEA AAAA

AAAA AAAA FOAA FDC3 FDFD FDFD



AUDT120When a NETX71AA or TLBK71AA PUPS (Point-of-Use Power Supply)card fails to produce -100V in a drawer for NETX27AA and/or TLBR27AAline cards, this Info Log is produced to report the condition and the locationof the relevant drawer.

Remedial actionPerform the following action(s) to rectify the problem:

• Check the PUPS card of the drawer indicated in the log.

• Replace the card if faulty.



NN10275-909v14 12.01 06 October 2011



Severity Warning

FormatAUDT120 <DATE> <TIME> <SEQNO> INFO Device State Change

<TEXT_DATA>

<SITE> <EXT_NO> <DRWR_NO>


VariableDescription

DATE 5-alphanumericcharacters: 3characters for monthand 2 digits for day(mmmdd)

Variable Date of log generation

TIME 6 digits representinghours, minutes andseconds of the day(hh:mm:ss)

Variable Time of log generation. It alsoindicates the time that the test callwas started

SEQNO 4-digit number Variable Generation sequence number of thereport

TEXT_DATA Up to 64 characters Variable Reason for log

SITE 4 characters Variable Peripheral Module name that causedthe log (e.g. HOST)

EXT_NO 2-digit numberrepresenting thePeripheral Modulenumber

Variable Peripheral Module node numbers (e.g.05 0,...)

DRWR_NO 1-digit for PeripheralModule's drawernumber

Variable Peripheral Module drawer number

Active message exampleAUDT120 JUN05 20:57:12 9100 INFO NETX71/TLBK71 PUPS AUDIT

Drawer PUPS Card NETX71AA or TLBK71AA -100 V lost

U-Loop voltage failure for

LCME : HOST 5 0 DRAWER : 7

AUDT120 63


NN10275-909v14 12.01 06 October 2011




AUDT121When a drawer with NETX27AA and/or TLBR27AA line cards recoversfrom a previous PUPS (Point-of-Use Power Supply) card -100V failure, thisInfo Log is produced to report the condition and the location for therelevant drawer.

Remedial actionNo action is required. This Info Log is only used to report the recovery.


Severity Warning


<TEXT_DATA>



VariableDescription










NN10275-909v14 12.01 06 October 2011


Field Value Fixed orVariable

Description






Drawer PUPS Card NETX71AA or TLBK71AA -100 V is OK

U-Loop voltage recovery for




AUDT122For the NETX71AA or TLBK71AA PUPS (Point-of-Use Power Supply)audit to be efficient, some system resources (i.e. MTA - Metallic TestAccess) should be available. If the audit is inefficient for an LCME(Enhanced ISDN Line Concentrating ModulE) for more than one day (i.e.when no drawers, in an LCME, are being checked against the PUPSfailure) this Info Log is produced to report the situation.

Remedial actionPerform the following action:

• Check if there are enough MTA resources in the office for the LCMEscarrying TLBR27AA line cards. (Proper MTA is required for the audit tobe effective.)

• Check if there is missing test equipment.


Severity Warning

AUDT122 65


NN10275-909v14 12.01 06 October 2011



<TEXT_DATA>



VariableDescription













Drawer PUPS Card NETX71AA or TLBK71AA -100 V lost

U-Loop voltage failure for





NN10275-909v14 12.01 06 October 2011



AUDT133The Audit (AUDT) subsystem generates log report AUDT133 when the callprocessing audit finds a particular problem with a call encapsulator(ENCAP).

Remedial actionn/a


Severity Warning

FormatAUDT133 mmmdd hh:mm:ss ssdd INFO ENCAP AUDIT

INDEX: <primary index> <secondary index>

STATE: <encapsulator state>

PROBLEM: <text>


VariableDescription

INFO ENCAP AUDIT Constant Fixed Indicates that the Audit subsystemdetects an error with a callencapsulator.

INDEX Symbolic text Variable Indicates the primary and secondaryindex of the encapsulator.

STATE Character string Variable Indicates the state that theencapsulator was in at the time of thelog generation.

PROBLEM Character string Variable Indicates the problem that occurred.

Active message exampleAUDT133 JUN06 18:22:55 5081 INFO ENCAP AUDIT

INDEX: 001A 0005

STATE: UNAVAILABLE_ENC

PROBLEM : BAD_CCB_PTR

AUDT133 67


NN10275-909v14 12.01 06 October 2011




AUDT134The Audit (AUDT) subsystem generates log report AUDT134 when the callprocessing audit finds a particular problem with an encapsulator messagebuffer.

Remedial actionn/a


Severity Warning

FormatAUDT134 mmmdd hh:mm:ss ssdd INFO ENCAP_MSG_BUFFER AUDIT

INDEX: <primary index> <secondary index

PROBLEM: <text>


VariableDescription

INFOENCAP_MSG_BUFFER AUDIT

Constant Fixed Indicates that the Audit subsystemdetects an error with a callencapsulator message buffer.

INDEX Symbolic text Variable Indicates the primary and secondaryindex of the encapsulator messagebuffer.

PROBLEM Character string Variable Indicates the problem that occurred.

Active message exampleAUDT134 JUN02 18:54:46 5935 INFO ENCAP_MSG_BUFFER AUDIT

INDEX: 001F 000F

PROBLEM: ERROR_LINKS



NN10275-909v14 12.01 06 October 2011




C7TU108The CCS7 Test Utility (C7TU) subsystem generates this report to provideinformation on the status of a routeset.

This report is for test purposes only and is not generated in a field office.

Remedial actionC7TU users view this log during tests. No additional action is required.


Severity Indeterminate

FormatSwitch_Name C7TU108 DPC <dpc_pc>

<Routeset Status> CONGESTION LEVEL:n


VariableDescription

Switch_Name Constant Fixed Is the name of the switch on which theC7TU test are made.

CONGESTIONLEVEL

Integer Variable Indicates the level of congestion in theformat of one digit.

dpc Integer Variable Indicates the destination point code(DPC) in the CCITT7 Bangladeshformat of one digit, two digits, threedigits.

Routeset_Status AVAIL, UNAVAIL,OFFL

Variable Indicates the routeset status.

Active message exampleC04MMP15 C7TU108 DPC=CCITT7 BANGLADESH 6 05 004

ROUTESET AVAILABLE CONGESTION LEVEL:0

C7TU108 69


NN10275-909v14 12.01 06 October 2011




C7UP124The system generates log C7UP124 when the user executes commandGROUPCMD at the C7 trunk test position (C7TTP) level. The commanddoes not have to be complete for the system to generate the log.

Remedial actionIf the group command has failed on any trunk, the end-user may receive anumber of responses. The following table shows the responses and thevalid actions that can be taken.

<Routeset> is not the name of a routeset.

• Issued when you enter a routeset which does not have an entry in tableRTESET.

• Re-enter the command with the correct name of the routeset, or

• Define the name in the table C7RTESET and repeat the command.

The routeset has no point code.

• Issued when you enter a routeset which does not have point codedefined in table C7RTESET.

• Re-enter the command with the correct routeset, or

• Define the point code in table C7RTESET and repeat the command.

The range of CICs is too large. Maximum range for the start CIC is < >.

• Issued when the range of CICs given in the command is too large.

• Enter the correct range of CICs.

There are no trunks in the routeset.

• Issued when there are no trunks datafilled in table C7TRKMEM.

• Datafill trunks in table C7TRKMEM and repeat the command, or

• Repeat the command with a trunk that is datafilled.



NN10275-909v14 12.01 06 October 2011


<CLLI> is not the name of a trunkgroup.

• Issued when <CLLI> is not datafilled in table CLLI or TRKGRP or both.

• Check tables CLLI and TRKGRP and datafill the trunk group whereverit is missing and repeat the command, or

• Repeat the command with a trunkgroup that is datafilled.

The userpart of the trunkgroup is not supported.

• Issued when the userpart given in the command is not supported.

• Re-enter the command with a user part of Q767, or define the userpartof the trunk group as Q767 in table TRKSGRP and repeat thecommand.

There are no trunks in the trunkgroup.

• Issued when there are no trunks datafilled for the given trunk group inthe command.

• Check the datafill for the trunk group in the tables TRKMEM, TRKGRP,and TRKSGRP. Datafill the trunks for the missing trunk group. Repeatthe command

• Repeat the command for the trunkgroup that does have trunksdatafilled.

There are no CCS7 trunks in the trunk group.

• Issued when there are no CCS7 trunks in the trunk group.

• Check the datafill for the CCS7 trunks in table C7TRKMEM and repeatthe command.

Neither of the subgroups contain datafill.

• Issued when there are no subgroups defined for the trunkgroup givenin the command.

• Check the datafill in table TRKSGRP. Datafill missing information andrepeat the command

• Enter trunkgroup which has subgroups datafilled in table TRKSGRP.

The trunk group has a non-CCS7 subgroup.

• Issued when the trunk group given in the command has a non-CCS7subgroup datafilled in table TRKSGRP.

• Enter the command for a trunk group which only has CCS7 subgroupsdatafilled.

C7UP124 71


NN10275-909v14 12.01 06 October 2011


The subgroups of the trunkgroup are not in the same routeset.

• Issued when the subgroups of the trunkgroup given in the commandare datafilled in different routesets.

• Enter the command for the trunkgroup which has the subgroupsdatafilled in the same routeset.

The subgroups of the trunkgroup have different userparts.

• Issued when the subgroups of the trunkgroup given in the commandare datafilled for different userparts.

• Enter the command for the trunkgroup which has the subgroupsdatafilled for the same userpart (Q767).

Group (un) blocking is not supported for this trunkgroup.

• Issued when the group (un) blocking is not supported for thetrunkgroup given in the command.

• Check the datafill for the trunkgroup in tables TRKSGRP andADJNODE and change the datafill to make the trunkgroup eligible forgroup (un) blocking.

This command can affect a large number of trunks, and could send a largenumber of CCS7 messages. Execute the command? Please confirm("YES", "Y", or "NO", "N"):

• Issued when a correct command is entered.

• Enter "Y" to execute the command. The user may receive one of thefollowing prompts:

• The command will be executed, see C7UP124 log for the result.

• There are too many GroupCmd requests waiting to be executed. Re-enter command when one of these has finished.

• The command cannot be queued to be executed.

• The command has aborted due to a software error. See SWER logs formore information

• Enter "N" to cancel the command. The command will not execute.


Severity Warning

FormatC7UP124 mmmdd hh:mm:ss ssdd INFO GRPCMD RESULT



NN10275-909v14 12.01 06 October 2011


Originator: <USER>

Result: <STATES RESULT OF THE COMMAND>

Target: <CLLI> or

<ROUTESET>, CIC range: <STARTING CIC> to <LAST

CIC>, userpart: <USERPART>

<STATES MESSAGES>

State of trunks specified in command after execution:

<STATE of TRUNKS>: <NUMBER of TRUNKS>


VariableDescription

C7UP124 Constant Fixed Name of the log.

INFO GROUPCMDRESULT

Constant Fixed Indicates that the system generatesan INFO log as a result ofGROUPCMD.

ORIGINATOR Constant Fixed Indicates who generated the log.

<USER> Alphanumeric Variable User Id of who generated the log.

Result Constant Fixed Provides result of the commandexecuted.

<states result of thecommand>

Text Variable States if command executedsuccessfully.

<Target> Alphanumeric Variable States on which target the commandwas performed.

<CLLI> Alphanumeric Variable Provides the trunkgroup name that thecommand affects.

<routeset> Alphanumeric Variable Provides the routeset name.

CIC Range Constant Fixed Provides the CIC value range.

<Starting CIC> Numeric Variable Indicates the starting CIC value thatthe command affects.

<Last CIC> Numeric Variable Indicates the last CIC value that thecommand affects.

Userpart Constant Fixed Provides the userpart name

<Userpart> Alphanumeric Variable Provides the USERPART name

C7UP124 73


NN10275-909v14 12.01 06 October 2011



Description

<STATESMESSAGES>

Text Variable States the result of the command afterit is executed.

State of trunksspecified in commandafter execution

Constant Fixed Indicates the state of the trunksaffected by the command execution.

<State of trunks> Alphanumeric Variable Indicates the states of the trunksaffected by the command execution.

<number of trunks> Variable Variable Provides the number of the trunksaffected by the command execution.

Active message exampleC7UP124 JAN28 17:51:47 2100 INFO GROUPCMD RESULT

Originator: TEAM_7

Result: Command executed without any errors

Trunkgroup: ETSI666GENIE

11 out of 11 trunks have been rts (unblocked) by this

command.

State of trunks specified in command after execution:

IDL: 11



C7UP602Call processing generates log report C7UP602 to assist the operatingcompany in tracking failure messages that are of particular interest. Logreport C7UP602 will be generated only if the LOG field of a LINES or aCAS tuple in table FAIL2TMT is set to Y and the call gets accessed by call-processing

Remedial actionThe action to be taken is a matter determined by operating companyprocedure. If no action is required, the LOG field in table FAIL2TMT shouldbe changed to N so no further C7UP602 logs are generated.



NN10275-909v14 12.01 06 October 2011



Severity Warning

FormatC7UP602 mmmdd hh:mm:ss ssdd INFO MSG (table FAIL2TMT)

CKT clli nn

Has reported msg: protocol and message

Treatment set: result from table FAIL2TMT

Incoming agent: CKT clli nn

or

Incoming agent: LEN len DN dn


VariableDescription

INFO MSG (tableFAIL2TMT)

Constant Fixed Indicates that a tuple of tableFAIL2TMT has been accessed by CallProcessing

CKT alphanumeric (nn) Variable Provides CLLI. Indicates which trunkreturned the failure message

Has reported msg Symbolic text Variable Represents the failure messagereceived

Treatment set Character string Variable Represents whichever treatment wasset by table FAIL2TMT

Incoming agent Alphanumeric Variable Indicates which incoming agent hashad treatment applied: CKT clli nn orLEN len DN dn

Active message exampleC7UP602 OCT25 04:35:30 6282 INFO MSG (table FAIL2TMT)

CKT BTUP50IC 0

Has reported msg: BTUP SEN

Treatment set: TESS

C7UP602 75


NN10275-909v14 12.01 06 October 2011


Incoming agent: CKT ISSU12WBT 0

CENTREX C7UP602 DEC02 09:24:42 1100 INFO MSG (table

FAIL2TMT)

CKT MCL0202BTBWE 1


Treatment set: TESS

Incoming agent: LEN HOST 00 0 07 04 DN 2753000



C7UP603When a two-stage call that originates on either BTUP (UK variant ofnational user part) or Digital Private Network Signaling System No. 1(DPNSS) trunks fails to complete successfully, and a fail message isreceived by the European DMS-100 (DMS-100E) switch, table FAIL2STGis indexed with the fail message and terminating agent. If field LOG in tableFAIL2STG is datafilled with Y (yes), the C7UP603 log report is generatedwith the fail message.

The generation of log C7UP603, which is used to track particular failmessages, is controlled by the operating company.

This log was introduced by design activity AG4761, "UK Two-Stage CallFailure Handling," in software release EUR004.

Remedial actionThe action to be taken is at the discretion of the operating company. If noaction is required, set the LOG field in table FAIL2STG to N (no) to preventthe generation of C7UP603 logs.


Severity Warning

FormatC7UP603 mmdd hh:mm:ss ssdd INFO MSG (Table FAIL2STG)



NN10275-909v14 12.01 06 October 2011


Agent: <CLLI/LEN>

Has reported message: <protocol and message>

To be handled as: <result from table FAIL2STG>

Incoming agent: <CLLI>

Outgoing agent: <CLLI/LEN>

Called number: <digits>


VariableDescription

INFO MSG (TableFAIL2STG)

INFO MSG (TableFAIL2STG)

Variable indicates a tuple in table FAIL2STGthat has been accessed

Agent CLLI or LEN Variable indicates which agent returned the failmessage or treatment

Has reportedmessage

protocol and message Variable indicates the fail message received

To be handled as action from tableFAIL2STG

Variable indicates how the fail message is tobe handled by table FAIL2STG

Incoming agent CLLI Variable indicates which protocol the failure ismapped to

Outgoing agent CLLI or LEN Variable indicates which agent returned the failmessage or treatment

Active message exampleC7UP603 MAY10 12:42:09 8798 INFO MSG (Table FAIL2STG)

Agent: CKT BNRBTUP2


To be handled as: TREAT BUSY

Incoming agent: BNRBTUP

Outgoing agent: BNRBTUP2

Called number: 8904011


C7UP603 77


NN10275-909v14 12.01 06 October 2011



CCHK100The CCBHNG tool can detect long call or hung calls. The switch savesinformation about a maximum of 50 of these calls in a buffer. When thebuffer exceeds the upper limit, a CCHK100 log is generated. If the bufferexceeds the upper limit, a CCHK100 log is generated for every new caseuntil the buffer is cleared.

Remedial actionBefore you clear the CCBHNG buffer, examine the data that has beencollected.

If the data is related to hung calls, contact Nortel Networks TechnicalSupport.

If the data is related to long calls, check that the calls are actually longcalls.

If you observe an abnormal situation, contact Nortel Networks TechnicalSupport.

To enable the switch to save new data, clear the CCBHNG buffer using theBUFFCLR command.


Severity Warning

FormatCCHK100 mmmdd hh:mm:ss ssdd INFO CCBHNG BUFFER REPORT

REASON: The CCBHNG buffer is full


VariableDescription

CCBHNG BUFFERREPORT

Constant Fixed Event label

The CCBHNG bufferis full

Constant Fixed Log body

Active message exampleCCHK100 AUG11 18:14:33 7000 INFO CCBHNG BUFFER REPORT



NN10275-909v14 12.01 06 October 2011


REASON: The CCBHNG buffer is full



CCS800Common Channel Signaling (CCS) subsystem report CCS800. Thesubsystem generates CCS800 when an error occurs during the cutover ofCCS7 links from LIU7s on an LPP or FLPP to a Universal Signaling Point(USP).

This log generates a major alarm.

Remedial actionAs described in Action text.


Severity • Warning

• Major

FormatCCS800 mmmdd hh:mm:ss ssdd INFO USP Cutover Error

USP Cutover error has occurred

Problem : <problem description>

Action : <action description>


VariableDescription

INFO USP CutoverError

Constant Fixed Indicates that an error has occurredduring the LIU7 to USP cutover.

Problem:<problemdescriptions>

Symbolic text Variable Identifies the problem encounteredduring the cutover.

Action:<actiondescription>

Symbolic text Variable Identifies the action required to solvethe problem encountered during thecutover.

CCS800 79


NN10275-909v14 12.01 06 October 2011


Active message exampleCCS800 SEP05 18:14:33 4827 INFO USP Cutover Error

USP Cutover error has occurred

Problem : Could not return the linkset to service.

Action : Contact the next level of support



CCS801Common Channel Signaling (CCS) subsystem report CCS801. Thesubsystem generates CCS801 when the USPCUTOVR directory has beenaccessed.

Remedial actionn/a


Severity Warning

FormatCCS801 mmmdd hh:mm:ss ssdd INFO USP Cutover Utility

USP Cutover Utility (USPCUTOVR) invoked.


VariableDescription

INFO USP CutoverUtility

Constant Fixed Indicates the USP Cutover utility isactive.

USP Cutover Utility(USPCUTOVR)invoked

Constant Fixed Indicates that the USPCUTOVRdirectory has been accessed.

Active message exampleCCS801 SEP05 18:14:33 4827 INFO USP Cutover Utility

USP Cutover Utility (USPCUTOVR) invoked.



NN10275-909v14 12.01 06 October 2011




CCS802Common Channel Signaling (CCS) subsystem report CCS802. Thesubsystem generates CCS802 when the USPCUTOVR commandSTARTCUT is entered.

Remedial actionn/a


Severity Warning


USP Cutover started.


VariableDescription



USP Cutover started Constant Fixed Indicates that the USPCUTOVRcommand STARTCUT has beenentered.


USP Cutover started.


CCS802 81


NN10275-909v14 12.01 06 October 2011



CCS803Common Channel Signaling (CCS) subsystem report CCS803. Thesubsystem generates CCS803 when the USPCUTOVR commandSTOPCUT is entered.

Remedial actionn/a


Severity Warning


USP Cutover stopped.


VariableDescription



USP Cutover stopped Constant Fixed Indicates that the USPCUTOVRcommand STOPCUT has beenentered.


USP Cutover stopped.



CCS804Common Channel Signaling (CCS) subsystem report CCS804. Thesubsystem generates CCS804 when the USPCUTOVR commandCUTOVLS with a link set name has been entered.



NN10275-909v14 12.01 06 October 2011


Remedial actionn/a


Severity Warning


Linkset cutover completed

Linkset : <linkset name>


VariableDescription



Linkset cutovercompleted

Constant Fixed Indicates the specified linkset hasbeen cutover from the LIU7 to theUSP.

Linkset :<linksetname>

Symbolic text Variable Identifies the linkset that has beencutover.


Linkset cutover completed.

Linkset : LS000001



CCS805Common Channel Signaling (CCS) subsystem report CCS804. Thesubsystem generates CCS804 when the USPCUTOVR commandABORTLS with a link set name has been entered.

This log generates a minor alarm.

CCS805 83


NN10275-909v14 12.01 06 October 2011


Remedial actionn/a



• Minor


Linkset cutover aborted.

Linkset : <linkset name>


VariableDescription



Linkset cutoveraborted

Constant Fixed Indicates the specified linkset cutoverfrom the LIU7 to the USP has beenaborted.

Linkset :<linksetname>

Symbolic text Variable Identifies the linkset whose cutoverhas been aborted.


Linkset cutover aborted.

Linkset : LS000001



CCS808Common Channel Signaling (CCS) subsystem report CCS808. Thesubsystem generates CCS808 when the USPCUTOVR commandCLEANUP has completed.



NN10275-909v14 12.01 06 October 2011


Remedial actionn/a


Severity Warning


USP Cutover SS7 data cleanup completed.

USP is master of SS7 data and signaling


VariableDescription



USP Cutover SS7data cleanupcompleted USP ismaster of SS7 dataand signaling

Constant Fixed Indicates that the USPCUTOVRcommand CLEANUP has beencompleted and the USP is handling allSS7 signaling.


USP Cutover SS7 data cleanup completed

USP is master of SS7 data and signaling



CDR268The Call Detail Recording (CDR) system generates log report CDR268 orlog report CDR269 whenever a user enables CDR log output with theCDRSET ACTLOG ON command at the CDR level of the MAP display.The value of the office parameter CDR_LOG_FIELD_DESCRIPTORS in

CDR268 85


NN10275-909v14 12.01 06 October 2011


table OFCVAR determines the CDR log format. A value of Y generates thelong log report CDR269. A value of N generates the short log reportCDR268.

Do not enable CDR logging during heavy traffic periods. CDR logging cancause excessive log subsystem buffering, which slows system response.

Remedial actionn/a


Severity Warning

FormatCDR268 mmmdd hh:mm:ss ssdd INFO CDR_CALL_ENTRY

RECCDORIGTIMEDISCTIMECALLDUR ORIGCLLIORIGMEM

TERMCLLI TERMEM

BILLNUMCUSTCOSTBILLTYPEDESTNUMSUPPSERV NETCGID

ANSDETTIMECHGSEQNUM


VariableDescription

RECCD D Variable Return code indicating a CDR

ORIGTIME month 01-12 day01-31 hour 00-23minute 00-59 second00-59

Variable Indicates the date and time the calloriginates

DISCTIME month 01-12 day01-31 hour 00-23minute 00-59 second00-59

Variable Indicates the date and time the calldisconnects

CALLDUR 00000000-21474835 Variable Indicates the amount of timemeasured in seconds between answerand disconnect

ORIGCLLI CLLI Variable Identifies common language locationidentifier (CLLI) of the originating trunkgroup. Refer to Table I of any LogReport Reference Manual .



NN10275-909v14 12.01 06 October 2011



Description

ORIGMEM 0-999 Variable Identifies the originating trunk memberin the originating trunk group

TERMCLLI CLLI Variable Identifies the CLLI of the terminatingtrunk group. Refer to Table I of anyLog Report Reference Manual .

TERMEM 0-999 Variable Identifies the terminating trunkmember in the originating trunk group

BILLNUM up to 16 Variable digits Identifies the billing number forthe call. The billing number consists ofthe authorization code, the fullnational number (FNN), or the creditcard number.

CUSTCOST symbolic text Variable Identifies the cost center number. Thisfield is left-justified.

BILLTYPE 0-9 Variable Identifies the type of number in theBILLNUM field. The following are thecurrent BILLTYPE field values:

• 0--authorization code (singlestage override) processed

• 1--FNN

• 2--credit card number

• 5--calling line identification (CLI)registered customers

• 6--authcode customers

• 3, 4, 7-9--reserved for future use

DESTNUM up to 18 digits Variable Indicates the called party number

SUPPSERV 0-63 Variable Provides the bearer capability of thefollowing ISDN services beingsupplied:

• 0--NIL (NIL_BC)

• 1--speech (BC_SPEECH)

• 2--64 Kbit unrestricted data(BC_64K_DATA)

• 3--64 Kbit X.25 data(BC_64K_DATA)

• 4--56 Kbit data (BC_56K_DATA)

• 5--data unit (BC_DATAUNIT)

CDR268 87


NN10275-909v14 12.01 06 October 2011



Description

• 6--64 Kbit restricted(BC_64K_DATA)

• 7--3.1 KHz audio (BC_3_1_KHZ)

• 8--7.0 Khz audio(BC_7_KHZ)

• 9--voice data (BC_VOICE_DATA)

• 10--BC_64_RATE_AD_DATA

• 11-63--reserved for future use

NETCGID 0-4096 Variable Provides the customer network ID

ANSDET Y or N Variable Confirms if an answer is detected

TIMECHG Y or N Variable Confirms a time discontinuity

SEQNUM 0000000- 9999999 Variable Contains the call identification numberserially assigned to each call atdisconnect

Active message exampleCDR268 JANO3 09:38:08 8596 INFO CDR_CALL_ENTRY

F0109880103093058 1988010309380700000426CUSTOMER

1 CUST1TRK1 5 23661001 15283001

5283001 040000 YCUSA IBN2500002871



CDR269 Format 1The Call Detail Recording (CDR) system generates log report CDR268 orlog report CDR269 whenever a user enables CDR log output with theSETLOG ALL command at the CDR level of the MAP display.

Do not enable CDR logging during heavy traffic periods. CDR logging cancause excessive log subsystem buffering, which slows system response.

Remedial actionn/a



NN10275-909v14 12.01 06 October 2011



Severity Warning


RECCD n

ORIGTIME mmddhhmmss

DISCTIME mmddhhmmss

CALLDUR nnnnn

ORIGCLLI nnnnnnnnnnnn

ORIGMEM nnnn

TERMCLLI nnnnnnnnnnnn

TERMEM nnnn

COMPCD n

TRMTCD nnn

ANSDET n

TIMECHG n

FAILURE n

BILLNUM nnnnnnnnnnnnnnnn

BILLTYPE n

CUSTCOST nn

DESTNUM nnnnnnnnnnnnnnnnnn

SUPPSERV nn

NETCGID nnnn

NETID nnnnnnnnnnnn

CDR269 Format 1 89


NN10275-909v14 12.01 06 October 2011


NCOS nnn

SEQNUM nnnnnnnn


VariableDescription


Variable Indicates the date and time the calloriginates. In Format 2, ORIGTIME isthe hour, minute and second.

DISCDATE day 01-31 month01-12

Variable In Format 2, the day and month thecall disconnects.


Variable Indicates the date and time the calldisconnects. In Format 2, only thehour, minute and second that the calldisconnects


ORIGCLLI CLLI Variable Refer to Table I of any Log ReportReference Manual . Identifiescommon language location identifier(CLLI) of the originating trunk group


TERMCLLI CLLI Variable Refer to Table I. Identifies the CLLI ofthe terminating trunk group

TERMMEM 0-999 Variable Identifies the terminating trunkmember in the originating trunk group

COMPCD 0-3 Variable Defines the call completion code. Thefollowing are possible COMPCD fieldvalues:

• 0 -- normal completed call

• 1 -- treated call

• 2 -- abandoned call

• 3 -- abnormal call

• 4 -- first record of a long-durationcall

• 5 -- intermediate record of a long-duration call



NN10275-909v14 12.01 06 October 2011



Description

• 6 -- last record of a long-durationcall

• 7 -- spare

TRMTCD 0-255 Variable Provides the treatment code

ANSDET Y or N Variable Confirms if an answer is detected

CLASSMK alphanumeric Variable Indicates bearer capability, in 7 bytesof EBCDIC

TIMECHG Y or N Variable Confirms a time discontinuity

FAILURE Y or N Variable Confirms a failure

BILLNUM up to 16 digits Variable Identifies the billing number for thecall. The billing number consists of theauthorization code, the full nationalnumber (FNN), or the credit cardnumber.

BILLTYPE 0-9 Variable Identifies the type of number in theBILLNUM field. The following are thecurrent BILLTYPE field values:

• 0 -- authorization code (singlestage override) processed

• 1 -- FNN

• 2 -- credit card number

• 5 -- calling line identification (CLI)registered customers

• 6 -- authcode customers

• 3, 4, 7-9 -- reserved for future use

CUSTCOST symbolic text Variable Identifies the cost center number. Thisfield is left-justified.

DESTNUM up to 18 digits Variable Indicates the called party number

SUPPSERV 0-63 Variable Provides the bearer capability of thefollowing ISDN services beingsupplied:

• 0 -- NIL (NIL_BC)

• 1 -- speech (BC_SPEECH)

• 2 -- 64 Kbit unrestricted data(BC_64K_DATA)

• 3 -- 64 Kbit X.25 data(BC_64K_DATA)

CDR269 Format 1 91


NN10275-909v14 12.01 06 October 2011



Description

• 4 -- 56 Kbit data (BC_56K_DATA)

• 5 -- data unit (BC_DATAUNIT)

• 6 -- 64 Kbit restricted(BC_64K_DATA)

• 7 -- 3.1 KHz audio (BC_3_1_KHZ)

• 8 -- 7.0 Khz audio(BC_7_KHZ)

• 9 -- Vvoice data(BC_VOICE_DATA)

• 10 -- BC_64_RATE_AD_DATA

• 11-63 -- reserved for future use

NETCGID 0-4096 Variable Provides the customer network ID

NCOS 0-255 Variable Provides the network class of service(NCOS) of the originating agent in thecall

SEQNUM 0000000- 9999999 Variable Contains the call identification numberserially assigned to each call atdisconnect

RECCD D E G Variable Return code indicating a 46-byte CDR

Return code indicating a 100-byteCentrex

Variable Return code indicating an INAP CDR

ORIGDATE day 01-31 month01-12

Variable In format 2, the day and month the calloriginates.


RECCD D

ORIGTIME 0103093058

DISCTIME 0103093807

CALLDUR 429

ORIGCLLI CUSTOMER1

ORIGMEM

TERMCLLI CUST1TRK1



NN10275-909v14 12.01 06 October 2011


TERMEM 5

COMPCD 0

TRMTCD 000

ANSDET Y

TIMECHG N

FAILURE N

BILLNUM 0712361001

BILLTYP 1

CUSTCOST

DESTNUM 92364000

SUPPSERV 00

NETCGID 000

NETID

NCOS

SEQNUM 0002871

CENTREX CDR269 JUN07 11:09:29 0900 INFO CDR_CALL_ENTRY

RECCD E

ORIGDATE 158

ORIGTIME 40143

DISCDATE 158

DISCTIME 40168

CALLDUR 00020

ORIGCLLI BNR0201BTBWE

ORIGMEM

CDR269 Format 1 93


NN10275-909v14 12.01 06 October 2011


TERMCLLI BNR0202BTBWE

TERMEM 2

BILLNUM 6282753107

CUSTCOST

BILLTYP 1

DESTNUM 2023106

TRMTCD 000

COMPCD 0

SUPPSERV

CLASSMK A 63

ANSDET Y

SEQNUM 0000110



CDR270The Call Detail Recording (CDR) system generates log report CDR270 atthe time checks specified for the recording of long calls. All calls identifiedas meeting the long-duration call description are printed out in a combinedlog format in log report CDR270.

Remedial actionn/a


Severity Warning




NN10275-909v14 12.01 06 October 2011


RECCD n

ORIGTIME mmddhhmmss

DISCTIME mmddhhmmss

CALLDUR nnnnn


ORIGMEM nnnn


TERMEM nnnn


COMPCD n

RECCD n

ORIGTIME mmddhhmmss

DISCTIME mmddhhmmss

CALLDUR nnnnn


ORIGMEM nnnn


TERMEM nnnn


COMPCD n

CDR270 95


NN10275-909v14 12.01 06 October 2011



VariableDescription

RECCD D Variable Return code indicating a CDR


Variable Indicates the date and time the calloriginates


Variable Indicates the date and time the calldisconnects


ORIGCLLI CLLI Variable Refer to Table I of any Log ReportReference Manual . Identifiescommon language location identifier(CLLI) of the originating trunk group


TERMCLLI CLLI Variable Refer to Table I of any Log ReportReference Manual . Identifies the CLLIof the terminating trunk group

TERMEM 0-999 Variable Identifies the terminating trunkmember in the originating trunk group

BILLNUM up to 16 digits Variable Identifies the billing number for thecall. The billing number consists of theauthorization code, the full nationalnumber (FNN), or the credit cardnumber.

COMPCD 0-3 Variable Defines the call completion code. Thefollowing are possible COMPCD fieldvalues:

• 0--normal completed call

• 1--treated call

• 2--abandoned call

• 3--abnormal call

• 4--first record of a long-durationcall



NN10275-909v14 12.01 06 October 2011



Description

• 5--intermediate record of a long-duration call

• 6--last record of a long-durationcall

• 7--spare


RECCD D

ORIGTIME 0103093000

DISCTIME

CALLDUR 42300

ORIGCLLI CUSTOMER1

ORIGMEM

TERMCLLI CUST1TRK1

TERMEM 5

BILLNUM 0712361001

COMPCD 4

RECCD D

ORIGTIME 0103041500

DISCTIME

CALLDUR 28800

ORIGCLLI CUSTOMER2

ORIGMEM

TERMCLLI CUST2TRK8

TERMEM 5

CDR270 97


NN10275-909v14 12.01 06 October 2011


BILLNUM 0812588934

COMPCD 5



CDR600This log is a short version of CDR601 log. (For detailed field descriptions,see CDR601 log documentation.) Only one of these logs (either the shortor long version) can be generated at a time.

This log displays the information contained in the call history recordassociated with a basic call (non-private network, non-operator service) ifthe call detail recording (CDR) billing record has been formatted.

To generate this log, complete the following:

• In table OFCVAR, set CDR_LOG_FIELD_DESCRIPTORS to "N" forthe short version of the log.

• In table OFCENG, set CDR_ENABLE_LOG_ALL to "Y" to log normalcalls (this activates treatment code 00).

• At the CDR level (mapci;mtc;cdr) of the MAP terminal, use theSETLOG command to select treatment codes for which this log isneeded.

• Make a basic (non-private network, non-operator service) call on theEuropean DMS-100 switch.

Remedial actionNo action is required. This log is for information only.


Severity Warning

FormatCDR600 date time seqnbr INFO CDR SHORT LOG

crid cdid tp1 tp6 tp7 op tp otg ttg tp3q tp6q ac otc ttc

id fc tne nat tp7q ec pd ndid divid dof cc inet ro cd de dtsa nocli en acif



NN10275-909v14 12.01 06 October 2011


ss7_cause tp3 ain cli a d ptd

Active message exampleCDR600 FEB23 03:17:00 8000 INFO CDR SHORT LOG

01 4001 02/23/2000/03:15:46 02/23/2000/03:16:00

02/23/2000/03:16:03 0023 0103 4001 2112 03 0 01 01 02 00

03 01 00 00 020 0 0 0 0 1 0 0 0 0 1 0 06 234 15 000

02/23/2000/03:15:50 222 2142453646 1234567890123456789012

0123456789



CDR601This log is the long version of CDR600 log. Only one of these logs (eitherthe short or long version) can be generated at a time.

This log displays the information contained in the call history recordassociated with a basic call (non-private network, non-operator service) ifthe call detail recording (CDR) billing record has been formatted.


• In table OFCVAR, set CDR_LOG_FIELD_DESCRIPTORS to "Y" forthe long version of the log.


• At the CDR level (mapci;mtc;cdr) of the MAP terminal, use theSETLOG command to select treatment codes for which this log isneeded.

• Make a basic (non-private network, non-operator service) call on theEuropean DMS-100 switch.


CDR601 99


NN10275-909v14 12.01 06 October 2011



Severity Warning

FormatCDR601 date time seqnbr INFO CDR LONG LOG

CRID crid

CDID cdid

TP1 tp1

TP6 tp6

TP7 tp7

OP op

TP tp

OTG otg

TTG ttg

TP3Q tp3q

TP6Q tp6q

AC ac

OTC otc

TTC ttc

ID id

FC fc

TNC tnc

NAT nat

TP7Q tp7q

EC ec



NN10275-909v14 12.01 06 October 2011


PD pd

NDID ndid

DIVID divid

DOF dof

CC cc

INET inet

RO ro

CD cd

DE de

DT dt

SA sa

NOCLI nocli

CN en

ACIF acif

SS7_CAUSE ss7_cause

TP3 tp3

AIN ain

CLI cli

A a

D d

PTD ptd


VariableDescription

CRID 0-15 (decimal) Variable Call record ID.

CDID 0-4095 (decimal) Variable Call disconnect ID.

CDR601 101


NN10275-909v14 12.01 06 October 2011



Description

TP1 MO/DA/YR/HH:MM:SS

Variable Time point 1. Range of MO is 1-12,DA is 1-31, YR is 1976-9999, HH is00-23, MM is 00-59, and SS is 00-59.





OP 0-9999 (decimal) Variable Originating port.

TP 0-9999 (decimal) Variable Terminating port.

OTG 0-8191 (decimal) Variable Originating trunk group.

TTG 0-8191 (decimal) Variable Terminating trunk group.

TP3Q 0-15 (decimal) Variable TP3 qualifier.


AC 0-63 (decimal) Variable Action code.

OTC 0-15 (decimal) Variable Originating trunk class.

TTC 0-15 (decimal) Variable Terminating trunk class.

ID 2 TBCD Digits Variable Info digits.

FC 0-15 (decimal) Variable Feature code.

TNC 0-15 (decimal) Variable Terminating net code.

NAT 0-15 (decimal) Variable Network access type.


EC 0-127 (decimal) Variable Entry code.

PD 0-7 (decimal) Variable Prefix digits.

NDID 0-7 (decimal) Variable NCS/DAP ID.

DIVID 0-7 (decimal) Variable Division ID.

DOF 0-1 (binary) Variable Distant overflow.

CC 0-1 (binary) Variable Customer connect.

INET 0-1 (binary) Variable Internetwork.

RO 0-1 (binary) Variable Reported overflow.

CD 0-1 (binary) Variable Call direction.

DE 0-1 (binary) Variable Destination.

DT 0-1 (binary) Variable Dedicated terminal.

SA 0-1 (binary) Variable Satellite.



NN10275-909v14 12.01 06 October 2011



Description

NOCLI 0-15 (decimal) Variable Nature of CLI.

CN 0-4 TBCD digits Variable Carrier number.

ACIF 0-4 TBCD digits Variable Auth code ID field.

SS7_CAUSE 0-127 (decimal) Variable SS7 release value.



AIN 0-255 (decimal) Variable ANI index.

CLI 0-10 TBCD digits Variable Calling line ID.

A 0-22 TBCD digits Variable Billing field "A."

D 0-17 TBCD digits Variable Destination address.

PTD 0-10 TBCD digits Variable PreTranslation digits.

Active message exampleCDR601 FEB23 03:17:00 8000 INFO CDR LONG LOG

CRID 01

CDID 4001

TP1 02/23/2000/03:15:46

TP6 02/23/2000/03:16:00

TP7 02/23/2000/03:16:03

OP 0023

TP 0103

OTG 4001

TTG 2112

TP3Q 03

TP6Q 0

AC 01

OTC 01

CDR601 103


NN10275-909v14 12.01 06 October 2011


TTC 02

ID 00

FC 03

TNC 01

NAT 00

TP7Q 00

EC 020

PD 0

NDID 0

DIVID 0

DOF 0

CC 1

INET 0

RO 0

CD 0

DE 0

DT 1

SA 0

NOCLI 06

CN 234

ACIF 15

SS7_CAUSE 000

TP3 02/23/2000/03:15:50

AIN 222



NN10275-909v14 12.01 06 October 2011


CLI 2142453646

A 1234567890123456789012

D 01234567899901234567

PTD 0123456789



CDR602This log is a short version of CDR603 log. (For detailed field descriptions,see CDR603 log documentation.) Only one of these logs (the short or longversion) can be generated at a time.

This log displays the information contained in the call history recordassociated with a private network call if a PNR billing record has beenformatted.

To generate this log, complete the following steps:

• In table OFCVAR, set CDR_LOG_FIELD_DESCRIPTORS to "N" forthe short version of the log report.


• At the call detail recording (CDR) level (mapci;mtc;cdr) of the MAPterminal, use the SETLOG command to select treatment codes forwhich this log is needed.

• Make a private network call on the European DMS-100 switch.



Severity Warning

FormatCDR602 date time seqnbr INFO PNR SHORT LOG


CDR602 105


NN10275-909v14 12.01 06 October 2011


id fc me nat tp7q ec pd ndid divid dof cc inet ro cd de dtsa nocli en acif

ss7_cause tp3 ain cli a d ptd

Active message exampleCDR602 FEB23 03:17:00 8000 INFO PNR SHORT LOG

03 4001 02/23/2000/03:15:46 02/23/2000/03:16:00

02/23/2000/03:16:03 0023 0103 4001 2112 03 0 01 01 02 00

03 01 00 00 020 0 0 0 0 1 0 0 0 0 1 0 06 234 15 000

02/23/2000/03:15:50 222 2142453646 1234567890123456789012

012345678901234567 0123456789



CDR603This log is the long version of CDR602 log. Only one of these logs (theshort or long version) can be generated at a time.

This log displays the information contained in the call history recordassociated with a private network call if a PNR billing record has beenformatted.


• In table OFCVAR, set CDR_LOG_FIELD_DESCRIPTORS to "Y" forthe long version of the log report.



• Make a private network call on the European DMS-100 switch.




NN10275-909v14 12.01 06 October 2011



Severity Warning

FormatCDR603 date time seqnbr INFO PNR LONG LOG

GRID crid

CDID cdid

TP1 tp1

TP6 tp6

TP7 tp7

OP op

TP tp

OTG otg

TTG ttg

TP3Q tp3q

TP6Q tp6q

AC ac

OTC otc

TTC ttc

ID id

FC fc

TNC tnc

NAT nat

TP7Q tp7q

EC ec

CDR603 107


NN10275-909v14 12.01 06 October 2011


PD pd

NDID ndid

DIVID divid

DOF dof

CC cc

INET inet

RO ro

CD cd

DE de

DT dt

SA sa

NOCLI nocli

CN en

ACIF acif

SS7_CAUSE ss7_cause

TP3 tp3

AIN ain

CLI cli

A a

D d

PTD ptd


VariableDescription

GRID 0-15 (decimal) Variable Call record ID.




NN10275-909v14 12.01 06 October 2011



Description

































CDR603 109


NN10275-909v14 12.01 06 October 2011



Description



ACIF 0-15 (decimal) Variable Auth code ID field.









Active message exampleCDR603 FEB23 03:17:00 8000 INFO PNR LONG LOG

CRID 03

CDID 4001

TP1 02/23/2000/03:15:46

TP6 02/23/2000/03:16:00

TP7 02/23/2000/03:16:03

OP 0023

TP 0103

OTG 4001

TTG 2112

TP3Q 03

TP6Q 0

AC 01

OTC 01



NN10275-909v14 12.01 06 October 2011


TTC 02

ID 00

FC 03

TNC 01

NAT 00

TP7Q 00

EC 020

PD 0

NDID 0

DIVID 0

DOF 0

CC 1

INET 0

RO 0

CD 0

DE O

DT 1

SA 0

NOCLI 06

CN 234

ACIF 15

SS7_CAUSE 000

TP3 02/23/2000/03:15:50

AIN 222

CDR603 111


NN10275-909v14 12.01 06 October 2011


CLI 2142453646

A 1234567890123456789012

D 012345678901234567

PTD 0123456789




This log displays the information contained in the expanded billing recordassociated with an operator service call if an ECDR billing record has beenformatted.



• In table OFCENG, set CDR_ENABLE_LOG_ALL to "Y" to log normal(treatment 00) calls; otherwise, set CDR_ENABLE_ LOG_ALL to "N."


• Make an operator service call on the European DMS-100 switch thatsatisfies one or more conditions in the following table.

Call involved in a direct terminating overflow at this switch-The desiredterminating switch ID and desired terminating trunk group upon which thecall is supposed to terminate is recorded using an expanded record(ECDR/EPNR/EOSR/EPOSR).

Calling line ID is greater than 10 digits-All digits are recorded using anexpanded record (ECDR/EPNR/EOSR/EPOSR).

Destination address is greater than 17 digits-All digits are recorded usingan expanded record (ECDR/EPNR/EOSR/EPOSR).



NN10275-909v14 12.01 06 October 2011


Pretranslation digits (PTD) field is greater than 10 digits in the CDR/PNR-The PTDs are recorded using an expanded record (ECDR/EPNR/EOSR/EPOSR). OSR and POSR do not contain a PTD field. EOSR writes a PTDfield, but no call processing is defined to cause the PTD field length totrigger an EOSR or EPOSR.

More than 22 auth digits (including supp codes) are used-The auth digitsare recorded using an expanded record (ECDR/EPNR/EOSR/ EPOSR).

A wideband call (NX64) is recorded-The originating X channels andterminating X channels are recorded using an expanded record. Theexpanded record writes a bitmap of the channels used on a T1 interface(ECDR/EPNR only).

An EVS/NARS call is recorded (NARS switch)-The EVS applicationcounter values are recorded using an expanded record (EOSR/EPOSRonly).

TCGUEST or TCROOM functionality is used-An EOSR/EPOSR call recordis required.



Severity Warning

FormatCDR604 date time seqnbr INFO ECDR SHORT LOG


id fc tnc nat tp7q ec pd ndid divid dof cc inet ro cd de dtsa nocli en acif

ss7_cause tp3 ain cli a d ptd mno ovfval ovfcs ovfcl dtaovfc dtac

orig_nx64 term_nx64

Active message exampleCDR604 FEB23 03:17:00 8000 INFO ECDR SHORT LOG

06 4002 02/23/2000/03:15:46 02/23/2000/03:16:00

CDR604 113


NN10275-909v14 12.01 06 October 2011


02/23/2000/03:16:03 0023 0103 4001 2112 03 00 01 01 02 00

03 01 00 0 020 0 0 0 0 1 0 0 0 0 1 0 06 234 15 000

02/23/2000/03:15:50 222 2142453646

123456789012345678901234567890123456789012345

2145551212 00 1 0 0 12 010101234 125 13 B2345 CA6743



CDR605This log is the long version of CDR604. Only one of these logs (the short orlong version) can be generated at a time.

This log displays the information contained in the expanded billing recordassociated with an operator service call if an ECDR billing record has beenformatted.



• In table OFCENG, set CDR_ENABLE_LOG_ALL to "Y" to log normalcalls (this turns on treatment code 00).


• Make an operator service call on the European DMS-100 switch thatsatisfies one or more conditions given in the table below.

Call involved in a direct terminating overflow at this switch-The desiredterminating switch ID and desired terminating trunk group upon which thecall is supposed to terminate is recorded using an expanded record(ECDR/EPNR/EOSR/EPOSR).

Calling line ID is greater than 10 digits-All digits are recorded using anexpanded record (ECDR/EPNR/EOSR/EPOSR).

Destination address is greater than 17 digits-All digits are recorded usingan expanded record (ECDR/EPNR/EOSR/EPOSR)



NN10275-909v14 12.01 06 October 2011


Pretranslation digits (PTD) field is greater than 10 digits in the CDR/PNR-The PTDs are recorded using an expanded record (ECDR/EPNR/EOSR/EPOSR). OSR and POSR do not contain a PTD field. EOSR writes a PTDfield, but no call processing is defined to cause the PTD field length totrigger an EOSR or EPOSR.


A wideband call (NX64) is recorded-The originating X channels andterminating X channels are recorded using an expanded record. Theexpanded record writes a bitmap of the channels used on a T1 interface(ECDR/EPNR only)

An EVS/NARS call is recorded (NARS switch)-The EVS applicationcounter values are recorded using an expanded record (EOSR/EPOSRonly)

TCGUEST or TCROOM functionality is used-An EOSR/EPOSR call recordis required



Severity Warning

FormatCDR605 date time seqnbr INFO ECDR LONG LOG

GRID crid

CDID cdid

TP1 tp1

TP6 tp6

TP7 tp7

OP op

TP tp

OTG otg

CDR605 115


NN10275-909v14 12.01 06 October 2011


TTG ttg

TP3Q tp3q

TP6Q tpoq

AC ac

OTC otc

TTC ttc

ID id

FC fc

TNC tnc

NAT nat

TP7Q tp7q

EC ec

PD pd

NDID ndid

DIVID divid

DOF dof

CC cc

INET inet

RO ro

CD cd

DE de

DT dt

SA sa

NOCLI nocli



NN10275-909v14 12.01 06 October 2011


CN cn

ACIF acif

SS7_CAUSE ss7_cause

TP3 tp3

AIN ain

CLI cli

A a

D d

PTD ptd

MNO mno

OVFVAL ovfval

OVFCS ovfcs

OVFCL ovfcl

DTA dta

OVFC ovfc

DTAC dtac

ORIG_NX64 orig_nx64

TERM_NX64 term_nx64


VariableDescription





CDR605 117


NN10275-909v14 12.01 06 October 2011



Description




































NN10275-909v14 12.01 06 October 2011



Description









MNO 0-1 (decimal) Variable Network indicator.

OVFVAL 0-127 (decimal) Variable Overflow cause value.

OVFCS 0-3 (decimal) Variable Overflow cause coding standard.

OVFCL 0-15 (decimal) Variable Overflow cause location.

DTA 15 TBCD digits Variable Desired terminating address.

OVFC 0-127 (decimal) Variable Overflow count.

DTAC 0-63 (decimal) Variable Desired terminating action code.

ORIG_NX64 6 hexadecimal digits Variable Originating NX64 bitmap.

TERM_NX64 6 hexadecimal digits Variable Terminating NX64 bitmap.

Active message exampleCDR605 FEB23 03:17:00 8000 INFO ECDR LONG LOG

CRID 06

CDID 4002

TP1 02/23/2000/03:15:46

TP6 02/23/2000/03:16:00

TP7 02/23/2000/03:16:03

OP 0023

TP 0103

OTG 4001

TTG 2112

CDR605 119


NN10275-909v14 12.01 06 October 2011


TP3Q 03

TP6Q 00

AC 01

OTC 01

TTC 02

ID 00

FC 03

TNC 01

NAT 00

TP7Q 0

EC 020

PD 0

NDID 0

DVID 0

DOF 0

CC 1

INET 0

RO 0

CD O

DE O

DT 1

SA 0

NOCLI 06

CN 234



NN10275-909v14 12.01 06 October 2011


ACIF 15

SS7_CAUSE 000

TP3 02/23/2000/034:15:50

AIN 222

CLI 2142453646

A 123456789012345678901234567890123456789012345

D 2145551212

PTD 00

MNO 1

OVFVAL 0

OVFCS 0

OVFCL 12

DTA 010101234

OVFC 125

DTAC 13

ORIG_NX64 B2345

TERM_NX64 CA6743



CDR606This log is a short version of CDR607 log. (For detailed field descriptions,see the CDR607 log documentation.) Only one of these logs (either theshort or long version) can be generated at a time.

This log displays the information contained in the expanded billing recordassociated with a private network call if an EPNR billing record has beenformatted.

CDR606 121


NN10275-909v14 12.01 06 October 2011






• Make a private network call on the European DMS-100 switch thatsatisfies one or more conditions given in the table below.

Call involved in a direct terminating overflow at this switch-The desiredterminating switch ID and desired terminating trunk group upon which thecall is supposed to terminate is recorded using an expanded record(ECDR/EPNR/EOSR/EPOSR)

Calling line ID is greater than 10 digits-All digits are recorded using anexpanded record (ECDR/EPNR/EOSR/EPOSR)


Pretranslation digits (PTD) field is greater than 10 digits in the CDR/PNR-The PTDs are recorded using an expanded record (ECDR/EPNR/EOSR/EPOSR). OSR and POSR do not contain a PTD field. EOSR writes a PTDfield, but no call processing is defined to cause the PTD field length totrigger an EOSR or EPOSR

More than 22 auth digits (including supp codes) are used-The auth digitsare recorded using an expanded record (ECDR/EPNR/EOSR/ EPOSR)






NN10275-909v14 12.01 06 October 2011




Severity Warning

FormatCDR606 date time seqnbr INFO EPNR SHORT LOG


id fc tnc nat tp7q ec pd ndid divid dof cc inet ro cd de dtsa nocli cn

acif ss7_cause tp3 ain cli a d ptd mno ovfval ovfcs ovfcldta ovfc dtac

orig_nx64 term_nx64

Active message exampleCDR606 FEB23 03:17:00 8002 INFO EPNR SHORT LOG

07 4002 02/23/2000/03:15:46 02/23/2000/03:16:00

02/23/2000/03:16:03 0023 0103 4001 2112 03 00 01 01 02

00 03 01 00 0 020 0 0 0 0 1 0 0 0 0 1 0 06 234 15 000

02/23/2000/03:15:50 222 2142453646

123456789012345678901234567890123456789012345

2145551212 00 0 0 0 12 010101234 125 13 B2345 CA6743




CDR607 123


NN10275-909v14 12.01 06 October 2011


This log displays the information contained in the expanded billing recordassociated with a private network call if an EPNR billing record has beenformatted.





• Make a private network call on the European DMS-100 switch thatsatisfies one or more conditions given in the table below.










NN10275-909v14 12.01 06 October 2011





Severity Warning

FormatCDR607 date time seqnbr INFO EPNR LONG LOG

GRID crid

CDID cdid

TP1 tp1

TP6 tp6

TP7 tp7

OP op

TP tp

OTG otg

TTG ttg

TP3Q tp3q

TP6Q tp6q

AC ac

OTC otc

TTC ttc

ID id

FC fc

TNC tnc

CDR607 125


NN10275-909v14 12.01 06 October 2011


NAT nat

TP7Q tp7q

EC ec

PD pd

NDID ndid

DIVID divid

DOF dof

CC cc

INET inet

RO ro

CD cd

DE de

DT dt

SA sa

NOCLI nocli

CN cn

ACIF acif

SS7_CAUSE ss7_cause

TP3 tp3

AIN ain

CLI cli

A a

D d

PTD ptd



NN10275-909v14 12.01 06 October 2011


MNO mno

OVFVAL ovfval

OVFCS ovfcs

OVFCL ovfcl

DTA dta

OVFC ovfc

DTAC dtac

ORIG_NX64 orig_nx64

TERM_NX64 term_nx64


VariableDescription


















ID 2 TBCD Digits Variable info digits.

CDR607 127


NN10275-909v14 12.01 06 October 2011



Description




























MNO 0-1 (decimal) Variable Network indicator.








NN10275-909v14 12.01 06 October 2011



Description


ORIG_NX64 6 hexadecimal digits Variable Originating NX64 bitmap.

TERM_NX64 6 hexadecimal digits Variable Terminating NX64 bitmap.

Active message exampleCDR607 FEB23 03:17:00 8002 INFO EPNR LONG LOG

GRID 07

CDID 4002

TP1 02/23/2000/03:15:46

TP6 02/23/2000/03:16:00

TP7 02/23/2000/03:16:03

OP 0023

TP 0103

OTG 4001

TTG 2112

TP3Q 03

TP6Q 00

AC 01

OTC 01

TTC 02

ID 00

FC 03

TNC 01

NAT 00

TP7Q 0

CDR607 129


NN10275-909v14 12.01 06 October 2011


EC 020

PD 0

NDID 0

DVID 0

DOF 0

CC 1

INET 0

RO 0

CD 0

DE 0

DT 1

SA 0

NOCLI 06

CN 234

ACIF 15

SS7_CAUSE 000

TP3 02/23/2000/034:15:50

AIN 222

CLI 2142453646

A 123456789012345678901234567890123456789012345

D 2145551212

PTD 00

MNO 0

OVFVAL 0



NN10275-909v14 12.01 06 October 2011


OVFCS 0

OVFCL 12

DTA 010101234

OVFC 125

DTAC 13

ORIG_NX64 B2345

TERM_NX64 CA6743



CDR608This log is a short version of CDR609. (For detailed field descriptions, seethe CDR609 log documentation.) Only one of these logs (either the short orlong version) can be generated at a time.

This log displays the information contained in the expanded billing recordassociated with an operator services call if an OSR billing record has beenformatted.



• In table OFCENG, set CDR_ENABLE_LOG_ALL to "Y" to log normal(treatment O) calls; otherwise, set CDR_ENABLE_ LOG_ALL to "N."


• Make an operator services call that terminates to RLT trunk throughone of the operator tables on the European DMS-100 switch.


CDR608 131


NN10275-909v14 12.01 06 October 2011



Severity Warning

FormatCDR608 date time seqnbr INFO OSR SHORT LOG


id fc me nat tp7q ec pd ndid divid dof cc inet ro cd de dtsa nocli en

acif ss7_cause tp4 onacc tnacc opin tp5 rn pp xc cli a d

Active message exampleCDR608 AUG12 17:15:40 1111 INFO OSR SHORT LOG

04 0123 08/12/1993/17:01:40 08/12/1993/17:08:00

08/12/1993/17:10:00 0666 0999 1234 8191 01 0 00 00 03 00

00 01 03 00 000 0 0 0 0 0 0 0 0 0 0 0 01 747 00 000

08/12/1993/17:12:40 00 00 0621 08/12/1993/17:10:00 0 0

2144241212 8002341234 987654 2149071234



CDR609This log is the long version of CDR608. Only one of these logs (either theshort or long version) can be generated at a time.

This log displays the information contained in the expanded billing recordassociated with an operator services call if an OSR billing record has beenformatted.



NN10275-909v14 12.01 06 October 2011






• Make an operator services call that terminates to RLT trunk throughone of the operator tables on the European DMS-100 switch.



Severity Warning

FormatCDR609 date time seqnbr INFO OSR LONG LOG

CRID crid

CDID cdid

TP1 tp1

TP6 tp6

TP7 tp7

OP op

TP tp

OTG otg

TTG ttg

TP3Q tp3q

TP6Q tp6q

AC ac

CDR609 133


NN10275-909v14 12.01 06 October 2011


OTC otc

TTC ttc

ID id

FC fc

TNC me

NAT nat

TP7Q tp7q

EC ec

PD pd

NDID ndid

DIVID divid

DOF dof

CC cc

INET inet

RO ro

CD cd

DE de

DT dt

SA sa

NOCLI nocli

CN en

ACIF acif

SS7_CAUSE ss7_cause

TP4 tp4



NN10275-909v14 12.01 06 October 2011


ONACC onacc

TNACC tnacc

OPIN opin

TP5 tp5

RN rn

PP pp

XC xc

CLI cli

A a

D d


VariableDescription


CRDID 0-15 (decimal) Variable Call record ID.















OTC 0-15 (decimal Variable Originating trunk class.

CDR609 135


NN10275-909v14 12.01 06 October 2011



Description

TTC 0-15 (decimal Variable Terminating trunk class.

ID Two TBCD Digits Variable Info digits.























ONACC 0-15 (decimal) Variable Originating NACC.

TNACC 0-15 (decimal) Variable Terminating NACC.

OPIN 0-9999 (decimal) Variable Operator ID number.



RN 0-4 TBCD digits Variable Room number.

PP 0-1 (binary) Variable Person to person.

XC 0-1 (binary) Variable Transferred call.



NN10275-909v14 12.01 06 October 2011



Description



Active message exampleCDR609 AUG12 17:15:40 1111 INFO OSR LONG LOG

CRID 04

CDID 0123

TP1 08/12/1993/17:01:40

TP6 08/12/1993/17:08:00

TP7 08/12/1993/17:10:00

OP 0666

TP 0999

OTG 1234

TTG 8191

TP3Q 01

TP6Q 0

AC 00

OTC 00

TTC 03

ID 00

FC 00

TNC 01

NAT 03

TP7Q 00

EC 000

CDR609 137


NN10275-909v14 12.01 06 October 2011


PD 0

NDID 0

DIVID 0

DOF 0

CC 0

INET 0

RO 0

CD 0

DE 0

DT 0

SA 0

NOCLI 01

CN 747

ACIF 00

SS7_CAUSE 000

TP4 08/12/1993/17:12:40

ONACC 00

TNACC 00

OPIN 0621

TP5 08/12/1993/17:10:00

RN

PP 0

XC 0

CLI 2144241212



NN10275-909v14 12.01 06 October 2011


A 8002341234 987654

D 2149071234



CDR610This log is a short version of CDR611 log. (For detailed field descriptions,see CDR611 log documentation). Only one of these logs (the short or thelong version) can be generated at a time.

This log displays the information contained in the billing record associatedwith a private network operator call if a POSR billing record has beenformatted.



• In table OFCENG, set CDR_ENABLE_LOG_ALL to "Y" to log normal(treatment O) calls; otherwise, set CDR_ENABLE_LOG_ALL to "N."

• At the call detail recording (CDR) level (mapci;mtc;iod;cdr) of the MAPterminal, use the SETLOG command to select treatment codes forwhich this log is needed.

• Make a private network operator call on the European DMS-100 switch.



Severity Warning

FormatCDR610 date time seqnbr INFO POSR SHORT LOG


id fc me nat tp7q ec pd ndid divid dof cc inet ro cd de dtsa nocli en acif

CDR610 139


NN10275-909v14 12.01 06 October 2011


ss7_cause tp4 onacc tnacc opin tp5 rn pp xc cli a d

Active message exampleCDR610 AUG12 17:15:40 1111 INFO POSR SHORT LOG

05 0123 08/12/1993/17:01:40 08/12/1993/17:08:00

08/12/1993/17:10:00 0666 0999 1234 8191 01 0 00 00 03 00

00 01 03 00 000 0 0 0 0 0 0 0 0 0 0 0 01 747 00 000

08/12/1993/17:12:40 00 00 0621 08/12/1993/17:10:00 0 0

2144241212 8002341234 987654 2149071234



CDR611This log is the long version of CDR610 log. Only one of these logs (theshort or the long version) can be generated at a time.

This log displays the information contained in the billing record associatedwith a private network operator call if a POSR billing record has beenformatted.





• Make a private network operator call on the European DMS-100 switch.




NN10275-909v14 12.01 06 October 2011



Severity Warning

FormatCDR611 date time seqnbr INFO POSR LONG LOG

GRID crid

CDID cdid

TP1 tp1

TP6 tp6

TP7 tp7

OP op

TP tp

OTG otg

TTG ttg

TP3Q tp3q

TP6Q tp6q

AC ac

OTC otc

TTC ttc

ID id

FC fc

TNC tnc

NAT nat

TP7Q tp7q

EC ec

CDR611 141


NN10275-909v14 12.01 06 October 2011


PD pd

NDID ndid

DIVID divid

DOF dof

CC cc

INET inet

RO ro

CD cd

DE de

DT dt

SA sa

NOCLI nocli

CN en

ACIF acif

SS7_CAUSE ss7_cause

TP4 tp4

ONACC onacc

TNACC tnacc

OPIN opin

TP5 tp5

RN rn

PP pp

XC xc

CLI cli



NN10275-909v14 12.01 06 October 2011


A a

D d


VariableDescription





























CDR611 143


NN10275-909v14 12.01 06 October 2011



Description
























Active message exampleCDR611 AUG12 17:15:40 1111 INFO POSR LONG LOG

GRID 05

CDID 0123

TP1 08/12/1993/17:01:40

TP6 08/12/1993/17:08:00

TP7 08/12/1993/17:10:00



NN10275-909v14 12.01 06 October 2011


OP 0666

TP 0999

OTG 1234

TTG 8191

TP3Q 01

TP6Q 0

AC 00

OTC 00

TTC 03

ID 00

FC 00

TNC 01

NAT 03

TP7Q 00

EC 000

PD 0

NDID 0

DIVID 0

DOF 0

CC 0

INET 0

RO 0

CD 0

DE 0

CDR611 145


NN10275-909v14 12.01 06 October 2011


DT 0

SA 0

NOCLI 01

CN 747

ACIF 00

SS7_CAUSE 000

TP4 08/12/1993/17:12:40

ONACC 00

TNACC 00

OPIN 0621

TP5 08/12/1993/17:10:00

RN

PP 0

XC 0

CLI 2144241212

A 8002341234 987654

D 2149071234




This log displays the information contained in the expanded billing recordassociated with an operator services call if a POSR billing record has beenformatted.



NN10275-909v14 12.01 06 October 2011



• In table OFCVAR, set CDR_LOG_FIELD_DESCRIPTORS to "N" forthe short version of the log report.

• In table OFCENG, set CDR_ENABLE_LOG_ALL to "Y" to log normal(treatment 0) calls; otherwise, set CDR_ENABLE_LOG_ALL to "N."

• At the call detail recording (CDRO level (mapci;mtc;iod;cdr) of the MAPterminal, use the SETLOG command to select treatment codes forwhich this log is needed.

• Make an operator services call on the European DMS-100 switch thatsatisfies one or more conditions given in the table below.







An EVS/NARS call is recorded (NARS Switch)-The EVS applicationcounter values are recorded using an expanded record (EOSR/EPOSRonly)


CDR612 147


NN10275-909v14 12.01 06 October 2011




Severity Warning

FormatCDR612 date time seqnbr INFO EOSR SHORT LOG


id fc tnc nat tp7q cc pd ndid divid dof cc inet ro cd de dtsa nocli cn

acif ss7_cause tp4 onacc tnacc opin tp5 rn pp xc cli a d ptdmno ovfval

ovfcs ovfcl dta ovfc dtac tcroom tcguest eac

Active message exampleCDR612 AUG12 17:15:40 1111 INFO EOSR SHORT LOG

08 0123 08/12/1993/17:01:40 08/12/1993/17:08:00

08/12/1993/17:10:00 0666 0999 1234 8191 01 0 00 00 03 00

00 01 03 00 000 0 0 0 0 0 0 0 0 0 0 0 01 747 00 000

08/12/1993/17:12:40 00 00 0621 08/12/1993/17:10:00 0 0

2144241212 8002341234 987654 2149071234 5678 0 0 0 12

010101234 125 13 1123HA ABCD 1234AB000000






NN10275-909v14 12.01 06 October 2011


This log displays the information contained in the expanded billing recordassociated with an operator services call if a POSR billing record has beenformatted.





• Make an operator services call on the European DMS-100 switch thatsatisfies one or more conditions given in the table below.








CDR613 149


NN10275-909v14 12.01 06 October 2011





Severity Warning

FormatCDR613 date time seqnbr INFO EOSR LONG LOG

CRID crid

CDID cdid

TP1 tp1

TP6 tp6

TP7 tp7

OP op

TP tp

OTG otg

TTG ttg

TP3Q tp3q

TP6Q tp6q

AC ac

OTC otc

TTC ttc

ID id

FC fc

TNC tnc



NN10275-909v14 12.01 06 October 2011


NAT nat

TP7Q tp7q

EC ec

PD pd

NDID ndid

DIVID divid

DOF dof

CC cc

INET inct

RO ro

CD cd

DE de

DT dt

SA sa

NOCLI nocli

CN cn

ACIF acif

SS7_CAUSE ss7_cause

TP4 tp4

ONACC onacc

TNACC tnacc

OPIN opin

TP5 tp5

RN rn

CDR613 151


NN10275-909v14 12.01 06 October 2011


PP pp

XC xc

CLI cli

A a

D d

PTD ptd

MNO mno

OVFVAL ovfval

OVFCS ovfcs

OVFCL ovfcl

DTA dta

OVFC ovfc

DTAC dtac

TCROOM tcroom

TCGUEST tcguest

EAC eac


VariableDescription











NN10275-909v14 12.01 06 October 2011



Description


































CDR613 153


NN10275-909v14 12.01 06 October 2011



Description






Variable RN and TCRoom are mutuallyexclusive fields.






PTD 0-15 TBCD digits Variable Pretranslation digits.

MNO 0-1 (decimal) Variable MCI network indicator.







TCROOM 0-6 characters Variable Time and charge room number.

Variable TCRoom and RN are mutuallyexclusive fields.

TCGUEST 0-4 characters Variable Time and charge guest name.

EAC 0-FFFFFFFFFFFF(hexadecimal)

Variable EVS application counter.

Active message exampleCDR613 AUG12 17:15:40 1111 INFO EOSR LONG LOG

CRID 08

CDID 0123

TP1 08/12/1993/17:01:40

TP6 08/12/1993/17:08:00



NN10275-909v14 12.01 06 October 2011


TP7 08/12/1993/17:10:00

OP 0666

TP 0999

OTG 1234

TTG 8191

TP3Q 01

TP6Q 0

AC 00

OTC 00

TTC 03

ID 00

FC 00

TNC 01

NAT 03

TP7Q 00

EC 000

PD 0

NDID 0

DIVID 0

DOF 0

CC 0

INET 0

RO 0

CD 0

CDR613 155


NN10275-909v14 12.01 06 October 2011


DE 0

DT 0

SA 0

NOCLI 01

CN 747

ACIF 00

SS7_CAUSE 000

TP4 08/12/1993/17:12:40

ONACC 00

TNACC 00

OPIN 0621

TP5 08/12/1993/17:10:00

RN

PP 0

XC 0

CLI 2144241212

A 8002341234 987654

D 2149071234

PTD 5678

MNO 0

OVFVAL 0

OVFCS 0

OVFCL 12

DTA 010101234



NN10275-909v14 12.01 06 October 2011


OVFC 125

DTAC 13

TCROOM 1123HA

TCGUEST ABCD

EAC 1234AB000000



CDR614This log is a short version of CDR615 log. (For detailed field descriptions,see the CDR615 log documentation.) Only one of these logs (either theshort or long version) can be generated at a time.

This log displays the information contained in the expanded billing recordassociated with a private network operator call if an EPOSR billing recordhas been formatted.


• In table OFCVAR, set CDR_LOG_FIELD_DESCRIPTORS to "N" forthe short format log report.



• Make a private network operator call on the European DMS-100 switchthat satisfies one or more conditions given in the table below.



CDR614 157


NN10275-909v14 12.01 06 October 2011




More than 22 auth digits (including supp codes) are used-The auth digitsare recorded using an expanded record (ECDR/EPNR/EOSR/EPOSR)

A wideband call (NX64) is recorded-The wriginating X channels andterminating X channels are recorded using an expanded record. Theexpanded record writes a bitmap of the channels used on a T1 interface(ECDR/EPNR only)

An EVS/NARS call is recorded (NARS Switch)-The EVS applicationcounter values are recorded using an expanded record (EOSR/EPOSRonly).




Severity Warning

FormatCDR614 date time seqnbr INFO EPOSR SHORT LOG


id fc tnc nat tp7q ec pd ndid divid dof cc inet ro cd de dtsa nocli cn

acif ss7_cause tp4 onacc tnacc opin tp5 rn pp xc cli a d ptdmno ovfval

ovfcs ovfcl dta ovfc dtac tcroom tcguest eac



NN10275-909v14 12.01 06 October 2011


Active message exampleCDR614 AUG12 17:15:40 1111 INFO EPOSR SHORT LOG

09 0123 08/12/1993/17:01:40 08/12/1993/17:08:00

08/12/1993/17:10:00 0666 0999 1234 8191 01 0 00 00 03 00

00 01 03 00 000 0 0 0 0 0 0 0 0 0 0 0 01 747 00 000

08/12/1993/17:12:40 00 00 0621 08/12/1993/17:10:00 0 0

2144241212 8002341234 987654 2149071234987654321012345

5678 0 0 0 12 010101234 125 13 1123HA ABCD 1234AB000000




This log displays the information contained in the expanded billing recordassociated with a private network operator call if an EPOSR billing recordhas been formatted.




• At the call detail recording (CDRO level (mapci;mtc;iod;cdr) of the MAPterminal, use the SETLOG command to select treatment codes forwhich this log is needed.

• Make a private network operator call on the European DMS-100 switchthat satisfies one or more conditions given in the table below.


CDR615 159


NN10275-909v14 12.01 06 October 2011






A wideband call (NX64) is recorded-The wriginating X channels andterminating X channels are recorded using an expanded record. Theexpanded record writes a bitmap of the channels used on a T1 interface(ECDR/EPNR only)





Severity Warning

FormatCDR615 date time seqnbr INFO EPOSR LONG LOG

CRID crid

CDID cdid

TP1 tp1

TP6 tp6



NN10275-909v14 12.01 06 October 2011


TP7 tp7

OP op

TP tp

OTG otg

TTG ttg

TP3Q tp3q

TP6Q tpoq

AC ac

OTC otc

TTC ttc

ID id

FC fc

TNC tnc

NAT nat

TP7Q tp7q

EC cc

PD pd

NDID ndid

DIVID divid

DOF dof

CC cc

INET inct

RO ro

CD cd

CDR615 161


NN10275-909v14 12.01 06 October 2011


DE de

DT dt

SA sa

NOCLI nocli

CN cn

ACIF acif

SS7_CAUSE ss7_cause

TP4 tp4

ONACC onacc

TNACC tnacc

OPIN opin

TP5 tp5

RN rn

PP pp

XC xc

CLI cli

A a

D d

PTD ptd

MNO mno

OVFVAL ovfval

OVFCS ovfcs

OVFCL ovfcl

DTA dta



NN10275-909v14 12.01 06 October 2011


OVFC ovfc

DTAC dtac

TCROOM tcroom

TCGUEST tcguest

EAC eac


VariableDescription

























CDR615 163


NN10275-909v14 12.01 06 October 2011



Description



















Variable RN and TCRoom are mutuallyexclusive fields.







MNO 0-1 (decimal) Variable MCI network indicator.









NN10275-909v14 12.01 06 October 2011



Description

TCROOM 0-6 characters Variable Time and charge room number.

Variable TCRoom and RN are mutuallyexclusive fields.

TCGUEST 0-4 characters Variable Time and charge guest name.

EAC 0-FFFFFFFFFFFF(hexadecimal)

Variable EVS application counter.





Active message exampleCDR615 AUG12 17:15:40 1111 INFO EPOSR LONG LOG

CRID 09

CDID 0123

TP1 08/12/1993/17:01:40

TP6 08/12/1993/17:08:00

TP7 08/12/1993/17:10:00

OP 0666

TP 0999

OTG 1234

TTG 8191

TP3Q 01

TP6Q 0

AC 00

OTC 00

TTC 03

CDR615 165


NN10275-909v14 12.01 06 October 2011


ID 00

FC 00

TNC 01

NAT 03

TP7Q 00

EC 000

PD 0

NDID 0

DIVID 0

DOF 0

CC 0

INET 0

RO 0

CD 0

DE 0

DT 0

SA 0

NOCLI 01

CN 747

ACIF 00

SS7_CAUSE 000

TP4 08/12/1993/17:12:40

ONACC 00

TNACC 00



NN10275-909v14 12.01 06 October 2011


OPIN 0621

TP5 08/12/1993/17:10:00

RN

PP 0

XC 0

CLI 2144241212

A 8002341234 987654

D 2149071234

PTD 5678

MNO 0

OVFVAL 0

OVFCS 0

OVFCL 12

DTA 010101234

OVFC 125

DTAC 13

TCROOM 1123HA

TCGUEST ABCD

EAC 1234AB000000


CDR615 167


NN10275-909v14 12.01 06 October 2011



CEPT100Log report CEPT100 (''CEPTPW is locked remotely'') is generated only ifthe CEPTPW (CEPT password) feature has become locked due torepeated incorrect password entry using the CEPTRA (CEPT remoteaccess) feature.

Log history

ISN07 (TDM)

Log report CEPT100 introduced by feature A00001919, CEPT servicespassword enhancement.

Remedial actionNo immediate action is taken.


Severity Warning

FormatCEPT100 mmmdd hh:mm:ss ssdd INFO CEPTPW IS LOCKED REMOTELY

BASE DN: <base_dn>

ORIGINATING DN: <orig_dn>

ORIGINATING TRUNK: <orig_cpid>


VariableDescription

INFO CEPTPW ISLOCKED REMOTELY

Constant Fixed Indicates a report of CEPT information

BASE DN Digits (18 digits) Variable Identifies the serving numbering planarea (SNPA) and directory number(DN) of the base agent.

ORIGINATING DN Digits (18 digits) Variable Identifies the SNPA and DN of the calloriginator

ORIGINATINGTRUNK

CPID Variable Identifies the originator trunk(incoming trunk)



NN10275-909v14 12.01 06 October 2011


Active message exampleCEPT100 APR28 09:33:57 2909 INFO CEPTPW IS LOCKED REMOTELY

BASE DN: 1027835411

ORIGINATING DN: 1027835475

ORIGINATING TRUNK: CKT ICISP2BA 0

CEPT100 APR28 09:33:57 2909 INFO CEPTPW IS LOCKED REMOTELY

BASEDN: 1027835411

ORIGINATING DN:


CEPT100 APR28 09:33:57 2909 INFO CEPTPW IS LOCKED REMOTELY

BASEDN: 1027835411


ORIGINATING TRUNK:



CEPT101Log report CEPT101 log (''CEPTRA usage attempt'') is generated when asubscriber attempts to use supported CEPT features (ILR, IWUC,CEPTPW, CFD, CFU and CFB) from remote agents via CEPTRA.

Log history

ISN07 (TDM)

Log report CEPT101 introduced by feature A00001919, CEPT servicespassword enhancement.

Remedial actionNo immediate action is taken.

CEPT101 169


NN10275-909v14 12.01 06 October 2011



Severity Warning

FormatCEPT101 mmmdd hh:mm:ss ssdd INFO CEPTRA USAGE ATTEMPT

BASE DN: <base_dn>

ORIGINATING DN: <orig_dn>

ORIGINATING TRUNK: <orig_cpid>

FEATURE: <requsted_ftr>

ACTION: <ftr_action>


VariableDescription

CEPTRA USAGEATTEMPT

Constant Fixed Indicates a report of CEPT information

BASE DN Digits (18 digits) Variable Identifies the serving numbering planarea (SNPA) and directory number(DN) of the base agent.

ORIGINATING DN Digits (18 digits) Variable Identifies the SNPA and DN of the calloriginator

ORIGINATINGTRUNK

CPID Variable Identifies the originator trunk(incoming trunk)

FEATURE line_option Variable Identifies the which CEPT feature isrequested.

ACTION xla_ftr_function (ACT,DEACT, INTER,USAGE, PROG,DELETE

Variable Indicates the subscriber action onrequested CEPT feature.

Active message exampleCEPT101 APR28 09:33:57 2909 INFO CEPTRA USAGE ATTEMPT

BASE DN: 1027835411





NN10275-909v14 12.01 06 October 2011


FEATURE: ILR

ACTION: INTER



• The CPTRAATT register in CEPTRA OM group CEPTRA is pegged,andif the subscriber''s attempt to program one of supported CEPTfeatures is unsuccessful, the CPTRAFAL register is pegged; if thesubscriber''s attempt to program one of supported CEPT features issuccessful, the CPTRASUC register is pegged; the OM register of therequested CEPT feature is pegged, according to success of result

• These OMs are pegged in other cases, not for this scenario only.

CFW107The Call Forwarding (CFW) subsystem generates log report CFW107. Thisreport appears when the journal file is inactive when the system activatesor deactivates Usage Sensitive Call Forwarding (UCFW) feature. and . Thesystem only generates a log report if the system activates or deactivates(UCFW) when the journal file is not active.

The system activates or deactivates this feature on a line that does notcontain the following:

• Call Forward Don''t Answer (CFDA)

• Call Forward Busy Line (CFBL)

• other CFW types. The Selective Call Forwarding feature is notincluded.

This log report reminds the operating company to enable the journal file.This report displays the fields in the CFX tuple in table CFX to track theUsage Sensitive Pricing (USP) status.

Remedial actionn/a


Severity Warning

CFW107 171


NN10275-909v14 12.01 06 October 2011


FormatPROTECTED cfxusp_add_del_fail_log_format DESC OF CHAR IS%%

________________________________

{''&/CALL FORWARDING - USP WAS &!"<CFXUSP_ACTION>"'', ''

WHEN JOURNAL FILE WAS INACTIVE.'', ''&/CFX TABLE

CONTENTS WERE &!"<CFXU_TUPLE_ACTION>"'', ''&/CFX_LEN:

&!"<CFX_KEY_AREA>''"};


VariableDescription

CFXU_TUPLE_ACTION

ADDED, CHANGED,or DELETED

Variable Indicates the system adds, changes,or deletes a CFX tuple from theUCFW update.

CFX_KEY_AREA len + key number Variable Displays the LEN of the line where thesystem adds or deletes UCFW.

CFUIF_DISPLAY_AREA

CFUIF forwarding info Variable Displays current CFUIF line data

CFUI_STATE Active, Inactive, orWait

Variable Displays current CFUIF line data.

THIRTY_DIGIT_REGISTER

DN from 7 to 30 digits Variable Displays current CFBD and CFDAforward DNs.

CFXUSP_ACTION ADDED, or DELETED Variable Indicates that system adds or deletesUCFW from the subscriber line.

Active message exampleMTLEN06AW CFW107 MAR28 13:42:37 9300 INFO JOURNAL FILE

CALL FORWARDING - USP WAS DELETED

WHEN JOURNAL FILE WAS INACTIVE

CFX TABLE CONTENTS WHERE CHANGED

CFX_LEN: HOST 00 00 01 07 7

CFUIF_VAR_AREA: Y N A 6216803

CFBSTATE: A CFBDN: 6216501



NN10275-909v14 12.01 06 October 2011


CFDSTATE: A CFDDN: 6216502

CFBSTAT2: A CFBDN2: 6216503

CFDSTAT2: A CFDDN2: 6216504



CFW109The call forwarding (CFW) subsystem generates log CFW109 if the journalfile is inactive when a subscriber deactivates the Call Forward to Operator(CFO) feature. A journal file describes changes to table datafill. The usercan use log CFW109 to check whether any IBNFEAT table datafill ismissing and to determine that the table must be manually updated.

Remedial actionThe reason that the journal file is inactive shall be investigated.


Severity Warning

FormatCFW109 mmmdd hh:mm:ss ssdd INFO NO JOURNAL FILE

JOURNAL FILE NOT ACTIVE DURING CFO DEACTIVATION

NEW IBNFEAT TUPLE IS:

<ibnfeat_tuple>


VariableDescription

INFO NO JOURNALFILE

Constant text string Variable This field indicates that the journal fileis not active.

JOURNAL FILE NOTACTIVE DURINGCFO DEACTIVATION

Constant text string Variable This field indicates that the CFOfeature is not active.

CFW109 173


NN10275-909v14 12.01 06 October 2011



Description

NEW IBNFEATTUPLE IS:

Constant text string Variable This field indicates that tableIBNFEAT needs to be updated.

ibnfeat_tuple Alphanumeric string Variable This field identifies the missingIBNFEAT table datafill.

Active message exampleCFW109 FEB17 13:00:00 9216 INFO NO JOURNAL FILE

JOURNAL FILE NOT ACTIVE DURING CFO DEACTIVATION


HOST 03 0 00 04 0 CFO 01 I



CFW110The call forwarding (CFW) subsystem generates log CFW110 if the journalfile is inactive when a subscriber activates the Call Forward toAnnouncement (CFTANN) feature. A journal file describes changes totable datafill. The user can use log CFW110 to check whether anyIBNFEAT table datafill is missing and to determine that the table must bemanually updated.



Severity Warning


JOURNAL FILE NOT ACTIVE DURING CFTANN ACTIVATION


<ibnfeat_tuple>



NN10275-909v14 12.01 06 October 2011



VariableDescription

INFO NO JOURNALFILE


JOURNAL FILE NOTACTIVE DURINGCFTANNACTIVATION

Constant text string Variable This field indicates that the CFTANNfeature is active.





JOURNAL FILE NOT ACTIVE DURING CFTANN ACTIVATION


HOST 03 0 00 04 0 CFTANN A 35



CFW111The call forwarding (CFW) subsystem generates log CFW111 if the journalfile is inactive when a subscriber deactivates the Call Forward toAnnouncement (CFTANN) feature. A journal file describes changes totable datafill. The user can use log CFW111 to check whether anyIBNFEAT table datafill is missing and to determine that the table must bemanually updated.



Severity Warning

CFW111 175


NN10275-909v14 12.01 06 October 2011



JOURNAL FILE NOT ACTIVE DURING CFTANN

DEACTIVATION NEW IBNFEAT TUPLE IS:

<ibnfeat_tuple>


VariableDescription

INFO NO JOURNALFILE


JOURNAL FILE NOTACTIVE DURINGCFTANNDEACTIVATION

Constant text string Variable This field indicates that the CFTANNfeature is not active.





JOURNAL FILE NOT ACTIVE DURING CFTANN DEACTIVATION


HOST 03 0 00 04 0 CFTANN I $



CLBK600The notification of time and charge (NTC) service delivers an automaticnotification of time and charge announcement from a DMS-100 switch afterthe call requesting this service is answered and released.

Log CLBK600 is generated when the NTC service is requested but thesystem''s attempts to call back the subscriber have failed.



NN10275-909v14 12.01 06 October 2011


Remedial actionn/a This log is provided for information purposes only. Operating companyprocedures may require action when this log is generated.


Severity Warning

FormatCLBK600 mmmdd hh:mm:ss ssdd INFO NTC Callback Failure

Number to callback = <number to callback>

Number to announce = <number to announce>

Adj. Duration(sec) = <adjustment time>

Orig Charge Amount = <call cost>

Retry for Far_End = <far_end_retries>

Retry for Local = <local_retries>

Failure Reason = <reason>


VariableDescription

number to callback numeric(1 to 15 digits) Variable Telephone number of the subscriberto be called back.

number to announce numeric(1 to 15 digits) Variable The dialed telephone number.

adjustment time numeric(0 to 99) Variable The adjustment made to themeasured call duration.

call cost numeric Variable The amount the subscriber will becharged including any tax, butexcluding the charge for NTCconnection.

CLBK600 177


NN10275-909v14 12.01 06 October 2011



Description

far_end_retries numeric(0 to 9) Variable The number of retry attempts madebecause of either of the followingcircumstances:

• The subscriber does not answerthe telephone.

• A technical problem caused thecall back attempt to fail at somepoint in the calls connection, butnot at the DMS switch local to thesubscriber initiating the call.

local_retries numeric(0 to 9) Variable The number of retry attempts madebecause of either of the followingcircumstances:

• The subscriber does not answerthe telephone.

• A technical problem caused thecall back attempt to fail at theDMS switch local to the subscriberinitiating the call.

reason alphanumericcharacter string

Variable The reason the last retry attemptfailed.

Adjusted duration<= 0 Variable The adjusted call duration is less thanzero seconds.

Callback outgoing trknot available

Variable No outgoing trunk member is idle forcallback. Callback may be re-attempted, if necessary.

Cannot collect digits Variable During NTC announcement playing,digit collection was stopped by auniversal tone receiver (UTR).

Cannot continue digitcollection

Variable Computing module (CM) could notcontinue the UTR digit collectionduring the NTC announcementplayback.

Cannot do SMDRbilling

Variable The station message detailedrecording (SMDR) billing recordcannot be generated for an NTCcallback call. No NTC callback occurs.

Cannot play over thesame channel

Variable Indicates a problem with starting thenext language over the same channelas the previous language.



NN10275-909v14 12.01 06 October 2011



Description

Cannot repeatannouncement

Variable Indicates a problem with repeating thecurrent playing language.

Cannot startannouncement utility

Variable Could not start the NTCannouncement. Check NTCannouncement/EDRAM datafill.

Cannot start digitcollection

Variable CM could not start UTR digit collectionfor the first time. Normally, digitcollection is started immediately afterthe NTC announcement is started.

Charge>9 999 999 Variable The charge amount for original NTCcall is greater than 9 999 999. No NTCcallback occurs.

Charge not available,check log INTL

Variable Charge amount cannot be calculated.Check the INTL log.

Edram Channel notavailable

Variable No EDRAM channel is available forthe NTC announcement. Callbackmay be re-attempted, if necessary.

EDRAM Trunkreleased during annplaying

Variable The reserving EDRAM channel, notthe playing one, is force-released orthe reserving EDRAM itself is manualbusied during an announcementplaying.

Excess calling digitsfor NTC callback

Variable Calling party number of the originalNTC call has too many digits.

Excess calling dn&adjduration<= 0

Variable Calling party number of the originalNTC call has too many digits, and theadjusted call duration is less than zeroseconds.

Excess callingdn&orig call is free

Variable Calling party number of the originalNTC call has too many digits, and theoriginal NTC call is a free call.

External audio servertrouble during ann

Variable Audio server can not play theannouncement normally. The server isnot idle or the provisioning hasproblem.

Info missing&adjustedduration<= 0

Variable Some information for callback ismissing, and the adjusted call durationis less than zero seconds.

Info missing&orig callis free

Variable Some information for callback ismissing, and the original NTC call is afree call.

CLBK600 179


NN10275-909v14 12.01 06 October 2011



Description

Info missing as shownabove

Variable Some information for callback ismissing as shown in this CLBK600 logreport.

Info missing, thuscharge no available

Variable Some information for callback ismissing, therefore, the charge amountcannot be calculated.

NTC callbacktranslation failed

Variable Callback translation failed. Checktranslation datafill.

NTC Flat Fee>65 535 Variable The flat charge for NTC service is outof bound. No NTC callback occurs.

No answer, ringbacktime out

Variable The called party did not answer thecallback. Callback may be re-attempted, if necessary.

No digits to outpulseafter prefix fence

Variable During callback translation, the prefixfence was moved after the last digit.Therefore, there is nothing to send.

No NTC languagedatafilled

Variable There is no datafill for NTC languagesin any of the following tables:

• AREANAME

• DNSCRN

• NTCLANGS

No NTC callback occurs.

No softwareresources

Variable Cannot get enough internal resourcesto initiate NTC callback.

No softwareresources to startcallback

Variable Unable to allocate internal resources(NTC FDB) for NTC callback. Checkthe datafill in table OFCENG for officeparameterNO_OF_LARGE_FTR_DATA_BLKS.

No timer for re-attempt, check datafill

Variable Could not start the large storage timerutility for NTC callback re-attempts.Check the datafill in table OFCENGfor office parameterLARGE_STORAGE_TIMER_NUM.

Not NCCI origination Variable The incoming trunk of the originalNTC call is not using NCCI protocol.

OfcparmNTC_XLATIONScontains NIL

Variable Office parameter NTC_XLATIONS intable OFCVAR is not datafilled.



NN10275-909v14 12.01 06 October 2011



Description

Option NETWORKnot in tableCUSTSMDR

Variable The NETWORK option is not datafilledfor the customer group in tableCUSTSMDR at the setup stage of theoriginal NTC call. Therefore, no #DArecord is generated, and no NTCcallback occurs.

Orig Charge Amount= 0

Variable Charge amount for original NTC call is0. No NTC callback occurs.

Orig duration>999999 sec

Variable Indicates the original call duration islonger than 999 999 seconds butSMDR billing record can only displayup to 999 999 seconds. No NTCcallback occurs.

The original NTC callis a free call

Variable The original NTC call is a free call.

Other features on thiscall denied NTC

Variable Indicates a problem of featureinteractions on an NTC callback call. Ifanother feature, which is active onNTC callback call, chooses to denythe NTC feature, this log reason isdisplayed.

A possible route is notNCCI

Variable Indicates a datafill problem. Theselected route is not using NCCIprotocol.

A possible route is nottrunk

Variable Indicates a datafill problem. A non-trunk agent is datafilled for callback.The non-trunk agent is not supportedfor NTC callback.

Routing failed, checkdatafill

Variable Indicates a datafill problem. Nooutgoing route is available forcallback.

Subscriber may bebusy

Variable The called party may be busy.Callback may be re-attempted, ifnecessary.

Trunk released duringann playing

Variable NTC callback outgoing trunk is locallyor remotely force-released duringannouncement playing.

WARNING: msg fromDTM

Variable This is only a warning message, theNTC announcement continues. Duringthe NTC announcement, it is possiblethat more than one EDRAM isselected for playing multilingualannouncements. If so, only one

CLBK600 181


NN10275-909v14 12.01 06 October 2011



Description

EDRAM is being used at any givenmoment; all the others are reserved. Ifthe reserving EDRAM sends amessage, this log reason is displayedfor information purposes only. Thegeneration of this log report has noimpact to the end caller. The NTCannouncement continues.

XXXXXX missing Variable Indicate datafill of the phrase XXXXXXis missing in table ANNAUDID.

Active message exampleCLBK600 DEc01 19:26:05 0200 INFO NTC Callback Failure

Number to Callback = 3119231210

Number to announce = 006416137639687

Adj. Duration(sec) = 99

Orig Charge Amount = 9999999

Retry for Far_End = 3

Retry for Local = 2

Failure Reason = EDRAM not available



CLBK610Log CLBK610 is generated when a system failure occurs during thenotification of time and charge (NTC) callback announcement. The logdisplays the information needed to perform a preliminary investigation ofthe failure.

The types of system failures that trigger log CLBK610 are

• The system cannot start the announcement.

• The system cannot repeat the announcement.

• The system cannot perform digit collection during the announcement.



NN10275-909v14 12.01 06 October 2011


• The system receives a treatment-completed message from the EDRAMduring the announcement.

• The system receives an internal digit collection error message from aport other than the terminating port.

• The system receives an internal digit collection error message from theterminating port.

• The system receives a release message from a source other than theterminating port or EDRAM.

• The system receives a message from a reserved EDRAM.

Remedial actionRecord the log and contact the next level of support.


Severity Warning

FormatCLBK610 mmmdd hh:mm:ss ssdd INFO NTC Callback System Failure

Call ID = <call_id_in_hex>

Outgoing Trunk = <CLLI_&_number>

Announcement Being Played = <announcement#>

Announcement Playing Trunk = <CLLI_&_number>

Announcement Cycles Left to be played = <number_of_cycles>

EDRAM Trunk 1 = <CLLI_and_number>



Current message = <current_message_in_hex_format>

Call Event 1 = <event #, hh:mm:ss sss>



CLBK610 183


NN10275-909v14 12.01 06 October 2011










VariableDescription

Call ID 8-digit hexadecimal Variable Specifies the call identifier.

Outgoing Trunk symbolic text and anumber (1 to 2047)

Variable Specifies the outgoing trunk agent'scommon language location identifier(CLLI) and member number.

Announcement BeingPlayed

0 to 99 Variable Specifies the announcement numberthat was playing at the time of thesystem failure.

AnnouncementPlaying Trunk

symbolic text and anumber (1 to 2047)

Variable Specifies the EDRAM trunk's CLLIand member number of theannouncement being played.

AnnouncementCycles Left To BePlayed

0 to 3 Variable Specifies the announcement cyclesleft to be played at the time of thesystem failure.

EDRAM Trunk 1, 2,and 3

symbolic text and anumber (1 to 2047)

Variable Specifies the EDRAM trunk's CLLIand member number that is reservedfor the announcement.

Current Message 50-digit alphanumericcharacter string

Variable Specifies the message that was beingprocessed before the system failure.

Call Event 1 through10

alphanumericcharacter string andtime (hh:mm:ss sss)

Variable Specifies the call history text and thetime stamp of when that event tookplace.

Active message exampleCLBK610 JAN02 03:51:09 9400 INFO NTC Callback System Failure

Call ID = 4F1C 0000

Outgoing trunk = NCCIV2LPA 1



NN10275-909v14 12.01 06 October 2011


Announcement Being Played = 1

Announcement Playing Trunk = NTCENG 1

Announcement Cycles Left To Be Played = 1

EDRAM Trunk 1 = NTCENG 1

EDRAM Trunk 2 = NTCJPN 1

EDRAM Trunk 3 = NTCTHAI 1

Current Message = 0101 0000 000B 0000 0000 0000

0000 0000 0000 0000 00FF BF84

4BFF BD00 1001 6E95 FD4B FDFD

FDFD FDFD FDFD FDFD FDFD FDFD

FDFD

Call Event 1 = Any of 0 to 9 keys pressed 03:50:52.646




Call Event 5 = # key pressed -- Skipping 03:50:55.806


Call Event 7 = # key pressed -- Skipping 03:50:58.806



Call Event 10 = REL msg from unknown source 03:51:09.007


CLBK610 185


NN10275-909v14 12.01 06 October 2011



CLBK700The push button international subscriber dialled (PB-ISD) feature allowssubscribers to have access to services previously only available whencalling line identification (CLI) was automatically provided. A subscriberwho is connected to a switch not automatically providing CLI, enters thisinformation on a touch-tone telephone.

The following steps enable access to services requiring a CLI:

• The subscriber dials 0064.

• The subscriber hears a dial tone.

• The subscriber enters 620.

• The subscriber enters their CLI digits (telephone number).

• The subscriber is prompted to hang up the handset.

• The CLI entered is verified.

• The subscriber is called back and one of the following occurs:

• A treatment tells the subscriber that they do not have access to theservice and the reason access is denied.

• The user is prompted as required by the service.

The number of attempts made by the switch to call back the subscriber isset in office parameter CALL_BACK_RETRY_ATTEMPTS. This logprovides the reason the last back call attempt failed.

The following are entries in the reasons field and associated additionalinformation field, with details on what these entries mean:

• TRANSLATIONS FAILURE--The translation could not be made usinguniversal translations. If the starting translations tuple specified byoffice parameter CALL_BACK_CLI_XLATIONS cannot be found, theadditional information field contains the messageCALL_BACK_CLI_XLATIONS OFFICE FARM INVALID

• TREATMENT ENCOUNTERED--The call back attempt was routed tothe treatment specified in the additional information field. Retries areattempted only if the treatment applied is GNCT.

• UNANSWERED--The callback attempt was unanswered. Repeatedoccurrences of this type of log may indicate abuse of the PB-Callsfeature.

• BUSY--The callback attempt failed because the subscriber''s line wasbusy.



NN10275-909v14 12.01 06 October 2011


• TEMPORARY FAILURE--The additional information field indicates thetype of temporary failure:

• RECEIVED REL WITH CAUSE VALUE = nn--The far end returned arelease message (REL). The cause value indicates why the REL wasreturned. The following are possible cause values (nn) and theirmeanings:

• 31 normal unspecified

• 34 circuit congestion

• 41 temporary failure

• 42 switching equipment congestion

• NO OUTGOING TRUNK AVAILABLE--There are no outgoing trunksavailable for this call.

• INVALID OR NO RESPONSE--There is a problem with the responsereceived from the far end. The following are possible problems and aredisplayed in the additional information field:

• TIMEOUT WAITING FOR ACM--No response was received from thefar end.

• INVALID RESPONSE--No retries are attempted. An invalid responsewas received from the far end for one of the following reasons:

• a communication fault between the CM and the trunk peripheral

• the trunk peripheral has reported a problem

• an unknown problem

• SOFTWARE RESOURCE UNAVAILABLE--No retries are attempted. Acritical software resource was unavailable.

Remedial actionIf the entry in the failure reason field is TRANSLATIONS FAILURE, thedata in table OFCVAR office parameter CALL_BACK_CLI_XLATIONSshould be corrected.

CLBK700 187


NN10275-909v14 12.01 06 October 2011


All other failure reasons require no immediate action. Non-urgent actionmay be required by repeated occurrences of this log with the followingaction field entries:

• UNANSWERED--This may indicate abuse of the PB-Calls feature. Thesubscriber identified in the subscriber_cli field should be contactedwhen the number of log reports generated by the same subscriberexceeds a threshold determined by the operating company.

• TEMPORARY FAILURE--This may indicate a capacity problem withthe current switch configuration. Contact your next level of supportwhen the number of log reports generated exceeds a thresholddetermined by the operating company.

The values set in the following office parameters affect the number andtype of CLBK700 log generated. If the entries in these office parametersare incorrectly set, a large number of logs will be generated:

• CALL_BACK_ANSWER_TIME

• CALL_BACK_RETRY_WAIT_TIME

• CALL_BACK_RETRY_ATTEMPTS



• Critical

FormatCLBK700 mmmyy hh:mm:ss xxxx INFO FAILED CALL BACK CALL BACK

CLI: <subscriber_cli> RETRY COUNT: <#_failed>

FAILURE REASON: <failure_reason>

<additional information>



NN10275-909v14 12.01 06 October 2011



VariableDescription

subscriber_cli numeric Variable Telephone number of the subscriberinitiating the call (calling line identifier).

#_failed numeric (1 to 9) Variable The number of retry attempts madebefore the call was failed. A value of 1indicates 2 attempts; the original failedattempt and 1 retry attempt.

failure_reason alphanumeric Variable The reason the last retry attemptfailed. The Additional informationsection of this log report lists thepossible failure reasons and theirmeaning.

additional information alphanumeric Variable This field may be left bank or containsadditional information on the failurereason. The Additional informationsection of this log report lists thepossible entries in this field.

Active message exampleCLBK700 MAY93 12:25:20 1300 INFO FAILED CALL BACK

CALL BACK CLI: 6135551212 RETRY COUNT: 4

FAILURE REASON: TEMPORARY FAILURE

RECEIVED REL WITH CAUSE VALUE = 31



CLIS100The CLIS100 log is generated when calling line identification (CLI)screening fails. The log report includes information about the originalcalling party number (CPN) received in the SETUP message, the name ofthe originating trunk group, and the failure reason.

Remedial actionNone. Failures are logged to provide additional information regarding failedcall screening.

CLIS100 189


NN10275-909v14 12.01 06 October 2011



Severity Warning

FormatCLIS100 mmmdd hh:mm:ss ssdd INFO CLI SCREENING FAILED

CALLING PARTY NUMBER: <dn>

CALLING PARTY : CKT <trkid>

FAILURE REASON : <reason_text>


VariableDescription

INFO CLISCREENING FAILED

Constant Fixed Indicates that CLI screening hasfailed.

CALLING PARTYNUMBER

Constant Fixed Indicates that the calling party numberfollows.

dn Integers (0 to 23digits)

Variable Identifies the originating directorynumber in the SETUP message.

CALLING PARTY Constant Fixed Indicates that the calling party follows.

CKT trkid CLLI nnnn Variable Identifies the originating trunk group

• CLLI: the common languagelocation identifier datafilled in tableCLLI

• nnnn: the circuit number for thetrunk group in CLLI (0 to 9999)

FAILURE REASON Constant Fixed Describes why CLI screening failed.

reason_text Symbolic text Variable Failure reasons can be one of thefollowing strings:

• No CLISI attribute

• CPN not datafilled in DNSCRN

• No CLILTID attribute

• LTIDs do not match

Active message exampleCLIS100 SEP05 18:14:33 4827 INFO CLI SCREENING FAILED

CALLING PARTY NUMBER: 11111



NN10275-909v14 12.01 06 October 2011


CALLING PARTY : CKT WITS10 3

FAILURE REASON: No CLISI attribute



CLIV100Log CLIV100 generates when the original or edited calling lineidentification (CLI) fails screening. The screening datafill is in option CLIVDin tables DNSCRN and LTDATA.

Log CLIV100 reports screening failures when

• the original or edited CLI is not datafilled in table DNSCRN and optionCLIVD is datafilled in table LTDATA. The failure reason is "DN orCLIVD attribute not found.".

• the DNSCRN table tuple does not contain option CLIVD. The failurereason is "DN or CLIVD attribute not found.".

• field CLIVD in table DNSCRN does not contain the same value as fieldCLIVD in table LTDATA. The failure reason is "CLIVD indices do notmatch.".

Remedial actionn/a


Severity Warning

FormatCLIV100 mmmdd hh:mm:ss ssdd INFO CLIVD Screening Failed

Calling Party Number : <calling party DN>

Originating Trunk : <trunk group number CLLI>

Failure Reason : <reason for failure>

CLIV100 191


NN10275-909v14 12.01 06 October 2011



VariableDescription

CLIV100 CLIV100 Variable This field contains the log reportnumber.

mmmdd 5 digits, alphanumeric Variable The first three letters are the month.The next two digits are the day of themonth.

hh:mm:ss numeric Variable This field contains the time in hours,minutes, and seconds.

ssdd 4 digits, numeric Variable This field is an automatically-generated sequence number.

calling party number 0 to 23 digits Variable This field contains the calling partyDN.

originating trunk alphanumeric Variable This field contains the number of theoriginating trunk group.

failure reason alphanumeric Variable This field contains the failure reason.

Active message exampleCWS11_09AY CM CLIV100 JAN05 18:14:33 2700 INFO CLIVD

Screening Failed

Calling Party Number : 1034209876

Originating Trunk : CKT CUITS14PRIC2 1

Failure Reason : DN or CLIVD attribute not found.



CNN100If the following conditions hold true in an exchange, the Japan InterconnectISUP Carrier Name Notification for Carrier Designation feature is notactivated, the TNS parameter is stripped from the IAM leaving theexchange and the CNN100 log report (INFO CNN Failure) is generated:

• The office parameter CARRNAME_ANNC in table OFCENG is set to Y

• The Network Identification Field of the TNS parameter in the incomingIAM matches a datafilled Carrier Identification code in tableCARRNAME



NN10275-909v14 12.01 06 October 2011


• The feature activation key CARRANNC is hit during translations

• The TMR value in the incoming IAM is not TMR_SPEECH orTMR_3_1KHZ_AUDIO and the CPC value in the incoming IAM is not"ordinary" or "subscriber with priority" or "test call"

If the TMR and CPC values do not match, the log says "Invalid TMRValue."

Remedial actionn/a


Severity Warning

FormatCNN100 mmmdd hh:mm:ss ssdd INFO CNN Failure

Called Party Number (CDPN) = <cdpn>

Calling Party Number (CGPN) = <cgpn>

Calling Party Category (CPC) = <cpc>

Transmission Medium Req (TMR) = <tmr>

Failure Reason = Invalid TMR Value/Invalid CPC Value


VariableDescription

Called Party Number 0 to 24 digits Variable Pre-translated digits at that switch

Calling Party Number 0 to 24 digits Variable Calling Party Number

Calling PartyCategory

ISUP CPC value Variable CPC value in the IAM

Transmission MediumRequirement

TMR value Variable TMR value in the IAM

Active message exampleCNN100 SEP14 11:25:22 8303 INFO CNN Failure

Called Party Number (CDPN) = 10424105

CNN100 193


NN10275-909v14 12.01 06 October 2011


Calling Party Number (CGPN) = 05404107

Calling Party Category (CPC) = #0A (ISUP_CPC_SUBSCRIBER_1)

Transmission Medium Req (TMR) = #02 (TMR_64KB_UNRES)

Failure Reason = Invalid TMR Value

CNN100 SEP14 11:25:22 8303 INFO CNN Failure

Called Party Number (CDPN) = 10424105

Calling Party Number (CGPN) = 05404107

Calling Party Category (CPC) = #0F (ISUP_CPC_PAYPHONE)

Transmission Medium Req (TMR) = #02 (TMR_3_1KHZ_AUDIO)

Failure Reason = Invalid CPC Value



CNN101If all the conditions for activation of the Japan Interconnect ISUP CarrierName Notification for Carrier Designation feature are met at an exchange,but the announcement CLLI in which the announcement is to be played isnot valid or idle, then the CNN101 log report (INFO CARRANNC ResourceNot Available) is generated.

Remedial actionn/a


Severity Warning

FormatCNN101 mmmdd hh:mm:ss ssdd INFO CARRANNC Resource NotAvailable Announcement CLLI = CKT ANNOUNCEMENT CLLI 0



NN10275-909v14 12.01 06 October 2011



VariableDescription

Announcement CLLI CLLI Variable The announcement CLLI

Active message exampleCNN101 SEP14 11:25:22 8505 INFO CARRANNC RESOURCE NOTAVAILABLE Announcement CLLI = CKT BCNIANN 0



CNN102If the following conditions hold true in an exchange, the Japan InterconnectISUP Carrier Name Notification for Carrier Designation feature is notactivated, the TNS parameter is stripped from the IAM leaving theexchange and the CNN102 log report (INFO Datafill Warning) isgenerated:

• The office parameter CARRNAME_ANNC in table OFCENG is set to Y

• The Network Identification Field of the TNS parameter in the incomingIAM matches a datafilled Carrier Identification code in tableCARRNAME

• The feature activation key CARRANNC is not hit during translations

Remedial actionn/a


Severity Warning

FormatCNN102 mmmdd hh:mm:ss ssdd INFO Datafill Warning

Called Party Number = <cdpn>

Failure Reason = Missing option CARRANNC in XLA tables

or unexpected TNS parm in IAM

CNN102 195


NN10275-909v14 12.01 06 October 2011



VariableDescription

Called Party Number 0 to 24 digits Variable Pre-translated digits at that switch

Active message exampleCNN102 SEP14 11:25:22 8404 INFO Datafill Warning

Called Party Number = 10424105

Failure Reason = Missing option CARRANNC in XLA tables

or unexpected TNS parm in IAM



CSFJFLog CSFJF is generated for CEPT Call Diversion and CDND featuresduring activation or deactivation by a subscriber when the Journal File isinactive.

The CSFJF logs are generated when the following events occur:

• Activation of any CEPT features when JF was inactive

• De-activation of any CEPT features when JF was inactive.

Remedial actionFollow standard administration procedures when changes are made duringthe time that the journal file is inactive.


Severity Warning

FormatTCSB_09BK CM CSFJF100 AUG24 15:37:07 8200 INFO CEPT FEATURES

<LEN> <DN>.

JOURNAL FILE NOT ACTIVE DURING CEPT UPDATE



NN10275-909v14 12.01 06 October 2011



<IBNFEAT TUPLE>

TCSB_09BK CM CSFJ100 AUG24 15:44:28 0300 INFO CEPT FEATURES

<LEN> <DN>


THE CFX TUPLE UPDATED IS:

<LEN> <KEY>

CFUF :I <DN>

CFB :A <DN>

CFD :I <DN>


VariableDescription

LEN LEN Variable LEN of the set

DN DN Variable Directory number

KEY KEY Variable Key of DN (0 for IBN)

CFUF I or A Variable State of CFU/CFF

CFB I or A Variable State of CFB

CFD I or A Variable State of CFD

Active message exampleTCSB_09BK CM CSFJF100 AUG24 15:37:07 8200 INFO CEPT FEATURES

HOST 00 0 01 03 DN 1036340103



HOST 00 0 01 03 0 CDTO CDTO ACTIVE 6340203

TCSB_09BK CM CSFJF100 AUG24 15:38:23 4200 INFO CEPT FEATURES

HOST 00 0 01 03 DN 1036340103

CSFJF 197


NN10275-909v14 12.01 06 October 2011




HOST 00 0 01 03 0 CDTO CDTO ACTIVE 6340203


HOST 00 0 01 03 DN 1036340103



HOST 00 0 01 03 0

CFUF : A 6340202


HOST 00 0 01 03 DN 1036340103



HOST 00 0 01 03 0

CFUF : I 6340202


HOST 00 0 01 03 DN 1036340103



HOST 00 0 01 03 0

CFUF : I 6340204

CFB : A 6340505

CFD : I $




NN10275-909v14 12.01 06 October 2011


HOST 00 0 01 03 DN 1036340103



HOST 00 0 01 03 0

CFUF : I 6340204

CFB : I 6340505

CFD : I $



CTFP600The system generates the CTFP600 log each time a call transfer attempt isdenied due to CTFP call type screening or throttling.

Remedial actionThe system generates the CTFP600 log each time a call transfer attempt isdenied due to CTFP call type screening or throttling. No action is required.The log is for information purposes only.


Severity Warning

Formatlogoffid CTFP600 mmmdd hh:mm:ss nnnn INFO ATTEMPT BLOCKED

Call_ID: call identification number

SUBSCRIBER_DN: subscriber directory number

TRANSFER_TO_DN: transfer to directory number

Reason: the condition that caused the log to generate

CTFP600 199


NN10275-909v14 12.01 06 October 2011



VariableDescription

logoffid symbolic text Variable Log_office_id - an office parameterdefined in table OFCVAR thatspecifies a name for the office for thepurpose of office identification in thelog output header

CTFP600 constant Fixed log name

mmmdd symbolic text Variable date the system generates the log, inthe format month:day

hh:mm:ss symbolic text Variable time the system generates the log, inthe format hour:minute:second

nnnn symbolic text Variable sequential number of logs

INFO attempt blocked constant Fixed log report type

call id symbolic text Variable call identification number

subscriber_dn symbolic text Variable a directory number

transfer_to_dn symbolic text Variable a directory number

Variable CTFP displays 10 digits DN when thenumbering plan area (NPA) isavailable and 7 digits DN when theNPA is not available.

Variable For international calls, the 011 prefixis displayed.

reason one of the followingreasons: op_outrestricted iddd_inrestricted iddd_outrestricted fgbrestricted cutthrurestricted intertollrestricted intratollrestricted coinrestricted prexlarestricted postxlarestricted throttlingexceeded

Variable the reason that the call transfer wasdenied

Active message exampleSAINUS09BL CTFP600 JUN25 12:36:20 2800 INFO ATTEMPT BLOCKED

Call_ID: 131119

SUBSCRIBER_DN : 6136218960



NN10275-909v14 12.01 06 October 2011


TRANSFER_TO_DN : 6136218902

Reason: COIN RESTRICTED



DCME100This log occurs whenever a DCME state is changed.

Remedial actionn/a


Severity Warning

FormatDCME100 <mxd> <t> <c> INFO

DCME State Changed DCME

<DCME NAME> state changed

from <Prev St> to <DCME St>


VariableDescription

m three alpha characterstring

Variable the first three characters of the month.

d two digit numericstring

Variable the current day of month in two digits.

t hh/mm/ss Variable the time log is generated.

c numeric string Variable the total numbers of whole logs.

DCME NAME Character string Variable the DCME name

DCME St MtcB, OOS, ISTb,InSv

Variable DCME state

Prev St MtcB, OOS, ISTb,InSv

Variable Previous DCME state

DCME100 201


NN10275-909v14 12.01 06 October 2011


Active message exampleDCME100 JAN09 14:15:22 1709 INFO DCME State changed

DCME DCME1 state changed from InSv to MtcB



DCME101This log occurs when a Maintenance Release Request is received from aDCME where maintenance is not supported (MTC field set to ''N(o)'' intable DCMEINV).

Remedial actionn/a


Severity Warning

FormatDCME101 <mxd> <t> <c> INFO DCME Unsupported MRR


VariableDescription





t hh/mm/ss Variable the time log is generated,


Link# 0-9 Variable Link number


Active message exampleDCME101 JAN09 14:15:22 1709 INFO DCME Unsupported MRR

Unsupported Maintenance Release Request received on link



NN10275-909v14 12.01 06 October 2011


2 of DCME DCME1.



DCME102This log occurs when a spare bit pattern (000) is received in signalling bits5, 7 and 8 of TS16 for frame 0 of PCM30 multiframe.

Remedial actionn/a


Severity Warning

FormatDCME102 <m><d> <t> <c> INFO DCME Spare bit pattern

Spare bit pattern TRM received from DCME <DCME NAME>


VariableDescription








Active message exampleDCME102 JAN09 14:15:22 1709 INFO Spare bit pattern

Spare bit pattern TRM received from DCME DCME1.


DCME102 203


NN10275-909v14 12.01 06 October 2011



DCME103This log occurs after a Bearer Service Request has been sent to theDCME, and no acknowledgement has been received within the timeoutspecified in table DCMEMTC.

Remedial actionn/a



FormatDCME103 <m><d> <t> <c> TBL DCME No Ack

No acknowledgement for <BSR> from DCME <DCME NAME>


VariableDescription








BSR 'speech', '3k1', '64k' Variable the Bearer Service Request

Active message exampleDCME103 JAN09 14:15:22 1709 TBL DCME No Ack

No acknowledgement for speech from DCME DCME1.




NN10275-909v14 12.01 06 October 2011



DCME104This log occurs when there is a change in the TS16 signalling channel froma DCME.

Remedial actionn/a


Severity Warning

FormatDCME104 <m><d> <t> <c> INFO DCME bit pattern in TS16

<BITS> received in TS16 from DCME <DCME NAME>


VariableDescription








BITS 00, 01, 10, or 11 Variable Spare bit pattern[00].Normal Service[01].Special service ack [10].ChannelOOS [11].

Active message exampleDCME104 JAN09 14:15:22 1709 INFO DCME Spare bit pattern in

TS16

Channel OOS 11 received in TS16 from DCME DCME1.


DCME104 205


NN10275-909v14 12.01 06 October 2011



DCME105This log occurs when the OMs peg count, which is incremented per DCMEon each occasion, exceeds a predetermined threshold in a specified time(datafilled in table DCMEMTC).

Remedial actionn/a


Severity Warning

FormatDCME105 <mxd> <t> <c> INFO DCME OM Peg overflow BS

<BS Type> unavailability has exceeded predetermined

threshold for DCMEBSS OM of DCME <DCME NAME>


VariableDescription








BS Type speech, 64k, 3k1 Variable the Bearer Services type

Active message exampleDCME105 JAN09 14:15:22 1709 INFO DCME OM Peg overflow

BS 64k unavailability has exceeded predetermined

threshold for DCMEBSS OM of DCME DCME1.




NN10275-909v14 12.01 06 October 2011



DCME106DCME log report 106 ''DCME Per-Trunk Signalling Monitor Fail'' isgenerated if monitoring at the XDCME sublevel of the TTP is aborted dueto a fault.

The BSS and RCVD fields are ''blanked'' if monitoring is aborted due to afault. To re-start monitoring, the trunk must be posted again or the XDCMElevel has to be re-entered. The monitoring may be aborted again if thefaults are still present.

Remedial actionQuit and then re-enter the XDCME level of the MAP display. If log re-occurs, contact next level of support.


Severity Warning

FormatDCME105 <mxd> <t> <c> INFO DCME Per-Trunk

Signalling Monitor Fail

CKT: <trunk name>

Reason: <reason text>


VariableDescription








DCME106 207


NN10275-909v14 12.01 06 October 2011



Description

CKT alpha numeric string Variable the trunk name; the CommonLanguage Location Identifier (CLLI)and the External Trunk Number(EXTRKNUM).

reason reason text Variable reason text: Fault reported byXPM,Communication with XPM;XDCMEPRC error.

Active message exampleDCME106 JAN09 14:15:22 1709 INFO DCME Per-Trunk SignallingMonitor Fail.

CKT: DCMEISUP2W 0

Reason: Communication with XPM.



DFIL139The Digital Private Network Signaling System (DPNSS) datafill (DFIL)subsystem generates log report DFIL139 during call processing when aroute list of type CFT references a non-IBN7 (Integrated Business Networkimplementation of a CCS7) trunk. Datafill has been entered for the CFTroute selector that references a Common Language Location Identifier(CLLI) other than an IBN7 signaling trunk.

Remedial actionChange the datafill of the CLLI referenced by the CFT route selector to anIBN7 trunk.


Severity Warning

FormatDFIL139 mmmdd hh:mm:ss ssdd INFO CFT WITH NONIBN7 TRUNK

ORIG_AGENT = CPID CALLED_DR = dn



NN10275-909v14 12.01 06 October 2011


RTEREF = TABLE NAME RTEREF

CFT ROUTE SELECTOR REFERENCES A NONIBN7 CLLI


VariableDescription

INFO CFT WITHNONIBN7 TRUNK

Constant Fixed Indicates a route selector of CFT anda referenced CLLI of a non-IBN7trunk.

ORIG_AGENT Symbolic text Variable CLLI and Circuit Number (CKT#) iftrunk; Line Equipment Number (LEN)and Directory Number (DN) if line

CALLED_DR Integers Variable Contents of called number digitregister (digits collected from theoriginator)

RETEREF Character string Variable Indicates the routing table name andindex to the route list element

CFT ROUTESELECTORREFERENCES ANONIBN7 CLLI

Constant Fixed Describes the datafill error

Active message exampleDFIL139 FEB04 09:21:03 3100 INFO CFT WITH NONIBN7 TRUNK

ORIG_AGENT = DPNSSSW2 4 CALLED_DR = 7224110

RTEREF = IBNRTE 90

CFT ROUTE SELECTOR REFERENCES A NONIBN7 CLLI



DFIL157Log report DFIL157 is generated if there is no tuple datafilled in tableBGIDMAP during call processing for

• the Business Group Identifier(BGID) or network significance valuesassociated with the call

• the customer group associated with the call

DFIL157 209


NN10275-909v14 12.01 06 October 2011


Remedial actionCheck the datafill of table BGIDMAP and add any missing tuples.


Severity Warning

Formatoffice_clli DFIL157 mmmdd hh:mm:ss ssdd INFO MISSING

DATAFILL IN TABLE BGIDMAP

<cps> <aid>

BGID = <bgid>

SIGNIFICANCE = <bgidsig>

CUSTNAME = <custname>

NOT DATAFILLED IN TABLE BGIDMAP


VariableDescription

cps Variable length text Variable This field indicates the call processingselector of the call that encounteredthe datafill problem.

aid Variable length text Variable This field indicates the agentidentification of the call thatencountered the datafill problem.

bgid 18 charactersmaximum

Variable This field indicates the BGID that wasused to access table BGIDMAP.

bgidsig GLOBAL orNETWORK

Variable This field indicates the networksignificance of the BGID used toaccess the table BGIDMAP.

custname 16 charactersmaximum

Variable This field indicates the customergroup that was used to access tableBGIDMAP.

Active message exampleOTWAONXBDS0 DFIL157 NOV07 17:57:04 6200 INFO MISSING

DATAFILL IN TABLE BGIDMAP



NN10275-909v14 12.01 06 October 2011


GLOG_TID_CPS 2D10009

BGID = 001122

SIGNIFICANCE = NETWORK

CUSTNAME =

NOT DATAFILLED IN TABLE BGIDMAP



DFIL161Log DFIL161 is an information log. DFIL161 is generated when HNPA1 isused in translations during CALLP or TRAVER.

Remedial actionNo action is required. DFIL161 is an information log.


Severity Warning

Format*DFIL161 MAY04 11:48:55 9700 INFO HNPA1 is being used. Itwill be

obsoleted in CSP11.

<LEN> DN <DN>

DIALLED DIGITS = <CALLED_DR>

DFIL161 211


NN10275-909v14 12.01 06 October 2011



VariableDescription

len Integer Variable Indicates the line equipment numberof the originating circuit.

dn Integer Variable Indicates the directory number of theoriginating circuit.

dialled digits Integer Variable Indicates all the digits collected thenthe HNPA1 selector is used fortranslation.

Active message example*DFIL161 MAY04 11:48:55 9700 INFO HNPA1 is being used. It

will be obsoleted in CSP11.

HOST 00 0 00 15 DN 8075641003

DIALLED DIGITS = 13065921002



DFIL321This log is generated when a subscriber dials the international/nationalprefix, and the corresponding carrier number is not defined or the tuple inMULCARR table is not found.

The DFIL 321 add_report_type() procedure is located in the IMULCAUImodule.

This log can be generated by calling the IMULCATC moduleREPORT_MULCARR_ERROR procedure. This procedure is called by:

REPORT_MULCARR_ERROR("string_of_exactly_fifty_characters_including_nulls");

Remedial actionCheck datafill of the CARR option in MULCARR and xxCODE tables.



NN10275-909v14 12.01 06 October 2011



Severity Minor

FormatDFIL321 <date><time> minor<seqno> TBL DATAFILL PROBLEM

<calling DN>

REASON = <reason text>

DIALLED DIGITS = <dialled digits>

CALLID = <call id>

INTINDEX = <carrier index for International calls>

NATINDEX = <carrier index for National calls>


VariableDescription

DN variable Variable This field contains the DN of theoriginator.

REASON 50 characters Variable This field inserts the following textmessages to describe the reason fortranslation failing with the carrier:"This subscriber has CARR optionwith NONE index" "No tuple exists forthis CARR option in MULCARR tab"

DIALLED DIGITS variable Variable This field contains all the digitsreceived.

CALLID variable Variable This field provides the ID number ofthe call that had the datafill problem.

INTINDEX variable Variable This field provides the internationalindex number of the subscriber whohad the datafill problem (if CARRoption is defined).

NATINDEX variable Variable This field provides the national indexnumber of the subscriber who had thedatafill problem (if CARR option isdefined).

DFIL321 213


NN10275-909v14 12.01 06 October 2011


Active message example* DFIL321 JUL23 08:04:26 8765 TBL DATAFILL PROBLEM

DN 3340001

REASON = This subscriber has CARR option with NONE index


CALLID= 183158

INTINDEX = None

NATINDEX = 2



DFIL322This log is generated when a subscriber dials the international or nationalprefix and translation can not continue because of a datafill problem.

Remedial actionComplete the datafill for the MULCARR and xxCODE tables.


Severity Major

FormatDFIL322 <date><time> major<seqno>TBL TRANSLATION IS FAILED

<calling DN>



CALLID = <call id>

INTINDEX = <carrier index for International calls>

NATINDEX = <carrier index for National calls>



NN10275-909v14 12.01 06 October 2011



VariableDescription


REASON 50 characters Variable This field inserts the following textmessage to describe the reason fortranslation failing with the carrier:"Translation failed"



INTINDEX variable Variable This field provides the internationalindex number of the subscriber whohad the datafill problem (if CARRoption is defined).

NATINDEX variable Variable This field provides the national indexnumber of the subscriber who had thedatafill problem (if CARR option isdefined).

Active message example* DFIL321 JUL23 08:04:26 8765 TBL TRANSLATION FAILING

DN 3340001

REASON = Translation failed because datafill problem


CALLID= 183158

INTINDEX = None

NATINDEX = 2



DFIL323This log is generated when a subscriber does not have the CARR optionand dials an International or National default prefix.

DFIL323 215


NN10275-909v14 12.01 06 October 2011


The DFIL323 add_report_type() procedure is located in the IMULCAUImodule.

This log can be generated by calling the IMULCATC moduleREPORT_MULCARR_ERROR procedure. This procedure is called by:

REPORT_MULCARR_ERROR("string_of_exactly_fifty_characters_including_nulls");

Remedial actionCheck if absence of describer CARR option is true.



FormatDFIL323 <date><time> <seqno> TBL NO CARR OPTION IN LINE

<calling DN>



CALLID = <call id>


VariableDescription


REASON 50 characters Variable This field inserts the following textmessage to describe the reason fortranslation failing with the carrier:"This subscriber has no CARR option"



Active message exampleDFIL323 JUL23 08:04:26 8765 TBL NO CARR OPTION IN LINE



NN10275-909v14 12.01 06 October 2011


DN 3340001

REASON = This subscriber has no CARR option


CALLID= 183158



DFIL600The system generates DFIL600 when Integrated Business Network (IBN)translation and datafill do not agree. Consult IBN translations and datafill todetermine which Multi Location Business Group (MBG) parameter thesystem generates.

The MBG the Network Information (NETINFO) provides group membersconnected to different nodes to have access to the same range of sharedservices. The shared service also are available when the group membersare connected to the same node. The NETINFO allows one network to useshared trunking to support multiple groups. The ANSI7 + positive signallingenhanced with some parameters to offer more services. The NETINFOparameter enhances the ANSI7 signalling and supports MBG services.Enter new field MBG is entered in the TRKSGRP table for IBN trunks.

Remedial actionChange IBN translations or TRKSGRP data when they cause the followingto occur:

Business Group calls the IBN translations determine route over MBGtrunks entered as NETINFO or NONE.


Severity Warning

Format* DFIL600 mmmdd hh:mm:ss ssdd INFO Translation or Datafillerror

CKT <CLLI>

DFIL600 217


NN10275-909v14 12.01 06 October 2011


IBN translation and TRKSGRP Datafill (MBG optional field)

are not consistent for that trunk

REASON= <rsntxt>


VariableDescription

REASON String Variable Indicates the reason the IBNtranslation and the datafill do notagree

Active message example* DFIL600 MAY04 10:00:00 8000 INFO Translation or Datafill

error

CKT ISUPTRK 2

IBN translation and TRKSGRP Datafill (MBG optional field)

are not consistent for that trunk

REASON= IBN translation: BG call:MBG field:NONE



DFIL607The datafill (DFIL) issues report log DFIL 607 when table CUSTCONS ismissing datafill.

Remedial actionAdd missing datafill to table Customer Group Attendant Consoles(CUSTCONS).


Severity Warning



NN10275-909v14 12.01 06 October 2011


FormatDFIL607 mmmdd hh:mm:ss ssdd INFO Missing Datafill

Location: <object description>

REASON: <change reason>

CALLED DR = 0

Active message exampleDFIL607 May24 10:51:27 2300 INFO MISSING DATAFILL

Location: F058 00 0 01 23 DN 0243256103

REASON: Missing tuple in table CUSTCONS

CALLED DR = 0



DFIL608The datafill (DFIL) subsystem issues report log DFIL608 when tableSUBGRP is missing datafill. The end user can correct the datafill in tableSUBGRP once the log identifies the called directory number (DN) by usingtravers.

Remedial actionAdd missing datafill to table Attendant Subgroup (SUBGRP).


Severity Warning

FormatDFIL608 mmmdd hh:mm:ss ssdd INFO MISSING DATAFILL


REASON: <change reason>

CALLED DR = 0

DFIL608 219


NN10275-909v14 12.01 06 October 2011


Active message exampleDFIL608 MAY24 10:51:27 2300 INFO MISSING DATAFILL

Location: F058 00 0 01 23 DN 0243256103

REASON: Missing tuple in table SUBGRP.

CALLED DR = 0



DFIL609The system generates this Automatic Absentee Log (DFIL609 - CDNDAutomatic Absentee log) if a subscriber is attempting to activate CDND(Call Diversion Do Not Disturb) without an announcement code for CDNDbeing set by the administrator. That is, CDND activation attempt whiledefault announcement or route was not datafilled in table CDANNS or intable OFRT.

Remedial actionThis log will be generated if a subscriber is attempting to activate CDND(Call Diversion Do Not Disturb) without an announcement code for CDNDbeing set by the administrator (that is, "00" key does not exist in tableCDANNS).

Perform the following action to rectify the problem:

• Add a valid announcement code to table CDANNS


Severity Warning

FormatRSNW04_CO4 DFIL609 <TIME> 9600 INFO CNDN TRANSLATION ERROR

<LEN> DN <DN>

CNDN activation attempt while default announcement or route

was not datafilled in table CDANNS or in table OFRT.



NN10275-909v14 12.01 06 October 2011


DIALED DIGITS = <DN>

DEFAULT ANNOUNCEMENT INDEX = 0


VariableDescription

TIME TIME Variable Current time value (mmmddhh:mm:ss)

LEN LEN Variable Line Equipment Number of the set

DN DN Variable Directory Number

Active message exampleRSNW04_CO4 DFIL609 NOV14 14:33:56 9600 INFO CNDN TRANSLATIONERROR

HOST 03 0 10 06 DN 1027835586

CNDN activation attempt while default announcement or route

was not datafilled in table CDANNS or in table OFRT.

DIALED DIGITS = 1027835585

DEFAULT ANNOUNCEMENT INDEX = 0



DFIL611The system generates this Automatic Absentee Log (DFIL611) if a call isterminating on a line with active CDTA and the announcement code couldnot be found in table CDANNS.

Remedial actionThis log will be generated if a call is terminating on a line with active CDTAand the announcement code could not be found in table CDANNS.

Perform the following action to rectify the problem:

• Add a valid announcement code to table CDANNS

DFIL611 221


NN10275-909v14 12.01 06 October 2011



Severity Warning

FormatRSNW04_CO4 DFIL611 <TIME> 2900 INFO CDTA TRANSLATION ERROR

<LEN> DN <DN>

Announcement code can not be found in table CDANNS.

CALLED DR = <DN>

ANNOUNCEMENT INDEX = <ANNOUNCEMENT INDEX>


VariableDescription

TIME TIME Variable Current time value (mmmddhh:mm:ss)

LEN LEN Variable Line Equipment Number of the set


Active message exampleRSNW04_CO4DFIL611 NOV14 14:41:10 2900 INFO CDTA TRANSLATIONERROR

HOST 03 0 10 06 DN 1027835586

Announcement code can not be found in table CDANNS.

CALLED DR = 7835585

ANNOUNCEMENT INDEX = 1



DFIL700This log informs the user of any datafill errors in table FLEXANI. This log isgenerated during CALLP and when using the DISPANI tool.



NN10275-909v14 12.01 06 October 2011


Remedial actionThe actions indicated in the REASON TEXT field must be checked. Thecounter and position of added or deleted digits must be validated.


Severity Warning

FormatDFIL700 <DATE> <TIME> <SEQNO> INFO FLEXANI Datafill Error

REASON = <REASON TEXT>

CLLI = <CLLI>

ANI_DIGITS = <CLI>


VariableDescription

SEQNO numeric Variable The current log number in thesequence of logs created in theswitch.

REASON TEXT CHECK THE ADDSUPER MODIFIER,CHECK THE REPSUPER MODIFIER,CHECK THE DELSUPER MODIFIER,CHECK THE ADDSUB MODIFIER,CHECK THE REPSUB MODIFIER,CHECK THE DELSUB MODIFIER,CHECK THE MAKSUB MODIFIER,

Variable The text message that describes thedatafill problem.

CLLI alphabetic Variable The Common Language LocationIdentifier (the logical name of thetrunk).

Active message exampleDFIL 700 JUN14 18:11:15 5900 FLEXANI Datafill Error

REASON = CHECK THE ADD SUPER MODIFIER

DFIL700 223


NN10275-909v14 12.01 06 October 2011


CLLI = TRISUPIC

ANI_DIGITS = 9728675555

DFIL 700 JUN14 18:11:15 5900 FLEXANI Datafill Error

REASON = CHECK THE DEL SUB MODIFIER

CLLI = TRISUPIC

ANI_DIGITS = 9728675555



DFIL701The Datafill (DFIL) subsystem generates DFIL701 during call processingwhen more than 18 digit are outpulsed in one stage. The CCS7 trunkscannot transmit more than 18 digits in one stage of transmitting. Whenuser entry data specifies more than this limit, DFIL generates DFIL701.

During call processing, the system links digits to be transmitted based ontranslations and the called number digit register. Links of prefix digits to thesuffix digit register must be less than 19 digits.

Log history

ISN09 (TDM)

Q01113841: log DFIL701 is generated during call processing when morethan 18 digit are outpulsed in one stage.

Remedial actionChange the datafill so that the system transmits 18 digits or less on thetrunk or use two-stage transmitting.



Format*DFIL701 mmmdd hh:mm:ss ssdd FAIL TRANSLATION ERROR



NN10275-909v14 12.01 06 October 2011


len DN dn

OG CKT = trkid, CALLED DR = dn

PREFIX DR = preftxt, SUFFIX DR = dn

MORE THAN 18 DIGITS IN 1 STAGE OF OUTPULSING


VariableDescription

FAIL TRANSLATIONERROR

Constant Fixed Indicates an error in user entry datacausing a call cutoff.

len Integers Variable Indicates the line equipment number(LEN) of originating circuit. Refer toTable I.

DN Integers Variable Indicates the ten digit directorynumber (DN) of originating circuit.Refer to Table I.

OG CKT Alphanumeric Variable Indicates the common languagelocation identifier (CLLI) and circuitnumber of the outgoing trunk on whichoutpulsing is done. Refer to Table I.

CALLED DR Integers Variable Indicates the contents of callednumber digit register (DR) (digits thatthe switch collects from the originator).Refer to Table I.

PREFIX DR Character string Variable Indicates the contents of prefix digitregister. $means the DN is notavailable for display. Refer to Table I.

SUFFIX DR Integers Variable Indicates the contents of suffix digitregister. Refer to Table I.

MORETHAN18DIGITS IN 1 STAGEOF OUTPULSING

Constant Fixed Indicates the total of the digits in theprefix and suffix registers is greaterthan 18.

Active message example*DFIL701 JAN01 09:21:03 XXXX FAIL TRANSLATION ERROR

HOST 00 1 04 19 DN 9097224112

OG CKT = TOPOGNY 1, CALLED DR = 90114466062112345

PREFIX DR = $, SUFFIX DR = 0114466062112345

DFIL701 225


NN10275-909v14 12.01 06 October 2011


MORE THAN 18 DIGITS IN 1 STAGE OF OUTPULSING



DMCT100The system generates the DMCT100 log when the subscriber adds a newDMCT entry to the DMCT list. The system generates this log if the journalfile is not active. The subscriber uses a DMCT list management session toupdate the DMCTLIST table.

Remedial actionOperating company personnel can use the information in this log to updatethe contents of the DMCTLIST table. Operating company personnel usethis information when the journal file is not active and the switch requiresrebooting.


Severity Warning

Format<Ofc_id> <Report_id> <Time_of_trace> <Seq_no> INFO Nojournal file

THE DMCTLIST TABLE WAS UPDATED WHILE THE JOURNAL

FILE WAS INACTIVE. THE NEW TUPLE IS:

<dmctlist_ruple>


VariableDescription

INFO no journal file Constant Fixed The journal file was not active duringthe DMCTLIST table update.

THE DMCTLISTTABLE WASUPDATED WHILETHE JOURNAL FILEWAS INACTIVE. THENEW TUPLE IS:

Character string Variable This field describes the new tuple inthe DMCTLIST table.



NN10275-909v14 12.01 06 October 2011


Active message examplePRIDE0J10BL DMCT100 JUL29 10:44:29 3000 INFO No journal file

THE DMCTLIST TABLE WAS UPDATED WHILE THE JOURNAL FILE

WAS INACTIVE. THE NEW TUPLE IS

I HOST 02 0 14 01 4 359300001



DMCT101The system generates this log when the subscriber adds a new entry to afull DMCT list. The system must remove the oldest entry in the DMCTLISTtable to add the new entry.

The system generates this log when the journal file is not active. Thesubscriber uses a DMCT list management session to update theDMCTLIST table.

Remedial actionOperating company personnel can use the information in this log to updatethe contents of the DMCTLIST table. Operating company personnel usethis information when the journal file is not active and the switch requiresrebooting.


Severity Warning



FILE WAS INACTIVE. THE DELETED TUPLE IS:

<dmctlist_tuple>

DMCT101 227


NN10275-909v14 12.01 06 October 2011



VariableDescription

INFO no journal file Constant Fixed The journal file was not active duringthe DMCTLIST table update.

THE DMCTLISTTABLE WASUPDATED WHILETHE JOURNAL FILEWAS INACTIVE. THEDELETED TUPLE IS:

Character string Variable This field describes the new tuple inthe DMCTLIST table.



WAS INACTIVE. THE DELETED TUPLE IS:

I HOST 02 0 14 01 4 $



DMCT102The system generates the DMCT102 log when the Denied Malicious CallTermination (DMCT) subscriber erases all entries in the DMCT list. Thesystem generates this log when the journal file is not active. The subscriberuses a DMCT list management session to update the DMCTLIST table.

Remedial actionOperating company personnel can use the information in this log to updatethe contents of the DMCTLIST table. Operating company personnel usethis information when the journal file is not active, and the switch requiresrebooting.


Severity Warning



NN10275-909v14 12.01 06 October 2011




FILE WAS INACTIVE. TUPLES HAVE BEEN DELETED FOR

KEY OWNER: <dmctlist key owner>

FROM 0 UP TO INDEX: <dmctlist key index>


VariableDescription

INFO No journal file Constant Fixed This field indicates the journal file wasnot active during the DMCTLIST tableupdate.

THE DMCTLISTTABLE WASUPDATED WHILETHE JOURNAL FILEWAS INACTIVE.TUPLES HAVE BEENDELETED FOR:

Character string Variable This field indicates the journal file wasnot active during the DMCTLIST tableupdate. The update deletes the tupleslisted in the log.

KEY OWNER Constant Fixed This field indicates the owner of theDMCT list in which the subscriberremoves entries.

FROM 0 UP TOINDEX:

Integers Variable This field indicates the number ofentries a DMCT subscriber removesfrom the DMCT list during a listmanagement session. The entryremoval begins with the first entry inthe list.



WAS INACTIVE. TUPLES HAVE BEEN DELETED FOR:

KEY OWNER: I HOST 02 1 14 01

FROM 0 UP TO INDEX: 4

DMCT102 229


NN10275-909v14 12.01 06 October 2011




DNC100Log DNC100 reports errors that result from a Digit Reception Test (DRT).Data is reported when a mismatch occurs between the digits received bythe switch and the directory number (DN) datafilled for the terminal undertest.

Remedial actionThe reports is for the information of the faultsman. No action is required inresponse to the log report.


Severity Warning

FormatDNC100 date time log no. INFO "Directory Number CheckMismatch"

DN = digit_ register Dialled Digits = digit_register


VariableDescription

date 3 characters formonth and 2 digits forday


time 6 digits<hh:mm:ss> Variable Time of log generation. Also indicatestime that inhibit is activated

log no 4 digits Variable Generation log number of the report

DN Digit register Variable Directory number of subscriber

Dialled digits Digit register Variable Dialled digits by faultsman

Active message exampleDNC100 APR01 10:56:06 8581 INFO Directory Number CheckMismatch

DN= 2000 Dialled Digits = 2001



NN10275-909v14 12.01 06 October 2011




DPNS400This log is generated by the DPNSS link subsystem (DLKSUB) when a linkenters the offline state. Link made offline by operator command.

Remedial actionn/a



FormatDPNS400 <date> <time> <number> OFFL DPNSS link <link name>

Offl from ManB


VariableDescription

TBL DPNSSConstant Variable Indicates that the link is in an ISTbstate.

Link Alphanumeric Variable Specifies the name of the affectedlink.

ISTb Text Variable Gives the current and previous stateof the link.

reastxt LAP(s) Out-of-ServiceLAPS(s) Returned-to-Service

Variable Gives the cause of the problem.

Active message exampleDPNS400 MAR16 08:15:00 2658 OFFL DPNSS link PDTC 1 0

Offl from ManB


DPNS400 231


NN10275-909v14 12.01 06 October 2011



DPNS401This log is generated by the DPNSS link subsystem (DLKSUB) when a linkenters the man-busy state. The link has been made man-busy by acommand entered at a MAP. The state of the link prior to this command isgiven.

Remedial actionn/a



Format*DPNS401 <date> <time> <number> MANB DPNSS link <link name>

ManB from <old state>


VariableDescription






Active message example*DPNS401 MAR16 08:15:00 1234 MANB DPNSS link PDTC 0 12

ManB from Offl




NN10275-909v14 12.01 06 October 2011



DPNS402This log is generated by the DPNSS link subsystem (DLKSUB) when a linkenters the system-busy state, or an event occurs within the system-busystate. The link has gone system busy or has changed substate within thesystem bust state. The possible reasons for this report are:

"carrier OOS"

"ST OOS"

"flag synch lost" (not receiving flags from far PBX)

"get conn fail" (failed to set up network connection)

"all LAPs OOS" (all LAPs in reset attempted or disabled)

"carrier RTS"

"ST RTS"

"flag synch found" (flags being received from far PBX)

Remedial actionPost the link at the MAP and identify all the problems with the link.

To clear problems, try the following in increasing order of severity:

BSY and RTS ST

BSY and RTS DPNSS link

BSY and RTS carrier

If problem is all LAPs out of service and other DPNSS links on same PDTCand MSB are functioning correctly, then swap the endpoint of the link intable DPNSSLK. If this does not cure the problem, the fault is probably withother PBX. If more than one DPNSS link has a problem try:

swact PDTC

swact MSB

swact CC

DPNS402 233


NN10275-909v14 12.01 06 October 2011




Format*DPNS402 <date> <time><number> SYSB DPNSS link <link name>

SysB from <old state>: <reason>


VariableDescription






Active message example*DPNS402 MAR16 08:20:00 1234 SYSB DPNSS link PDTC 1 13

SysB from InSv: carrier OOS



DPNS404This log is generated by the DPNSS link subsystem (DLKSUB) when allLAPs return to service. The old state can be SysB (if all LAPs were out ofservice) or ISTb (if some LAPs were already in service).

Remedial actionn/a



NN10275-909v14 12.01 06 October 2011




FormatDPNS404 <date><time><number> RTS DPNSS link <link name>

InSv from <old state>: All LAPs RTS


VariableDescription






Active message exampleDPNS404 MAR16 08:15:00 1234 RTS DPNSS link PDTC 0 12

InSv from SysB: all LAPs RTS



DPNT101The Digital Private Network Test Utility (DPNTU) tool generates log reportDPNT101 when an incoming Digital Private Network Signaling System No.1 (DPNSS) message is detected on the selected DPNSS trunk. TheDPNTU tool is accessed from an input device at the command interpreter(CI) level or any MAP display menu level by entering the DPNTUcommand.

Warm restarts and cold restarts have no effect on the DPNTU tool. All thecontrols remain active, but during a restart the DPNTU tool is in a dormantstate. If a reload restart occurs, all activated DPNTU controls are cleared.

DPNT101 235


NN10275-909v14 12.01 06 October 2011


Remedial actionThe MONITOR command of the DPNTU tool generates log reportDPNT101. The tool aids debugging, so no action is required when this logis generated.

To stop monitoring, use the REMOVE NUMBER <entry_number>command, where <ENTRY_NUMBER> is the number assigned to anactive DPNTU command.


Severity Warning

FormatDPNT101 mmmdd hh:mm:ss ssdd INFO DPNSS Incoming Message

CKT <TRUNK GROUP CLLI> <MEMBER No.>

Location: PDTC <PDTC No.>, CARRIER <Carr No.>,

CHANNEL <Ch No.>

Length: <Bytes>

Msgcode: <DPNSS Message>


VariableDescription

INFO DPNSSincoming Message

Constant Fixed Indicates that an incoming DPNSSNo-1 message is detected on theselected DPNSS trunk

CKT TRUNK GROUP CLLI Variable Group name of the selected DPNSStrunk

MEMBER No. Variable Member number of the selectedDPNSS trunk group

Location PDTC No. Variable Number of PCM30 digital trunkcontroller used

Carr No. Variable Number of the port on which the trunkis located

Ch No. Variable Telephony channel number (time slot)of the trunk



NN10275-909v14 12.01 06 October 2011



Description

Length Bytes Variable Message length in bytes

Msgcode DPNSS Message Variable Message content

Active message exampleDPNT101 DEC02 18:14:33 4827 INFO DPNSS Incoming Message

CKT MCL0217DPICO 1

Location: PDTC 6, CARRIER 2, CHANNEL 23

Length: 16

Msgcode: #05 CCM (CALL CONNECTED MESSAGE)

2A 31 23 2A 35 30 2A 32 32 32 <*1#*50*222>

33 30 30 37 23 <3007# >



DPNT102The Digital Private Network Test Utility (DPNTU) tool generates log reportDPNT102 when an outgoing Digital Private Network Signaling System No.1 (DPNSS) message is detected on the selected DPNSS trunk. TheDPNTU tool is accessed from an input device at the command interpreter(CI) level or any MAP display menu level by entering the DPNTUcommand.



To stop monitoring, use the REMOVE NUMBER<entry_number>command, where <ENTRY_NUMBER> is the numberassigned to an active DPNTU command.

DPNT102 237


NN10275-909v14 12.01 06 October 2011



Severity Warning

FormatDPNT102 mmmdd hh:mm:ss ssdd INFO DPNSS Outgoing Message



CHANNEL <Ch No.>

Length: <Bytes>



VariableDescription

INFO DPNSSOutgoing Message

Constant Fixed Indicates that an outgoing DPNSSNo-1 message is detected on theselected DPNSS trunk


MEMBER No. Variable Member number of the selectedDPNSS TRUNK group






Active message exampleDPNT102 DEC02 18:14:33 4827 INFO DPNSS Outgoing Message

CKT MCL0217DPICO 1




NN10275-909v14 12.01 06 October 2011


Length: 16


2A 31 23 2A 35 30 2A 32 32 32 <*1#*50*222>

33 30 30 37 23 <3007#>



DPNT103The Digital Private Network Test Utility (DPNTU) tool generates log reportDPNT103 when an intercepted incoming Digital Private Network SignalingSystem No. 1 (DPNSS) message is detected on the selected DPNSStrunk. The DPNTU tool is accessed from an input device at the commandinterpreter (CI) level or any MAP display menu level by entering theDPNTU command.



To stop intercepting, use the REMOVE NUMBER<entry_number>command, where <ENTRY_NUMBER> is the numberassigned to an active DPNTU command.


Severity Warning

FormatDPNT103 mmmdd hh:mm:ss ssdd INFO DPNSS Intercepted Incoming

Message


DPNT103 239


NN10275-909v14 12.01 06 October 2011



CHANNEL <Ch No.>

Length: <Bytes>



VariableDescription

INFO DPNSSIntercepted IncomingMessage

Constant Fixed Indicates that the selected DPNSStrunk detected an interceptedincoming DPNSS No-1 message








Active message exampleDPNT103 DEC02 18:14:33 4827 INFO DPNSS Intercepted Incoming

Message

CKT MCL0217DPICO 1


Length: 16

Msgcode: #08 CIM/CRM (CLEAR INDICATION[REQUEST] MESSAGE)

30 <0 >




NN10275-909v14 12.01 06 October 2011



DPNT104The Digital Private Network Test Utility (DPNTU) tool generates log reportDPNT104 when an intercepted outgoing Digital Private Network SignalingSystem No. 1 (DPNSS) message is detected on the selected DPNSStrunk. The DPNTU tool is accessed from an input device at the commandinterpreter (CI) level or any MAP display menu level by entering theDPNTU command.

Remedial actionThe INTERCEPT command of the DPNTU tool generates log reportDPNT104. The tool aids debugging, so no action is required when this logis generated.

To stop intercepting, use the REMOVE NUMBER<entry_number>command, where <ENTRY_NUMBER> is the numberassigned to an active DPNTU command.


Severity Warning

FormatDPNT104 mmmdd hh:mm:ss ssdd INFO DPNSS Intercepted Outgoing

Message

CKT <TRUNK GROUP CLLI> <MEMBER No>


CHANNEL <Ch No.>

Length: <Bytes>


DPNT104 241


NN10275-909v14 12.01 06 October 2011



VariableDescription

INFO DPNSSIntercepted OutgoingMessage

Constant Fixed Indicates that the selected DPNSStrunk intercepted an outgoing DPNSSNo-1 message








Active message exampleDPNT104 DEC02 18:14:33 4827 INFO DPNSS Intercepted Outgoing

Message

CKT MCL0217DPICO 1


Length: 16


30 <0 >



DPNT105The Digital Private Network Test Utility (DPNTU) tool generates log reportDPNT105 when an injected incoming Digital Private Network SignalingSystem No. 1 (DPNSS) message is detected on the selected DPNSS



NN10275-909v14 12.01 06 October 2011


trunk. The DPNTU tool is accessed from an input device at the commandinterpreter (CI) level or any MAP display menu level by entering theDPNTU command.

Remedial actionThe INJECT command of the DPNTU tool generates log report DPNT105.The tool aids debugging, so no action is required when this log isgenerated.


Severity Warning

FormatDPNT105 mmmdd hh:mm:ss ssdd INFO DPNSS injected By Command

(Incoming)


Message injected by:# OPERATOR


CHANNEL <Ch No.>

Length: <Bytes>



VariableDescription

INFO DPNSS injectedBy Command(Incoming)

Constant Fixed Indicates that the selected DPNSStrunk detected an injected incomingDPNSS No-1 message





DPNT105 243


NN10275-909v14 12.01 06 October 2011



Description




Active message exampleDPNT105 DEC02 18:14:33 4827 INFO DPNSS injected By Command

(Incoming)

CKT MCL0217DPICO 1

Message injected by: OPERATOR


Length: 16




DPNT106The Digital Private Network Test Utility (DPNTU) tool generates log reportDPNT106 when an injected outgoing Digital Private Network SignalingSystem No. 1 (DPNSS) message is detected on the selected DPNSStrunk. The DPNTU is accessed from an input device at the commandinterpreter (CI) level or any MAP display menu level by entering theDPNTU command.

Remedial actionThe INJECT command of the DPNTU tool generates log report DPNT106.The tool aids debugging, so no action is required when this log isgenerated.


Severity Warning



NN10275-909v14 12.01 06 October 2011


FormatDPNT106 mmmdd hh:mm:ss ssdd INFO DPNSS injected By Command

(Outgoing)




CHANNEL <Ch No.>

Length: <Bytes>



VariableDescription

INFO DPNSS injectedBy Command(Outgoing)

Constant Fixed Indicates that the selected DPNSStrunk detected an injected outgoingDPNSS No-1 message








Active message exampleDPNT106 DEC02 18:14:33 4827 INFO DPNSS injected By Command

(Outgoing)

CKT MCL0216DPICO 1


DPNT106 245


NN10275-909v14 12.01 06 October 2011



Length: 1




DPNT201The Digital Private Network Test Utility (DPNTU) tool generates log reportDPNT201 when an incoming Digital Private Network Signaling System No.1 (DPNSS) message is detected on the selected DPNSS link (DLK).

Access the DPNTU tool from an input device at the command interpreter(CI) level or any MAP display level by entering the DPNTU command. Tomonitor DPNSS messages, set up the LINK level with the LINK command.At the LINK level, enter the MONITOR command.

Warm and cold restarts have no effect on DPNTU. Activated DPNTUcontrols are cleared during a reload restart.

Remedial actionTo stop monitoring incoming messages, execute the DPNTU REMOVEcommand.


Severity Warning

FormatDPNT201 mmmdd hh:mm:ss ssdd INFO DLK Incoming Message

CKT link

Link ID: # n (on MSB7 n), Lap Number nn

Signalling Link for PDTC n, Carrier n,

Length: n

Msgcode: DPNSS message



NN10275-909v14 12.01 06 October 2011



VariableDescription

INFO DLK IncomingMessage

Constant Fixed Indicates that an incoming DPNSSNo-1 message is detected on theselected DPNSS trunk

CKT Symbolic text Variable Group name of the selected DPNSStrunk

Link ID Symbolic text Variable Provides the link identity number,which is a reference into the link tableDPNSSLK

on MSB7 n Variable Provides the number of the messageswitch and buffer 7

Lap Number nn Variable Identifies the number of the LinkAccess Protocol (LAP). LAPs arelogical signaling channels multiplexedonto the signaling link.

Signalling Link forPDTC

Symbolic text Variable Identifies the number of the PCM30digital trunk controller used

Carrier n Variable Identifies the port number on whichthe trunk is located

Length Integer Variable Indicates the message length in bytes

Msgcode Variable length string Variable Provides the incoming messagecontent

Active message exampleDPNT201 JUL28 10:00:25 4600 INFO DLK Incoming Message

CKT MCL0217DPICO 1

Link ID: 2 (on MSB? 1), Lap Number 23

Signalling Link for PDTC 6, Carrier 3,

Length: 2


30 <0 >


DPNT201 247


NN10275-909v14 12.01 06 October 2011



DPNT202The Digital Private Network Test Utility (DPNTU) tool generates log reportDPNT202 when an outgoing Digital Private Network Signaling System No.1 (DPNSS) message is detected on the selected DPNSS link (DLK).

You access the DPNTU tool from an input device at the commandinterpreter (CI) level or any MAP display level by entering the DPNTUcommand. To monitor DPNSS messages, set up the LESTK level with theLESTK command. At the LINK level, enter the MONITOR command.

Warm and cold restarts have no effect on DPNTU. Activated DPNTUcontrol are cleared during a reload restart.

Remedial actionTo stop monitoring outgoing messages, execute the DPNTU REMOVEcommand.


Severity Warning

FormatDPNT202 mmmdd hh:mm:ss ssdd INFO DLK Outgoing Message

CKT link



Length: n



VariableDescription





NN10275-909v14 12.01 06 October 2011



Description




Symbolic text Variable Identifies the number of the PCM30digital trunk controller (PDTC) used



Msgcode Variable length string Variable Provides the outgoing messagecontent

INFO DLK OutgoingMessage

Constant Fixed Indicates that an outgoing DPNSSNo-1 message is detected on theselected DPNSS trunk

Active message exampleDPNT202 JUL28 10:00:25 4500 INFO DLK Outgoing Message

CKT MCL0216DPOGO 1

Link ID: 1 (on MSB7 1), Lap Number 23


Length: 2


30 <0 >



DPNT203The Digital Private Network Test Utility (DPNTU) tool generates log reportDPNT203 when an intercepted incoming Digital Private Network SignalingSystem No. 1 (DPNSS) message is detected on the selected DPNSS link(DLK).

DPNT203 249


NN10275-909v14 12.01 06 October 2011


You access the DPNTU tool from an input device at the commandinterpreter (CI) level or any MAP display level by entering the DPNTUcommand. To monitor the DPNSS messages, set up the LESTK level withthe LESTK command. At the LINK level, enter the INTERCEPT command.


Remedial actionTo stop intercepting incoming messages, execute the DPNTU REMOVEcommand.


Severity Warning

FormatDPNT203 mmmdd hh:mm:ss ssdd INFO DLK Intercepted Incoming

Message

CKT link



Length: n



VariableDescription

INFO DLK InterceptedIncoming Message

Constant Fixed Indicates that an intercepted incomingDPNSS No-1 message is detected onthe selected DPNSS trunk



on MSB7 n Variable Provides the number of the messageswitch and the buffer



NN10275-909v14 12.01 06 October 2011



Description






Msgcode Variable length string Variable Provides the intercepted incomingmessage content

Active message exampleDPNT203 JUL28 10:00:25 4600 INFO DLK Intercepted Incoming

Message

CKT MCL0217DPICO 1



Length: 2


30 <0 >



DPNT204The Digital Private Network Test Utility (DPNTU) tool generates log reportDPNT204 when an intercepted outgoing Digital Private Network SignalingSystem No. 1 (DPNSS) message is detected on the selected DPNSS link(DLK).

DPNT204 251


NN10275-909v14 12.01 06 October 2011


You access the DPNTU tool from an input device at the commandinterpreter (CI) level or any MAP display level by entering the DPNTUcommand. To monitor DPNSS messages, set up the LINK level with theLINK command. At the LINK level, enter the INTERCEPT command.


Remedial actionTo stop intercepting outgoing messages, execute the DPNTU REMOVEcommand.


Severity Warning

FormatDPNT204 mmmdd hh:mm:ss ssdd INFO DLK Intercepted Outgoing

Message

CKT link



Length: n



VariableDescription

INFO DLK InterceptedOutgoing Message

Constant Fixed Indicates that an intercepted outgoingDPNSS No-1 message is detected onthe selected trunk






NN10275-909v14 12.01 06 October 2011



Description






Msgcode Variable length string Variable Provides the intercepted outgoingmessage content

Active message exampleDPNT204 JUL28 10:00:25 4600 INFO DLK Intercepted Outgoing

Message

CKT MCL0216DPOGO 1



Length: 2


1IA <. >



DPNT205The Digital Private Network Test Utility (DPNTU) tool generates log reportDPNT205 when an injected incoming Digital Private Network SignalingSystem No. 1 (DPNSS) message is detected on the selected DPNSS link(DLK).

DPNT205 253


NN10275-909v14 12.01 06 October 2011


You access the DPNTU tool from an input device at the commandinterpreter (CI) level or any MAP display level by entering the DPNTUcommand. To monitor DPNSS messages, set up the LESTK level with theLESTK command. At the LINK level, enter the INJECT command.

Remedial actionn/a


Severity Warning

FormatDPNT205 mmmdd hh:mm:ss ssdd INFO DLK Message Injected by

Command (Incoming)

CKT link




Length: n



VariableDescription

INFO DLK MessageInjected By Command(Incoming)

Constant Fixed Indicates that an injected incomingDPNSS message is detected on theincoming trunk

Message injected by:OPERATOR

Constant Fixed Indicates that the message wasentered by the operator


Link ID Symbolic text Variable Provides the link identity numberwhich is a reference into the link tableDPNSSLK

on MSB n Variable Provides the number of the messageswitch and buffer n



NN10275-909v14 12.01 06 October 2011



Description






Msgcode variable length string Variable Provides the injected incomingmessage content

Active message exampleDPNT205 JUL28 10:00:25 4600 INFO DLK Message Injected by

Command (Incoming)

CKT MCL0217DPICO 1




Length: 1




DPNT206The Digital Private Network Test Utility (DPNTU) tool generates log reportDPNT206 when an injected outgoing Digital Private Network SignalingSystem No. 1 (DPNSS) message is detected on the selected DPNSS link(DLK).

DPNT206 255


NN10275-909v14 12.01 06 October 2011


You access the DPNTU tool from an input device at the commandinterpreter (CI) level or any MAP display level by entering the DPNTUcommand. To monitor DPNSS messages, set up the LINK level with theLINK command. At the LINK level, enter the INJECT command.

Remedial actionn/a


Severity Warning

FormatDPNT206 mmmdd hh:mm:ss ssdd INFO DLK Message Injected by

Command (Outgoing)

CKT link




Length: n



VariableDescription


INFO DLK MessageInjected By Command(Outgoing)

Constant Fixed Indicates that an injected outgoingDPNSS No-1 message is detected onthe selected DPNSS trunk

Message injected by:OPERATOR

Constant Fixed Indicates that the message wasentered by the operator

Link ID Symbolic text Variable Provides the link identity numberwhich is a reference into the link tableDPNSSLK




NN10275-909v14 12.01 06 October 2011



Description



Symbolic text Variable Identifies the number of the peripheraldigital trunk controller used



Msgcode Variable length string Variable Provides the injected outgoingmessage content

Active message exampleDPNT206 JUL28 10:00:25 0800 INFO DLK Message Injected by

Command (Outgoing)

CKT MCL0216DPOGO 1




Length: 1




DRM602Tape out of space. This log report is generated when a DAT tape runs outof space while trying to write a file to tape. This is a prompt for theoperating company personnel to mount a new tape on the FP DAT drive.

DRM602 257


NN10275-909v14 12.01 06 October 2011


Remedial actionWhen a DRM602 log report occurs, the operating company personnelshould eject the currently mounted tape for the node and device causingthe report, mount a new tape, and copy the filename to the new tape. Noimmediate action is required, but the operating company personnel shouldnote that the file causing this log report has not been backed up to tape.


Severity Warning

FormatDRM602 mmmdd hh:mm:ss ss INFO Application Protocol

A DAT tape ran out of room while attempting to write a file

Node Name: <node name>

DAT Tape Drive: <device name>

File Name: <file name>


VariableDescription

mmmdd hh mm:ss Constant Fixed Month, Date, hour, minutes, seconds

INFO ApplicationProtocol

Constant Fixed Text String

Log Text "A DAT tape ran outof room whileattempting to write afile"

Variable Information regarding tape space error

node name Symbolic Text Variable The name of the node on which theevent occurred (for example FP0)

device name Symbolic Text Variable The name of the device on which theevent occurred (for example CT02

file name Symbolic Text Variable The name of the file causing the event(for example UN0002181400140CC)

Active message exampleDRM602 AUG11 10 : 03 : 00 INFO Device State Change

A DAT tape ran out of room while attempting to write a file.



NN10275-909v14 12.01 06 October 2011


Node Name: FP0

DAT Tape Drive: CT02

File Name: UN0002181400140CC



DRM603Dump is idle on non-current date. This log report is generated when a DATDUMP process runs out of files to write to tape on a non-current date. Thisis a prompt for the operating company personnel to decide whether or notto deactivate the dump process via a DAT DUMP STOP.

Remedial actionWhen a DRM603 log report occurs, the operating company personnelshould determine if the dump process should be stopped. This will dependon whether multiple applications belong to the group identification specifiedfor the dump. For example, if there are multiple billing streams registeredfor DRM, it is possible that one stream will be finished and produce theDRM603 log before the other stream has closed its last file. n/a


Severity Warning

FormatDRM603 mmmdd hh:mm:ss ss INFO Operation

A DAT DUMP process is now waiting for additional files toclose for

a date other than the current date.

DAT Tape Drive: <device name>


VariableDescription

mmddhh mm:ss Constant Fixed Month, Date, hour, minutes, seconds

INFO Operation Constant Fixed Text String

DRM603 259


NN10275-909v14 12.01 06 October 2011



Description

Log Text "A DAT DUMPprocess is nowwaiting for additionalfiles to close for adate other than thecurrent date."

Variable Information regarding tape space error

device name Symbolic Text Variable The name of the device on which theevent occurred (for example CT02)

Active message exampleDRM603 AUG11 10 : 03 : 00 INFO Device State Change

A DAT DUMP process is now waiting for additional files toclose for a date other than the current date.

DAT Tape Drive: CT02



DRT100The DRT100 log reports errors that result from a Digit Reception Test(DRT). Data is reported when a mismatch occurs between the digitsreceived by the switch and those expected, for the terminal type.

Remedial actionThe reports is for the information of the faultsman, no action is taken indirect response to the generation of the log.


Severity Warning

FormatDRT100 date time log no. INFO "Digit reception TestMismatch"

DN = digit_ register Received Digits = digit_register

Expected Digits = digit_register



NN10275-909v14 12.01 06 October 2011



VariableDescription

date 3 characters formonth and 2 digit forday


time 6 digit<hh:mm:ss> Variable Time of log generation. Also indicatestime that inhibit is activated.

log no 4 digit Variable Generation log number of the report

DN Digit register Variable Directory number of subscriber

Received digits Digit register Variable Dialled digits by faultsman

Expected digits Digit register Variable All digits on a DTMF telephone or zeroon a DPtelephone

Active message exampleDRT100 APR01 10:56:06 8581 INFO Digit reception TestMismatch

DN = 2000 Received Digits = 123456

Expected Digits = 1234567890*#



EIN301The Feature Processing Environment (FPE) generates the FPE trouble logreport EIN301. A trouble log indicates abnormal switch behavior. Theswitch requires maintenance action by the operating company. Parametersfrom a Generic AIN Messaging Environment (GAME) return procedureappear in the log. This log reports GAME call processing problems thatoccur in the FPE.

The first five fields allow the operating company to analyze and correct theproblem. The Trouble field identifies the trouble entity. The Action fieldsuggests appropriate maintenance action for the problem. The Reasonfield indicates the root cause of the log generation.

The system does not support the Implied State Change Log that indicatesthat the trouble entity was removed.

EIN301 261


NN10275-909v14 12.01 06 October 2011


Remedial actionSee the Action field of the log.



FormatUKC9004BI EIN301 mmmdd hh:mm:ss ssdd TBL FPE

Location: <FPE>

Status: <Trouble alert>

Trouble: <TROUBLE_DESCRIPTION>

Action: <ACTION_DESCRIPTION>

Reason: <EIN_LOG_REASON_TYPE>

Svc_Key: <Service_Key>

GTT: <GTT_digits>

XLAB : <XLAB_digits>

CgPN: <CallingPN>

CallID: <CallID>8 CDB_Message: <CDB_message>

OperationID: <Operation_ID>

ParameterID: <Parameter_ID>

SSF_State: <SSF_state>

SSF_Substate:<SSF_substate>

SRF_State: <SRF_state>

Port: <Port>

CVS State: <Connection View State>

LegID 1: <Originating LegID>



NN10275-909v14 12.01 06 October 2011


LegID 2: <Terminating LegID>

CallSegmentID:<Call Segment ID>

Data Size: <bytes>

Data:

------

<User data>


VariableDescription

Location FPE Variable Location. This field identifies thelocation of the trouble condition.

Status Trouble alert Variable Status. This field identifies the statusof the trouble entity.

Trouble Up to 48 characters Variable Trouble. This field describes thetrouble condition.

Action Up to 48 characters Variable Action. This field describes the actionassociated with the trouble condition.

Reason Up to 48 characters Variable Reason. This field supplies the reasonfor the trouble condition.

Svc_Key 0 to 9999 Variable Service key. Service key is aparameter of the EuropeanTelecommunications StandardsInstitute Intelligent NetworkApplication Protocol (ETSI INAP)InitialDP operation. This parameteridentifies the requested IN service tothe service control point (SCP).

GTT NIL to999999999999999999

Variable Global title translation digits. This fieldidentifies the route to the SCP. ThisDigit_Register type field contains amaximum of 18 digits.

XLAB NIL to999999999999999999999999999999

Variable Translation block digits. This fieldidentifies the translated dialed digits.This Digit_Register type field containsa maximum of 30 digits.

CgPN NIL to999999999999999999999999999999 99

Variable Calling party number. This fieldidentifies the calling party. ThisDigit32_DR type field contains amaximum of 32 digits.

EIN301 263


NN10275-909v14 12.01 06 October 2011



Description

CallID 0 to 4294967296 Variable Call ID. This field identifies the call ID.The call ID is an identifier associatedwith a specified call.

CDB_Message #000 to #FFF Variable Call Data Block (CDB) message. Thisfield identifies the message stored inthe message field of the Call DataBlock. This message is normally thelast message that the call receives.

Operation ID Up to 48 characters Variable Operation ID. This field contains theoperation ID text.

ParameterID Up to 48 characters Variable Parameter ID. This field identifies theGAME parameter.

SSF_State Up to 48 characters Variable Service Switching Function (SSF)state. This field indicates the state ofthe SSF when the system generatedthe log.

SSF_Substate Up to 48 characters Variable SSF substate. This field indicates thestate of the SSF when the systemgenerated the log. Possible valuesare:

• Waiting For Instructions

• Monitoring

• Not Applicable

SRF_State Up to 48 characters Variable Service Resource Function (SRF)state. This field indicates the state ofthe SRF when the system generatedthe log.

Port 0 to 14 Variable Port. This field identifies the portreceiving the message.

CVS State CS2 Null CVS, CS2Orig Setup, CS2Stable 2 Party, CS2 Mparty Setup, CS2 CallHold, or CS2 StableMparty

Variable Connection View State. This fieldindicates the connection view statethat applied to the call when thesystem generated the log.

LegID 1 No LegID, ControllerLegID, or DMSResource

Variable LegID 1. This field indicates the LegIDof the originating leg of the callsegment that generated the log.



NN10275-909v14 12.01 06 October 2011



Description

DMS Resource denotes a leg that wasconnected to a DMS resource. A portor the Specialized Resource Functionis an example of a DMS resource.

LegID 2 No LegID, ControllerLegID, Passive 1LegID, Passive 2LegID, or DMSResource

Variable LegID 2. This field indicates the LegIDof the terminating leg of the callsegment that generated the log.

DMS Resource denotes a leg thatconnected to a DMS resource such asa port or the Specialized ResourceFunction.

CallSegmentID Call Segment Nil, CallSegment One, or CallSegment Two

Variable Call Segment ID. This field indicatesthe callSegmentID of the call segmentthat generated the log.

Data Size 0 to 128 Variable Data size. This field lists the numberof bytes in the data field.

Data #00 to #FF Variable Data. This field contains optional user-defined data. This field can contain amaximum of 128 hexadecimal bytes.

Active message exampleUKC9004BI EIN301 JUL06 15:09:30 2800 TBL FPE

Location: FPE

Status: Trouble alert

Trouble: IN Service Timer Expired whilst Waiting on SCP

Action: Check SVC Oper, SCP Comms and TSSF Office Parms

Reason: TSSF_EXPIRY

Svc_Key: 4444

GTT: 050051234

XLAB: 05634529565699050051234

CgPN:

CallID: 11337728 CDB_Message: 0277

OperationID: Connect ID

EIN301 265


NN10275-909v14 12.01 06 October 2011


ParameterID: Cut and Paste PID

SSF_State: AIN Init

SSF_Substate: Not Applicable

SRF_State: SRF Idle

Port: 1

CVS State: CS2 Orig Setup

LegID 1: Controller LegID

LegID 2: No LegID

CallSegmentID: Call Segment One

Data Size: 61 bytes

Data:

----

D7 00 14 00 30 12 EE EE EE EE EE EE EE EE EE EE

EE EE EE EE EE EE EE EE 84 04 99 99 99 99 83 03

34 56 78 84 04 45 67 89 45 A5 D5 58 55 55 55 A7

AD C4 44 88 71 7E 7E D2 37 45 45 45 78



EIN305The system generates the EIN305, Generic Advanced Intelligent Network(AIN) Messaging Environment (GAME) Trouble Log from within the GAME.

The first five fields allow the operating company to analyze and correct theproblem. The Trouble field identifies the trouble entity. The action field inlog EIN305 suggests the correcting action. The reason field indicates theroot cause of the log generation.



NN10275-909v14 12.01 06 October 2011


The Implied State Change Log indicates that the trouble entity is removed.This log is not supported.

Remedial actionRefer to the Action field of the log.



FormatUKC9004BI EIN305 JUL06 15:09:30 2800 TBL FPE

Location: <GAME>

Status: <Trouble alert>




SSP Trans ID: <SSP Trans ID>

SCP Trans ID: <SCP Trans ID>

Called Addr Digits: <Called address digits>

TCAP Package Type: <TCAP Package type>

TCAP Component Type: <TCAP Component type>

Calling Addr Info:

------

<Calling address information>

Data Size: <bytes>

Data:

--

<User data>

EIN305 267


NN10275-909v14 12.01 06 October 2011



VariableDescription

Location GAME Variable Location. This field identifies thelocation of the trouble condition.

Status Trouble alert Variable Status. This field identifies the statusof the trouble entity.

Trouble up to 48 characters Variable Trouble. This field describes thetrouble condition.

Action up to 48 characters Variable Action. This field describes the actionassociated with the trouble condition.

Reason up to 48 characters Variable Reason. This field supplies the reasonfor the trouble condition.

SSP Trans ID 0 to 65536 Variable Service switching point transaction ID.This optional field identifies theoriginating transaction ID, which linksan originating transaction to a givencall.

SCP Trans ID 0 to 65536 Variable Service control point transaction ID.This optional field identifies thedestination transaction ID, which linksan destination transaction to a givencall.

Called Addr Digits NIL to999999999999999999999999999999

Variable Called address digits. This optionalfield contains the complete numberdialed by the originating party. Thisfield contains a maximum of 30 digits.

TCAP Package Type up to 48 characters Variable TCAP package type. This optionalfield identifies the type of packageused by the Transaction CapabilitiesApplication Part (TCAP) message.

TCAP ComponentType

up to 48 characters Variable TCAP component type. This optionalfield identifies the type of componentused by the TCAP message.

Calling Addr Info 00 to FF Variable Calling address information. This fieldcontains the full Signalling ConnectionControl Part (SCCP) address. It cancontain up to 48 hexadecimal bytes.

Data Size 0 to 128 Variable Data size. This field lists the numberof bytes in the data field.

Data #00 to #FF Variable Data. This field contains optional datadefined by the user. It can contain upto 128 hexadecimal bytes.



NN10275-909v14 12.01 06 October 2011


Active message exampleUKC9004BI EIN305 JUL03 19:49:22 5900 TBL GAME

Location: GAME

Status: Trouble alert

Trouble: Nil Trouble

Action: Nil Action

Reason: TCAP Decode Failure

SSP Trans ID: 0

SCP Trans ID: 0 -1

Called Addr Digits: 0500577729565690500667890

TCAP Package Type: Continue

Calling Addr Info:

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

30 14 47 6A 10 01 4D 01 B9 A2 67 B0 68 4F 31 04

E8 11 67 B0 88 4F 0E 07 74 05 4F 23 B4 FD 0E 07

F8 04 67 B0 78 4F 31 04 04 12 67 B0 88 4F 50 23

Data Size: = 61 bytes

Data:

----



34 56 78 84 04 45 67 89 45 A5 D5 58 55 55 55 A7

AD C4 44 88 71 7E 7E D2 37 45 45 45 78


EIN305 269


NN10275-909v14 12.01 06 October 2011



EIN310EIN310 is a generic trouble log report specific to billing. The subsystemgenerates log report EIN310 in the Feature Processing Environment (FPE)or Generic Advanced Intelligent Network (AIN) Messaging Environment(GAME) for incoming operations. The report does not report callprocessing problems from within GAME. The subsystem generates the logwith a major alarm. A double asterisk in the second field of the log headerindicates the alarm.

The first five fields allow the operating company to analyze and correct theproblem. The Trouble field identifies the Trouble entity. The Action fieldsuggests the action to correct the trouble. The Reason field indicates thereason the subsystem generates the log.

The subsystem does not support the Implied State Change Log. This logindicates that the trouble entity is removed.

Remedial actionSee the Action field of the log.


Severity Major

FormatUKC9004BI ** mmmdd hh:mm:ss ssdd TBL Billing Major Alarm

Location: <FPE or GAME>

Status: < Alarm raised>




SSP Trans ID: <SSP trans ID>

SCP Trans ID: <SCP trans ID>

Called Addr Digits: <Called address digits>



NN10275-909v14 12.01 06 October 2011


Svc_Key: <Service_Key> GTT: <GTT_digits>

CgPN: <Calling Party Number>

CallID: <CallID> CDB_Message: <CDB_message>



SSF_State: <SSF_state>

SSF_Substate: <SSF_substate>

SRF_State: <SRF_state>

Port: <Port>

TCAP Package Type: <TCAP Package type>

TCAP Component Type: <TCAP Component type>

Calling Addr Info:

------

<Calling address information>

Data Size: <bytes>

Data:

--

<User data>


VariableDescription

Location FPE or GAME Variable Indicates the location of the troublecondition.

Status Alarm raised Variable Indicates the status of the troubleentity.

Trouble up to 48 characters Variable Describes the trouble condition.

Action up to 48 characters Variable Describes the action that associateswith the trouble condition.

EIN310 271


NN10275-909v14 12.01 06 October 2011



Description

Reason up to 48 characters Variable Indicates the reason for the troublecondition.

SSP Trans ID 0 to 65536 Variable Indicates the service switching point(SSP) transaction ID that links anoriginating transaction to a given call.

SCP Trans ID 0 to 65536 Variable Indicates the service control point(SCP) destination transaction ID thatlinks a destination transaction to agiven call.

Called Addr Digits NIL to999999999999999999999999999999

Variable Contains the complete number dialedby the party which originated the callto a maximum of 30 digits.

Svc_Key 0 to 9999 Variable Indicates the Service key (Svc_Key)parameter of the InitiaIDP operation.This field identifies the requested INservice to the SCP.

Global title translationdigits (GTT)

NIL to999999999999999999

Variable Indicates the route to the SCP. ThisDigit_Register type field can hold upto 18 digits.

Calling Party Number(CgPN)

NIL to999999999999999999999999999999 99

Variable Indicates the calling party. TheDigit32_DR type field can hold amaximum of 32 digits.

CallID 0 to 4294967296 Variable Identifies the call ID, a differentidentifier associated with a given call.

Call data blockmessage(CDB_Message)

#000 to #FFF Variable Indicates the message stored in themessage field of the call data block.This message is normally the lastmessage the call receives.

OperationID up to 48 characters Variable Operation ID. This field contains theoperation ID text.

ParameterID up to 48 characters Variable Indicates the GAME parameter.

SSF_State up to 48 characters Variable The Service Switching Function (SSF)state indicates the state of the SSFwhen the subsystem generated thelog.



NN10275-909v14 12.01 06 October 2011



Description

SSF_Substate up to 48 characters Variable SSF substate. This field indicates thestate of the SSF when the systemgenerated the log. Possible valuesare:

• Waiting For Instructions

• Monitoring

• Not Applicable

SRF_State up to 48 characters Variable Service Resource Function (SRF)state. This field indicates the state ofthe SRF when the subsystemgenerated the log.

Port 0 to 14 Variable Port. This field identifies the port thatreceived the message.

TransactionCapabilitiesApplication Part(TCAP) PackageType

up to 48 characters Variable The package type that the TCAPmessage uses.

TCAP ComponentType

up to 48 characters Variable Identifies the component type theTCAP message uses.

Calling Addr Info 00 to FF Variable Contains the full SCP address andholds a maximum of 48 hexadecimalbytes.

Data Size 0 to 128 Variable Lists the number of bytes in the datafield.

Data #00 to #FF Variable Contains optional data forinterpretation by the user. It can holdup to 128 hexadecimal bytes.

Active message exampleUKC9004BI ** EIN310 JUL06 15:09:30 2800 TBL Billing Major

Alarm

Location: FPE/GAME

Status: Alarm raised

Trouble: Trouble Within an IN Service

Action: Check for Error at the SCP

EIN310 273


NN10275-909v14 12.01 06 October 2011


Reason: Incorrect Number of parameters

SSP Trans ID: 0

SCP Trans ID: 0 -1

Called Addr Digits: 0500577729565690500667890

Svc_Key: 4444 GTT: 050051234

CgPN:

CallID: 11337728 CDB_Message: 0277

OperationID: Connect ID

ParameterID: Cut and Paste PID

SSF_State: AIN Init

SSF_Substate: Not Applicable

SRF_State: SRF Idle

Port: 1

TCAP Package Type: Continue

TCAP Component Type: Invoke Component

Calling Addr Info:

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

30 14 47 6A 10 01 4D 01 B9 A2 67 B0 68 4F 31 04

E8 11 67 B0 88 4F 0E 07 74 05 4F 23 B4 FD 0E 07

F8 04 67 B0 78 4F 31 04 04 12 67 B0 88 4F 50 23

Data Size: = 61 bytes

Data:

----




NN10275-909v14 12.01 06 October 2011



34 56 78 84 04 45 67 89 45 A5 D5 58 55 55 55 A7

AD C4 44 88 71 7E 7E D2 37 45 45 45 78



EIN315Log EIN315 is a trouble log. The system generates EIN315 when events inthe non-call-related (NCR) Service Filtering function of the DMS-100Service Switching Point (SSP) occur.

TROUBLE DESCRIPTION VALUES

• Type value 0 -- Nil Problem.

• Type value 1 -- IN Service Timer stopped while service timer waited onSCP.

• Type value 2 -- Cannot request an IN Service from the SC.

• Type value 3 -- Problem to collect data for IN Service Query.

• Type value 4 -- IN SVC Specific Billing Data Lost for a Call.

• Type value 5 -- Problem with an IN SVC, possibly with SVC Logic.

• Type value 6 -- Problem in an IN Service.

• Type value 7 -- Problem to collect digits in an IN Service.

• Type value 8 -- Problem to collect DGTS in an IN SVC User Error.

• Type value 9 -- Did not provide Tone Announcement in IN SVC.

• Type value 10 -- Not able to obtain CalledPN required for IN.

• Type value 11 -- Not able to obtain CallingPN required for IN.

• Type value 12 -- Error while system processed an RRBCSMEoperation.

• Type value 13 -- IN SVC EDPs not supported for Given Agent on Call.

• Type value 14 -- N Cannot Interwork with another service.

• Type value 15 -- Non IN resources not found.

• Type value 16 -- Maximum number of SSF operations exceeded.

• Type value 17 -- IN Extensions not supported for given operation.

EIN315 275


NN10275-909v14 12.01 06 October 2011


• Type value 18 -- Not able to obtain IN Service Info options.

• Type value 19 -- Problem or Error with Data Received from SCP.

• Type value 20 -- Request to Work with Dialogue that is not known.

• Type value 21 -- Problem of TCAP Package/Component group.

• Type value 22 -- Received Package Type that is not supported from theSCP.

• Type value 23 -- Not enough resources to process INAP Messages.

• Type value 24 -- Cannot Relate Rxd Invoke ID to a previous operation.

• Type value 25 -- This INAP operation is not supported at the presenttime.

• Type value 26 -- SSP-SCP Communication Error, possibly CCS7 Link.

• Type value 27 -- GAME cannot obtain Destination Transaction ID.

• Type value 28 -- INAP Error in Entering Message from the SCP.

• Type value 29 -- Rxd Invoke ID duplicated in an Active operation.

• Type value 30 -- Protocol Problem in Messaging Below INAP.

• Type value 31 -- Use that is not expected or Error in TCAP Endpackage.

• Type value 32 -- IN Service temporary connection is not supported forGiven Agent on Call.

• Type value 33 -- Error while the system processed Extensionsparameter.

• Type value 34 -- Transition to Monitor state is not permitted.

• Type value 35 -- GAME detected error or not able to send data to SCP.

• Type value 36 -- Function that is not supported requested by the SCP.

• Type value 37 -- Requested IN function is not available.

• Type value 38 -- Problem with attempt to play Announcement or collectDigits in IN Service.

• Type value 39 -- Problem with attempt to store CCB and HDB Values.

• Type value 40 -- Problem with attempt to return CCB and HDB Values.

• Type value 41 -- IN Service TONEBURST is not supported for GivenAgent on Call.

• Type value 42 -- Return Error with Invoke ID that is not correct.



NN10275-909v14 12.01 06 October 2011


REASON ID DESCRIPTIONS

• Type value 0 -- Nil Reason.

• Type value 1 -- Parameter out of range.

• Type value 2 -- Last Two Dgts of CalledAddressValue Not Ok.

• Type value 3 -- Stop Time before Start Time.

• Type value 4 -- ASF not permitted because of Office Dump.

• Type value 5 -- Parameter that is not expected.

• Type value 6 --Data Value that is not expected.

OPERATION ID DESCRIPTIONS

• Type value 04 -- Continue ID.

• Type value 20 -- Prompt and Collect User Information ID.

• Type value 21 -- Connect to Resource ID.

• Type value 22 -- Disconnect Forward Connection ID.

• Type value 23 -- Activate Service Filtering ID.

• Type value 24 -- Apply Charging ID.

• Type value 25 -- Apply Charging Report ID.

• Type value 26 -- Assist Request Instructions ID.

• Type value 27 -- Call Gap ID.

• Type value 28 -- Call Information Request ID.

• Type value 29 -- Call Information Report ID.

• Type value 30 -- Cancel ID.

• Type value 31 -- Collect Information ID.

• Type value 32 -- Connect ID.

• Type value 33 -- Dialogue Portion ID.

• Type value 34 -- Establish Temporary Connection ID.

• Type value 35 -- Request Notif Charge ID.

• Type value 36 -- Event Notif Charge ID.

• Type value 37 -- Event Report BCSM ID.

• Type value 38 -- Provide Charge Information ID.

• Type value 39 -- Initial DP ID.

• Type value 40 -- Start Call Attempt ID.

EIN315 277


NN10275-909v14 12.01 06 October 2011


• Type value 41 -- Play Announcement ID.

• Type value 42 -- Release Call ID.

• Type value 43 -- Request Report BCSM Event ID.

• Type value 44 -- Reset Timer ID.

• Type value 45 -- Send Charge Information ID.

• Type value 46 -- Service Filtering Response ID.

• Type value 47 -- Special Resource Report ID.

• Type value 48 -- Activity Test ID.

PARAMETER ID DESCRIPTIONS

• Type value 4 -- Bearer ability PID.

• Type value 5 -- Busy Cause PID.

• Type value 6 -- Called Party ID PID.

• Type value 14 -- Collected Digits PID.

• Type value 15 -- Failure Cause.

• Type value 16 to 17 -- Parameter ID that is not supported.

• Type value 18 -- Original Called Party ID PID.

• Type value 19 -- Parameter ID that is not supported.

• Type value 20 -- Redirecting Party ID PID.

• Type value 21 -- Redirection Information PID.

• Type value 40 -- Answer Indicator PID.

• Type value 200 -- ACH Billing Charging Description PID.

• Type value 201 -- Address and Service PID.

• Type value 202 -- Additional Calling Party Number PID.

• Type value 203 -- Alerting Pattern PID.

• Type value 204 -- All Requests PID.

• Type value 205 -- Analyzed Information Specific Info PID.

• Type value 206 -- Application Timer PID.

• Type value 207 -- Assisting SSP IP Routing Address PID.

• Type value 208 -- Attributes PID.

• Type value 209 -- BCSM Event PID.

• Type value 210 -- BCSM Events PID.



NN10275-909v14 12.01 06 October 2011


• Type value 211 -- Bearer Cap PID.

• Type value 212 -- Billing Charging Description PID.

• Type value 213 -- Both PID.

• Type value 214 -- Call Attempt Elapsed Time Value PID.

• Type value 215 -- Call Attempt Elapsed Time Value PID.

• Type value 216 -- Call Stop Time Value PID.

• Type value 217 -- Called Address and Service PID.

• Type value 218 -- Called Address Value PID.

• Type value 219 -- Calling Address and Service PID.

• Type value 220 -- Calling Address Value PID.

• Type value 221 -- Calling Party Number PID.

• Type value 222 -- Category PID of the Calling Party.

• Type value 223 -- Call Result PID.

• Type value 224 -- Cancel Digit PID.

• Type value 225 -- Cause Indicator PID.

• Type value 226 -- CG Encountered PID.

• Type value 227 -- Charging Event PID.

• Type value 228 -- Collected Information PID.

• Type value 229 -- Collected Information Specific Info PID.

• Type value 230 -- Control Type PID.

• Type value 231 -- Correlation ID PID.

• Type value 232 -- Counter and Value PID.

• Type value 233 -- Counter ID PID.

• Type value 234 -- Counter Value PID.

• Type value 235 -- Counters Value PID.

• Type value 236 -- Cut and Paste PID.

• Type value 237 -- Date PID.

• Type value 238 -- Date and Time PID.

• Type value 239 -- Destination Routing Address PID.

• Type value 240 -- Digits PID.

• Type value 241 -- Digits Response PID.

• Type value 242 -- Disconnect from IP not permitted PID.

EIN315 279


NN10275-909v14 12.01 06 October 2011


• Type value 243 -- Display Information PID.

• Type value 244 -- DP Specific Criteria PID.

• Type value 245 -- Duration PID.

• Type value 246 -- Durationfto PID.

• Type value 247 -- Elementary Message ID PID.

• Type value 248 -- Elementary Message IDS PID.

• Type value 249 -- End of Reply Digit PID.

• Type value 250 -- Error Treatment PID.

• Type value 251 -- Event Specific Information BCSM PID.

• Type value 252 -- Event Specific Info Charging PID.

• Type value 253 -- Event Type BCSM PID.

• Type value 254 -- Event Type Charging PID.

• Type value 255 -- Extensions PID.

• Type value 256 -- FCI Billing Charging Characteristics PID.

• Type value 257 -- Filtered Call Treatment PID.

• Type value 258 -- Filtering Characteristics PID.

• Type value 259 -- Filtering Criteria PID.

• Type value 260 -- Filtering Time Out PID.

• Type value 261 -- First Digit Time Out PID.

• Type value 262 -- Forward Call Indicators PID.

• Type value 263 -- Gap Criteria PID.

• Type value 264 -- Gap On Service PID.

• Type value 265 -- Gap Indicators PID.

• Type value 266 -- Gap Interval PID.

• Type value 267 -- Gap Treatment PID.

• Type value 268 -- Higher Layer Compatibility PID.

• Type value 269 -- INband Information PID.

• Type value 270 -- Information to Send PID.

• Type value 271 -- Integer PID.

• Type value 272 -- Inter Digit Time-Out PID.

• Type value 273 -- ANN IND PID that can be interrupted.

• Type value 274 -- Interval PID.



NN10275-909v14 12.01 06 October 2011


• Type value 275 -- Cause ID PID.

• Type value 276 -- IP Available PID.

• Type value 277 -- IP Routing Address PID.

• Type value 278 -- IP SSP Capabilities PID.

• Type value 279 -- Leg ID PID.

• Type value 280 -- Leg Type PID.

• Type value 281 -- Location Number PID.

• Type value 282 -- Operation that is not supported.

• Type value 283 -- Maximum Number of Counters PID.

• Type value 284 -- Maximum Number of Digits PID.

• Type value 285 -- Message Content PID.

• Type value 286 -- Message ID PID.

• Type value 287 -- Message Type PID.

• Type value 288 -- Minimum Number of Digits PID.

• Type value 289 -- Miscellaneous Call Information PID.

• Type value 290 -- Monitor Mode PID.

• Type value 291 -- None PID.

• Type value 292 -- Null PID.

• Type value 293 -- Number PID.

• Type value 294 -- Number of Calls PID.

• Type value 295 -- Number of Digits PID.

• Type value 296 -- Number of Repetitions PID.

• Type value 297 -- 0 Called Party Busy Specific Info PID.

• Type value 298 -- 0 Answer Specific Info PID.

• Type value 299 -- 0 Disconnect Specific Info PID.

• Type value 300 -- 0 Midcall Specific Info PID.

• Type value 301 -- 0 No Answer Specific Info PID.

• Type value 302 -- Party to Charge PID.

• Type value 303 -- Price PID.

• Type value 304 -- Receiving Side ID PID.

• Type value 305 -- Release Cause PID.

• Type value 306 -- Release Cause Value PID.

EIN315 281


NN10275-909v14 12.01 06 October 2011


• Type value 307 -- Request Announcement Complete PID.

• Type value 308 -- Requested Information List PID.

• Type value 309 -- Requested Information Type List PID.

• Type value 310 -- Requested Information PID.

• Type value 311 -- Requested Information Type PID.

• Type value 312 -- Requested Information Value.

• Type value 313 -- Resource Address PID.

• Type value 314 -- Route List PID.

• Type value 315 -- Route Select Failure Specific Info PID.

• Type value 316 -- SCF ID PID.

• Type value 317 -- SCI Bill Charge Characteristics PID.

• Type value 318 -- Parameter that is not supported.

• Type value 319 -- Send Calc to SCP Indication PID.

• Type value 320 -- Sending Side ID PID.

• Type value 321 -- Service Interaction Indicators PID.

• Type value 322 -- Service Key PID.

• Type value 323 -- SF Billing Charging Characteristics PID.

• Type value 324 -- Start Time PID.

• Type value 325 -- Start Digit PID.

• Type value 326 -- Stop Time PID.

• Type value 327 -- T Answer Specific Info PID.

• Type value 328 -- T Called Party Busy Specific Info PID.

• Type value 329 -- T Disconnect Specific Info PID.

• Type value 330 -- T Midcall Specific Info PID.

• Type value 331 -- T No Answer Specific Info PID.

• Type value 332 -- Task Refused ID.

• Type value 333 -- Text PID.

• Type value 334 -- Time PID.

• Type value 335 -- Timer ID PID.

• Type value 336 -- Timer Value PID.

• Type value 337 -- Tone PID.

• Type value 338 -- Tone ID PID.



NN10275-909v14 12.01 06 October 2011


• Type value 339 -- Network Resource ID not available.

• Type value 340 -- Variable Message PID.

• Type value 341 -- Variable Part PID.

• Type value 342 -- Variable Parts PID.

• Type value 343 -- Voice Back PID.

• Type value 344 -- Voice Information PID.

• Type value 345 -- FCI2 PID.

• Type value 346 -- FCI AMA Modify PID.

• Type value 347 -- FCI AMA Append PID.

• Type value 348 -- FCI AMA Delete PID.

• Type value 349 -- FCI AMA Open PID.

• Type value 350 -- FCI AMA Clear PID.

• Type value 351 -- FCI AMA Billing Data Item PID.

• Type value 352 -- FCI AMA FreeForm PID.

• Type value 353 -- FCI AMA IN Service ID PID.

• Type value 354 -- FCI AMA Calling Line ID PID.

• Type value 355 -- FCI AMA Dialed Digits PID.

• Type value 356 -- FCI AMA Alternate Billing Number PID.

• Type value 357 -- FCI AMA Authorization Code PID.

• Type value 358 -- FCI AMA Account Code PID.

• Type value 359 -- FCI AMA Call Characteristic PID.

• Type value 360 -- FCI AMA Trunk Information PID.

• Type value 361 -- FCI AMA Customer Group ID PID.

• Type value 362 -- FCI AMA Orig Billing Aggregate Group PID.

• Type value 363 -- FCI AMA Term Billing Aggregate Group PID.

• Type value 364 -- FCI AMA Data Descriptor PID.

• Type value 365 -- FCI AMA Network Operator Data PID.

• Type value 366 -- FCI AMA Trunk Group PID.

• Type value 367 -- FCI AMA Trunk Group Member PID.

• Type value 368 -- FCI AMA Context ID PID.

• Type value 369 -- FCI AMA ID PID.

• Type value 370 -- Extension PID.

EIN315 283


NN10275-909v14 12.01 06 October 2011


• Type value 371 -- Extension Field TYPE PID.

• Type value 372 -- Extension Field CRITICALITY PID.

• Type value 373 -- Extension Field VALUE PID.

• Type value 374 -- Connect Extension NCOS PID.

• Type value 375 -- Connect Extension Customer Group PID.

• Type value 376 -- Connect Extension Tone Burst.

• Type value 377 --<Reserved for Expansion of Extensions>

• Type value 378 -- CIRQ Extension Add Info Type List PID.

• Type value 379 -- CIRQ Extension Add Info Type PID.

• Type value 380 -- CIRP Extension Add Info List PID.

• Type value 381 -- CIRP Extension Add Info PID.

• Type value 382 -- CIRP Extension Add Info Type PID.

• Type value 383 -- CIRP Extension Add Info Value PID.

• Type value 384 -- CIRP Extension Trunk CLLI Value PID.

• Type value 385 -- CIRP Extension Trunk Member Value PID.

• Type value 386 -- Requested Info Error PID.

• Type value 387 -- Extension IN Business Group PID.

• Type value 388 -- IN Business Group Party Selector PID.

• Type value 389 -- IN Business Group Bus Grp ID PID.

• Type value 390 -- IN Business Group Sub Group ID PID.

• Type value 391 -- IN Business Group Line Priv Info PID.

• Type value 392 -- IN Business Group Attendant Status PID.

• Type value 393 -- Bus Grp ID BGIDTP PID.

• Type value 394 -- Bus Grp ID Business Group ID PID.

• Type value 395 -- LPI Line Priv Info Ind PID.

• Type value 396 -- LPI Line Privileges PID.




• Type value 400 -- ASN ASF Billing Charging Characteristics PID.



NN10275-909v14 12.01 06 October 2011


Remedial actionACTION DESCRIPTION VALUES:

• Type value 0 -- Nil Action.

• Type value 1 -- Check SVC Oper, SCP Comms and TSSF OfficeParms.

• Type value 2 -- Check SVC Oper, SCP Comms and TSRF OfficeParms.

• Type value 3 -- Check Communication to/or the State of the SCP.

• Type value 4 -- Check Service Operation.

• Type value 5 -- Check for Error at the SCP.

• Type value 6 -- Check for problems with DGT RX equipment on DMS.

• Type value 7 -- Analyze if this occurs often.

• Type value 8 -- Check for problem with Tone/Anoncmnt equipment inOffice.

• Type value 9 -- Check for problem with Tone/Anoncmnt Equipment inOffice.

• Type value 10 -- Report Billing problem to next line of support.

• Type value 11 -- This function is NOT supported.

• Type value 12 -- Non IN function is NOT supported.

• Type value 13 -- Check Service Info datafill for this IN service.

• Type value 14 -- Possible SCP Error/Contact next line of support.

• Type value 15 -- Visit again SCP serv logic or DMS translations fortemporary connection.

• Type value 16 -- Monitor for function to start again.

• Type value 17 -- Check INBGCUST datafill for this IN service.

• Type value 18 -- Check Table AINANNS or check for problems withDGT equipment.

• Type value 19 -- Check Trigger Datafill and report to next line ofsupport.


Severity Critical

FormatUKC9004BI ** EIN315 JUL06 15:09:30 2800

EIN315 285


NN10275-909v14 12.01 06 October 2011


Location: Service Filtering (NCR)

Status: Trouble Alert

Trouble: <TROUBLE DESCRIPTION>

Action: <ACTION DESCRIPTION>




ParameterValue/Digits:


VariableDescription

Location Service Filtering(NCR)

Variable Location. This field identifies that theService Filtering non-call-relatedfunction generated the problem log.

Status Trouble Alert Variable Status. This field identifies the statusof the problem item.

Trouble Refer to TROUBLE IDDESCRIPTIONS.

Variable This field describes the problem.

Action Refer to ACTION IDVALUES.

Variable This field describes the actions for theproblem description.

Reason Refer to REASON IDDESCRIPTIONS.

Variable This field provides the cause for theproblem description.

Operation ID Refer to OPERATIONID DESCRIPTIONS.

Variable This field contains the OperationIDtext. This field depends on the INAPoperation GAME processes.

ParameterID Refer toPARAMETER IDDESCRIPTIONS.

Variable This field contains the ParameterIDtext. This field depends on the INAPoperation GAME processes.

Parameter Value/Digits

Numeric, maximum30 digits.

Variable This field contains thecalledAddressValue parameter of theActivateServiceFiltering operation.This parameter invokes the servicefiltering instance for which thesubsystem generates the log. Thedigits are compared against thetranslated dialed digits that enter todetermine if the call must be filtered.



NN10275-909v14 12.01 06 October 2011


Active message exampleUKC90071CB EIN315 JUN04 15:53:29 9308 TBL NCR

Location: Service Filtering (NCR)

Status: Trouble Alert

Trouble: Problem with an IN Service

Action: Report the Problem to the Next Line of Support

Reason: Parameter Out of Range

OperationID: Activate Service Filtering ID

ParameterID: Tone ID PID

ParameterValue/Digits: 3



EIN601This is a trouble log generated by certain events occurring in the ActivateService Filtering (ASF) functionality of the DMS-100 SSP.

The following information provides type values and the associated actiondescriptions:

• Type value 0 -- ASF Received

• Type value 1-- ASF New Parameter Set Received

• Type value 2 -- ASF Started

• Type value 3 -- ASF Restarted

• Type value 4 -- ASF Stop Time Reached

• Type value 5 -- ASF Stopped By Request

• Type value 6 -- ASF Filtering Timeout Invalid

• Type value 7 -- ASF Data Table Full

• Type value 8 -- ASF Entry Removed from Full ASF Data Table

• Type value 9 -- ASF Entry Removed by Audit

EIN601 287


NN10275-909v14 12.01 06 October 2011


• Type value 10 -- ASF Called Address Value Overlap

• Type value 11 -- ASF Start Treatment

Remedial actionn/a


Severity Warning

FormatUKC9004BI ** EIN601 JUL06 15:09:30 2800

Location: Service Filtering (ASF)

Reason: <ASF_LOG_REASON_TYPE>

CalledAddressValue: <CALLED_ADDRESS_VALUE_DIGITS>

ServiceKey: <SERVICE_KEY_DIGITS>


VariableDescription

Location Service Filtering(ASF)

Variable This field indicates the log has beengenerated by events in the ServiceFiltering (ASF) functionality.

Reason String Variable This field indicates the ASF eventwhich caused the log to be generated.

CalledAddressValue 18 digits maximum Variable This field contains the Called-Address-Value supplied in the ASFoperation.

ServiceKey 4 digits maximum Variable This field contains the Service-Keyvalue supplied in the ASF operation.

Active message exampleUKC90071BY EIN601 MAY16 14:53:02 1700 INFO ASF

Location: Service Filtering (ASF)

Reason: ASF Started

CalledAddresValue: 8104008



NN10275-909v14 12.01 06 October 2011


ServiceKey: 9



EIN602The EIN602 log report provides information about events occurring in theCall Gapping functionality of the DMS-100 SSP

The log provides a reason and indicates the gap criteria that applied to theCall Gapping instance that generated the log.

Remedial actionNone EIN602 is an information log only.


Severity Critical

FormatLocation: CallGap (CG)

Reason: <reason>

GapCriteria <GapCriteria>

AddressValue: <AddressValue>

ServiceKey: <ServiceKey>

EIN602 289


NN10275-909v14 12.01 06 October 2011



VariableDescription

AdressValue 1 to 18 digits Variable This field indicates the called or callingaddress value being used as a gapcriterion by the Call Gapping instancethat generated the log. Refer to theGapCriteria field to determine if thecalled or calling address value is usedas a gap criterion.

This field is blank if GapOnService isused.

ServiceKey 0 to 2147483647 Variable This field indicates the value of theservice key used as a gap criterion bythe Call Gapping instance thatgenerated the log.

If the ServiceKey field is notapplicable to the type of GapCriteriabeing applied (CalledAddressValue),this field is blank to indicate that it isnot initialized (and therefore unused).

Location Constant Fixed This field indicates that the EIN602 logis concerned with the Call Gappingfunctionality.

Reason Symbolic text Variable This field provides an explanation ofwhy the log was generated.

GapCriteria Symbolic text Variable This field indicates the value of thegapCriteria parameter of the CallGapping operation.

Active message exampleLocation: CallGap (CG)

Reason: CallGap Applied

GapCriteria: CallingAddressAndService

AddressValue: 1628787120

ServiceKey: 9999




NN10275-909v14 12.01 06 October 2011



EIN603The EIN603 log report provides information on events occurring in theService Profiling functionality of the DMS-100 SSP.

Remedial actionNone. EIN603 is an information log only.



FormatLocation: Service Profiling

Reason: <reason>


VariableDescription

Location Constant Fixed This field indicates that the EIN603 logis generated by the Service Profilingfunctionality.

Reason Symbolic text Variable This field shows the reason why thelog report was generated.

Active message exampleLocation: Service Profiling

Reason: Failed To Restore Tuple In TRIGDIG: SK

Mandatory When Gtsrouce DFLT



EMD100The Excessive Metering subsystem log report EMD100 is generated whena subscriber is detected whose meter counts reach or exceed a thresholdvalue in a time period.

EMD100 291


NN10275-909v14 12.01 06 October 2011


Remedial actionn/a


Severity Warning

FormatEMD100 mmmdd hh:mm:ss ssdd INFO EXCESSIVE METERING

<cpid>

Reason: <rsn>

Previous date: yyyy/mm/dd hh:mm:ss

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

METER NAME WRP1 COUNT1 WRP2 COUNT2 DELTA

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

<mtrnm> <wrp> <cnt> <wrp> <cnt> <dlt>

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

Threshold: <thr> Total delta: <tdlt>


VariableDescription

INFO EXCESSIVEMETERING

Constant Fixed Indicates that a subscriber whosemeter counts are increased by morethan a threshold value in a time periodis detected.

cpid Symbolic text Variable Identifies a LINE CP_ID.

Reason: PERIODIC, BILLING,OOS or WRAP

Variable Indicates the reason for thegeneration of the log.

Previous date: Alphanumeric Variable The copy date for the meter blocks.

METER NAME Character string Variable Indicates a valid meter name.

WRP1 YES, NO or **** Variable Wrap information for the copied meter.

COUNT1 00 000 000 to 99 999999 or ********

Variable Count information for the copiedmeter.



NN10275-909v14 12.01 06 October 2011



Description

WRP2 YES, NO or **** Variable Wrap information for the currentmeter.

COUNT2 00 000 000 to 99 999999 or ********

Variable Count information for the currentmeter.

DELTA 0 000 000 000 to 0199 999 998 or**********

Variable Difference between the previous countand the current count for that meter.

Total delta: 0 000 000 000 to 0799 999 992

Variable Indicates the total of all meter deltasfor that subscriber.

Threshold 0 to 0 799 999 992 Variable Indicates the threshold for thecomparison.

Active message exampleEMD100 JUN10 18:10:12 1367 INFO EXCESSIVE METERING

HOST 01 0 10 09 DN 7835489

Reason: PERIODIC

Previous date: 2000/08/12 18:05:10

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


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

FEATURE **** ******** **** ******** ********

LOCAL NO 00000012 NO 00000045 0000000033

TOLL NO 99999999 YES 00000009 0000000010

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

Threshold: 0000000020 Total delta: 0000000043


EMD100 293


NN10275-909v14 12.01 06 October 2011



EMD101The Excessive Trunk Metering log report EMD101 is generated when asubscriber is detected whose meter counts are increased by more than athreshold value in a time period.

Remedial actionn/a


Severity Warning

FormatEMD101 mmmdd hh:mm:ss ssdd INFO EXCESSIVE TRUNK METERING

<clli>

Reason: <rsn>

Previous date: yyyy/mm/dd hh:mm:ss

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


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

<mtrnm> <wrp> <cnt> <wrp> <cnt> <dlt>

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

Threshold: <thr> Total delta: <tdlt>


VariableDescription

EXCESSIVEMETERING FORTRUNKS

Constant Fixed Indicates that a trunk agent whosemeter counts are increased by morethan a threshold value in time periodis detected.

CLLI Symbolic text Variable Identifies CLLI of a trunk.



NN10275-909v14 12.01 06 October 2011



Description

Reason: PERIODIC, BILLING,OOS or WRAP

Variable Indicates the reason for thegeneration of the log.

Previous date: Alphanumeric Variable The copy date for the meter blocks.

METER NAME Character string Variable Indicates a valid assigned metername.


COUNT1 0000 0000 0000 -9999 9999 9999 or************



COUNT2 0000 0000 0000 -9999 9999 9999 or************


DELTA 0 0000 0000 0000 -1.999.999.999.998 or**********

Variable Difference between the previous countand the current count for that meter.

Total delta: 0 0000 0000 0000-7.999.999.999.992

Variable Indicates the total of all meter deltasfor that subscriber.

Threshold 0 0000 0000 0000-7.999.999.999.992

Variable Indicates the threshold for thecomparison.

Active message exampleEMD101 JUN10 18:10:12 1367 INFO EXCESSIVE TRUNK METERING

CLLI : ICPRIBA

Reason: PERIODIC

Previous date: 2000/08/12 18:05:10

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


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

TLOCAL NO 00000012 NO 00000045 0000000033

TTOLL NO 99999999 YES 00000009 0000000010

TINTL NO ******** *** ******** **********

EMD101 295


NN10275-909v14 12.01 06 October 2011


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

Threshold: 0000000020 Total delta: 0000000043



ESV120In a condition where a Japan Emergency Services (JES) call is made froman extension on a PBX connected to the DMS-100 system through a T1CAS trunk connected to a channel bank, and the originator hangs-up. TheJES operator tries to re-ring the subscriber and the BILLDN field datafill intable TRKGRP for T1 trunk is N. A re-ring to the PBX attendant is notpossible.

Remedial actionDetermine the DN that terminates on the attendant on the PBX. Datafill thisDN in the BILLDN field in table TRKGRP for the outgoing trunk accepted inthe ESV120 log.


Severity Warning

FormatESV120 mmmdd hh:mm:ss nnnn INFO DATAFILL NOT FOUND

<DESC OF CHAR> IS NOT DATAFILLED

CALLING PARTY : <cp_id>

OUTGOING TRUNK : <cp_id>


VariableDescription

cp_id (incoming) CKT CLLI nnnn Variable The incoming trunk stored in port 1 ofthe CCB of the JES re-ring call.

cp_id (outgoing) CKT CLLI nnnn Variable The outgoing trunk stored in port 2 ofthe CCB of the JES re-ring call.



NN10275-909v14 12.01 06 October 2011


Active message exampleESV120 SEP05 18:14:33 4827 INFO DATAFILL NOT FOUND

BILLDN IS NOT DATFILLED

CALLING PARTY : CKT WCTK1DE04CAS12 1

OUTGOING TRUNK : CKT FPTPLC1 3



FEAT400FEAT400 is generated when PBXA DPNSS route optimisation cannot beinitiated due to:

• Unavailability of a free Feature Data Block (FDB)

• Unavailability of an unused ROPID

Both of these requirements are essential to the operation of PBXA DPNSSroute optimization.

The report is produced once for every ten calls denied PBXA DPNSS routeoptimization due to unavailability of the above requirements.

The report contains the total number of calls denied PBXA DPNSS routeoptimization since the last successful attempt.

Remedial actionn/a



FormatFRES400 <mmm><dd> <hh>: <mm>: <ss> <nnnn> FBD/ROPID

UNAVAILABLE

8 blks>FAIL_COUNT: <nnn>

FEAT400 297


NN10275-909v14 12.01 06 October 2011



VariableDescription

FAIL_COUNT 10 to 990 Variable The number of feature initiationattempts denied since the lastsuccessful initiation.

Active message examplen/a



FPS100This log is generated when a subscriber''s FPS counter is loaded (creditedwith units). Subscriber''s FPS counters can be loaded in three ways:

• Using the LOAD command under the LFPS sublevel of the FPScommand interface (CI) level

• By assigning FPS to lines using the ADO command in SERVORD

• By adding an FPS tuple to table IBNFEAT

Log history

ISN06 (TDM)

Log FPS100 added for activity A89007209.

Remedial actionFPS100 is an information log and so requires no immediate action.


Severity Warning

Format** FPS100 <mmmdd hh:mm:ss ssdd> INFO FPS COUNTER LOADED

LOADED DN : <Directory Number> LOADED WITH :<FPS Limit>

LOADED BY : <User Name> LOAD TYPE : <Load type>



NN10275-909v14 12.01 06 October 2011



VariableDescription

Loaded DN Directory Number Variable The directory number of the loadedFPS subscriber

Loaded by Username Variable The login name of the user whoperformed the load

Loaded with FPS1, FPS2 Variable Predefined number of credits loadedto the subscriber's account. Definedby FPS_CREDIT_LIMIT1 andFPS_CREDIT_LIMIT2 in theOFCENG office parameters table

Load type LOAD Command,New Assignment

Variable The FPS counter can be loaded by:

• The LOAD Command in the LFPSsublevel of the FPS Cl level

• A New Assignment usingSERVORD to allocate the FPSfeature to the line,

• By adding an FPS tuple to tableIBNFEAT

Active message example** FPS100 APR03 13:40:13 0100 INFO FPS COUNTER LOADED

LOADED DN: 8694658002 LOADED WITH : FPS1

LOADED BY: CMAP18 LOAD TYPE : NEW FPS ASSIGNMENT



FRB100The FRB10 log is generated when the Faultsman''s Ring Back featureterminates unsuccessfully. The feature is unsuccessful when no on-hooksignal is received before the SIT (acknowledgement tone) times out.

Remedial actionThis report is for information only. No action is to be taken.

FRB100 299


NN10275-909v14 12.01 06 October 2011



Severity Warning

FormatFRB100 <DATE> <TIME> <SEQNO> INFO UNSUCCESSFUL TERM. OF FRB


VariableDescription

Date 3 characters formonth and 2 digit forday

Variable Date of log generation.

TIME 6 digit<hh:mm:ss> Variable Time of log generation.

SEQNO 4 digit number Variable Generation sequence number of thereport.

Active message exampleFRB100 JAN17 21:26:30 7000 INFO UNSUCCESSFUL TERM. OF FRB



IBN134An IBN134 log is generated when the Insert National Numbering Group(INSNNG) option, datafilled in field NETRTOPT in table IBNXLA or tableXLANAME, fails to perform a digit manipulation function.

The log means that INSNNG digit prefixing has failed. Associated callsmay have gone to treatment if translations could not continue on theunchanged numbers.

Remedial actionConfirm the datafill error by using the TRAVER utility. For INSNNG failureson the second leg of two-stage translations, for example, MONA, DISA,call forwarding, or VFGs, the Calling Party field of the IBN134 log maycontain the feature/agent being translated from. Otherwise, the actual calloriginator (or first leg originator) information is provided.



NN10275-909v14 12.01 06 October 2011


If the log was generated from attempting to use INSNNG with anunsupported originator type, alter the translations for that originator so thatsuch translations do not require the INSNNG option.

If logs appear because of an INSNNG datafill error, the INSNNG number toprefix value should be altered. Check table DNGRPS for the originatingagent to ensure that the desired results are being achieved.

For logs generated because of hexadecimal digits being provided as prefixdigits by table DNGRPS formatting, alter table DNGRPS formatting to usetranslation digits 0 to 9.



FormatIBN134 mmmdd hh:mm:ss ssdd TBL IBNXLA INSNNG DATA ERROR

TYPE = <problem type>

CALLING PARTY = LEN <len> <dn>

DIALED DIGITS = <digits>

CALL_JD = <callid>


VariableDescription

IBNXLA INSNNGDATA ERROR

Constant Fixed Indicates an error arising from optionINSNNG in table IBNXLA.

problem type Symbolic text Variable Indicates the type of problem. Errorsare:

INSNNG FAILED TOGET DN OF ORIGIN

Variable An INSNNG attempt to retrieve adirectory number for the agent beingtranslated from has failed. Thetranslation may not be supported--forexample, an attempt was made totranslate from a Virtual Facility Group(VFG) or to retranslate with the RXselector.

IBN134 301


NN10275-909v14 12.01 06 October 2011



Description

INSNNGTRANSLATIONSDIGITS EXCEEDMAX

Variable The digit prefixing attempted by theINSNNG option would produce anumber with too many digits.

INSNNG PREFIXNUM EXCEEDSORIGIN DN

Variable The specified number of INSNNGdigits to prefix to the dialed numberexceeds the number of digits availablein the originator's directory number.

INSNNG RECEIVEDHEX DIGITS FROMDNGRPS

Variable Table DNGRPS formatting of anoriginating DN results in prefix digitscontaining hexadecimal digits.

len numeric Variable Identifies the agent from which the calloriginated.

dn numeric Variable Identifies the agent from which the calloriginated.

digits numeric Variable Specifies the digits being translated.

callid alphanumeric Variable Specifies the call identifier.

Active message exampleIBN134 MAY11 11:29:45 6600 TBL IBNXLA INSNNG DATA ERROR

TYPE INSNNG TRANSLATIONS DIGITS EXCEED MAX

CALLING PARTY LEN HOST 0 0 5 0 1818114013

DIALED DIGITS 128114006

CALL_ID 885139



IBN138Log IBN138 (CLI Screening via Translations Failure) indicates that therehas been a failure while performing CLI Screening via Translations.

Remedial actionNo immediate action is required when log IBN138 is generated.



NN10275-909v14 12.01 06 October 2011



Severity Warning

FormatIBN138 mmmdd hh:mm:ss ssdd INFO CLI SCRN FAILURE

TYPE: CLI SCREENING VIA TRANSLATIONS FAILURE

REASON: <failure reason>

SERVICE: <service name>

ADDRESS: <address screened>

CALLID: <callid>

NPI: <NPI>

NOA: <NOA>


VariableDescription

REASON failure reason Variable The reason for the failure.

SERVICE Valid SERVNAMEfrom table CLISERV

Variable The SERVNAME from table CLISERVused by the call.

ADDRESS CLI, REDIRECTING,CHARGE,CONTRACTOR,GENERIC,PRESENTATION

Variable The address which is screened.

CALLID Call id Variable The call id.

NPI E164, UNKN Variable The Numbering Plan Indicator of theselected address.

NOA SUBSCRIBER,NATIONAL,INTERNATIONAL,UNKNOWN

Variable The Nature of Address of the selectedaddress.

Active message exampleIBN138 APR21 03:20:18 4685 INFO CLI SCRN FAILURE

TYPE: CLI SCREENING VIA TRANSLATIONS FAILURE

IBN138 303


NN10275-909v14 12.01 06 October 2011


REASON: FAILED CLI MATCH

SERVICE: SERVI

ADDRESS: REDIRECTING

CALLID: 32813

NPI: E164

NOA: NATIONAL



INH105The system generates this log when a user activates the INHIBITcommand.

Remedial actionThis log is an information log and does not require immediate action.


Severity Warning

FormatINH105 mmmdd hh:mm:ss ssdd INFO INHIBIT ON

USER: <USERNAME>

TERMINAL: <TERMINAL_ID>


VariableDescription

DATE alphanumeric string Variable This field indicates the date thesystem generated the log.

TIME numeric string Variable This field indicates the time the useractivated the INHIBIT command andthe system generated the log.



NN10275-909v14 12.01 06 October 2011



Description

SEQNO numeric (four digits) Variable This field indicates the generationsequence number of the log.

USER alphanumeric string Variable This field indicates the login name ofthe user.

TERMINAL_ID alphanumeric string Variable This field indicates the terminal deviceon which the user activated theINHIBIT command.

Active message exampleINH105 MAY08 10:15:40 5100 INFO INHIBIT ON

USER: ADMIN

TERMINAL: TTY18



ISDN310The DMS-100 MMP switch generates the ISDN310 log when messagereassembly or segmentation for a PRI ISDN variant fails. Failure can occurin the following situations:

• There is too much segmented data to send from Computing Module(CM) to the Extended Peripheral Module (XPM). The CM cannotdetermine the exact maximum payload that can be carried in theoutgoing ISDN message. This log is generated only if the payload isabout 300 bytes higher than the maximum payload of a segmentedISDN message.

• The sanity timer times out before reassembly is complete. The sanitytimer is an internal CM timer that does not require datafill. The sanitytimer determines the time allowed to receive a maximum-sizesegmented message that has a maximum number of segments. Thetime-out period of the sanity timer is 60 seconds.

• A segmented message is expected but a nonsegmented message isreceived.

• A reassembly error is detected.

ISDN310 305


NN10275-909v14 12.01 06 October 2011


The DMS-100 MMP switch generates the ISDN310 log in this situation onlyif the error has not already been detected by the XPM.

• The received segmented message type is incorrect.

• The received sequence number is incorrect.


The results in the log report can be:

• Segments Discarded

• Call Released

Remedial actionThe DMS-100 MMP switch typically generates the ISDN310 log whenerrors occur in the transfer of segmented messages from a remote privateintegrated network exchange (PESTX) to a DMS-100 MMP member. Thetrunk member to which the segmented messages are sent is indicated inthe log in field CKT.

Repeated occurrences of the log can indicate a software malfunction at theremote PINX. If repeated occurrences of the log occur, arrange forpersonnel at the remote PINX and at the DMS-100 MMP switch to capturemessage traces for the affected D-channel or call. These call traces can beused to analyze the problem.


Severity Warning

FormatISDN310 mmmdd hh:mm:ss ssdd INFO Reassembly/SegmentationError

CKT:<CPID of the trunk member or D-channel failure occurredon>

Call ID: <The Call ID number>

ERROR TYPE <Type of Error>

RESULT: <Action taken>



NN10275-909v14 12.01 06 October 2011



VariableDescription

CPID Defined CPIDs Variable The call processing identifier of thetrunk member or D-channel on whichfailure occurred.

CaIIID Call ID as two-parthexadecimal value

Variable The call ID number.

Error 50 bytes of text errormessage

Variable The type of error that occurred. Thepossible errors are:

• Received Sequence NumberIncorrect

• Received Message Type Incorrect

• Cannot Reassemble Data

• Segmented Message Expected

• Reassembly Sanity Timer Expired

• Too Much Segmented Data ToSend

Result Segments Discarded,or Call Released

Variable Action taken.

Received A defined Q931message type

Variable The segmented ISDN Q931 messagetype that the CM just received. NONEindicates that no message wasreceived. No message is received if,for example, the reassembly timertimes out.

Sequence# 0 to 15 Variable The sequence number of the segmentthat the CM just received.

Last A defined Q931message type

Variable The segmented Q931 ISDN messagetype that the CM previously received.

Sequence # 0 to 15 Variable The sequence number of the segmentthat the CM previously received.

Active message exampleTCB3_LOG ISDN310 OCT13 19:14:36 6600 INFO Reassembly/Segmentation Error

CKT CRES12QSIG 7

Call ID: #97AF #FE53

ERROR: Too Much Segmented Data To Send

ISDN310 307


NN10275-909v14 12.01 06 October 2011


RESULT: Segments Discarded



ISDN310 Format 2The DMS-100 MMP switch generates the ISDN310 log when messagereassembly or segmentation for a PRI ISDN variant fails. Failure can occurin the following situations:

• There is too much segmented data to send from Computing Module(CM) to the Extended Peripheral Module (XPM). The CM cannotdetermine the exact maximum payload that can be carried in theoutgoing ISDN message. This log is generated only if the payload isabout 300 bytes higher than the maximum payload of a segmentedISDN message.

• The sanity timer times out before reassembly is complete. The sanitytimer is an internal CM timer that does not require datafill. The sanitytimer determines the time allowed to receive a maximum-sizesegmented message that has a maximum number of segments. Thetime-out period of the sanity timer is 60 seconds.

• A segmented message is expected but a nonsegmented message isreceived.

• A reassembly error is detected.


• The received segmented message type is incorrect.

• The received sequence number is incorrect.


The results in the log report can be:

• Segments Discarded

• Call Released



NN10275-909v14 12.01 06 October 2011


Remedial actionThe DMS-100 MMP switch typically generates the ISDN310 log whenerrors occur in the transfer of segmented messages from a remote privateintegrated network exchange (PESTX) to a DMS-100 MMP member. Thetrunk member to which the segmented messages are sent is indicated inthe log in field CKT.

Repeated occurrences of the log can indicate a software malfunction at theremote PINX. If repeated occurrences of the log occur, arrange forpersonnel at the remote PINX and at the DMS-100 MMP switch to capturemessage traces for the affected D-channel or call. These call traces can beused to analyze the problem.


Severity Warning

FormatISDN310 mmmdd hh:mm:ss ssdd INFO Reassembly/SegmentationError

CKT:<CPID of the trunk member or D-channel failure occurredon>

Call ID: <The Call ID number>

ERROR: <Type of Error>

RESULT: <Action taken>

RECEIVED: <Received ISDN MSG Type> SEQUENCE # <Received SeqNo.>

LAST: <Last ISDN MSG Type> SEQUENCE #<Last Seq No>


VariableDescription

CPID Defined CPIDs Variable The call processing identifier of thetrunk member or D-channel on whichfailure occurred.

CaIIID Call ID as two-parthexadecimal value

Variable The call ID number.

ISDN310 Format 2 309


NN10275-909v14 12.01 06 October 2011



Description

Error 50 bytes of text errormessage

Variable The type of error that occurred. Thepossible errors are:

• Received Sequence NumberIncorrect

• Received Message Type Incorrect

• Cannot Reassemble Data

• Segmented Message Expected

• Reassembly Sanity Timer Expired

• Too Much Segmented Data ToSend

Result Segments Discarded,or Call Released

Variable Action taken.

Received A defined Q931message type

Variable The segmented ISDN Q931 messagetype that the CM just received. NONEindicates that no message wasreceived. No message is received if,for example, the reassembly timertimes out.

Sequence# 0 to 15 Variable The sequence number of the segmentthat the CM just received.

Last A defined Q931message type

Variable The segmented Q931 ISDN messagetype that the CM previously received.

Sequence # 0 to 15 Variable The sequence number of the segmentthat the CM previously received.

Active message exampleTCB3_LOG ISDN310 OCT13 19:14:36 6400 INFO Reassembly/Segmentation Error

CKT CRES12QSIG 7

Call ID: #97AF #FE53

ERROR: Reassembly Sanity Timer Expired

RESULT: Call Released

Received: NONE Sequence #0

Last : FACILITY Sequence #4



NN10275-909v14 12.01 06 October 2011




ITN202The InTerNet (ITN) subsystem generates log report ITN202. Thesubsystem generates ITN202 when the subsystem receives a connectionrequest from a peer transmission control protocol (TCP). The connectionrequest is for a local port that is not present in the system. The systemsends a RESET TCP segment back to the peer TCP.

Remedial actionThere are no manual actions required. Note the source host addresses ofbad peer TCP users.


Severity Warning

FormatITN202 mmmdd hh:mm:ss ssdd INFO NO MATCHING PORT FOR

RECEIVED

TCP CONN REQUEST

NODE: nodeid

ACTION: tcpaction

LOCAL TCP PORT: portnum LOCAL IP: aa.bb.cc.dd

REMOTE TCP PORT: portnum REMOTE IP: aa.bb.cc.dd

ITN202 311


NN10275-909v14 12.01 06 October 2011



VariableDescription

INFO NO MATCHINGPORT FORRECEIVED TCPCONN REQUESTNODE: nodeid

Symbolic text Variable Indicates the node identifier of theethernet interface unit (EIU) in thecomputing module (CM) ofSupernode. The log originates in theCM of the Supernode.

ACTION: tcpaction Symbolic text Variable Indicates a variable-length characterstring that describes the action thatthe local TCP takes when the logevent occurs.

LOCAL or REMOTETCP PORT: portnum

Unsignedinteger<range 0 to65535>

Variable Indicates the TCP port number of thesource or destination TCP serviceuser.

LOCAL or REMOTEIP: aa.bb.cc.dd

Table<0 to 3>of byte Variable Indicates the internet host address ofthe source or destination service user.

Active message exampleITN202 mmmdd hh:mm:ss ssdd INFO NO MATCHING PORT FOR

RECEIVED

NODE: EIU207

ACTION: RST SEG SENT

LOCAL TCP PORT: 30814 LOCAL IP: 47.36.8.1

REMOTE TCP PORT: 257 REMOTE IP: 98.23.0.3



IWUCWhen an IWUC log is generated, wakeup calls which cannot be completedbecause the subscriber lines are busy or the subscriber does not answerthe wakeup call are displayed.

Remedial actionn/a



NN10275-909v14 12.01 06 October 2011



Severity Warning

FormatTCSB_09BK CM IWUC102 SEP22 <TIME> 5400 INFO wakeup callaborted

<LEN> DN <DN>

WAKEUPTIME : < >, REASON: < >

TCSB_09BK CM IWUC103 SEP22 <TIME> 5400 INFO wakeup callunanswered

<LEN> DN <DN>

WAKEUP TIME : < >

TCSB_09BK CM IWUC104 SEP22 <TIME> 5400 INFO wakeup call nottransferred

<LEN> DN <DN>

WAKEUP TIME : < >


VariableDescription

LEN LEN Variable LEN of the set


Active message exampleTCSB_09BK CM IWUC102 SEP23 16:55:00 1500 INFO wakeup callaborted

HOST 00 0 01 03 DN 1036340103

WAKEUP TIME : 16:59, REASON : LINE RESTRICTIONS

TCSB_09BK CM IWUC103 SEP22 16:16:00 5400 INFO wakeup callunanswered

HOST 00 0 01 03 DN 1036340103

IWUC 313


NN10275-909v14 12.01 06 October 2011


WAKEUP TIME : 16:15

TCSB_09BK CM IWUC104 SEP22 16:16:00 5400 INFO wakeupcall nottransferred

HOST 00 0 01 03 DN 1036340103

WAKEUP TIME : 16:15



LINE124A LINE124 log report is generated for Italian ISDN Standard User Part(ISUP) to line calls when the ETSI ISDN Malicious Call Identification (MID)feature is activated on a connected agent. The format of the log variesdepending upon whether a complete calling line identity (CLI) or a partialCLI is present.

Remedial actionn/a


Severity • Major

• Critical

• Minor

FormatFop mmmdd hh:mm:ss ssdd

Location: <location>

Alarmclass: <alarm>

Calling Agent: <originating user>

Calling Number: <number of originating user>

Called Number: <number of subscribed user>

Last Forwarding Number: <last diverted number>



NN10275-909v14 12.01 06 October 2011


Date: <date>

Time: <time>


VariableDescription

Location string Variable Identifies the switch that generates thelog.

Alarm ***, **, *or blank Variable Indicates the alarm type of the logreport. Three asterisks (***) indicatesa critical alarm. Two asterisks (**)indicate a major alarm. One asterisk(*) indicates a minor alarm. Noasterisk indicates that no alarmappears.

Calling Agent line equipmentnumber (LEN) or CLLIof the trunk

Variable Type of originating user (full CLI only).

Calling Number numeric (0 to 9 digits) Variable Number of originating user (full CLIonly).

Signaling Point Code numeric(0 to 9 digits) Variable Identifies the signaling point (partialCLI only).

Trunk Identity Alphanumeric(up to15 IA characters)

Variable Common language location identifier,giving the logical name of theincoming trunk (partial CLI only).

Called Number numeric(0 to 9 digits) Variable Number of subscribed user.

Last ForwardingNumber

numeric(0 to 9 digits) Variable Last diverted number for callforwarding.

Date numeric(0 to 9 digits) Variable Date

Time numeric(0 to 9 digits) Variable Time of day

Active message example***LINE124 OCT05 10:05:07 1998

LINELOG1

Alarmclass: MAJOR

Cal ling Agent: LEN HOST 1 0 0 2

Calling Number: 222740040

Called Number: 222740041

LINE124 315


NN10275-909v14 12.01 06 October 2011


Last Forwarding Number:

Date: OCT05

Time: 10:05:02



LINE124 Format 2A LINE124 log report is generated for Italian ISDN Standard User Part(ISUP) to line calls when the ETSI ISDN Malicious Call Identification (MID)feature is activated on a connected agent. The format of the log variesdepending upon whether a complete calling line identity (CLI) or a partialCLI is present.

Remedial actionn/a


Severity • Major

• Critical

• Minor


Location: <location>

Alarmclass: <alarm>

Signaling Point Code: <signaling point code>

Trunk Identity: <trkid>

Called Number: <cdli>


Date: <mmmdd>



NN10275-909v14 12.01 06 October 2011


Time: <hh:mm:ss>


VariableDescription


Alarm ***, **, *or blank Variable Indicates the alarm type of the logreport. Three asterisks (***) indicatesa critical alarm. Two asterisks (**)indicate a major alarm. One asterisk(*) indicates a minor alarm. Noasterisk indicates that no alarmappears.

Calling Agent line equipmentnumber (LEN) or CLLIof the trunk

Variable Type of originating user (full CLI only).

Calling Number numeric (0 to 9 digits) Variable Number of originating user (full CLIonly).

Signaling Point Code numeric(0 to 9 digits) Variable Identifies the signaling point (partialCLI only).

Trunk Identity Alphanumeric(up to15 IA characters)

Variable Common language location identifier,giving the logical name of theincoming trunk (partial CLI only).

Called Number numeric(0 to 9 digits) Variable Number of subscribed user.


numeric(0 to 9 digits) Variable Last diverted number for callforwarding.

Date numeric(0 to 9 digits) Variable Date


Active message example***LINE124 OCT05 10:05:07 1998

LINELOG1

Alarmclass: MAJOR

Signaling Point Code: CCITT INTL 222 333 444

TRUNK IDENTITY: ROMAMILNO001





NN10275-909v14 12.01 06 October 2011


Date: OCT05

Time: 10:05:02



LINE129This log report applies when the DMS-100 MMP Switch terminates to aPrivate Exchange (PBX) using the Czech R2 or Poland R2 protocols.

This log is generated when all of the following conditions are met:

• A line call is made by a line or any trunk agent using the Czech R2 orPoland R2 protocols

• The terminator activates MID functionality.

The Poland R2 Format 1 log is generated when the default CLI isavailable. The Poland R2 Format 2 log is generated when only the PartialCLI is available.

The Poland R2 logs are generated only for Poland R2 to line calls. ForPoland R2 to interworking trunk calls, ETSI ISUP and ETSI PRI, theterminating protocol handles the generation of the logs. No logs aregenerated when Poland R2 is the terminator because of the inherentlimitations of the Poland R2 protocol.

Log history

ISN06 (TDM)

The change to LINE129 for feature A59039187 is first documented inISN06 (TDM). This change was first implemented by ISN05 (TDM) activityA59039187. This feature adds a new field, MCT Duration which shows theduration of malicious calls.

Remedial actionThe log is printed when the user activates the feature, and is useful fortracking malicious calls. The logs are provided on request to subscribers ofthe feature. The visibility of MCT Duration depends on the office parameterDURATION_IN_MALICIOUS_CALL_LOGS which is created by featureA5903187.



NN10275-909v14 12.01 06 October 2011



Severity Warning

FormatINC215AV LINE129 mmmdd hh:mm:ss ssdd INFO

MALICIOUS_CALL_IDENTIFICATION_ACTIVATED

len DN dn

Calling_Agent = originating user

Calling_Number = number of originating user

Called_Number = number of subscribed user

Date = dd.mm.yyyy

Time = hh:mm:ss

MCT Duration= hh:mm:ss


VariableDescription

len Alphanumeric text Variable The line equipment number (LEN) ofthe calling agent

DN Constant Fixed Indicates that a directory number (DN)follows

dn Integers Variable The directory number (DN) of thecalled number

Calling_Agent Symbolic text Variable The circuit name and number fromwhere the call originated

Calling_Number Numeric Variable Identifies the number of the callingparty

Called_Number Numeric Variable Identifies the number of the calledparty

Date Numeric Variable The date that the log was generated

Time Numeric Variable The time that the log was generated

MCT Duration time Variable The value of MCT Duration=MCTACTIVATION TIME STAMP -ANSWER TIME STAMP

LINE129 319


NN10275-909v14 12.01 06 October 2011


Active message exampleINC215AV LINE129 NOV28 05:16:00 7680 INFO


HOST 04 1 01 06 DN 9057700023

Calling_Agent: CKT CZECHR2LPB 2

Calling_Number: 7700024

Called_Number:7700023

Date:28:11:2001

Time: 05: 16: 00

MCT Duration = 00:12:34



LINE129 Format 2This log report applies when the DMS-100 MMP Switch terminates to aPrivate Exchange (PBX) using the Czech R2 or Poland R2 protocols.






Log history



NN10275-909v14 12.01 06 October 2011


ISN06 (TDM)




Severity Warning

Format***LINE129 mmmdd hh:mm:ss yyyy

INFO

Log Name:

Calling Agent = originating user

Calling Number = number of originating user

Called Number = number of subscribed user

Date = dd.mm.yyyy

Time = hh:mm:ss

MCT Duration = hh:mm:ss



NN10275-909v14 12.01 06 October 2011



VariableDescription

Name PIE_MALICIOUS_CALL_IDENTIFICATION_ACTIVATED

Variable The printed name of the log

Calling Agent CKT Circuit NameNumber

Variable The circuit name and number fromwhere the call originated

Calling Number Number Variable The number of the calling party

Called Number Number Variable The number of the called party

Date dd.mm.yyyy Variable The date the log was printed

Time hh:mm:ss Variable The time the log was printed

Trunk Identity Circuit Name Variable If the default CLI is not available, thePartial CLI or the circuit name fromwhere the call originated is printed


Active message example***LINE129 JUL07 10:10:12 2000

INFO

PIE_MALICIOUS_CALL_IDENTIFICATION_ACTIVATED

Calling Agent: CKT POLR2LPA 1



Date: 07.07.2000

Time: 10:10:12





NN10275-909v14 12.01 06 October 2011



LINE129 Format 3This log report applies when the DMS-100 MMP Switch terminates to aPrivate Exchange (PBX) using the Czech R2 or Poland R2 protocols.






Log history

ISN06 (TDM)




Severity Warning

Format***LINE129 mmmdd hh:mm:ss yyyy



NN10275-909v14 12.01 06 October 2011


INFO

Log Name:

Trunk Identity:

Called Number:

Date: dd.mm.yyyy

Time: hh:mm:ss



VariableDescription

Name PIE_MALICIOUS_CALL_IDENTIFICATION_ACTIVATED

Variable The printed name of the log

Called Number Number Variable The number of the called party

Date dd.mm.yyyy Variable The date the log was printed

Time hh:mm:ss Variable The time the log was printed

Trunk Identity Circuit Name Variable If the default CLI is not available, thePartial CLI or the circuit name fromwhere the call originated is printed


Active message example***LINE129 JUL07 10:10:12 2000

INFO

PIE_MALICIOUS_CALL_IDENTIFICATION_ACTIVATED

Trunk Identity: POLR2LPA


Date: 07.07.2000

Time: 10:10:12



NN10275-909v14 12.01 06 October 2011





LINE170This log report will be generated if the posted line card passes thediagnostic tests run when the DIAG command is executed with the optionalparameter D. The DIAG command is in the line test position (LTP) menulevel of the MAP display.

This log provides the measured information during the line card diagnostictest.

Remedial actionNo action is required. However, in the event that a line card fails the linecard diagnostics tests (refer to log report LESTE171), the LESTE170 logreport provides information for card repair. Printouts of the diagnostic testresults from the logs must be attached when the card is returned for repair.


Severity Critical

Format*** LINE170 mmmdd hh:mm:ss ssdd PASS LN_DIAG

DIAGNOSTIC RESULT

LEN len DN dn

CARD TYPE: cardtype

TEMPLATE NAME: templatename

MISSING CARD: test result

RINGING TEST: test result

NOISE TEST: test result nn dB

CURRENT LIMIT TEST: test result

LINE170 325


NN10275-909v14 12.01 06 October 2011


TRANSMISSION TEST: test result

LOOP SUPERVISION TEST: test result

REVERSAL RELAY TEST: test result

GND START RELAY TEST: test result


VariableDescription

alarm *** Variable Three asterisks indicate a criticalalarm, which would exist if any linecard or cards fail the diagnostic test

PASS LN_DIAG Constant Fixed Identifies test type as a linediagnostic. LN_DIAG checks for hardware-related faults in line equipment

DIAGNOSTICRESULT

Constant Fixed Indicates the results of diagnostictests follows

LEN Symbolic text Variable Provides equipment identification forthe suspect line card

DN Symbolic text Variable Provides directory number for thesuspect line card

CARD TYPE Symbolic text Variable Identifies the product engineeringcode (PEC) of the line card

TEMPLATE NAME Symbolic text Variable Identifies the template namecorresponding to the line card type

MISSING CARD PASS, FAIL, SKIP Variable Indicates whether the line cardpassed, failed, or skipped thisdiagnostic test

RINGING TEST PASS, FAIL, SKIP Variable Indicates whether the line cardpassed, failed, or skipped thisdiagnostic test

NOISE TEST PASS, FAIL, SKIP Variable Indicates whether the line cardpassed, failed, or skipped thisdiagnostic test

nn dB Variable Provides the measured result of thenoise test in decibels (dB)

CURRENT LIMITTEST

PASS, FAIL, SKIP Variable Indicates whether the line cardpassed, failed, or skipped thisdiagnostic test

TRANSMISSIONTEST




NN10275-909v14 12.01 06 October 2011



Description

LOOP SUPERVISIONTEST


REVERSAL RELAYTEST


GND START RELAYTEST


Active message example*** LINE170 JUL25 11:27:33 1090 PASS LN_DIAG

DIAGNOSTIC RESULT

LEN HOST 00 00 15 DN 7221231

CARD TYPE: 6X17BA

TEMPLATE NAME: WL94CA

MISSING CARD: PASS

RINGING TEST: PASS

NOISE TEST: PASS 20 dB

CURRENT LIMIT TEST: PASS

TRANSMISSION TEST: PASS

LOOP SUPERVISION TEST: PASS

REVERSAL RELAY TEST: PASS

GND START RELAY TEST: PASS


LINE170 327


NN10275-909v14 12.01 06 October 2011



LINE171This log report will be generated if the line card fails the diagnostic testsrun when the DIAG command is executed with the optional parameter D.The DIAG command is in the line test position (LTP) menu level of theMAP display.

This log provides the measured information during the line card diagnostictest.

Remedial actionIf the line card fails the diagnostic tests and needs to be returned for repair,a printout of this log report must be attached to the card. This log reportprovides the information needed to repair the card.



Format*** LINE171 mmmddhh:mm:ss ssdd FAIL LN_DIAG

DIAGNOSTIC RESULT

LEN len DN dn

CARD TYPE: card type

TEMPLATE NAME: template name

MISSING CARD: test result

RINGING TEST: test result

NOISE TEST: test result nn dB

CURRENT LIMIT TEST: test result

TRANSMISSION TEST: test result

LOOP SUPERVISION TEST: test result

REVERSAL RELAY TEST: test result

GND START RELAY TEST: test result



NN10275-909v14 12.01 06 October 2011



VariableDescription

PASS LN_DIAG Constant Fixed Identifies test type as a linediagnostic. LN_DIAG checks for hardware-related faults in line equipment.

DIAGNOSTICRESULT

Constant Fixed Indicates the results of diagnostictests follow

LEN Symbolic text Variable Provides equipment identification forthe suspect line card

DN Symbolic text Variable Provides directory number for thesuspect line card

CARD TYPE Symbolic text Variable Identifies the product engineeringcode (PEC) of the line card

TEMPLATE NAME Symbolic text Variable Identifies the template namecorresponding to the line card type

MISSING CARD PASS, FAIL, SKIP Variable Indicates whether the line cardpassed, failed, or skipped thisdiagnostic test

RINGING TEST PASS, FAIL, SKIP Variable Indicates whether the line cardpassed, failed, or skipped thisdiagnostic test

NOISE TEST PASS, FAIL, SKIP Variable Indicates whether the line cardpassed, failed, or skipped thisdiagnostic test

nn dB Variable Provides the measured result of thenoise test in decibels (dB)

CURRENT LIMITTEST


TRANSMISSIONTEST


LOOP SUPERVISIONTEST


REVERSAL RELAYTEST


GND START RELAYTEST


LINE171 329


NN10275-909v14 12.01 06 October 2011


Active message example*** LINE171 JUL25 11:27:33 1090 FAIL LN_DIAG

DIAGNOSTIC RESULT

LEN HOST 00 00 15 DN 7221231

CARD TYPE: 6X17BA

TEMPLATE NAME: WL94CA

MISSING CARD: PASS

RINGING TEST: PASS

NOISE TEST: PASS 20 dB

CURRENT LIMIT TEST: PASS

TRANSMISSION TEST: PASS

LOOP SUPERVISION TEST: FAIL

REVERSAL RELAY TEST: PASS

GND START RELAY TEST: FAIL



LINK300The LINK300 log generates when the system detects or clears a fault on aresource that Integrated Link Maintenance (ILM) maintains.

Remedial actionThe DS512 paddle board card (9X62) and the Dual Port MessageController (9X86) on the FP communicate with the MSs. Change theNT9X62 and the NT9X86 on plane 0 and perform an intensive Rex test. Ifthe test fails generates LINK300 replace NT9X62 and NT9X86 on Plane 1.


Severity Critical



NN10275-909v14 12.01 06 October 2011


FormatLINK300 mmmddhh:mm:ss ssdd TBL Transport Resource Fault

Location: location id

Status: trouble status

Problem: problem type

Fault Owner: fault id

Description: description of problem

Resource: resource id


VariableDescription

LOCATION Variable Variable Indicates the location on the MessageSwitch (MS) where the system detectsthe fault.

STATUS Variable Variable Indicates if the fault status is raised orcleared.

PROBLEM Variable Variable Indicates if the fault is endpointspecific or end-to-end

FAULT OWNER Variable Variable Indicates the fault ID for the FileProcessor (FP).

DESCRIPTION Variable Variable The string that results when thesystem translates the fault ID with amessage to the node maintenancetarget.

RESOURCE Alphanumeric Variable Indicates the resource as link ormessage channel. Indicates theresource ID.

Active message exampleLINK300 APR02 01:27:09 8400 TBL Transport Resource Fault

Location: "MSO Shelf0 Chain17 Link0 Card17 Port 0"

To "FP 0 Plane

Status: Alarm Raised

Problem: Critical Problem Fault: End-ToEnd Problem

LINK300 331


NN10275-909v14 12.01 06 October 2011


Fault Owner: FP Fault Id: 9

Description: FP DPMC CRITICAL threshold exceeded

MPLH: wait_send_tout

Resource: MCh 0068 000 FFF

AVL: REC: Acc: Prob: 0_RR: T_RR: M_RR: Cond:

NA Sys TRUE Crit TRUE TRUE TRUE FALSE OPEN



LNG101Info Log for Long Calls

This log reports the long duration calls in Table PFXTHR for predefinedprefixes with their threshold values

Log history

ISN06 (TDM)

Log LNG101 added for activity A59039260.

Remedial actionTurn off the LONGCALM using CI command CLEAR_LONGCALM.


Severity Warning

Format> **LNG101 mmmdd hh:mm:ss ssdd <event> <event type>

ANS_TIME = mmmdd hh:mm:ss DURATION= <time>

ORIG_AGENT = <originating agent>

TERM_AGENT = <terminating agent>



NN10275-909v14 12.01 06 October 2011


CALLED_DGTS = <digit registers>


VariableDescription

EVENT INFO Variable Indicates the type of log. The INFOlabel shows that this log reportsinformation only.

EVENT TYPE LNG CALL INFO Variable Indicates the type of INFO event. Itsvalue is a constant.

ANS_TIME N/A Variable The answer time of the long call andits date.

DURATION 15 mins to 24 hours Variable Indicates the time duration of the longcall until this log is generated.

ORIG_AGENT N/A Variable The originating agent of the long call.It is either a DN number or a CLLIname.

TERM_AGENT N/A Variable The terminating agent of the long call.It is a CLLI name.

CALLED_DGTS N/A Variable Called digits

Active message example**LNG101 JAN22 16:00:00 1234 INFO LNG CALL INFO

ANS_TIME = JAN22 14:30:00 DURATION= 1 hour 30 mins

ORIG_AGENT = CKT ICISP2BA

TERM_AGENT = CKT OGISP2BC

CALLED_DGTS = 8222317859



LOGT900When the logtrace feature has been activated for a desired log, it outputs asingle LOGT900 log on every occasion that the traced log is produced. TheLOGT900 log report shows the software code that has been passedthrough to generate the fault/information log. The LOGT900 log stops oncethe logtrace feature has been deactivated.

LOGT900 333


NN10275-909v14 12.01 06 October 2011


See NTP 297-1001-8202 Non-Menu Commands Historical ReferenceManual, Volume 2 of 4, for activating the traceback feature using thelogtrace command in logutil.

Remedial actionContact your next level of support. This is a traceback feature for a report.


Severity Warning

FormatLOGT900 mmdd hh:mm:ss ssdd INFO LOG OUTPUT DEVICE Report

TRACING: <Log type> <Log number> SEQ NO: <id>

<HEX address>=<8th source code module>:<8th source codeprocedure>+#

<code offset>


<code offset>


<code offset>


<code offset>


<code offset>

<HEX address>=<3rd source code module>:<3rd source codeprocedure>+#

<code offset>



NN10275-909v14 12.01 06 October 2011


<HEX address>=<2nd source code module>:<2nd source codeprocedure>+#

<code offset>

<HEX address>=<1st source code module>:<1st source codeprocedure>+#

<code offset>


VariableDescription

INFO LOG OUTPUTDEVICE REPORT

Constant Fixed Indicates that information about anoutput device follows

TRACING Text string Variable Indicates which log report is beingtraced

SEQ NO Numeric Variable Indicates the sequence number

Trace information Software addressesand procedures

Variable Provides traceback information onmodules and processes in use beforethe system produced the log report

Active message exampleLOGT900 OCT09 16:45:58 5900 INFO Logtrace Report

TRACING: CM 102 SEQ NO: 58

0512C2C8=LOGS.FL02:GENERATE_REPORT+#0038

08C02184=CMLOG.BF03:CM_GENER+#00F8

08BF92C0=CMLOG.BF03:GENERATE_G+#00E0

08C7405C=CMMMITRG.BB01:CM_CPU_E+#001C

0407552C=CMMTCKE.BV02:REPORT_M+#002C

08BCAFE8=CMDPXAPR.BI01:CM_DUPLE+#075C

04126518=MODULES.FC14:INITIALIZEP+#0018

0413C408=PROCS.GI02:LIVEANDD+#0018


LOGT900 335


NN10275-909v14 12.01 06 October 2011



MCID100Log MCID100 supports the ETSI ISDN Malicious Call Identificationsupplementary service. It is generated for Italian ISDN Standard User Part(ISUP) to Basic Rate Interface (BRI) or Primary Rate Interface (PRI) callswhenever the ETSI MID feature is activated on a connected agent, and afull calling line identity (CLI) is presented.

Log MCID100 generates an alarm. The log contains the followinginformation:

• calling party number or common language location identifier (CLLI)

• called party number

• the last diverted directory number

• local date and time

Remedial actionThe visibility of the field MID Duration depends on the office parameterDURATION_IN_MALICIOUS_CALL_LOGS.


Severity • Major

• Critical

• Minor

FormatMCID100 mmmdd hh:mm:ss ssdd

Location = object description

Alarmclass = alarm

Calling Agent = originating user

Calling Number = number of originating user

Called Number = number of subscribed user

Last Forwarding Number = last diverted number

Date = date



NN10275-909v14 12.01 06 October 2011


Time = time

MID Duration = time


VariableDescription


Alarmclass ***,**, *or blank Variable Indicates the alarm type of the logreport. Three asterisks (***) indicatesa critical alarm. Two asterisks (**)indicates a major alarm. One asterisk(*) indicates a minor alarm. Noasterisk indicates that no alarmgenerates.

Calling Agent line equipmentnumber (LEN) or CLLItrunk

Variable Type of originating user

Calling Number numeric (0 to 9 digits) Variable Number of originating user

Called Number numeric(0 to 9 digits) Variable Number of subscribed user


numeric(0 to 9 digits) Variable This field is the last diverted numberfor call forwarding.

Date numeric(0 to 9 digits) Variable Date of current year


MID Duration time Variable The value of MID Duration = MCTACTIVATION TIME STAMP -ANSWER TIME STAMP

Active message example***MCID100 OCT05 10:05:07 1998

MCIDLOG1

Alarmclass: MAJOR

Calling Agent: LEN HOST 1 0 0 2




MCID100 337


NN10275-909v14 12.01 06 October 2011


Date: OCT05

Time: 10:05:02

MID Duration: 00:05:01



MCID101Log report MCID101 is generated for ISDN Standard User Part (ISUP) toBasic Rate Interface (BRI) or Primary Rate Interface (PRI) calls wheneverthe ETSIMCID feature is activated on a connected agent, and only a partialcalling line identity (CLI) is present.

The generation of log MCID101 does not indicate a fault or error conditionon the switch. No action by any maintenance support groups is required.

The information in the log can be used in connection with the ETSI MIDservice to identify the source of a call.

Remedial actionn/a


Severity • Major

• Critical

• Minor



Alarmclass: <alarm>

Signaling Point Code: <signaling

point> Trunk Identity: <logical trunk name>




NN10275-909v14 12.01 06 October 2011


Last Forwarded Number: <last diverted number>

Date: <date>

Time: <time>


VariableDescription


Alarm class ***, **, *or blank Variable Indicates the alarm type of the logreport. Three asterisks (***) indicate acritical alarm. Two asterisks (**)indicate a major alarm. One asterisk(*) indicates a minor alarm. Noasterisk indicates that no alarmappears.

Signaling Point Code numeric (0 to 9 digits) Variable Identifies the signaling point.

Trunk Identity alphanumeric (up to15 IA characters)

Variable Common language location identifier,giving the logical name of theincoming trunk.

Called Number numeric (0 to 9 digits) Variable Number of subscribed user.


numeric (0 to 9 digits) Variable Last diverted number for callforwarding.

Date numeric (0 to 9 digits) Variable Date

Time numeric (0 to 9 digits) Variable Time of day

Active message example***MCID100 JAN04 10:05:07 2000

MCIDLOG1

Alarmclass: MAJOR

Signaling Point Code: CCITT INTL 222 333 444

TRUNK IDENTITY: ROMAMILNO001



Date: JAN04

MCID101 339


NN10275-909v14 12.01 06 October 2011


Time: 10:05:02



MCID103The Log MCID103 feature applies to VN4 Basic Rate Interface (BRI) Point-to-Point (p-p) access. The Malicious Call Identification (MID) feature allowsa called party to request that the originator of an incoming call isidentifiable, and the call is recorded by the network. The called party canarrange for this information to be made available during the active phase ofthe call or during the clearing phase.

Remedial actionThis is an information log. No action is required on the part of the user.


Severity Warning



Calling Number NDS: <originating user network number>

Calling Number NDI: <originating user

user-provided number>

Called Party Number: <number of subscribed user>

First_FWDing_Number: <first diverted number>

Date: <date>

Time: <time>



NN10275-909v14 12.01 06 October 2011



VariableDescription

Calling Agent line equipmentnumber (LEN) or CLLItrunk

Variable Type of originating user

Calling Number NDS numeric (0 to 9 digits) Variable Number of originating user

Calling Number NDI numeric (0 to 9 digits) Variable Network number of originating user

Called Party Number numeric (0 to 9 digits) Variable Number of subscribed user

First_FWDing_Number

numeric (0 to 9 digits) Variable The first diverted number for callforwarding.

Date numeric (0 to 9 digits) Variable Date of current year

Time numeric (0 to 9 digits) Variable Time of day

Active message example***MCID103 JUL04 05:46:56 3200 INFO

VN_MALICIOUS_CALL_IDENTIFICATION_ACTIVATED

Calling Agent: LTID GUI 200 DN 727777777300 KEY 2

Calling Number NDS: 727777777300

Calling Number NDI (if NDI is present): 727777777300

Calling Number NDI (if NDI is not present): $


First_FWDing_Number

(if the call has not been forwarded): $

First_FWDing_Number

(if the call has been forwarded): 1036340119

Date: JUL04

Time: 05:46:56


MCID103 341


NN10275-909v14 12.01 06 October 2011



MCID110This log report applies to feature Metering Support with Flexible ChannelAssociated Signalling (CAS) when the DMS-100 MMP Switch terminates toa Private Branch Exchange (PBX) using the Czech R2 protocol.

This log report is generated when a Malicious Call Identification (MID)subscriber activates MID during any of the following conditions:

• The DMS-100 MMP Switch terminates to a Private Branch Exchange(PBX)

• The DMS-100 MMP Switch receives a Malicious Line Call (MLC) linesignal from the PBX during the answer phase

• The called party remains on-hook for 30 seconds after the calling partygoes on-hook.

Remedial actionn/a


Severity Warning

FormatINC215AU MCID110 mmmdd hh:mm:ss ssdd INFO


Term_Agent Trunk_Mem


Calling_Number: 9057700071

Called_Number: 1337700071

Date: 21.11.2001

Time: 15:48:08



NN10275-909v14 12.01 06 October 2011



VariableDescription

mmmdd Alphanumeric Variable The date that the log was generated

hh:mm:ss Numeric Variable The time that the log was generated

ssdd Numeric Variable The sequence number of the log

Inch Alphanumeric text Variable Identifies the name of the DMS-100switch

15AU Alphanumeric text Variable Identifies the Call Machine load on theDMS-100 switch

INFO Constant Fixed Indicates an Information Log

Term_Agent Symbolic text Variable Identifies the called party

Trunk_Mem Numeric Variable Identifies the trunk member (1 = firsttrunk member)

Calling_Agent Symbolic text Variable Identifies the calling party agent

Calling_Number Numeric Variable Identifies the number of the callingparty

Called_Number Numeric Variable Identifies the number of the calledparty

Date Numeric Variable The date that the log was generated

Time Numeric Variable The time that the log was generated

Active message exampleINC215AU *MCID110 NOV21 15:48:08 2412 INFO


CKT STEP_CZR2_OG 1


Called_Number: 9057700072

Date:21.11.2001

Time:15:48:08


MCID110 343


NN10275-909v14 12.01 06 October 2011



MCT104The Malicious Call Trace (MCT) subsystem generates log report MCT104if the terminating subscriber activates the MCT feature either during thespeech phase of the call, or within a certain period after the callingsubscriber has gone on-hook with the terminating subscriber remaining off-hook.

The MCT104 log is produced in the UK market if an incoming BTUP (UKvariant of a national user part) call terminates on a Meridian Digital Centrex(MDC) line with a malicious call identification (MCI) feature activated.Some interworking must have been involved in the call connection suchthat the Partial Calling Line Identification (PCLI) of the first BTUP-compatible node has been recorded.

Log report Line125 is not produced in the UK market; log reports MCT103and MCT104 are produced instead.

The generation of log report MCT104 does not indicate a fault or errorcondition on the switch. The information contained in the log is to be usedonly in conjunction with the malicious call identification (MCI) features.

Remedial actionn/a


Severity Warning

Format***MCT104 mmmdd hh:mm:ss ssdd INFO

TRACE_ON_MALICIOUS_CALL_ACTIVATED

UNIT_TYPE : unit type nn

REGION_AND_AREA : RA #

UNIT_ID : unit id #

INCOMING_TRUNK : CKT

CALLED_PARTY : <full number> <terminating agent>



NN10275-909v14 12.01 06 October 2011


CALLING_PARTY_CATEGORY : cpc #


VariableDescription

***INFO TRACE_ON_MALICIOUS_CALL_ACTIVATED

Constant Fixed Indicates that the MCT feature hasbeen activated

UNIT_TYPE nn Variable Identifies the type of the unit involvedin the MCT

REGION_AND_AREA Integers (RA id #) Variable Identifies the region and area idnumber involved in the MCT

UNIT_ID Integers (id #) Variable Identifies the unit involved in the MCT

INCOMING_TRUNK CKT Variable Identifies the circuit / trunk id

CALLED_PARTY Integers Variable Identifies the national numberrepresenting the terminator of the call.The terminating agent identifies theline equipment number (LEN) at theterminating exchange.

CALLING_PARTY_CATEGORY

cpc # (0-255) Variable Indicates the classification of theoriginating party

Active message example***MCT104 MAY28 12:01:00 3281 INFO

TRACE_ON_MALICIOUS_CALL_ACTIVATED

UNIT_TYPE : 02

REGION_AND_AREA: 36

UNIT_ID : 1832

INCOMING_TRUNK: CKT BTUP1IC

CALLED_PARTY : 4102 LEN HOST 03 1 04 02 DN 2364102

CALLING_PARTY_CATEGORY : 0


MCT104 345


NN10275-909v14 12.01 06 October 2011



MCT105The Call Presentation Malicious Call Trace (MCT) Log feature generateslog report MCT105 when a subscriber''s line with the MCT Log featureactive is called. The MCT Log feature is active when theMCT_PRESENTATION_LOG_ACT field of office parameterMCT_PRESENTATION_LOG is set to Y, and the line has the option CLF(Calling Line Identity with Flash) or MCH (Malicious Call Hold) assigned.

The log displays details of the originator and destination of the call. TheMCT_PRES_LOG_ALARM option of office parameterMCT_PRESENTATION_LOG in table OFCVAR determines whether thesoftware alarm, MCTALARM, is activated when this report is generated.

Remedial actionNo immediate action is necessary. Generation of this log does not indicatea fault or error condition on the switch.


Severity Warning

Format** MCT105 <mmmdd> <hh:mm:ss> <log_count> INFO

MCTLOG

CALLING : $ <len> <dn>

CALLED : <cdli> <len> <dn>


VariableDescription

MCTLOG constant Fixed Indicates that the Call PresentationMCT Log feature has been activated

len alphanumeric Variable Identifies the line equipment number(LEN) used in the call

dn integer Variable Identifies the directory number (DN) ofthe calling or called party

cdli integer Variable Called Line Identification. This fieldprovides the numbers in the calleddigit register.



NN10275-909v14 12.01 06 October 2011



Description

cgli integer Variable Calling Line Identification (CLI). Thisfield provides the national numberrepresenting the originator of the call.The value $ indicates no CLI isavailable.

clli alphanumeric Variable Indicates the logical name for theincoming trunk

trkid alphanumeric Variable Indicates the trunk identification

Active message example** MCT105 NOV19 12:18:08 5900 INFO MCTLOG

CALLING : $ LEN REM3 50 0 04 00 DN 8798007

CALLED : 8008 LEN HOST 50 1 04 01 DN 8798008

** MCT105 NOV19 12:17:41 5000 INFO MCTLOG

CALLING : 8798007 CKT KNGB211ISWBE 3



CALLING : $ CKT KNGB211ISWBE 1




MCT105 Format 2The Call Presentation Malicious Call Trace (MCT) Log feature generateslog report MCT105 when a subscriber''s line with the MCT Log featureactive is called. The MCT Log feature is active when theMCT_PRESENTATION_LOG_ACT field of office parameterMCT_PRESENTATION_LOG is set to Y, and the line has the option CLF(Calling Line Identity with Flash) or MCH (Malicious Call Hold) assigned.

MCT105 Format 2 347


NN10275-909v14 12.01 06 October 2011


The log displays details of the originator and destination of the call. TheMCT_PRES_LOG_ALARM option of office parameterMCT_PRESENTATION_LOG in table OFCVAR determines whether thesoftware alarm, MCTALARM, is activated when this report is generated.

Remedial actionNo immediate action is necessary. Generation of this log does not indicatea fault or error condition on the switch.


Severity Warning

Format** MCT105 <mmmdd> <hh:mm:ss> <log_count> INFO

MCTLOG

CALLING : <cgli> <clli> <trkid>

CALLED : <cdli> <len> <dn>


VariableDescription

MCTLOG constant Fixed Indicates that the Call PresentationMCT Log feature has been activated

len alphanumeric Variable Identifies the line equipment number(LEN) used in the call

dn integer Variable Identifies the directory number (DN) ofthe calling or called party

cdli integer Variable Called Line Identification. This fieldprovides the numbers in the calleddigit register.

cgli integer Variable Calling Line Identification (CLI). Thisfield provides the national numberrepresenting the originator of the call.The value $ indicates no CLI isavailable.

clli alphanumeric Variable Indicates the logical name for theincoming trunk

trkid alphanumeric Variable Indicates the trunk identification



NN10275-909v14 12.01 06 October 2011


Active message example** MCT105 NOV19 12:18:08 5900 INFO MCTLOG

CALLING : $ LEN REM3 50 0 04 00 DN 8798007



CALLING : 8798007 CKT KNGB211ISWBE 3



CALLING : $ CKT KNGB211ISWBE 1




MCT106The DMS-Global Services Platform (DMS-GSP) generates the log reportMCT106 Emergency call trace to alert the network operator of emergencytraffic. Information on the calling party, the called party, and the time of thecall are recorded.

This service implements delayed release and call trace functionality forcalls terminating to Hong Kong ISUP agencies. The DMS-GSP receives aninformation request (INR) message with "Holding Indicator" bit = 1 for allemergency calls.

The MCT103 Malicious call trace presently generates an emergency calllog upon receipt of an INR message with "Malicious Call IdentificationIndicator" bit = 1. If the DMS-GSP receives an INR message with both the"Holding Indicator" bit = 1 and the "Malicious Call Identification Indicator"bit = 1 at the same time, the MCT106 log is generated. Holding bit takesprecedence over malicious call trace bit.

The log report MCT106 overrides the MCT103. For more information onthe MCT103, see the MCT103 log report.

Log history

MCT106 349


NN10275-909v14 12.01 06 October 2011


ISN06 (TDM)

The change to MCT106 for feature A59039187 is first documented inISN06 (TDM). This change was first implemented by ISN05 (TDM) activityA59039187. This feature adds a new field, MCT Duration which shows theduration of malicious calls.

Remedial actionThis log report requires no action, but should be saved for later referencein case the MCT103 is received. It provides information on the callingparty, called party, and the time of the call.


Severity Warning


lcn DN dn


Calling Number: <number of originating user>



Date: <date>

Time: <time>

MCT Duration= <time>



NN10275-909v14 12.01 06 October 2011



VariableDescription

MCT DURATION Time Variable The value of MCT DURATION=MCTACTIVATION TIME STAMP -ANSWER TIME STAMP. The MCTDURATION field is visible when theofcparm is ON.

CALLING_PARTY Alphanumeric Variable This field indicates the calling line ID(CLI) and/or the originating agent(trunk group) of the calling party.

CALLED_PARTY Alphanumeric Variable This field provides the full number ofthe party called and the CLI and trunkgroup of the called party.

MCT DURATIONCALLING_PARTY_CATEGORY

0 - 255 Variable The MCT DURATIONCALLING_PARTY_CATEGORY(CPC) field provides the classificationof user placing the call. Specificvalues depend on the trunk agency.Refer to NTP 297-2651-119 BillingRecords Reference Manual for moreinformation.

DELAY_RELEASE_ACTIVATED

Constant Fixed Delayed release functionalityimplementation is based on receipt ofan Information Request Message(INR) with the Holding Indicator bit = 1or the Malicious Call IdentificationIndicator bit = 1. If the DMS-GSPreceives an Information Message(INF) indicating no holding provided(Hold Provided Indicator bit = 0 in theINF) in response to the initial INR,delayed release functionality is stillprovided.

Active message example***MCID106 OCT05 10:05:07 1998

HOST 00 0 10 02 DN 1027835590 KEY 1

Calling Agent: LEN HOST 1 0 0 2



MCT106 351


NN10275-909v14 12.01 06 October 2011


Last Forwarding Number: $

Date: 12.02.2002

Time: 10:05:02

MCT Duration= 00:12:34

***MCT106 NOV08 08:11:00 1234 INFO

DELAY_RELEASE_ACTIVATED

CALLING_PARTY:$ CKT GCR13T1A01A 101

CALLED_PARTY:9612345 CKT GCR141T1A01B 1612

MCT DURATION CALLING_PARTY_CATEGORY: 2

MCT DURATION:00:12:34



MML300 Format 1This log is generated if the DN is illegal or contains an incorrect number ofdigits.

For an unsuccessful process, the log will include one of the following causenumbers:

00000001 (1-9D)

00000002 Translation problem

...(error codes from TX-1)

00001001

00001010 (10D) -Link CSL failed (link between TX-1 and MM)

00001011 (11D) -TX-1 time out (MM didn''t respond)

00010011 (19D) -Administration server is busy



NN10275-909v14 12.01 06 October 2011


00010100 (20D) -MM in SYSB state






00011110 (30D) -Incorrect CI command

00011111 (31D) -DN is not correct

00100001 (33D) -DN cannot be the same as Broadcast DN

00100010 (34D) -DN cannot begin with Name Dial Prefix

00100100 (36D) -Module parameters are wrong

00101000 (40D) -Mailbox doesn''t exist (for VMDEL/VMQDN)

00101001 (41D) -Mailbox already exists (for VMDEF command)

00101010 (42D) -The Mailbox number has reached the maximum limit

00101100 (44D) -Another MM program locked the resources

00101101 (45D) -Error occurred during lock operation

00101110 (46D) -Problems while model reading

01011010 (90D) -A general system error occurred during operation

Remedial actionRepeat the command with the correct DN.



FormatMML 300 <Date> <Hour> <Seq. no.> FAIL Illegal DN

MML300 Format 1 353


NN10275-909v14 12.01 06 October 2011


Invalid DN

Try again to enter DN.

DN: <DN>


VariableDescription

Seq. no NNNN Variable The current log number in thesequence of logs created in theswitch.

Active message exampleCAP7_35 * MML300 MAY06 14:48:35 1700 FAIL Illegal DN

Invalid DN

Area code is illegal

DN: 033333333



MML300 Format 2This log is generated if the DN is illegal or contains an incorrect number ofdigits.


00000001 (1-9D)



00001001





NN10275-909v14 12.01 06 October 2011





















Remedial actionRepeat the command with the correct DN.



MML300 Format 2 355


NN10275-909v14 12.01 06 October 2011


FormatMML 300 <Date> <Hour> <Seq. no.> FAIL Illegal DN

Invalid DN

Try again to enter DN.

DN: <DN>


VariableDescription


Active message exampleCAP7_35 * MML300 MAY06 14:48:35 1700 FAIL Illegal DN

Invalid DN

Area code is illegal

DN: 033333333



MML301This log is generated if the High Data Link Controller (HDLC) link fails (bothlinks must be in service to enable CI commands for Voice Mail (VML)).


00000001 (1-9D)



00001001



NN10275-909v14 12.01 06 October 2011























Remedial actionThe operator must rectify both links before issuing a definition process inthe CI.

MML301 357


NN10275-909v14 12.01 06 October 2011




FormatMML 301 <Date> <Hour> <Seq. no.>TBL HDLC link not available

HDLC not available!

DN: <DN>.


VariableDescription


Active message exampleCAP7_35 * MML301 MAY06 14:48:35 1700 TBL HDLC link notavailable

HDLC not available!

DN: 03340082



MML310This log is generated if the subscriber definition is unsuccessful.


00000001 (1-9D)



00001001



NN10275-909v14 12.01 06 October 2011























Remedial actionAccording to the cause number, the craft person must decide to repeat thecommand, or ask the operator to solve the problem. See the causenumbers listed under Additional information.

MML310 359


NN10275-909v14 12.01 06 October 2011




FormatMML 310 <Date> <Hour> <Seq. no.> FAIL Voice Mail: Add new DN

RESULT: Subscriber addition failed

MODULE: <MODULE>

STATUS: <STATUS>

COUNT: <COUNT>

DN: <DN>


VariableDescription


MODULE 1 to 255 Variable The profile of the subscriber.

STATUS N Variable The status of the subscriber. If thedefinition succeeded, the status is setto 0.

COUNT 0 to 9 Variable The number of digits in the DN.

Active message exampleCAP7_35 * MML310 MAY06 14:48:35 1700 FAIL Voice Mail: Addnew DN

RESULT: Subscriber addition failed

MODULE: 12

STATUS: 4

COUNT: 8

DN: 03340058



NN10275-909v14 12.01 06 October 2011




MML311This log is generated if the deletion of a subscriber is unsuccessful.


00000001 (1-9D)



00001001















MML311 361


NN10275-909v14 12.01 06 October 2011









Remedial actionAccording to the cause number, the craft person must decide to repeat thecommand, or ask the operator to solve the problem. See the causenumbers listed under Additional information.



FormatMML 311 <Date> <Hour> <Seq. no.> FAIL Voice Mail: Deleteexisting DN

RESULT: Subscriber deletion failed

STATUS: <STATUS>

COUNT: <COUNT>

DN: <DN>



NN10275-909v14 12.01 06 October 2011



VariableDescription


STATUS N Variable The status of the subscriber. If thedeletion succeeded, the status is setto 0.


Active message exampleCAP7_35 * MML311 MAY06 14:48:35 1700 FAIL Voice Mail: Delete

existing DN

RESULT: Subscriber deletion failed

MODULE: 12

STATUS: 4

COUNT: 8

DN: 03340058



MML312This log is generated if the DN does not exist at Voice Mail (VML).


00000001 (1-9D)



00001001

MML312 363


NN10275-909v14 12.01 06 October 2011























Remedial actionn/a



NN10275-909v14 12.01 06 October 2011




FormatMML 312 <Date> <Hour> <Seq. no.> FAIL Voice Mail: queryexisting DN

RESULT: Subscriber query not exist

STATUS: <STATUS>

COUNT: <COUNT>

DN: <DN>


VariableDescription


STATUS N Variable The status of the subscriber.


Active message exampleCAP7_35 * MML 312 MAY06 14:48:35 1700 FAIL Voice Mail: query

existing DN

RESULT: Subscriber query not exist

STATUS: 4

COUNT: 8

DN: 03340058


MML312 365


NN10275-909v14 12.01 06 October 2011



MML313This log is generated if modification of the subscriber profile isunsuccessful.


00000001 (1-9D)



00001001


















NN10275-909v14 12.01 06 October 2011








Remedial actionn/a



FormatMML 313 <Date> <Hour> <Seq. no.> FAIL Voice Mail: Modifyingexisting

DN profile

RESULT: Modifying profile of subscriber failed

STATUS: <STATUS>

COUNT: <COUNT>

DN: <DN>


VariableDescription




MML313 367


NN10275-909v14 12.01 06 October 2011


Active message exampleCAP7_35 * MML 313 MAY06 14:48:35 1700 FAIL Voice Mail:Modifying

existing DN profile

RESULT: Modifying profile of subscriber failed

STATUS: 4

COUNT: 8

DN: 03340058



MML314This log is generated if the password is not reset.


00000001 (1-9D)



00001001










NN10275-909v14 12.01 06 October 2011
















Remedial actionn/a



FormatMML 314 <Date> <Hour> <Seq. no.> FAIL Voice Mail: Resetexisting DN

password

RESULT: Reset password failed

STATUS: <STATUS>

MML314 369


NN10275-909v14 12.01 06 October 2011


COUNT: <COUNT>

DN: <DN>


VariableDescription




Active message exampleCAP7_35 * MML 314 MAY06 14:48:35 1700 FAIL Voice Mail: Reset

existing DN password

RESULT: Reset password failed

STATUS: 4

COUNT: 8

DN: 03340058



MML610This log is generated if the subscriber was defined correctly, and thedefinition succeeded.

For a successful process, the log includes the cause number:

00000000 (OH) -O.K.

Remedial actionn/a



NN10275-909v14 12.01 06 October 2011




FormatMML 610 <Date> <Hour> <Seq. no.> PASS Voice Mail: Add new DN

RESULT: Subscriber added.

MODULE: <MODULE>

STATUS: <STATUS>

COUNT: <COUNT>

DN: <DN>


VariableDescription


MODULE 1 to 255 Variable The profile of the subscriber.


COUNT 0 to 9 Variable The number of digits in the DN

Active message exampleCAP7_35 * MML610 MAY06 14:48:35 1700 PASS Voice Mail: Addnew

DN

RESULT: Subscriber added.

MODULE: 12

STATUS: 0

COUNT: 8

DN: 03340058

MML610 371


NN10275-909v14 12.01 06 October 2011




MML611This log is generated if the subscriber was successfully deleted.


00000000 (OH) -O.K.

Remedial actionn/a



FormatMML 611 <Date> <Hour> <Seq. no.> PASS Voice Mail: Deleteexisting DN

RESULT: Subscriber deleted

STATUS: <STATUS>

COUNT: <COUNT>

DN: <DN>


VariableDescription




Active message exampleCAP7_35 * MML611 MAY06 14:48:35 1700 PASS Voice Mail: Delete

existing DN



NN10275-909v14 12.01 06 October 2011


RESULT: Subscriber deleted

STATUS: 0

COUNT: 8

DN: 03340058



MML612This log is generated if the DN exists at Voice Mail (VML).


00000000 (OH) -O.K.

Remedial actionn/a



FormatMML 612 <Date> <Hour> <Seq. no.> PASS Voice Mail: queryexisting DN

RESULT: Subscriber query exist

STATUS: <STATUS>

COUNT: <COUNT>

DN: <DN>

MML612 373


NN10275-909v14 12.01 06 October 2011



VariableDescription




Active message exampleCAP7_35 * MML612 MAY06 14:48:35 1700 PASS Voice Mail: query

existing DN

RESULT: Subscriber query exist

STATUS: 0

COUNT: 8

DN: 03340058



MML613This log is generated if the profile of the subscriber is modified.


00000000 (OH) -O.K.

Remedial actionn/a



FormatMML 613 <Date> <Hour> <Seq. no.> PASS Voice Mail: Modifyingexisting



NN10275-909v14 12.01 06 October 2011


DN profile

RESULT: Profile of subscriber modified

STATUS: <STATUS>

COUNT: <COUNT>

DN: <DN>


VariableDescription




Active message exampleCAP7_35 * MML613 MAY06 14:48:35 1700 PASS Voice Mail:Modifying

existing DN profile

RESULT: Profile of subscriber modified

STATUS: 0

COUNT: 8

DN: 03340058



MML614This log is generated if the reset password succeeded.

Remedial actionn/a

MML614 375


NN10275-909v14 12.01 06 October 2011




FormatMML 614 <Date> <Hour> <Seq. no.> PASS Voice Mail: Resetexisting DN

password

RESULT: Reset password succeeded

STATUS: <STATUS>

COUNT: <COUNT>

DN: <DN>


VariableDescription




Active message exampleCAP7_35 * MML614 MAY06 14:48:35 1700 PASS Voice Mail: Reset

existing DN password

RESULT: Reset password succeeded

STATUS: 0

COUNT: 8

DN: 03340058




NN10275-909v14 12.01 06 October 2011



MS304The Message Switch (MS) subsystem generates log report MS304 whenthe state of a port changes. The state of the port changes from P-side busy(PBsy) or C-side busy (CBsy) to system busy (SysB).

Remedial actionManually-busy, and test the port. If this test fails, the system generates acardlist. If the defective card is on the peripheral side, performmaintenance action on the peripheral. Also, check for logs related to theperipheral.

If the defective card is on the MS, manually-busy the node. Replace thedefective card and manually return to service (RTS) the node. If this statechange fails, the system generates another cardlist. Replace any defectivecards and RTS again. If the port is not OK, check the backplane for looseor bad cables.



Format*MS304 mmmdd hh:mm:ss ssdd SYSB PORT STATE CHANGE

SET FROM event_type BY reptxt n CODE REF: nnn

FLT MAP:

MS: n SHELF: n CARD: nn PORT: n

FRONT PEC: pec BACK PEC: pec

comment line or fault description report


VariableDescription

SYSB PORT STATECHANGE

Constant Fixed Indicates a change of state for aspecified port.

SET FROM Symbolic text Variable Indicates the previous state of themessage switch. Refer to table E.

MS304 377


NN10275-909v14 12.01 06 October 2011



Description

BY SYSTEM ACTIONFAULT REPORT(blank)

Variable Indicates the reason for the report. Ifblank, the reason is not reported.

CODE REF Integer Variable Indicates in the code, the location ofthe MS log. This number identifiesrelated log reports.

MS 0 or 1 Variable Indicates the MS involved.

SHELF 0 to 3 Variable Indicates the shelf number.

CARD 1 to 26 Variable Indicates the card number.

PORT 0 to 3 Variable Indicates the port number.

FRONT PEC Alphanumeric Variable Indicates the product engineeringcode (PEC) of the front card. Refer totable I.

BACK PEC Alphanumeric Variable Indicates the PEC of the back card.Refer to table I.

comment line or faultdescription report

Symbolic text Variable Includes an optional comment line. Ifreptxt has the value FAULT REPORT,then all faults, raised or cleared, arereported, one on each line. Theheader message appears before thedescription. The message FAULTCLEARED indicates that the fault isclear. The FAULT PRESENTmessage indicates that the detectedfault remains. The FAULT RAISEDmessage indicates a new fault.

Active message example*MS304 SEP24 00:00:00 6000 SYSB PORT STATE CHANGE

SET FROM PBSY BY SYSTEM ACTION CODE REF: 0:000000000000

FLT MAP: 0000 0000 0000 0000 0000

MS: 0 SHELF: 1 CARD: 21 PORT: 3

FRONT PEC: 9X17AA BACK PEC: 9X23AA




NN10275-909v14 12.01 06 October 2011



MTR100The Metering (MTR) subsystem generates log report MTR100 when thesubscriber meter count exceeds the maximum meter count for the secondtime in one billing period. In this situation, a meter wraparound occurs.

Remedial actionIf meter wraparound occurs more than once during a billing period, savethe log reports. Contact the next level of maintenance.


Severity Warning

FormatMTR100 mmmdd hh:mm:ss ssdd INFO METER WRAPAROUND

<cpid>

METER NAME: <mtrnm> METER COUNT: <nnnn nnnn nnnn>


VariableDescription

INFO METERWRAPAROUND

Constant Fixed Indicates that the subscriber metercount exceeds the maximum metercount for the second time in one billingperiod. A meter wraparound occurs.

cpid Alphanumeric Variable Identifies the LINE CP_ID or TRUNKCP_ID.

mtrnm Character string Variable Meter name. Indicates the line or trunkmeter name. Refer to tableMTRNAMES in the data schemasection of Translations Guide .

nnnn nnnn nnnn 0000 0000 0000 to9999 9999 9999

Variable Meter count. Indicates the count onthe meter when the secondwraparound occurred.

Active message exampleMTR100 MAR26 15:58:59 3529 INFO METER WRAPAROUND

DN 20007

MTR100 379


NN10275-909v14 12.01 06 October 2011


METER NAME: FEATURE METER COUNT: 0000 0000 0015



MTR107This log indicates that a process is running.

Remedial actionn/a


Severity Warning

FormatMTR107 mmmdd hh:mm:ss ssdd INFO PROCESS IS RUNNING

PROCESS : <process>


VariableDescription

process alphanumeric Variable Indicates the process that is running.Examples include Backup Process,Line Recovery Process, Out ofService Process, Line Meter Audit,Threshold Queue Audit.

Active message exampleMTR107 AUG16 10:34:56 3927 INFO PROCESS IS RUNNING

PROCESS : LINE METER AUDIT




NN10275-909v14 12.01 06 October 2011



MTR152The metering (MTR) subsystem generates this report when both of thefollowing happens:

• a subscriber originates a call

• the datafill of the logical network (LNET) indicates an unsupportedmetering role (MTRROLE)

Operating company personnel cannot meter the call. The value of fieldmeter fail parameter (MFP) in table MTRSYSPM determines if the callgoes to treatment.

Remedial actionFor the indicated originator, check the MTRROLE value shown in tableMTRNETIF for the given LNET. Metering does not support this role.Operating company personnel can change the MTRROLE value to asupported value.


Severity Warning

FormatMTR152 mmmdd hh:mm:ss ssdd INFO FAIL METER DATAFILL

orig cpid

UNSUPPORTED METER ROLE - CHECK TABLE MTRNETIF

DATAFILL

LNETWORK: lnet MTRROLE: role


VariableDescription

FAIL METERDATAFILL

constant Fixed The call cannot be metered. Apossible reason is incorrect datafill intable MTRNETIF.

orig cpid alphanumericcharacter string

Variable This field indicates the host numberand directory number of the partyoriginating the call.

MTR152 381


NN10275-909v14 12.01 06 October 2011



Description

UNSUPPORTEDMETER ROLE -CHECK TABLEMTRNETIFDATAFILL

constant Fixed The datafill of the LNET indicates anunsupported MTRROLE.

LNETWORK alphanumeric (up to16 characters)

Variable This field indicates the logical networkname.

MTRROLE GENERATE,RECEIVE, orTANDEM

Variable This field indicates the agent-independent metering role. This entrycan be either of the following:

• GENERATE (generates meterpulses)

• RECEIVE (receives meter pulses)

• TANDEM (receives meter pulseson an outgoing trunk andgenerates them again on theincoming agent)

This system may not support valuesRECEIVE and TANDEM.

Active message exampleMTR152 MAY04 15:34:44 0177 INFO FAIL METER DATAFILL

HOST 05 1 00 20 DN 9096210001

UNSUPPORTED METER ROLE - CHECK TABLE MTRNETIF DATAFILL

LNETWORK: INTL MTRROLE: RECEIVE



MTR154The Metering (MTR) subsystem generates log report MTR154 when atrunk group is added to a logical meter group (LMG) by adding option LMGto the trunk in table TRKOPTS.

Remedial actionn/a



NN10275-909v14 12.01 06 October 2011



Severity Warning

FormatMTR154 mmmdd hh:mm:ss ssdd INFO LMG TRUNK ADDED

<clli> added to LMG <lmgno>


VariableDescription

clli Alphanumeric Variable CLLI of the specified trunk

lmgno Numeric Variable LMG number

Active message exampleMTR154 SEP24 13:23:54 2112 INFO LMG TRUNK ADDED

PRITRUNK013 added to LMG 4711



MTR155The Metering (MTR) subsystem generates log report MTR155 when atrunk group is removed from a logical meter group (LMG) by removingoption LMG from the trunk in table TRKOPTS.

Remedial actionn/a


Severity Warning

FormatMTR155 mmmdd hh:mm:ss ssdd INFO LMG TRUNK DELETED

<clli> deleted from LMG <lmgno>

MTR155 383


NN10275-909v14 12.01 06 October 2011



VariableDescription

clli Alphanumeric Variable CLLI of the specified trunk

lmgno Numeric Variable LMG number

Active message exampleMTR155 SEP24 13:23:54 2112 INFO LMG TRUNK DELETED

PRITRUNK013 deleted from LMG 4711



MTR156Successful metering (CEPT feature) actions such as assign, usage,deassign, activation, deactivation or interrogation generates log MTR156.

Log MTR156 contains the calling number, date, hour, feature code,function code and the feature meter count.

Remedial actionSuccessful metering due to CEPT feature actions generates Log MTR156.


Severity Warning

FormatMTR156 mmmdd hh:mm:ss ssdd INFO MCR LOG ENTRY

CALLING NUMBER : <callg_nm> FEATURE CODE : <ftr_cod>

ACTION : <act_cod> COUNT : <nn>

TIME : <HH:MM:SS> DATE : <YY/MM/DD>



NN10275-909v14 12.01 06 October 2011



VariableDescription

INFO MTR LOGENTRY

Constant Fixed Indicates a report of MTR information

CALLING NUMBER Symbolic text Variable Identifies the number of the originator

FEATURE CODE 00-99 Variable Indicates the feature name

ACTION 00-99 Variable Indicates which action is done

FEATUREMETERING COUNT

00-99 Variable Indicates the charges according to thefeature action

ANSWER DATE Integers Variable Indicates the date the call wasanswered

ANSWER TIME Integers Variable Indicates the time in hours, minutesand seconds the call was answered

Active message exampleMTR156 JUN28 09:33:57 2909 INFO LOG

CALLING NUMBER : 1027845477 FEATURE CODE : 12

ACTION : 01 COUNT : 05

TIME: 09:33:57 DATE : 00/06/28



MTR157The MTR157 log is generated by the Reverse Charging (REV) feature forany of the following conditions:

• Originator line has Free Number Origination (FNO) option

• Primary Rate Interface (PRI) interworking

• ISDN User Part (ISUP) - R1/R2/Flexible Digital CAS Platform (FDCP)interworkings

• Reverse Charging (REV) is already active

• REV has timed out

• REV is rejected by originator

• REV is rejected by network

MTR157 385


NN10275-909v14 12.01 06 October 2011


• Calling Directory Number (DN) is unavailable

• Answer time stamp is unavailable

• Originator line is COIN/Subscriber Private Metering (SPM)

• Terminator line is COIN/SPM

• Originator line is a Proprietary Phone (PPHONE)

• The call has been forwarded

• Selected Charge Record (SCR) is active at the originator side

• Printed Meter Check (PMC) is active at the originator side

• Resources are unavailable.

Remedial actionn/a


Severity Warning

FormatMTR157 mmmdd hh:mm:ss ssdd FAIL REV REQUEST

HOST nn n nn nn DN 102nnnnnnn

CALLED DR nnnnnnn

REV text

LNETWORK = MZONE nn n


VariableDescription

FAIL REV REQUEST Constant Fixed Indicates that the Reverse Chargingservice has failed.

HOST nn n nn nn Variable Identifies the agent that has theReverse Charging service.

DN nnnnnnn Variable Identifies the DN of the agent that hasthe Reverse Charging service.

CALLED DR nnnnnnn Variable Identifies the DN of the calling agent.

REV text Variable Text giving the reason for failure of theReverse Charging service.



NN10275-909v14 12.01 06 October 2011



Description

LNETWORK LOC, NAT or INTL Variable Identifies the logical network (LNET)of the agent that has the ReverseCharging service; local, national orinternational.

MZONE 0 to 63 Variable Identifies the metering zone (MZONE)of the agent that has the ReverseCharging service.

Active message exampleMTR157 JAN03 02:04:30 9844 FAIL REV REQUEST

HOST 00 0 00 19 DN 1027831001

CALLED DR 7831002

NO CALLING DN INFO AVAILABLE FOR:

LNETWORK = MZONE 63 0



MTR158The Log MTR158 feature, MOG Option Missing, does not allow a calloriginated by IBN or ISDNKSET LCC (Line Class Code) types if the MOGoption is not used. The log informs the operator that a call has beenattempted without the MOG option. The feature adds the obligation to usethe MOG option for meter line types for Turkish Telecom.

Remedial actionThe operator may receive the log where the value of theNO_CALL_WITHOUT_MOG parameter is Disallowed. This indicates thatthe originator does not have the MOG option. The operator can thenassign the MOG option to the line so that the call can be tried again.


Severity Warning

MTR158 387


NN10275-909v14 12.01 06 October 2011


FormatMTR158 mmmmdd hh:mm:ss INFO MOG OPTION MISSING

CPID of origination: <Host number>

DN of origination: <DN number>

Text about the call behaviour: <Constant>


VariableDescription

INFO MOG OPTIONMISSING

Constant Fixed Indicates that a call originated by IBNor ISDNKSET without the MOG optionis active.

CPID of origination Host number Variable Identifies the line CP_ID of theoriginator.

DN of origination DN number Variable Identifies the DN number of theoriginator.

Text about the callbehavior

Constant Fixed Indicates that a call goes to treatment.

Active message exampleMTR158 June 10 10:45:27 INFO MOG OPTION MISSING

HOST 01 0 10 06 DN 1027831023

CALL RESULT: TREATMENT



MTR159The Log MTR159, WRONG PASSWORD, is generated if the RESTOREcommand password has been entered incorrectly on 3 consecutiveoccasions.

Log history

ISN06 (TDM)

Log MTR159 was introduced by design activity A59039275.



NN10275-909v14 12.01 06 October 2011


Remedial actionMTR 159 log is for information purposes only. The craft person can contactNortel Networks ETAS Group to obtain the correct password.


Severity Warning

Format**MTR159 <mmmdd hh:mmm:ss ssdd> WRONG_PASSWORD

INCORRECT RESTORE PASSWORD IS ENTERED FOR

THREE TIMES

USER: <userid>


VariableDescription

<userid> may be any of theUSERIDs to whompermission is given

Variable this field gives the userid of the userwho entered the password wronglythree times

Active message exampleMTR159 JAN 14 08:00:06 7900 INFO WRONG_PASSWORD

INCORRECT RESTORE PASSWORD IS ENTERED FOR THREE TIMES

USER: ADMIN



MTRS100Log MTRS100 (metering component activation log) is generated when theoffice parameter ENABLE_METERING is changed from N to Y.

MTRS100 is a secret log type which is accessed by executing the''OPENSECRET MTRS'' command from LOGUTIL level and deleted onlyon reload restarts.

MTRS100 389


NN10275-909v14 12.01 06 October 2011


Remedial actionLog MTRS100 is an information log and requires no immediate action.


Severity Warning

FormatMTRS100 mmmdd hh:mm:ss SEQNO INFO METERING

FUNCTIONALITY IS ENABLED

USER: username


VariableDescription

mmmdd mmm = month dd =day


hh:mm:ss hh = hour mm =minutes ss = seconds

Variable Time of log generation. Also indicatesthe time that the test call is started.

SEQNO 4-digit number Variable Generating sequence number of thereport.

USER Character set Variable Login name of the user who runs thecommand.

Active message exampleMTRS100 JUN12 02:30:42 8100 INFO METERING FUNCTIONALITY IS

ENABLED

USER: ADMIN



MTRS101Log MTRS101 (metering component deactivation log) is generated whenthe office parameter ENABLE_METERING is changed from Y to N.



NN10275-909v14 12.01 06 October 2011


MTRS101 is a secret log type which is accessed by executing the''OPENSECRET MTRS'' command from LOGUTIL level and deleted onlyon reload restarts.

Remedial actionLog MTRS101 is an information log and requires no immediate action.


Severity Warning

FormatMTRS101 mmmdd hh:mm:ss SEQNO INFO METERING

FUNCTIONALITY IS DISABLED

USER: username


VariableDescription

mmmdd mmm = month dd =day


hh:mm:ss hh = hour mm =minutes ss = seconds

Variable Time of log generation. Also indicatesthe time that the test call is started.

SEQNO 4-digit number Variable Generation sequence number of thereport.

USER Character set Variable Login name of the user who runs thecommand.

Active message exampleMTRS100 JUN12 02:30:42 8100 INFO METERING FUNCTIONALITY IS

DISABLED

USER: ADMIN


MTRS101 391


NN10275-909v14 12.01 06 October 2011



NAOC200This log is generated when an invalid network advice of charge (AOC)message is received for a call originated by an AOC essential subscriber.

Remedial actionThis log provides the information that the charge determination point (CDP)has received an invalid network AOC message indicated in the Network ID.As a result, no immediate action within the subscriber network is required.

Inform the corresponding CDP network when an NAOC200 log shows thesame Network ID.



FormatNAOC200 mmmdd hh:mm:ss ssdd NAOC CGP CALL RELEASE

Calling Party Number: <cgpa>


Network ID: <netid>

Charging Reference ID: <chrgid>

Global Call ID: callid


VariableDescription

Calling Party Number digits Variable This field provides the calling partyaddress of the AOC-essentialoriginator.

Called Party Number digits Variable This field provides the address of thecalling party.

Network ID numeric Variable This field provides the network IDreceived for the invalid network AOCmessage from the CDP.



NN10275-909v14 12.01 06 October 2011



Description

Charging ReferenceID

numeric Variable This field provides the ChargingReference ID received for the invalidnetwork AOC message from the CDP.

Global Call ID numeric Variable This field provides the Global Call IDassigned to the call

Active message exampleNAOC200 FEB02 12:23:45 6789 NAOC CGP CALL RELEASE

Calling Party Number: 2227400020

Called Party Number: 02236961234

Network ID: 12345678

Charging Reference ID: 2234

Global Call ID: 406359



NAOC210This log generates when there is no network advice of charge (AOC)message received during call setup for a call originated by an AOC-essential subscriber.

Remedial actionThis log generates when a network AOC message has not been receivedfrom the charge determination point (CDP) during call setup. As a result,no immediate action within the subscriber network is required.

In the case that frequent NAOC210 logs occur, please check whichnetwork is responsible to provide the CDP function for that type of call.Inform the corresponding network.


Severity Warning

NAOC210 393


NN10275-909v14 12.01 06 October 2011


FormatNAOC210 mmmdd hh:mm:ss ssdd NO NAOC INFO RECEIVED


Called Party Number: <cdpa>

Global Call ID: callid


VariableDescription

Calling Party Number digits Variable This field provides the calling partyaddress of the AOC-essentialoriginator

Called Party Number digits Variable This field provides the called partyaddress

Global Call ID numeric Variable This field provides the Global Call IDassigned to the call

Active message exampleNAOC210 FEB02 12:23:45 6789 NO NAOC INFO RECEIVED



Global Call ID: 406359



NAOC220This log report can appear when the switch is converting Euro currencyvalues to meter pulses. This log applies only to DMS switches in Europe.

The log is generated if the internal conversion from Euros or Euro values,received in a Network Advice of Charge (NAOC) tariff message, to pulses(by division through datafill in table CURRCONV) leads to values thatexceed the maximum CGP limit. The CGP limit is 100 pulses per secondfor CRGT (cyclical) tariffs or 10 000 pulses for AOCRG charges. Thedatafill entry that pertains to the tariff values is in subfield EURO in tableCURRCONV.



NN10275-909v14 12.01 06 October 2011


Possible reasons for the log appearing are:

• The EURO tuple in table CURRCONV on the CGP switch has a ''0''value, is missing, or is datafilled with an illogically small value. Thus, areasonable tariff, received from the CDP in Euros, is mapped internallyto a very high CRGT tariff (for example, more than 100 pulses persecond) or to an unreasonable AOCRG charge (for example, morethan 10 000 pulses).

• If the Euro value in table CURRCONV contains proper datafill, eitherthe received value of a CRGT tariff in Euros or the AOCRG charges insubfield EURO are unreasonably high. In that case, contact the CDPgenerating the NAOC message to correct the CDP tariff datafill.

The log is generated for both essential and non-essential AOCsubscribers, and is one reason for a call being released from an essentialAOC subscriber.

The call release is indicated by log NAOC200.

Remedial actionLog NAOC220 appears if a NAOC message with a tariff has beenreceived, and the tariff is too high to be handled by the CGP.

The charges, received in Euros from the CDP, is divided internally by theCGP through the EURO value from table CURRCONV. If it exceeds eitherthe values of 100 pulses per second for cyclical tariffs, or 10 000 pulses forAOCRG charges, which are the highest possible limits, it is indicated bythis log.

If a NAOC220 log appears:

• Check the EURO value in table CURRCONV.

• Correct the EURO datafill if it''s missing, zeroed, or datafilled withillogically small values, leading to high tariffs in pulses per second (forcyclical tariffs) or pulses (for AOCRG charges).

• If table CURRCONV datafill is correct, check the network ID, displayedin the log. It identifies the CDP which is sending illogically high tariffs inEuros or Euros per second. Contact personnel at the CDP and advisethem that you are receiving unreasonably high tariff values in NAOCmessages.



NAOC220 395


NN10275-909v14 12.01 06 October 2011


FormatNAOC220 mmmdd hh:mm:ss ssdd NAOC MAX TARIFF EXCEEDED

Calling Party Number: cgpa

Called Party Number: cdpa

Network ID: netid


VariableDescription

cgpa numeric Variable The calling party address of the AOCessential originator,

cdpa numeric Variable The called party address.

netid numeric Variable The network ID of the CDP, receivedwith the NAOC message, containing ahigh tariff.

Active message exampleNAOC220 APR13 07:35:11 3927 NAOC MAX TARIFF EXCEEDED



Network ID: 12 34 56 78



NAOC600This log is generated to inform you that verification of the NAOC databasehas failed because of datafill errors.

Use the NAOCCI tool to investigate this log.

Remedial actionn/a



NN10275-909v14 12.01 06 October 2011



Severity Warning

FormatNAOC600 mmmdd hh:mm:ss ssdd NAOC DATABASE TRAVERSALINCOMPLETE

CALLING NUMBER

CALLED NUMBER

CIC

MCE

SCENARIO

ZONE CLASS


VariableDescription

CALLING NUMBER up to 24 digits Variable This is the originating directorynumber that is used to tariff for NAOC.

CALLED NUMBER up to 30 digits Variable This is the terminating directorynumber that is used to tariff for NAOC.

CIC up to 4 digits Variable This is the Carrier Identification Codethat is used to tariff for NAOC.

MCE PRESELECTED,CALL BY CALL,CALL BY CALLOVERRIDE, SPARE

Variable This is the value of the Multi-CarrierEnvironment parameter.

SCENARIO CDP, COMBINEDCGP/CDP,UNSUPPORTED

Variable This is the type of NAOC tariffing.

ZONE CLASS LOCAL, NATL, INTL,SERV

Variable This is the zone class used to tariff forNAOC. The classes are local,national, international, or service.

Active message exampleTCB4_LOG NAOC600 NOV30 12:00:00 1000 INFO NAOC DATABASETRAVERSAL INCOMPLETE

NAOC600 397


NN10275-909v14 12.01 06 October 2011


CALLING NUMBER : 72270

CALLED NUMBER : 0727270

CIC : 11

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

MCE : Preselected

SCENARIO : Combined CDP/CGP

ZONE CLASS : NATL Zone

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



NAOC610This log is generated when a combined charge generation point (CGP) andcharge determination point (CDP) on the same network node receives acharge message from a CDP on another network node. The charginginformation from the external CDP is discarded. The log indicates that atariff is generated internally, and that the tariff received from an externalCDP is discarded.

Remedial actionn/a


Severity Warning

FormatNAOC 610 mmmdd hh:mm:ss ssdd CGP/CDP: DUPLICATE TARIFFRECEIVED

CALLING NUMBER

CALLED NUMBER

GLOBAL CALL ID



NN10275-909v14 12.01 06 October 2011



VariableDescription

CALLING NUMBER up to 24 digits Variable This is the originating directorynumber.

CALLED NUMBER up to 30 digits Variable This is the terminating directorynumber.

GLOBAL CALL ID numeric Variable This the global call ID assigned to thecall.

Active message exampleTCB4_LOG NAOC610 NOV30 12:00:00 1100 INFO CGP/CDP:DUPLICATETARIFF RECEIVED

CALLING NUMBER : 7777527

CALLED NUMBER : 77775727000

GLOBAL CALL ID : 807192



NAOC620This log is generated when there is no carrier/reseller and TCO indexcombination in the TARFESTDX table and therefore no zone is found.

Enter a zone by providing datafill for at least one carrier/reseller and TCOindex combination in the TARFINDX table.

Remedial actionn/a


Severity Warning

FormatNAOC 620 mmmdd hh:mm:ss ssdd CARRSNAM/TCOINDX NOT IN TABLETARFINDX

CARRIER/RESELLER NUMBER

NAOC620 399


NN10275-909v14 12.01 06 October 2011


CARRIER/RESELLER NAME

TARIFF CHANGE OVER INDEX


VariableDescription

Carrier/resellernumber

0 to 79 Variable This is the number of the carrier orreseller.

Carrier/reseller name up to 8 characters Variable This is the name of the carrier orreseller.

Tariff change overindex

0 to 15 Variable This is the value of the tariff chargeover index.

Active message exampleTCB4_LOG NAOC620 NOV30 12:00:00 INFO CARRESNAM/TCOINDX NOTIN TABLE TARFINDX

Carrier Number : 0

Carrier Name : CAR01

Tariff Change Over Index : 7



NWM601The system generates this log for the application or removal of a pre-routepeg (PRP) code.

When the system generates this log for the application of PRP, the logindicates the control and the destination code.

When the system generates the log for the removal of PRP, the logindicates the control and destination code. The PEG field shows thenumber of calls the control counted. If a single command removes morethan one control, the system generates a log for each removed control.

Remedial actionn/a



NN10275-909v14 12.01 06 October 2011



Severity Warning

Format<officeid>NWM601 <mmmdd> <hh:mm:ss> <ssdd> INFO <prponoff>

<xlasys> <xlaname> <fromd> <tod>

PEG=<pegcount>


VariableDescription

PRPONOFF PRP_ON orPRP_OFF

Variable The value of this field is PRP_ONwhen the system applies the control toa destination code. The value of thisfield is PRP_OFF when the systemremoves the control from a destinationcode.

XLASYS AC, CT, FA, FT, NSC,OFC, or PX

Variable This field represents the translationsystem against which the systemdefines the control.

XLANAME Symbolic text Variable This field represents the translationsname in the translations systemagainst which the system defines thecontrol.

FROMD 0-999999999999999999

Variable This field represents the start of therange of destination codes to or fromwhich the system applies or removesthe control.

TOD 0-999999999999999999

Variable This field represents the end of therange of destination codes to or fromwhich the system applies or removesthe control.

PEGCOUNT 0-65535 Variable This field represents the number ofcalls the control counts. The maximumvalue of the control is 65535,regardless of the length of time.

Active message exampleECOME010BU NWM601 SEP24 15:20:05 5977 INFO PRP_ON

PX VPNXLA 602220380 602220380

NWM601 401


NN10275-909v14 12.01 06 October 2011


PEG=0

ECOME010BU NWM601 SEP24 15:28:13 0818 INFO PRP_OFF

PX VPNXLA 602220380 602220380

PEG=100



NWM602The system generates this log when the system applies or removes ahard-to-reach flag (HTRF) code control.

When the system generates this log for the application of HTRF, the logdescribes the control and the destination code.

When the system generates this log for the removal of HTRF, the logdescribes the control and the destination code. If a single commandremoves more than one control, the system generates a log for eachcontrol.

This log is for information purposes only.

Remedial actionn/a


Severity Warning

Format<officeid> NWM602 <mmmdd> <hh:mm:ss> <ssdd> INFO<htrfonoff;>

<xlasys> <xlaname> <fromd> <tod>



NN10275-909v14 12.01 06 October 2011



VariableDescription

HTRFONOFF HTRF_ON orHTRF_OFF

Variable The value HTRF_ON indicates thesystem applies the control. The valueHTRF_OFF indicates the systemremoves the control.

XLASYS AC, CT, FA, FT, NSC,OFC, PX


XLANAME Symbolic text Variable This field represents the translationsname in the translation system againstwhich the system defines the control.

FROMD 0-999999999999999999


TOD 0-999999999999999999


Active message exampleECOME010BT NWM602 SEP18 16:35:19 0516 INFO HTRF_ON

PX VPNXLA 602220022 602220024

ECOME010BT NWM602 SEP18 16:36:19 0819 INFO HTRF_OFF

PX VPNXLA 60222022 602220024



NWM603The system generates this log for the application or removal of the codeblocking (CBK) code control with call gapping. The BLK field displays thecount of calls that the system blocked. The ALLOW field displays the countof calls that the system passed.

When the system generates this log for the application of the control, thelog displays the control and the destination code.

NWM603 403


NN10275-909v14 12.01 06 October 2011


When the system generates this log for the removal of the control, the logdisplays the control and the destination code. If a single commandremoves more than one control, the system generates a log for eachcontrol.

This log is for information purposes only.

Remedial actionn/a


Severity Warning

Format<officeid> NWM603 <mmmdd> <hh:mm:ss> <ssdd> INFO <cbkonoff>

<xlasys> <xlaname> <fromd> <tod> GAP=<gggg> <ann>

BLK=<pegcount> ALLOW=<allowcount>


VariableDescription

CBKONOFF CBK_ON orCBK_OFF

Variable The value of this field is CBK_ONwhen the system applies the control toa destination code. The value of thisfield is CBK_OFF when the systemremoves the control from a destinationcode.

XLASYS AC, CT, FA, FT, NSCOFC, PX


XLANAME Symbolic text Variable This field represents the translationsname in the translation system againstwhich the system defines the control.

FROMD 0-999999999999999999


TOD 0-999999999999999999




NN10275-909v14 12.01 06 October 2011



Description

GGGG 0-6000 Variable This field represents the time gapwhich must elapse between calls. Thesystem measures the time gap indeci-seconds. When a call continues,the system blocks all other calls untilthe end of this time period.

ANN NAC, EA1, EA2 Variable This field represents the treatment thesystem applies to calls the controlblocked.

PEGCOUNT 0-65535 Variable This field represents the number ofcalls the control blocked. Themaximum value of this field is 65535,regardless of the length of time thecontrol is active.

PEGALLOW 0-65535 Variable This field represents the number ofcalls the control passed. Themaximum value of this field is 65535,regardless of the length of time thecontrol is active.

Active message exampleECOME010BT NWM603 SEP18 16:47:30 5765 INFO CBK_ON

PX VPNXLA 602220022 602220024 GAP=3.0 NCA

BLK=0 ALLOW=0

ECOME010BT NWM603 SEP18 16:47:43 6169 INFO CBK_OFF

PX VPNXLA 602220022 602220024 GAP=3.0 NCA

BLK=100 ALLOW=100



OCC213This log is generated when field TCN is not datafilled in table TCNFAST.The contents of the log contain the trouble code and the travel cardnumber (TCN) that was dialed.

OCC213 405


NN10275-909v14 12.01 06 October 2011


Remedial actionWhen log OCC213 is generated, a customer service report is issued.


Severity Warning

FormatOCC213 mmmdd hh:mm:ss ssdd INFO TCN IS NOT DATAFILLED

TRBCODE = <trbcode>

TCN = <tcn>


VariableDescription

trbcode TCN_IS_NOT_IN_TABLE_TCNFAST

Variable This field contains the trouble code.

tcn 8 to 18 digits Variable This field contains the travel cardnumber dialed that was not found intable TCNFAST.

Active message exampleRECS01AL OCC213 FEB21 14:37:29 5669 INFO TCN IS NOT

DATAFILLED

TRBCODE= TCN_IS_NOT_IN_TABLE_TCNFAST

TCN = 41234567891235



OCC230This log is generated when an invalid travel card number (TCN, or callingcard number) is entered.

Remedial actionWhen the OCC213 log is generated, a customer service report is issued.



NN10275-909v14 12.01 06 October 2011



Severity Warning

FormatOCC230 mmmdd hh:mm:ss ssdd INFO TRAVEL CARD NUMBER INVALID

TRBCODE = <trbcode>

TCN = <tcn>

ANI_SP = <ani_sp>

UNIV_AC = <univ_ac>

DIALD_NO = <diald_no>

ORG_GRP = <org_grp>

ORG_MEM = <org_mem>

ORG_DATE = <org_date>


VariableDescription

trbcode Variable Contains the contents of the troublecode

ten 8 to 18 digits Variable Contains the invalid entered travelcard number

ani_sp Variable

univ_ac Variable Access code

diald_no Variable Contains the dialed number

org_grp Variable Contains the originating trunk group

org_mem Variable Contains the originating member

org_date Variable Contains the date of the calling cardcall attempt

Active message exampleOCC230 FEB15 21:42:58 8852 INFO TRAVEL CARD NUMBER INVALID

TRBCODE = FIRST_TCN_ATTEMPT_INVALID

OCC230 407


NN10275-909v14 12.01 06 October 2011


TCN = 50015198989898

ANI_SP = 00

UNIV_AC = 600123456

DIALD_NO = 02142221234

ORG_GRP=1791

ORG_MEM = 0

ORG_DATE = 1997 2 15 21 42 49



PTP100This log is generated when an attempt to establish a Point-to-Point (PTP)call fails. The log shows the reason why the call establishment failed,according to the treatment. It also states whether the audit that tries againto establish this call is disabled or enabled.

Remedial action

• terminator busy -- The terminator is probably involved in another call.Decide which one you want to keep.

• dialing limitation -- The originator is not allowed to dial to the destnumber. Redefine it and reactivate.

• incorrect digits -- The test number is an invalid DN. Redefine it andreactivate.

• route not available -- The call can not be activated due to a problemsomewhere along the route. No action is required, the audit will try tore-establish the call periodically.


Severity Warning

FormatCPM1A * PTP100 MAY01 12:11:58 3100 INFO PTP CALL FAILURE



NN10275-909v14 12.01 06 October 2011


LEN <len>DN <dn>CALLED NO=<calledno>

REASON: <reason>

AUDIT: <audstate>


VariableDescription

LEN 15 characters Variable The LEN of the PTP line.

DN 7 characters Variable The DN of the PTP line.

CALLEDNO 7 characters Variable The destination number of the PTP.

REASON terminator busy,dialling limitation,incorrect digits, routenot available

Variable Describes the reason for the callfailure according to the treatmentreceived.

AUDSTATE stopped, running Variable Describes whether the audit that triesagain to establish the call is stillrunning or whether is was stopped.

Active message exampleCPM1A * PTP100 MAY01 12:11:58 3100 INFO PTP CALL FAILURE

LEN REM1 00 0 4 2DN 7224121 CALLED NO=7214422

REASON: incorrect digits

AUDIT: stopped



PTP101This log is generated when an established Point-to-Point (PTP) call isbroken. The log is produced by the audit. The audit tries to re-establishsuch a call.

Remedial actionn/a

PTP101 409


NN10275-909v14 12.01 06 October 2011



Severity Warning

FormatCPM1A * PTP101 MAY01 12:11:58 3100 INFO PTP CALL DIED

LEN <len>DN <dn>CALLED NO=<calledno>


VariableDescription

LEN 15 characters Variable The LEN of the PTP line.

DN 7 characters Variable The DN of the PTP line.

CALLEDNO 7 characters Variable The destination number of the PTP.

Active message exampleCPM1A * PTP101 MAY01 12:11:58 3100 INFO PTP CALL DIED

LEN REM1 0 0 4 2DN 7224121CALLED NO=7214422



QSIG100The QSIG100 log is generated when Non-call Associated Generic FunctionTransport (NCAGFT) call processing cannot allocate new Virtual Identifiers(VID).

Remedial actionn/a


Severity Warning

Format<log_office_id> mmmdd hh:mm:ss nnnn INFO All NCAGFT Sessionsare in Use



NN10275-909v14 12.01 06 October 2011


<ORIG Trunk CLLI Name>


VariableDescription

log_office_id 12 charactersmaximum

Variable Indicates the originating switch name.

ORIG Trunk CLLIName

16 charactersmaximum

Variable Indicates the originating trunkCommon Language Location Identifier(CLLI) name.

Active message exampleOTWAONXBDS0 QSIG100 JAN15 21:35:03 3200 INFO All NCAGFT

Sessions are in Use

MQSIGE1A01B



QSIG101The QSIG101 log is generated when call processing cannot allocate aHistory Data Block (HDB) for a QSIG call.

If the call is Call-associated, the call continues but GF gateway functionsare performed. For Non Call-associated calls, the call is rejected.

Remedial actionn/a


Severity Warning

Format<log_office_id> mmmdd hh:mm:ss nnnn INFO HDB Not Allocated

for QSIG GF Call


QSIG101 411


NN10275-909v14 12.01 06 October 2011



VariableDescription



ORIG Trunk CLLIName



Active message exampleOTWAONXBDS0 QSIG101 JAN15 21:35:03 3200 INFO HDB Not

Allocated for QSIG GF Call

MQSIGE1A01B



QSIG102The QSIG102 log is generated when the Generic Function Transport(GFT) control clears the call by Reject Application Protocol Data Unit(APDU).

Remedial actionn/a


Severity Warning

Format<log_office_id> QSIG102 mmmdd hh:mm:ss nnnn INFO Call ClearGFT Control




NN10275-909v14 12.01 06 October 2011



VariableDescription



ORIG Trunk CLLIName



Active message exampleOTWAONXBDS0 QSIG102 JAN15 21:35:03 3200 INFO Call Cleared byGFT Control

MQSIGE1A01B



QSIG103The QSIG103 log is generated when the number of intermediate transitnodes a SETUP message passes through exceeds the number defined bythe office parameter TRANSIT_COUNTER_LIMIT in table OFCENG.

Remedial actionn/a


Severity Warning

Format<log_office_id> QSIG103 mmmdd hh:mm:ss nnnn INFO Num oftransit nodes exceed TRANSIT_COUNTER_LIMIT in OFCENG

<ORIG Trunk CLLI Name> Total Hops = <hops>

QSIG103 413


NN10275-909v14 12.01 06 October 2011



VariableDescription



ORIG Trunk CLLIName



hops 1 to 31 Variable Indicates the actual number of transitnodes that the SETUP message hasalready passed through.

Active message exampleOTWAONXBDS0 QSIG103 JAN15 21:35:03 3200 INFO Num of transitnodes exceed TRANSIT_COUNTER_LIMIT in OFCENG

MQSIGE1A01B Total Hops = 6



QSIG104The QSIG104 log is generated when the originating and terminating trunksbelong to different customer groups causing a GF gateway condition. Forbearer-related QSIG terminations the call proceeds, but any Facility IEsand Notify IEs present are removed by the DMS before sending QSIGmessages for that call to the terminating trunk. For Non-call Associatedsignalling (non-bearer related) calls, the call is released.

Remedial actionn/a


Severity Warning

Format<log_office_id> mmmdd hh:mm:ss nnnn INFO Different CustomerGroups Encountered




NN10275-909v14 12.01 06 October 2011


<TERM Trunk CLLI Name>


VariableDescription



ORIG Trunk CLLIName



TERM Trunk CLLIName


Variable Indicates the terminating trunk CLLIname.

Active message exampleOTWAONXBDS0 QSIG104 JAN15 21:35:03 3200 INFO DifferentCustomer Groups Encountered

MQSIGE1A01B

MQSIGE1A01A



QSIG105The QSIG105 log is generated when the System Audit Facility finds andcorrects a mismatch in the Non Call-associated Generic FunctionTransport (NCAGFT) Virtual Identifier (VID) database. The audit runsapproximately every five minutes.

Remedial actionn/a


Severity Warning

Format<office_clli-name> QSIG105 mmmdd hh:mm:ss nnnn INFO NCAGFTVID Database Mismatch found and corrected

QSIG105 415


NN10275-909v14 12.01 06 October 2011



VariableDescription

Variable

Active message example250K_100E QSIG105 JAN15 21:35:03 3200 INFO NCAGFT VIDDatabase Mismatch found and corrected



QSIG106The Call Processing Audit Facility generates the QSIG106 log when it findsa QSIG non-call-associated signaling virtual identifier (VID) in an incorrectstate. The audit runs approximately every five minutes. The officeparameter AUDIT_INTERVAL in table OFCENG determines the frequencyof the audit.

Remedial actionIf log QSIG106 persists over an extended period of time, capture theswitch logs over several periods of the AUDIT_INTERVAL officeparameter. Escalate the problem and the switch logs to your next level ofsupport.


Severity Warning

Format<log_office_id> QSIG106 mmmdd hh:mm:ss nnnn INFO VID StateMismatch Corrected

Peripheral state mismatches corrected = xxxx

CM state mismatches corrected = yyyy

Number of VIDs Idled = zzzz



NN10275-909v14 12.01 06 October 2011



VariableDescription


Variable indicates the originating switch name

INFO VID statemismatch corrected

constant Fixed indicates QSIG virtual identifier statemismatches have been detected andcorrected

xxxx 0 to 32 767 Variable indicates the number of peripheralstate mismatches corrected

yyyy 0 to 32 767 Variable indicates the number of computingmodule state mismatches corrected

zzzz 0 to 32 767 Variable indicates the total number of virtualidentifiers idled

Active message exampleOTWAONXBDS0 QSIG106 AUG05 14:06:46 9500 INFO VID StateMismatch Corrected

Peripheral state mismatches corrected = 10

CM state mismatches corrected = 2

Number of VIDs Idled = 12



QSIG107The QSIG107 log is generated when the supplementary services use anundefined component.

Remedial actionn/a


Severity Warning

QSIG107 417


NN10275-909v14 12.01 06 October 2011


Format<log_office_id> QSIG107 mmmdd hh:mm:ss nnnn INFO BadSupplementary Services Component




VariableDescription



ORIG Trunk CLLIName



TERM Trunk CLLIName



Active message exampleOTWAONXBDS0 QSIG107 JAN15 21:35:03 3200 INFO BadSupplementary Services Component

MQSIGE1A01B

MQSIGE1A01A



QSIG108The QSIG108 log is generated when corrupt data is detected in at leastone Application Protocol Data Unit (APDU).

Remedial actionn/a


Severity Warning



NN10275-909v14 12.01 06 October 2011


Format<log_office_id> QSIG108 mmmdd hh:mm:ss nnnn INFO Bad orIncomplete Supplementary Services Data




VariableDescription



ORIG Trunk CLLIName



TERM Trunk CLLIName



Active message exampleOTWAONXBDS0 QSIG108 JAN15 21:35:03 3200 INFO Bad orIncomplete Supplementary Services Data

MQSIGE1A01B

MQSIGE1A01A



QSIG109The QSIG109 log is generated when no more datastore is available for theincoming Information Elements (IE).

Remedial actionn/a


Severity Warning

QSIG109 419


NN10275-909v14 12.01 06 October 2011


Format<log_office_id> QSIG109 mmmdd hh:mm:ss nnnn INFO IE Lost DueTo IE Buffer Exhaustion



VariableDescription



ORIG Trunk CLLIName



Active message exampleOTWAONXBDS0 QSIG109 JAN15 21:35:03 3200 INFO IE Lost Due ToIE Buffer Exhaustion

MQSIGE1A01B



RBP100Log RBP100 is generated when a Ring Back Price (RBP) call has ended.

This log report is defined in module RBPLOGE.

Remedial actionAfter receiving the RBPLOG, the subscriber is advised, in a separate callfrom an operator, of the price that is applicable for that call. This pricinginformation is manually obtained from the call charge information (thebegin time of call and its duration) and is given to a special operatorposition by a new log, with the applicable service fees.


Severity Warning

FormatCONNECT TIME = <Connect_Time>



NN10275-909v14 12.01 06 October 2011


ELAPSED TIME = <Elapsed_Time>

CALLING DN = <CALLING_DN>

CALLED DN = <CALLED_DN>


VariableDescription

CONNECT TIME Valid Time Variable The time when the call started.

ELAPSED TIME Valid Time Variable The time of the call (exit time -connect time).

CALLING DN SNPA + DN Variable The DN of the call originator.

CALLED DN DN Variable The DN of the call terminator.

Active message exampleCAP7B RBP100 JUN23 11:01:24 2700 INFO RBPCONNECT TIME =1101197

ELAPSED TIME = 00000035

CALLING DN = 3321002

CALLED DN = 600004



SFPS100This log is generated when a user enters an invalid password three timeswhile trying to enter the Load Fixed Price Service (LPFS) level below theFPS level of the command interface (CI).

Log history

ISN06 (TDM)

Log SFPS100 was introduced by design activity A89007209.

Remedial actionSFPS100 is an information log and so requires no immediate action.

SFPS100 421


NN10275-909v14 12.01 06 October 2011



Severity Warning

Format** SFPS100 <mmmdd hh:mmm:ss ssdd> INFO WRONG PASSWORD

Incorrect LFPS Password is entered for three times.

USER: <USERNAME>


VariableDescription

USER Username Variable The login name of the user who ranthe command

Active message example** SFPS100 APR03 13:40:13 0100 INFO WRONG PASSWORD

Incorrect LFPS Password is entered for three times.

USER: OPERATOR1



SM21300The Services Application Module Element Manager (SAM21EM), a pieceof the software on the SNM, gets events from the SAM21. The SAM21EMtranslates an event into the SDM log format and delivers it to the SDMlogging system. These logs appear in the ''custlog'' file under the ''/usr/adm'' directory on the SDM.

Log report SM21300 reports all types of alarms and faults on the SAM21.

Remedial actionn/a



NN10275-909v14 12.01 06 October 2011



Severity • Major

• Critical

• Minor

Format<Log name> <Log number> <Alarm value> <Event type> <Label>

<Log body>


VariableDescription

log name alpha-numeric (aann) Variable The log name for logs coming fromthe SAM21EM is SM21.

log number numeric (nnn) Variable The SAM21EM defines the lognumber based on the log category.

alarm value critical, major or minor Variable This field describes what kind of alarmhas occurred.

event type FLT Variable Associated with log category.

label Fault Variable Short description of the event.

log body Variable Provides additional event informationsuch as location, time, status andreason.

Active message exampleSM21300 MAJOR FLT Fault

Location: SAM21 1:chassis 1:shelf 1:slot 7:card 1

Time: Tue Jun 06 07:54:33 EDT 2000

Status: Alarm Raised

Reason: Loss of Communications: Remote Network Unreachable

Jun 06 07:54:55 SAIN1SDM syslog:


SM21300 423


NN10275-909v14 12.01 06 October 2011




Log report SM21500 reports all state changes on the SAM21.

Remedial actionn/a


Severity Warning

Format<Log name> <Log number> <Alarm value> <Event type> <Label><Log body>


VariableDescription



alarm value NONE Variable The alarm value is not applicable forthis log. It is always identified asNONE.

event type INFO Variable This field describes the event. In thiscase, the event is for information only.

label State Change Variable This field provides a short descriptionof the event.

log body Variable This field provides additional eventinformation such as location and newstate. The Administrative state can belocked or unlocked. The Operationalstate can be Enabled or Disabled. TheUsage state can be active or inactive.



NN10275-909v14 12.01 06 October 2011


Active message exampleSM21500 NONE INFO State Change


New state: Unlocked/Disabled/Inactive





Log report SM21501 reports all card insertions into the SAM21.

Remedial actionn/a


Severity Warning



VariableDescription




SM21501 425


NN10275-909v14 12.01 06 October 2011



Description

event type INFO Variable This field describes the event. In thiscase, the event is for information only.

label Card insertion Variable This field provides a short descriptionof the event.

log body Variable This field provides additional eventinformation such as the location.

Active message exampleSM21501 NONE INFO Card Insertion





SM21502The SAM21EM, a software on the SNM, gets events from the SAM21. TheSAM21EM translates an event into the SDM log format and delivers it tothe SDM logging system. These logs appear in the ''custlog'' file under the''/usr/adm'' directory on the SDM.

Log report SM21502 reports all card removals from the SAM21.

Remedial actionn/a


Severity Warning




NN10275-909v14 12.01 06 October 2011



VariableDescription




event type INFO Variable This field describes the event. In thiscase the event is for information only.

label Card removal Variable This field provides a short descriptionof the event.

log body Variable This field provides additional eventinformation such as the location.

Active message exampleSM21502 NONE INFO Card removal





SMDR100Log SMDR100 is generated when either of the following events occur:

• More than 256 bytes of formatted data is required to be processed forthe call.

• The call has produced more station message detailed recording(SMDR) billing extension records than it is allowed.

After this log is generated, no more SMDR records are generated for thecall. Additional billing information for the call is lost.

Remedial actionThere is no immediate action required. The called and calling numbers areincluded in this log to associate them with the SMDR record that containsincomplete data.

SMDR100 427


NN10275-909v14 12.01 06 October 2011



Severity Warning

FormatSMDR100 mmmdd hh:mm:ss ssdd INFO SMDR Information

CALLING ID = <subscriber_clid>

CALLED ID = <called_dn>

TEXT = <reason_text>


VariableDescription

INFO SMDRInformation

constant Fixed Specifies that this is an information-only log that contains information forSMDR billing.

Calling ID 1 to 18 numericcharacters

Variable Contains the network calling lineidentifier (CLID) specified in fieldNETWORK CLID of the extensionrecord DA of the associated call.

This field contains up to 18 digits andis left justified. If all characters are notused, the field is filled with asterisks(*).

If the CLID is not available, the fieldcontains all asterisks (*).

Called ID 1 to 30 numericcharacters

Variable Contains the called numbers specifiedin the CLD NO field in the D1 or D3records of the associated call.

This field contains up to 30 digits andis left justified. If all characters are notused, the field is filled with asterisks(*).

Text alphanumericcharacter string

Variable Specifies the reason the log wasgenerated. Any of the following valuesmay appear in this field:

• DF05 count exceeded. LogSMDR100 is generated whenmore than ten DF05 records are



NN10275-909v14 12.01 06 October 2011



Description

produced for a call. No moreDF05 records are processed forthe call after the log is generated.

• DF06 count exceeded. LogSMDR100 is generated whenmore than three DF06 records areproduced for a call. No moreDF06 records are processed forthe call after the log is generated.

• DF07 count exceeded. LogSMDR100 is generated whenmore than six DF07 records areproduced for a call. No moreDF07 records are processed forthe call after the log is generated.

• SMDR overflow while generatingDF05. Log SMDR100 isgenerated if more than 256 bytesof formatted data is required to beprocessed for the call.



Active message exampleSMDR100 AUG14 18:14:33 6400 INFO SMDR Information

CALLING ID = 3119233200********

CALLED ID = 5689057704333*****************

TEXT = DF05 count exceeded


SMDR100 429


NN10275-909v14 12.01 06 October 2011



SPL101This log is generated when the limit of the allowed incorrect attempts ofpassword dialing is reached. It includes the originator''s LEN, DN and thelast password dialed.

Remedial actionn/a


Severity Warning

Format{NC_ALARM, $INFO, ''SPL_AUTHC_FAIL'', 0,

''&/ORIG = &C AUTHC DIALED = &!"DIGIT_REGISTER" '',

101};


VariableDescription

report label SPL_AUTHC_FAIL Variable This field explains the reason the loghas been produced.

originator LEN andDN

LEN HOST Variable This field displays the LEN and DN ofthe originator.

DN Variable This field displays the DN of theoriginator,

last dialed password 4 digits (numeric) Variable This field displays the last dialedpassword.

Active message exampleSPL101 JUN24 02:09:28 9700 INFO SPL_AUTHC_FAIL

ORIG = LEN HOST 00 0 00 01 DN 3344001 AUTHC DIALED = 8888




NN10275-909v14 12.01 06 October 2011



TEST101In Trunk Test Position (TTP) level of the MAP terminal, a call can bemonitored using MONPOST, MONLINK, MONTALK and MONBOTHcommands. TEST101 log report is generated to indicate that thesecommands are used.

An intervention tone provided through trunks informs only the subscriber atthe end-office that the call is monitored by these monitoring commands.

MONPOST command

This command sets up a connection between the headset of the TTPcommunications device and the circuit in the control position. It establishesa connection for listening to incoming transmission of the posted circuit. Ananalog monitoring connection is established when MONPOST commandwithout a parameter is used in the MONITOR level.

MONLINK command

This command sets up a connection between the headset of the TTPcommunications device and the circuit that is linked to the circuit in thecontrol position. It enables a user to listen to the incoming transmission ofthe linked circuit. Analog monitoring connection is established whenMONLINK command without a parameter is used in the MONITOR level.

MONTALK command

This command establishes a three-party analog conference circuitconnection including the circuit in the control position, the circuit linked to it,and the headset (hset) of the trunk test position (TTP). The connectionsare set up using a three-port conference circuit.

MONBOTH command

This command sets up a connection between the headset of the TTPcommunications module and the trunk in the control position. Thisconnection enables the user to listen to the incoming and outgoingtransmission of the posted trunk.

For all monitoring commands in the MONITOR level, the trunk to bemonitored is posted and should be in CPB or CPD state. There should bea circuit which is linked to the trunk to be monitored. When the call-processing connection is taken down, the monitor connections arereleased.

TEST101 431


NN10275-909v14 12.01 06 October 2011


Remedial actionTEST101 log report is for information only and therefore requires noimmediate action.



FormatTEST101 <DATE><TIME><SEQNO>RBSY MONITOR

USER : <USERNAME>

TRUNK NAME: <TRUNK NAME>


VariableDescription

DATE 3 characters formonth and 2 digit forday

Variable log generation date

TIME 6 digit<hh:mm:ss< Variable log generation time, also indicates thetime the monitor is started

SEQNO 4 digit number Variable generation sequence number report

USER Character set Variable user login name

TRUNK NAME Character set for CLLIname and digit(s) forexternal trunk name

Variable monitored CLLI name of the trunk

Active message exampleTEST101 MAR08 09:45:50 5400 RBSY MONITOR

USER : ADMIN

TRUNK NAME : OGISUPAB 1




NN10275-909v14 12.01 06 October 2011



TIV102The Line Maintenance (LINE) subsystem generates log report TIV102when a call routes to a treatment. A call routes to treatment for differentreasons.

Equal access (EA) Generic Services Framework (GSF) software does notsupport log report TIV102. If this software generates log report TIV102, thereport can contain information that is not correct.

Remedial actionCheck the LINE log report buffer for problem reports on the same lineequipment. Follow the Action to take for trouble reports generated.


Severity Warning

Formatreportid mmmdd hh:mm:ss ssdd officeid

len DN dn

TREATMENT SET = treatment CALLED NO = dn

CALLID = callid


VariableDescription

INFO TRMT Constant Fixed Indicates the assignment of atreatment to the originating line

len Symbolic text Variable A seven-digit number identifyingphysical location data on equipment,such as site, frame number, unitnumber, line subgroup (shelf), andcircuit pack, (line equipment number)

DN dn Symbolic text Variable The full complement of digits requiredto designate a subscriber's stationwithin one numbering plan area,(directory number)

TREATMENT SET Symbolic text Variable Provides treatment assigned to theline

TIV102 433


NN10275-909v14 12.01 06 October 2011



Description

CALLED NO Symbolic text Variable Provides terminating line directorynumber

CALLID Symbolic text Variable A number that identifies the caller

REPORTID Symbolic text Variable Indicates the current log id

MMMDD Symbolic text Variable Indicates the month and day thesystem generated the report

HH:MM:SS Symbolic text Variable Identifies hour, minute and second thesystem generated the report

SSDD Symbolic text Variable Defines the sequence number foreach log report that the systemgenerated. The SS increases whenthe system generates a report and isreset to 00 after the SS reaches 99.The DD increases when a reportappears at a given device and is resetto 00 after the DD reaches 99.

OFFICEID Symbolic text Variable Identifies the switch that generates thelog. This field is optional. Maximumlength of this field is 12 characters.Office parameter LOG_OFFICE setsthe length.

Active message exampleTIV102 APR01 12:00:00 2112 INFO TRMT

HOST 00 0 19 20 DN 2557811999

TREATMENT SET = MANL CALLED NO = $

CALLID = 123456



TIV103The Trunk (TRK) Maintenance subsystem generates log report TIV103.The subsystem generates TIV103 when it sends a call to a treatment afterbeing call processing busy.



NN10275-909v14 12.01 06 October 2011


Remedial actionCheck TRK log report buffer for trunk problem report(s) with the sameoriginating trunk circuit or trunk group. Follow the actions advised for thetrouble reports the subsystem generates.

A TRKT205 log report generates when a DMS500 call is routed to atreatment after being call processing busy.


Severity Warning

Formatreportid mmmdd hh:mm:ss ssdd INFO TRMT

CKT trkid

TREATMENT SET = trtnm CALLED NO = dn

CALLID = callid


VariableDescription

INFO TRMT Constant Fixed Indicates treatment assigned tooriginating trunk.

CKT Symbolic text Variable Indicates originating trunk equipment.See Table I in the Understanding logreports section of Volume 1 of the LogReport Reference Manual .

TREATMENT SET Symbolic text Variable Indicates treatment assigned to trunk.Refer to table M.

CALLED NO Integers Variable Provides terminating line directorynumber if you dial before treatmentassigned. This field can be a LocationRouting Number (LRN) See table I.

CALLID Integers Variable Indicates the callid. See table I.

Active message exampleTIV103 APR01 12:00:00 2112 INFO TRMT

CKT RTP2W 0

TREATMENT SET = BLDN CALLED NO = 2122201234

TIV103 435


NN10275-909v14 12.01 06 October 2011


CALLID = 123456



TIV117This log is a sampling of local automatic message accounting (LAMA) callson a switch. This sampling is done to prevent the printing of too many logson the monitor.

When the parameter ENABLE_TLR_BILLING is turned ON in tableAMAOPTS, calls which are treated before being answered do not generateTIV117 logs. If the call is successfully established but disconnected beforeanswer (unanswered call), then this log will be pegged as well as theanswered call.

The number of events is calculated according to office parameterTIV_STATISTIC_FILTER, defined in table OFCENG.

This log applies to the Israeli market only.

History

ISN07 (TDM)

Table history added.

Log TIV117 expanded and updated for CR Q00874034.

Remedial actionn/a


Severity Warning

FormatTIV117 mmmdd hh:mm:ss ssdd INFO AMA RECORD DATA

STRUCTURE CODE = aaaaaCALL CODE = bbb

CONNECT DATE = cccccCONNECT TIME = hhmmssd



NN10275-909v14 12.01 06 October 2011


ELAPSED TIME = ssssssssANSWERED = YES/NO

CALLING DN = dn

ORIG AGENT = CKT clli

CALLED DN = dn

TERM AGENT = CKT clli


VariableDescription

STRUCTURE CODE Integers Variable Identifier that defines the content andorder of the AMA record.

CALL CODE Integers Variable Indicates the call code. BellcoreFormat Automatic MessageAccounting Reference Guide,297-1001-830, contains the call codesfor BCFMT office.

CONNECT DATE Integers Variable Gives the date when the connectionfor this call was set up. The format isyymmdd (y=year, m=month, d=day).

CONNECT TIME Integers Variable Gives the time when the connectionfor this call was set up. First andsecond digits indicate hours, third andfourth digits indicate minutes, fifth andsixth digits indicate seconds, and thelast digit indicates milliseconds

ELAPSED TIME Integers Variable Duration of call in seconds

ANSWERED YES or NO Variable Indicates if the call was answered.

CALLING DN Symbolic text, up to18 digits

Variable Indicates calling number.

ORIG AGENT Symbolic text Variable Identifies the CLLI and circuit numberfor the originating circuit. Theoriginating agent can also be a line,identified by LEN and DN, attendantconsole, which is identified bycustomer group and console name, ora VFG identified by name andmember number.

TIV117 437


NN10275-909v14 12.01 06 October 2011



Description

CALLED DN Symbolic text, up to18 digits

Variable Identifies called number.

TERM AGENT Symbolic text Variable Identifies the CLLI and circuit numberfor the terminating circuit. This fieldcan also contain a line equipmentnumber (LEN) and a directory number(DN).

Active message exampleTIV117 JUL04 14:23:35 6900 INFO AMA RECORD DATA

STRUCTURE CODE = 40510 CALL CODE = 006

CONNECT DATE = 70704 CONNECT TIME = 1423344

ELAPSED TIME = 00098182 ANSWERED = YES

CALLING DN = 9197828826

ORIG AGENT = LEN HOST 30 0 04 00 DN 8114007

CALLED DN = 800555121212121212121212121212

TERM AGENT = CKT KNGA200BTBWE



TIV118This log applies to the Israeli market only.

This log is a sampling of centralized automatic message accounting(CAMA) calls on a switch. This sampling is done to prevent the printing oftoo many logs on the monitor.

When the parameter ENABLE_TLR_BILLING is turned ON in tableAMAOPTS, calls which are treated before being answered do not generateTIV118 logs. If the call is successfully established but disconnected beforeanswer (unanswered call), then this log will be pegged as well as theanswered call.



NN10275-909v14 12.01 06 October 2011


The number of events is calculated according to office parameterTIV_STATISTIC_FILTER, defined in table OFCENG.

CHARGE DETAILS (digit 1)

• 0 -- Indicates the call is chargeable and manual "no charge" overridedid not occur.

• 1 -- Indicates the call is not chargeable and manual "no charge"override did not occur.

• 2 -- Indicates the call is chargeable and manual "no charge" overrideoccurred.

• 3 -- Indicates the call is not chargeable and manual "no charge"override occurred.

• 4 -- Indicates that the call is chargeable but the subscriberdisconnected before connection to an Audio Response Unit.

• 5 -- Indicates the call is not chargeable but the subscriber disconnectedbefore connection to an Audio Response Unit.

TRANSFER AND TROUBLE DETAILS (digit 2)

• 0 -- Indicates the call did not transfer and a problem reported.

• 1 -- Indicates a transferred call.

• 2 -- Indicates a call with a problem reported.

• 3 -- Indicates a transferred call with a problem reported.

CALL ORIGINATION TYPES

• 00 -- Unspecified.

• 01 -- Indicates a Local Directory Assistance call (the subscriber dialed411).

• 02 -- Indicates a HNPA DA call (the subscriber dialed 1+555-1212).

• 03 -- Indicates a FNPA DA call (the subscriber dialed l+NPA+555-1212)

• 04 -- Indicates a traffic operator dialed 131 to ask for assistance froman AOSS operator.

• 05 -- Indicates a traffic operator dialed 141 to obtain rate and routeinformation from an AOSS operator.

• 06 -- Indicates a call an AOSS operator intercepts.

• 07 -- Indicates an ACS operator keys to access a forward number.

Table history

TIV118 439


NN10275-909v14 12.01 06 October 2011


ISN07 (TDM)

Table history added.

Log TIV118 expanded and updated for CR Q00874034.

Remedial actionAction not required.


Severity Warning

FormatTIV118 mmmdd hh:mm:ss ssdd INFO AOSS VR CALL ENTRY

B8 ec ce sf dn fwddn day hhmmss oprn tn ct co n chd


VariableDescription

INFO AOSS VR CALLENTRY

Constant Fixed Indicates a report of data associatedwith the AOSS Voice Responsesystem.

B8 Constant Fixed Identifies an AOSS VR CALL ENTRYrecord type.

ec 00-99 Variable Identifies the entry code.

ce (0-7), (0-7) Variable Indicates call event Information. Digitone is on the left. Refer to Table Callevent information in log reportAMAB100.

sf (0-7), (0-7) Variable Indicates service features of callingparty (left digit) and the forward party(right digit). Refer to Table Servicefeatures in log report AMAB100.

dn Symbolic text Variable Identifies calling number.

fwddn 2-10 digits Variable Identifies the forward or requestednumber the operator enters.

day 1-366 Variable Indicates the day of the year on whichthe call arrived at the AOSS position.

hhmmss 000000-235959 Variable Indicates the time of the day when thecall arrived at the AOSS position.



NN10275-909v14 12.01 06 October 2011



Description

oprn 0000-9999 Variable Identifies AOSS operator handling thecall.

tn 00-99 Variable Identifies the team that the systemassigns to the AOSS operator.

ct (0-5), (0-3) Variable Provides charge, transfer, and troubleinformation about the AOSS call thesystem handles. Digit 1 (left)represents charge details. Refer toCHARGE DETAILS. Digit 2represents transfer and troubledetails. Refer to TRANSFER ANDTROUBLE DETAILS.

co 00-07 Variable Indicates origination manner of a callto an AOSS operator. Refer to CALLORIGINATION TYPE.

n 0 Variable Indicates the call is not a recall nor acut-through.

1 Variable Indicates a call the operator recalls.

2 Variable Indicates a call cut through to theoperator.

chd 0-255 Variable Indicates downstream chargedetermination.

Active message exampleTIV118 MAY11 12:23:52 2112 INFO AOSS VR CALL ENTRY

B8 00 24 00 321234 62177 003 094032 0212 02 00 01 1 057



TKCV101TKCV101 log is generated when a failure occurs during an automatic trunkconversion process. One log is generated for each failure.

Remedial actionExamine the log and manually return to service (RTS) the trunks that weresuccessfully converted. For records of TKCVDATA that failed theconversion, determine the cause of the failure. To convert those ISDN user

TKCV101 441


NN10275-909v14 12.01 06 October 2011


part (ISUP) trunks back to per-trunk signaling (PTS) trunks, execute theCVPOST and UNDO commands at the TRKCONV level of the MAPdisplay.


Severity Warning

FormatTKCV101 mmmdd hh:mm:ss <log no.> INFO AUTO TRKCONV TRBL

CKT = <clli ckt no.>

RECORD NUMBER = <tkcvdata rec no.>

REASON = <string>


VariableDescription

INFO AUTOTRKCONV TRBL

Constant Fixed Indicates trunk conversion trouble.

CKT Symbolic text Variable Provides the equipment identificationfor suspect trunk equipment where thefailure occurred.

Variable Only single-circuit failures aredisplayed.

RECORD NUMBER Integer Variable Indicates the record number of theTKCVDATA table in which the failureoccurred.

REASON Character string Variable Indicates the reason for the failure.

Active message exampleTKCV101 NOV25 02:30:15 8200 INFO AUTO TRKCONV TRBL

CKT PTSOGGA 1

RECORD NUMBER = 1

REASON = Cannot change state to MB




NN10275-909v14 12.01 06 October 2011



TKCV102TKCV102 log is generated when a failure occurs during an automatic trunkconversion process due to one of the following reasons:

• datafill changes complete

• continuity test passed

TKCV102 log with reason "Datafill changes complete" is generated when aTKCVDATA record is successfully converted by the automatic trunkconversion process when a no continuity test was requested.

TKCV102 log with reason "Continuity test PASSED" is generated for eachtrunk in a TKCVDATA record that passes the continuity test. A value forthe CKT field is displayed where a continuity test passed log is generated.

Remedial actionExamine the log and manually return to service (RTS) the trunks that weresuccessfully converted. For records of TKCVDATA that failed theconversion, determine the cause of the failure. To convert those ISDN userpart (ISUP) trunks back to per-trunk signaling (PTS) trunks, execute theCVPOST and UNDO commands at the TRKCONV level of the MAPdisplay.


Severity Warning

FormatTKCV102 mmmdd hh:mm:ss <log no.> INFO AUTO TRKCONV PASS

CKT = <clli ckt no.>

RECORD NUMBER = <tkcvdata rec no.>

REASON = <string>

TKCV102 443


NN10275-909v14 12.01 06 October 2011



VariableDescription

CKT Symbolic text Variable Provides the equipment identificationfor suspected trunk equipment wherethe failure occurred.

RECORD NUMBER Integer Variable Indicates the record number of theTKCVDATA table in which the failureoccurred.

REASON Character string Variable Indicates the reason for the failure.

Active message exampleTKCV102 NOV25 02:30:15 8200 INFO AUTO TRKCONV PASS

RECORD NUMBER = 1

REASON = Datafill changes complete



TOPS303This log is generated when the TOPS switch receives an intelligentnetwork (IN) operator backup call and the IN Fall Back SOC ENSV0023state is IDLE.

History

TOPS11

This log was created by feature AF7805 in functionality IN Fall Back,ENSV0023.

Remedial actionCheck the SOC state and set to ON if applicable. Otherwise, check if thesending switch should be sending IN operator backup calls to the TOPSswitch. Refer to functionality IN Fall Back, ENSV0023 in the applicablemanual as follows:

• NA DMS-100 Translations Guide, 297-8021-350

• GTOP DMS-100 Translations Guide, 297-8441-350



NN10275-909v14 12.01 06 October 2011




FormatTOPS303 mmmdd hh:mm:ss ssdd TBL IN Operator Backup SOC NOTON

INCOMING TRK = <clg circuit id>


VariableDescription

INCOMING TRK CLLI from ISUPTRK Variable Calling party trunk CLLI identifier.Refer to table ISUPTRK.

Active message exampleTOPS303 JUN08 18:30:20 8701 TBL IN Operator Backup SOC NOTON

INCOMING TRK = CKT ISUPIP11



TOPS614This log indicates that a message from a position or over an OC link hasbeen received by the switch with an invalid IP address. That is, an addresswhich does not correspond to the switch''s current notion of the correctaddress.

Remedial actionThis log represents a possible security violation or improper datafill. Assuch, the source of the faulty IP address should be investigated todetermine whether any further action is necessary.


Severity Warning

TOPS614 445


NN10275-909v14 12.01 06 October 2011


FormatTOPS504 <Date> <Time><Sequence Numbers> INFO TOPS Msg IPAddr Mismatch

Source ID = <pos id | oc data link>

Expected Addr = <ip address>

Msg Addr = <ip address>


VariableDescription

Date mmmdd Variable This field indicates the month anddate the log was generated.

Time hh:mm:ss Variable This field display the time in hours (24hour clock), minutes, and secondsthat the log was generated.

Sequence Numbers ssdd Variable This field defines a unique sequencenumber for each log report generated.

Source ID TOPSPOS<positionnumber>or OC officename and data link

Variable The source of the received message.

Expected Addr 4 sets of numbers,each in the range of 0to 255

Variable The IP address of the position or OCdatalink as the switch expects.

Message Addr 4 sets of numbers,each in the range of 0to 255

Variable The IP address of the source of themessage.

Active message exampleTOPS 614 DEC03 18:30:02 2112 INFO TOPS Msg IP Addr Mismatch

Source ID = TOPSPOS 500

Expected Addr = 47 192 5 216

Msg Addr = 47 103 23 95




NN10275-909v14 12.01 06 October 2011



TRK255Operators can restrict trunk-to-trunk calls by using Class Of Service (COS)screening. The COS values of the originating and terminating trunks areused to determine whether a call is allowed or restricted.

Also, operators can prevent trunk-to-trunk calls from being routed back tothe incoming trunk by using trunk loop prevention.

Log TRK255 indicates that a trunk-to-trunk call has been restrictedbecause of COS screening or trunk looping.

When this log is generated, the operator must:

• Verify that table TRKOPTS has a COS or LOOPBACK option for therelevant trunk groups.

• If the COS option is datafilled against the trunk groups, verify that theCOS combination is datafilled in table COSBLK.

If COS screening is not required, remove the COS option that is datafilledagainst the trunk groups.

Remedial actionNone immediately. See the Additional information for instructions for theoperator.


Severity Warning

FormatTRK255 mmmdd hh:mm:ss ssdd INFO DATA BASE TRBL

<agent ID of originator>

TRBCODE = CLASS_OF_SERVICE_BLKD OUTGTRK = <agent ID ofterminator>

CLDNO = <Called Number> CALLID = <CALLID>

TRK255 447


NN10275-909v14 12.01 06 October 2011



VariableDescription

INFO DATA BASETRBL

Constant Fixed Indicates a problem in a networkservices software feature group D call.

TRBCODE CLASS_OF_SERVICE_BLKD

Variable Explains why the current route isrestricted. This message is the samefor trunk looping and COS screening.

OUTGTRK Symbolic text Variable Identifies the CLLI for the outgoingtrunk.

CLDNO Symbolic text Variable Identifies the called directory number,before routing. Refer to dn in table 9.

CALLID Integers Variable Indicates the callid. Refer to table 9.

Active message exampleTRK255 AUG18 16:17:35 0800 INFO DATA BASE TRBL

CKT KNGA201BTWBE 1

TRBCODE = CLASS_OF_SERVICE_BLKD OUTGTRK = CKT KNGA201BTWBE 1

CLDNO = 4102 CALLID = 789006335



TRK353The Digital Private Network Signaling System (DPNSS) No. 1 generateslog report TRK353 if the value of the Type of Answer (TOA) field is in theinvalid range, 2 - 15. The TOA value is checked when a UK variant ofnational User Part (BTUP) answer message (ANM) is received by aperipheral module (PM).

The call will be treated automatically as if it were a chargeable call(TOA=1).

Remedial actionNone. The call is treated automatically.



NN10275-909v14 12.01 06 October 2011



Severity Warning

FormatCENTREX TRK353 mmmdd hh:mm:ss ssdd INFO TUP TRK FEAT TRBL

CKT TRKID

REPORTING CKT reporting TRKID

REASON = RSNTXT

DATA = TOA#


VariableDescription

INFO TUP TRK FEATTRBL

Constant Fixed Indicates that the TOA field in a BTUPANM has an invalid value in the range2-15

CKT Symbolic text Variable Provides equipment identificationnumber for the affected trunk

REPORTING CKT Symbolic text Variable Provides equipment identificationnumber for the trunk reporting theANM problem

REASON Character string Variable Indicates that the reason generatingthis log is an INVALID ANM TOA

DATA Integer Variable Indicates one relevant value of theTOA

Active message exampleCENTREX TRK353 JAN3016:21:29 0900 INFO TUP TRK FEAT TRBL

CKT BNR0201 1

REPORTING CKT BNR0201 1

REASON = INVALID ANM TOA

DATA = 2


TRK353 449


NN10275-909v14 12.01 06 October 2011



TRK601The Trunk (TRK) subsystem generates the information log report TRK601when a fraudulent or an invalid authcode, or invalid security digits, areused to place an Indirect Authcode call.

Log report TRK601 replaces log report IBN110 for the following IndirectAuthcode conditions:

• when a fraudulent authcode call occurs that has the Authlogreq optionassigned in table Authcde and the call is answered, routed totreatment, or abandoned. Fraudulent authcodes are valid authcodesthat are used by people other than their owners.

• when an invalid authcode or personal identification number (PIN) isused for an Indirect Authcode call on an incoming BTUP (UK variant ofnational user part) trunk that has the ANIREC option in table TRKGRPset to ALWAYS or ALLOWED.

• when a valid authcode used to initiate an Indirect Authcode call, butdoes not use expected security digits or uses incorrect ones.

Log report TRK601 will not be generated for either fraudulent or invalidauthcodes when:

• an ACI response message is not received in response to an ACIrequest.

• a CONFusion message is returned in response to an ACI request.

• the call clears before authcode validation has completed.

• the ANIREC option in table TRKGRP is set to NEVER.

Remedial actionThis information log should be retained for statistical purposes and to trackpatterns of Indirect Authcode abuse. Refer to the next level ofmaintenance.


Severity Warning

FormatTRK601 mmmdd hh:mm:ss ssdd INFO AUTH ABUSE

CLLI <incoming BTUP trunk clli>



NN10275-909v14 12.01 06 October 2011


AUTHCODE <authcode used>

CLI <full or partial>

TYPE <type of abuse>


VariableDescription

INFO AUTH_ABUSE Constant Fixed Indicates that the authority or securitycodes have been abused.

CKT Symbolic text Variable Indicates the identity of the switchreporting the abuse

CLLI Integers Variable Identifies the common languagelocation identifier (CLLI) of theincoming BTUP trunk

AUTHCODE Integers Variable Identifies the authority code used

CCC Integers Variable Identifies the cost center code numberfor the call

DIGITS DIALED Integers Variable Gives a record of the directory number(DN) digits dialed by the customer

CLI Integers Variable Identifies the full or partial calling lineidentification of the originator of thecall

TYPE Symbolic text asshown below:

Variable Identifies the type of abuseencountered

INVALID AUTHCODE

Variable Indicates that the authority code is notknown to the switch

INVALID PIN DIGITS Variable Indicates that the dialed PIN digits donot match the digits listed in tableAUTHCDE

INCORRECT PINDIGITS

Variable Indicates that the number of the PINdigits dialed is more or less than thenumber specified in table AUTHCDE

INVALID SECURITYCODE

Variable Indicates that the security code dialed(subsequent to the authority code) isnot the same as that datafilled for theauthority code

NO SECURITYCODE

Variable Indicates that the security code thatshould be dialed after the authoritycode was not dialed

TRK601 451


NN10275-909v14 12.01 06 October 2011


Active message exampleTRK601 JUL12 19:01:08 8900 INFO AUTH ABUSE

CLLI: HOST 00 0 10 30

AUTHCODE: 7221112

CLI 0987123456

TYPE INVALID AUTH CODE



TRK601 Format 2The Trunk (TRK) subsystem generates the information log report TRK601when a fraudulent or an invalid authcode, or invalid security digits, areused to place an Indirect Authcode call.












NN10275-909v14 12.01 06 October 2011




Severity Warning




ccc <cost center code>

Security digits




VariableDescription








TRK601 Format 2 453


NN10275-909v14 12.01 06 October 2011



Description



INVALID AUTHCODE



INCORRECT PINDIGITS




NO SECURITYCODE



CLLI: HOST 00 0 10 30

AUTHCODE: 7221112

CLI 0987123456




TRK601 Format 3The Trunk (TRK) subsystem generates the information log report TRK601when a fraudulent or an invalid authcode, or invalid security digits, areused to place an Indirect Authcode call.



NN10275-909v14 12.01 06 October 2011













Severity Warning


CKT <identity of switch reporting abuse>



ccc <cost center code>

DIGITS DIALED dn

TRK601 Format 3 455


NN10275-909v14 12.01 06 October 2011





VariableDescription










INVALID AUTHCODE



INCORRECT PINDIGITS




NO SECURITYCODE





NN10275-909v14 12.01 06 October 2011


CLLI: HOST 00 0 10 30

AUTHCODE: 7221112

CLI 0987123456




TRK602The Trunk Maintenance subsystem generates information log reportTRK602 for all PCM30 digital trunk controller (PDTC) MEL and DigitalPrivate Network Signaling System No. 1 (DPNSS) calls to identify thedefault calling line identification (CLI) for PDTC MEL and DPNSS calls thatare datafilled in table CLIDN.

CLIDN works by matching the digits to be outpulses with the digitsdatafilled in the table. If there is a match then either a TRK163 or TRK164log is produced. However, log report TRK602 replaces TRK164 log reportfor PDTC MEL and DPNSS calls to BTUP (UK variant of national userpart). The TRK164 log report is inadequate to trace the originator of a call.

If there is no CLI datafilled in table TRKGRP or the call is not PDTC MELor DPNSS to BTUP, then the TRK164 log will be produced as before.

Remedial actionNo immediate action needs to be taken. Post action is required for caseswhere table CLIDN is datafilled to generate a log for emergency ormalicious calls. In such a case, the log can be used to trace the origin ofthe call.


Severity Warning

FormatTRK602 mmmdd mm:hh:ss ssdd INFO CALLING LINE IDENT

INCOMING TRUNK = CKT <trunk CLLI><trunk member>

OUTGOING TRUNK = CKT <trunk CLLI><trunk member>

TRK602 457


NN10275-909v14 12.01 06 October 2011


CALLED NUMBER = <dialed digits>

CALLID = <Call ID for the call>

DEFAULT CLI = <CLI datafilled in table TRKMEM>


VariableDescription

INFO CALLING LINEIDENT

Constant Fixed Indicates that this is an informationallog, and that a CLI is requested forcall through the office.

INCOMING TRUNK Symbolic text (25bytes)

Variable Identifies the incoming trunk CLLIname and trunk member (0-255)

OUTGOING TRUNK Symbolic text (25bytes)

Variable Identifies the outgoing trunk CLLIname and trunk member (0-255)

CALLED NUMBER Integer (10 bytes) Variable Identifies the digits received on theincoming trunk

CALLID Integers (32 bytes) Variable Identifies the internal call id numberfor the call

DEFAULT CLI Integers (6 bytes) Variable Identifies the Default CLI obtainedfrom the DEFLTCLI field of tableTRKGRP

Active message exampleTRK602 JUN24 11:35:10 1234 INFO CALLING LINE IDENT

INCOMING TRUNK = CKT BNRTESTINC 0

OUTGOING TRUNK = CKT BNRTESTOTG 1

CALLED NUMBER = 987654321

CALLID = 123456

DEFAULT CLI = 0987123456




NN10275-909v14 12.01 06 October 2011



TRK606The TRK606 log lists protocol errors on DPNSS trunks that do not violatethe protocol. Types of error messages include:

• optional unrecognized string

• PSTN barred calls

• missing CLC in NAM

The format and purpose of log TRK606 is similar to log TRK340. LogTRK340 lists genuine protocol violations.

Log history

MMP13

Log introduced.

Remedial actionn/a


Severity Warning

FormatTRK606 date time seqnbr INFO DPNSS PROTOCOL INFORMATION

CKT circuit, CALLID: call_id

TROUBLE: DPNSS trouble code

MSG:

hex display of the message buffer

TRK606 459


NN10275-909v14 12.01 06 October 2011



VariableDescription

DPNSS PROTOCOLINFORMATION

Constant Fixed

CKT or VIRT CKT Symbolic text Variable Provides equipment identification forDPNSS trunk. See Table 9 in the LogReport Reference Manual .

CALLID Integers Variable The call's unique callid.

Trouble Trouble text Variable Identifies trouble encountered on theDPNSS trunk. Sample messages are:

• OPT_UNREC_STRING (optionalunrecognized string)

• PSTN call barred (PSTN barredcalls)

• missing CLC in NAM

MSG Message text Variable Displays the hex numbers in themessage buffer.

Active message exampleTRK606 DEC02 16:21:49 2387 INFO DPNSS PROTOCOL INFORMATION

CKT KNGA222BWD 0, CALLID: 622634

TROUBLE: MISSING_CLC

MSG:

2A09 3035 352A 3034 3134 3130 FD23 FDFD

FDFD FDFD FDFD FDFD FDFD FDFD FDFD FDFD

FDFD FDFD FDFD FDFD FDFD FDFD FDFD FDFD



TRST100This log displays the status of trunks on the switch. This log is generatedevery five minutes.



NN10275-909v14 12.01 06 October 2011


Only BAMA or ATLAS control systems allow the log output. The defaultcontrol system is NONE.

The log is limited by the LOG_TRST_CONFIG parameter (OFCENG),which holds the BAMA or ATLAS control system.

The default TRST_LOG_CONFIG_TYPE is NONE.

Remedial actionn/a


Severity Warning

Format---------------------------------------------------------------

CAP7B TRST100 SEP15 11:12:09 1500 INFO TRK_STATE_SUMMARY

LOG <curr_log> OF <num_of_logs>

CLLI | IDL | CPB | LO | OTHER | TOTAL

--------------|-------|------|-------|-------|------

<trkgname> <idle> <cpb> <lo> <other> <TOTAL>

<Nexttrkgname><idle> <cpb> <lo> <other> <TOTAL>

<Nexttrkgname><idle> <cpb> <lo> <other> <TOTAL>

<Last trkgname><idle> <cpb> <lo> <other> <TOTAL>

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


VariableDescription

Report Label TRK_STATE_SUMMARY

Variable The log target.

curr_log UNSIGNEDINT Variable The current log number.

TRST100 461


NN10275-909v14 12.01 06 October 2011



Description

num_of_logs UNSIGNEDINT Variable The maximum number of TRST100logs.

trkgname common_language_name

Variable The trunk group's name.

idle UNSIGNEDINT Variable The trk_idle counter.

cpb UNSIGNEDINT Variable The trunk busy counter.

lo UNSIGNEDINT Variable The tk_lockout counter.

other UNSIGNEDINT Variable The (TOTAL - (CPB+CPD+LO+IDL+INB)) counter.

TOTAL UNSIGNEDINT Variable The total number of trunks in thegroup counter.

Active message example---------------------------------------------------------------

CAP7B TRST100 SEP15 11:12:09 1500 INFO TRK_STATE_SUMMARY

LOG 01 OF 01

CLLI | IDL| CPB | LO | OTHER | TOTAL

--------------|-------|------|-------|-------|------

HSET 0 0 0 0 1

JACK 0 0 0 0 1

LTU 0 0 0 0 2



TSTK910T901 is a communication test. The terminating switch returns a reply(offhook tone) and an answer_msg. The originating switch checks that ananswer_msg has arrived.

This log is generated when the test is successful.



NN10275-909v14 12.01 06 October 2011


Remedial actionn/a



FormatTEST OK

Switch *** TSTK910 mmm dd hh:mm:ss ssdd PASS T901 PASSED

CKT trkid

Active message exampleTEST OK

CFAST2 *** TSTK910 JAN22 18:08:49 2100 PASS T901 PASSED

CKT TNORM 0



TSTK911T901 is a communication test. The terminating switch returns a reply(offhook tone) and an answer_msg. The originating switch checks that ananswer_msg has arrived.

This log is generated when the test is unsuccessful.

Remedial actionAction to be taken by failure reason

• ILLEGAL TESTED TRK

• None

• NO TLINE ACCESS CODE

• Check table TSTLCONT, sub table TLNOS

• NO REPLY

• The trunk defined in another carrier

TSTK911 463


NN10275-909v14 12.01 06 October 2011


• Test the carrier

• CONGESTION RCVD

• Test trunk defined in another carrier


• TRK HARDWARE FAIL

• Verify that the outgoing trunk state is not CFL, LO or RMB



• INTEGRITY LOST RCVD



• OUTPULSE TROUBLE



• FAR END DISCONNECTED

• Test the other trunk


• NO ANSWER



• UNKNOWN PROBLEM






FormatTEST FL

Switch *** TSTK911 mmm dd hh:mm:ss ssdd FAIL T901 FAILED



NN10275-909v14 12.01 06 October 2011


CKT trkid

REASON = text


VariableDescription

REASON ILLEGAL TESTEDTRK

Variable T901 is implemented for Israeli ISUP/R2 trunks only.

NO TLINE ACCESSCODE

Variable Unable to find T901 digit to outpulse.The digit should be in tableTSTLCONT, subtable TLNOS. Thesubtable is taken from tableCLLIMTCE, for each trunk.

NO REPLY Variable Outpulsing fault, no reply wasreceived.

CONGESTION RCVD Variable Outpulsing fault, Congestion msg wasreceived.

TRK HARDWAREFAIL

Variable Outpulsing fault because of ahardware fault.

INTEGRITY LOSTRCVD

Variable Integ lost msg was received whilewaiting for answer msg .

OUTPULSETROUBLE

Variable Outpulsing fault, no reason supplied.

FAR ENDDISCONNECTED

Variable Blocking msglFrls msg was receivedwhile waiting for answer msg .

NO ANSWER Variable No answer msg was received within10 seconds.

UNEXPECTED MSGabed

Variable Unexpected message received.

UNKNOWNPROBLEM

Variable Unknown problem received.

Active message exampleTEST FL

CFAST2 ***+TSTK911 NOV14 15:40:52 6100 FAIL T901 FAILED

CKT TNORM 0

REASON = TRK HARDWARE FAIL

TSTK911 465


NN10275-909v14 12.01 06 October 2011




TSTK920T902 is two-way transmitting test for Israeli R2 trunks. It contains theExpected Measure Lost (EML) and the measurement result: Far-Near-Deviation (F_N_DEV). The ORIG switch prints this log message aftersuccessful test T902.

Remedial actionn/a



FormatTEST OK


CKT trkid

EML = expected measured loss DB F_N DEV =Far-Near-DeviationDB


VariableDescription

EML 0 to 360 dB Variable The expected measured loss is set to0.1 dB by default.

F_N DEV 60 dB or less Variable The Far-Near-Deviation in dB.

Active message exampleTEST OK

CFAST2 *** TSTK920 JAN22 18:09:07 3500 PASS T902 PASSED

CKT TNORM 0

EML = 0.0 DB F_N DEV = 0.9 DB



NN10275-909v14 12.01 06 October 2011




TSTK921T902 is two-way transmitting test (TTT) for Israeli R2 trunks. It contains theExpected Measure Lost (EML) and the measurement result:

Far-Near-Deviation (F_N_DEV).

The originating switch generates this log message after test T902 hasfailed. Test T902 fails when there is no connection between originating andterminating switches.



• T902 is implemented for Israeli R2 trunk only


• Check table TSTLCONT, subtable TLNOS

• NO REPLY



• CONGESTION RCVD












TSTK921 467


NN10275-909v14 12.01 06 October 2011






• CONNECTION FAULT

• Check TTT card in the originating captive switch

• SUPERVISION FAULT


• RING NO ANSWER


• Check TTT/TERM902T card in the terminating captive switch


• 800 HZ BUT NO ANSWER




• UNEXPECTED TONE RCVD




• TONE DETED FAILED




• NO ANSWER



• UNEXPECTED MSG abcd






NN10275-909v14 12.01 06 October 2011




FormatTEST FL

Switch *** TSTK921 mmm dd hh:mm:ss ssdd FAIL T902 ABORTED

CKT trkid

TSTEQ = test eq. id REASON = text


VariableDescription


Variable T902 is implemented for Israeli R2trunk only.

NO TLINE ACCESSCODE




TRK HARDWAREFAIL

Variable Outpulsing fault because of ahardware fault.

INTEGRITY LOSTRCVD

Variable Integ lost msg was received whilewaiting for answer msg .

OUTPULSETROUBLE


FAR ENDDISCONNECTED

Variable Blocking msg/Frls msg was receivedwhile waiting for answer msg .

CONNECTIONFAULT

Variable Failed to connect TTT to the testedtrunk.

SUPERVISIONFAULT

Variable Failed to establish supervisionbetween TTT and tested trunk.

RING NO ANSWER Variable The ringing tone has been received,but answer msg was not receivedwithin 3 seconds.

TSTK921 469


NN10275-909v14 12.01 06 October 2011



Description

800HZ BUT NOANSWER

Variable The correct tone was received, butanswer msg was not.

UNEXPECTED TONERCVD

Variable Unexpected tone received.

TONE DETEDTFAILED

Variable Tone detection failed.

NO ANSWER Variable No answer msg was received afterTTT had been connected to the testtrunk and tried to establishsupervision.

UNEXPECTED MSGabcd



CFAST2 ***+ TSTK921 NOV14 15:48:41 0500 FAIL T902 ABORTED

CKT TNORM 0

TSTEQ = TTT 0 REASON = TRK HARDWARE FAILED



TSTK922T902 is two-way transmitting test (TTT) for Israeli R2 trunks. It contains theExpected Measure Lost (EML) and the measurement result: Far-Near-Deviation (F_N_DEV).

The originating switch generates this log message after test T902 hasfailed. Test T902 fails when the originating switch receives the answermessage, but the transmit/receive tone to/from the terminating switch is notcorrect.


• NO TONE OFF MSG




NN10275-909v14 12.01 06 October 2011











• NO 800 HZ AFTER ANS



• UNEXPECTED RELEASE


• UNEXPECTED MSG abcd






FormatTEST FL


CKT trkid


TSTK922 471


NN10275-909v14 12.01 06 October 2011



VariableDescription

REASON NO TONE OFF MSG Variable TTT does not stop broadcasting800Hz from the terminating switch.

UNEXPECTED TONERCVD

Variable Unexpected tone received. Clearforward msg is sent from theoriginating switch.

TONE DETEDTFAILED


NO 800HZ AFTERANS

Variable The 800Hz tone was not receivedfrom the terminating switch. Clearforward msg is sent from theoriginating switch.

UNEXPECTEDRELEASE

Variable Clear back msg (R2) /release msg(ISUP) received from terminatingswitch instead of 800Hz tone.

UNEXPECTED MSGabed



CFAST2 ***+ TSTK922 NOV14 15:48:41 0500 FAIL T902 ABORTED

CKT TNORM 0

TSTEQ = TTT 0 REASON = TRK HARDWARE FAILED



TSTK924T902 is two-way transmitting test (TTT) for Israeli R2 trunks. It contains theExpected Measure Lost (EML) and the measurement result: Far-Near-Deviation (F_N_DEV).

The originating switch generates this log message after test T902 hasfailed. This log message is generated when the terminating switch detectsdeviation from the limits (Q1 or Q2).



NN10275-909v14 12.01 06 October 2011



• 800 HZ TONE UNSTEADY




• F_N LOSS EXCEEDED Q1



• Check TTT card in originating captive







FormatTEST FL


CKT trkid

TSTEQ =test eq. id REASON = text

EML = expected measured loss DBF_N DEV =Far-Near-DeviationDB

(measurement result)

TSTK924 473


NN10275-909v14 12.01 06 October 2011



VariableDescription

REASON 800 HZ TONEUNSTEADY

Variable The difference between the currentdeviation and the previous deviation isequal to or greater then 0.4dB.

F_N LOSSEXCEEDED Q1

Variable The incoming tested trunk loss is lessthen the minimum value. The defaultfor Q1 is -65dB.

F_N LOSSEXCEEDED Q2

Variable The incoming trunk loss is greaterthen the maximum value. The defaultfor Q2 is 35dB.

EML numeric Variable The expected measurement loss indB.

F_N_DEV numeric Variable The Far-Near-Deviation in dB.


CFAST2 ***+ TSTK924 NOV14 15:48:41 0500 FAIL T902 FAILED

CKT TNORM 0

TSTEQ = TTT 0 REASON = Q1 LIMIT EXCEEDED

EML = 1.0 DB F_NDEV = 1.9 DB



TSTK940T904 is two-way transmitting test. It contains the Expected Measure Lost(EML) and the measurement result: Far-Near-Deviation (F_N_DEV). Theoriginating switch prints this log message after successful test T904.

Remedial actionn/a





NN10275-909v14 12.01 06 October 2011


FormatTESTOK


CKT trkid



VariableDescription

EML 0 to 360 dB Variable The expected measured loss is set to0 dB by default.

F_N DEV 60 dB or less Variable The Far-Near-Deviation in dB.

Active message exampleTESTOK

CFAST2 ***+TSTK940 NOV14 15:52:34 2300 PASS T904 PASSED

CKT R2OCAP3 1

EML = 0.0 DB F_N DEV = 1.2DB



TSTK941T904 is two-way transmitting test (TTT). It contains the Expected MeasureLost (EML) and the measurement result: Far-Near-Deviation (F_N_DEV).

The originating switch generates this log message after test T904 hasfailed. Test T904 fails when there is no connection between originating andterminating switches, for example, outpulsing failed, no connection/supervision with test equipment (TTT card), or answer msg is not received.



• T904 is implemented for Israeli ISUP/R2 trunks only

TSTK941 475


NN10275-909v14 12.01 06 October 2011



• Check table TSTLCONT, subtable TLNOS



• CONGESTION RCVD
















• CONNECTION FAULT


• SUPERVISION FAULT


• RING NO ANSWER




• 800 HZ BUT NO ANSWER






NN10275-909v14 12.01 06 October 2011




• Check TTT/TERM902T card in TERM captive






• NO ANSWER



• UNEXPECTED MSG abed






FormatTEST FL


CKT trkid


TSTK941 477


NN10275-909v14 12.01 06 October 2011



VariableDescription


Variable T904 is implemented for Israeli ISUP/R2 trunks only.

NO TLINE ACCESSCODE




TRK HARDWAREFAIL

Variable Outpulsing fault due to a hardwarefault.

INTEGRITY LOSTRCVD

Variable Integ lost msg was received whilewaiting for answer msg.

OUTPULSETROUBLE


FAR ENDDISCONNECTED

Variable Blocking msg/Frls msg was receivedwhile waiting for answer msg .

CONNECTIONFAULT

Variable Failed to connect TTT to the testedtrunk.

SUPERVISIONFAULT

Variable Failed to establish supervisionbetween TTT and tested trunk.

RING NO ANSWER Variable The ringing tone has been received,but answer msg was not receivedwithin 3 seconds.

800HZ BUT NOANSWER

Variable The correct tone was received, butanswer msg was not.

UNEXPECTED TONERCVD

Variable Unexpected tone received.

TONE DETEDTFAILED


NO ANSWER Variable No answer msg was received afterTTT had been connected to the testtrunk and tried to establishsupervision.

UNEXPECTED MSGabed




NN10275-909v14 12.01 06 October 2011



CFAST2 *** TSTK941 JAN22 18:11:32 9900 FAIL T904 ABORTED

CKT TNORM 0

TTT: TTT 1

REASON = NO ANSWER




The originating switch generates this log message after test T904 hasfailed. Test T904 fails when the originating switch receives the answermessage, but the transmit/receive tone to/from the terminating switch is notcorrect.


• NO TONE OFF MSG









• Check TTT/TERM902T card in TERM captive


• NO 800 HZ AFTER ANS

TSTK942 479


NN10275-909v14 12.01 06 October 2011




• UNEXPECTED RELEASE


• UNEXPECTED MSG abed






FormatTEST FL


CKT trkid



VariableDescription

REASON NO TONE OFF MSG Variable TTT does not stop broadcasting800Hz TERM switch.

UNEXPECTED TONERCVD

Variable Unexpected tone received. Clearforward msg is sent from theoriginating switch.

TONE DETEDTFAILED


NO 800HZ AFTERANS

Variable The 800Hz tone was not receivedfrom the TERM switch. Clear forwardmsg is sent from the originatingswitch.

UNEXPECTEDRELEASE

Variable Clear back msg (R2)/ release msg(ISUP) received from the terminatingswitch instead of 800Hz tone.

UNEXPECTED MSGabed




NN10275-909v14 12.01 06 October 2011



CFAST2 *** TSTK942 JAN22 18:11:32 9900 FAIL T904 ABORTED

CKT TNORM 0

TTT:TTT 1

REASON = NO ANSWER




The originating switch generates this log message after test T904 hasfailed. This log message is generated when the terminating switch detectslimits deviation (Q1 or Q2).


• N_F LOSS EXCEEDED Q1


• Check TTT card in the terminating captive switch


• N_F LOSS EXCEEDED Q2


• Check TTT card in the terminating captive switch




FormatTEST FL

TSTK943 481


NN10275-909v14 12.01 06 October 2011



CKT trkid



VariableDescription

REASON N_F LOSSEXCEEDED Q1

Variable The Far_End received the 800Hztone, but the loss exceeded the Q1limitation.

N_F LOSSEXCEEDED Q2

Variable The Far_End received the 800Hztone, but the loss exceeded the Q2limitation.


CFAST2 *** TSTK943 JAN22 18:11:32 9900 FAIL T904 FAILED

CKT TNORM 0

TTT: TTT 1

REASON = NO ANSWER





• 800 HZ TONE UNSTEADY







NN10275-909v14 12.01 06 October 2011











FormatTEST FL


CKT trkid



(measurement result)


VariableDescription

REASON 800 HZ TONEUNSTEADY

Variable The difference between the currentdeviation and the previous deviation isequal to or greater then 0.4dB.

F_N LOSSEXCEEDED Q1

Variable The incoming tested trunk loss is lessthen the minimum value. The defaultfor Q1 is -65dB.

F_N LOSSEXCEEDED Q2

Variable The incoming trunk loss is greaterthen the maximum value. The defaultfor Q2 is 35dB.


TSTK944 483


NN10275-909v14 12.01 06 October 2011


CFAST2 ***+ TSTK944 NOV14 15:48:41 0500 FAIL T904 FAILED

CKT TNORM 0

TSTEQ = TTT 0 REASON = F_N LOSS EXCEEDED Q1

EML = LODB F_NDEV = 1.9DB



TUPL608The TUPL608 log report generates when the compress command, locatedin the COMPRSCI directory, removes identical tuples from the LINEATTRtable. The TUPL608 log report generation requires the following:

• the BASE011 software optionality code (SOC) set to ON

• the LOG and MONITOR fields in the TABMON table set to Y for theLINEATTR entry

The TUPL608 log report contains a list of up to 20 tuples deleted based onthe reference tuple used with the compress command. Each referencetuple generates a separate TUPL608 log report. A reference tuplegenerates additional log reports only if the compress command deletesmore than 20 tuples.

The compress command also generates the TUPL601 and TUPL602 logs,and also the TUPL605 log if the command updates references in tablesother than the LINEATTR table.

The LINEATTR Compression Tool feature removes duplicate tuples fromthe LINEATTR table. The compress command also replaces tuples in thefollowing tables with the referenced LINEATTR key:

• ACDDNDR*CFW

• CUSTHEAD

• DATAOWNR

• DNINV

• DNROUTE

• IBNLINES

• IBNRTE



NN10275-909v14 12.01 06 October 2011


• IBNRT2

• IBNRT3

• IBNRT4

• IBNXLA

• KSETLINE

• LATTRDR

• LENLINES

• LTCALLS

• NCOS

• PODPATTR

• RMPCKT

• TRIGITM

• VFGDATA

• VIRTGRPS

• XLAMAP

• XLANAME

Remedial actionTo restore tuples that the compress command deleted from the LINEATTRtable, use the information in the TUPL608 log report to create a datamodification order processor (DMOPRO) file. Execute the DMOPRO file onthe switch to restore the deleted tuples to the LINEATTR table. Use thesame process to restore replaced or deleted datafill from other tables usinginformation from the TUPL601, TUPL602, and TUPL605 logs.


Severity Warning

FormatTUPL608 mmmdd hh:mm:ss ssdd INFO TABLE LINEATTR COMPRESSION

OPERATION: <compress command entered by user>

TABLE: <lineattr>

REFERENCE TUPLE: <tuple LKx>

TUPL608 485


NN10275-909v14 12.01 06 October 2011


OWNED BY: <reference tuple owner>

LIST OF TUPLES DELETED: <list of up to 20 LINEATTR keys>

SEQNUM: <log sequence number>

DATE: <mmddyyy> <hhmmss>

USER ID: <8 character string> ON: CONSOLE: <console name>

PCL: <PCL product name and version>


VariableDescription

OPERATION up to 252 charactersThis field supports upto 4 lines of 72characters each.

Variable The compress command entered bythe user.

TABLE up to 8 characters Variable The name of the table used with thecompress command.

REFERENCE TUPLE 1 tuple Variable The defined tuple to search and deleteall instances from the table.

OWNER ID up to 8 characters Variable The reference tuple owner ID definedin the DATAOWNR table.

LIST OF TUPLESDELETED

up to 360 charactersThis field supports upto 4 tuples in a rowand up to 5 rows.

Variable The list of table tuples that weredeleted during the compressionprocess. A log specifies up to 20different tuples.

SEQNUM 0 to 32 767 Variable The log sequence number issuedduring the compression process.

DATE mmddyy Variable The month, day, and year that thecompress command was used.

TIME hhmmss Variable The hour, minute, and second that thecompress command was used.

USER up to 16 characters Variable Identification of the user that enteredthe compress command.

ON up to 17 characters Variable The name and type of device that wasused to enter the compress command.

PCL up to 34 characters Variable The PCL product name and version.

Active message exampleTUPL608 JAN05 23:32:19 9503 INFO TABLE LINEATTR COMPRESSION



NN10275-909v14 12.01 06 October 2011


OPERATION: COMPRESS KEY 2 0 4 5 $

TABLE: LINEATTR

REFERENCE TUPLE: 2 1FR NONE NT 10 NILSFC 0 NIL NIL 00 $

OWNED BY: CIVIC

LIST OF TUPLES DELETED:

0 3 4 6

8 LATTR21 10 11

98 121 LATTR1 900

SEQNUM: 1

DATE: 01052000 TIME: 233119

USER: ADMIN ON: CONSOLE: MAP

PCL: LETO 11



V5101The peripheral module (PM) subsystem generates this report when a V5link between a generic access node (AN) and a Global peripheral Platform(GPP) goes off-line (OFFL).

Remedial actionQuery the MAP display at the MAPCI;MTC;CCS;V5 level to determine ifthe V5 link was set offline at the DMS switch or at the AN by operatingcompany personnel. If the link carried control or PSTN information,protection switching occurs if back up channels are provisioned. If the linkcarried speech information no calls can be completed on the link until thelink is returned to service (RTS).



V5101 487


NN10275-909v14 12.01 06 October 2011


FormatV5101 mmmdd hh:mm:ss xxxx <log_type> <link_type> <pm_id>

V5LINK No: <link_number> V5ID: <ID>

PORT: <GPP_number> <P-side_link_number>


VariableDescription

log_type OFFL Variable Status. Indicated V5 link state haschanged from in-service (INSV) to off-line (OFFL).

link_type V5LINK Variable V5LINK or channel information.

pm_id see subfields Variable Peripheral module (PM) identifier.Consists of subfields PM_type andGPP_PM number.

PM_type GPP Variable V5 links always terminate on a GPP.

GPP_PM_number 0 to 255 Variable Peripheral module number assignedto the GPP.

link_number 0 to 15 Variable V5 AN C-side link number.

ID see subfields Variable V5 interface identifier. Equates to fieldAMCNO in table GPPTRNSL.composed of subfields; SITE, FRAME,and UNIT.

SITE alphanumeric Variable Four character site designator.

FRAME 0 to 511 Variable Frame number of access node (AN)supplying the V5 interface. Entry canbe unique within the site if officeparameter,UNIQUE_BY_SITE_NUMBERING, intable OFCENG, is datafilled Y.

UNIT 0 to 9 Variable Access node unit number

PORT see subfields Variable GPP port of affected link. Consists ofsubfields GPP_PM_number andP_side_link number.

P-side_link_number 0 to 47 Variable GPP P-side PCM30 link number.

Active message exampleV5101 SEP05 18:14:33 1305 OFFL V5LINK GPP 1

V5LINK NO:1 V5ID: RMV5 1 0



NN10275-909v14 12.01 06 October 2011


PORT: GPP 1 P-side link 1



V5102The peripheral module (PM) subsystem generates this report when a V5link between a generic access node (AN) and a Global peripheral Platform(GPP) is set maintenance busy (MANB).

Remedial actionQuery the MAP display at the MAPCI;MTC;CCS;V5 level to determine ifthe V5 link was set maintenance busy (MANB) at the DMS switch or at theAN by operating company personnel. If a link carries control or PSTNinformation and no protection links are provisioned the interface must bedeactivated before issuing the MANB command to that link.







VariableDescription

log_type MANB Variable Status. Indicated V5 link has been setmaintenance busy.


pm_id see subfields Variable Peripheral module (PM) identifier.Consists of subfields PM type andGPP PM number.




V5102 489


NN10275-909v14 12.01 06 October 2011



Description





PORT see subfields Variable GPP port of affected link. Consists ofsubfields GPP_PM_number and P-side_link_number.

P-side_ink_number 0 to 47 Variable GPP P-side PCM30 link number.

Active message exampleV5102 SEP05 18:14:33 1305 MANB V5LINK GPP 1





V5103The peripheral module (PM) subsystem generates this report when a V5link connected between a generic access node (AN) and a Globalperipheral Platform (GPP) goes system busy (SYSB).

Remedial actionPost the V5 link at the carrier level and query the fault diagnostics. If thePCM30 link(s) are out-of-service, post the GPP at the PM level and queryfor faults. Go to the alarm clearing procedures in the GPP maintenancemanual for more information on clearing SYSB condition. Links that failduring activation of the V5 interface may stay in either a system busy(SYSB) or remote blocked state.



NN10275-909v14 12.01 06 October 2011


If the link carried control or PSTN information, protection switching occursif back up channels are provisioned. If the link carried speech informationno calls can be completed until the link is returned to service (RTS).







VariableDescription


PORT see subfields Variable GPP port of affected link. Consists ofsubfields GPP PM number and P-sidelink number.

GPP PM number 0 to 255 Variable Peripheral module number assignedto the GPP.

P-side link number 0 to 47 Variable GPP P-side PCM30 link number.

log_type SYSB Variable Status. V5 link has been set busy bythe system, indicating a faultcondition.







V5103 491


NN10275-909v14 12.01 06 October 2011



Description



Active message exampleV5103 SEP05 18:14:33 1305 SYSB V5LINK GPP 1





V5104The peripheral module (PM) subsystem generates this information reportwhen a V5 link connected to a Global Peripheral Platform (GPP) isremotely blocked at the access node (AN).

Remedial actionQuery the MAP display at the MAPCI;MTC;CCS;V5 level to determine thereason the interface has been blocked by maintenance action on theaccess node (AN) side. No calls can be completed to lines on the blockedinterface.


Severity Warning


INFO:<interface_information>




NN10275-909v14 12.01 06 October 2011


PORT <GPP_number> <P-side_link_number>


VariableDescription

log_type INFO Variable Indicated V5 interface informationfollows in field INFO.

link_type V5LINK Variable VSLINK or channel information.

pm_id see subfields Variable Peripheral module (PM) identifier.Consists of subfields PM_type andGPP_PM_number.



interface_information alphanumeric string Variable Information. The indicated V5interface is remotely blocked.








Active message exampleV5104 SEP05 18:14:33 1305 INFO V5LINK GPP 1

INFO: V5 interface is Remote Blocked



V5104 493


NN10275-909v14 12.01 06 October 2011




V5105The peripheral module (PM) subsystem generates this report when a V5link between a generic access node (AN) and a Global Peripheral Platform(GPP) is set in-service (INSV).

Remedial actionn/a




VSLINK No: <link_number> V5ID: <ID>



VariableDescription

log_type INSV Variable Status. Indicated V5 link has been setin-service.

link_type V5LINK Variable VSLINK or channel information.

pm_id see subfields Variable Peripheral module (PM) identifier.Consists of subfields PM_type andGPP_PM number.



V5_link_number 1 to 16 Variable V5 AN C-side link number.





NN10275-909v14 12.01 06 October 2011



Description





Active message exampleV5105 SEP05 18:14:33 1305 INSV V5LINK GPP 1





V5106The peripheral module (PM) subsystem generates this information reportwhen a V5 interface is activated.

Remedial actionWhen a V5 interfaces is activated the following functions are performed:

• The software optionality control (SOC) information is updated.

• All ports are changed from maintenance busy (MANB) to system busy(SYSB).

• All data links are started.

• All links and C-channels are returned to service (RTS).


Severity Warning

V5106 495


NN10275-909v14 12.01 06 October 2011


FormatV5106 mmmdd hh:mm:ss xxxx <log_type> <ID>

<interface information>

V5ID No: <ID>


VariableDescription

log_type INFO Variable Indicated V5 interface informationfollows in field interface information

ID see subfields Variable V5 interface identifier. Equates to fieldAMCNO in table GPPTRNSL.Composed of subfields SITE, FRAME,and UNIT.



UNIT 0 to 9 Variable Access node unit number.

interface information Interface Activated Variable Information message. The indicatedV5 interface is activated.

ID alphanumeric Variable same as above

Active message exampleV5106 SEP05 18:14:33 1305 INFO RMV5 01 0

V5 Interface Activated

V5ID: RMV5 1 0



V5107The peripheral module (PM) subsystem generates this information reportwhen a V5 interface is deactivated.



NN10275-909v14 12.01 06 October 2011


Remedial actionn/a


Severity Warning


<interface_information>

<ID>


VariableDescription

log_type INFO Variable Indicated V5 interface informationfollows in field interface information.



FRAME 0 to 511 Variable Frame number of access node (AN)supplying the V5 interface. Entry canbe unique within the site if officeparameterUNIQUE_BY_SITE_NUMBERING, intable OFCENG, is datafilled Y.


interface_information alphanumeric string Variable Information. The indicated V5interface is deactivated.

ID see subfields Variable Same as above.


V5 Interface Deactivated

V5ID: RMV5 1 0

V5107 497


NN10275-909v14 12.01 06 October 2011




V5108The peripheral module (PM) subsystem generates this information reportwhen a V5 interface startup fails.

Remedial actionQuery the MAP display at the MAPCI;MTC;CCS;V5 level to determine ifany alarms indicate the cause of failure. When a V5 interface is activated,the following functions are performed. Failure to achieve activation mayleave the links in the system busy (SYSB) condition.

• The software optionality control (SOC) information is updated.

• All ports are changed from maintenance busy (MANB) to SYSB.

• All data links are started.

• All links and C-channels are returned to service (RTS).


Severity Warning



Reason: <reason for failure>

<ID>


VariableDescription


interface_information alphanumeric string Variable Information. The indicated V5interface failed to startup.



NN10275-909v14 12.01 06 October 2011



Description

Reason alphanumeric string Variable Reason for failure. Failure occurredduring startup for one of the followingreasons:

• datalink failure

• mismatch of variant valuebetween LE and AN

• PSTN restart procedure failed






V5 Interface startup failed.

Datalink failed

V5ID: RMV5 1 0



V5109The peripheral module (PM) subsystem generates this information reportwhen a V5 interface startup completes.

Remedial actionn/a

V5109 499


NN10275-909v14 12.01 06 October 2011



Severity Warning

FormatV5109 mmmdd hh:mm:ss xxxx <log_type> GPP <gpp_no>

V5 Interface startup completed.

V5id: <ID>


VariableDescription

log_type INFO Variable This field indicates V5 information thatfollows in field interface information.

gpp_no 0 to 255 Variable Peripheral number assigned to GPP.

ID see subfields Variable V5 interface identifier. Made ofsubfields SITE, FRAME, and UNIT.

SITE alphanumeric Variable Four character site identifier.

FRAME 0 to 511 Variable Frame number of the access node(AN) that supplies the V5 interface.

UNIT 0 to 9 Variable AN node number.

Active message exampleV5109 NOV14 18:14:33 6124 INFO GPP 2

V5 Interface startup completed.

V5ID: V5AN 0 2



V5110The peripheral module (PM) subsystem generates this information reportwhen a V5 interface startup begins from the computing module (CM).

Remedial actionn/a



NN10275-909v14 12.01 06 October 2011



Severity Warning


V5 Interface startup initiated from the CM.

V5id: <ID>


VariableDescription








V5 Interface startup initiated from the CM.

V5ID: V5AN 0 2



V5111The peripheral module (PM) subsystem generates this information reportwhen a V5 interface startup autonomously initialized at the local exchange(LE).

Remedial actionn/a

V5111 501


NN10275-909v14 12.01 06 October 2011



Severity Warning


V5 Interface startup initiated from the LE.

V5id: <ID>


VariableDescription








V5 Interface startup initiated from the LE.

V5ID: V5AN 0 2



V5150The peripheral module (PM) subsystem generates this information reportwhen a V5.2 C-channel is removed from service. The system alsogenerates this log when the ISDN D-channel (ISDD) is out of service andthe P-phone set (PSET) data link (DL) is down.



NN10275-909v14 12.01 06 October 2011


Remedial actionn/a



FormatV5150 mmmdd hh:mm:ss xxx FLTC-chnl<C-no>GPP<GPP-no>

V5.2 C-Channel has been removed from service

V5LINK No: <link_number> <C-no> V5ID: <name><No-l><No-2>



VariableDescription

log type FLT Variable Status. Indicates operating companypersonnel removed V5 link state fromservice.

C-no 0 to 31 Variable C-channel number. The channel onthe PCM30 V5.2 link that wasremoved from service.

C-channels can only be located onPCM30 link channels 16,15,31.



GPP-no 0 to 127 Variable Peripheral module number assignedto the GPP.

interface_information alphanumeric string Variable Information. V5.2 C-channel has beenremoved from service


pm_id alphanumeric Variable PM identification number. Same asabove.


V5150 503


NN10275-909v14 12.01 06 October 2011



Description




No-1 0 to 99 Variable first unit number

No-2 0 to 9 Variable second unit number

PORT see subfields Variable GPP port of affected link. Consists ofsubfields GPP PM_number and P-side_link_number.



Active message exampleV5150 JUN30 11:56:09 5889 FLT C-chnl 16 GPP 3

V5.2 C-channel has been removed from service.

V5LINK No: 0 C-chnl 16 V5ID: RMV5 1 1

PORT: GPP 3 P-side Link 5



V5151The peripheral module (PM) subsystem generates this information reportwhen a V5.2 C-channel has been returned to service.

Remedial actionn/a





NN10275-909v14 12.01 06 October 2011


FormatV5151 mmmdd hh:mm:ss xxx <log_type> chnl <C-no> GPP<GPP-no>

V5.2 P-Phone DL has been returned to service

V5LINK No: <link-no> C-chnl<C-no> V5id: <name> <No-1> <No-2>

PORT: <GPP-no> P-Side Link <P-side_link_no>


VariableDescription

log_type FLT Variable Status. Indicated V5 link state hasbeen returned to service.

C-no 1 to 31 Variable C-channel number. The channel onthe PCM30 V5.2 link that wasremoved from service.



PM_type GPP Variable Peripheral module type. V5 linksalways terminate on a GPP.


interface_information alphanumeric string Variable Information. Indicated V5.2 C-channelhas been returned to service.


pm_id alphanumeric Variable PM identification number. Same asabove.





V5151 505


NN10275-909v14 12.01 06 October 2011



Description

No-1 0 to 99 Variable Unit number

No-2 0 to 9 Variable Second unit number


GPP-no 0 to 127 Variable Peripheral module number assignedto the GPP.


Active message exampleV5151 JUN30 11:56:09 5889 FLT C-chnl 16 GPP 3

V5.2 P-Phone DL has been returned to service.

V5LINK No: 0 C-hnl 16 V5ID: HOST 1 1

PORT: GPP 3 P-side Link 5



V5152The peripheral module (PM) subsystem generates this information reportwhen a V5.2 link protection switchover occurs.

Remedial actionPost the V5 link at the carrier level and query the fault diagnostics for thelinks switched from. If the PCM30 link(s) are out-of-service, post the GPPat the PM level and query for faults. Go to the alarm clearing procedures inthe GPP maintenance manual for more information on clearing SYSB linkconditions.

If a link carried control or PSTN information, protection switching occurs ifback up channels are provisioned.


Severity Warning



NN10275-909v14 12.01 06 October 2011


FormatV5152 mmmdd hh:mm:ss xxx <log type> <C-chnl_number> <pm_id>


Protocol: <C-channel_type>

Protection group: <prot_grp_number>

V5ID: <ID>

Switch from:

V5LINK No:<V5_link_number> <C-chnl_number>


To:

V5LINK No: <V5_link_number> <C-chnl_number>



VariableDescription

log_type INFO Variable Status. Protection switching hasoccurred indicating a link with a C-channel has failed.

C-chnl_number 16, 15, or 31 Variable C-channel number. The channel onthe PCM30 V5.2 link that wasremoved from service.

C-channels can only be located onPCM30 link channels 16, 15, 31.




interface_information alphanumeric string Variable Information. Protection switchover hasoccurred on the indicated link.

V5152 507


NN10275-909v14 12.01 06 October 2011



Description

C-channel_type Control or PSTN Variable Control channel type. Valid V5interface control channel types are;Control (CNTRL) or public switchedtelephone networks (PSTN) protocol.

prot_grp_number 1 or 2 Variable Protection group number. Twoprotection groups exist for V5interfaces. Protection group 1switches to the same channel (16) onan alternate link. Protection group 2 isa multiple of up to three alternate linksand channels.





Switch From: see subfields Variable Protection has switched an out-of-service link with control channel(s)identified by the following subfields;V5LINK number, C-chnl number, andPORT.

V5_LINK_number 1 to 16 Variable Number assigned to V5LINK at theaccess node (AN). Determined byorder of datafill in table GPPTRNSL.

C-chnl_number 16,15, or 31 Variable Channel number assigned as controlchannel.


GPP_number 0 to 255 Variable Peripheral module number assignedto the GPP.




NN10275-909v14 12.01 06 October 2011



Description

Switch TO: see subfields Variable Protection has switched to a link(s)with control channel(s) identified bythe following subfields; V5LINKnumber, C-chnl number, and PORT.

V5LINK_number 1 to 16 Variable Number assigned to V5LINK at theaccess node (AN). Determined byorder of datafill in table GPPTRNSL.

V5 link Protectiongroups are defined intable V5PROV.

Variable

Active message exampleV5152 SEP05 18:14:33 1305 INFO C-chnl 16 GPP 1

Protection has occurred.

Protocol: Control

Protection group: 1

RMV5 1 0

Switch From:


PORT: GPP3 P-side Link 5

To:

V5LINK No: 8 C-chnl 16




V5153The peripheral module (PM) subsystem generates this information reportwhen a V5.2 link protection switchover failed.

V5153 509


NN10275-909v14 12.01 06 October 2011


Remedial actionPost the V5 link at the carrier level and query the fault diagnostics. If the C-channel links are out-of-service a critical alarm condition exists. Ifprotection switching fails all calls on the interfaces are dropped. See thereasons field for fault explanations. Post the GPP at the PM level andquery for faults. Go to the alarm clearing procedures in the GPPmaintenance manual for more information on clearing critical condition.



• Critical

FormatV5153 mmmdd hh:mm:ss xxx <log_type> <C-chnl_number> <pm_id>


Reason: <reason>

Protocol: <C-channel_type>

Protection group: <prot_grp_number>

<ID>

Switch from:

V5LINK No:<V5_link_number> <C-chnl_number>

PORT: <GPP_number> <P-side link_number>

To:

V5LINK No: <V5_link_number> <C-chnl_number>




NN10275-909v14 12.01 06 October 2011



VariableDescription

log_type INFO Variable Status. Protection switching hasoccurred indicating a link with a C-channel has failed.

C-chnl_number 16,15, or 31 Variable C-channel number. The channel onthe PCM30 V5.2 link that wasremoved from service.





interface_information alphanumeric string Variable Information. Protection switchover hasoccurred on the indicated link.

reason alphanumeric string Variable Reason for failure. Failure ofattempted protection link switchoveroccurred for one of the followingreasons.

• No standby C-channel available.

• Target physical C-channel notoperational.

• Target physical C-channel notprovisioned.

C-channel_type Control or PSTN Variable Control channel type. Valid V5interface control channel types are;Control (CNTRL) or public switchedtelephone networks (PSTN) protocol.

prot_grp_number 1 or 2 Variable Protection group number. Twoprotection groups exist for V5interfaces. Protection group 1switches to the same channel (16) onan alternate link. Protection group 2 isa multiple of up to three alternate linksand channels.

V5153 511


NN10275-909v14 12.01 06 October 2011



Description





Switch From: see subfields Variable Protection has switched an out-of-service link with control channel(s)identified by the following subfields;V5LINK number, C-chnl number, andPORT.

V5LINK_number 1 to 16 Variable Number assigned to V5LINK at theaccess node (AN). Determined byorder of datafill in table GPPTRNSL.

C-chnl_number 16,15, or 31 Variable Channel number assigned as controlchannel.




Switch TO: see subfields Variable Protection has switched to a link(s)with control channel(s) identified bythe following subfields; V5LINKnumber, C-chnl number, and PORT.

V5LINK_number 1 to 16 Variable Number assigned to V5LINK at theaccess node (AN). Determined byorder of datafill in table GPPTRNSL


V5 link Protectiongroups are defined intable V5PROV.

Variable



NN10275-909v14 12.01 06 October 2011


Active message exampleV5153 SEP05 18:14:33 1305 INFO C-chnl 16 GPP 1

Protection has occurred.

Reason: No standby C-channel available.

Protocol: Control

Protection group: 1

RMV5 1 0

Switch From:



To:

V5LINK No: 8 C-chnl 16




V5154The peripheral module (PM) subsystem generates this information reportwhen a V5 link identification fails.

Remedial actionn/a





V5154 513


NN10275-909v14 12.01 06 October 2011


V5LINK No: <link_number> <ID>



VariableDescription

log-type FLT Variable Status. V5 link fault,

link_type Symbolic text Variable Fault is on any V5LINK.




interface_information alphanumeric string Variable Information. Indicated V5.2 linkidentification procedure failed.

Link_number 1 to 16 Variable V5 AN C-side link number.







Active message exampleV5151 SEP05 18:14:33 1305 FLT V5LINK GPP 1

V5 link identification procedure failed.

V5LINK No: 1 V5ID: RMV5 1 0



NN10275-909v14 12.01 06 October 2011





V5203The peripheral module (PM) subsystem generates this information reportwhen a V5.2 access node (AN) fault message is received.

Remedial actionn/a


Severity Warning

FormatV5203 mmmdd hh:mm:ss xxxx <log_type> <link_type>


V5LINK No: <link_number> <chnl_number> V5ID: <ID>

PORT: <PM_type> <GPP_number> <P-side_link_number>

LEN: <line_equipment_number> DN: <directory_number>


VariableDescription

log_type INFO Variable Information. AN link and lineinformation where the fault occurred.

link_type BCC Variable Fault occurred on BCC (speech) link.

interface_information alphanumeric string Variable Information. Indicated line on V5.2 ANhas fault symptoms.


chnl_number 0 to 31 Variable C-channel number. The bearerchannel on the PCM30 V5.2 link.

V5203 515


NN10275-909v14 12.01 06 October 2011



Description





PORT see subfields Variable GPP port of affected link. Consists ofsubfields PM type, GPP PM number,and P-side link number.

PM_type Symbolic text Variable PM identification number. V5 linksalways terminate on a GPP.



line_equipment_number

numeric Variable Virtual line equipment numberassigned to line in table LNINV.

directory_number numeric Variable Directory number assigned to line.

(up to 15 digits) Variable

Active message exampleV5203 SEP05 18:14:33 8500 INFO BCC

AN fault message received.

V5LINK No: 1 channel 0 V5ID: RMV5 1 0


LEN: RMV5 01 0 00 01 DN: 7241001




NN10275-909v14 12.01 06 October 2011



V5250The peripheral module (PM) subsystem generates this information reportwhen a bearer channel connection (BCC) protocol error is detected.

Remedial actionn/a


Severity Warning



Received in: <pm_id> V5ID: <ID>

Reason: <reason>

LEN: <line_equipment_number> DN: <Directory Number


VariableDescription





interface_information alphanumeric string Variable Information. Protection protocol erroroccurred. See field Reason.

V5250 517


NN10275-909v14 12.01 06 October 2011



Description



PM_number 0 to 255 Variable Peripheral module number assignedto the GPP.


Reason alphanumeric string Variable Reason for failure. BCC protocol errorwas for one of the following reasons.

• Protocol discriminator error.

• Message type unrecognized.

• Out of sequence informationelement.

• Repeated optional informationelement.

• Mandatory information elementmissing.

• Unrecognized informationelement.

• Mandatory information elementcontent error.

• Optional information elementcontent error.

• Message not compatible withProtocol state.

Reason (continued) alphanumeric string Variable Reason for failure. BCC protocol errorwas for one of the following reasons.

• Repeated mandatory informationelement.

• Too many information elements.


numeric Variable Virtual line equipment number fromtable LNINV assigned to line.






NN10275-909v14 12.01 06 October 2011



BCC protocol error received from AN

Received in: GPP 1 V5ID: RMV5 01 0

Reason: Protocol discriminator error

LEN: PDMX 00 1 00 01 DN: 9096214001



V5251The peripheral module (PM) subsystem generates this information reportwhen a protection protocol error is received from the access node (AN).

Remedial actionn/a


Severity Warning




Reason: <reason>

V5251 519


NN10275-909v14 12.01 06 October 2011



VariableDescription






interface_information alphanumeric string Variable Information. Protection protocol erroroccurred. See field Reason.





Reason alphanumeric string Variable Reason for failure. Protection protocolerror was for one of the followingreasons.






• Message not compatible withprotection protocol state.



NN10275-909v14 12.01 06 October 2011



Description




Protection protocol error received from AN


Reason: Protocol discriminator error



V5252The peripheral module (PM) subsystem generates this information reportwhen a public switched telephone network (PSTN) protocol error isreceived from the access node (AN).

Remedial actionn/a


Severity Warning




Reason: <reason>

LEN: <line_equipment_number> DN <directory number>

V5252 521


NN10275-909v14 12.01 06 October 2011



VariableDescription






interface information alphanumeric string Variable Information. Protection protocol erroroccurred. See field Reason.










• Message not compatible withprotocol state.

• Out of sequence informationelement.



NN10275-909v14 12.01 06 October 2011



Description


• Optional information elementcontent error.




• Response to STATUS ENQUIRY.

• L3 address error.






PSTN protocol error received from AN.


Reason: Mandatory infornation element missing.

LEN: PDMX 00 1 00 01 DN: 9096214001



V5253The peripheral module (PM) subsystem generates this information reportwhen a public switched telephone network (PSTN) protocol error isdetected.

Remedial actionn/a

V5253 523


NN10275-909v14 12.01 06 October 2011



Severity Warning

FormatV5253 mmmdd hh:mm:ss xxxx <log_type> <pm_id>

<error_information

Reason: <reason>

LEN: <line_equipment_number> DN: <directory number>


VariableDescription





interface_information Interface Activated Variable Information message. PSTN layer 3error detection procedure.

reason alphanumeric string Variable Reason for failure. PSTN protocolerror was for one of the followingreasons.

• Counter S(S) exceeds themaximum number.

• Counter M(S) does not equalcounter S(R).

• Counter M(R) is not valid.



directory_number numeric Directory Variable number assigned to line.




NN10275-909v14 12.01 06 October 2011


Active message exampleV5253 SEP05 18:14:33 9001 INFO GPP 1

PSTN layer 3 error detection procedure

V5ID: RMV5 1 0

LEN: PDMX 00 1 00 01 DN: 9096214001



V5254The peripheral module (PM) subsystem generates this information reportwhen a V5 public switched telephone network (PSTN) state mismatchoccurs.

Remedial actionThe V5 interface PSTN protocol is defined by two finite state machines(FSM). The local entity (LE) FSM resides in the GPP and the access node(AN) FSM resides in the AN. PSTN messages transfer information aboutthe state of the AN and analog lines connected to it, to the LE FSM. If noerror exists in the GPP this log defines a hardware or setup error at theAN.


Severity Warning

FormatV5254 mmmdd hh:mm:ss xxxx <log_type> <pm_id>


Recieved in: <pm_id> V5ID <ID>

LE state: <LE_state>

AN state: <AN_state>

LEN: <line_equipment_number> DN: <directory number>

V5254 525


NN10275-909v14 12.01 06 October 2011



VariableDescription





interface_information Interface Activated Variable Information message The indicatedV5.2 interface has a state mismatch.

pm_id alphanumeric Variable Same as above.

LE_state alphanumeric Variable Event of the LE state machine.

AN_state alphanumeric Variable Event of the AN state machine





Active message exampleV5254 SEP05 18:14:33 1305 INFO GPP 0

PSTN state mismatch

LE state: NULL LE.

AN state: Path active AN5.

LEN: PDMX 00 1 00 01 DN: 9096214001



V5255The peripheral module (PM) subsystem generates this information reportwhen a protection protocol error is received from the access node (AN).



NN10275-909v14 12.01 06 October 2011


Remedial actionn/a


Severity Warning




Reason: <reason>



V5256THE PERIPHERAL MODULE (PM) SUBSYSTEM GENERATES THISINFORMATION LOG WHEN A LINK CONTROL PROTOCOL ERROR ISRECEIVED FROM THE ACCESS NODE (AN).

Remedial actionn/a


Severity Warning

FormatV5256 mmmdd hh:mm:ss ssdd INFO RMV5 05 0

Link Control protocol error received from AN.

Received in: GPP <GPP_no> V5id: <ID>

Reason: <text-1>

Affected link:<text-2>

V5256 527


NN10275-909v14 12.01 06 October 2011



VariableDescription




• Information element out ofsequence


• Repeated optional informationelement.




• Message not compatible with linkcontrol protocol state.


Affected link Integer 1 to 16 Variable V5 link number affected by the errorcondition.

Number should be in the range 1-16.Any number above 16 represents anL3 address error, because of out-of-range value received from accessnode.

INFO CONSTANT Fixed Indicated V5 information follows infield interface information.

GPP_number alphanumericcharacter string

Variable Specifies the global peripheralplatform (GPP) peripheral number.The number is an integer with a rangefrom 0 to 127.

V5ID see subfields Variable V5 interface identifier. Equates to fieldAMCNO in table GPPTRNSL.composed of subfields; SITE, FRAME,and UNIT.




NN10275-909v14 12.01 06 October 2011



Description




Link Control protocol error received from AN.

Received in: GPP 5 V5id: RMV5 5 0

Reason: Message type unrecognized.

Affected link: 2



V5257The peripheral module (PM) subsystem generates this log report when aPort Control Protocol Error message is received.

Remedial actionContact the supporter of the AN vendor.


Severity Warning



Received in: GPP <gpp_no> V5id: <ID>

V5257 529


NN10275-909v14 12.01 06 October 2011


Reason: <reason>

LEN: <line_equipment_number> DN: <directory_number>


VariableDescription







numeric Variable Virtual line equipment numberassigned to line in table LNINV.

directory_number (up to 15 digits) Variable numeric Directory number assigned toline.

Active message exampleV5257 FEB12 11:21:41 4150 INFO V5AN 00 1

Port Control protocol error received from AN.

Received in: GPP 1 V5id: V5AN 0 1

Reason: Protocol discriminator error.

LEN: V5AN 00 1 00 22 DN: 9096214001




NN10275-909v14 12.01 06 October 2011



V5260The DMS switch generates a V5260 log report if the local exchange tries touse the Accelerated Port Alignment (APA) feature. The APA featurereduces the number of messages required to set up access from anaccess network (AN) to the local exchange. The feature sends a singleblock/unblock message to align the switches'' port states, instead ofaligning each port by using separate messages.

The switch generates V5260 logs for the reasons that are explained in thefollowing.

Accelerated Port Alignment was Successful: The access network acceptedthe request to align and unblock its ports, and the local exchangeunblocked its ports.

Accelerated Port Alignment rejected by the AN: The access network doesnot support the APA feature. Ports are unblocked one port at a time.

Accelerated Port Alignment TU1 timer expired: The timer controlling theAPA function expired. Ports are unblocked one port at a time.

Accelerated Port Alignment TU2 timer expired: A timer expired while thelocal exchange was waiting for the access network to unblock its ports.

Unexpected Accelerated Port Alignment Message Received: An APAmessage was received when a message was not expected.

Remedial actionIf the log reason is "Accelerated Port Alignment TU2 timer expired," checkthe port states of the local exchange and the access network to ensure thatthey match. If the port states do not match, restart the interface.

No action is required if the log was generated for the following reasons:

• Accelerated Port Alignment was Successful

• Accelerated Port Alignment rejected by the AN

• Accelerated Port Alignment TU1 timer expired

• Unexpected Accelerated Port Alignment Message Received


Severity Warning

V5260 531


NN10275-909v14 12.01 06 October 2011


FormatCPM2AB V5260 mmmdd hh:mm:ss INFO APA

Accelerated Port Alignment message received

Reason: <Reason>

V5id: <Site> <Frame> <Group>


VariableDescription

Reason string Variable The reason the log report wasgenerated. Refer to the explanationsin the "Additional information" section.

Site string Variable The access network site.

Frame numeric, 00 to 99 Variable The frame serving the local exchangeinterface.

Group numeric, 0 to 9 Variable The group serving the local exchangeinterface.

Active message exampleCPM2AB V5260 APR30 08:13:00 INFO APA

Accelerated Port Alignment message received

Reason: Accelerated Port Alignment was Successful

V5 id: KOKI 34 7



V5300The peripheral module (PM) subsystem generates this information reportdaily. This log report lists total C-channel frames and error counts.

Remedial actionn/a



NN10275-909v14 12.01 06 October 2011



Severity Warning

FormatV5300 mmmdd hh:mm:ss xxxx <log_type> FRAMES ERROR C-CHNL<interface_information>

C-channel: <C-chnl_number> Link: <link_number> <ID> <pm_id>Frames received in total : <rec_frm_cnt> In error:<r_err_frm

cnt><%>

Frames transmitted in total: <xmit_frm_cnt> Inerror:<t_err_frm cnt><%>


VariableDescription

log_type INFO Variable Information log. Refer to interfaceinformation field.

interface_information alphanumeric string Variable V5.2 link total frame and error countswith percentage errored rates on theC-channel for preceding 24 hours.

C-chnl_number 16, 15 or 31 Variable C-channel number. PCM30 channelcarrying control informaton on theV5.2 link.

C-channels can only be located onPCM30 link channels 16, 15, or 31.






V5300 533


NN10275-909v14 12.01 06 October 2011



Description




rec_frm_cnt numeric Variable Total number of frames received.

r_err_frm_cnt numeric Variable Total number of errored framesreceived.

% percentage Variable Percentage of errored receivedframes to total received frames.

xmit_frm_cnt numeric Variable Total number of frames transmitted.

t_err_frm_cnt numeric Variable Total number of errored framestransmitted

Active message exampleV5300 SEP05 18:14:33 6000 INFO FRAMES ERROR C-CHNL

C-channel: 16 Link: 0 RMV5 5 1 GPP 5

Frames received in total: 567 In error: 45 7.9%

Frames transmitted in total 345 In error: 45 13.0%



V5301The peripheral module (PM) subsystem generates this information reportdaily. This log report lists total V5 errors on the switch, time lost to errors,and percentage of errored and retransmitted frames.

Remedial actionn/a


Severity Warning



NN10275-909v14 12.01 06 October 2011


FormatV5301 mmmdd hh:mm:ss xxxx <log_type> FRAMES REPORT

Percentage of errored frames on V5 switch: <err_frm_%>

Percentage of retransmitted frames on V5 switch: <re_xmit_%>

Number of bad C-channels reported is <err_C-chnl_cnt>

Abnormalities: <total_err_cnt> Minutes disrupted<err_min_cnt>


VariableDescription

log_type INFO Variable Information log. Total V5.2 erroredand retransmitted frames during thepreceding 24 hours.

err_frm_% percentage Variable Percentage of errored V5 frames.

re_xmit_% percentage Variable Percentage of frames retransmitted.

err_C-chnl_cnt numeric Variable Number of bad C-channels reported.

total_err_cnt numeric Variable Total count of all V5 errors occurringon a switch.

err_min_cnt numeric Variable Total amount of minutes lost on V5interfaces to errors.

Active message exampleV5301 SEP05 18:14:33 9600 INFO FRAMES REPORT

Percentage of errored frames on V5 switch: 9.8%

Percentage of retransmitted frames on V5 switch: 13.0

Number of bad C-channels reported <err_C-chnl_cnt>

Abnormalities: 0 Minutes disrupted: 0


V5301 535


NN10275-909v14 12.01 06 October 2011



V5302The peripheral module (PM) subsystem generates this information reportdaily. This log report lists the abnormality rate of V5 interfaces connectedto a DMS switch.

Remedial actionn/a



• Major

FormatV5302 mmmdd hh:mm:ss xxxx <log_type> L2 ABNORMALITY RATE

Abnormality Threshold: <threshold_limit>

C-channel: <C-chnl_num> Link: <link_num> <ID> <pm_id>

Abnormalities: <total_err_cnt> Minutes disrupted<err_min_cnt>


VariableDescription

log_type INFO Variable Information log. Refer to interfaceinformation field.

constant L2 ABNORMALITYRATE

Variable Log contains the number of frameswith abnormal or faulty layer2addresses in the preceding 24 hours.

threshold_limit numeric Variable Threshold limit before link major alarm(LKMJALM) is set. Defined in tableV5PROV.

C-chnl_number 16, 15, or 31 Variable C-channel number. The channel onthe PCM30 V5.2 link that has errors.

C-channels can only be located onPCM30 link channels 16, 15, 31.




NN10275-909v14 12.01 06 October 2011



Description








total_err_cnt numeric Variable Total count of all L2 abnormalitiesoccurring on a V5 access node (AN)link.

err_min_cnt numeric Variable Total amount of minutes V5 link wasdisrupted.

Active message exampleV5302 SEP05 18:14:33 9600 INFO FRAMES REPORT

Abnormality Threshold: 4

C-channel: 16 Link: 0 RMV5 11 GPP 9

Abnormalities: 0 Minutes disrupted: 0



VIP101The system generates the VIP101 log when the VIP command limitsaccess to a specific local exchange code (LEC) to very important person(VIP) subscribers only.

VIP101 537


NN10275-909v14 12.01 06 October 2011


Remedial actionThis is a read-only log. There is no action required.


Severity Warning

Format<Ofc_id><Report_id><time_of_trace><seq_no> INFO VIP SERVICEON

SERVICE TO LOCAL EXCHANGE CODE <lec> IS BEING

RESTRICTED TO VIP SUBSCRIBERS.


VariableDescription

INFO VIP SERVICEON

constant Fixed This field indicates that VIP service isactive.

SERVICE TO LOCALEXCHANGECODE<lec>IS BEINGRESTRICTED TOVIP SUBSCRIBERS

constant Fixed This field indicates that VIP servicerestricts access to the lee indicated.The lee value in this field indicates theaffected lee. The lee value can rangefrom 000 to 999.

Active message exampleOFFICECLLI VIP101 JAN01 09:01:38 1234 INFO VIP SERVICE ON

SERVICE TO LOCAL EXCHANGE CODE 237 IS BEING RESTRICTED TO

VIP SUBSCRIBERS.



VIP102The system generates the VIP102 log when the VIP command restoresservice to all subscribers of a local exchange code (LEC).




NN10275-909v14 12.01 06 October 2011



Severity Warning

Format<Ofc_id> <Report_id> <time_of_trace> <seq_no> INFO VIPSERVICE OFF

SERVICE TO LOCAL EXCHANGE CODE <lec> HAS BEEN RESTORED

TO ALL SUBSCRIBERS.


VariableDescription

INFO VIP SERVICEOFF

constant Fixed This field indicates that VIP service isnot active.

SERVICE TO LOCALEXCHANGECODE<lec>HASBEEN RESTOREDTO ALLSUBSCRIBERS

constant Fixed This field indicates that VIP servicehas restored access to the leeindicated to all subscribers. The leevalue in this field indicates theaffected lee. The lee value can rangefrom 000 to 999.

Active message exampleOFFICECLLI VIP102 JAN01 09:01:38 1234 INFO VIP SERVICE OFF

SERVICE TO LOCAL EXCHANGE CODE 237 HAS BEEN RESTORED TO ALL

SUBSCRIBERS.



VIP103The system generates the VIP103 log when the VIP command restoresaccess to all local exchange codes (LECs).


VIP103 539


NN10275-909v14 12.01 06 October 2011



Severity Warning

Format<Ofc_id> <Report_id> <time_of_trace> <seq_no> INFO VIPSERVICE OFF

SERVICE TO ALL LOCAL EXCHANGE CODES HAS BEEN RESTORED TO ALL

SUBSCRIBERS.


VariableDescription

INFO VIP SERVICEOFF

constant Fixed This field indicates that VIP service isnot active.

SERVICE TO ALLLOCAL EXCHANGECODES HAS BEENRESTORED TO ALLSUBSCRIBERS

constant Fixed This field indicates that VIP servicehas restored access to all localexchange codes to all subscribers.

Active message exampleOFFICECLLI VIP103 JAN01 09:01:38 1234 INFO VIP SERVICE OFF

SERVICE TO ALL LOCAL EXCHANGE CODES HAS BEEN RESTORED TO ALL

SUBSCRIBERS.



VIP104The system generates the VIP104 log when the journal file is inactive andthe VIP command limits or restores access to a specific local exchangecode (LEC).

Remedial actionThere is no action required unless the journal file is inactive and the switchmust be rebooted. The information in these logs is used to bring theservice status of each LEC up to date.



NN10275-909v14 12.01 06 October 2011



Severity Warning

Format<Ofc_id> <Report_id> <time_of_trace> <seq_no> INFO NOJOURNAL FILE

THE VIPCODES TABLE WAS UPDATED WHILE THE JOURNAL

FILE WAS INACTIVE. THE NEW TUPLE IS:

<vipcodes tuple>


VariableDescription

INFO NO JOURNALFILE

constant Fixed This field indicates that journal file isnot active.

THE VIPCODESTABLE WASUPDATED WHILETHE JOURNAL FILEWAS INACTIVE. THENEW TUPLEIS:<vipcodes tuple>

constant Fixed This field indicates that the vipcodestable was updated while the journalfile was inactive. The vipcodes tuplevalue in this field indicates the newvipcodes tuple.

Active message exampleOFFICECLLI VIP104 JAN01 09:01:38 1234 INFO NO JOURNAL FILE

THE VIPCODES TABLE WAS UPDATED WHILE THE JOURNAL FILE WAS

INACTIVE. THE NEW TUPLE IS:

237 N



VML101The log report is generated when the waiting flag status setting isunsuccessful.

VML101 541


NN10275-909v14 12.01 06 October 2011


This log report is defined in module VMLLOGE.

Remedial actionIf this log report was not generated during a DUMP process, this is not acustomer-resolvable problem. Contact Nortel Networks product support torefer the problem to a voice mail system developer (TX1).


Severity Warning

FormatTEST_CAP VML101 DEC14 07:03:13 4400 INFO VOICEMAIL

VOICE MAIL MESSAGE LINK: <link_number>

SET MESSAGE WAITING BIT: <result>

SUBSC: <mobile_dn network subscriber''s No.>


VariableDescription

link_number 0 to 15 (decimal) Variable The number of the High Data LinkController (HDLC)

result ' ', 'IGN' Variable Result of message waiting flag settingto ON/OFF is unsuccessful.

mobile_dn networksubscriber's No.

4 bytes Variable The subscriber's network number(mobile DN).

Active message exampleTEST_CAP VML101 DEC14 07:03:13 4400 INFO VOICEMAIL

VOICE MAIL MESSAGE LINK: #0000

SET MESSAGE WAITING BIT: IGN

SUBSC: 602001




NN10275-909v14 12.01 06 October 2011



VML102This log report is generated when the message waiting status in a receivedmessage is neither ON (1) nor OFF (0).


Remedial actionThis is not a customer-resolvable problem. Contact Nortel Networksproduct support to refer the problem to a voice mail system developer(TX1).


Severity Warning



UNKNOWN MESSAGE WAITING FLAG STATUS: <message waiting

status code>

SUBSC: <mobile_dn network subscriber''s No.>


VariableDescription


waiting status code 0 to 8 (decimal) Variable The message waiting code.

mobile_dn networksubscriber's No.

4 bytes Variable The subscriber's network number(from incoming message).



UNKNOWN MESSAGE WAITING FLAG STATUS: #0004

VML102 543


NN10275-909v14 12.01 06 October 2011


SUBSC: 602001



VML103This log report is generated when the subscriber''s DN in a receivedmessage is incorrect.




Severity Warning



INVALID DN RCVD

STATUS: <status_code>

COUNT: <digit_count>

DN: <mobile_dn>


VariableDescription


status code 0, 1 Variable The message waiting status code.



NN10275-909v14 12.01 06 October 2011



Description

digit_count 0 to 7 (decimal) Variable The number of digits in the mobile_dn.

mobile_dn 4 bytes Variable The subscriber's network number(from incoming message).



INVALID DN RCVD

STATUS: #0000

COUNT: #0007

DN: 3347028



VML104This log report is generated when the message type of the incomingmessage is illegal.




Severity Warning



VML104 545


NN10275-909v14 12.01 06 October 2011


UNKNOWN MESSAGE TYPE, MT = <message_type>


VariableDescription


message_type alphanumeric Variable The message type



UNKNOWN MESSAGE TYPE, MT = #0000



VML105This log report is generated when the number of digits in a subscriber''sDN in an incoming message is out of range.




Severity Warning



DN DIGIT COUNT OUT OF RANGE

STATUS: <status_code>



NN10275-909v14 12.01 06 October 2011


COUNT: <digit_count>


VariableDescription


status_code 0, 1 Variable The Voice Mail status code

digit_code 0 to 8 (decimal) Variable The number of digits in thesubscriber's DN



DN DIGIT COUNT OUT OF RANGE

STATUS: #0000

COUNT: #0009



VML106This log report is generated when the following maintenance message wasreceived: FW fatal error.


Remedial actionIf this log report occurs, the HDLC must be checked for correct operation.


Severity Warning



VML106 547


NN10275-909v14 12.01 06 October 2011


MTCE STATUS, STATUS = <mtce_status>


VariableDescription


mtce_status #003F Variable The maintenance status



MTCE STATUS, STATUS = #003F



VML107This log report is generated when the High Data Link Controller (HDLC) isout of service.


Remedial actionIf the DATA LINK fails, action must be taken corresponding to a<failure_reason>. In most cases the failure is caused by a hardwareproblem.


Severity Warning



HDLC DATA LINK IS OUT OF SERVICE

REASON: <failure_reason>



NN10275-909v14 12.01 06 October 2011



VariableDescription


failure_reason HDLC_INIT_FAILEDHDLC_DEACTIVATED_FAILEDHDLC_PROTOCOL_ERRHIGH_RNR_STATEBUFF_CAPACITY_HIGHCRC_ERROR_HIGHRTX_PERECNTAGE_HIGHBUFFERS_OVERFLOWCKT_STATUS_BLK

Variable The failure reason



HDLC DATA LINK IS OUT OF SERVICE

REASON: HIGH_RNR_STATE



VML108This log report is generated when the High Data Link Controller (HDLC)returns to service.


Remedial actionn/a

VML108 549


NN10275-909v14 12.01 06 October 2011



Severity Warning



HDLC DATA LINK RETURNS TO SERVICE

REASON: <rts_reason>


VariableDescription


rts_reason RNR_STATE_OVERBUFF_CAPACITY_OKWATCHDOG_RESET_COMPLETE

Variable The return to service reason



HDLC DATA LINK RETURNS TO SERVICE

REASON: RNR_STATE_OVER



VML109This log report is generated when mailbox usage is over the critical level(for example, TMX100 does not have enough time to process TX1messages).




NN10275-909v14 12.01 06 October 2011


Remedial actionIf this log report occurs with <usage_part> more than 90, there may benon-processed messages from TX1. A special audit on TX1 office (in non-strenuous period) is run to send the status of all subscribers from TX1 toTMX100.


Severity • Critical

• Warning

FormatVOICE MAIL MESSAGE LINK: <link_number>

MB IS <usage_part> FULL


VariableDescription


usage_part 90 to 100 (decimal) Variable The usage part (as a percentage).



MB IS 95 FULL



VML110This log report is generated when the far end is disconnected.


VML110 551


NN10275-909v14 12.01 06 October 2011




Severity Warning



FAR_END_DISCONNECT


VariableDescription




FAR_END_DISCONNECT








NN10275-909v14 12.01 06 October 2011



Severity Warning



FAR_END_DISCONNECT


VariableDescription




MB IS FULL







Severity Warning

VML112 553


NN10275-909v14 12.01 06 October 2011



UNKNOWN MTCE STATUS FW FATAL ERROR STATUS


UNKNOWN MTCE STATUS FW FATAL ERROR STATUS



WTNP101The DMS-100 MMP switch generates a WTNP101 log report if translationproblems occur when calls are redirected by the local number portabilityfeature.

A WTNP101 log report indicates one of the following problems:

• The routing code prefix on the incoming call matches the office''s homerouting code (HRC), but the called DN has not been ported in by thisoffice. This problem can occur if an incorrect routing code has beenassigned to the ported-out DN at the donor office.

• The routing code prefix on the incoming call matches the office''s HRCand the called DN has been ported in by this office, but the PIP optionhas not been entered in the xxCODE or xxHEAD table for the ported-inDN''s SNPA-NXX range.

Remedial actionExamine the local number portability translations to determine if datafillproblems have occurred with this switch. Ensure that the HRC and PIPoptions have been datafilled correctly in the xxCODE and xxHEAD tables.Examine the calling party information in the log report and identify thedonor node in which this office''s HRC was prefixed to the called DN.Ensure that translations for the ported-out DN are correct at the donornode.





NN10275-909v14 12.01 06 October 2011


FormatWTNP101 mmmdd hh:mm:ss ssdd TBL WT NP Routing Code Mismatch

Routing Code <routing code prefix>

Called DN <calledDN>

Calling Pty <calling party>

Cannot Route Call to Ported DN at Recipient Switch.


VariableDescription

routing code prefix 6-digit number Variable The routing code prefix used to routethe call to this switch.

called DN DN in national 11-digitformat

Variable A DN that is believed to be ported into this switch.

calling party either a LEN andassociated DN, or theCLLI of an incomingtrunk

Variable The line or trunk from which the calloriginated.

Active message exampleWTNP101 JUL01 15:41:50 2100 TBL WT NP Routing Code Mismatch

Routing Code 505050

Called DN 01818117777

Calling Pty LEN HOST 31 0 02 02

Cannot Route Call to Ported DN at Recipient Switch.



WTNP102The DMS-100 MMP switch generates a WTNP102 log report when atranslation error occurs in the local number portability feature. This logreport indicates that a ported-out DN in the donor node is present in table

WTNP102 555


NN10275-909v14 12.01 06 October 2011


DNINV, but a corresponding entry does not exist in table DNPORT. Theported-out DN must be listed in table DNPORT so that the switch can routethe call to the correct recipient switch.

If you use SERVORD to change a DN''s intercept to PODN, the switchcreates a tuple for the ported-out DN in table DNPORT.

If you use SERVORD to change the intercept for a ported-out DN to BLDN,the switch deletes the corresponding entry in table DNPORT.

Remedial actionExamine the datafill for the called DN in tables DNINV and DNPORT.Ensure that

• the DN is correctly entered with the PODN intercept in table DNINV

• the DN''s tuple is present in table DNPORT. If it is not, use SERVORDto change the intercept for the DN. See the "Additional information"section.



FormatWTNP102 mmmdd hh:mm:ss ssdd TBL WT NP Datafill Missing

Called DN <directory number>

Ported-Out DN has no datafill in Table DNPORT.


VariableDescription

directory number DN in national 11-digitformat

Variable A DN that is listed as a ported-out DNin table DNINV.

Active message exampleWTNP102 JUL15 15:31:40 7600 TBL WT NP Datafill Missing

Called DN 01628797005

Ported-Out DN has no datafill in Table DNPORT.



NN10275-909v14 12.01 06 October 2011




XAC400 XA-Core Summary ReportThe system generates the XA-Core Summary Report log (XAC400) toprovide a summary of performance and maintenance information about theXA-Core for a 24-hour period.

Remedial actionn/a


Severity Warning

FormatXAC400 mmmdd hh:mm:ss ssdd INFO XA-Core Summary Report

TOTAL TRAPS IN LAST 24 HOURS: n

AVERAGE TRAPS PER MINUTE: n

LAST RESTART: MANUAL RELOAD mmm-dd hh:mm:ss

FAULT EVENT COUNTERS FOR LAST 24 HOUR PERIOD

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

PE Fault Events : n

SM Fault Events : n

IOP Fault Events : n

DISK Fault Events : n

TAPE Fault Events : n

RTIF Fault Events : n

Loc Port Fault Events: 0

Rem Port Fault Events: n

XAC400 XA-Core Summary Report 557


NN10275-909v14 12.01 06 October 2011


CMIC Fault Events : n

SYSTEM WARM restarts : n

MANUAL WARM Restarts : n

SYSTEM COLD Restarts : n

MANUAL COLD Restarts : n

XAC Trap Events : n

CURRENTLY DISABLED XA-CORE ALARMS

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

<alarm> <alarm>

CURRENTLY SOAKING FW

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

<card> <slot> <side> <packlet position>





VariableDescription

Reportid Alphanumeric Variable Indicates the log group (XAC) andidentification number of the log.

Event Type Character string Variable Indicates the type of event identified inthe log report.

Event Text Text string Variable Indicates describes the type of eventidentified in the log report.

TOTAL TRAPS INTHE LAST 24HOURS

Numeric Variable Indicates the total number of TRAPSdetected in the last 24 hours.

AVERAGE TRAPSPER MINUTE

Numeric Variable Indicates the average number ofTRAPS detected per minute.



NN10275-909v14 12.01 06 October 2011



Description

LAST RESTART intitiator=MANUAL, orSYSTEM restarttype=WARM, COLD,or RELOAD yyyy/mm/dd hh:mm:ss.nnn ccc.

Variable This field displays the followinginformation about the last restart:

initiator=The trigger that began thelast restart can either be MANUAL orSYSTEM restart.

restart type =The type of restart canbe WARM, COLD, or RELOADrestart.

yyyy/mm/dd=The year, month and dayof the last restart.

hh:mm:ss.nnn ccc.=The hour, minute,second, millisecond, and day of thelast restart.

FAULT EVENTCOUNTERS FORLAST 24 HOURPERIOD

Numeric Variable Indicates the number of XA-Coreevents for the last 24 hour period.

The system counts the followingevents for the last 24 hour period:

PE Fault Events

SM Fault Events

IOP Fault Events

DISK Fault Events

TAPE Fault Events

RTIF Fault Events

CMIC Fault Events

SYSTEM WARM Restarts

MANUAL WARM Restarts

SYSTEM COLD Restarts

MANUAL COLD Restarts

XAC Trap Events

CURRENTLYDISABLED XA-COREALARMS

Character string Variable Operating company personnel candisable XA-Core alarms fromdisplaying at the MAP.

Variable This field displays alarms that arecurrently disabled.

CURRENTLYSOAKING FW

Character string Variable Indicates the position of the card/packlet that is currently soakingfirmware (FW).



NN10275-909v14 12.01 06 October 2011


Active message exampleXAC400 OCT27 00:00:00 5600 INFO XA-Core Summary Report

TOTAL TRAPS IN LAST 24 HOURS: 0

AVERAGE TRAPS PER MINUTE: 0

LAST RESTART: MANUAL RELOAD OCT-26 18:04:15

FAULT EVENT COUNTERS FOR LAST 24 HOUR PERIOD

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

PE Fault Events : 2

SM Fault Events : 0

IOP Fault Events : 3

DISK Fault Events : 0

TAPE Fault Events : 0

RTIF Fault Events : 0

Loc Port Fault Events: 0

Rem Port Fault Events: 0

CMIC Fault Events : 1

SYSTEM WARM restarts : 0

MANUAL WARM Restarts : 0

SYSTEM COLD Restarts : 0

MANUAL COLD Restarts : 0

XAC Trap Events : 0

CURRENTLY DISABLED XA-CORE ALARMS

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

FWsoak FWvers

CURRENTLY SOAKING FW



NN10275-909v14 12.01 06 October 2011


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

CMIC 4 rear lower





NN10275-909v14 12.01 06 October 2011




NN10275-909v14 12.01 06 October 2011


C20 Converged Softswitch

Logs and Alarms Reference, Volume 14Release: CVM16 and upPublication: NN10275-909v14Document Revision: 12.01Document release date: 06 October 2011

Copyright © 2011 GENBAND. All rights reserved. Use of this documentation and its contents is subject to the terms and conditionsof the applicable end user or software license agreement, right to use notice, and all relevant copyright protections.

GENBAND, the GENBAND corporate logo and tagline, and certain of GENBAND's product and solution names are registeredtrademarks of GENBAND and its affiliates.

While the information in this document is believed to be accurate and reliable, except as otherwise expressly agreed to in writingGENBAND AND/OR ITS LICENSORS PROVIDES THIS DOCUMENT "AS IS" WITHOUT WARRANTY OR CONDITION OF ANYKIND, EITHER EXPRESS OR IMPLIED. The information and/or products described in this document are subject to changewithout notice.

THE INFORMATION CONTAINED HEREIN IS THE PROPERTY OF GENBAND OR ITS LICENSORS AND MUST NOT BEDISCLOSED, OTHER THAN TO EMPLOYEES OF GENBAND OR CUSTOMERS WITH NEED-TO-KNOW, WITHOUT THEPRIOR WRITTEN CONSENT OF GENBAND OR ITS LICENSORS. THE INFORMATION MUST NOT BE DISCLOSED TOSUBCONTRACTORS OR REGULATORY AUTHORITIES. GENBAND MUST BE NOTIFIED OF ANY REQUEST OR ORDERFOR DISCLOSURE PRIOR TO SUCH DISCLOSURE.

Software and documentation owned by or under license with Nortel Networks included in this Release or in any documentprovided with this Release is Copyright © 2010 Nortel Networks or its licensors. All rights reserved. Use of this software and/ordocumentation and its contents is subject to the terms and conditions of the applicable end user or software license agreement,right to use notice, and all relevant copyright protections. The product names remain as Carrier VoIP and CS 2000 in Canada and France pending regulatory approvals for a name change.

www.genband.com

nn10275 909v14 12.01 cvm16 c20 fault management logs alarms ref

Documents

clear message example

active message example

remedial action

selected field descriptions

property of genband

employees of genband

writing genband andor

genband corporate logo