Cisco BTS 10200 Troubleshooting Manual
  1. Manuals
  2. Brands
  3. Cisco Manuals
  4. Switch
  5. BTS 10200 Softswitch
  6. Troubleshooting manual
Cisco BTS 10200 Troubleshooting Manual

Cisco BTS 10200 Troubleshooting Manual

Softswitch
Hide thumbs Also See for BTS 10200:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
Table of Contents

Advertisement

Quick Links

Download this manual See also: User Manual, Manual
Cisco BTS 10200 Softswitch
Troubleshooting Guide, Release 5.0.x
Revised: July 22, 2009
Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 527-0883
Text Part Number: OL-8723-19

Advertisement

Table of Contents
loading

Related Manuals for Cisco BTS 10200

Summary of Contents for Cisco BTS 10200

  • Page 1 Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x Revised: July 22, 2009 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883 Text Part Number: OL-8723-19...
  • Page 2 OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks.

  • Page 3: Table Of Contents

    Viewing Event or Alarm Logs 1-14 Show, Add, and Delete Event Queue Commands 1-16 Saving Events to Log Files 1-16 Show Report-Properties Command 1-16 Changing Report Properties 1-16 Changing Threshold and Throttle Values 1-17 Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...
  • Page 4 Start or Stop of Signaling System 7–Circuit Identification Code Audit—Audit (2) 2-18 Signaling System 7 Circuit Identification Code Audit Terminated Before Successful Completion—Audit (3) 2-18 Call Exceeds a Long-Duration Threshold—Audit (4) 2-18 Critical Internal Audit Failure—Audit (5) 2-18 Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...
  • Page 5 Audit Found Lost Call Data Record—Audit (20) 2-27 Core File Present—Audit (25) 2-27 Billing Troubleshooting C H A P T E R Introduction Billing Events and Alarms BILLING (1) BILLING (2) BILLING (3) Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...
  • Page 6 3-14 BILLING (34) 3-14 BILLING (35) 3-14 BILLING (36) 3-15 BILLING (37) 3-15 BILLING (38) 3-16 BILLING (39) 3-16 BILLING (40) 3-17 BILLING (41) 3-17 BILLING (42) 3-18 BILLING (43) 3-18 Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...
  • Page 7 Billing Link Failure—Billing (37) 3-30 Event Message Log File Access Error—Billing (38) 3-30 Event Message Encode Failure—Billing (40) 3-30 Message Content Error—Billing (41) 3-30 Error Reading Provisioned Data–Using Default—Billing (42) 3-31 Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...
  • Page 8 3-41 Record Keeping System Unreachable for Three Hours—Billing (48) 3-41 Record Keeping System Unreachable for 5 Hours—Billing (49) 3-41 Bulk Data Management System Stopped Generating New Billing File—Billing (52) 3-42 Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x viii OL-8723-19...
  • Page 9 4-10 CALLP (21) 4-10 CALLP (22) 4-11 CALLP (23) 4-11 CALLP (24) 4-12 CALLP (25) 4-12 CALLP (26) 4-13 CALLP (27) 4-13 CALLP (28) 4-14 CALLP (29) 4-14 CALLP (30) 4-15 Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...
  • Page 10 Unable to Route: Blocked by Destination Subscriber Status—Call Processing (27) 4-27 Route Name Does Not Exist—Call Processing (28) 4-27 Routing Selection Failure—Call Processing (29) 4-27 Customer-Originated Trace Test Failed—Call Processing (30) 4-28 Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...
  • Page 11 4-30 INVITE Message From Unauthorized Call Agent—Call Processing (41) 4-30 Call Failed after Local Number Portability Query with Location Routing Number of this BTS 10200 and the Directory Number—Call Processing (42) 4-30 Call Processing Session Initiation Protocol Trigger Provisioning Error—Call Processing (43) 4-30 Call Processing No Session Initiation Protocol Trigger Context Found—Call Processing (44)
  • Page 12 Contents FIMXML Parse Error—Configuration (6) Application Server Provisioning Error—Configuration (7) BTS 10200 Provisioning for External Applications is not Complete—Configuration (8) Troubleshooting Configuration Alarms Mate Configuration Error—Configuration (3) Configuration Error—Configuration (4) Feature–Server Database and Command Line Host Mismatch—Configuration (5) Database Troubleshooting...
  • Page 13 Element Management System Database Replication DefTranDest Queue Overloaded—Database 6-30 Element Management System Database DefTran Queue is Overloaded—Database (7) 6-30 Element Management System Database Tablespace is Out of Free Space—Database (8) 6-31 Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x xiii OL-8723-19...
  • Page 14 MAINTENANCE (8) MAINTENANCE (9) MAINTENANCE (10) 7-10 MAINTENANCE (11) 7-10 MAINTENANCE (12) 7-11 MAINTENANCE (13) 7-11 MAINTENANCE (14) 7-12 MAINTENANCE (15) 7-12 MAINTENANCE (16) 7-13 MAINTENANCE (17) 7-13 MAINTENANCE (18) 7-14 Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...
  • Page 15 7-27 MAINTENANCE (49) 7-28 MAINTENANCE (50) 7-29 MAINTENANCE (51) 7-29 MAINTENANCE (52) 7-30 MAINTENANCE (53) 7-30 MAINTENANCE (54) 7-31 MAINTENANCE (55) 7-31 MAINTENANCE (56) 7-32 MAINTENANCE (57) 7-32 MAINTENANCE (58) 7-33 Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...
  • Page 16 7-47 MAINTENANCE (89) 7-47 MAINTENANCE (90) 7-48 MAINTENANCE (91) 7-48 MAINTENANCE (92) 7-49 MAINTENANCE (93) 7-49 MAINTENANCE (94) 7-50 MAINTENANCE (95) 7-50 MAINTENANCE (96) 7-51 MAINTENANCE (97) 7-51 MAINTENANCE (98) 7-52 Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...
  • Page 17 Local Initialization Failure—Maintenance (9) 7-71 Local Initialization Timeout—Maintenance (10) 7-71 Switchover Complete—Maintenance (11) 7-71 Initialization Successful—Maintenance (12) 7-71 Administrative State Change—Maintenance (13) 7-71 Call Agent Administrative State Change—Maintenance (14) 7-71 Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x xvii OL-8723-19...
  • Page 18 Central Processing Unit Usage is Now Below the 50% Level—Maintenance (52) 7-77 The Central Processing Unit Usage is Over 90% Busy—Maintenance (53) 7-78 The Central Processing Unit has Returned to Normal Levels of Operation—Maintenance (54) 7-78 Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x xviii OL-8723-19...
  • Page 19 Status Update Process Database Update Error—Maintenance (89) 7-84 Disk Partition Moderately Consumed—Maintenance (90) 7-84 Internet Protocol Manager Configuration File Error—Maintenance (91) 7-84 Internet Protocol Manager Initialization Error—Maintenance (92) 7-84 Internet Protocol Manager Interface Failure—Maintenance (93) 7-84 Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...
  • Page 20 Troubleshooting Maintenance Alarms 7-90 Local Side has Become Faulty—Maintenance (3) 7-92 Mate Side has Become Faulty—Maintenance (4) 7-92 Changeover Failure—Maintenance (5) 7-93 Changeover Timeout—Maintenance (6) 7-93 Mate Rejected Changeover—Maintenance (7) 7-94 Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...
  • Page 21 Local Domain Name System Server Response Too Slow—Maintenance (71) 7-105 External Domain Name System Server Response Too Slow—Maintenance (72) 7-105 External Domain Name System Server not Responsive—Maintenance (73) 7-105 Local Domain Name System Service not Responsive—Maintenance (74) 7-105 Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...
  • Page 22 Periodic Shared Memory Database Backup Failure—Maintenance (119) 7-111 Operations Support System Troubleshooting C H A P T E R Introduction Operations Support System Events and Alarms OSS (1) OSS (2) OSS (3) OSS (4) Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x xxii OL-8723-19...
  • Page 23 Simple Network Management Protocol Authentication Error—Operations Support System (9) 8-15 Queue Processing Module Database Management Index Failed with Error—Operations Support System (10) 8-15 User Session Count Exceeds Major Threshold Limit—Operations Support System (14) 8-15 Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x xxiii OL-8723-19...
  • Page 24 SIGNALING (8) 10-6 SIGNALING (9) 10-6 SIGNALING (10) 10-7 SIGNALING (11) 10-7 SIGNALING (12) 10-8 SIGNALING (13) 10-8 SIGNALING (14) 10-9 SIGNALING (15) 10-9 SIGNALING (16) 10-10 SIGNALING (17) 10-10 Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x xxiv OL-8723-19...
  • Page 25 10-27 SIGNALING (48) 10-27 SIGNALING (49) 10-28 SIGNALING (50) 10-28 SIGNALING (51) 10-29 SIGNALING (52) 10-29 SIGNALING (53) 10-30 SIGNALING (54) 10-30 SIGNALING (55) 10-31 SIGNALING (56) 10-31 SIGNALING (57) 10-31 Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...
  • Page 26 SIGNALING (88) 10-47 SIGNALING (89) 10-48 SIGNALING (90) 10-48 SIGNALING (91) 10-49 SIGNALING (92) 10-49 SIGNALING (93) 10-50 SIGNALING (94) 10-51 SIGNALING (95) 10-52 SIGNALING (96) 10-52 SIGNALING (97) 10-53 Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x xxvi OL-8723-19...
  • Page 27 SIGNALING (128) 10-69 SIGNALING (129) 10-69 SIGNALING (130) 10-69 SIGNALING (131) 10-69 SIGNALING (132) 10-69 SIGNALING (133) 10-70 SIGNALING (134) 10-70 SIGNALING (135) 10-71 SIGNALING (136) 10-72 SIGNALING (137) 10-73 Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x xxvii OL-8723-19...
  • Page 28 SIGNALING (168) 10-87 SIGNALING (169) 10-88 SIGNALING (170) 10-88 SIGNALING (171) 10-89 SIGNALING (172) 10-89 SIGNALING (173) 10-90 SIGNALING (174) 10-90 SIGNALING (175) 10-91 SIGNALING (176) 10-91 SIGNALING (177) 10-92 Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x xxviii OL-8723-19...
  • Page 29 Release Complete Received in Response to Reset Circuit Message on the Specified Circuit Identification Code—Signaling (43) 10-103 Continuity Recheck is Performed on Specified Circuit Identification Code—Signaling (44) 10-104 Circuit is UNEQUIPPED on Remote Side—Signaling (45) 10-104 Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x xxix OL-8723-19...
  • Page 30 10-109 Integrated Services Digital Network Single D-channel Down for Non-Facility Associated Signaling—Signaling (78) 10-109 Trunking Gateway Unreachable—Signaling (79) 10-110 Out of Bounds, Memory/Socket Error—Signaling (80) 10-110 Insufficient Heap Memory—Signaling (81) 10-110 Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...
  • Page 31 Aggregation Connection Down—Signaling (103) 10-113 Aggregation Unable To Establish Connection—Signaling (104) 10-113 Aggregation Gate Set Failed—Signaling (105) 10-113 Enhanced Subscriber Authentication BTS 10200 Delivery Function Connection Down—Signaling (106) 10-114 Logical Internet Protocol Addresses not Mapped Correctly—Signaling (107) 10-114 Simplex Only Operational Mode—Signaling (108) 10-114 Stream Control Transmission Protocol Association Failure—Signaling (109)
  • Page 32 Integrated Services Digital Network Signaling Gateway Inactive—Signaling (157) 10-122 Invalid Integrated Services Digital Network Interface Identification—Signaling (158) 10-122 Integrated Services Digital Network User Adaptation Layer can not Go Active—Signaling (159) 10-123 Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x xxxii OL-8723-19...
  • Page 33 Signaling System 7 Signaling Link Down—Signaling (13) 10-133 Signal System 7 and Call Agent Fail-over Interaction 10-133 Link is Remotely Inhibited—Signaling (14) 10-133 Link is Locally Inhibited—Signaling (15) 10-133 Link is Congested—Signaling (16) 10-134 Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x xxxiii OL-8723-19...
  • Page 34 10-142 Invalid Call Identifier—Signaling (92) 10-142 Invalid Call Reference Value—Signaling (93) 10-142 Invalid Conference Identifier—Signaling (94) 10-142 Invalid Message from the Network—Signaling (95) 10-143 Internal Call Processing Error—Signaling (96) 10-143 Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x xxxiv OL-8723-19...
  • Page 35 Per Call Security Violation—Signaling (101) 10-144 H323 Network Congested—Signaling (102) 10-144 Aggregation Connection Down—Signaling (103) 10-144 Enhanced Subscriber Authentication BTS 10200 Delivery Function Connection Down—Signaling (106) 10-144 Logical Internet Protocol Addresses not Mapped Correctly—Signaling (107) 10-145 Simplex Only Operational Mode—Signaling (108) 10-145 Stream Control Transmission Protocol Association Failure—Signaling (109)
  • Page 36 STATISTICS (7) 11-4 STATISTICS (8) 11-5 STATISTICS (9) 11-6 STATISTICS (10) 11-7 STATISTICS (11) 11-8 STATISTICS (12) 11-9 STATISTICS (13) 11-10 STATISTICS (14) 11-10 STATISTICS (15) 11-11 STATISTICS (16) 11-11 Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x xxxvi OL-8723-19...
  • Page 37 System Events and Alarms 12-1 SYSTEM (1) 12-2 SYSTEM (2) 12-2 SYSTEM (3) 12-3 SYSTEM (4) 12-4 SYSTEM (5) 12-5 SYSTEM (6) 12-5 SYSTEM (7) 12-6 SYSTEM (8) 12-6 SYSTEM (9) 12-7 Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x xxxvii OL-8723-19...
  • Page 38 Multiple Readers and Multiple Writers Queue Reached Low Queue Depth—System (14) 12-17 Multiple Readers and Multiple Writers Throttle Queue Depth Reached—System (15) 12-17 Network Troubleshooting 13-1 C H A P T E R Introduction 13-1 Troubleshooting a Network Failure 13-1 Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x xxxviii OL-8723-19...
  • Page 39 Outgoing H.323 Gateway is Out of Service 14-25 H.323 Gateway Fails to Register With Gatekeeper (Invalid Alias) 14-26 Outgoing H.323 Gateway Unregistered With Gatekeeper and Needs to Use Registration, Admissions, and Status 14-27 Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x xxxix OL-8723-19...
  • Page 40 Troubleshooting the Timeout Queue 14-47 Troubleshooting QoS 14-48 Troubleshooting Audit Connection 14-48 Multi-Lingual Support Troubleshooting 14-49 Viewing Trace Logs for Throttled Flood of MGCP Messages from Specific Endpoint 14-50 Platform Core File Alarm 14-50 Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...
  • Page 41 15-32 Example 2 15-34 Example 3 15-36 Example 4 15-38 Example 5 15-40 Network Loopback Test for Network-based Call Signaling/Media Gateway Control Protocol Endpoints 15-41 Overview 15-42 Restrictions 15-42 Installing 15-42 Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...
  • Page 42 Clearing Current Interval Counts 15-82 Measurements 15-84 ISDN Protocol Counters 15-85 Call Processing Counters 15-88 MGCP Adapter Counters 15-95 Session Initiation Protocol Counters 15-97 BTS 10200 Status 15-100 System Context for BTSSTAT 15-102 Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x xlii OL-8723-19...
  • Page 43 15-113 Test Overview 15-113 Cisco BTS 10200 Originating Test Line 15-114 Function 15-114 Test Equipment 15-114 Test Line 15-114 Trunk Access 15-114 Trunk Access and Test Termination Number Format 15-115 Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x xliii OL-8723-19...
  • Page 44 Restarting a Cisco BTS 10200 Softswitch Process 16-1 Disaster Recovery From Flash Archive 16-1 Before You Begin 16-2 Flash Archive Restore 16-3 Setting up Interfaces 16-5 Restoring the BTS 10200 Application 16-6 Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x xliv OL-8723-19...
  • Page 45 16-41 Platform Configuration 16-41 Troubleshooting 16-42 Switchover in Progress–Maintenance (101) 16-42 Side Automatically Restarting Due to Fault–Maintenance (117) 16-42 Disk Replacement 17-1 C H A P T E R Introduction 17-1 Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...
  • Page 46 MGCP-RTO-MAX B-23 MGCP-MAX2-RETRIES and MGCP-T-MAX B-24 Keepalive Process B-25 Scenario 1—MGW Reachable B-25 Scenario 2 (Special Case)—Reachable RGW with 16 or Fewer Endpoints and No Stable Calls In Progress B-28 Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x xlvi OL-8723-19...
  • Page 47 CPU Load of Critical Processes—Maintenance(113) C-13 Queue Length of Critical Processes—Maintenance(114) C-13 IPC Buffer Usage Level—Maintenance(115) C-13 CA Reports the Congestion Level of FS—Maintenance(116) C-13 Logs C-13 L O S S A R Y Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x xlvii OL-8723-19...
  • Page 48 Contents Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x xlviii OL-8723-19...
  • Page 49 It also includes details for aiding troubleshooting by utilizing diagnostic and trace procedures. Objective The maintenance personnel or troubleshooters of a BTS 10200 can use this document to better understand how to troubleshoot the BTS 10200 and quickly clear network problems. Audience This document is designed for engineers, technicians, and system administrators who troubleshoot and repair the BTS 10200.
  • Page 50 Call Agent shared memory. Chapter 17, “Disk Replacement”—Describes how to manually recover a BTS 10200 system. • Appendix A, “Recoverable and Nonrecoverable Error Codes”—Lists normal, recoverable and •...
  • Page 51 The update to Version OL-8723-15 included updating the Audit 4 alarm information. The update to Version OL-8723-16 included adding the “PSTN Trunk Testing” section on page 15-113. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...
  • Page 52 16-30. New Events and Alarms (Release 4.5.1 to Release 5.0) Table 1 lists the new events and alarms that were incorporated into the BTS 10200 system as part of the update from Release 4.5.1 to Release 5.0. Table 1 New Events and Alarms (Release 4.5.1 to Release 5.0)
  • Page 53 No Session Initiation Protocol P-DCS Billing Information Header Received (No SIP P-DCS Billing Info Hdr Rcvd) SIGNALING (168) A Session Initiation Protocol Server Group has no Child Elements Provisioned (A SIP Server Group has no Child Elements Provisioned) Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x liii OL-8723-19...
  • Page 54 No Resources Available to Launch ENUM Query SIGNALING (177) ISDN Unable to Restore D-Channel into In-Service Active State STATISTICS (14) MDII Trunk STATISTICS (15) Threshold Crossing Alert STATISTICS (16) Trunk Group has Reached the MDII Alarm Threshold Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...
  • Page 55 Preface Modified Events and Alarms (Release 4.5.1 to Release 5.0) Table 2 lists the BTS 10200 modified events and alarms that were modified as part of the upgrade from Release 4.5.1 to Release 5.0. Table 2 Modified Events and Alarms (Release 4.5.1 to Release 5.0)

  • Page 56: Obtaining Documentation And Submitting A Service Request

    Obtaining Documentation and Submitting a Service Request For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What’s New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at: http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html...

  • Page 57: Introduction

    Cisco BTS 10200 Softswitch. Interoperability The BTS 10200 inter-works with a wide range of network elements (NEs), but there are certain limitations. Cisco recommends that you keep the following caution in mind as you prepare to purchase and use NEs for your network.

  • Page 58: C H A P T E R 1 Troubleshooting Overview

    If you are having difficulty installing or starting your BTS 10200, it could be caused by provisioning problems, or by problems with initial status or control settings. If this is the case, your system should display one or more status or error messages.
  • Page 59 If a variable change does not resolve the network problem, change the variable back to its initial setting before proceeding. This allows the resolution of the network problem to be traced to a single variable change instead of a combination of variable changes. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...
  • Page 60 If you exhaust all the common causes and actions—either those outlined in this book or ones that you Note have identified for your environment—you should contact your Cisco technical support representative. Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request.

  • Page 61: Resolving Network Problems

    This way, you will create a problem and answer database that others in your organization can refer to in case similar problems occur later. This will invariably reduce the time to troubleshoot your networks and, consequently, minimize your business impact. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...

  • Page 62: Resolving System Problems

    If the procedures presented in this guide do not clear the problems, contact your technical support group. If additional support is needed, contact Cisco Technical Assistance Center (TAC) for assistance. When possible, have the following information on hand before calling Cisco TAC for technical support: •...
  • Page 63 Cisco TAC Cisco TAC will provide will provide detailed general guidance recommend- until problem ations. is resolved. Problem needs to be resolved with applicable supplier(s). Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...
  • Page 64 Done. HW repaired Did the successfully? problem clear? Next step Done. depends upon type of HW repaired or replaced. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...

  • Page 65: Managing Events And Alarms

    (CLI) commands or a Simple Network Management Protocol (SNMP) manager. The BTS 10200 software writes event and alarm messages to log files that are set up during system initialization. This section provides information on using and working with event and alarm log files.

  • Page 66: Managing Event And Alarm Reports

    Specifying a type and a number shows only alarms of that type and number. You can specify a number without specifying a type; and you can specify a type without specifying a number. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 1-10...

  • Page 67: Report Alarm Command

    • audit – billing – callp – config – database – maintenance – – security – signaling – statistics – – system Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 1-11 OL-8723-19...

  • Page 68: Ack Alarm Command

    The ID token is required for the ack alarm command, which acknowledges only the specified alarm. Note The ack alarm command only applies to BTS 10200 systems with the optional Call Control Unit (CCU) Alarm Panel installed. Clear Alarm Command Use the clear alarm command to clear an alarm.

  • Page 69: Format Of Alarm Reports

    (CALLP), CONFIG, DATABASE, MAINTENANCE, operations support system (OSS), SECURITY, SIGNALING, STATISTICS, or SYSTEM. Event or Alarm Number Event or alarm numbers are preset in the BTS 10200. They are not provisionable and cannot be changed. Event or Alarm Description Up to an 80-character description of the event or alarm.

  • Page 70: Events And Alarm Logs

    30,000 entries may be scrolled across the screen with no way to stop it. It may take an extended period of time to display all entries. These commands should ordinarily be issued with optional tokens. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 1-14...
  • Page 71 <yyyy-mm-dd hh:mm:ss> where: yyyy—year (4-digit number) – mm—month (01 to12) – dd—day (01 to 31) – hh—hour (00 to 23) – mm—minute (00 to 59) – ss—second (00 to 59) – Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 1-15 OL-8723-19...

  • Page 72: Show, Add, And Delete Event Queue Commands

    Use the following change report-properties command to specify the maximum number and/or the severity of event or alarm entries to be saved to the event or alarm logs: change report-properties type=<event-logsize|alarm-logsize>; value=<logsize>; change report-properties type=<event-level>; value=<severity> Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 1-16 OL-8723-19...

  • Page 73: Changing Threshold And Throttle Values

    Cisco recommends that you store events of all severity levels in the event and alarm log files by entering info as the value in this command. This permits the operator to access all event and alarm reports.

  • Page 74: Managing And Responding To Events And Alarms

    Step 9 clear alarm id=<sn> Where: is the system-assigned serial number of the event or alarm. Note Clearing of an alarm but not the symptom will cause the alarm to reappear. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 1-18 OL-8723-19...

  • Page 75: Events And Alarms Descriptions And Corrective Actions

    Events and Alarms Descriptions and Corrective Actions This section describes all the events and alarms that are generated by the BTS 10200 software. Each description includes the probable cause of the event or alarm and the corrective action that should be taken.
  • Page 76 The message type and number describe the type of alarm or event, the number assigned to the message, and the message text as it is displayed on the operator console or in a log file. BTS 10200 events and alarms are categorized into the following eleven types: AUDIT—Events or alarms generated by the audit subsystem. Refer to Chapter 2, “Audit...
  • Page 77 100. However, there are ways of setting the threshold to over 100 that must be coordinated with Cisco Customer Support. Setting the threshold to anything over 100 can cause performance degradation to the system. There are some events that have threshold over 100 as defaults.
  • Page 78 Chapter 1 Troubleshooting Overview Managing Events and Alarms Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 1-22 OL-8723-19...

  • Page 79: Introduction

    • audit alarms. Audit Events and Alarms This section provides a brief overview of the audit events and alarms for the Cisco BTS 10200 Softswitch in numerical order. Table 2-1 lists all of the audit events and alarms by severity.

  • Page 80: Chapter 2 Audit Troubleshooting

    THROTTLE DATAWORDS Type of Audit–STRING [64] PRIMARY The Signaling System 7 (SS7) circuit identification code (CIC) audit has started or stopped. CAUSE PRIMARY No action required. This is normal operation. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...

  • Page 81: Audit (3)

    Current long-duration threshold–TWO_BYTES PRIMARY A call exceeded the current system long-duration threshold. CAUSE PRIMARY If there is a reason to believe the call is no longer valid, release the associated trunk facility. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...

  • Page 82: Audit (5)

    DESCRIPTION Major Internal Audit Failure SEVERITY MAJOR THRESHOLD THROTTLE DATAWORDS Failure Details–STRING [220] Probable Causes–STRING [80] Corrective Actions–STRING [80] PRIMARY See the data field. CAUSE PRIMARY See the data field. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...

  • Page 83: Audit (7)

    THRESHOLD THROTTLE DATAWORDS Failure Details–STRING [220] Probable Causes–STRING [80] Corrective Actions–STRING [80] PRIMARY See the data field. CAUSE PRIMARY See the data field. ACTION AUDIT (9) AUDIT (9) is not used. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...

  • Page 84: Audit (10)

    Critical Network Time Protocol Service Failure (Critical NTP Service Failure) SEVERITY CRITICAL THRESHOLD THROTTLE DATAWORDS Failure Details–STRING [220] Probable Causes–STRING [80] Corrective Actions–STRING [80] PRIMARY See the data field. CAUSE PRIMARY See the data field. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...

  • Page 85: Audit (12)

    Minor Network Time Protocol Service Failure (Minor NTP Service Failure) SEVERITY MINOR THRESHOLD THROTTLE DATAWORDS Failure Details–STRING [220] Probable Causes–STRING [80] Corrective Actions–STRING [80] PRIMARY See the data field. CAUSE PRIMARY See the data field. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...

  • Page 86: Audit (14)

    Critical Index Shared Memory Error (Critical IDX Shared Memory Error) SEVERITY CRITICAL THRESHOLD THROTTLE DATAWORDS Failure Details–STRING [220] Probable Causes–STRING [80] Corrective Actions–STRING [80] PRIMARY See the data field. CAUSE PRIMARY See the data field. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...

  • Page 87: Audit (16)

    From UNIX prompt: date show_heap <pid of mga> > /opt/mga_heap.txt The show_heap command is not on the system by default. To obtain the show_heap tool contact Cisco TAC. Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request.

  • Page 88: Audit (17)

    From UNIX prompt: date show_heap <pid of mga> > /opt/mga_heap.txt The show_heap command is not on the system by default. To obtain the show_heap tool contact Cisco TAC. Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request.

  • Page 89: Audit (18)

    From UNIX prompt: date show_heap <pid of mga> > /opt/mga_heap.txt The show_heap command is not on the system by default. To obtain the show_heap tool contact Cisco TAC. Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request.

  • Page 90: Audit (19)

    “Obtaining Documentation and Submitting a Service Request” section on page lvi detailed instructions on contacting Cisco TAC and opening a service request. Prior to contacting Cisco TAC, collect a trace log corresponding to the time of the alarm. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x...

  • Page 91: Audit (20)

    Note detailed instructions on contacting Cisco TAC and opening a service request. Prior to contacting Cisco TAC, collect a trace log corresponding to the time of the alarm. AUDIT (21) To monitor and correct the cause of the event, refer to the “Quality of Service Gate Memory Audit...

  • Page 92: Audit (22)

    “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request. Prior to contacting Cisco TAC, collect a BTS 10200 trace log corresponding to the time of the event and collect the following additional information: From the CMTS: show packetcable gate summary show packetcable gate <gate id>...

  • Page 93: Audit (24)

    “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request. Prior to contacting Cisco TAC, collect a BTS 10200 trace log corresponding to the time of the event and collect the following additional information: From the CMTS:...

  • Page 94: Audit (25)

    2-27. Note While the BTS 10200 software directs its core files to the directory /bin, core files generated by non-BTS software (such as the platform operating system), are stored in the /opt/core directory. When a non-BTS-generated core dump occurs, the BTS 10200 issues an AUDIT 25 alarm, as it does for BTS 10200 core dumps, to indicate that such an incident occurred.

  • Page 95: Monitoring Audit Events

    Core File Present—Audit (25) MAJOR Test Report—Audit (1) The Test Report event is used for testing the audit event category. The event is informational and no further action is required. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 2-17 OL-8723-19...

  • Page 96: Completion—Audit (3)

    The Call Exceeds a Long-Duration Threshold event serves as a warning that a call has exceeded the current the BTS 10200 system long-duration threshold. If there is reason to believe the call is no longer valid, the associated trunk facility should be released.

  • Page 97: Major Internal Audit Failure—Audit (6)

    To troubleshoot and correct the cause of the Minor Network Time Protocol Service Failure alarm, refer to the “Minor Network Time Protocol Service Failure—Audit (13)” section on page 2-25. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 2-19 OL-8723-19...

  • Page 98: Network Time Protocol Service Warning—Audit (14)

    To troubleshoot and correct the cause of the Process Heap Memory Usage Exceeds Critical Threshold Level alarm, refer to the “Process Heap Memory Usage Exceeds Critical Threshold Level—Audit (18)” section on page 2-26. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 2-20 OL-8723-19...

  • Page 99: Recovered Memory Of Stale Call—Audit (19)

    To correct the secondary cause of the warning, check the adjacent network device protocol compatibility with the BTS 10200. The ternary cause of the warning is an internal software error. If a internal software error has occurred, contact Cisco TAC to obtain technical assistance.

  • Page 100: Recover Memory Of Dangling Gate—Audit (23)

    “Obtaining Documentation and Submitting a Service Request” section on page lvi detailed instructions on contacting Cisco TAC and opening a service request. Prior to contacting Cisco TAC, collect a BTS 10200 trace log corresponding to the time of the event and collect the following additional information:...

  • Page 101: Troubleshooting Audit Alarms

    To find the probable causes of the alarm, review the data field Failure Details and Probable Causes datawords. For the corrective actions for the alarm, review the data field Corrective Actions dataword. Once the Corrective Actions dataword has been reviewed, proceed with the corrective actions listed. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 2-23 OL-8723-19...

  • Page 102: Critical Network Time Protocol Service Failure—Audit (11)

    To gather additional troubleshooting information, use the following: From EMS: show ems From UNIX prompt: /opt/BTSxntp/bin/ntpq -c peers /opt/BTSxntp/bin/ntpq -c lpeers /opt/BTSxntp/bin/ntpq -c lopeers /opt/BTSxntp/bin/ntpq -c opeers cat /etc/inet/ntp.conf Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 2-24 OL-8723-19...

  • Page 103: Minor Network Time Protocol Service Failure—Audit (13)

    To show the process heap memory usage, use the following: From UNIX prompt: date show_heap <pid of mga> > /opt/mga_heap.txt The show_heap command is not on the system by default. To obtain the show_heap tool contact Cisco TAC. Note Refer to the “Obtaining Documentation and Submitting a Service Request”...

  • Page 104: Process Heap Memory Usage Exceeds Major Threshold Level—Audit (17)

    To show the process heap memory usage, use the following: From UNIX prompt: date show_heap <pid of mga> > /opt/mga_heap.txt The show_heap command is not on the system by default. To obtain the show_heap tool contact Cisco TAC. Note Refer to the “Obtaining Documentation and Submitting a Service Request”...

  • Page 105: Audit Found Lost Call Data Record—Audit (20)

    The Core File Present alarm (major) indicates that a network element process has crashed and that the BTS 10200 system has created a core file to assist in determining the root cause of the network element process crash. To correct the primary cause of the alarm, move the core file to a file server.
  • Page 106 Chapter 2 Audit Troubleshooting Troubleshooting Audit Alarms Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 2-28 OL-8723-19...

  • Page 107: Introduction

    The following billing records are created when a call is rejected due to overload conditions: Note • SS7 termination cause code 42 • Cable signaling stop event cause code “resource unavailable” Calls rejected by the signaling adapter will not generate a billing record. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...

  • Page 108: Billing Events And Alarms

    Billing Troubleshooting Billing Events and Alarms Billing Events and Alarms This section provides a brief overview of the billing events and alarms for the Cisco BTS 10200 Softswitch in numerical order. Table 3-1 lists all of the billing events and alarms by severity.

  • Page 109: Chapter 3 Billing Troubleshooting

    SECONDARY To monitor the alarm, use the subscribe alarm-report command. To obtain a summary, use the report ACTION alarm-summary command. Verify that type = billing is entered in the commands. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...

  • Page 110: Billing (3)

    ACTION alarm-summary command. Verify that type = billing is entered in the commands. TERNARY If the alarm does not clear (or step down to a reduced level) in a few minutes, contact Cisco Technical ACTION Assistance Center (TAC) for assistance.

  • Page 111: Billing (4)

    ACTION alarm-summary command. Verify that type = billing is entered in these commands. TERNARY If the alarm does not clear (or step down to a reduced level) in a few minutes, contact Cisco TAC for ACTION assistance. Refer to the “Obtaining Documentation and Submitting a Service Request”...

  • Page 112: Billing (6)

    Protocol (FTP), re-enter the password via the change billing-acct-addr command. If user-name is correct and the TransferType dataword shows Secure File Transfer Protocol (SFTP), verify that secure shell (SSH) keys have been pre-configured for the user-name on both the BTS 10200 and the remote host.

  • Page 113: Billing (7)

    “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request. If the alarm is repeating, collect a packet capture between the BTS 10200 and the billing server prior to contacting Cisco TAC. BILLING (8) To troubleshoot and correct the cause of the alarm, refer to the “Transmission Control Protocol Packet...

  • Page 114: Billing (9)

    PRIMARY Structured Query Language (SQL) server is down. CAUSE PRIMARY Restart server; if this does not correct the problem, call Cisco TAC technical support. (Contact Cisco ACTION TAC.) Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request.

  • Page 115: Billing (14)

    Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request. Prior to contacting Cisco TAC, collect the following information: From the UNIX prompt: sysdef -i df -k Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x...

  • Page 116: Billing (15)

    Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request. Prior to contacting Cisco TAC, collect the following information: From the UNIX prompt: sysdef -i...

  • Page 117: Billing (20)

    BILLING (24) is not used. BILLING (25) BILLING (25) is not used. BILLING (26) BILLING (26) is not used. BILLING (27) BILLING (27) is not used. BILLING (28) BILLING (28) is not used. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 3-11 OL-8723-19...

  • Page 118: Billing (29)

    THRESHOLD THROTTLE DATAWORDS Address–STRING [50] PRIMARY Wrong domain name system (DNS) name mapping specified in the configuration files. CAUSE PRIMARY Check the opticall.cfg and platform.cfg for the right mapping. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 3-12 OL-8723-19...

  • Page 119: Billing (31)

    Either the primary or secondary EMS address has not been specified in the platform.cfg file. CAUSE PRIMARY Check the platform.cfg for the process billing (BLG) and add the missing addresses to the file. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 3-13 OL-8723-19...

  • Page 120: Billing (33)

    CAUSE PRIMARY Restore the cable connection. ACTION SECONDARY An ifconfig down command might have been executed on the interfaces. CAUSE SECONDARY Execute an ifconfig up command on the interfaces. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 3-14 OL-8723-19...

  • Page 121: Billing (36)

    CAUSE PRIMARY Restore the cable connection. ACTION SECONDARY An ifconfig down command may have been performed on the interface. CAUSE SECONDARY Perform an ifconfig up command on the interface. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 3-15 OL-8723-19...

  • Page 122: Billing (38)

    Note Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi detailed instructions on contacting Cisco TAC and opening a service request. BILLING (39) BILLING (39) is not used. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x...

  • Page 123: Billing (40)

    Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request. BILLING (41) To troubleshoot and correct the cause of the alarm, refer to the “Message Content Error—Billing (41)”...

  • Page 124: Billing (42)

    Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request. BILLING (43) BILLING (43) is not used. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x...

  • Page 125: Billing (44)

    Location Tag–STRING [30] PRIMARY A log file has been created for the storage of event messages that cannot be transmitted to an RKS. CAUSE PRIMARY No action is necessary. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 3-19 OL-8723-19...

  • Page 126: Billing (46)

    Check status of the primary and secondary RKS servers; attempt to bring them into service. Verify that ACTION the radius-profile table and call-agent-profile table are provisioned such that communication with the RKS servers is possible. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 3-20 OL-8723-19...

  • Page 127: Billing (48)

    RKS servers is possible. BILLING (50) BILLING (50) is not used. BILLING (51) BILLING (51) is not used. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 3-21 OL-8723-19...

  • Page 128: Billing (52)

    The event message storage has reached 50% of the maximum storage allowed. CAUSE PRIMARY Move the event message files out of the specified directory. Store them in another location, or discard ACTION them. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 3-22 OL-8723-19...

  • Page 129: Billing (54)

    The event message storage has been completely filled. No additional event messages will be written CAUSE to disk until more space is made available. PRIMARY Move the event message files out of the specified directory. Store them in another location, or discard ACTION them. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 3-23 OL-8723-19...

  • Page 130: Billing (56)

    Note Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi detailed instructions on contacting Cisco TAC and opening a service request. BILLING (57) For additional information, refer to the “Prepaid Subscriber Call Attempt Failed Because of Balance—Billing (57)”...

  • Page 131: Billing (58)

    PRIMARY Check the operating status of the prepaid servers. ACTION SECONDARY The Internet Protocol (IP) network between the BTS 10200 plain old telephone service (POTS) Feature CAUSE Server (FS) and the prepaid servers is down. SECONDARY Check and correct any problems in the IP network.

  • Page 132: Monitoring Billing Events

    Record Keeping System Unreachable for Five Hours—Billing (49) CRITICAL BILLING(52) Bulk Data Management System Stopped Generating New Billing File—Billing (52) CRITICAL BILLING(53) Event Message Disk Space 50 Percent Full—Billing (53) MINOR Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 3-26 OL-8723-19...

  • Page 133: Test Report—Billing (1)

    Usage Critical Threshold Exceeded—Billing (4)” section on page 3-36. Billing Partition Disk Usage Within Normal Range—Billing (5) The Billing Partition Disk Usage Within Normal Range event is informational and no further action is required. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 3-27 OL-8723-19...

  • Page 134: File Transfer Protocol/Secure File Transfer Protocol Transfer Failed—Billing (6)

    Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request. Prior to contacting Cisco TAC, collect the following information: From the UNIX prompt: sysdef -i df -k Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x...

  • Page 135: File Write Error—Billing (15)

    File Transfer Protocol/Secure File Transfer Protocol Parameters Invalid alarm, refer to the “File Transfer Protocol/Secure File Transfer Protocol Parameters Invalid—Billing (33)” section on page 3-39. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 3-29 OL-8723-19...

  • Page 136: All Billing Links At Billing Server Down—Billing (35)

    The Message Content Error alarm (minor) indicates that a message content error has occurred. To troubleshoot and correct the cause of the Message Content Error alarm, refer to the “Message Content Error—Billing (41)” section on page 3-40. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 3-30 OL-8723-19...

  • Page 137: Error Reading Provisioned Data–Using Default—Billing (42)

    The primary cause of the error is that the application was unable to read provisioned data, and had to resort to using default values. Check to ensure a complete load has been installed on the BTS 10200 system. If the load is complete and problem persists, contact Cisco TAC.

  • Page 138: Record Keeping System Unreachable For Five Hours—Billing (49)

    The Billing Data Corruption Detected alarm (critical) indicates that a billing data corruption has been detected. To troubleshoot and correct the cause of the Billing Data Corruption Detected alarm, refer to “Billing Data Corruption Detected—Billing (56)” section on page 3-43. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 3-32 OL-8723-19...

  • Page 139: Prepaid Subscriber Call Attempt Failed Because Of Balance—Billing (57)

    CLI. To correct the primary cause of the event, execute a switchover or a platform restart so the change is propagated to the billing code. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 3-33...

  • Page 140: Troubleshooting Billing Alarms

    Event Message Disk Space 70 Percent Full—Billing (54) MAJOR BILLING(55) Event Message Disk Space 100 Percent Full—Billing (55) CRITICAL BILLING(56) Billing Data Corruption Detected—Billing (56) CRITICAL BILLING(58) Signaling Prepaid Server Inaccessible—Billing (58) MAJOR Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 3-34 OL-8723-19...

  • Page 141: Billing Partition Disk Usage Minor Threshold Exceeded—Billing (2)

    To monitor the alarm, use the subscribe alarm-report command. To obtain a summary, use the report alarm-summary command. Verify that type = billing is entered in these commands. If the alarm does not clear (or step down to a reduced level) in a few minutes, contact Cisco TAC for assistance.

  • Page 142: Billing Partition Disk Usage Critical Threshold Exceeded—Billing (4)

    Change the billing-server-addr, if necessary, by using the change billing-acct-addr command. The secondary cause of the alarm is that the BTS 10200 is unable to login to remote host. To correct the secondary cause of the alarm, use the show billing-acct-addr command to verify that the user-name is a valid user for the host specified in the billing-server-addr.

  • Page 143: Transmission Control Protocol Connection Error—Billing (7)

    BTS 10200 platform configuration. The secondary cause of the alarm is the BTS 10200 is not connected to the right address. To correct the secondary cause of the alarm, call Cisco TAC for technical support.

  • Page 144: Transmission Control Protocol Packet Receive Failure—Billing (8)

    The File Write Error alarm (major) indicates that a file write error has occurred. The primary cause of the alarm is that a system error has occurred. The BTS 10200 system may be out of file descriptors. To correct the primary cause of the alarm, contact Cisco TAC for technical support.

  • Page 145: Domain Name Mapping Failed—Billing (30)

    The Domain Name Mapping Failed alarm (major) indicates that a domain name mapping has failed. The primary cause of the alarm is that the wrong DNS server name mapping is specified in the BTS 10200 configuration files. To correct the primary cause of the alarm, check the opticall.cfg and platform.cfg files for the correct mapping information.

  • Page 146: Billing Link Failure—Billing (37)

    The Event Message Log File Access Error alarm (major) indicates that an EM log file access error has occurred. The primary cause of the alarm is that a system error has occurred. The BTS 10200 system may be out of file descriptors. To correct primary cause of the alarm, contact Cisco TAC. The secondary cause of the alarm is that a system hard drive may be faulty.

  • Page 147: Event Message Log File Opened—Billing (45)

    RKS servers and attempt to bring them into service. Verify that the radius-profile table and call-agent-profile table are provisioned such that communication with the RKS servers is possible. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 3-41 OL-8723-19...

  • Page 148: Bulk Data Management System Stopped Generating New Billing File—Billing (52)

    No additional event messages will be written to the disk until more space is made available. To correct the primary cause of the alarm, move the event message files out of the specified directory. Store them in another location, or discard them. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 3-42 OL-8723-19...
  • Page 149 The secondary cause of the alarm is that the IP network between the BTS 10200 POTS FS and the prepaid servers is down. To correct the secondary cause of the alarm, check and correct any problems in IP network.
  • Page 150 Chapter 3 Billing Troubleshooting Troubleshooting Billing Alarms Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 3-44 OL-8723-19...

  • Page 151: Introduction

    Troubleshooting Call Processing Alarms—Provides the information needed to troubleshoot and correct the call processing alarms. For additional call processing routing and translations information refer to the Cisco BTS 10200 Softswitch Routing, Translations, and Dial Plan Guide. Note The following billing records are created when a call is rejected due to overload conditions: •...
  • Page 152 Call Processing Troubleshooting Call Processing Events and Alarms Call Processing Events and Alarms This section provides a brief overview of the call processing events and alarms for the BTS 10200 in numerical order. Table 4-1 lists all of the call processing events and alarms by severity.

  • Page 153: Callp (1)

    CALLP (3) is not used. CALLP (4) CALLP (4) is not used. CALLP (5) CALLP (5) is not used. CALLP (6) CALLP (6) is not used. CALLP (7) CALLP (7) is not used. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...

  • Page 154: Callp (8)

    If the call is long distance using a presubscribed interexchange carrier (PIC), check that the PIC for ACTION this subscriber is properly provisioned in the dial-plan table. If necessary, edit these files using the change dial-plan or change subscriber commands. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...

  • Page 155: Callp (9)

    If the carrier-identification (ID) or route-grp-ID are not specified, or are incorrect, in the dial-plan ACTION table, enter the correct values. Use the change carrier or change route-grp command. CALLP (10) CALLP (10) is not used. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...

  • Page 156: Callp (11)

    SEVERITY CRITICAL THRESHOLD THROTTLE DATAWORDS Interface Name–STRING [65] Interface IP Address–STRING [65] Interface Name–STRING [65] Interface IP Address–STRING [65] PRIMARY The hardware is broken. CAUSE PRIMARY Check the link interfaces. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...

  • Page 157: Callp (13)

    MGW-NAME–STRING [80] PRIMARY The cable modem termination system (CMTS)/easily recognizable (ER) entry was not found in the CAUSE Media Gateway Table. PRIMARY Provision the CMTS-ER index in the Media Gateway Table. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...

  • Page 158: Callp (16)

    DESCRIPTION Invalid Route Index Used SEVERITY WARNING THRESHOLD THROTTLE DATAWORDS Route Index–FOUR_BYTES PRIMARY An invalid route index was used. CAUSE PRIMARY Correct the provisioning and assign a valid route index. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...

  • Page 159: Callp (18)

    4-26. DESCRIPTION Call Routed to Unprovisioned Subscriber SEVERITY WARNING THRESHOLD THROTTLE DATAWORDS Subscriber Index–FOUR_BYTES Directory Number Dia–STRING [20] PRIMARY A subscriber was not provisioned correctly. CAUSE PRIMARY Provision the subscriber. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...

  • Page 160: Callp (20)

    WARNING THRESHOLD THROTTLE DATAWORDS Calling Number–STRING [20] Called Number–STRING [20] Hop Count–FOUR_BYTES PRIMARY The number of hops between destinations is excessive. CAUSE PRIMARY Reduce number of hops between destinations. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 4-10 OL-8723-19...

  • Page 161: Callp (22)

    Routing Error: Termination is Not a Subscriber SEVERITY WARNING THRESHOLD THROTTLE DATAWORDS Termination Index–FOUR_BYTES Termination Type–FOUR_BYTES PRIMARY The destination termination is not provisioned as a subscriber. CAUSE PRIMARY Check the provisioning. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 4-11 OL-8723-19...

  • Page 162: Callp (24)

    Invalid Route Group for Subscriber Routing SEVERITY WARNING THRESHOLD THROTTLE DATAWORDS Route–STRING [20] Subscriber Index–FOUR_BYTES PRIMARY The route group is not provisioned correctly for the specified subscriber. CAUSE PRIMARY Check the provisioning. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 4-12 OL-8723-19...

  • Page 163: Callp (26)

    Unable to Route: Blocked by Destination Subscriber Status SEVERITY WARNING THRESHOLD THROTTLE DATAWORDS Subscriber Index–FOUR_BYTES Subscriber Status–STRING [20] PRIMARY The subscriber provisioning is not in the correct state. CAUSE PRIMARY Check the provisioning. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 4-13 OL-8723-19...

  • Page 164: Callp (28)

    DESCRIPTION Routing Selection Failure SEVERITY WARNING THRESHOLD THROTTLE DATAWORDS Route Index–FOUR_BYTES Calling Number–STRING [20] Called Number–STRING [20] PRIMARY The route is not correctly provisioned. CAUSE PRIMARY Check the provisioning. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 4-14 OL-8723-19...

  • Page 165: Callp (30)

    PRIMARY A customer-originated trace (COT) test has failed. CAUSE PRIMARY Contact Cisco for information on how to further debug the problem. (Contact Cisco Technical ACTION Assistance Center (TAC).) Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request.

  • Page 166: Callp (32)

    DATAWORDS Calling Number–STRING [20] Called Number–STRING [20] PRIMARY The call could not be completed because the number entered was invalid. CAUSE PRIMARY Check the provisioning and the number dialed. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 4-16 OL-8723-19...

  • Page 167: Callp (34)

    Dial Plan Index–FOUR_BYTES PRIMARY The test call could not be completed because the number entered could not be located in the dial-plan. CAUSE PRIMARY Check the provisioning and the number tested. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 4-17 OL-8723-19...

  • Page 168: Callp (36)

    “Obtaining Documentation and Submitting a Service Request” section on page lvi detailed instructions on contacting Cisco TAC and opening a service request. Prior to contacting Cisco TAC, collect a billing-record for the failed call using the following: report billing-record orignumber=<string>...

  • Page 169: Callp (38)

    The initial address message (IAM) for test call was blocked due to congestion or isolation. CAUSE PRIMARY Correct the congestion or isolation problem and place the test call again from a remote system. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 4-19 OL-8723-19...

  • Page 170: Callp (40)

    Reconfigure the call-agent table to have the authorized call agent (CA). ACTION SECONDARY A potential intrusion has occurred if the network-ID is mismatched from the local-network. CAUSE SECONDARY Configure the network to block the unauthorized network-ID. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 4-20 OL-8723-19...

  • Page 171: Callp (42)

    Routing Number of this BTS 10200 and the Directory Number—Call Processing (42)” section on page 4-30. DESCRIPTION Call Failed after Local Number Portability Query with Location Routing Number of this BTS 10200 and the Directory Number (Call Failed after LNP Query with LRN of this switch and the DN) SEVERITY INFO...

  • Page 172: Callp (44)

    THRESHOLD THROTTLE PRIMARY The BTS 10200 has received an INVITE from an AS which contains a context ID in the route header CAUSE which is invalid. It may be that the AS has not properly returned the Route Header. PRIMARY...

  • Page 173: Monitoring Call Processing Events

    Dial Plan Information for Test Call Not Found—Call Processing (35) WARNING CALLP(36) Invalid or Unknown Nature of Address—Call Processing (36) WARNING CALLP(37) Call Failure—Call Processing (37) WARNING CALLP(38) Release Cause 25 Exchange Routing Error Received—Call Processing (38) MINOR Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 4-23 OL-8723-19...

  • Page 174: Test Report—Call Processing (1)

    INVITE Message From Unauthorized Call Agent—Call Processing (41) MINOR CALLP(42) Call Failed after Local Number Portability Query with Location Routing Number of INFO this BTS 10200 and the Directory Number—Call Processing (42) CALLP(43) Call Processing Session Initiation Protocol Trigger Provisioning Error—Call WARNING Processing (43) CALLP(44) Call Processing No Session Initiation Protocol Trigger Context Found—Call...

  • Page 175: Feature Server One Link Down—Call Processing (11)

    To correct the cause of the event, correct the BTS 10200 provisioning by assigning a valid route index. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x...

  • Page 176: Unable To Play Announcement—Call Processing (18)

    The primary cause of the event is that the trunk group index could not be retrieved from the call data. To correct the primary cause of the event, check and correct the BTS 10200 trunk group and call data provisioning.

  • Page 177: Invalid Route For Subscriber Index—Call Processing (24)

    The Invalid Route for Subscriber Index event functions as a warning that an invalid route was selected for the subscriber index. The primary cause of the event is that the route is not provisioned correctly for the specified subscriber. To correct the primary cause of the event, check and correct the BTS 10200 subscriber index provisioning.

  • Page 178: Customer-Originated Trace Test Failed—Call Processing (30)

    The primary cause of the event is that the country code was not found in the dial plan. To correct the primary cause of the event, check and correct the BTS 10200 dial plan provisioning. Invalid Call—Call Processing (33) The Invalid Call event functions as a warning that an invalid call was attempted.

  • Page 179: Dial Plan Information For Test Call Not Found—Call Processing (35)

    To correct the primary cause of the event, check the data words type of call (four bytes), calling number (20), called number (20), and failure indication (20). Once the data words are checked, contact Cisco TAC to resolve the failure indicated. Refer to the “Obtaining Documentation and Submitting a Service Request”...

  • Page 180: Interactive Voice Response Real Time Transport Protocol Session Fail—Call Processing (40)

    To correct the primary cause of the event, verify whether the given DN has been provisioned correctly in the reporting BTS 10200. If there is an error in the LNP database (SCP) or other switch, then notify the appropriate administrators. Note that porting of the subscriber and DN from the donor switch to the recipient switch, and associated updates of the Location Routing Number (LRN) in all the SCP databases, may not all occur at exactly the same time.

  • Page 181: Call Processing No Session Initiation Protocol Trigger Context Found—Call Processing (44)

    Context in call from Application Server not Found—Call Processing (45) The Context in call from Application Server not Found event serves as a warning that an BTS 10200 has received an INVITE from an application server which contains a context ID in the route header which is invalid.

  • Page 182: Troubleshooting Call Processing Alarms

    CALLP(12) Feature Server Both Links Down—Call Processing (12) CRITICAL CALLP(38) Release Cause 25 Exchange Routing Error Received—Call Processing (38) MINOR CALLP(41) INVITE Message From Unauthorized Call Agent—Call Processing (41) MINOR Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 4-32 OL-8723-19...

  • Page 183: Feature Server One Link Down—Call Processing (11)

    Check for any errors pertaining to the interface in /var/adm/messages* file. Step 5 Check operational status of ethernet interface(s) on switch side as follows: Step 6 admin up / line protocol up Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 4-33 OL-8723-19...
  • Page 184 (CRC), frame errors. For a description of the output of “show interface fast ethernet”, refer to: http://www.cisco.com/en/US/customer/docs/ios/12_2/interface/command/reference/irfshoin.html Paste the output of “show interfaces” to the Cisco output interpreter for further analysis of the interfaces. Step 9 https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl Check the physical cable, the cable connectors, and the cable connections.

  • Page 185: Feature Server Both Links Down—Call Processing (12)

    Check for any errors pertaining to the interface in /var/adm/messages* file. Step 5 Check operational status of ethernet interface(s) on switch side as follows: Step 6 admin up / line protocol up Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 4-35 OL-8723-19...

  • Page 186: Release Cause 25 Exchange Routing Error Received—Call Processing (38)

    Step 8 frame errors. For a description of the output of “show interface fast ethernet”, refer to: http://www.cisco.com/en/US/customer/docs/ios/12_2/interface/command/reference/irfshoin.html Paste the output of “show interfaces” to the Cisco output interpreter for further analysis of the interfaces. Step 9 https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl Check the physical cable, the cable connectors, and the cable connections.

  • Page 187: Introduction

    • correct the configuration alarms. Configuration Events and Alarms This section provides a brief overview of the configuration events and alarms for the Cisco BTS 10200 Softswitch in numerical order. Table 5-1 lists all of the configuration events and alarms by severity.

  • Page 188: C H A P T E R 5 Configuration Troubleshooting

    At least half of the local machine address does not match the Media Gateway Control Protocol (MGCP) CAUSE domain name. SECONDARY Check the DNS server for the domain name to ensure that the Internet Protocol (IP) address is correct. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...

  • Page 189: Config (3)

    5-8. DESCRIPTION Configuration Error SEVERITY CRITICAL THRESHOLD THROTTLE DATAWORDS Reason–STRING [80] PRIMARY The wrong configuration is in the platform.cfg file. CAUSE PRIMARY Correct the appropriate parameters in the platform.cfg file. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...

  • Page 190: Config (5)

    THRESHOLD THROTTLE PRIMARY The BTS 10200 software is released with a file named FIMXMLRules.xml. This file is only read CAUSE during system initialization. It defines how to handle certain features provided on an external application server. The file may be missing.

  • Page 191: Config (7)

    THRESHOLD THROTTLE PRIMARY The BTS 10200 call agent is provisioned to send a trigger to the feature server for the offhook delay CAUSE trigger (OHD) feature or the terminating attempt trigger (TAT) feature. The subscriber is not provisioned to define the sip-trigger-profile ID.

  • Page 192: Monitoring Configuration Events

    CONFIG(7) Application Server Provisioning Error—Configuration (7) WARNING CONFIG(8) BTS 10200 Provisioning for External Applications is not Complete—Configuration WARNING Test Report—Configuration (1) The Test Report event is used for testing the configuration event category. The event is informational and no further action is required.

  • Page 193: Configuration Error—Configuration (4)

    The BTS 10200 Provisioning for External Applications is not Complete event serves as warning that the BTS 10200 call agent is provisioned to send a trigger to the Feature Server for OHD or TAT feature. The subscriber is not provisioned to define the sip-trigger-profile ID. To correct the cause of the BTS 10200 Provisioning for External Applications is not Complete event, provision the sip-trigger-profile ID for each subscriber which has OHD or TAT provisioned.

  • Page 194: Troubleshooting Configuration Alarms

    DB and host command line mismatch configuration error has occurred. The primary cause of the alarm is that the Feature–Server Table is mis-configured. To correct the primary cause of the alarm, reconfigure the Feature–Server table configuration to match command line –host and –port. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...

  • Page 195: Introduction

    Alarms—Provides a brief overview of each database event and alarm. • Monitoring Database Events—Provides the information needed to monitor and correct the database • events. Troubleshooting Database Alarms—Provides the information needed to troubleshoot and correct the • database alarms. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...

  • Page 196: Database Events And Alarms

    Database Troubleshooting Database Events and Alarms Database Events and Alarms This section provides a brief overview of the database events and alarms for the Cisco BTS 10200 Softswitch in numerical order. Table 6-1 lists all of the database events and alarms by severity.

  • Page 197: C H A P T E R 6 Database Troubleshooting

    Perform an audit of the database in question to correct the data stored in shared memory. ACTION SECONDARY Use command line interface (CLI) to show and delete the transaction queue, and to audit and manage ACTION the queue. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...

  • Page 198: Database (3)

    PRIMARY Replication data conflicts have occurred. CAUSE PRIMARY The replication data conflicts may require a manual update on the database tables. Call Cisco Support. ACTION (Contact Cisco Technical Assistance Center (TAC).) SECONDARY An update or delete attempt on non-existing data has occurred.

  • Page 199: Database (4)

    CAUSE SECONDARY Restart the remote listener process. ACTION TERNARY The remote Oracle listener process has died. CAUSE TERNARY Correct the network connection problem. ACTION SUBSEQUENT The network connection is broken. CAUSE Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...

  • Page 200: Database (5)

    ACTION SECONDARY The remote database is not accessible. CAUSE SECONDARY Make sure that the DBHeartBeat process is up. ACTION TERNARY The database is overloaded. CAUSE TERNARY Troubleshoot the database performance. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...

  • Page 201: Database (7)

    There are too many errors in the DefError queue. CAUSE SECONDARY Correct the replication errors. ACTION TERNARY The replication PURGE job is broken or overloaded. CAUSE TERNARY Enable the replication PURGE job. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...

  • Page 202: Database (8)

    Free Space–TWO_BYTES Time Stamp–STRING [20] PRIMARY The transaction volume has increased. CAUSE PRIMARY Backup and cleanup the archive log files. ACTION SECONDARY Add more space to the archive log directory. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...

  • Page 203: Database (10)

    THRESHOLD THROTTLE DATAWORDS Host Name–STRING [30] Database Name–STRING [10] Message 1–STRING [200] Message 2–STRING [200] Time Stamp–STRING [20] PRIMARY The system or hardware are unstable. CAUSE PRIMARY Re-start backup process. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...

  • Page 204: Database (11)

    The corrective action is documented in the $ORACLE_HOME/rdbms/mesg/oraus.msg file. Login to ACTION EMS system as oracle user (or su–oracle) to view this file. If more information is needed, contact Cisco TAC for database support, or query Oracle Metalink library at http://metalink.oracle.com. The alert.log file is the global message file for errors issued by all Oracle background processes.

  • Page 205: Database (12)

    Contact Cisco Support. (Contact Cisco TAC.) ACTION Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 6-11 OL-8723-19...

  • Page 206: Database (13)

    Perform a database performance tuning. ACTION Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 6-12 OL-8723-19...

  • Page 207: Database (14)

    The pre-provisioned size for the stated table is nearing the licensed limit on the number of entries it CAUSE can hold. PRIMARY Contact Cisco to purchase additional entry space for this particular table. (Contact Cisco TAC.) ACTION Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request.

  • Page 208: Database (16)

    Data Replication Failed SEVERITY MAJOR THRESHOLD THROTTLE DATAWORDS Replication-Stage–STRING [40] Table Name–STRING [40] Index–FOUR_BYTES Table ID–TWO_BYTES PRIMARY The index size is out of range. CAUSE SECONDARY Record the index size mismatch. CAUSE Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 6-14 OL-8723-19...

  • Page 209: Database (18)

    ACTION Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request. DATABASE (19) For additional information, refer to the “Daily Database Backup Completed Successfully—Database (19)”...

  • Page 210: Database (20)

    The correction action varies and is determined by the type of exception. For more information about ACTION the ORA-xxxxx errors, execute the oerr ora xxxxx command as an Oracle user. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 6-16 OL-8723-19...

  • Page 211: Database (22)

    The corrective action is documented in the $ORACLE_HOME/rdbms/mesg/oraus.msg file. To view ACTION the file, login to EMS system as root, then su–oracle. If more information is needed, contact Cisco TAC for database support, or query Oracle Metalink library at http://metalink.oracle.com. Many ORA- errors may need administrator to investigate and resolve the problem.

  • Page 212: Database (24)

    The corrective action is documented in the $ORACLE_HOME/rdbms/mesg/oraus.msg file. To view ACTION the file, login to EMS system as root, then su–oracle. If more information is needed, contact Cisco TAC for database support, or query Oracle Metalink library at http://metalink.oracle.com. Many ORA- errors may need administrator to investigate and resolve the problem.

  • Page 213: Database (25)

    Call Cisco TAC technical support. (Contact Cisco TAC.) ACTION Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 6-19 OL-8723-19...

  • Page 214: Database (27)

    Reason - STRING [200] PRIMARY A corruption of the IDX framework for the table has occurred. CAUSE PRIMARY Running the tiat command will verify if there is corruption. Fix the corruption ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 6-20 OL-8723-19...

  • Page 215: Monitoring Database Events

    Element Management System Oracle Database–Major Error—Database (24) MAJOR DATABASE(25) Secure File Transfer Protocol Transfer Failed—Database (25) MAJOR DATABASE(26) File Write Error—Database (26) MAJOR DATABASE(27) Failure Setting the Index Table Soft Limit—Database (27) MAJOR Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 6-21 OL-8723-19...

  • Page 216: Test Report—Database (1)

    EMS database heartbeat process has died. To troubleshoot and correct the cause of the Element Management System Database HeartBeat Process Died alarm, refer to the “Element Management System Database HeartBeat Process Died—Database (5)” section on page 6-29. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 6-22 OL-8723-19...

  • Page 217: Element Management System Database Deftran Queue Is Overloaded—Database (7)

    To troubleshoot and correct the cause of the Element Management System Database: Backup Fails alarm, refer to the “Element Management System Database: Backup Fails—Database (10)” section on page 6-31. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 6-23 OL-8723-19...

  • Page 218: Element Management System Database Alert.log Alerts—Database (11)

    To troubleshoot and correct the cause of the Table Size Exceeds Critical Threshold Limit alarm, refer to the “Table Size Exceeds Critical Threshold Limit—Database (16)” section on page 6-33. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 6-24 OL-8723-19...

  • Page 219: Data Replication Failed—Database (17)

    “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request. Daily Database Backup Completed Successfully—Database (19) The Daily Database Backup Completed Successfully event functions as an informational alert that the daily database backup has completed successfully.

  • Page 220: Element Management System Oracle Database–Minor Error—Database (23)

    To troubleshoot and correct the cause of the Failure Setting the Index Table Soft Limit alarm, refer to the “Failure Setting the Index Table Soft Limit—Database (27)” section on page 6-37. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 6-26 OL-8723-19...

  • Page 221: Troubleshooting Database Alarms

    Element Management System Oracle Database–Major Error—Database (24) MAJOR DATABASE(25) Secure File Transfer Protocol Transfer Failed—Database (25) MAJOR DATABASE(26) File Write Error—Database (26) MAJOR DATABASE(27) Failure Setting the Index Table Soft Limit—Database (27) MAJOR Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 6-27 OL-8723-19...

  • Page 222: Administrator—Database (3)

    Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request. Prior to contacting Cisco TAC, collect the following information: On one EMS server: su - oracle...

  • Page 223: Element Management System Database Heartbeat Process Died—Database (5)

    -C rep On both EMS servers: nodestat dbadm -r get_deferror dbadm -r get_deferr dbadm -r get_deftrandest dbadm -r get_defcall_order Do not perform an EM01 switchover until the deferrors are removed. Note Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 6-29 OL-8723-19...

  • Page 224: Element Management System Database Deftran Queue Is Overloaded—Database (7)

    -C rep On both EMS servers: nodestat dbadm -r get_deferror dbadm -r get_deferr dbadm -r get_deftrandest dbadm -r get_defcall_order Do not perform an EM01 switchover until the deferrors are removed. Note Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 6-30 OL-8723-19...

  • Page 225: Element Management System Database Tablespace Is Out Of Free Space—Database (8)

    The primary cause of the alarm is that the system or hardware is unstable. To correct the primary cause of the alarm, re-start the backup process. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 6-31 OL-8723-19...

  • Page 226: Element Management System Database Alert.log Alerts—Database (11)

    $ORACLE_HOME/rdbms/mesg/oraus.msg file. Login to EMS system as oracle user (or su - oracle) to view this file. If more information is needed, contact Cisco TAC for database support, or query Oracle metalink library at http://metalink.oracle.com. The corrective action is documented in the $ORACLE_HOME/rdbms/mesg/oraus.msg file.

  • Page 227: Table Size Exceeds Minor Threshold Limit—Database (14)

    The primary cause of the alarm is that the pre-provisioned size for the stated table is nearing the licensed limit on the number of entries it can hold. To correct the primary cause of the alarm, contact Cisco TAC to purchase additional entry space for this particular table. Refer to the “Obtaining Documentation and Submitting a Service Request”...

  • Page 228: Database Statistics Collection Exception—Database (21)

    “Exception” dataword field. The correction action varies and is determined by the type of exception. For more information about the ORA-xxxxx errors, execute an oerr ora xxxxx command as an Oracle user. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 6-34 OL-8723-19...

  • Page 229: Unprovisioned Language—Database (22)

    ID=1 ANNC_ID=18 btsadmin>show announcement ANNOUNCEMENT_FILE=ann_id_18.au ROUTE_GUIDE_ID=10013 Ensure the IVR script points to the correct MS and that the MLS has an FNAME: btsadmin>show ivr_script_profile FNAME=MLS IVR_ACCESS_MODE=IVR IVR_ROUTE_GUIDE_ID=10013 IVR_SCRIPT_PKG_TYPE=BAU Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 6-35 OL-8723-19...

  • Page 230: Element Management System Oracle Database–Minor Error—Database (23)

    $ORACLE_HOME/rdbms/mesg/oraus.msg file. Login to EMS system as oracle user (or su - oracle) to view this file. If more information is needed, contact Cisco TAC for database support, or query Oracle metalink library at http://metalink.oracle.com. The corrective action is documented in the $ORACLE_HOME/rdbms/mesg/oraus.msg file.

  • Page 231: Element Management System Oracle Database–Major Error—Database (24)

    $ORACLE_HOME/rdbms/mesg/oraus.msg file. Login to EMS system as oracle user (or su - oracle) to view this file. If more information is needed, contact Cisco TAC for database support, or query Oracle metalink library at http://metalink.oracle.com. The corrective action is documented in the $ORACLE_HOME/rdbms/mesg/oraus.msg file.
  • Page 232 Chapter 6 Database Troubleshooting Troubleshooting Database Alarms Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 6-38 OL-8723-19...

  • Page 233: Introduction

    Alarms—Provides a brief overview of each maintenance event and alarm. • Monitoring Maintenance Events—Provides the information needed to monitor and correct the • maintenance events. Troubleshooting Maintenance Alarms—Provides the information needed to troubleshoot and • correct the maintenance alarms. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...

  • Page 234: C H A P T E R 7 Maintenance Troubleshooting

    Maintenance Troubleshooting Maintenance Events and Alarms Maintenance Events and Alarms This section provides a brief overview of the maintenance events and alarms for the Cisco BTS 10200 Softswitch in numerical order. Table 7-1 lists all of the maintenance events and alarms by severity.

  • Page 235: Maintenance (1)

    No action is required since this is an information report. The root cause event report and the threshold ACTION setting should be investigated to determine if there is a service affecting situation. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...

  • Page 236: Maintenance (3)

    Reboot the host machine, reinstall all applications and restart all applications. If the fault state is a ACTION commonly occurring problem, then the operating system (OS) or a hardware failure may be the problem. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...

  • Page 237: Maintenance (4)

    If software restart does not resolve the problem or if the platform goes immediately to faulty again, or ACTION does not start, contact Cisco Technical Assistance Center (TAC). It may be necessary to reinstall software. If problem is commonly occurring, then the OS or a hardware failure may the problem.

  • Page 238: Maintenance (5)

    If faulty state is a commonly occurring event, then the OS or a hardware failure may be the problem. Contact Cisco TAC for assistance. It may also be helpful to gather information event/alarm reports that were issued before and after this alarm report.

  • Page 239: Maintenance (6)

    If faulty state is a commonly occurring event, then the operating system (OS) or a hardware failure may be the problem. Contact Cisco TAC for assistance. It may also be helpful to gather information event/alarm reports that were issued before and after this alarm report.

  • Page 240: Maintenance (7)

    If software restart does not resolve the problem, or if the problem is commonly occurring, contact Cisco TAC. It may be necessary to reinstall software. Additional OS or hardware problems may also need to be resolved.

  • Page 241: Maintenance (8)

    Check that the binary files are present for the unit (Call Agent, Feature Server, Element Manager). ACTION TERNARY If the files are not present, then re-install the files from the initial or backup media. Then restart the ACTION failed device. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...

  • Page 242: Maintenance (10)

    DATAWORDS Local State–STRING [30] Mate State–STRING [30] PRIMARY Acknowledges that the changeover has successfully completed. CAUSE PRIMARY This is an informational event report and no further action is required. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-10 OL-8723-19...

  • Page 243: Maintenance (12)

    The administrative state of a managed resource has changed. CAUSE PRIMARY No action is required, since this informational event report is given after a user has manually changed ACTION the administrative state of a managed resource. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-11 OL-8723-19...

  • Page 244: Maintenance (14)

    Current Mate State–STRING [20] PRIMARY Indicates that the call agent has changed operational state as a result of a manual switchover (control CAUSE command in CLI). PRIMARY No action is required. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-12 OL-8723-19...

  • Page 245: Maintenance (16)

    If during system initialization a short burst of these event reports are issued prior to the database ACTION initialization, then these event reports are informational and can be ignored. SECONDARY Otherwise, contact Cisco TAC technical support for more information. (Contact Cisco TAC.) ACTION Note Refer to the “Obtaining Documentation and Submitting a Service Request”...

  • Page 246: Maintenance (18)

    Process Group–FOUR_BYTES PRIMARY This alarm is caused by a software problem. CAUSE PRIMARY If problem persists, contact Cisco TAC technical support. (Contact Cisco TAC.) ACTION Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request.

  • Page 247: Maintenance (20)

    Soon after this event is issued, one platform may go to the faulty state. CAUSE SECONDARY Check whether or not the network interface is down. If the interface is down, restore network interface ACTION and restart the software. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-15 OL-8723-19...

  • Page 248: Maintenance (22)

    The specified process failed to complete the initialization during the restoral process. CAUSE PRIMARY Verify that the specified process’s binary image is installed. If not, install it and restart the platform. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-16 OL-8723-19...

  • Page 249: Maintenance (24)

    Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request. MAINTENANCE (25) For additional information, refer to the “Process Manager: Changing State—Maintenance (25)” section on page 7-73.

  • Page 250: Maintenance (26)

    For additional information, refer to the “Process Manager: Changing Over to Standby—Maintenance (28)” section on page 7-74. DESCRIPTION Process Manager: Changing Over to Standby (PMG: Changing Over to Standby) SEVERITY INFO THRESHOLD THROTTLE Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-18 OL-8723-19...

  • Page 251: Maintenance (29)

    No action is necessary. This is part of the normal state transitioning process for the EMS. ACTION SECONDARY Monitor the system for related event reports if the transition was to a faulty or out of service state. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-19 OL-8723-19...

  • Page 252: Maintenance (31)

    The switchover or shutdown could be due to either of the following: (1) The operator is taking the action to switch or shut down the system. (2) The system has detected a fault. PRIMARY No action is necessary. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-20 OL-8723-19...

  • Page 253: Maintenance (34)

    Process Manager: All Processes Completed Initialization (PMG: All Processes Completed Initialization) SEVERITY INFO THRESHOLD THROTTLE PRIMARY The system is being brought up, and all processes are ready to start executing. CAUSE PRIMARY No action is necessary. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-21 OL-8723-19...

  • Page 254: Maintenance (36)

    A process did not come up when the system was brought up and had to be killed in order to restart it. CAUSE TERNARY A process did not exit when asked to exit. CAUSE Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-22 OL-8723-19...

  • Page 255: Maintenance (38)

    Process Manager: Binary Does not Exist for Process (PMG: Binary Does not Exist for Process) SEVERITY CRITICAL THRESHOLD THROTTLE DATAWORDS Program Name–STRING [30] Executable Name–STRING [100] PRIMARY The platform is not installed correctly. CAUSE PRIMARY Reinstall the platform. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-23 OL-8723-19...

  • Page 256: Maintenance (41)

    THROTTLE DATAWORDS Interface Name–STRING [50] IP Address–STRING [50] Expected HB Messages–ONE_BYTE HB Messages Received–ONE_BYTE PRIMARY The alarm is caused by a network problem. CAUSE PRIMARY Fix the network problem. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-24 OL-8723-19...

  • Page 257: Maintenance (43)

    The alarm is caused by a software or a configuration problem. CAUSE PRIMARY Restart the platform. If problem persists call tech support. (Contact Cisco TAC.) ACTION Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request.

  • Page 258: Maintenance (45)

    The switchover of an application instance failed because of a platform fault. CAUSE PRIMARY Retry the switchover and if the condition continues call tech support. (Contact Cisco TAC.) ACTION Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request.

  • Page 259: Maintenance (47)

    Contact customer support. (Contact Cisco TAC.) ACTION Note Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi detailed instructions on contacting Cisco TAC and opening a service request. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-27 OL-8723-19...

  • Page 260: Maintenance (49)

    Contact customer support. (Contact Cisco TAC.) ACTION Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-28 OL-8723-19...

  • Page 261: Maintenance (50)

    Host Name–STRING [40] PID–STRING [40] Process Name–STRING [40] CPU Usage–STRING [40] PRIMARY A process has entered a state of erratic behavior. CAUSE PRIMARY Monitor the process and kill it if necessary. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-29 OL-8723-19...

  • Page 262: Maintenance (52)

    CPU Usage–STRING [40] PRIMARY To numerous to determine. CAUSE PRIMARY Try to isolate the problem. Call Cisco for assistance. (Contact Cisco TAC.) ACTION Note Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi detailed instructions on contacting Cisco TAC and opening a service request.

  • Page 263: Maintenance (54)

    Monitor the system to ensure that all subsystems are performing normally. If they are, only lightening ACTION the effective load on the system will clear the situation. If they are not, verify which process(es) are running at abnormally high rates and provide the information to Cisco TAC. (Contact Cisco TAC.) Note Refer to the “Obtaining Documentation and Submitting a Service Request”...

  • Page 264: Maintenance (56)

    Critical Levels—Maintenance (57)” section on page 7-102. Note Maintenance (57) is issued by the BTS 10200 system when memory consumption is greater than 95 percent (>95%) and swap space consumption is greater than 50 percent (>50%). DESCRIPTION Memory and Swap are Consumed at Critical Levels...

  • Page 265: Maintenance (58)

    Levels—Maintenance (58)” section on page 7-79. Note Maintenance (58) is issued by the BTS 10200 system when memory consumption is greater than 80 percent (>80%) and swap space consumption is greater than 30 percent (>30%). DESCRIPTION Memory and Swap are Consumed at Abnormal Levels...

  • Page 266: Maintenance (61)

    The interface cable is pulled out or the interface is set down using ifconfig down command. CAUSE PRIMARY Restore the network interface. ACTION SECONDARY The interface has no connectivity to any of the machines or routers. CAUSE Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-34 OL-8723-19...

  • Page 267: Maintenance (63)

    Identify the applications which are causing the system degradation by using the HMN CLI commands. ACTION Verify if this is a persistent or on-going situation. Contact Cisco TAC with the gathered information. Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request.

  • Page 268: Maintenance (65)

    Device–STRING [32] Percentage Used–STRING [8] PRIMARY A process or processes is/are writing extraneous data to the named partition. CAUSE PRIMARY Perform a disk clean-up and maintenance on the offending system. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-36 OL-8723-19...

  • Page 269: Maintenance (67)

    Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request. MAINTENANCE (68) To troubleshoot and correct the cause of the alarm, refer to the “The Free Inter-Process Communication...

  • Page 270: Maintenance (69)

    Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request. MAINTENANCE (70) To troubleshoot and correct the cause of the alarm, refer to the “The Free Inter-Process Communication...

  • Page 271: Maintenance (71)

    There is an daemon called monitorDNS.sh checking the DNS server every minute or so. It will issue CAUSE an alarm if it cannot contact the DNS server or the response is slow. But it will clear the alarm if it can contact the DNS server later. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-39 OL-8723-19...

  • Page 272: Maintenance (73)

    Local Domain Name System Service not Responsive (Local DNS Service not Responsive) SEVERITY CRITICAL THRESHOLD THROTTLE DATAWORDS DNS Server IP–STRING [64] Reason–STRING [64] PRIMARY The local DNS service may be down. CAUSE PRIMARY Check the local DNS server. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-40 OL-8723-19...

  • Page 273: Maintenance (75)

    IP Addr Local Server–STRING [64] IP Addr DNS Server–STRING [64] PRIMARY The DNS updates are not getting to the BTS 10200 from the external server or the discrepancy was CAUSE detected before the local DNS lookup table was updated. PRIMARY Ensure that the external DNS server is operational and is sending updates to the BTS 10200.

  • Page 274: Maintenance (78)

    “Resource Reset—Maintenance (79)” section on page 7-82. DESCRIPTION Resource Reset SEVERITY INFO THRESHOLD THROTTLE DATAWORDS Resource Type–STRING [40] Resource Instance–STRING [40] PRIMARY Trunk-Termination CAUSE Subscriber-Termination Media Gateways PRIMARY None ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-42 OL-8723-19...

  • Page 275: Maintenance (80)

    Check Dataword 3 (Failure Reason) to determine if the event was caused by invalid user input, ACTION inconsistent provisioning of the device, or if the system is busy and a timeout occurred. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-43 OL-8723-19...

  • Page 276: Maintenance (82)

    PRIMARY Too many processes are running. CAUSE PRIMARY Stop the proliferation of executables (processes-scripts). ACTION SECONDARY File spaces /tmp or /var/run are over-used. CAUSE SECONDARY Cleanup the file systems. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-44 OL-8723-19...

  • Page 277: Maintenance (84)

    DATAWORDS Critical Threshold (M–FOUR_BYTES Current Value (MB)–FOUR_BYTES PRIMARY Too many processes are running. CAUSE PRIMARY Restart the BTS 10200 software or reboot the system. ACTION SECONDARY File spaces /tmp or /var/run are over-used. CAUSE SECONDARY Cleanup the file systems. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x...

  • Page 278: Maintenance (86)

    Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request. MAINTENANCE (87) To troubleshoot and correct the cause of the alarm, refer to the “Status Update Process Request...

  • Page 279: Maintenance (88)

    Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request. MAINTENANCE (89) To troubleshoot and correct the cause of the alarm, refer to the “Status Update Process Database Update...

  • Page 280: Maintenance (90)

    SEVERITY CRITICAL THRESHOLD THROTTLE DATAWORDS Reason–STRING [128] PRIMARY The Internet Protocol Manager (IPM) has a configuration file error. CAUSE PRIMARY Check the IPM configuration file (ipm.cfg) for incorrect syntax. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-48 OL-8723-19...

  • Page 281: Maintenance (92)

    THRESHOLD THROTTLE DATAWORDS Interface Name–STRING [32] Reason–STRING [128] PRIMARY The IPM failed to create logical interface. CAUSE PRIMARY Check the Reason dataword as to the cause of the error. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-49 OL-8723-19...

  • Page 282: Maintenance (94)

    Hostname–STRING [128] Physical IF Name–STRING [32] Logical IF Name–STRING [32] IP Addr–STRING [32] Netmask–STRING [32] Broadcast Addr–STRING [32] PRIMARY The IPM created a new logical interface. CAUSE PRIMARY None ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-50 OL-8723-19...

  • Page 283: Maintenance (96)

    Contact Cisco TAC. ACTION Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-51 OL-8723-19...

  • Page 284: Maintenance (98)

    Contact Cisco TAC. ACTION Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-52 OL-8723-19...

  • Page 285: Maintenance (99)

    Contact Cisco TAC. ACTION Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-53 OL-8723-19...

  • Page 286: Maintenance (100)

    Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request. MAINTENANCE (101) To troubleshoot and correct the cause of the alarm, refer to the “Switchover in Progress—Maintenance...

  • Page 287: Maintenance (102)

    Restore the CPU or contact Cisco TAC. ACTION Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-55 OL-8723-19...

  • Page 288: Maintenance (104)

    PRIMARY The aggregation (AGGR) Internet Protocol (IP) address is not provisioned in the aggregation table. CAUSE PRIMARY Provision the AGGR with the AGGR IP address in the AGGR table. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-56 OL-8723-19...

  • Page 289: Maintenance (106)

    Router IP Address–STRING [50] PRIMARY The router is down. CAUSE PRIMARY Restore the router functionality. ACTION SECONDARY Connection to the router is down. CAUSE SECONDARY Restore the connection. ACTION TERNARY Network congestion. CAUSE Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-57 OL-8723-19...

  • Page 290: Maintenance (108)

    A problem in access to external archive system has occurred. CAUSE PRIMARY Check the external archive system. ACTION SECONDARY Network to the external archive system is down. CAUSE SECONDARY Check the network. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-58 OL-8723-19...

  • Page 291: Maintenance (110)

    THRESHOLD THROTTLE DATAWORDS External Archive Server–STRING [50] Username–STRING [50] PRIMARY No authorization access is set up in the external archive server for the user from the BTS 10200. CAUSE PRIMARY Set up the authorization. ACTION SECONDARY The external archive server is down.

  • Page 292: Maintenance (112)

    Factor MCL–ONE_BYTE PRIMARY A change (increase/decrease) has occurred in the call processing load. CAUSE PRIMARY If the level remains continuously high, change the configuration or redistribute the call load. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-60 OL-8723-19...

  • Page 293: Maintenance (114)

    Factor Level–ONE_BYTE Factor MCL–ONE_BYTE PRIMARY A change has occurred in the IPC buffer usage. CAUSE PRIMARY If the reported level remains continuously high, adjust the system load or configuration. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-61 OL-8723-19...

  • Page 294: Maintenance (116)

    PRIMARY Capture the debugging information, especially from the saved.debug directory. This alarm indicates ACTION that an automatic restart is pending and at what time it will be attempted. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-62 OL-8723-19...

  • Page 295: Maintenance (118)

    Periodic Shared Memory Database Backup Failure SEVERITY CRITICAL THRESHOLD THROTTLE DATAWORDS Reason–STRING [300] Available Disk Space (MB)–FOUR_BYTES Required Disk Space (MB)–FOUR_BYTES PRIMARY High disk usage. CAUSE PRIMARY Check disk usage. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-63 OL-8723-19...

  • Page 296: Maintenance (120)

    THRESHOLD THROTTLE DATAWORDS Request–STRING [256] Session ID–STRING [20] PRIMARY The provisioning client sent an invalid xml request to the soap provisioning adapter. CAUSE PRIMARY Re-send a valid xml request. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-64 OL-8723-19...

  • Page 297: Maintenance (122)

    Table Name–STRING [40] Update String–STRING [256] PRIMARY The EMS hub is not responding. CAUSE PRIMARY Verify if there are any alarms originating from the hub and take the appropriate action. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-65 OL-8723-19...

  • Page 298: Monitoring Maintenance Events

    Process Manager: Changing Over to Standby—Maintenance (28) INFO MAINTENANCE(29) Administrative State Change Failure—Maintenance (29) WARNING MAINTENANCE(30) Element Manager State Change—Maintenance (30) INFO MAINTENANCE(32) Process Manager: Sending Go Active to Process—Maintenance (32) INFO Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-66 OL-8723-19...
  • Page 299 Outgoing Heartbeat Period Exceeded Limit—Maintenance (63) MAJOR MAINTENANCE(64) Average Outgoing Heartbeat Period Exceeds Major Alarm Limit—Maintenance MAJOR (64) MAINTENANCE(65) Disk Partition Critically Consumed—Maintenance (65) CRITICAL MAINTENANCE(66) Disk Partition Significantly Consumed—Maintenance (66) MAJOR Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-67 OL-8723-19...
  • Page 300 Internet Protocol Manager Interface Removed—Maintenance (96) INFO MAINTENANCE(97) Inter-Process Communication Input Queue Entered Throttle State—Maintenance CRITICAL (97) MAINTENANCE(98) Inter-Process Communication Input Queue Depth at 25% of its MINOR Hi-Watermark—Maintenance (98) Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-68 OL-8723-19...

  • Page 301: Test Report—Maintenance (1)

    Northbound Provisioning Message Dropped Due To Full Index WARNING Table—Maintenance (123) Test Report—Maintenance (1) The Test Report is for testing the maintenance event category. The event is informational and no further action is required. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-69 OL-8723-19...

  • Page 302: Report Threshold Exceeded—Maintenance (2)

    The Mate Changeover Timeout alarm (major) indicates that the mate changeover timed out. To troubleshoot and correct the cause of the Mate Changeover Timeout alarm, refer to the “Mate Changeover Timeout—Maintenance (8)” section on page 7-97. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-70 OL-8723-19...

  • Page 303: Local Initialization Failure—Maintenance (9)

    The Feature Server Administrative State Change event functions as an informational alert that indicates that the feature server has changed operational state as a result of a manual switchover. The event is informational and no further action is required. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-71 OL-8723-19...

  • Page 304: Process Manager: Starting Process—Maintenance (16)

    “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request. Process Manager: Process has Died—Maintenance (18) The Process Manager: Process has Died alarm (minor) indicates that a process has died. To troubleshoot and correct the cause of the Process Manager: Process has Died alarm, refer to the “Process Manager:...

  • Page 305: Mate Is Alive—Maintenance (22)

    No action is necessary. This is part of the normal process of activating the platform. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-73...

  • Page 306: Process Manager: Changing Over To Standby—Maintenance (28)

    The switchover or shutdown could be due to the operator taking the action to switch or shut down the system or due to the system has detected a fault. The event is informational and no further action is required. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-74 OL-8723-19...

  • Page 307: Process Manager: All Processes Completed Initialization—Maintenance (35)

    To troubleshoot and correct the cause of the Process Manager: Binary Does not Exist for Process alarm, refer to the “Process Manager: Binary Does not Exist for Process—Maintenance (40)” section on page 7-99. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-75 OL-8723-19...

  • Page 308: Administrative State Change Successful With Warning—Maintenance (41)

    The primary cause of the event is that the interface cable is reconnected and the interface is put ‘up’ using ifconfig command. The event is informational and no further action is required. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-76...

  • Page 309: Thread Watchdog Counter Expired For A Thread—Maintenance (47)

    The Central Processing Unit Usage is Now Below the 50% Level event functions as an informational alert that the CPU usage level has fallen below the threshold level of 50 percent. The event is informational and no further action is required. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-77 OL-8723-19...

  • Page 310: The Central Processing Unit Usage Is Over 90% Busy—Maintenance (53)

    Memory and Swap are Consumed at Critical Levels—Maintenance (57) Note Maintenance (57) is issued by the BTS 10200 system when memory consumption is greater than 95 percent (>95%) and swap space consumption is greater than 50 percent (>50%). The Memory and Swap are Consumed at Critical Levels alarm (critical) indicates that memory and swap file usage have reached critical levels.

  • Page 311: Memory And Swap Are Consumed At Abnormal Levels—Maintenance (58)

    Monitoring Maintenance Events Memory and Swap are Consumed at Abnormal Levels—Maintenance (58) Maintenance (58) is issued by the BTS 10200 system when memory consumption is greater than 80 Note percent (>80%) and swap space consumption is greater than 30 percent (>30%).

  • Page 312: Average Outgoing Heartbeat Period Exceeds Major Alarm Limit—Maintenance (64)

    The Free Inter-Process Communication Pool Buffers Below Major Threshold alarm, refer to the “The Free Inter-Process Communication Pool Buffers Below Major Threshold—Maintenance (68)” section on page 7-104. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-80 OL-8723-19...

  • Page 313: Local Domain Name System Server Response Too Slow—Maintenance (71)

    DNS server is not responding to network queries. To troubleshoot and correct the cause of the External Domain Name System Server not Responsive alarm, refer to the “External Domain Name System Server not Responsive—Maintenance (73)” section on page 7-105. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-81 OL-8723-19...

  • Page 314: Local Domain Name System Service Not Responsive—Maintenance (74)

    IP address and the DNS server address has occurred. The primary cause of the event is that the DNS server updates are not getting to the BTS 10200 from the external server, or the discrepancy was detected before the local DNS lookup table was updated. Ensure the external DNS server is operational and sending updates to the BTS 10200.

  • Page 315: Resource Reset Failure—Maintenance (81)

    System Health Report. To troubleshoot and correct the cause of the System Health Report Collection Error alarm, refer to the “System Health Report Collection Error—Maintenance (86)” section on page 7-106. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-83 OL-8723-19...

  • Page 316: Status Update Process Request Failed—Maintenance (87)

    The Internet Protocol Manager Interface Failure alarm (major) indicates that an IPM interface has failed. To troubleshoot and correct the cause of the Internet Protocol Manager Interface Failure alarm, refer to “Internet Protocol Manager Interface Failure—Maintenance (93)” section on page 7-108. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-84 OL-8723-19...

  • Page 317: Internet Protocol Manager Interface State Change—Maintenance (94)

    Inter-Process Communication Input Queue Depth at 50% of its Hi-Watermark alarm, refer to the “Inter-Process Communication Input Queue Depth at 50% of Its Hi-Watermark—Maintenance (99)” section on page 7-108. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-85 OL-8723-19...

  • Page 318: Switchover In Progress—Maintenance (101)

    The Thread Watchdog Counter Close to Expiry for a Thread alarm (critical) indicates that the thread watchdog counter is close to expiry for a thread. The primary cause of the alarm is that a software error has occurred. No further action is required, the BTS 10200 system will automatically recover or shutdown.

  • Page 319: Aggregration Device Address Resolution Failure—Maintenance (106)

    Access to Log Archive Facility Configuration File Failed or File Corrupted alarm, refer to “Access to Log Archive Facility Configuration File Failed or File Corrupted—Maintenance (110)” section on page 7-110. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-87 OL-8723-19...

  • Page 320: Cannot Login To External Archive Server—Maintenance (111)

    OOS-FAULTY state, and is in the process of being automatically restarted. To troubleshoot and correct the cause of the Side Automatically Restarting Due to Fault alarm, refer to the “Side Automatically Restarting Due to Fault—Maintenance (117)” section on page 7-111. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-88 OL-8723-19...

  • Page 321: Domain Name Server Zone Database Does Not Match Between The Primary Domain Name Server And The Internal Secondary Authoritative Domain Name Server—Maintenance (118)

    EMS hub is not responding. To correct the primary cause of the event, verify if there are any alarms originating from the hub and take the appropriate action. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-89...

  • Page 322: Troubleshooting Maintenance Alarms

    MAJOR MAINTENANCE(57) Memory and Swap are Consumed at Critical Levels—Maintenance (57) CRITICAL MAINTENANCE(61) No Heartbeat Messages Received Through the Interface—Maintenance (61) CRITICAL MAINTENANCE(62) Link Monitor: Interface Lost Communication—Maintenance (62) MAJOR Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-90 OL-8723-19...
  • Page 323 Inter-Process Communication Input Queue Depth at 50% of Its MAJOR Hi-Watermark—Maintenance (99) MAINTENANCE(100) Inter-Process Communication Input Queue Depth at 75% of Its CRITICAL Hi-Watermark—Maintenance (100) MAINTENANCE(101) Switchover in Progress—Maintenance (101) CRITICAL Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-91 OL-8723-19...

  • Page 324: Local Side Has Become Faulty—Maintenance (3)

    If a software restart does not resolve the problem or if the platform goes immediately to faulty again, or does not start, contact Cisco TAC. It may be necessary to reinstall software. If the alarm is reoccurring, then the operating system or the hardware may have a problem.

  • Page 325: Changeover Failure—Maintenance (5)

    If faulty state is a reoccurring event, then operating system or the hardware may be defective. Contact Cisco TAC for assistance. It may also be helpful to gather information event/alarm reports that were issued before and after this alarm report.

  • Page 326: Mate Rejected Changeover—Maintenance (7)

    “platform stop” and “platform start” commands. If software restart does not resolve the problem, or if the problem is commonly occurring, contact Cisco TAC. It may be necessary to reinstall software. Additional operating system or hardware problems may also need to be resolved.
  • Page 327 Determine current status active_normal of applicable EMS/CA/FS. active_forced standby_forced If not successful, contact Is mate in Restart the instance that Cisco TAC for assistance. stable state? was just brought down. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-95 OL-8723-19...
  • Page 328 The attempted changeover could be caused by a forced (operator) switch, or it could be caused by Note secondary instance rejecting changeover as primary is being brought up. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-96 OL-8723-19...

  • Page 329: Mate Changeover Timeout—Maintenance (8)

    If problem persists or is reoccurring, contact Cisco TAC. Note Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi detailed instructions on contacting Cisco TAC and opening a service request. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-97 OL-8723-19...

  • Page 330: Process Manager: Process Exceeded Restart Rate—Maintenance (19)

    Then reinstall and restart all applications on this machine. If faulty state is a commonly occurring event, then OS or hardware may be a problem. Contact Cisco TAC for assistance. It may also be helpful to gather information event/alarm reports that were issued before and after this alarm report.

  • Page 331: Process Manager: Restarting Process—Maintenance (24)

    Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi detailed instructions on contacting Cisco TAC and opening a service request. Process Manager: Going Faulty—Maintenance (26) The Process Manager: Going Faulty alarm (major) indicates that a PMG process is going faulty. The primary cause of the alarm is that the system has been brought down or the system has detected a fault.

  • Page 332: Process Manager: Process Failed To Come Up In Standby Mode—Maintenance (44)

    To correct the primary cause of the alarm, verify that traffic is within the rated capacity. The secondary cause of the alarm is that a software problem requiring additional analysis has occurred. To correct the secondary cause of the alarm, contact Cisco TAC. Refer to the “Obtaining Documentation and Submitting a Service Request”...

  • Page 333: Index Table Usage Exceeded Major Usage Threshold Level—Maintenance (49)

    To correct the primary cause of the alarm, verify that traffic is within the rated capacity. The secondary cause of the alarm is that a software problem requiring additional analysis has occurred. To correct the secondary cause of the alarm, contact Cisco TAC. Refer to the “Obtaining Documentation and Submitting a Service Request”...

  • Page 334: The Five Minute Load Average Is Abnormally High—Maintenance (55)

    Cisco TAC and opening a service request. Memory and Swap are Consumed at Critical Levels—Maintenance (57) Maintenance (57) is issued by the BTS 10200 system when memory consumption is greater than 95 Note percent (>95%) and swap space consumption is greater than 50 percent (>50%).

  • Page 335: Link Monitor: Interface Lost Communication—Maintenance (62)

    CPU overload or excessive I/O operations. To correct the primary cause of the alarm, identify the applications which are causing the system degradation via the CLI commands to verify if this is a persistent or on-going situation. Contact Cisco TAC with the gathered information.

  • Page 336: Disk Partition Significantly Consumed—Maintenance (66)

    Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request. The Free Inter-Process Communication Pool Buffers Below Major Threshold—Maintenance (68) The Free Inter-Process Communication Pool Buffers Below Major Threshold alarm (major) indicates that the number of free IPC pool buffers has fallen below the major threshold crossing level.

  • Page 337: Local Domain Name System Server Response Too Slow—Maintenance (71)

    IPC messaging traffic. The primary cause of the alarm is that IPC pool buffers are not being freed properly by the application or the application is not able to keep up with the incoming IPC messaging traffic. To correct the primary cause of the alarm, contact Cisco TAC immediately.

  • Page 338: Mate Time Differs Beyond Tolerance—Maintenance (77)

    The primary cause of the alarm is that too many processes are running. To correct the primary cause of the alarm, restart the BTS 10200 software or reboot system The secondary cause of the alarm is that the /tmp or /var/run are being over-used. To correct the secondary cause of the alarm, cleanup the file systems.

  • Page 339: Status Update Process Request Failed—Maintenance (87)

    The Status Update Process Database Update Error alarm (major) indicates that the status update process DB had an update error. The primary cause of the alarm is that the MySQL DB on the EMS is not working properly. To correct the primary cause of the alarm, contact Cisco TAC. Refer to the “Obtaining Documentation and Submitting a Service Request”...

  • Page 340: Internet Protocol Manager Interface Failure—Maintenance (93)

    Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request. Inter-Process Communication Input Queue Depth at 25% of Its Hi-Watermark—Maintenance (98) The Inter-Process Communication Input Queue Depth at 25% of Its Hi-Watermark alarm (minor) indicates that the IPC input queue depth has reached 25 percent of its hi-watermark.

  • Page 341: Switchover In Progress—Maintenance (101)

    The Thread Watchdog Counter Close to Expiry for a Thread alarm (critical) indicates that the thread watchdog counter is close to expiry for a thread. The primary cause of the alarm is that a software error has occurred. No further action is required, the BTS 10200 system will automatically recover or shutdown.

  • Page 342: No Heartbeat Messages Received Through Interface From Router—Maintenance (107)

    The primary cause of the alarm is that no authorization access is set up in external archive server for that user from BTS 10200. To correct the primary cause of the alarm, set up the authorization. The secondary cause of the alarm is that the external archive server is down. To correct the secondary cause of the alarm, ping the external archive server, and try to bring it up.

  • Page 343: Side Automatically Restarting Due To Fault—Maintenance (117)

    The primary cause of the Periodic Shared Memory Database Backup Failure alarm is high disk usage. To correct the primary cause of the alarm, check disk usage. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-111...
  • Page 344 Chapter 7 Maintenance Troubleshooting Troubleshooting Maintenance Alarms Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 7-112 OL-8723-19...

  • Page 345: Introduction

    Alarms—Provides the information needed to troubleshoot and correct the operations support system alarms. Operations Support System Events and Alarms This section provides a brief overview of the operations support system events and alarms for the Cisco BTS 10200 Softswitch in numerical order. Table 8-1 lists all of the operations support system all of the events and alarms by severity.
  • Page 346 Contact Cisco Technical Assistance Center (TAC) for support. ACTION Note Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi detailed instructions on contacting Cisco TAC and opening a service request. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...

  • Page 347: C H A P T E R 8 Operations Support System Troubleshooting

    Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request. OSS (4) To troubleshoot and correct the cause of the alarm, refer to the “Request Handler Instantiation...
  • Page 348 Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request. OSS (6) To troubleshoot and correct the cause of the alarm, refer to the “Structured Query Language Connection...
  • Page 349 If this Event Report is issued while the system is stable (i.e. no device failures) and the traffic is at or ACTION below the engineered level, then Cisco TAC technical support should be contacted to investigate the cause. (Contact Cisco TAC.)

  • Page 350: Oss (10)

    Contact Cisco Support. (Contact Cisco TAC.) ACTION Note Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi detailed instructions on contacting Cisco TAC and opening a service request. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...

  • Page 351: Oss (11)

    PRIMARY Use report client_session command to view all login sessions. Use stop client_session to remove ACTION stale sessions. OSS (13) OSS (13) is not used. It is reserved for future use. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...

  • Page 352: Oss (14)

    User ID - STRING [16] Session Key - STRING [20] PRIMARY Session has been removed by the session control policy. CAUSE PRIMARY This is an informational alert and no corrective action is necessary. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...

  • Page 353: Monitoring Operations Support System Events

    To troubleshoot and correct the cause of the Undefined Variable in Known Set alarm, refer to the “Undefined Variable in Known Set—Operations Support System (2)” section on page 8-13. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...

  • Page 354: Undefined Data Column Identification—Operations Support System (3)

    Cisco TAC. Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 8-10 OL-8723-19...

  • Page 355: No Reply Received From Destination—Operations Support System (8)

    To correct the primary cause of the warning event, use the report client_session command to view all login sessions. Use the stop client_session command to remove stale sessions. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 8-11 OL-8723-19...

  • Page 356: User Session Count Exceeds Major Threshold Limit—Operation Support System (14)

    The Session Has Been Removed by Session Control Policy event serves as an information alert that the session has been removed by the session control policy. The event is informational and no further action is necessary. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 8-12 OL-8723-19...

  • Page 357: Troubleshooting Operations Support System Alarms

    SNMP interface. The primary cause of the alarm is that the database does not contain the required data column that was requested via the SNMP interface. To correct the primary cause of the alarm, contact Cisco TAC for support. Note Refer to the “Obtaining Documentation and Submitting a Service Request”...

  • Page 358: Request Handler Instantiation Error—Operations Support System (4)

    The primary cause of the alarm is that the connection to the database timed out or the database server is not running. The alarm is generated in the SNMP subsystem. To correct the primary cause of the alarm, contact Cisco TAC for support. Note Refer to the “Obtaining Documentation and Submitting a Service Request”...

  • Page 359: No Reply Received From Destination—Operations Support System (8)

    Audit on the failed table. The secondary cause of the alarm is that the DBM IDX is failing when attempting to perform a SQL command. To correct the secondary cause of the alarm, contact Cisco TAC. Refer to the “Obtaining Documentation and Submitting a Service Request”...
  • Page 360 Chapter 8 Operations Support System Troubleshooting Troubleshooting Operations Support System Alarms Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 8-16 OL-8723-19...

  • Page 361: Introduction

    • security alarms. Security Events and Alarms This section provides a brief overview of the security events and alarms for the Cisco BTS 10200 Softswitch in numerical order. Table 9-1 lists all of the security events and alarms by severity.

  • Page 362: C H A P T E R 9 Security Troubleshooting

    Sender IP–STRING [20] PRIMARY There are invalid credentials in Session Initiation Protocol (SIP) request. CAUSE PRIMARY Ensure that the password on the SIP phone matches the value provisioned in the BTS 10200. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...

  • Page 363: Security (3)

    1. Verify that the IPSEC is installed and running in the kernel. ACTION 2. Reboot. 3. If problem persists, call the Technical Assistance Center (TAC). (Contact Cisco TAC.) Note Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi detailed instructions on contacting Cisco TAC and opening a service request.

  • Page 364: Security (5)

    Violation Description–STRING [80] PRIMARY There is erroneous provisioning in the BTS 10200. CAUSE PRIMARY Check if correct value of Secure-FQDN is provisioned in the BTS 10200. ACTION SECONDARY There is erroneous provisioning in the domain name system (DNS). CAUSE SECONDARY Verify the resolution of the Secure-FQDN in the DNS.

  • Page 365: Monitoring Security Events

    The Invalid Credentials Presented by a Session Initiation Protocol Phone event serves as a warning that credentials in a SIP request are not valid. To correct the cause of the event, ensure that password provisioned on the SIP phone matches the value provisioned in the BTS 10200. Internet Protocol Security Connection Down—Security (3) The Internet Protocol Security Connection Down alarm (major) indicates that the IP security engine is not running.

  • Page 366: Internet Protocol Security Outgoing Security Association Not Found—Security (5)

    The Secure Session Initiation Protocol Endpoint Validation Failure event serves as a warning that a secure SIP endpoint validation failed. The primary cause of the event is that the BTS 10200 is incorrectly provisioned. To correct the primary cause of the event, check if correct value of secure-fqdn is provisioned in the BTS 10200 system.

  • Page 367: Troubleshooting Security Alarms

    IPSEC engine. The alarm implies that the IPSEC engine is not running and that it may not be installed. To primary cause of the alarm, verify that IPSEC is installed and running in the kernel and reboot the platform. If problem persists or is recurrent, contact Cisco TAC. Refer to the “Obtaining Documentation and Submitting a Service Request”...
  • Page 368 Chapter 9 Security Troubleshooting Troubleshooting Security Alarms Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...

  • Page 369: Introduction

    The use of the UNIX ifconfig down command on any signaling interface to test or troubleshoot network Caution or interface failures of the Cisco BTS 10200 Softswitch Signaling Interface may lead to undesirable consequences or conditions. The following billing records are created when a call is rejected due to overload conditions: Note •...

  • Page 370: C H A P T E R 10 Signaling Troubleshooting

    Signaling Troubleshooting Signaling Events and Alarms Signaling Events and Alarms This section provides a brief overview of the signaling events and alarms for the BTS 10200 in numerical order. Table 10-1 lists all of the signaling events and alarms by severity.

  • Page 371: Signaling (1)

    “Test Report—Signaling (1)” section on page 10-98. DESCRIPTION Test Report SEVERITY Information (INFO) THRESHOLD 10000 THROTTLE SIGNALING (2) SIGNALING (2) is not used. SIGNALING (3) SIGNALING (3) is not used. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-3 OL-8723-19...

  • Page 372: Signaling (4)

    ACTION expected by the call agent. SUBSEQUENT If there is a mismatch, then either the endpoint or call agent must be reprovisioned. ACTION SIGNALING (5) SIGNALING (5) is not used. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-4 OL-8723-19...

  • Page 373: Signaling (6)

    Contact Cisco Support. (Contact Cisco Technical Assistance Center (TAC).) ACTION Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-5 OL-8723-19...

  • Page 374: Signaling (8)

    Operating system level network errors have occurred or an invalid network configuration exists. CAUSE PRIMARY Have your network administrator resolve the network errors. Contact Cisco TAC if you need ACTION assistance. Manually clear the alarm. Restart this call agent instance using the platform start command.

  • Page 375: Signaling (10)

    Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request. SIGNALING (11) To troubleshoot and correct the cause of the alarm, refer to the “Failed to Allocate Session Initiation...

  • Page 376: Signaling (12)

    The SS7 link may be disconnected or faulty. CAUSE TERNARY Check the Ulticom local configuration. ACTION SUBSEQUENT The remote SS7 signaling site may be down or incorrectly configured. CAUSE SUBSEQUENT Check the Ulticom remote configuration. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-8 OL-8723-19...

  • Page 377: Signaling (14)

    Verify that the SS7 signaling adapter process is running and that the SS7 interface card(s) are in ACTION service. SECONDARY If a component is found to be non-operational, restore it to service. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-9 OL-8723-19...

  • Page 378: Signaling (16)

    Monitor the system for maintenance event reports associated with the signaling adapter or the ACTION underlying platform instances that support the specified SS7 link. Verify that the process and or platform are restarted and returned to service. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-10 OL-8723-19...

  • Page 379: Signaling (18)

    Issued when the specified SS7 link set is inaccessible. CAUSE PRIMARY If the SS7 signaling adapter is not running normally and the associated call agent platform is not active, ACTION return them to service. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-11 OL-8723-19...

  • Page 380: Signaling (20)

    Verify that the processing complex supporting the route set is functional. ACTION SECONDARY Monitor event reports at the network level to determine the failing component and to verify its restoral ACTION to service. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-12 OL-8723-19...

  • Page 381: Signaling (22)

    CAUSE of the following: 1) A failure in the affected DPC. 2) An unavailable route between the BTS 10200 and the affected DPC. PRIMARY Verify that an alternate routing has been assigned for traffic destined to the affected DPC. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x...

  • Page 382: Signaling (24)

    Verify that the SS7 interface hardware is in service. Verify that the associated SS7 signaling link is ACTION available. TERNARY Verify that the T13 timer is set to an appropriate level. ACTION SUBSEQUENT Verify that the SS7 link is not congested. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-14 OL-8723-19...

  • Page 383: Signaling (26)

    Verify that the SS7 interface hardware is in service. Verify that the associated SS7 signaling link is ACTION available. TERNARY Verify that the T13 timer is set to an appropriate level. ACTION SUBSEQUENT Verify that the SS7 link is not congested. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-15 OL-8723-19...

  • Page 384: Signaling (27)

    Verify that the SS7 interface hardware is in service. Verify that the associated SS7 signaling link is ACTION available. TERNARY Verify that the T13 timer is set to an appropriate level. ACTION SUBSEQUENT Verify that the SS7 link is not congested. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-16 OL-8723-19...

  • Page 385: Signaling (28)

    SUBSEQUENT Verify that the associated SS7 signaling link is available. Verify that the T13 timer is set to an ACTION appropriate level. Verify that the SS7 link is not congested. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-17 OL-8723-19...

  • Page 386: Signaling (29)

    Verify that the associated SS7 signaling link is available. ACTION SUBSEQUENT Verify that the T13 timer is set to an appropriate level. Verify that the SS7 link is not congested. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-18 OL-8723-19...

  • Page 387: Signaling (30)

    SUBSEQUENT Verify that the associated SS7 signaling link is available. Verify that the T13 timer is set to an ACTION appropriate level. Verify that the SS7 link is not congested. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-19 OL-8723-19...

  • Page 388: Signaling (31)

    Verify that the SS7 interface hardware is in service. Verify that the associated SS7 signaling link is ACTION available. TERNARY Verify that the T13 timer is set to an appropriate level. ACTION SUBSEQUENT Verify that the SS7 link is not congested. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-20 OL-8723-19...

  • Page 389: Signaling (32)

    Verify that the SS7 interface hardware is in service. Verify that the associated SS7 signaling link is ACTION available. TERNARY Verify that the T13 timer is set to an appropriate level. ACTION SUBSEQUENT Verify that the SS7 link is not congested. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-21 OL-8723-19...

  • Page 390: Signaling (33)

    Verify that the associated SS7 signaling link is available. Verify that the T13 timer is set to an ACTION appropriate level. SUBSEQUENT Verify that the SS7 link is not congested. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-22 OL-8723-19...

  • Page 391: Signaling (34)

    Verify that the associated SS7 signaling link is available. Verify that the T13 timer is set to an ACTION appropriate level. Verify that the SS7 link is not congested. SIGNALING (35) SIGNALING (35) is not used. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-23 OL-8723-19...

  • Page 392: Signaling (36)

    Issued when a BLO or CGB message was sent on the specified CIC. CAUSE PRIMARY No action required. ACTION SIGNALING (37) SIGNALING (37) is not used. SIGNALING (38) SIGNALING (38) is not used. SIGNALING (39) SIGNALING (39) is not used. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-24 OL-8723-19...

  • Page 393: Signaling (40)

    THRESHOLD THROTTLE DATAWORDS CIC Number–TWO_BYTES TGN-ID–FOUR_BYTES DPC–STRING [20] OPC–STRING [20] PRIMARY Issued when a continuity testing (COT) message was received on the specified CIC. CAUSE PRIMARY No action required. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-25 OL-8723-19...

  • Page 394: Signaling (43)

    SEVERITY INFO THRESHOLD THROTTLE DATAWORDS CIC Number–TWO_BYTES TGN-ID–FOUR_BYTES DPC–STRING [20] OPC–STRING [20] PRIMARY Issued when a continuity recheck was performed on the specified CIC. CAUSE PRIMARY No action required. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-26 OL-8723-19...

  • Page 395: Signaling (45)

    CAUSE PRIMARY Verify that the SS7 provisioning tables are properly configured at the circuit level. ACTION SIGNALING (47) SIGNALING (47) is not used. SIGNALING (48) SIGNALING (48) is not used. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-27 OL-8723-19...

  • Page 396: Signaling (49)

    Issued when an unexpected message was received for the current call state. CAUSE PRIMARY The call is cleared. Verify the status of the signaling adapter process and the SS7 signaling interface ACTION to verify proper operation. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-28 OL-8723-19...

  • Page 397: Signaling (51)

    Issued when the specified CIC is marked as not remotely blocked due to the CQM response indicating CAUSE that it is not remotely blocked at the far end. PRIMARY No action required. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-29 OL-8723-19...

  • Page 398: Signaling (53)

    Issued when the circuit specified failed a validation test due to an internal failure. CAUSE PRIMARY Verify that the SS7 signaling adapter process and that the SS7 interface are operating normally. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-30 OL-8723-19...

  • Page 399: Signaling (55)

    OPC–STRING [20] PRIMARY Issued when a continuity recheck of the specified CIC failed. CAUSE PRIMARY Verify that the SS7 signaling adapter process and that the SS7 interface are operating normally. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-31 OL-8723-19...

  • Page 400: Signaling (58)

    Monitor the event reports at the network level to determine which media gateway caused the status ACTION change of the trunk group. SECONDARY Verify that the gateway is reconfigured properly to support the usage of the trunk group. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-32 OL-8723-19...

  • Page 401: Signaling (60)

    Issued when the specified trunk group’s operational status was changed by a service message from the CAUSE specified gateway. PRIMARY Monitor the event reports at the network level to verify that the specified gateway and terminations are ACTION operating normally. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-33 OL-8723-19...

  • Page 402: Signaling (62)

    PRIMARY Verify the proper operation of the media gateway specified. Place the termination out-of-service and ACTION then back into service from the call agent. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-34 OL-8723-19...

  • Page 403: Signaling (64)

    Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request. SIGNALING (65) To troubleshoot and correct the cause of the alarm, refer to the “Media Gateway Adapter Running out of...

  • Page 404: Signaling (66)

    Issued when a call agent internal error has occurred causing the restart of the MGCP signaling adapter. CAUSE PRIMARY Send the log files to Cisco TAC for analysis and corrective action. (Contact Cisco TAC.) ACTION Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request.

  • Page 405: Signaling (68)

    CA or FS is down. PRIMARY Check the configuration related to the CA to FS communication link. Check the FS table entries and ACTION the CA entry. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-37 OL-8723-19...

  • Page 406: Signaling (70)

    The ISDN signaling adapter is unable to establish a D-channel due to layer one parameters not being CAUSE provisioned correctly or improper provisioning of the network or user side. PRIMARY Verify the correct provisioning at the media gateway. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-38 OL-8723-19...

  • Page 407: Signaling (72)

    The ISDN signaling adapter was unable to send a RESTART message due to the expiration of the CAUSE RESTART timer. PRIMARY Verify that the RESTART timer is set to an appropriate level. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-39 OL-8723-19...

  • Page 408: Signaling (74)

    Check SS7 stack configuration. ACTION SECONDARY SS7 stack is not ready. CAUSE SECONDARY Check SS7 stack status. Execute the platform start -i omni command to bring up SS7 stack. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-40 OL-8723-19...

  • Page 409: Signaling (76)

    PRIMARY Verify the operator action. ACTION SECONDARY The active D-channel is lost. CAUSE SECONDARY Verify that the gateway is operational and that the connection to the PBX is good. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-41 OL-8723-19...

  • Page 410: Signaling (78)

    Failure Context–STRING [40] PRIMARY The Trunking Gateway is not responding to keep-alive Audit Endpoint messages. CAUSE PRIMARY Check the IP connectivity status between BTS Call Agent and the Trunking Gateway. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-42 OL-8723-19...

  • Page 411: Signaling (80)

    Description–STRING [40] Extra Info–STRING [40] PRIMARY Out of heap memory. CAUSE PRIMARY Notify customer support. Increase the random access memory (RAM). (Contact Cisco TAC.) ACTION SECONDARY Out of IPC pool memory. CAUSE SECONDARY Resize the IPC pool size in the platform configuration file.

  • Page 412: Signaling (81)

    Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request. SIGNALING (82) To troubleshoot and correct the cause of the alarm, refer to the “Insufficient Shared Memory...

  • Page 413: Signaling (83)

    Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request. SIGNALING (84) To troubleshoot and correct the cause of the alarm, refer to the “Reached Maximum Socket...

  • Page 414: Signaling (85)

    A loss of communication with a remote gateway has occurred. CAUSE PRIMARY Perform the standard connectivity tests–both the physical checks and the IP tests. Also, ensure that the ACTION gateway is not out of service. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-46 OL-8723-19...

  • Page 415: Signaling (87)

    Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request. SIGNALING (88) To troubleshoot and correct the cause of the alarm, refer to the “H323 Message Encoding...

  • Page 416: Signaling (89)

    Check network connectivity. Check to ensure that the alternate GK is reachable by trying to ping the ACTION alternate GK IP address. If reachable, then check to ensure that the alternate GK is configured up. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-48 OL-8723-19...

  • Page 417: Signaling (91)

    PRIMARY The call ID was invalid or changed mid-call. CAUSE PRIMARY There is a software problem on the BTS 10200 or on an endpoint. Call Cisco TAC. (Contact Cisco ACTION TAC.) Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request.

  • Page 418: Signaling (93)

    PRIMARY The call ID was invalid or changed mid-call. CAUSE PRIMARY There is a software problem on the BTS 10200 or on an endpoint. Call Cisco TAC. (Contact Cisco ACTION TAC.) Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request.

  • Page 419: Signaling (94)

    Conference ID–EIGHT_BYTES PRIMARY The call ID was invalid or changed mid-call. CAUSE PRIMARY There is a software problem on the BTS 10200 or on an endpoint. Call Cisco TAC. (Contact Cisco ACTION TAC.) Note Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi detailed instructions on contacting Cisco TAC and opening a service request.

  • Page 420: Signaling (95)

    Note Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi detailed instructions on contacting Cisco TAC and opening a service request. SIGNALING (96) To troubleshoot and correct the cause of the alarm, refer to the “Internal Call Processing...

  • Page 421: Signaling (97)

    Gateway ID–STRING [32] Call ID–EIGHT_BYTES Reason–STRING [128] PRIMARY The H323 endpoint and the BTS 10200 are running different protocol versions. CAUSE PRIMARY This is only an issue where the endpoint is running a higher version of the H323 protocol than the BTS ACTION 10200.

  • Page 422: Signaling (99)

    Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request. SIGNALING (100) To troubleshoot and correct the cause of the alarm, refer to the “Codec Negotiation Failed—Signaling...

  • Page 423: Signaling (101)

    The high water mark has been reached–all new call requests are rejected until the low water mark is ACTION reached. Reprovision the water marks or check the network for overload. Also verify that alternate routes have been provisioned on the BTS 10200. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-55...

  • Page 424: Signaling (103)

    THRESHOLD THROTTLE DATAWORDS AGGR-ID–STRING [16] PRIMARY A TCP connection establish failure has occurred. CAUSE PRIMARY Check the IP connectivity of the CA and the cable modem termination system (CMTS). ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-56 OL-8723-19...

  • Page 425: Signaling (105)

    To troubleshoot and correct the cause of the alarm, refer to the “Enhanced Subscriber Authentication BTS 10200 Delivery Function Connection Down—Signaling (106)” section on page 10-144. DESCRIPTION Enhanced Subscriber Authentication BTS 10200 Delivery Function Connection Down (ESA BTS DF Connection Down) SEVERITY MINOR THRESHOLD...

  • Page 426: Signaling (107)

    A contact could not be resolved to an IP address on the host. CAUSE SECONDARY Verify that the DNS resolves to the IP addresses reserved for the process on the BTS 10200. ACTION TERNARY The IP address manager is not running.

  • Page 427: Signaling (108)

    PRIMARY The hostname parameter is specified in the platform.cfg file instead of -contact parameter. CAUSE PRIMARY The BTS 10200 is configured as a SIMPLEX system. ACTION SIGNALING (109) To troubleshoot and correct the cause of the alarm, refer to the “Stream Control Transmission Protocol...

  • Page 428: Signaling (110)

    The MTP3 user adapter (M3UA) layer is down between the CA and the SGs. CAUSE SECONDARY Use the Cisco snooper application to determine why the M3UA layer is down. ACTION SIGNALING (111) To troubleshoot and correct the cause of the alarm, refer to the “Stream Control Transmission Protocol...

  • Page 429: Signaling (112)

    CAUSE SECONDARY Input new local IP address information. ACTION TERNARY The IP Routing Table is not configured properly. CAUSE TERNARY Have the system administrator configure the IP routing table. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-61 OL-8723-19...

  • Page 430: Signaling (113)

    Signaling Gateway ID–STRING [17] PRIMARY All of the associated signaling gateway processes are out-of-service. CAUSE PRIMARY Determine why each of the associated SGP processes is out-of-service (see the SGP alarm definition). ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-62 OL-8723-19...

  • Page 431: Signaling (114)

    SECONDARY The M3UA layer is down between the CA and the SGP. CAUSE SECONDARY Use the Cisco snooper utility to determine why M3UA layer is down. Also see the log for additional ACTION information. SIGNALING (115) To monitor and correct the cause of the event, refer to the “Invalid Routing Context Received—Signaling...

  • Page 432: Signaling (116)

    Circuit Validation Test Message Received for an Unequipped Circuit Identification Code (CVT Message Received for an Unequipped CIC) SEVERITY MINOR THRESHOLD THROTTLE DATAWORDS CIC–TWO_BYTES TGN-ID–EIGHT_BYTES DPC–STRING [13] PRIMARY The CIC is not provisioned CAUSE PRIMARY Provision the CIC. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-64 OL-8723-19...

  • Page 433: Signaling (118)

    Reason–STRING [36] PRIMARY An OMNI or S7A exception has occurred. CAUSE PRIMARY Check the OMNI process. The S7A will restart itself if S7A maximum number of restarts is not ACTION exceeded. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-65 OL-8723-19...

  • Page 434: Signaling (120)

    No INACTIVE acknowledge (ACK) messages are received from any SG or SCTP. The associations CAUSE are probably down. PRIMARY Investigate any other alarms to see if SGs are down or the SCTP associations are down. Take corrective ACTION action according to those alarms. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-66 OL-8723-19...

  • Page 435: Signaling (122)

    Destination Point Co–STRING [20] Remote Subsystem Num–TWO_BYTES PRIMARY A link loss has occurred or the remote subsystem is out of service. CAUSE PRIMARY Check the links. Check the remote location, if possible. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-67 OL-8723-19...

  • Page 436: Signaling (125)

    MAJOR THRESHOLD THROTTLE PRIMARY A Trillium stack binding failure has occurred. CAUSE PRIMARY Re-initialize the TSA process or remove the subsystem from the EMS table and add it again. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-68 OL-8723-19...

  • Page 437: Signaling (128)

    Provisioned Resource Limit) SEVERITY WARNING THRESHOLD THROTTLE DATAWORDS Dialogue/Invoke ID–FOUR_BYTES PRIMARY The Transaction Capabilities Application Part (TCAP) has run out of all the pre-configured dialogue CAUSE IDs or invoke IDs. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-69 OL-8723-19...

  • Page 438: Signaling (133)

    An error in the ISDN user part (ISUP) stack or in a signaling adapter interface (SAI) message has CAUSE occurred. PRIMARY Capture the SS7 trace of circuit for examination by support personnel. (Contact Cisco TAC.) ACTION Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request.

  • Page 439: Signaling (135)

    An error in the ISUP stack or in a SAI message has occurred. CAUSE PRIMARY Capture the SS7 trace of circuit for examination by support personnel. (Contact Cisco TAC.) ACTION Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request.

  • Page 440: Signaling (136)

    An invalid message was received from the line in the ISUP stack. CAUSE PRIMARY Capture the SS7 trace of circuit for examination by support personnel. (Contact Cisco TAC.) ACTION SECONDARY An invalid message was received from the line in the ISUP stack.

  • Page 441: Signaling (137)

    Cisco support. (Contact Cisco TAC.) Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-73 OL-8723-19...

  • Page 442: Signaling (139)

    The far-end switch is not responding to an information (INF) message with an information request CAUSE (INR) message. PRIMARY Verify that the far-end switch can correctly respond to an INF message. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-74 OL-8723-19...

  • Page 443: Signaling (141)

    The transport service access point (TSAP) address or hostname is not defined in the DNS. CAUSE PRIMARY Add an entry for the TSAP address to the DNS server, or fix the BTS 10200 provisioning. ACTION SIGNALING (142) To troubleshoot and correct the cause of the alarm, refer to the “Session Initiation Protocol Trunk...

  • Page 444: Signaling (143)

    Interface Links to SS7 Signaling Gateway are Down) SEVERITY CRITICAL THRESHOLD THROTTLE DATAWORDS Interface Name–STRING [65] Interface IP Address–STRING [65] PRIMARY A hardware problem has occurred. CAUSE PRIMARY Check the link interfaces. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-76 OL-8723-19...

  • Page 445: Signaling (145)

    IP addresses. Ensure that the previous hop network component is alive and in a healthy state for failures related to the SIP responses. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-77 OL-8723-19...

  • Page 446: Signaling (147)

    PRIMARY The DNS service (SRV) hostname resolution to the IP address is exhausted. CAUSE PRIMARY Add an entry to the SRV in the DNS server. Fix the BTS 10200 provisioning. ACTION SIGNALING (148) SIGNALING (148) is not used. SIGNALING (149) SIGNALING (149) is not used.

  • Page 447: Signaling (151)

    Try controlling subscriber termination to OOS and back to INS using the BTS 10200 CLI command. ACTION If the problem persist after more calls, check the configuration in the BTS 10200 and the RGW. If the error codes returned by the MGW are harmless, it can be suppressed by adding a new entry in MGCP-RETCODE-ACTION table and by changing the EP-ACTION to RESET/NONE.

  • Page 448: Signaling (153)

    DPC- STRING [20] OPC- STRING [20] MGW-EP-Name–STRING [64] MGW-TSAP_ADDR–STRING [80] Reason–STRING [80] PRIMARY Issued when an emergency trunk (CAS, SS7, or ISDN) gets remotely blocked. CAUSE PRIMARY No action is required. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-80 OL-8723-19...

  • Page 449: Signaling (155)

    Check to see if the SCTP association is down due to an issue on the network. ACTION SECONDARY The IUA layer may be down in the gateway. CAUSE SECONDARY No action is needed. The IUA layer will be automatically recovered. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-81 OL-8723-19...

  • Page 450: Signaling (157)

    The interface ID is not configured correctly on the ISDN gateway side. CAUSE PRIMARY Configure the D-channel correctly on the gateway side. The D-channel configuration on the call-agent ACTION side should match with that on the gateway side. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-82 OL-8723-19...

  • Page 451: Signaling (159)

    SCTP associations are probably down. PRIMARY Investigate other alarms to see if the signaling gateways are down or the SCTP associations are down. ACTION Take corrective action according to those alarms. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-83 OL-8723-19...

  • Page 452: Signaling (161)

    The remote switch does not allow the BTS 10200 to send SIP UPDATE messages. The UPDATE CAUSE message is mandatory in CMSS and is used exclusively by the BTS 10200 for operator service calls over SIP including BLV, emergency interrupt, and 911 ringback calls.

  • Page 453: Signaling (163)

    Signaling Gateway ID–STRING [17] Signaling Gateway Process ID–STRING [17] PRIMARY The traffic mode does not match on the BTS 10200 and the Signaling Gateway. CAUSE PRIMARY Verify the AS traffic-mode configuration in the Signaling Gateway. Check that the SG internal ACTION redundancy mode for the traffic-mode setting has been set correctly in the BTS 10200.

  • Page 454: Signaling (165)

    Routing keys are not controlled into an ACTIVE state. CAUSE PRIMARY Control the routing keys to the ACTIVE state. ACTION SECONDARY The ITP provisioning is incorrect. CAUSE SECONDARY Check the ITP provisioning. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-86 OL-8723-19...

  • Page 455: Signaling (167)

    No Signaling Gateways are Active SEVERITY WARNING THRESHOLD THROTTLE PRIMARY A communication problem between the ITP and the BTS 10200 has occurred. CAUSE PRIMARY Check the communication path between the BTS 10200 and the ITP. ACTION SIGNALING (168) To monitor and correct the cause of the event, refer to the “A Session Initiation Protocol Server Group...

  • Page 456: Signaling (169)

    The residential gateway has been administratively taken OOS using the command at the GW. CAUSE PRIMARY Bring the residential gateway administratively into INS using the command at the GW. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-88 OL-8723-19...

  • Page 457: Signaling (171)

    A MGCP signaling interop error has occurred with the residential media gateway. CAUSE PRIMARY Check the IP connectivity status between BTS 10200 call agent and the trunking gateway. If the ACTION residential gateway is not physically connected, but controlled INS at the BTS 10200.

  • Page 458: Signaling (173)

    ENUM Server Farm Name - STRING [128] ENUM Profile ID - STRING [64] PRIMARY A network or server problem has occurred. CAUSE PRIMARY Fix the network or server problem. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-90 OL-8723-19...

  • Page 459: Signaling (175)

    No Resources Available to Launch ENUM Query SEVERITY CRITICAL THRESHOLD THROTTLE DATAWORDS PRIMARY Internal or network congestion or slow server response has occurred. CAUSE PRIMARY Fix the network congestion or improve the server response. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-91 OL-8723-19...

  • Page 460: Signaling (177)

    D-Chan ID - STRING [20] D-Chan Index - FOUR_BYTES D-Chan Type - STRING [10] PRIMARY The BTS 10200 does not receive the Service Ack from the remote end in response to Service message CAUSE to make the D-Channel active. PRIMARY Verify that the NFAS provisioning at the PBX/media gateway is correct.

  • Page 461: Monitoring Signaling Events

    Unanswered Circuit Validation Test Message—Signaling (30) WARNING SIGNALING(31) Unanswered Reset Circuit Message—Signaling (31) WARNING SIGNALING(32) Unanswered Group Reset Message—Signaling (32) WARNING SIGNALING(33) Unanswered Release Message—Signaling (33) WARNING SIGNALING(34) Unanswered Continuity Check Request Message—Signaling (34) WARNING Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-93 OL-8723-19...
  • Page 462 Integrated Services Digital Network–Calls Lost Due to D-channel Down for Period WARNING of Time—Signaling (72) SIGNALING(73) Integrated Services Digital Network–Unable to Send RESTART Due to RESTART WARNING Timer Expired—Signaling (73) Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-94 OL-8723-19...
  • Page 463 Aggregation Connection Down—Signaling (103) MAJOR SIGNALING(104) Aggregation Unable To Establish Connection—Signaling (104) INFO SIGNALING(105) Aggregation Gate Set Failed—Signaling (105) INFO SIGNALING(106) Enhanced Subscriber Authentication BTS 10200 Delivery Function Connection MINOR Down—Signaling (106) Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-95 OL-8723-19...
  • Page 464 Signaling System 7 Trunk was Found to be in Erroneous State—Signaling (139) INFO (SS7) SIGNALING(140) Unanswered Information Message—Signaling (140) INFO SIGNALING(141) Address not Resolved by Domain Name System Server—Signaling (141) WARNING SIGNALING(142) Session Initiation Protocol Trunk Operationally Out-of-Service—Signaling (142) CRITICAL Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-96 OL-8723-19...
  • Page 465 Session Initiation Protocol Element Provisioned with Service Enabled is Internally INFO Disabled—Signaling (169) SIGNALING(170) Residential Gateway Endpoints are out of Service at the Gateway—Signaling (170) MINOR SIGNALING(171) Residential Gateway Unreachable—Signaling (171) MINOR Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-97 OL-8723-19...

  • Page 466: Test Report—Signaling (1)

    The Socket Failure alarm (major) indicates that there is a failure in creating/binding to the UDP socket. To troubleshoot and correct the cause of the Socket Failure alarm, refer to the “Socket Failure—Signaling (7)” section on page 10-130. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-98 OL-8723-19...

  • Page 467: Session Initiation Protocol Message Receive Failure—Signaling (8)

    The Link is Remotely Inhibited alarm (minor) indicates that the SS7 link is inhibited at the remote end. To troubleshoot and correct the cause of the Link is Remotely Inhibited alarm, refer to the “Link is Remotely Inhibited—Signaling (14)” section on page 10-133. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-99 OL-8723-19...

  • Page 468: Link Is Locally Inhibited—Signaling (15)

    The Route Set Failure alarm (major) indicates that the specified route set has a experienced a failure. To troubleshoot and correct the cause of the Route Set Failure alarm, refer to the “Route Set Failure—Signaling (21)” section on page 10-135. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-100 OL-8723-19...

  • Page 469: Route Set Congested—Signaling (22)

    SS7 interface hardware is in service. Verify that the associated SS7 signaling link is available. Verify that the T13 timer is set to an appropriate level. Verify that the SS7 link is not congested. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-101...

  • Page 470: Unanswered Circuit Group Unblocking Message—Signaling (28)

    Verify that the associated SS7 signaling link is available. Verify that the T13 timer is set to an appropriate level. Verify that the SS7 link is not congested. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-102...

  • Page 471: Unanswered Release Message—Signaling (33)

    Identification Code event functions as an informational alert that the RLC was received in response to the RSC message received on the specified CIC. The event is informational and no further action is required, Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-103 OL-8723-19...

  • Page 472: Continuity Recheck Is Performed On Specified Circuit Identification Code—Signaling (44)

    CQM response indicating that it is unequipped at the far end. To correct the primary cause of the event, equip the trunk circuit at the far end. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-104...

  • Page 473: Set Trunk State As Not Remotely Blocked—Signaling (52)

    The Continuity Recheck Successful event functions as an informational alert that the continuity recheck of the specified CIC was successful. The event is informational and no further action is required. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-105 OL-8723-19...

  • Page 474: Gateway—Signaling (59)

    To troubleshoot and correct the cause of the Media Gateway/Termination Faulty alarm, refer to the “Media Gateway/Termination Faulty—Signaling (63)” section on page 10-137. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-106 OL-8723-19...

  • Page 475: Media Gateway Adapter Running Out Of Shared Memory Pools—Signaling (64)

    Up or is not Responding to the Feature Server alarm, refer to the “Call Agent is not Up or is not Responding to the Feature Server—Signaling (69)” section on page 10-139. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-107 OL-8723-19...

  • Page 476: Integrated Services Digital Network Unable To Restore D-Channel Due To Failed Communication—Signaling (70)

    RESTART message due to the expiration of the RESTART timer. To correct the primary cause of the event, verify that the RESTART timer is set to an appropriate level. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-108...

  • Page 477: Expired—Signaling (74)

    Integrated Services Digital Network Single D-channel Down for Non-Facility Associated Signaling alarm, refer to the “Integrated Services Digital Network Single D-channel Down for Non-Facility Associated Signaling—Signaling (78)” section on page 10-139. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-109 OL-8723-19...

  • Page 478: Trunking Gateway Unreachable—Signaling (79)

    10-140. Reached Maximum Socket Limit—Signaling (84) The Reached Maximum Socket Limit alarm (critical) indicates that the BTS 10200 system has reached the maximum socket limit. To troubleshoot and correct the cause of the Reached Maximum Socket Limit alarm, refer to the “Reached Maximum Socket Limit—Signaling (84)”...

  • Page 479: Remote H323 Gateway Is Not Reachable—Signaling (86)

    The Invalid Call Identifier alarm (minor) indicates that the Call ID was invalid or changed mid-call. To troubleshoot and correct the cause of the Invalid Call Identifier alarm, refer to the “Invalid Call Identifier—Signaling (92)” section on page 10-142. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-111 OL-8723-19...

  • Page 480: Invalid Call Reference Value—Signaling (93)

    10-143. H323 Protocol Inconsistencies—Signaling (98) The H323 Protocol Inconsistencies alarm (minor) indicates that the H323 endpoint and BTS 10200 are running different protocol versions. To troubleshoot and correct the cause of the H323 Protocol Inconsistencies alarm, refer to the “H323 Protocol Inconsistencies—Signaling (98)”...

  • Page 481: Codec Negotiation Failed—Signaling (100)

    The Aggregation Gate Set Failed event functions as an informational alert that the AGGR gate set failed. The primary cause of the event is that the gate set acknowledgement never came from the CMTS. The event is informational and no further action is required. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-113 OL-8723-19...

  • Page 482: Logical Internet Protocol Addresses Not Mapped Correctly—Signaling (107)

    10-145. Simplex Only Operational Mode—Signaling (108) The Simplex Only Operational Mode alarm (major) indicates that the BTS 10200 system can only operate in the simplex mode. To troubleshoot and correct the cause of the Simplex Only Operational Mode alarm, refer to the “Simplex Only Operational Mode—Signaling (108)”...

  • Page 483: Stream Control Transmission Protocol Association Configuration Error—Signaling (112)

    Circuit Validation Test Message Received for an Unequipped Circuit Identification Code alarm, refer to the “Circuit Validation Test Message Received for an Unequipped Circuit Identification Code—Signaling (117)” section on page 10-153. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-115 OL-8723-19...

  • Page 484: Circuit Verification Response Received With Failed Indication—Signaling (118)

    To troubleshoot and correct the cause of the Remote Subsystem is out of Service alarm, refer to the “Remote Subsystem is Out Of Service—Signaling (124)” section on page 10-154. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-116 OL-8723-19...

  • Page 485: Signaling Connection Control Part Routing Error—Signaling (125)

    GTD protocol used by the device at the remote endpoint is consistent with the version expected by the call agent. Examine the associated signaling link to see if there is any interruption of the supplementary services on the link. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-117 OL-8723-19...

  • Page 486: Signaling System 7 Message Encoding Failure—Signaling (134)

    (including CFN diagnostic output). Capture SS7 trace of affected circuits. If diagnostic data indicates messages/parameters that must be supported are being dropped, refer the captured data to Cisco TAC along with a description of the call scenario. Refer to the “Obtaining Documentation and Submitting a Service Request”...

  • Page 487: Signaling System 7 Trunk Was Found To Be In Erroneous State—Signaling (139) (Ss7)

    System configuration and traffic load have caused the number of open connections to approach the engineered limit. Contact Cisco TAC for assistance in increasing in the limit. Refer to the “Obtaining Documentation and Submitting a Service Request”...

  • Page 488: Session Initiation Protocol Trunk Operationally Out-Of-Service—Signaling (142)

    One Internet Protocol Interface to Signaling System 7 Signaling Gateway is Down alarm, refer to the “One Internet Protocol Interface to Signaling System 7 Signaling Gateway is Down—Signaling (145)” section on page 10-156. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-120 OL-8723-19...

  • Page 489: Domain Name System Service Addresses Exhausted—Signaling (147)

    The Termination Transient Error Received event functions as an informational alert that a termination transient error was received. The primary cause of the event is that the MGCP signaling process has inter-operational errors. To correct the primary cause of the event, notify Cisco TAC. Refer to the “Obtaining Documentation and Submitting a Service Request”...

  • Page 490: Emergency Trunks Become Locally Blocked—Signaling (153)

    ID is not configured correctly on the ISDN gateway side. To correct the cause of the event, configure the D-channel correctly on the gateway side. The D-channel configuration on the call-agent side should match with that on the gateway side. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-122 OL-8723-19...

  • Page 491: Calls—Signaling (161)

    The Session Initiation Protocol Update not Allowed for Operator Service Position System Calls event serves as a warning that the remote switch is not allowing the BTS 10200 to send SIP UPDATE messages. The UPDATE messages are mandatory in the CMSS and are used exclusively by the BTS 10200 for operator service calls over SIP including BLV, emergency interrupt, and 911 ringback calls.

  • Page 492: Signaling Gateway Traffic Mode Mismatch—Signaling (164)

    The Signaling Gateway Traffic Mode Mismatch alarm (major) indicates that the traffic mode does not match on the BTS 10200 and the Signaling Gateway. To troubleshoot and correct the primary cause of the Signaling Gateway Traffic Mode Mismatch alarm, refer to the “Signaling Gateway Traffic Mode...

  • Page 493: Disabled—Signaling (169)

    ENUM Server Domain Cannot be Resolved Into Any IP Address alarm, refer to the “ENUM Server Domain Cannot be Resolved Into Any IP Address —Signaling (173)” section on page 10-159. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-125 OL-8723-19...

  • Page 494: Enum Server Unavailable—Signaling (174)

    The ISDN Unable to Restore D-Channel Into In-Service Active State warning event indicates that the BTS 10200 did not receive the Service Ack from the remote end in response to the Service message to make the D-Channel active. To correct the cause of the event, verify that the NFAS provisioning at the PBX/media gateway is correct.

  • Page 495: Troubleshooting Signaling Alarms

    Call Agent is not Up or is not Responding to the Feature Server—Signaling (69) CRITICAL SIGNALING(75) Signaling System 7 Stack not Ready—Signaling (75) CRITICAL SIGNALING(78) Integrated Services Digital Network Single D-channel Down for Non-Facility MINOR Associated Signaling—Signaling (78) Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-127 OL-8723-19...
  • Page 496 SIGNALING(102) H323 Network Congested—Signaling (102) MINOR SIGNALING(103) Aggregation Connection Down—Signaling (103) MAJOR SIGNALING(106) Enhanced Subscriber Authentication BTS 10200 Delivery Function Connection MINOR Down—Signaling (106) SIGNALING(107) Logical Internet Protocol Addresses not Mapped Correctly—Signaling (107) CRITICAL SIGNALING(108) Simplex Only Operational Mode—Signaling (108)
  • Page 497 Multimedia Terminal Adapter Effective-Aggr-Id Becomes Unavailable Due to Its IP MAJOR Address—Signaling (172) SIGNALING(173) ENUM Server Domain Cannot be Resolved Into Any IP Address —Signaling (173) CRITICAL SIGNALING(174) ENUM Server Unavailable—Signaling (174) CRITICAL Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-129 OL-8723-19...

  • Page 498: Socket Failure—Signaling (7)

    “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request. Media Gateway Control Protocol The Socket Failure alarm is issued when there is a failure in creating the UDP port used by the MGCP stacks.

  • Page 499: Session Initiation Protocol Message Receive Failure—Signaling (8)

    Media Gateway Control Protocol The Timeout on IP Address alarm is issued when the BTS 10200 is unable to communicate with a gateway. Verify that the gateway is both configured for service and that it has been set in service.

  • Page 500: Failed To Send Complete Session Initiation Protocol Message—Signaling (10)

    UDP packet. To correct the primary cause of the alarm, the message should be captured on passive testing equipment and sent to Cisco TAC for evaluation if that alarm occurred during normal network operations.

  • Page 501: Signaling System 7 Signaling Link Down—Signaling (13)

    SS7 signaling adapter process is running and that the SS7 interface card(s) are in service. If a component is found to be non-operational, restore it to service. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-133...

  • Page 502: Link Is Congested—Signaling (16)

    Verify that the SS7 link set has not degraded in quality. Verify that the traffic load has not become unbalanced if multiple SS7 link sets are used. Verify that local SS7 signaling adapter process is running normally. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-134 OL-8723-19...

  • Page 503: Route Set Failure—Signaling (21)

    SS7 link set has not degraded in quality. Verify that the traffic load has not become unbalanced if multiple SS7 link sets are used. Verify that local SS7 signaling adapter process is running normally. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-135...

  • Page 504: Destination Point Code Unavailable—Signaling (23)

    Determine if there is an M3UA Cannot Go Active alarm. This occurs if, at the time of startup or failover, Step 2 the BTS 10200 is not able to communicate with any of the SGs. If this is the case, proceed to the “Message Transfer Part 3 User Adapter Cannot Go Active—Signaling (122)” section on page 10-154.

  • Page 505: Destination Point Code Congested—Signaling (24)

    (either a hardware failure or a general call agent error). To correct the primary cause of the alarm, verify the proper operation of the media gateway specified. Place the termination out-of-service and then back into service from the call agent. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-137 OL-8723-19...

  • Page 506: Media Gateway Adapter Running Out Of Shared Memory Pools—Signaling (64)

    The primary cause of the alarm is that the MGCP signaling adapter was unable to allocate data store for an IPC message due to a lack of resources. To correct the primary cause of the alarm, contact Cisco TAC technologies for assistance.

  • Page 507: Call Agent Is Not Up Or Is Not Responding To The Feature Server—Signaling (69)

    The primary cause of the alarm is that the system is out of heap memory. To correct the primary cause of the alarm, contact Cisco TAC and increase RAM memory. The secondary cause of the alarm is that the system is out of IPC pool memory. To correct the secondary cause of the alarm, resize the IPC pool size in Platform Configuration file.

  • Page 508: Insufficient Heap Memory—Signaling (81)

    Cisco TAC and opening a service request. Reached Maximum Socket Limit—Signaling (84) The Reached Maximum Socket Limit alarm (critical) indicates that the BTS 10200 system has reached the maximum socket limit. The primary cause of the alarm is that the configuration setting of an H3A parameter in the platform.cfg file is wrong.

  • Page 509: Remote H323 Gateway Is Not Reachable—Signaling (86)

    The H323 Message Encoding Error alarm (major) indicates that a H323 message encoding error has occurred. The primary cause of the alarm is that the system was unable to encode an H323 message for sending. The alarm is indicative a software bug. To correct the primary cause of the alarm, contact Cisco TAC.

  • Page 510: Endpoint Security Violation—Signaling (91)

    Call ID was invalid or changed mid-call. The alarm indicates that a software problem has occurred on the BTS 10200 or on the endpoint. To correct the primary cause of the alarm, contact Cisco TAC.

  • Page 511: Invalid Message From The Network—Signaling (95)

    The primary cause of the alarm is that the H323 endpoint and the BTS 10200 are running different protocol versions. This is only an issue where the endpoint is running a higher version of the H323 protocol than the BTS 10200. To correct the primary cause of the alarm, contact Cisco TAC.

  • Page 512: Abnormal Call Clearing—Signaling (99)

    The Enhanced Subscriber Authentication BTS 10200 Delivery Function Connection Down alarm (minor) indicates that the ESA BTS 10200 DF connection is down. The primary cause of the alarm is that the DF server is not responding. To correct the primary cause of the alarm, check the encryption key or the IP connectivity to the DF.

  • Page 513: Logical Internet Protocol Addresses Not Mapped Correctly—Signaling (107)

    The Simplex Only Operational Mode alarm (major) indicates that the BTS 10200 system can only operate in the simplex mode. The primary cause of the alarm is that the -hostname parameter is specified in the platform.cfg file (instead of the -contact parameter). The BTS 10200 is configured as a SIMPLEX system.

  • Page 514: Stream Control Transmission Protocol Association Failure—Signaling (109)

    If the state is down proceed to Step 2. If the state of the ASP is inactive, the ASP is probably on the standby BTS 10200. If the ASP on the active BTS 10200 is inactive, proceed to Step 7.
  • Page 515 The local IP port number is shown directly after the -p option. – The local IP addresses that are used by the BTS 10200 are derived from the DNS name, which is given directly after the -h option. At the BTS 10200 UNIX prompt, enter: NSlookup <DNS name>...
  • Page 516 IP router. In the platform.log, look for the following ERROR message: “All the IP interfaces are faulty!!” If this message is found, the Ethernet connections of the BTS 10200 have been pulled or cut. If this message is not found, proceed to Step 4.

  • Page 517: Signaling Connection Control Part User Adapter Troubleshooting Procedures

    Determine if the SCTP association has come back in service by typing the following BTS 10200 CLI command: status sctp-assoc id=<sctp-assoc-name>; The output will display either OPER STATE -> SCTP-ASSOC out of service or OPER STATE ->...

  • Page 518: Signaling Gateway Group Is Out-Of-Service—Signaling (110)

    “Stream Control Transmission Protocol Association Degraded (One of Two Internet Protocol Connections Down)—Signaling (111)” section on page 10-150, or contact the Cisco TAC for assistance in resolving this issue. Signaling Connection Control Part User Adapter Troubleshooting Procedure This is either an IP routing problem or an ITP Ethernet port hardware failure. Change the hardware immediately, if it is a hardware failure, to prevent dual outage of the ITP’s IP communication.

  • Page 519: Stream Control Transmission Protocol Association Configuration Error—Signaling (112)

    IP routing table. Message Transfer Part 3 User Adapter Troubleshooting Procedure This alarm indicates that there is a provisioning error keeping the BTS 10200 from properly configuring the SCTP association. Perform the following steps to resolve the problem: To get more information about this alarm, look at the platform.log for error messages containing the...

  • Page 520: Signaling Gateway Failure—Signaling (113)

    “Stream Control Transmission Protocol Association Degraded (One of Two Internet Protocol Connections Down)—Signaling (111)” section on page 10-150. Otherwise, the problem is at the M3UA layer. Call the Cisco TAC for assistance. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-152 OL-8723-19...

  • Page 521: Destination Point Code User Part Unavailable—Signaling (116)

    S7M/S7A processes are faulty. The primary cause of the alarm is that an OMNI failure has occurred. To correct the primary cause of the alarm, check the OMNI status. An automatic failover will occur in a duplex configuration. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-153 OL-8723-19...

  • Page 522: Message Transfer Part 3 User Adapter Cannot Go Standby—Signaling (121)

    To correct the primary cause of the alarm, investigate other alarms to see if SGs are down or if SCTP associations are down. Take corrective action according to those alarms. This alarm is raised at initial startup or during failover by the BTS 10200 node that is trying to go into platform Standby mode. See the “Stream Control Transmission Protocol Association Degraded (One of...

  • Page 523: Signaling Connection Control Part Binding Failure—Signaling (126)

    The Session Initiation Protocol Trunk Operationally Out-of-Service alarm (critical) indicates that the SIP trunk is operationally out-of-service. The primary cause of the alarm is that the BTS 10200 is unable to communicate with a remote SIP party (Call-Agent or Proxy) over a SIP or SIP-T trunk. To correct the primary cause of the alarm, verify that the DNS resolution exists, if TSAP address of the remote entity is a domain name.

  • Page 524: Stream Control Transmission Protocol Association Congested—Signaling (150)

    OOS and back into INS using the BTS 10200 CLI command. If the problem persist after more calls, check the configuration in the BTS 10200 and the RGW. If the error codes returned by MGW are harmless, it can be suppressed by adding a new entry in the MGCP-RETCODE-ACTION table and change EP-ACTION to RESET/NONE.

  • Page 525: Emergency Trunks Become Locally Blocked—Signaling (153)

    The Session Initiation Protocol Server Group Element Operationally Out of Service alarm (critical) is issued when the BTS 10200 is unable to communicate with a remote SIP party. The primary cause of the alarm is that the BTS 10200 is unable to communicate with a remote SIP party (call-agent or proxy) over a SIP server group element.

  • Page 526: Routing Key Inactive—Signaling (163)

    The Signaling Gateway Traffic Mode Mismatch alarm (major) indicates that the traffic mode does not match on the BTS 10200 and the Signaling Gateway. To troubleshoot and correct the primary cause of the Signaling Gateway Traffic Mode Mismatch alarm, verify the AS traffic-mode configuration in the Signaling Gateway.

  • Page 527: Enum Server Domain Cannot Be Resolved Into Any Ip Address —Signaling (173)

    ENUM query. The primary cause of the alarm is that there is internal or network congestion or that the server response is slow. To troubleshoot and correct the primary cause of the alarm, fix the network congestion or improve the server response. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-159 OL-8723-19...
  • Page 528 Chapter 10 Signaling Troubleshooting Troubleshooting Signaling Alarms Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 10-160 OL-8723-19...

  • Page 529: Introduction

    • statistics alarms. Statistics Events and Alarms This section provides a brief overview of all of the statistics events and alarms for the Cisco BTS 10200 Softswitch in numerical order. Table 11-1 lists all of the statistics events and alarms by severity.

  • Page 530: C H A P T E R 11 Statistics Troubleshooting

    SEVERITY INFO THRESHOLD THROTTLE DATAWORDS End Time–STRING [40] PRIMARY Indicates that the 15-minute traffic measurement collection process has completed on the Call Agent. CAUSE PRIMARY No action is necessary. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 11-2 OL-8723-19...

  • Page 531: Statistics (4)

    INFO THRESHOLD THROTTLE DATAWORDS End Time–STRING [40] PRIMARY Indicates that the 15-minute traffic measurement collection process has finished on the CAUSE POTS/Centrex/Tandem Feature Server. PRIMARY No action is necessary. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 11-3 OL-8723-19...

  • Page 532: Statistics (6)

    INFO THRESHOLD THROTTLE DATAWORDS End Time–STRING [40] PRIMARY Indicates that the 15-minute traffic measurement collection process has completed on the AIN feature CAUSE server. PRIMARY No action is necessary. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 11-4 OL-8723-19...

  • Page 533: Statistics (8)

    TERNARY The platform is currently shutting down a process. CAUSE TERNARY If the hub process is down, try to bring it into a normal state. (Contact Cisco Technical Assistance ACTION Center (TAC).) Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request.

  • Page 534: Statistics (9)

    Cisco TAC for technical support. Note Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi detailed instructions on contacting Cisco TAC and opening a service request. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 11-6 OL-8723-19...

  • Page 535: Statistics (10)

    Cisco TAC for technical support. Note Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi detailed instructions on contacting Cisco TAC and opening a service request. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 11-7 OL-8723-19...

  • Page 536: Statistics (11)

    If the status report indicates that the originating process is down, try to bring the process back into the ACTION normal (In Service) state. If you need assistance in restoring a process, contact Cisco TAC. TERNARY The platform is currently shutting down the originating process.

  • Page 537: Statistics (12)

    Counters were added or deleted from the schema in Oracle but not in the call agent. CAUSE PRIMARY Add or delete the counters on the CA. ACTION SECONDARY Load is installed incorrectly. CAUSE SECONDARY Reinstall the load. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 11-9 OL-8723-19...

  • Page 538: Statistics (13)

    Calls on the MDII trunk termination are not being successfully completed. CAUSE PRIMARY The BTS 10200 system may take this trunk out of service if it does not take the full trunk group out of ACTION service. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x...

  • Page 539: Statistics (15)

    Trunk Group has Reached the MDII Alarm Threshold SEVERITY WARNING THRESHOLD THROTTLE DATAWORDS Trunk Group - FOUR_BYTES PRIMARY The trunk group has reached the MDII alarm threshold. CAUSE PRIMARY Check the performance status of trunk group. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 11-11 OL-8723-19...

  • Page 540: Monitoring Statistics Events

    The Call Agent Measurement Collection Started event functions as an informational alert that the call agent measurement collection has started. The event is informational and no further action is required. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 11-12 OL-8723-19...

  • Page 541: Call Agent Measurement Collection Finished—Statistics (3)

    The Advanced Intelligent Network Feature Server Measurement Collection Finished event functions as an informational alert that the AIN feature server measurement collection has finished. The event is informational and no further action is required. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 11-13 OL-8723-19...

  • Page 542: Message Send Failure—Statistics (8)

    “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request. Issued when the traffic measurement subsystem in the CA fails to send messages to the EMS due to: Originating process (for CA, FS or EMS) is not in active state, or is shut down.

  • Page 543: Measurement Table Structured Query Language Write Error—Statistics (10)

    (In Service) state. If you need assistance in restoring a process, contact Cisco TAC. The ternary cause of the event is that the platform is currently shutting down the originating process. To correct the ternary cause of the event, check and see if this event report is being issued every collection period, contact Cisco TAC for assistance.

  • Page 544: Mdii Trunk—Statistics (14)

    The MDII Trunk event serves as a warning that the calls on the MDII trunk termination are not being successfully completed. The BTS 10200 system may take the MDII trunk out of service if it does not take the full trunk group out of service.

  • Page 545: Troubleshooting Statistics Alarms

    To correct the subsequent cause of the alarm, reconfigure and restart the system. Threshold Crossing Alert—Statistics (15) The Threshold Crossing Alert alarm (minor) indicates that a threshold crossing has occurred. To correct the cause of the alarm, reduce the provisioning workload. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 11-17 OL-8723-19...
  • Page 546 Chapter 11 Statistics Troubleshooting Troubleshooting Statistics Alarms Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 11-18 OL-8723-19...

  • Page 547: Introduction

    • system alarms. System Events and Alarms This section provides a brief overview of all of the system events and alarms for the Cisco BTS 10200 Softswitch in numerical order. Table 12-1 lists all of the system events and alarms by severity.

  • Page 548: Chapter 12 System Troubleshooting

    There is a problem with the inter-process communication (IPC) process. CAUSE PRIMARY If the problem persists, call Cisco Technical Assistance Center (TAC). (Contact Cisco TAC.) ACTION Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request.

  • Page 549: System (3)

    “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request. Prior to contacting Cisco TAC, collect the message pool and message queue statistics. To collect the statistics, use the pdm.CAxxx script in the /opt/OptiCall/CAxxx/bin directory. Example: pdm.CA146 ->...

  • Page 550: System (4)

    If the problem persists, call Cisco TAC. (Contact Cisco TAC.) ACTION Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 12-4 OL-8723-19...

  • Page 551: System (5)

    Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request. SYSTEM (6) To troubleshoot and correct the cause of the alarm, refer to the “Index List Insert Error—System (6)”...

  • Page 552: System (7)

    An internal error has occurred. A process was unable to create one of its threads. CAUSE PRIMARY Attempt to restart the node on which the error occurred. If the same error occurs, call Cisco TAC. ACTION (Contact Cisco TAC.) Note Refer to the “Obtaining Documentation and Submitting a Service Request”...

  • Page 553: System (9)

    Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request. SYSTEM (10) To troubleshoot and correct the cause of the alarm, refer to the “Index Update Registration...

  • Page 554: System (11)

    PRIMARY The logic path is not handled by an algorithm in the code. CAUSE PRIMARY Save a trace log from around the time of the occurrence and notify Cisco Systems, Inc. (Contact Cisco ACTION TAC.) Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request.

  • Page 555: System (13)

    A high rate of messages is being received from the network. CAUSE PRIMARY Check the messages to the system. ACTION SECONDARY System or processing thread congestion has occurred. CAUSE SECONDARY Check the process and the system resources. ACTION Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 12-9 OL-8723-19...

  • Page 556: System (15)

    Resource congestion resulting in a slow down in processing messages from queue has occurred. CAUSE SECONDARY Check the platform CPU utilization, the IPC queue depth, and the overall availability of system ACTION resources. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 12-10 OL-8723-19...

  • Page 557: Monitoring System Events

    To troubleshoot and correct the cause of the Inter-Process Communication Message Allocate Failure alarm, refer to the “Inter-Process Communication Message Allocate Failure—System (3)” section on page 12-15. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 12-11 OL-8723-19...

  • Page 558: Inter-Process Communication Message Send Failure—System (4)

    The Unexpected Inter-Process Communication Message Received event serves as a warning that an unexpected IPC message was received. The primary cause of the event is that the IPC process is receiving messages it is not expecting. To correct the primary cause of the event, contact Cisco TAC. Refer to the “Obtaining Documentation and Submitting a Service Request”...

  • Page 559: Index Update Registration Error—System (10)

    MRMW queue has reached the throttle depth. To troubleshoot and correct the cause of the Multiple Readers and Multiple Writers Throttle Queue Depth Reached alarm, refer to the “Multiple Readers and Multiple Writers Throttle Queue Depth Reached—System (15)” section on page 12-17. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 12-13 OL-8723-19...

  • Page 560: Troubleshooting System Alarms

    Cisco TAC. Refer to the “Obtaining Documentation and Submitting a Service Request” section on page lvi Note detailed instructions on contacting Cisco TAC and opening a service request. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 12-14 OL-8723-19...

  • Page 561: Inter-Process Communication Message Allocate Failure—System (3)

    “Obtaining Documentation and Submitting a Service Request” section on page lvi detailed instructions on contacting Cisco TAC and opening a service request. Prior to contacting Cisco TAC, collect the message pool and message queue statistics. To collect the statistics, use the pdm.CAxxx script in the /opt/OptiCall/CAxxx/bin directory.

  • Page 562: Index List Remove Error—System (7)

    The Index Update Registration Error alarm (minor) indicates that an index update registration error has occurred. The primary cause of the alarm is that an application unsuccessfully requested to be notified of table changes. To correct the primary cause of the alarm, contact Cisco TAC. Refer to the “Obtaining Documentation and Submitting a Service Request”...

  • Page 563: Software Error—System (12)

    The Software Error alarm (major) indicates that a software error has occurred. The primary cause of the alarm is that a logic path is not handled by algorithm in the code. To correct the primary cause of the alarm, save the trace log from around the time of occurrence and contact Cisco TAC. Note Refer to the “Obtaining Documentation and Submitting a Service Request”...
  • Page 564 Chapter 12 System Troubleshooting Troubleshooting System Alarms Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 12-18 OL-8723-19...

  • Page 565: Introduction

    Chapter 10, “Signaling Troubleshooting.” The use of the UNIX ifconfig down command on any signaling interface to test or troubleshoot network Caution or interface failures of the BTS 10200 Signaling Interface may lead to undesirable consequences or conditions. Troubleshooting a Network Failure Network failure issues can be caused by several problems.

  • Page 566: C H A P T E R 13 Network Troubleshooting

    If the status of the ASP is inactive, the ASP is probably on the standby BTS 10200. If the ASP on the active BTS 10200 is inactive, enter the following commands on the ITP and check the status again: config terminal cs7 asp <asp-name>...

  • Page 567: Verify The Configuration

    Step 3 association on the BTS 10200 is the same as the local IP address and the local port used by the ITP SCCP user adapter (SUA). If the SCTP association is multi-homed, all of the IP addresses should be verified.
  • Page 568 Network Troubleshooting Troubleshooting a Network Failure Verify that the SCTP port on the BTS 10200 and the remote port of the ASP on the ITP are the same. Step 5 On the BTS 10200, open the platform.cfg file and locate the section for TCAP signaling adapter...

  • Page 569: Verify The Internet Protocol Routing

    “Verify the Configuration” section on page 13-3 from the BTS Step 1 10200 in order to see if traffic is routed as planned. Ping the BTS 10200 addresses discovered in the “Verify the Configuration” section on page 13-3 from Step 2 the ITP to see if traffic is routed as planned.

  • Page 570: Verify The Internet Protocol Transfer Point Message Transfer Part 2 Serial Interface

    If both the interface and the line protocol are down, there is a hardware failure or the interface is manually shutdown. After correcting the problem, continue to the next section. Step 3 Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 13-6 OL-8723-19...

  • Page 571: Verify The Internet Protocol Transfer Point-Signal Transfer Point Linkset Status

    If the checking is successful, continue to the next section. Otherwise, correct the problem and continue. Step 3 Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 13-7 OL-8723-19...

  • Page 572: Verify The Internet Protocol Transfer Point Route

    Verify the Internet Protocol Transfer Point Route To resolve problems with the ITP route, perform the following steps: Verify if there is a route to the destination point code provisioned in the BTS 10200 by entering the Step 1 following command:...

  • Page 573: Oracle Database Tool Restart

    $ java dba.rep.RepAdmin -enable job 4 Restart database job 5. Step 4 $ java dba.rep.RepAdmin -enable job 5 Restart database job 6. Step 5 $ java dba.rep.RepAdmin -enable job 6 Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 13-9 OL-8723-19...
  • Page 574 Chapter 13 Network Troubleshooting Troubleshooting a Network Failure Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 13-10 OL-8723-19...

  • Page 575: Introduction

    Caution The use of the UNIX ifconfig down command on any signaling interface to test or troubleshoot network or interface failures of the BTS 10200 Signaling Interface may lead to undesirable consequences or conditions. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x...

  • Page 576: C H A P T E R 14 General Troubleshooting

    General Troubleshooting Troubleshooting CORBA Problems Troubleshooting CORBA Problems To troubleshoot CORBA interface problems, refer to the BTS 10200 CORBA Adapter Interface Specification Programmer Guide, Chapter 5. Troubleshooting Local Number Portability Problems Problems can arise when porting a subscriber’s telephone number from one service provider to another.

  • Page 577: Resolving Local Number Portability Conflicts

    Within the first 6 hours, only the old service provider can initiate “conflict off.” After 6 hours, either service provider can remove the conflict status. The new service provider can alternatively request cancellation of the Subscription Version. Figure 14-1 Conflict Resolution Work Flow Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 14-3 OL-8723-19...

  • Page 578: Audit Requests

    The report distribution service supports distribution to electronic files, to local or remote printers, to e-mail addresses, and to fax machines. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 14-4 OL-8723-19...

  • Page 579: Troubleshooting Alerting Notification Problems

    Enter the CLI command to check for Signaling alarm #12—Feature Server is not up or is not responding Step 5 to Call Agent. If this alarm is raised, there is a communications problem between the BTS 10200 and the 3PTYFS.

  • Page 580: Command Responses

    Step 6 Verify that the 3PTYFS is provisioned to support this feature in accordance with the applicable product Step 7 documentation. The BTS 10200 does not send any provisioning or status/control commands to the 3PTYFS. Step 8 Verify that the 3PTYFS and peripheral devices are operating properly according to the applicable product documentation.

  • Page 581: Success And Failure Responses

    • ADM not allow trunk to reset. • ADM not allow subscriber to reset. • ADM change to out-of-service state required. • ADM change to request graceful mode error. • Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 14-7 OL-8723-19...
  • Page 582 ADM found entity unequipped in initial state. • ADM operation not allowed because D Channel(s) is down. • The H.323 Gateway was not found in database management (DBM). • ADM found unknown failure reason(s). • Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 14-8 OL-8723-19...

  • Page 583: Termination Reason Responses

    Quality of service (QoS) resource reservation was lost Response too big • The media gateway is down • The media gateway is in a faulty state • The media gateway is transitioning to another state • Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 14-9 OL-8723-19...
  • Page 584 Unknown or unsupported digit map extension • Unknown or unsupported quarantine handling • Unknown or unsupported RestartMethod • Unsupported or invalid mode • Unsupported or unknown package • Unsupported values on local connection options • Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 14-10 OL-8723-19...

  • Page 585: Trunk Reason Responses

    TERM-FAULT—Bearer termination is in faulty condition. • TFC_CONGESTION_LEVEL_1—Transfer controlled (TFC) congestion is at level 1. • TFC_CONGESTION_LEVEL_2—TFC congestion is at level 2. • TFC_CONGESTION_LEVEL_3—TFC congestion is at level 3. • • TFC_INTL_CONGESTION • UNKNOWN_REASON Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 14-11 OL-8723-19...

  • Page 586: Trunk Termination Reason Responses, Signaling System 7 Only

    – Signaling link is faulty. – dpc congestion – SIGNALLING-FAULT-This is set to indicate that the BTS 10200 processed a • DES_LOC_SIG—SS7 signaling fault. DES_LOC_FORCE—Local hardware failure. • DES_LOC_MML—MMLQ—This is set when a control command is issued with mode=graceful •...
  • Page 587 REMOTE_FORCE—Trunk is blocked remotely because of a hardware failure on the remote switch. • RESERVE_SPARE1—Reserved for future use. • RESERVE_SPARE2—Reserved for future use. • TERM_GRACE—Trunk is gracefully blocked because of an RSIP from the MGW. • Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 14-13 OL-8723-19...

  • Page 588: Fault Reason Responses

    Incompatible protocol version. • Internal hardware failure. • CAS signaling protocol error. • Failure of a group of trunks. • Unsupported values on local connection options. • Response too big. • Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 14-14 OL-8723-19...

  • Page 589: Protocol Troubleshooting

    This section describes tools and procedures for troubleshooting SIGTRAN problems on the BTS 10200 and Cisco ITP. It also describes how to clear SIGTRAN related BTS 10200 alarms. In the descriptions within, a series of steps may be required to determine the source of the problem and may include viewing other alarms, invoking command-line interface (CLI) status and control commands, viewing the BTS 10200 logs, and invoking ITP control and status requests.
  • Page 590 To put the linkset back in service, type the following command: va-2651-33(config-cs7-ls)#no shut *May 19 12:33:47.704: %CS7MTP3-5-ACTDEACTLINKSET: Linkset lset1 activation is in progress *May 19 12:33:47.704: %CS7MTP3-5-ACTDEACTLINK: Link 0 linkset lset1 activation is in progress Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 14-16 OL-8723-19...

  • Page 591: Using Bts 10200 Command Line Interface Commands

    To clear an alarm, enter the following command: clear alarm id=<alarm id> For a detailed description of the CLI commands that are used, please see the BTS 10200 Command Line Interface Reference Guide, Release 4.5, at the following universal resource locator (URL): http://www.cisco.com/univercd/cc/td/doc/product/voice/bts10200/bts4_5/cli/index.htm...

  • Page 592: Viewing Bts 10200 Logs

    Viewing BTS 10200 logs is helpful when debugging MTP3 user adaptation (M3UA) related objects of the BTS 10200. Specific string patterns are printed out by the M3UA Interface Module and are useful to determine what is occurring in the log. These strings are formatted as follows: MIM <functional area>...
  • Page 593 Protocol Troubleshooting Table Configuration Problems The CLI query command with the table-info option displays the tables used for routing the external SS7 queries on the BTS 10200. The query command can identify the following problems: Missing Call Agent (CA)-CONFIG table •...

  • Page 594: Control Part Problems

    No Translation for this Specific Address Layer SCCP Version ITU88, ITU92, ITU96, ANSI88, ANSI92 Location Cause The GTT entry is not provisioned correctly in the STP. Solution Add the GTT entry in the STP. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 14-20 OL-8723-19...
  • Page 595 Local, STP, or SCP Cause The Broadband Telephony Softswitch (BTS)-ITP sctp-association is down or the SS7 link, linkset, or route is down. Solution Chapter 13, “Network Troubleshooting,” section assistance in solving this problem. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 14-21 OL-8723-19...
  • Page 596 The service provider of the SS7 network needs to either provide higher capacity or re-engineer the traffic. SCTP layer congestion normally indicates insufficient central processing unit (CPU) power. Hardware needs to be upgraded or more BTS 10200 need to be added to offload traffic.
  • Page 597 Segmentation Not Supported Layer SCCP Version ITU96 Location Cause The peer side is not capable of reassembling XUDTS packets. Solution The ITP does not support segmentation and reassembly. Contact the Cisco TAC for assistance. Segmentation Failure Layer SCCP Version ITU96 Location Cause The segmentation failed.

  • Page 598: Troubleshooting H.323 Problems

    Status • Outgoing H.323 Calls Routed to Incorrect Endpoint When Using Direct Signaling • Registration, Admissions, and Status Still Used When Outgoing H.323 Call is Provisioned to Use Direct Signaling Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 14-24 OL-8723-19...

  • Page 599: Outgoing Trunk Group Is Out Of Service

    H323 VERSION -> 4 TIME TO LIVE -> 0 NUM ALT GATEKEEPERS -> 0 ALT GATEKEEPER PERMANENT -> FALSE THRESHOLD ENABLED -> FALSE OUT OF RESOURCES -> FALSE ALT GATEKEEPER LIST -> Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 14-25 OL-8723-19...

  • Page 600: H.323 Gateway Fails To Register With Gatekeeper (Invalid Alias)

    (RRQ) message from gateway. Currently, this configuration is supported on Integrated Operating System (IOS) gateways (not in use on BTS 10200) when Foreign Exchange Station (FXS) ports are involved. If an request rejected (RRJ) message is received by gateway with reject reason of “invalidAlias”, this is symptomatic of an alias list being provided to the gatekeeper...

  • Page 601: Admissions, And Status

    TIME TO LIVE -> 0 NUM ALT GATEKEEPERS -> 0 ALT GATEKEEPER PERMANENT -> TRUE THRESHOLD ENABLED -> FALSE OUT OF RESOURCES -> FALSE ALT GATEKEEPER LIST -> CLI>status h323_gw id=CHINA_3; Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 14-27 OL-8723-19...

  • Page 602: Stable Calls Are Dropped When Call Agent Switches Over

    Stable Calls Are Dropped When Call Agent Switches Over If Annex E functionality is provisioned on the BTS 10200, but stable calls are being dropped when the H.323 process restarts or CA switches over, check to see whether configuration is correctly registered...

  • Page 603: Configuration At Softswitch Or Gatekeeper Has Placed Routing Into A Loop

    “alarm=99 reason=<Loop detected!!> call cleared for callid=1 39 “ [h3a_alarms.c:281] Solution The routing problem could be in either the gatekeeper or the BTS 10200. Check the gatekeeper against the dialedDigits pattern in the admission request (ARQ), example: destinationInfo “ H3A3 .

  • Page 604: Outgoing H.323 Calls Routed To Incorrect Endpoint When Using Direct Signaling

    DIRECTION=BOTH SEL_POLICY=ASC GLARE=SLAVE ALT_ROUTE_ON_CONG=N SIGNAL_PORTED_NUMBER=N DIAL_PLAN_ID=cdp1 DEL_DIGITS=0 OPER_STATUS=NF Solution If the value for the SOFTSW_TSAP_ADDR is incorrect, use CLI to make the change as follows: CLI> change trunk_grp id=8991; softsw_tsap_addr=10.89.227.219; Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 14-30 OL-8723-19...

  • Page 605: Registration, Admissions, And Status Still Used When Outgoing H.323 Call Is Provisioned To Use Direct Signaling

    Use CLI to change the outgoing trunk group as follows: CLI> change trunk_grp id=8991; softsw_tsap_addr=10.89.227.219; Troubleshooting Integrated Services Digital Network Problems This section describes ISDN troubleshooting and maintenance for the BTS 10200. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 14-31...

  • Page 606: How To Troubleshoot When The Integrated Services Digital Network Trunk Group Fails To Restore

    This means the administrative state was set to in-service, but the command to go to operational state was ignored due to bad provisioning. Things to Check: Make sure that entries exist for this trunk group in the ISDN D Channel table. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 14-32 OL-8723-19...
  • Page 607 (DNS) names, or network connectivity. These values are all provisioned in the Reliable User Datagram Protocol (RUDP) Backhaul Session table in the Call Agent. For Cisco IOS gateways, these values are part of the session group groupn..
  • Page 608 0, 1, 2, or 3. This is a decimal value. The top 16 bits are the slot and the bottom 16 bits are the port. Trunk group states for NFAS: ISDN_DCHAN_STATE_WAIT/ISDN_DCHAN_STATE_MB. Step 4 This means the states at the far end are sending a SERVICE_ACK to the BTS 10200 service message for primary rate interface (PRI). Things to Check: Make sure the far end is sending a SERVICE_ACK.

  • Page 609: Checking The Status Of A Trunk Termination

    If the trunk static state is set to TERM_STATUS_FAULTY, go to the “Termination Status Is Faulty” section. If the trunk static state returns Cannot Make Call, go to the “Cannot Make a Call” section. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 14-35 OL-8723-19...
  • Page 610 Clear any termination faults at the gateway by turning off, then turning on, Media Gateway Control Protocol (MGCP) (use the mgcp, no mgcp procedure on the media gateway). Clear any TERM_FAULT on the BTS 10200. Trunks must be in active or idle mode and ready for use.
  • Page 611 Verify that the initialization procedure (ISDN-FAREND-Initialize (INIT) token), as depicted by Step 1 associated isdn-tg-profile in the BTS 10200, and as used by the PBX, is in sync. Using the CLI command “control trunk-termination” to reset the RBLK state, perform a control Step 2 trunk-termination to OOS, then control trunk-termination to INS—in case there is an error on the PBX...

  • Page 612: Checking Media Gateway Provisioning

    General Troubleshooting Protocol Troubleshooting Checking Media Gateway Provisioning The following example shows how a Cisco IOS gateway is provisioned. The typical problem areas are in bold italic type. Look at the problem area after the Call Agent Note is provisioned.
  • Page 613 1.0 mgcp dtmf-relay voip codec all mode nte-gw mgcp package-capability rtp-package mgcp default-package dt-package no mgcp timer receive-rtcp mgcp profile default timeout tsmax 100 max2 retries 3 dial-peer cor custom Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 14-39 OL-8723-19...
  • Page 614 General Troubleshooting Protocol Troubleshooting dial-peer voice 1 pots application mgcpapp port 1:23 line con 0 line aux 0 line 2 3 line vty 0 4 password xxxxxxxx login ntp server 10.89.227.254 Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 14-40 OL-8723-19...

  • Page 615: Additional Command Line Interface Verification

    CIC STATIC STATE -ACTV CIC DYNAMIC STATE -IDLE status trunk-termination tgn-id=17; cic=23 REPLY=CONFIGURATION COMMAND EXECUTED ISDN_TRUNK_GROUP -17 -CIC -23 TERM ADMINstatus -ADMIN_INS TERM OPERstatus -TERM_STATE_IDLE CIC STATIC STATE -ACTV CIC DYNAMIC STATE -IDLE Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 14-41 OL-8723-19...

  • Page 616: Maintenance Of A Call Agent Connected To An Integrated Services Digital Network Trunk Group

    ISDN D channel is temporarily down. However, the D channel comes back up, and the ISDN trunk group automatically returns to INS, when the switchover completes. This switchover process does not have any impact on stable calls. Note Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 14-42 OL-8723-19...

  • Page 617: File Configuration–Bts.properties

    This section provides instructions for editing and configuring the bts.properties file. The default content of the /opt/ems/etc/bts.properties file is in listed in Table 14-1. Modification of the bts.properties file should not be attempted without Cisco TAC support or Note supervision. Table 14-1 Default Content of the bts.properties File...

  • Page 618: Editing–Bts.properties

    This section lists several privacy screening troubleshooting symptoms and solutions. Symptom One With a Cisco 2421, calls are placed, but PRIVACY SCREENING is not displayed on the caller-id display for the subscriber. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x...

  • Page 619: Solution One

    Chapter 14 General Troubleshooting Privacy Screening Troubleshooting Solution One Telnet to the Cisco 2421 and set dtmf-relay mode to nse. For example, execute the following command in config mode: mgcp dtmf-relay voip codec all mode nse Symptom Two The caller or the subscriber is on a Cisco ATA MGW and CRCX/MGCX is failing.

  • Page 620: Call Agent Controlled Mode For Rfc 2833 Dtmf Relay Troubleshooting

    Symptom: DTMF tones do not go through. Diagnosis: Determine whether the RFC 2833 payload configured on the H.323 gateway or endpoint matches the payload configured on the Cisco BTS 10200 Softswitch. Resolution: Ensure that the value of rfc2833-payload in the applicable h323-tg-profile or h323-term-profile table is set to the same value as that on the H.323 gateway or endpoint.

  • Page 621: General Troubleshooting Information

    Call Agent (CA) log files are located in /opt/OptiCall/CA[XYZ]/bin/logs directory, where XYZ is the CA instance (for example CA146). If you need to call Cisco TAC regarding a call-processing issue, first collect the log files from this directory if possible.

  • Page 622: Troubleshooting Qos

    Troubleshooting Audit Connection Problem: Stray connections have not been removed after failover. Symptoms: Endpoint(s) unable to place feature calls, dropped active calls after a Cisco BTS 10200 Softswitch failover. Diagnosis: Place a call through the endpoint. Use network packet analysis software to observe any negative CreateConnection (CRCX) ACK responses from the MGCP device.

  • Page 623: Multi-Lingual Support Troubleshooting

    Ensure the IVR script points to the correct MS and that the MLS has an FNAME: btsadmin>show ivr_script_profile FNAME=MLS IVR_ACCESS_MODE=IVR IVR_ROUTE_GUIDE_ID=10013 IVR_SCRIPT_PKG_TYPE=BAU Ensure the annc-tg-profile table is correct: ANNC_LANG_FORMAT_SUPPORTED=N for IPUnity ANNC_LANG_FORMAT_SUPPORTED=Y for Cognitronics Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 14-49 OL-8723-19...

  • Page 624: Viewing Trace Logs For Throttled Flood Of Mgcp Messages From Specific Endpoint

    The Cisco BTS 10200 Softswitch Core File Monitor feature provides Cisco BTS 10200 Softswitch customers with an alarm notification whenever a core file is generated on a Cisco BTS 10200 Softswitch platform system. The Cisco BTS 10200 Softswitch Core File Monitor feature also removes core files automatically when disk space is critically low or when the core file has aged beyond a maximum allowable time.

  • Page 625: Planning

    General Troubleshooting Platform Core File Alarm The Cisco BTS 10200 Softswitch Core File Monitor enhancement is driven by the problem that core files are huge (2–4 GB) and eventually cause a disk full condition resulting in a switchover. In the field, operators rely on a process crash alarm to alert them that a core file is present.
  • Page 626 If set to true, the oldest core files are deleted when free file space is low. Default is true. For details on troubleshooting the “Core File Present” condition, refer to Core File Present—Audit (25), page 2-22. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 14-52 OL-8723-19...

  • Page 627: Introduction

    • Call Tracer (CTRAC), page 15-103 • Tabular Display of Events and Alarms, page 15-106 Pre-Manual Switchover Switch Integrity Diagnostic Utility, page 15-107 • PSTN Trunk Testing, page 15-113 • Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-1 OL-8723-19...

  • Page 628: Chapter 15 Diagnostic Test

    Media Gateway Tests The use of the UNIX ifconfig down command on any signaling interface to test or troubleshoot network Caution or interface failures of the Cisco BTS 10200 Softswitch Signaling Interface may lead to undesirable consequences or conditions. Media Gateway Tests This section describes the tests that can be performed on media gateways.
  • Page 629 INITIAL STATE -> ADMIN_MAINT REQUEST STATE -> ADMIN_INS RESULT STATE -> ADMIN_INS FAIL REASON -> ADM found no failure REASON -> ADM executed successful RESULT -> ADM configure result in success Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-3 OL-8723-19...

  • Page 630: Subscriber Termination Tests

    Test #3 tests if the subscriber can be rung. The Ring parameter must be specified in seconds for this test. The default is 5 seconds. Test #4 performs tests 1 through 3. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-4 OL-8723-19...
  • Page 631 Ring-duration values are 0–999 (Default = 5). Maximum ring time is 30 seconds regardless of whether Note the duration is set higher than or equal to 31. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-5 OL-8723-19...

  • Page 632: Signaling System 7 Trunk Termination Tests

    Test #5 tests to ensure that each end of the circuit has sufficient and consistent information for using the circuit in call connections. Common language location identifier (CLLI) names are included. Test #6 tests to ensure the CIC connections. Test #0 performs tests 1 through 6. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-6 OL-8723-19...
  • Page 633 TEST TYPE -> ADM running SS7 circuit query message test TEST DURATION -> 0 RESULT -> ADM ran test successfully REASON -> CQM test pass CIC COUNT -> 24 CIC STATES -> Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-7 OL-8723-19...
  • Page 634 TEST DURATION -> 0 RESULT -> ADM ran test successfully REASON -> CVT test pass CLLI -> DALLTXRCDN5 Force the SS7 trunk termination into INS state: Step 4 control ss7-trunk-termination tgn-id=103; mode=forced; target-state=ins; Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-8 OL-8723-19...
  • Page 635 Remotely and Locally Hardware Blocked CS_HW_BOTHBLOC_LOCBLOC Remotely and Locally Hardware and Locally Maintenance Blocked CS_HW_BOTHBLOC_REMBLOC Remotely and Locally Hardware and Remotely Maintenance Blocked CS_HW_BOTHBLOC_BOTHBLOC Remotely and Locally Hardware and Remotely and Locally Maintenance Blocked Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-9 OL-8723-19...

  • Page 636: Integrated Services Digital Network Trunk Termination Tests

    RESULT -> TEST-SUCCESS REASON -> PASSED: Reason: AUEP-NACK received with RespCode = 510 Reply: Diagnostic command executed. Force the ISDN trunk termination into MAINT state: Step 4 control isdn-trunk-termination tgn-id=17; mode=forced; target-state=maint; Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-10 OL-8723-19...

  • Page 637: Channel-Associated Signaling Trunk Termination Tests

    REASON -> PASS successfully. Reply: Diagnostic command executed. diag cas-trunk-termination tgn-id=64;cic=1;test=3; Reply Example: TRUNK DIAGNOSTIC TEST EXECUTED -> diag trunk TG-NUM -> 64 CIC -> 1 TEST-TYPE -> ADM-MGW-MGCP-CONNECTIVITY-TEST TEST-DURATION -> 11 Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-11 OL-8723-19...
  • Page 638 Note On some Cisco voice gateways ringback tone may be played when the subscriber line is idle. If the router statement "voice call-sendalert" is added to the run file the ringback tone is not be played.

  • Page 639: Announcement Trunk Termination Tests

    Test #1 tests if MGCP has access to the announcements module (ANC) termination. Note Test #2, tests if there is a path to the device (ping). Test #3 performs tests 1 and 2. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-13 OL-8723-19...
  • Page 640 TEST-TYPE -> ADM-TERM-CONNECTION-TEST TEST-DURATION -> 33 RESULT -> TEST-SUCCESS REASON -> PASS successfully. Reply: Diagnostic command executed. Force the Announcement trunk termination into INS state: Step 4 control annc-trunk-termination tgn-id=13; mode=forced; target-state=ins; Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-14 OL-8723-19...

  • Page 641: Troubleshooting Using Snoop

    Troubleshooting Using Snoop Caution Snoop should NOT be used on the BTS 10200 call agent itself in a Production Network. It can cause performance degradation. Snoop can be used on the BTS 10200 call agent during test and turn-up phase during very low call volume periods.
  • Page 642 Session Initiation Protocol (SIP) example: 10.0.0.1 is a SIP Phone. The goal is to monitor the SIP traffic between the BTS 10200 and the SIP phone. # snoop -d qfe0 -x 42 host 10.0.0.1 and port 5060 and udp &...
  • Page 643 Troubleshooting Using Snoop SCTP/SUA/TCAP example 1: 10.0.0.1 is a Signaling Gateway acting as an SUA peer with the BTS 10200. The goal is to capture all 800/local number portability (LNP) queries. Follow the same syntax as for the M3UA case, except find which port SUA communicates with the SG for Advanced Intelligent Network (AIN) features: CLI>show sctp-assoc platform-id=FSAIN205...
  • Page 644 # snoop -d qfe0 -o h323.cap host 10.0.0.1 and port 1720 or host 10.0.0.129 and port 1719 Use Control-C to stop the packet capture. Open the file in Ethereal and inspect. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-18 OL-8723-19...

  • Page 645: Query Verification Tool And Translation Verification Tool

    COPs example: 10.0.0.1 is a cable modem termination system (CMTS) and is configured as an aggregation identification (AGGR-ID) in the BTS 10200. The goal is to monitor all Common Open Policy Service Protocol (COPS) messaging to and from the CMTS.

  • Page 646: Query Verification Tool

    Origination Point Code ID * Calling-DN The caller’s directory number. Table-Info Specifies whether or not you want to see the tables accessed when processing the query. Y/N; default=N Examples query toll-free Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-20 OL-8723-19...

  • Page 647: Response Format

    Specifies whether or not you want to see the tables accessed when processing the query. Y/N; default=N Response Format The system response to a query is in the following format: Reply: <success|failure>; parameter=value; Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-21 OL-8723-19...

  • Page 648: Query Errors

    The following additional parameters are returned in response to a query LNP command: Original Number • Translated Number • Query Errors An error can occur when a query command fails. This section specifies error responses and possible resolutions for problems. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-22 OL-8723-19...
  • Page 649 QUERYSTATUS -> Miscellaneous Failure Reply : Success: CLI> There is no response from the SCP. Contact the SCP provider to find out why there is no error response returned from the SCP. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-23 OL-8723-19...
  • Page 650 Reissue the command in the AIN 0.1 format. To see what message type is specified for the Toll-Free subs system, enter the following command: CLI> query toll-free-msg-type; opc-id=opc; MESSAGE-TYPE=AIN01 Reply : Success: CLI> Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-24 OL-8723-19...
  • Page 651 To resolve this error, enter a provisioned local access and transport area (LATA). Local Network Failure When communication is lost between the BTS 10200 and the IP transfer point (ITP) gateway, a local network failure may occur. The most likely reason for this error is that the SCTP association is Out Of Service.

  • Page 652: Query Verification Tool Measurements

    LIDB query from the QVT tool. TOOLS_LIDB_QUERY_SUCC The total number of times the reporting feature server received a request to perform an LIDB query from the QVT tool and completed it successfully. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-26 OL-8723-19...

  • Page 653: Translation Verification Tool

    Syntax Description * Calling-DN The caller’s directory number. VARCHAR(10): 10 digits in the format npaxxxxxxx. Called-DN Examples translate trunk tgn-id= 1; called-dn=7034321234; Syntax Description * Called-DN * Tgn-ID Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-27 OL-8723-19...

  • Page 654: Response Format

    ID=northtexas;DIAL_PLAN_ID=dp1;LOCAL_PFX1_OPT=NR;TOLL_PFX1_OPT=RQ;POP_ID=1;OLI=0;EA_USE_PI C1=Y; TABLE: DIAL_PLAN_PROFILE ID=dp1;DESCRIPTION=dialingplanprofile;NANP_DIAL_PLAN=Y;DNIS_DIGMAN_ID=dp1; TABLE: DIAL_PLAN ID=dp1;DIGIT_STRING=408555;DEST_ID=ssp1dest;SPLIT_NPA=NONE;DEL_DIGITS=0;MIN_DIGITS=10;MAX_ DIGITS=10;NOA=NATIONAL; TABLE: DESTINATION DEST_ID=ssp1dest;CALL_TYPE=LOCAL;ROUTE_TYPE=ROUTE;ROUTE_GUIDE_ID=ssp1rg;ZERO_PLUS=N;INTRA_ STATE=Y;GAP_ROUTING=N;CLDPTY_CTRL_REL_ALWD=N;TABLE: ROUTE_GUIDE ID=ssp1rg;POLICY_TYPE=ROUTE;POLICY_ID=ssp1route; TABLE: ROUTE ID=ssp1route;TGN1_ID=1;DEL_DIGITS1=0;DEL_DIGITS2=0;DEL_DIGITS3=0;DEL_DIGITS4=0;DEL_DIGITS5 =0;DEL_DIGITS6=0;DEL_DIGITS7=0;DEL_DIGITS8=0;DEL_DIGITS9=0;DEL_DIGITS10=0;TG_SELECTION=RR; TABLE: TRUNK_GRP ID=1;CALL_AGENT_ID=CA146;TG_TYPE=SS7;NUM_OF_TRUNKS=24;DPC=1-12-1;TG_PROFILE_ID=ssp1-tg-pro f;STATUS=INS;DIRECTION=BOTH;SEL_POLICY=ASC;GLARE=EVEN;ALT_ROUTE_ON_CONG=N;SIGNAL_PORTED_NU MBER=N;POP_ID=1;REMOTE_SWITCH_LRN=2122129999;DIAL_PLAN_ID=dp19;DESCRIPTION=TG to BTS12;DEL_DIGITS=0;OPER_STATUS=NF;TRAFFIC_TYPE=TANDEM;ANI_BASED_ROUTING=N;CLLI=DAL177DS3;C ALL_CTRL_ROUTE_ID=bts12-ccroute1;MGCP_PKG_TYPE=T;ANI_SCREENING=N;SEND_RDN_AS_CPN=N; Reply :Success: CLI> Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-28 OL-8723-19...

  • Page 655: Translation Verification Tool Measurements

    Toll Free query from the QVT tool. TOOLS_TOLLFREE_QUERY_SUCC The total number of times the reporting feature server received a request to perform a Toll Free query from the QVT tool and completed it successfully. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-29 OL-8723-19...

  • Page 656: Using Query Verification Tool And Translation Verification Tool Together

    CLI> query toll-free called-dn=8002553002; calling-dn=9722331286; lata=100; opc-id=opc; TOLL FREE QUERY ON FEATURE SERVER FSAIN520 IS...-> RESULT-> OPC=7-2-1 SSN=254 TT-254 SCP-Point-Code=1-101-0 Message-Type=IN/1 Called Number=8002553002 Translated Number=7034323002 Carrier=0000 Reply : Success: CLI> Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-30 OL-8723-19...
  • Page 657 ID=dp1;DESCRIPTION=dialing plan profile ID 1;NANP_DIAL_PLAN=Y;DNIS_DIGMAN_ID=dp_svc; TABLE: DIAL_PLAN ID=dp1;DIGIT_STRING=703432;DEST_ID=ssp1-dest;SPLIT_NPA=NONE;DEL_DIGITS=0;MIN_DIGITS=7;MAX_ DIGITS=10;NOA=NATIONAL; TABLE: DESTINATION DEST_ID=ssp1-dest;CALL_TYPE=LOCAL;ROUTE_TYPE=ROUTE;ROUTE_GUIDE_ID=ssp1-rg;ZERO_PLUS=N;INTR A_STATE=Y;GAP_ROUTING=N;CLDPTY_CTRL_REL_ALWD=N; TABLE: ROUTE_GUIDE ID=ssp1-rg;POLICY_TYPE=ROUTE;POLICY_ID=ssp1-route; TABLE: ROUTE ID=ssp1-route;TGN1_ID=3;DEL_DIGITS1=0;DEL_DIGITS2=0;DEL_DIGITS3=0;DEL_DIGITS4=0;DEL_DIGITS 5=0;DEL_DIGITS6=0;DEL_DIGITS7=0;DEL_DIGITS8=0;DEL_DIGITS9=0;DEL_DIGITS10=0;TG_SELECTION=RR TABLE: TRUNK_GRP ID=3;CALL_AGENT_ID=CA146;TG_TYPE=SS7;NUM_OF_TRUNKS=24;DPC=1-12-1;TG_PROFILE_ID=ssp1-tg-pro f;STATUS=INS;DIRECTION=BOTH;SEL_POLICY=ASC;GLARE=EVEN;ALT_ROUTE_ON_CONG=N;SIGNAL_PORTED_NU MBER=N;POP_ID=1;REMOTE_SWITCH_LRN=2122129999;DIAL_PLAN_ID=dp19;DESCRIPTION=TG to BTS12;DEL_DIGITS=0;OPER_STATUS=NF;TRAFFIC_TYPE=TANDEM;ANI_BASED_ROUTING=N;CLLI=DAL177DS3;C ALL_CTRL_ROUTE_ID=bts12-ccroute1;MGCP_PKG_TYPE=T;ANI_SCREENING=N;SEND_RDN_AS_CPN=N; Reply : Success: CLI> Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-31 OL-8723-19...

  • Page 658: Lnp Examples

    DIGIT_STRING=11501;OFFICE_CODE_INDEX=15;DID=N;CALL_AGENT_ID=CA146;DIALAB LE=Y;NDC=1;EC=150;DN_GROUP=1xxx;EC_DIGIT_STRING=1150; TABLE: DN2SUBSCRIBER OFFICE_CODE_INDEX=15;DN=1160;STATUS=PORTED_OUT;RING_TYPE=1;LNP_TRIGGER=N ;NP_RESERVED=N;LAST_CHANGED=2005-08-11 14:30:09.0;VIRTUAL_DN=N;PORTED_IN=N; ****** THIS CALL NEEDS AN LNP QUERY ****** ****** LNP QUERY is needed (Onward Call Routing query), Suggested QUERY Command to Run ****** Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-32 OL-8723-19...
  • Page 659 TRANSLATE ON CALL AGENT CA146 IS... -> TABLEINFO -> TABLE: TRUNK_GRP ID=inet116_rg1;POLICY_TYPE=ROUTE;POLICY_ID=inet116_rte; TABLE: ROUTE ID=inet116_rte;TGN1_ID=6;DEL_DIGITS1=0;DEL_DIGITS2=0;DEL_DIGITS3=0;DEL_D IGITS4=0;DEL_DIGITS5=0;DEL_DIGITS6=0;DEL_DIGITS7=0;DEL_DIGITS8=0;DEL_DIG ITS9=0;DEL_DIGITS10=0;TG_SELECTION=SEQ;NEXT_ACTION=NONE; TABLE: TRUNK_GRP ID=6;CALL_AGENT_ID=CA146;TG_TYPE=SS7;NUM_OF_TRUNKS=24;DPC=5-2-4;TG_PROFI LE_ID=tgprof_inet116;STATUS=INS;DIRECTION=OUT;SEL_POLICY=DSC;GLARE=SLAVE ;ALT_ROUTE_ON_CONG=N;SIGNAL_PORTED_NUMBER=Y;POP_ID=hun1;DIAL_PLAN_ID=dp_ trk_itu;DESCRIPTION=TG OUT to Inet 116;DEL_DIGITS=0;TRAFFIC_TYPE=LOCAL;ANI_BASED_ROUTING=N;CALL_CTRL_ROUTE_ ID=cc_rte_i116_tg6;MGCP_PKG_TYPE=T;ANI_SCREENING=N;SEND_RDN_AS_CPN=N;STA TUS_MONITORING=N;SEND_EARLY_BKWD_MSG=N;EARLY_BKWD_MSG_TMR=5;SCRIPT_SUPP= N;VOICE_LAYER1_USERINFO=AUTO;VOICE_INFO_TRANSFER_CAP=AUTO;ACCESS_TYPE=CO MBINED;POI=INTER_ENDOFFICE;PERFORM_LNP_QUERY=N; Reply : Success: Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-33 OL-8723-19...

  • Page 660: Example 2

    Reply : Success: btsadmin> btsadmin> btsadmin>QUERY LNP;calling-dn=11501511;called-dn=11501160 QUERY ON FEATURE SERVER FSAIN205 IS... -> RESULT -> Called Number=11501160, Routing Number (RN) =4101 **** Suggested TRANSLATE Command **** Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-34 OL-8723-19...
  • Page 661 TRANSLATE ON CALL AGENT CA146 IS... -> TABLEINFO -> TABLE: SUBSCRIBER ID=sipata1;CATEGORY=INDIVIDUAL;NAME=h15 sipata1 Moe;STATUS=ACTIVE;BILLING_DN=11501511;DN1=11501511;PRIVACY=NONE;RING_TYPE_DN1=1;PIC1=NONE; PIC2=NONE;PIC3=NONE;GRP=N;USAGE_SENS=Y;SUB_PROFILE_ID=hungary_prof;TERM_TYPE=SIP;IMMEDIATE _RELEASE=N;TERMINATING_IMMEDIATE_REL=N;AOR_ID=11501511@192.168.54.124;SEND_BDN_AS_CPN=N;SE ND_BDN_FOR_EMG=N;PORTED_IN=N;BILLING_TYPE=NONE;VMWI=Y;SDT_MWI=Y; TABLE: TRUNK_GRP ID=6;CALL_AGENT_ID=CA146;TG_TYPE=SS7;NUM_OF_TRUNKS=24;DPC=5-2-4;TG_PROFILE_ID=tgprof_inet1 16;STATUS=INS;DIRECTION=OUT;SEL_POLICY=DSC;GLARE=SLAVE;ALT_ROUTE_ON_CONG=N;SIGNAL_PORTED_N UMBER=Y;POP_ID=hun1;DIAL_PLAN_ID=dp_trk_itu;DESCRIPTION=TG OUT to Inet 116;DEL_DIGITS=0;TRAFFIC_TYPE=LOCAL;ANI_BASED_ROUTING=N;CALL_CTRL_ROUTE_ID=cc_rte_i116_tg6 ;MGCP_PKG_TYPE=T;ANI_SCREENING=N;SEND_RDN_AS_CPN=N;STATUS_MONITORING=N;SEND_EARLY_BKWD_MSG =N;EARLY_BKWD_MSG_TMR=5;SCRIPT_SUPP=N;VOICE_LAYER1_USERINFO=AUTO;VOICE_INFO_TRANSFER_CAP=A UTO;ACCESS_TYPE=COMBINED;POI=INTER_ENDOFFICE;PERFORM_LNP_QUERY=N; Reply : Success: btsadmin> Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-35 OL-8723-19...

  • Page 662: Example 3

    QUERY LNP;calling-dn=11501511;called-dn=11501512 ****** If query result is Routing Number (RN) Not Found, the above translation is valid ****** Otherwise, use the TRANSLATE command suggested by the query result Reply : Success: Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-36 OL-8723-19...
  • Page 663 Query Verification Tool and Translation Verification Tool btsadmin> btsadmin>QUERY LNP;calling-dn=11501511;called-dn=11501512 QUERY ON FEATURE SERVER FSAIN205 IS... -> RESULT -> Called Number=11501512, Routing Number (RN) Not Found QUERYSTATUS -> Query Success Reply : Success: Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-37 OL-8723-19...

  • Page 664: Example 4

    Reply : Success: btsadmin> btsadmin> btsadmin> btsadmin> btsadmin>query LNP; calling-dn=11501511; called-dn=11161168; QUERY ON FEATURE SERVER FSAIN205 IS... -> RESULT -> Called Number=11161168, Routing Number (RN) =4001 **** Suggested TRANSLATE Command **** Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-38 OL-8723-19...
  • Page 665 TRANSLATE ON CALL AGENT CA146 IS... -> TABLEINFO -> TABLE: SUBSCRIBER ID=sipata1;CATEGORY=INDIVIDUAL;NAME=h15 sipata1 Moe;STATUS=ACTIVE;BILLING_DN=11501511;DN1=11501511;PRIVACY=NONE;RING_TYPE_DN1=1;PIC1=NONE; PIC2=NONE;PIC3=NONE;GRP=N;USAGE_SENS=Y;SUB_PROFILE_ID=hungary_prof;TERM_TYPE=SIP;IMMEDIATE _RELEASE=N;TERMINATING_IMMEDIATE_REL=N;AOR_ID=11501511@192.168.54.124;SEND_BDN_AS_CPN=N;SE ND_BDN_FOR_EMG=N;PORTED_IN=N;BILLING_TYPE=NONE;VMWI=Y;SDT_MWI=Y; TABLE: SUBSCRIBER_PROFILE ID=hungary_prof;DIAL_PLAN_ID=dp_sub_itu;LOCAL_PFX1_OPT=NR;TOLL_PFX1_OPT=RQ;POP_ID=hun1;OLI =0;EA_USE_PIC1=Y;INTERLATA_PFX1_OPT=RQ; TABLE: TRUNK_GRP ID=6;CALL_AGENT_ID=CA146;TG_TYPE=SS7;NUM_OF_TRUNKS=24;DPC=5-2-4;TG_PROFILE_ID=tgprof_inet1 16;STATUS=INS;DIRECTION=OUT;SEL_POLICY=DSC;GLARE=SLAVE;ALT_ROUTE_ON_CONG=N;SIGNAL_PORTED_N UMBER=Y;POP_ID=hun1;DIAL_PLAN_ID=dp_trk_itu;DESCRIPTION=TG OUT to Inet 116;DEL_DIGITS=0;TRAFFIC_TYPE=LOCAL;ANI_BASED_ROUTING=N;CALL_CTRL_ROUTE_ID=cc_rte_i116_tg6 ;MGCP_PKG_TYPE=T;ANI_SCREENING=N;SEND_RDN_AS_CPN=N;STATUS_MONITORING=N;SEND_EARLY_BKWD_MSG =N;EARLY_BKWD_MSG_TMR=5;SCRIPT_SUPP=N;VOICE_LAYER1_USERINFO=AUTO;VOICE_INFO_TRANSFER_CAP=A UTO;ACCESS_TYPE=COMBINED;POI=INTER_ENDOFFICE;PERFORM_LNP_QUERY=N; Reply : Success: Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-39 OL-8723-19...

  • Page 666: Example 5

    ID=dp_trk_itu;DESCRIPTION=Trunk Origination Local dial-plan (ITU);NANP_DIAL_PLAN=N;ANI_DIGMAN_ID=dm_dpp_ani_itu;DNIS_DIGMAN_ID=dm_dpp_trk_itu;OVERDECA DIC_DIGITS_SUPP=N;NOA_BASED_ROUTING=Y;NOA_ROUTE_PROFILE_ID=noa_rt; TABLE: DIGMAN ID=dm_dpp_ani_itu;RULE=1;MATCH_NOA=ANY;REPLACE_NOA=NATIONAL; TABLE: DIGMAN ID=dm_dpp_trk_itu;RULE=1;MATCH_STRING=^4001;REPLACE_STRING=NONE;MATCH_NOA=PORTED_NUMBER_WI TH_RN;REPLACE_NOA=UNKNOWN; TABLE: NOA_ROUTE_PROFILE ID=noa_rt;DESCRIPTION=NOA Route profile (ITU) to RN dial-plan; CONTINUE WITH EXISTING DIAL-PLAN TABLE: DIAL_PLAN ID=dp_trk_itu;DIGIT_STRING=1150;DEST_ID=dest_sub_itu;SPLIT_NPA=NONE;DEL_DIGITS=0;MIN_DIGIT S=8;MAX_DIGITS=8;NOA=UNKNOWN; Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-40 OL-8723-19...

  • Page 667: Network Loopback Test For Network-Based Call Signaling/Media Gateway Control Protocol Endpoints

    TDM bearer path test call feature. This section contains the following: Overview • Restrictions • Installing • • Configuring • Using/Operating the Network Loopback Test for Network-based Call Signaling/Media Gateway Control Protocol Endpoints Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-41 OL-8723-19...

  • Page 668: Overview

    BTS 10200 will provide preference to regular calls over any test calls. In the service affected mode the BTS 10200 will not try to perform other calls, even if the test MTA/TGW has capability to perform multiple connections (PARALLEL-TEST-CONN-SUPP=Y).

  • Page 669: Configuration Examples

    Note Most of these tables have additional tokens that are not included in the examples. For a complete list of all CLI tables and tokens, see the BTS 10200 Command Line Interface Reference Guide. Global Configuration Example Use the following procedure as a global configuration example.
  • Page 670 Add termination. Step 5 add termination prefix=aaln/; port-start=1; port-end=2; type=TRUNK; mgw-id=c925.172; Add trunk. Step 6 add trunk termination-prefix=aaln/; termination-port-start=1; termination-port-end=2; cic-start=1; cic-end=2; tgn-id=100 Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-44 OL-8723-19...
  • Page 671 Add subscriber-profile. Step 10 add subscriber-profile id=subpf1; digit-map-id=test; dial-plan-id=DP1; POP-ID=1; Add subscriber. Step 11 add subscriber id=sub11; sub-profile-id= subpf1; category=individual; term-id=aaln/0; mgw-id=c925.172; dn1=919-392-1235; name=RTP5; Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-45 OL-8723-19...
  • Page 672 Step 6 add dial-plan id=dp1; digit-string=919-392; dest-id=sub; noa=national; Add subscriber-profile. Step 7 add subscriber-profile id=subpf1; dial-plan-id=dp1; pop-id=1; Step 8 Add subscriber. add subscriber id=sub11; sub-profile-id= subpf1; category=individual; term-id=aaln/0; mgw-id=c925.172; dn1=919-392-1235; name=RTP5; Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-46 OL-8723-19...
  • Page 673 Step 3 add dial-plan id=test; digit-string=151; dest-id=DEST_NLB_SUB; min-digits=13; max-digits=13 add dial-plan id=test; digit-string=152; dest-id=DEST_NCB_SUB; min-digits=13; max-digits=13 add dial-plan id=test; digit-string=153; dest-id=DEST_NLB_TRUNK; min-digits=13; max-digits=13 add dial-plan id=test; digit-string=154; dest-id=DEST_NCT_TRUNK; min-digits=13; max-digits=13 Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-47 OL-8723-19...

  • Page 674: Control Protocol Endpoints

    To use this feature, place a call from the testing device subscriber to any MGCP subscriber to be tested. For example, if the testing device is an MGCP telephone, dial the number of the subscriber to be tested. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-48...

  • Page 675: Dedicated Test Trunk Group

    In addition to dedicated test trunk groups, the BTS 10200 allows a shared test trunk group, where the category of the test to be run is specified by the test-prefix. BTS 10200 allows a test trunk group to be associated with a test dial plan. The test trunk group can be either the IP or CAS TDM trunks. Incoming calls from the network on these trunk groups will be analyzed according to a pre configured test dial plan.

  • Page 676: Configuring The Originating Trunk Group

    Configure the test dial plan destination with the exact type of test call. Step 4 Configure the main subscriber ID for testing trunk-grp. Step 5 Configure the digit map for collecting prefixed digits and associate it to the SUBSCRIBER-PROFILE Step 6 table. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-50 OL-8723-19...

  • Page 677: Session Initiation Protocol Subscriber Registration Status Check

    USER -> 4692551001 HOST -> 10.89.223.193 PORT -> 5060 USER TYPE -> USER_IP_TYPE EXPIRES -> 3600 EXPIRETIME -> Thu Oct 23 16:23:48 2003 STATUS -> REGISTERED CONTACT Reply : Success: Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-51 OL-8723-19...

  • Page 678: System Health Report

    CLI>show scheduled-command verb=report; noun=system-health To reschedule an SHR command for another time, change the recurrence, or change the collection period, use the following command: CLI>change scheduled-command id=NNN; <recurrence=DAILY>; <start-time=…>; <keys=period>; <values=…> Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-52 OL-8723-19...

  • Page 679: Fast Audit And Sync Tool

    The bts_sync tool is used to send the generated SQL statements to the appropriate destination to bring the databases into synchronization. The BTS 10200 Fast Audit and Sync Tools feature consists of two expect shell scripts that use other unix scripts and utilities to perform full-database and table audits of the databases on the various network elements of the system, and synchronize the mismatches found.

  • Page 680: Using The Bts_Sync Tool

    To troubleshoot database out of synchronization alarms, take the following steps: Log in the system at the unix root prompt. Step 1 Step 2 Execute the bts_audit command. Step 3 Once the audit is completed, execute the bts_sync command. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-54 OL-8723-19...

  • Page 681: Isdn Network Loopback Test

    Test calls are identified by provisioning the call-type and call-subtype tokens in the Destination table. The BTS 10200 cannot perform network loopback test calls that originate from another switch and does not route calls from a testing device on an H.323 or SIP interface.

  • Page 682: Originating Trunk Group

    The ISDN NLB feature uses a shared test trunk group, where the type of test is specified by the test-prefix. BTS 10200 allows a test trunk group to be associated with a test dial plan. The test trunk group is an ISDN PRI trunk. Incoming calls from the network on an ISDN PRI trunk are analyzed according to a preconfigured test dial plan.

  • Page 683: Sample Configurations

    These tasks include examples of CLI commands that illustrate how to provision the specific feature. Most of these tables have additional tokens that are not included in the examples. For a complete list of all CLI tables and tokens, see the BTS 10200 Command Line Interface Reference Guide.
  • Page 684 Take the subscriber under test off-hook. There is no dial tone. Call the subscriber under test from another subscriber. Call is treated, and the test call is still active. Hang up the test call and verify the Billing call type. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-58 OL-8723-19...
  • Page 685 Take the subscriber under test off-hook. There is a dial tone. Call the subscriber under test from another subscriber. Call is set up, and the test call is released. Hang up the test call and verify the Billing call type. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-59 OL-8723-19...
  • Page 686 Call the subscriber under test from another subscriber. Call is set up, and the test call is still active. Hang up the test call and verify the Billing call type. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-60 OL-8723-19...
  • Page 687 Call the subscriber under test from another subscriber. Call is set up, and the test call stays up. Verify the Billing call type. NCT Tests This section provides examples of line loopback network continuity tests (NCT) over ISDN. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-61 OL-8723-19...
  • Page 688 Take the subscriber under test off-hook. There is no dial tone. Call the subscriber under test from another subscriber. Call is treated, and the test call is still active. Hang up the test call and verify the Billing call type. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-62 OL-8723-19...
  • Page 689 Take the subscriber under test off-hook. There is a dial tone. Call the subscriber under test from another subscriber. Call is set up, and the test call is released. Hang up the test call and verify the Billing call type. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-63 OL-8723-19...
  • Page 690 Call the subscriber under test from another subscriber. Call is set up, and the test call is still active. Hang up the test call and verify the Billing call type. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-64 OL-8723-19...

  • Page 691: Trunk Loopback Tests Over An Isdn Trunk

    Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-65 OL-8723-19...
  • Page 692 Then: From the test equipment, dial the NTE NLB trunk test call (554+trunk digits+members) (trunk) Hang up the test call and verify the Billing call type. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-66 OL-8723-19...

  • Page 693: Enhanced Traffic Measurement

    FTP or SFTP interface. The measurement data can be provisioned and is accessible through the SNMP MIB. The supported version of SNMP on the Cisco BTS 10200 is v2c. There is detailed information on both of these access mechanisms available in separate operations manuals.

  • Page 694: Measurement Data Event Reports

    Chapter 15 Diagnostic Tests Enhanced Traffic Measurement Measurement Data Event Reports The measurement subsystem within the BTS 10200 supports several events that are issued in various abnormal scenarios. Table 15-5 illustrates the event reports that the measurements subsystem supports and their significance.

  • Page 695: Operating

    Cisco BTS 10200 system. Actual examples are provided with explanations to illustrate the operational mechanics. These and other commands are documented in the BTS 10200 Command Line Interface Reference Manual and the BTS 10200 Operations and Maintenance Guide.

  • Page 696: Provisioning Measurement Report Types

    15 minutes. Currently, there are 13 types of measurement data generated by the Cisco BTS 10200. The following list illustrates each of these categories of data: ISDN—ISDN signaling protocol related information...
  • Page 697 Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-71 OL-8723-19...
  • Page 698 Chapter 15 Diagnostic Tests Enhanced Traffic Measurement show measurement-prov type=tg-usg; show measurement-prov type=h323; show measurement-prov type=call-tools; show measurement-prov type=ain-tools; show measurement-prov type=pct-tools; Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-72 OL-8723-19...

  • Page 699: Measurement Report Summaries

    Enhanced Traffic Measurement Measurement Report Summaries The Cisco BTS 10200 system provides a command line interface (CLI) command to query summary reports of measurement data from the database on the Element Management System (EMS). This mechanism provides the ability to specify an interval and the particular type and source of data. The time interval specified must be prior to the current collection interval.
  • Page 700 12:00:00; call-agent-id= CA146; output=h323-report; output-type=csv; report measurement-call-tools-summary start-time=2002-03-27 10:00:00; end-time=2002-03-27 12:00:00; call-agent-id=CA146; output=call-tools-report; output-type=csv; report measurement-ain-tools-summary start-time=2002-03-27 10:00:00; end-time=2002-03-27 12:00:00; feature-server-id=AIN01; output=ain-tools-report; output-type=csv; report measurement-pct-tools-summary start-time=2002-03-27 10:00:00; end-time=2002-03-27 12:00:00; feature-server-id=PCT01; output=pct-tools-report; output-type=csv; Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-74 OL-8723-19...
  • Page 701 If you enter a value of "%", then a list of all possible column values are displayed, but the report itself is not created. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-75 OL-8723-19...
  • Page 702 This is an optional token that is only applicable to the following measurement types: tg-usage • isup • When used with the trunk measurement type, it results in all trunks within the trunk group being reported. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-76 OL-8723-19...
  • Page 703 This is an optional token that is only applicable to the following measurement type: • sctp aggr-id The aggregation id for reporting measurement data. This is an optional token that is only applicable to the following measurement type: dqos • Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-77 OL-8723-19...

  • Page 704: Reporting Current Interval Counts

    Enhanced Traffic Measurement Reporting Current Interval Counts The BTS 10200 system provides a CLI command to query in-progress partial interval counts of measurement data from the actual source of the data. This mechanism provides the ability to specify the current collection interval and the particular type and source of data. The start time specified must fall within the current collection interval.
  • Page 705 The following table lists the command line tokens associated with this command and the valid values and purpose of each: Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-79 OL-8723-19...
  • Page 706 This is an optional token that defaults to all call agents and is only applicable to the following measurement types: call-tools • billing • callp • • mgcp • isdn • audit • • • h323 • • Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-80 OL-8723-19...
  • Page 707 If entered, the corresponding call-agent-id or feature-server-id must be specified. There is no default value for this token. If this token and the start-time token are not entered by the user, the last collected interval is reported. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-81 OL-8723-19...

  • Page 708: Clearing Current Interval Counts

    Enhanced Traffic Measurement Clearing Current Interval Counts The Cisco BTS 10200 system provides a CLI command to clear in-progress partial counts of measurement data at the actual source of the data. This mechanism provides the ability to specify the particular type and source of data.
  • Page 709 This is an optional token that defaults to all feature servers and is only applicable to the following measurement types: • ain-tools • pct-tools • ainsvc sccp • tcap • m3ua • sctp • pots-local • pots-misc • pots-sle • pots-acar • pots-cos • pots-cot • Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-83 OL-8723-19...

  • Page 710: Measurements

    A description of the meaning of each counter is also provided. The name of each counter is an exact ASCII match to the label that is printed within the reports issued by the Cisco BTS 10200. These labels can then be used for automation purposes in testing and retrieving data from the BTS 10200 via the command line or FTP interfaces.

  • Page 711: Isdn Protocol Counters

    The number of ISDN NOTIFY messages received by the reporting call agent ISDN_STATUS_TX The number of ISDN STATUS messages sent from the reporting call agent ISDN_STATUS_RX The number of ISDN STATUS messages received by the reporting call agent Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-85 OL-8723-19...
  • Page 712 This counter is only applicable to ETSI PRI. Note ISDN_RESUME_REJ_RX The number of ISDN Resume Reject messages received by the reporting call agent. Note This counter is only applicable to ETSI PRI. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-86 OL-8723-19...
  • Page 713 This counter is only applicable to ETSI PRI. Note ISDN_SEGMENT_RX The number of ISDN Segment messages received by the reporting call agent. This counter is only applicable to ETSI PRI. Note Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-87 OL-8723-19...

  • Page 714: Call Processing Counters

    CALLP_SIP_ORIG_FAIL The number of SIP originating call attempts that failed on the reporting call agent. CALLP_SIP_TERM_FAIL The number of SIP terminating call attempts that failed on the reporting call agent. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-88 OL-8723-19...
  • Page 715 The number of successfully completed calls from an SS7 originator to an ISDN terminator on the reporting call agent. CALLP_SS7_SIP_CALL The number of successfully completed calls from an SS7 originator to an SIP terminator on the reporting call agent. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-89 OL-8723-19...
  • Page 716 CALLP_INTERLA_ABAND The number of Interlata call origination attempts that were abandoned on the reporting call agent. CALLP_INTRALA_ATTMP The number of Intralata call attempts on the reporting call agent. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-90 OL-8723-19...
  • Page 717 The number of terminating H323 call attempts that failed on the reporting call agent. CALLP_H323_CALL_SUCC The number of originating and terminating H323 call attempts that completed successfully on the reporting call agent. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-91 OL-8723-19...
  • Page 718 The total number of User Requests–Reason Code 801–that are received in the DLCX messages on the reporting call agent. CALLP_NAS_LOST_CARRIER The total number of Lost Carrier–Reason Code 802–that are received in the DLCX messages on the reporting call agent. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-92 OL-8723-19...
  • Page 719 The total number of origination attempts by subscribers that are marked as temporarily disconnected, detected by the reporting call agent. CALLP_ NLB_TEST_SUCC The total number of successful Network Loop Back Tests completed by the reporting call agent. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-93 OL-8723-19...
  • Page 720 T.38 fax transmission. CALLP_T38_FAX_MEDIA_SETUP_FAIL This counter is incremented when a T.38 media connection is not established successfully between the endpoints for T.38 fax transmission. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-94 OL-8723-19...

  • Page 721: Mgcp Adapter Counters

    The number of MGCP RSIP acknowledgement messages sent by the reporting call agent. MGCP_AUCX_TX The number of AUCX (Audit Connection) messages that were sent by the reporting call agent. (FUTURE–R5.0). Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-95 OL-8723-19...
  • Page 722 The number of AUCX ACK (Audit Connection Acknowledgement) messages that were received by the reporting call agent. (FUTURE–R5.0). MGCP_AUCX_NACK_RX The number of AUCX NACK (Audit Connection NotAcknowlegement) messages that were received by the reporting call agent. (FUTURE–R5.0). Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-96 OL-8723-19...

  • Page 723: Session Initiation Protocol Counters

    SIS_REGISTER_RX The number of SIP REGISTER messages the reporting call agent or feature server received. SIS_REGISTER_TX The number of SIP REGISTER messages the reporting call agent or feature server sent. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-97 OL-8723-19...
  • Page 724 The number of SIP provisioning response retransmission messages the reporting call agent or feature server received. SIS_PROV_RSP_RETRAN_TX The number of SIP provisioning response retransmission messages the reporting call agent or feature server sent. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-98 OL-8723-19...
  • Page 725 SIS_UPDATE_RX The number of SIP UPDATE messages the reporting call agent or feature server received. SIS_UPDATE_TX The number of SIP UPDATE messages the reporting call agent or feature server sent. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-99 OL-8723-19...

  • Page 726: Bts 10200 Status

    The BTSSTAT software utility provides status information for the entire BTS 10200 system. It can run on any BTS 10200 host and report the status of all the network elements in the BTS 10200 system, including those not on the same host. BTSSTAT is designed to be fast and secure.
  • Page 727 You can run BTSSTAT from a non-BTS 10200 host, provided that the host can establish an SSL connection to the target BTS 10200 host. In this case, the BTS 10200 hosts should be specified in a configuration file. Users can specify a configuration file with the -f option as follows:...

  • Page 728: System Context For Btsstat

    15-2. Additionally, Figure 15-2 illustrates the interrelated conditions or context for which the btsstat command provides status. BTSSTAT can run on any of these BTS 10200 hosts, or it can run on a separate host. Figure 15-2 BTSSTAT System Context...

  • Page 729: Installation On A Bts 10200 Host

    10200 system call to provide a system call trace troubleshooting capability. In the BTS 10200 releases prior to Release 5.0, TRACE logs captured the detailed operations of the call processing system, had a practical problem in that there was no easy means to filter out TRACE logs pertaining to a single basic or feature call.

  • Page 730: Restrictions And Limitations

    Where platform-instance-name could be CA146, FSPTC235, or the name of some other platform installed in your system. In the directory where the BTS 10200 trace logs are available, use the UNIX grep command to filter out Step 3 the trace logs corresponding to the selected CTRAC-ID.

  • Page 731: Isolating Calls Based On A Given Originating End Point

    Step 3 Use the CTRAC-ID to filter out the trace log lines from the BTS 10200 logs. Isolating Calls Based on a Given Terminating End Point To isolate calls based on a given terminating end point, take the following steps: Go to the desired target platform log directory.

  • Page 732: Isolating Calls Which Show Internal Symptoms Of Problems

    TRACE lines corresponding to a CTRAC-ID. Tabular Display of Events and Alarms The BTS 10200 Tabular Display of Events and Alarms feature enables the BTS 10200 to display current alarms, alarm history and event history in tabular form. The underlying CPI layer modification will easily facilitate other commands to display their data in tabular form.

  • Page 733: Operating

    Chapter 15 Diagnostic Tests Pre-Manual Switchover Switch Integrity Diagnostic Utility Operating There are three new CLI commands related to the BTS 10200 Tabular Display of Events and Alarms feature correlating to the following: • Show current alarms in tabular format •...

  • Page 734: Application Status Check

    Because the CA/FS node is likely to be in a “mixed” state, the utility script and the CLI command checks a specific switchover target or all three applications using an optional argument. Database Check The Cisco BTS 10200 Softswitch Pre-Manual Switchover Switch Integrity Diagnostic Utility feature performs the following tasks to check database synchronization, replication, and shared memory integrity.

  • Page 735: Switchover Impact Alarms Check

    Pre-Manual Switchover Switch Integrity Diagnostic Utility Switchover Impact Alarms Check The Cisco BTS 10200 Softswitch Pre-Manual Switchover Switch Integrity Diagnostic Utility feature queries the database for the following alarms to see if they are being raised by the switchover target side.

  • Page 736: Inter-Node Communication Check

    Diagnostic Tests Pre-Manual Switchover Switch Integrity Diagnostic Utility Inter-Node Communication Check The Cisco BTS 10200 Softswitch Pre-Manual Switchover Switch Integrity Diagnostic Utility feature performs the following checks on all four nodes to get the current communication status: • Checks if internode communication links are established •...

  • Page 737: Installing

    Switchover Switch Integrity Diagnostic Utility script. The output of the utility script is displayed as the command response. For security reasons, user input for the password field is masked with asterisks (“*”). The assumption here is that the passwords for of all four Cisco BTS 10200 Softswitch nodes is identical.

  • Page 738: Script Arguments

    Pre-Manual Switchover Switch Integrity Diagnostic Utility Script Arguments The Cisco BTS 10200 Softswitch Pre-Manual Switchover Switch Integrity Diagnostic Utility script will uses an optional argument for specifying the switchover target. Possible argument values are: CA, FSPTC, and FSAIN. The usage of this optional argument is the same as that for the presw-diag CLI command target field.

  • Page 739: Pstn Trunk Testing

    The legacy PSTN trunk network supports connection and performance appraisal testing individual trunks or network routes. This is generally referred to as 100-type tests. The Cisco BTS 10200 provides specific capabilities to support test call origination to selected individual trunks as well as test call termination.

  • Page 740: Cisco Bts 10200 Originating Test Line

    Trunk Access The Cisco BTS 10200 OTL can logically access up to 9,999 trunk groups, each with up to 9,999 trunks. Conditions for trunk test access are met when either the requested trunk is in service and idle or the requested trunk is out of service or blocked.

  • Page 741: Trunk Access And Test Termination Number Format

    Echo Trunk Under Test Outpulsing Once the specified trunk is selected, the Cisco BTS 10200 translates the dialed digits into a digit string for outpulsing. Once the trunk under test (TUT) is seized, it will outpulse the destination digits depicted Figure 15-5.

  • Page 742: Cisco Bts 10200 Terminating Test Line

    • arrangements can be supported). TTL Dial Plan The Cisco BTS 10200 test lines are typically assigned 958-11XX numbers as depicted in Figure 15-6. Any line or trunk may dial the appropriate digits to reach a TTL. Other dial plans are also supported and may also work in conjunction with the depicted plan.

  • Page 743: Near End Test Origination Test Line

    The user verifies that the remote CO has the desired 1xx test line available. The user sets up a test device on a CAS TGW that is connected to the local BTS 10200. The user provisions the CAS-TG-PROFILE table, setting TEST-LINE = YES. (Provisioning...

  • Page 744: Far End Originating Test Line

    Trunk Under Test Outpulsing, page 15-118 Function The OTL originates all test calls towards the Cisco BTS 10200 softswitch. The OTL may be part of an automated trunk test system (for example, CAROT) that will select trunks, make test calls, conduct tests, record measurements and report marginal or inferior trunk performance.

  • Page 745: Far End Terminating Test Line

    108 Test Line Group 109 Test Line Group 109 Test Line Group Far End Terminating Test Line This section discusses the following Cisco BTS 10200 far end terminating test line information: Function, page 15-119 • Test Equipment, page 15-119 •...

  • Page 746: Xx Test Lines

    Additional test processes may be used, depending on the specific test configuration. When the BTS 10200 is supporting the TTL capability (test call originated at another switch), the BTS 10200 receives the 958 or 959 call, recognizes the 958 or 959 type, and routes the test to the appropriate test line.

  • Page 747: Test–Balance

    The 105 test line is normally used by CAROT and other automated trunk test systems as the far end test line. In CAROT terms, this is commonly called the responder. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 15-121 OL-8723-19...

  • Page 748: Test Line–Data Transmission

    (VoP) softswitches. BTS 10200 incoming trunks requesting other 1xx-type test lines are routed to shared test lines for the requested tests, regardless of which gateway terminates the trunk or which gateway/IAD terminates the test line.

  • Page 749: Introduction

    In that case, data must be restored from a backup file. Restarting a Cisco BTS 10200 Softswitch Process When a BTS 10200 process exits due to an internal error (such as SIGSEGV on UNIX) or is terminated by the platform, the system automatically restarts the process that shut down.

  • Page 750: Before You Begin

    Location of an archive • Enabling negotiation on the 2900 switch for the primary interface of the system • Example: c2924.118-A#config t c2924.118-A(config-t)#int fastEthernet 0/1 c2924.118-A(config-if)#no speed 100 c2924.118-A(config-if)#no full duplex Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 16-2 OL-8723-19...

  • Page 751: C H A P T E R 16 Disaster Recovery Procedures

    Chapter 16 Disaster Recovery Procedures Disaster Recovery From Flash Archive Flash Archive Restore Cisco recommends running this procedure during maintenance window or when traffic is low. Note Connect to the console of the restored unit. Step 1 Load the bootable Solaris-10 CD into the compact disk–read only media (CD-ROM) drive.
  • Page 752 Enter the following command: Step 40 cp /a/bin/date /a/bin/.date mv /a/bin/date.archive /a/bin/date mv /a/etc/rc3.d/S99platform /a/etc/rc3.d/saved.S99platform Restore 2900 switch back to force 100MB full-duplex. Step 41 Power cycle the system. Step 42 Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 16-4 OL-8723-19...

  • Page 753: Setting Up Interfaces

    ( Run this script to set up interfaces on CA box) Verify all interfaces are setting up properly. Step 8 Set up root password by enter the following command: passwd root Step 9 Reboot the box: shutdown –y –g0 –i6 Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 16-5 OL-8723-19...

  • Page 754: Restoring The Bts 10200 Application

    Note Power Failure Recovery One critical component of the BTS 10200 software is the memory resident database, also referred to as Shared Memory. Shared memory can be damaged by internal/external power supply failure. The local status indicator for the shared memory database indicates that all actions needed to synchronize this database with the Active side while on standby have been completed.

  • Page 755: Power Fail Occurs Procedure

    Check the alarm logs if the EMS is available. Power is Restored Procedure When power comes back on, the BTS 10200 software and all platforms should power up running in duplex Active/Standby. Use the nodestat command to verify that all platforms are running with no failure indication.
  • Page 756 Check and analyze the logs for details that may provide the cause of the failure. If possible, fix the Step 3 problem. If the system can run in simplex, send the logs to Cisco Technical Assistance Center (TAC) for diagnosis and assistance. If the system cannot run simplex, run the procedure for a duplex power failure.

  • Page 757: Power Failure On Both Call Agent Computers

    This may take hours to complete and during this time, call processing is lost, that is why it is critical that Caution there is no common single point of failure in the power feeds. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 16-9 OL-8723-19...

  • Page 758: Total System Power Outage

    2:00 AM–daily hot backup (by ora_hot_backup.ksh process) 18:00 PM–daily archive log backup (by ora_arch_backup.ksh process) Oracle databases on both primary and secondary EMS systems crashed completely at January 10, 2002, 20:00pm. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 16-10 OL-8723-19...

  • Page 759: Recovery Goal

    EMS will be recovered using the procedures that recover data from the primary EMS. Before this recovery process is applied, it is assumed that the entire system, including all corrupted Note applications, has been restored. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 16-11 OL-8723-19...

  • Page 760: Recovering The Primary Element Management System Database

    5MB additional space. The number of archivelog files in the backup set can be identified from the optical1_ora_hot_full_backup_<timestamp>.log and/or the optical1_ora_arc_incr_backup_<timestamp>.log file in /opt/oraback directory. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 16-12 OL-8723-19...
  • Page 761 At this point all files are restored from remote ftp server in the /opt/oraback directory. You are Note now ready to apply the database recovery processes to bring your database up to the point of your last backup. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 16-13 OL-8723-19...
  • Page 762 You must complete the following procedures before this process: 1. platform stop all 2. stop_cron.sh 3. restore all required backup datasets to /opt/oraback directory 4. copy optical1_ctl_binary file to /data1/../<db1 and db2> ************************************************************************************* Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 16-14 OL-8723-19...
  • Page 763 <Thu Jan 10 16:44:27 CST 2002> Database recovery ended. <Thu Jan 10 16:44:27 CST 2002> Alter database open resetlogs Connected. Database altered. …. Database is successfully recovered. <Thu Jan 10 16:44:38 CST 2002> ./recover_db_until_time.ksh ended. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 16-15 OL-8723-19...

  • Page 764: Post Recovery–Cold Backup

    Once the cold backup is completed, save a copy of the backup files to the /opt/oraback directory for the Step 3 ftp script to transfer offsite. cd /opt/oracle/tmp cp optical1_ADMIN_upd.tar /opt/oraback cp optical1_upd.crontab /opt/oraback cp optical1_DB_upd.tar.gz /opt/oraback Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 16-16 OL-8723-19...

  • Page 765: Recovering The Element Management System Database From Another Database

    “Recovering the Element Management System Database from Another Database”. Recovering the Element Management System Database from Another Database This section provides the procedures to recover one corrupted EMS database from another active database. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 16-17 OL-8723-19...

  • Page 766: Recovery Procedures

    # ipcs –p | grep oracle You can use the ipcrm command to remove any shared memory or semaphore still allocated to oracle now. For example: ipcrm –m <identification (ID)>, ipcrm –s <ID> Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 16-18 OL-8723-19...
  • Page 767 On the corrupted EMS site, rebuild the Oracle database from one of the following three options: Option 1 If only database is corrupted and the BTS 10200 re-installation is not required, go to Step 5 to reload the database from the database backup file. Continue to...
  • Page 768 $ gzip –cd /opt/oraback/optical2_DB_upd.tar.gz | tar xvf - Start the database restore process. After the database data files are re-stored, execute the following command to start up the EMS database process: $ dbinit -L -E -i start Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 16-20 OL-8723-19...
  • Page 769 Text similar to the following is displayed: ***This will EMPTY all the tables on: *** local host ==> secems47 *** local database ==> optical2 *** Then copy data from remote DB optical1 at priems47 Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 16-21 OL-8723-19...
  • Page 770 <Mon Jan 24 11:46:42 CST 2005> INFO: copy tables => OK=190, FAIL=0, SKIP=0, OTHERS=0 <Mon Jan 24 11:46:42 CST 2005> INFO: DMMgr::Enabling Foreign Key constraints for OPTICALL... <Mon Jan 24 11:47:20 CST 2005> INFO: DMMgr::Enabling triggers for OPTICALL... Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 16-22 OL-8723-19...
  • Page 771 Start the DBHeartBeat process. Enter the following command: $ dbinit -H -i start $ dbadm -r get_broken_jobs Text similar to the following is displayed: declare rc binary_integer; begin rc := sys.dbms_defer_sys.push(destination=>'OPTICAL1', stop_on_error=>FALSE,delay_seconds=>0, parallelism=>1); end; Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 16-23 OL-8723-19...
  • Page 772 OPTICAL2::JQ Lock is empty? Checking table => OPTICALL.AGGR..OK Checking table => OPTICALL.ANI..OK Number of tables to be checked: xxx Number of tables checked OK: xxx Number of tables out-of-sync: 0 Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 16-24 OL-8723-19...
  • Page 773 Verify the Oracle crontab file on the corrupted EMS site. Compare the schedules of jobs with those on the active EMS site. If any schedule needs to be modified, enter the following command: $ crontab -e Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 16-25 OL-8723-19...

  • Page 774: Fresh Download

    The fresh download wipes out Call Agent shared memory data and causes a total outage. Caution Do not use this command on any live traffic production systems. Please contact Cisco TAC regarding the use of this command for disaster recovery.

  • Page 775: Call Agent Database Download And Recovery

    This call agent database download and recovery procedure is recommended as a last resort for recovering corrupted call agent databases. Please contact Cisco TAC regarding the use of this procedure for call agent database recovery. Note If transactions are stuck in the queue, execute a delete transaction-queue CLI command before Note beginning this procedure.
  • Page 776 Place the completed script in the /opt/OptiCall/CAxxx/bin directory on the primary call agent. Invoke the cs-control script from /opt/OptiCall/CAxxx/bin directory to place subscribers in service. cs-control data <name of script from step 8b> Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 16-28 OL-8723-19...

  • Page 777: Recovering Shared Memory Data

    Read this section in its entirety before attempting this procedure. Caution Do not use this command on any live traffic production systems. Contact Cisco TAC regarding the use of this command for disaster recovery. Do not download the database through the console port because the TTY can cause long delays.

  • Page 778: Recovering Shared Memory

    In such scenarios, it is recommended to flush all the entries from Oracle. CLI> show transaction_queue limit=2 TRANSACTION_ID=1242510999092 SEQUENCE_NUM=0 TARGET=CA101 Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 16-30 OL-8723-19...
  • Page 779 Use ftp to transfer the file created in Step 3 to the primary CA. Place the files in the following directories: Step 10 download-CA in /opt/OptiCall/CAxxx/bin download-FSPTC in /opt/OptiCall/FSPTCxxx/bin download-FSAIN in /opt/OptiCall/FSAINxxx/bin Start the primary CA and FS platforms. Enter the following command: Step 11 platform start Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 16-31 OL-8723-19...

  • Page 780: Restoring Subscriber And Trunk Terminations To Service

    You must run the following procedures in parallel, to limit the amount of down time. For example, one engineer can be working on subscribers while another engineer is working on trunks or trunk groups. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 16-32...

  • Page 781: Controlling Trunks And Trunk Groups

    Using the cs-control Tool to Bring Subscribers In-Service Use the cs-control tool to bring subscribers in-service. Obtain the cs-control tool from Cisco. You must write a script (as shown in the following example) to be used by the cs-control tool.

  • Page 782: Disaster Recovery Using The Automatic Shared Memory Backup

    Before You Begin This procedure should only be completed if both of the following conditions are true: Both Side A and Side B of the same BTS 10200 network element are out of service. • Neither side of the same BTS 10200 network element can be returned to service with a platform •...

  • Page 783: Automatic Shared Memory Backup Restore

    Step 7 and restoreSharedMemory -i FSAINzzz. After all BTS 10200 NEs are in service on Side A, perform an Audit of the EMS system database to the Step 8 CA/FS system database. The Audit will report any differences between the two system databases.

  • Page 784: Restore Shared Memory Script

    The software version and the current time are used in the name. For example: data.corrupt.900-04.05.01.V14.2006_09_01__00_21_50 Step 4 Copies the most recent ASMB shared memory backup copy to the data directory for the BTS 10200 NE being restored. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x...

  • Page 785: Automatic Restart

    This section describes the new BTS 10200 Automatic Restart feature. The BTS 10200 Automatic Restart feature is beneficial to customers because the BTS 10200 will attempt to automatically restart a platform (EMS/FS/CA) to STANDBY that has become OOS-FAULTY and has shut down. Currently the BTS 10200 will not restart a platform in this situation, leaving the active platform running in a vulnerable simplex mode until the standby platform is restored manually.

  • Page 786: Automatic Restart Processing

    SDAMR (Shut Down and Manually Restart)—These scenarios are handled the same way as the OOS-FAULTY behavior for earlier releases of the BTS 10200. The platform will shut down and wait for manual restart. All initialization-related processing (bringup) is treated this way.
  • Page 787 While waiting for CRQ, data replication was restarted. SDAAR Switchover to Active Switchover to active, but failure. SDAAR Switchover to active, but timeout failure. SDAAR Switchover to active, but RDM re-started. SDAAR Switchover to Standby Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 16-39 OL-8723-19...
  • Page 788 Automatic Restart is scheduled. However, the user can use the -noautorestart command option on either command to bypass the Automatic Restart and force the platform start or stop to occur immediately. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 16-40 OL-8723-19...

  • Page 789: Installing

    Installing There are two customer-provisionable parameters (SystemAutoRestartRate and SystemAutoRestartDelay) and one new platform-provisionable parameter (SystemAutoRestartNumSavedTraceLogs) for the BTS 10200 Automatic Restart feature. Additionally, two existing parameters are expanded into three parameters. Configuring This section explains how to perform the following tasks: Opticall Configuration •...

  • Page 790: Troubleshooting

    This alarm indicates that an Automatic Restart is pending and at what time it will be attempted. For additional information, refer to MAINTENANCE (117). Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 16-42 OL-8723-19...
  • Page 791 Revised: February 24, 2011, OL-8723-19 Introduction This chapter describes the process of replacing a defective Cisco BTS 10200 Softswitch disk. Each BTS 10200 system element contains two hard disks (disk 0 and disk 1) that are mirrored using Sun Solaris Disk Suite.

  • Page 792: Chapter 17 Disk Replacement

    System Backup Procedure The purpose of this section is to describe the needed steps to create a backup using the Flash Archive on BTS 10200 system. The procedure is performed before and after any software upgrade or for routine maintenance purposes.

  • Page 793: System Backup Procedure

    Where xxx is the instance number. Note Backup the system. Step 10 <hostname>#mv /bin/date /bin/date.archive <hostname>#mv /bin/.date /bin/date <hostname>#flarcreate –n <hostname> -I -X /tmp/excluded_dir –c /mnt/<hostname>.archive <hostname>#mv /bin/date /bin/.date <hostname>#mv /bin/date.archive /bin/date Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 17-3 OL-8723-19...
  • Page 794 <hostname>#ssh optiuser@<hostname> cli>control feature-server id=FSAINxxx;target-state=standby-active; cli>control feature-server id=FSPTCxxx;target-state=standby-active; cli>control call-agent id=CAxxx;target-state=standby-active; Where xxx is the instance number of each platform. Note Step 13 Repeat the same steps for the PRIMARY CA/FS. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 17-4 OL-8723-19...

  • Page 795: Element Management System/Bulk Data Management System Backup

    Switchover all platforms. Step 10 Perform the following commands from the active EMS. <hostname>#ssh optiuser@<hostname> cli>control bdms id=BDMS01;target-state=standby-active; cli>control element-manager id=EM01;target-state=standby-active; Repeat the same steps for PRIMARY EMS/BDMS. Step 11 Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 17-5 OL-8723-19...
  • Page 796 <hostname>#metaclear d6 Delete database replica on defective disk. Step 6 <hostname>#metadb –d –f /dev/dsk/cxt0d0s4 Step 7 Verify that there is no existing metadevice on defective disk. <hostname>#metastat –p |grep cxt0d0 Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 17-6 OL-8723-19...

  • Page 797: Call Agent/Feature Server Or Element Management System Disk 0 Replacement

    Remove the defective disk and insert the new replacement disk into slot 0. Step 11 Use the cfgadm command to bring the new Disk 0 on line. Step 12 <hostname># cfgadm -c configure c1::dsk/cxt0d0 Example: Secca38#cfgadm -c configure c1::dsk/c1t0d0 Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 17-7 OL-8723-19...
  • Page 798 <hostname>#metainit -f d9 1 1 /dev/dsk/cxt0d0s5 <hostname>#metainit -f d3 1 1 /dev/dsk/cxt0d0s1 <hostname>#metainit -f d6 1 1 /dev/dsk/cxt0d0s3 Step 17 Install the boot block on the new disk. <hostname>#installboot /usr/platform/`uname -i`/lib/fs/ufs/bootblk /dev/rdsk/cxt0d0s0 Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 17-8 OL-8723-19...
  • Page 799 The disk sync process with take awhile depending on the disk size. To find out the percentage completion Note of this process, you can run the metastat|grep % command. Start all BTS 10200 platforms. Step 19 <hostname>#platform start -nocopy Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 17-9 OL-8723-19...
  • Page 800 <hostname>#metaclear d7 Delete database replica on defective disk. Step 6 <hostname>#metadb –d –f /dev/dsk/cxt1d0s4 Step 7 Verify that there is no existing metadevice on defective disk. <hostname>#metastat –p |grep cxt1d0 Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 17-10 OL-8723-19...

  • Page 801: Call Agent/Feature Server Or Element Management System Disk 1 Replacement

    Remove the defective disk and insert the new replacement disk into slot 1. Step 11 Use the cfgadm command to bring the new Disk 1 on line. Step 12 <hostname># cfgadm -c configure c1::dsk/cxt1d0 Example: Secca38#cfgadm -c configure c1::dsk/c1t1d0 Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 17-11 OL-8723-19...
  • Page 802 <hostname>#metainit -f d9 1 1 /dev/dsk/cxt1d0s5 <hostname>#metainit -f d3 1 1 /dev/dsk/cxt1d0s1 <hostname>#metainit -f d6 1 1 /dev/dsk/cxt1d0s3 Install the boot block on the new disk. Step 17 <hostname>#installboot /usr/platform/`uname -i`/lib/fs/ufs/bootblk /dev/rdsk/cxt1d0s0 Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 17-12 OL-8723-19...
  • Page 803 The disk sync process with take awhile depending on the disk size. To find out the percentage completion Note of this process, you can run the metastat|grep % command. Start all BTS 10200 platforms. Step 19 <hostname>#platform start -nocopy Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 17-13 OL-8723-19...
  • Page 804 Chapter 17 Disk Replacement Call Agent/Feature Server or Element Management System Disk 1 Replacement Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x 17-14 OL-8723-19...
  • Page 805 Recoverable and Nonrecoverable Error Codes Revised: July 22, 2009, OL-8723-19 MGCP Normal, Recoverable, and Nonrecoverable Error Codes This appendix lists normal, recoverable and nonrecoverable error codes for the Cisco BTS 10200 Softswitch. Table A-1 categorizes Media Gateway Control Protocol (MGCP) error codes into three categories: normal, recoverable, and non-recoverable.

  • Page 806: A P P E N D I X A Recoverable And Nonrecoverable Error Codes

    DeleteConnection command Endpoint is unknown. If this code is received during idling of an endpoint, the BTS 10200 marks the endpoint as faulty and perform automatic recovery. Endpoint is not ready. If this code is received, the BTS...
  • Page 807 Event/signal parameter error (e.g. missing, erroneous, unsupported, unknown, etc.). Invalid or unsupported command parameter. This code SHOULD only be used when the parameter is neither a package or vendor extension parameter Per endpoint connection limit exceeded. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...
  • Page 808 AUEP—audit endpoint, DLCX—delete connection, CRCX—create connection, MDCX—modify connection, Note RQNT—notification request Normal (N)—other than 200 error code, the BTS 10200 clears the call. recoverable (R)—: the BTS 10200 clears the Note call and starts finite recovery. non-recoverable (NR) or faulty (F)— the BTS 10200 clears the call.

  • Page 809: Introduction

    BTS 10200. Keepalive for Release 5.0 Prior to Maintenance Release 1.1 Use this section of the document if you are running BTS 10200 Release 5.0 with a Maintenance Release prior to 1.1. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x...

  • Page 810: Provisionable Parameters

    Caution Before modifying any of these numerical values (using values different than the factory default settings), thoroughly read and understand the contents of this document. If you have questions, contact your Cisco account team or Cisco TAC. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x...

  • Page 811: Definitions And Additional Parameters

    MGW in down status—After a defined number of KA retry failures, the BTS 10200 declares this MGW to be in down status, and continues to perform the KA procedure. Note To learn more about the MGW operational states reported by the BTS 10200, see the MGW table in the Cisco BTS 10200 Softswitch CLI Database.

  • Page 812: Examples Of Successful Mgcp Message Transmissions

    In a typical network, the average response time is much less than 400 milliseconds. Therefore, in this section, the drawings show the initial waiting period as mgcp-t-tran. The drawings in this section are not to scale. Note Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...

  • Page 813: Scenarios With Auep Message Retransmissions And Ack Received

    (3rd retransmission) (2nd retransmission) received trying 1st IP address Time mgcp-t-tran 2*mgcp-t-tran 4*mgcp-t-tran 8*mgcp-t-tran See the additional information about mgcp-t-tran in the “Initial Transmission Waiting Period Note (mgcp-t-tran)” section on page B-4. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...
  • Page 814 2*mgcp-t-tran 4*mgcp-t-tran 8*mgcp-t-tran The system attempts up to four different IP addresses for any single MGW listed in the DNS server. (This Note maximum number of IP addresses is not provisionable.) Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...

  • Page 815: Scenarios With Auep Message Retransmissions And No Ack

    (default = 4 seconds) (default = 4 seconds) Time mgcp-t-tran 2*mgcp-t-tran 4*mgcp-t-tran 8*mgcp-t-tran 16*mgcp-t-tran See the additional information about mgcp-t-tran in the “Initial Transmission Waiting Period Note (mgcp-t-tran)” section on page B-4. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...

  • Page 816: Mgcp-Max2-Retries, Mgcp-T-Max And 2*Mgcp-T-Hist

    Keepalive for Release 5.0 Prior to Maintenance Release 1.1 MGCP-MAX2-RETRIES, MGCP-T-MAX and 2*MGCP-T-HIST The BTS 10200 limits retransmissions of the AUEP message to mgcp-max2-retries or a total duration of mgcp-t-max (default = 20 seconds), whichever occurs first. If the system does not receive an ACK before the expiration of 2*mgcp-t-hist (two times the provisioned...

  • Page 817: Keepalive Process

    Keepalive for Release 5.0 Prior to Maintenance Release 1.1 Keepalive Process This section describes the keepalive (KA) process. The BTS 10200 performs KA attempts to determine whether a MGW should be considered to be in working status or down status.
  • Page 818 B-5. The MGW is reachable (an ACK is received during each KA attempt) and has stable calls, but no MGCP messages have been exchanged between the BTS 10200 and the MGW for a time interval equal to the provisioned value of mgcp-keepalive-interval (default 60 seconds) in the mgw-profile table.
  • Page 819 MGCP Message Sent and Is Unsuccessful If the BTS 10200 sends an MGCP message to the MGW, and the message is unsuccessful (no ACK received), the KA process is expedited even though the next KA attempt is scheduled for a later time.

  • Page 820: Scenario 2 (Special Case)—Reachable Rgw With 16 Or Fewer Endpoints And No Stable Calls In Progress

    Keepalive for Release 5.0 Prior to Maintenance Release 1.1 MGCP Message Sent and Is Successful If the BTS 10200 sends an MGCP message to the MGW, and the message is successful (an ACK is received), the system restarts the keepalive timer. This condition is shown in Figure B-7.
  • Page 821 B-8. The MGW is reachable (an ACK is received during each KA attempt) and has no stable calls, and no MGCP messages have been exchanged between the BTS 10200 and the MGW for a time interval equal to the provisioned value of mgcp-keepalive-interval (default 60 seconds) in the mgw-profile table.
  • Page 822 MGCP Message Sent and Is Unsuccessful If the BTS 10200 sends an MGCP message to the MGW, and the message is unsuccessful (no ACK received), the KA process is expedited even though the next KA attempt is scheduled for a later time.

  • Page 823: Scenario 3—Mgw Unreachable

    Keepalive for Release 5.0 Prior to Maintenance Release 1.1 MGCP Message Sent and Is Successful If the BTS 10200 sends an MGCP message to the MGW, and the message is successful (an ACK is received), the system restarts the keepalive timer. This condition is shown in Figure B-10.
  • Page 824 If no ACK is received during any KA attempt, and no MGCP messages have been exchanged between the BTS 10200 and the MGW for a specified time interval (see the time interval description in the drawing), the system performs a specified number of KA retries before declaring the MGW to be unreachable.
  • Page 825 AUEP transaction. Starts at 10 seconds and increases Maximum value is as shown, but is not allowed to exceed mgcp-max-keepalive-interval (default = 600 seconds). 60 seconds (not provisionable). Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x B-17 OL-8723-19...
  • Page 826 If the MGW is still in down status, the KA attempts continue. This condition is shown in Figure B-13. In this case, the BTS 10200 fails the call immediately after receiving the call termination attempt, Note without sending any MGCP message to the MGW.

  • Page 827: Keepalive For Release 5.0 Maintenance Release 1.1 And Later

    Keepalive for Release 5.0 Maintenance Release 1.1 and Later Keepalive for Release 5.0 Maintenance Release 1.1 and Later Use this section of the document if you are running BTS 10200 Release 5.0 MR1.1 or later. Provisionable Parameters The following tokens are involved in KA process: In the mgw-profile table: •...

  • Page 828: Definitions And Additional Parameters

    MGW in down status—After a defined number of KA retry failures, the BTS 10200 declares this MGW to be in down status, and continues to perform the KA procedure. Note To learn more about the MGW operational states reported by the BTS 10200, see the MGW table in the Cisco BTS 10200 Softswitch CLI Database.

  • Page 829: Initial Transmission Waiting Period (Mgcp-T-Tran)

    (2nd retransmission) received trying 1st IP address Time mgcp-t-tran 2*mgcp-t-tran 4*mgcp-t-tran 8*mgcp-t-tran See the additional information about mgcp-t-tran in the “Initial Transmission Waiting Period Note (mgcp-t-tran)” section on page B-21. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x B-21 OL-8723-19...
  • Page 830 4*mgcp-t-tran 8*mgcp-t-tran The system attempts up to four different IP addresses for any single MGW listed in the DNS server. (This Note maximum number of IP addresses is not provisionable.) Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x B-22 OL-8723-19...

  • Page 831: Scenarios With Auep Message Retransmissions And No Ack

    (default = 4 seconds) (default = 4 seconds) Time mgcp-t-tran 2*mgcp-t-tran 4*mgcp-t-tran 8*mgcp-t-tran 16*mgcp-t-tran See the additional information about mgcp-t-tran in the “Initial Transmission Waiting Period Note (mgcp-t-tran)” section on page B-21. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x B-23 OL-8723-19...

  • Page 832: Mgcp-Max2-Retries And Mgcp-T-Max

    Keepalive for Release 5.0 Maintenance Release 1.1 and Later MGCP-MAX2-RETRIES and MGCP-T-MAX The BTS 10200 limits retransmissions of the AUEP message to mgcp-max2-retries or a total duration of mgcp-t-max (default = 20 seconds), whichever occurs first. If the system has not received an ACK at this point, it takes the following actions: It stops all retransmissions and abandons the transaction.

  • Page 833: Keepalive Process

    Keepalive for Release 5.0 Maintenance Release 1.1 and Later Keepalive Process This section describes the keepalive (KA) process. The BTS 10200 performs KA attempts to determine whether a MGW should be considered to be in working status or down status.
  • Page 834 B-18. The MGW is reachable (an ACK is received during each KA attempt) and has stable calls, but no MGCP messages have been exchanged between the BTS 10200 and the MGW for a time interval equal to the provisioned value of mgcp-keepalive-interval (default 60 seconds) in the mgw-profile table.
  • Page 835 MGCP Message Sent and Is Unsuccessful If the BTS 10200 sends an MGCP message to the MGW, and the message is unsuccessful (no ACK received), the KA process is expedited even though the next KA attempt is scheduled for a later time.

  • Page 836: Scenario 2 (Special Case)—Reachable Rgw With 16 Or Fewer Endpoints And No Stable Calls In Progress

    Keepalive for Release 5.0 Maintenance Release 1.1 and Later MGCP Message Sent and Is Successful If the BTS 10200 sends an MGCP message to the MGW, and the message is successful (an ACK is received), the system restarts the keepalive timer. This condition is shown in Figure B-20.
  • Page 837 (Scenario 2 (Special Case)—Reachable RGW with 16 or Fewer Endpoints and No Stable Calls In Progress). If a KA attempt is unsuccessful: The system implements the KA pattern shown in Scenario 3. (See • Scenario 3—MGW Unreachable.) Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x B-29 OL-8723-19...
  • Page 838 MGCP Message Sent and Is Unsuccessful If the BTS 10200 sends an MGCP message to the MGW, and the message is unsuccessful (no ACK received), the KA process is expedited even though the next KA attempt is scheduled for a later time.

  • Page 839: Scenario 3—Mgw Unreachable

    Keepalive for Release 5.0 Maintenance Release 1.1 and Later MGCP Message Sent and Is Successful If the BTS 10200 sends an MGCP message to the MGW, and the message is successful (an ACK is received), the system restarts the keepalive timer. This condition is shown in Figure B-23.
  • Page 840 If no ACK is received during any KA attempt, and no MGCP messages have been exchanged between the BTS 10200 and the MGW for a specified time interval (see the time interval description in the drawing), the system performs a specified number of KA retries before declaring the MGW to be unreachable.
  • Page 841 (76)—Timeout on remote instance. This event is applicable when the keepalive – functionality is disabled. If all KA attempts are unsuccessful through mgcp-keepalive-retries, the system declares the MGW • unreachable. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x B-33 OL-8723-19...
  • Page 842 AUEP transaction. Starts at 10 seconds and increases Maximum value is as shown, but is not allowed to exceed mgcp-max-keepalive-interval (default = 600 seconds). 60 seconds (not provisionable). Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x B-34 OL-8723-19...
  • Page 843 If the MGW is still in down status, the KA attempts continue. This condition is shown in Figure B-26. In this case, the BTS 10200 fails the call immediately after receiving the call termination attempt, Note without sending any MGCP message to the MGW.
  • Page 844 Appendix B System Usage of MGW Keepalive Parameters, Release 5.0 Keepalive for Release 5.0 Maintenance Release 1.1 and Later Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x B-36 OL-8723-19...

  • Page 845: Overload Control Phases

    Changes to these files significantly impact system performance. Edit them only under the direction of a Cisco engineer. 3. Management Affects the following switch areas: Alarms • Logs • • Billing • Measurements Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...

  • Page 846: Appendix C Overload Control

    70, 80, 90, and 95 percent. Table C-2 MCL Thresholds Onset /abatement thresholds Factor Level 0–69 level_1_threshold = 70 70–79 level_2_threshold = 80 80–89 level_3_threshold = 90 90–95 level_4_threshold = 95 95–100 Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...

  • Page 847: Reducing Overload

    These tasks include examples of CLI commands that illustrate how to provision the specific feature. For Note a complete list of all CLI tables and tokens, refer to the Cisco BTS 10200 Softswitch Command Line Interface Reference Guide. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x...

  • Page 848: Setting The Minimum System Mcl

    When rejecting a SIP message during overload, you can use either of the following: 500 Server Internal Error • 503 Service Unavailable • Use the following command. The default value is 503. add ca_config type=SIA-OC-REJECTION-RESP; datatype=integer; value=500; Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...

  • Page 849: Configuring Emergency Call Handling

    Message Rejection: INVITE If overloaded BTS rejects a percentage of incoming INVITE messages. The percentage rejected is based on sia.cfg. Only new INVITE messages are checked for acceptance. Re-INVITE messages are always accepted. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...

  • Page 850: Message Rejection Logic

    Operating This section explains how to perform the following tasks: Viewing MCL • Editing the OLM.CFG File • It also explains how this feature affects the following operational area: Measurements • Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...

  • Page 851: Viewing Mcl

    Edit it only under the direction of a Cisco engineer. sia.cfg /opt/OptiCall/ca/bin/ Has SIP timer values used during overload (SIP Adapter) These values can be changed Caution only by a Cisco engineer. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...

  • Page 852: Sample Olm.cfg

    #The minimum amount of time (ms) that can be spent at MCL2 level_3_damping_time=800 #The minimum amount of time (ms) that can be spent at MCL3 level_4_damping_time=400 #The minimum amount of time (ms) that can be spent at MCL4 Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...
  • Page 853 #The value at which MCL level 4 is triggered for this factor #Alarm Step Size % info_alarm_step_size=${STEP} #The number of percentage point steps that will cause an #info alarm for this factor Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x OL-8723-19...

  • Page 854: Measurements

    Appendix C Overload Control Operating Measurements These tables list new, modified, or deleted measurements. See the Measurements section of the BTS 10200 Operations and Maintenance Guide for a complete list Note of all traffic measurements. Call Processing Measurements Table C-4 lists the new call processing measurements provided to support this feature.

  • Page 855: Service Interaction Manager Measurements

    The total number of incoming SUBSCRIBE messages rejected. SIA_OC_RX_UNSOL_NOTIFY_SUPP The total number of unsolicited notification requests suppressed without sending to endpoints. SIA_OC_RX_OPTIONS_REJECT The total number of incoming OPTIONS messages rejected by SIA due to overload. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x C-11 OL-8723-19...

  • Page 856: Miscellaneous Measurements

    Dampen this alarm using alarm_damping_time in olm.cfg. The value of alarm_damping_time is the minimum amount of time that passes before the alarm is issued after the change occurred. For additional information, refer to the “MAINTENANCE (112)” section on page 7-60. Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x C-12 OL-8723-19...

  • Page 857: Cpu Load Of Critical Processes—Maintenance(113)

    Use the INFO logs to get differing levels of information about the alarms: • INFO1—Are included with each alarm INFO3—Prints factors feature controlled by olm.cfg shows system overview • INFO4—Have extra detail • INFO5—Shows exact details of the factor MCL computations • Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x C-13 OL-8723-19...
  • Page 858 Appendix C Overload Control Troubleshooting Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x C-14 OL-8723-19...
  • Page 859 American National Standards Institute ANSI address of record application programming interface admission request application server associate application service provider Alliance for Telecommunications Industry Solutions ATIS Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x GL-1 OL-8723-19...
  • Page 860 Glossary audit connection AUCX audit endpoint AUEP binary 8-zero substitution B8ZS Basic Call module Bulk Data Management System BDMS billing blocking Broadband Telephony Softswitch band width Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x GL-2 OL-8723-19...
  • Page 861 CNAM coder/decoder, compression/decompression CODEC Common Open Policy Service Protocol COPS Common Object Request Broker Architecture CORBA customer-originated trace, continuity testing, central office termination customer premises equipment central processing unit Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x GL-3 OL-8723-19...
  • Page 862 Dynamic Host Configuration Protocol DHCP delete connection DLCX delay directory number dialed number identification service DNIS domain name system document destination point code differentiated service code point DSCP destination user part unavailable DUPU Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x GL-4 OL-8723-19...
  • Page 863 FPGA fully qualified domain name FQDN Feature Server Feature Server for AIN services FSAIN Feature Server for POTS, Tandem, and Centrex services FSPTC File Transfer Protocol Foreign Exchange Station Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x GL-5 OL-8723-19...
  • Page 864 Greenwich Mean Time group reset acknowledge gatekeeper reject group gatekeeper request group reset generic transport descriptor global title translation gateway H.323 Protocol H323 H323 gateway H323GW H.323 signaling adapter heartbeat Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x GL-6 OL-8723-19...
  • Page 865 Internet Protocol Manager Internet Protocol security IPSEC Integrated Services Digital Network ISDN Internet service provider ISDN user part ISUP IP transfer point interactive voice response interexchange carrier Java message service Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x GL-7 OL-8723-19...
  • Page 866 Kerberized management server log archive facility local access and transport area LATA locally blocked LBLK line information database LIDB local number portability loop prevention acknowledgement local routing number local serving area Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x GL-8 OL-8723-19...
  • Page 867 MRMW millisecond media terminal adapter, Metropolitan Trading Area message transfer part message transfer part 1 MTP1 message transfer part 2 MTP2 message transfer part 3 MTP3 maximum transmission unit Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x GL-9 OL-8723-19...
  • Page 868 OAMP originating line information Ulticom SS7 stack OMNI OptiCall Messaging System originating point code Open Packet Telephony Oracle operating system operations support system Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x GL-10 OL-8723-19...
  • Page 869 ID process manager point of presence plain old telephone service POTS primary rate interface public switched telephone network PSTN queue processing module quality of service Query Verification Tool Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x GL-11 OL-8723-19...
  • Page 870 RQNT resource record request rejected registration request reset circuit restart in progress RSIP re-transact routing module retransmission time out Real Time Transport Protocol Reliable User Datagram Protocol RUDP retransmit Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x GL-12 OL-8723-19...
  • Page 871 System Health Report (system-health) SIP adapter system identification number Session Initiation Protocol signaling link code Service Logic Host Route SLHR system manager system manager program service management system Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x GL-13 OL-8723-19...
  • Page 872 Glossary Simple Network Management Protocol SNMP service provider Structured Query Language service Signaling System 7 secure shell subsystem number signal switching point signal transfer point SCCP user adapter subscriber Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x GL-14 OL-8723-19...
  • Page 873 ID TGID trunk group ID TGN-ID Traffic and Measurements module type of service terminating point master transient TRNS TCAP signaling adapter transport service access point TSAP Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x GL-15 OL-8723-19...
  • Page 874 Upper Layer Protocol uniform resource identifier universal resource locator United States United States of America voice over IP VOIP volume table of contents VTOC extended unit association extended unit data service XUDTS Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x GL-16 OL-8723-19...

Table of Contents