line locked out" error for some outbound calls

[cuneyt2020]

Hi all
The system is BC9
PRI Route is between Md110 (BC9) and AXE10 GSM company...
The GSM calls which the staff of MD generates, are routed to this route (Route 55)

Route parameters are
[tt]
<ROCAP:ROU=55;
ROUTE CATEGORY DATA
ROU SEL TRM SERV NODG DIST DISL TRAF SIG BCAP
55 711000000000 7 2100000001 0 30 128 00070715 000010010030 101100

END

<ROdAP:ROU=55;
ROUTE DATA
ROU TYPE VARC VARI VARO FILTER
55 SL60 H'00000200 H'14400000 H'06410000 NO

For some of the calls whic md makes, are getting "line locked out" message on telephone set with an anonymous reason.. This is true for some calls , i made 10 calls to GSM operator and 3 of them was getting tri tone and line locked out message.

Giving allop command i saw execution time out message for SLP60

<ALLOP;
ALARM LOG
IDENTITY: KADIKOY-CNI82
VERSION: LZY20351/1/CNI70-CNI71/R1A

DATE: 01FEB05 TIME: 17:56:27
CLASS: 1
2 EXECUTION TIMEOUT
DATE TIME ALP NOIF UNIT EQU INF1
01FEB05 17:42:05 2 1 SLP60 002-0-**-** 0

CLASS: 0
260 FAULT ON LINE TO INTERWORKING PABX OR PUBLIC EXCHANGE
DATE TIME ALP NOIF UNIT EQU BRDID INF1 INF2
01FEB05 17:46:27 1 5 TLP11 001-1-70-06 76 92 1
RDATE RTIME
01FEB05 17:46:28

and HIEDP is increasing after HIREI for LIM 4;
and same error occurs

TIME DATE ERROR CODE
18:09:33 01FEB05 H'14
JUMP TO ILLEGALSTATE
LOGICAL PROGRAM ERROR ADDRESS = 0203AB54
ENTER
SWSW A-LEVEL SIGNAL BPAANSACK (H'0094)
FROM TLP60 (H'3CD) EXE A IN LIM 004
TO SLP60 (H'374) EXE A IN LIM 004
NUMBER OF DATA BYTES IN SIGNAL = 2
WITH 0 1 2 3 4 5 6 7 8 9
000 E0 37

USER STACK DUMP
0 1 2 3 4 5 6 7 8 9 A B C D E F
02 01 09 9A

TIME DATE ERROR CODE
18:00:49 01FEB05 H'14
JUMP TO ILLEGALSTATE
LOGICAL PROGRAM ERROR ADDRESS = 0203AB54
ENTER
SWSW A-LEVEL SIGNAL BPAANSACK (H'0094)
FROM TLP60 (H'3CD) EXE A IN LIM 004
TO SLP60 (H'374) EXE A IN LIM 004
NUMBER OF DATA BYTES IN SIGNAL = 2
WITH 0 1 2 3 4 5 6 7 8 9
000 27 D6
STACK ADDRESS = 00000000
SIGNAL SEND ADDRESS = 0200696C

USER STACK DUMP
0 1 2 3 4 5 6 7 8 9 A B C D E F
02 01 09 9A

TIME DATE ERROR CODE
18:00:27 01FEB05 H'14
JUMP TO ILLEGALSTATE
LOGICAL PROGRAM ERROR ADDRESS = 0203AB54
ENTER
SWSW A-LEVEL SIGNAL BPAANSACK (H'0094)
FROM TLP60 (H'3CD) EXE A IN LIM 004
TO SLP60 (H'374) EXE A IN LIM 004
NUMBER OF DATA BYTES IN SIGNAL = 2
WITH 0 1 2 3 4 5 6 7 8 9
000 76 D2

USER STACK DUMP
0 1 2 3 4 5 6 7 8 9 A B C D E F
02 01 09 9A

TIME DATE ERROR CODE
17:59:50 01FEB05 H'14
JUMP TO ILLEGALSTATE
LOGICAL PROGRAM ERROR ADDRESS = 0203AB54
ENTER
SWSW A-LEVEL SIGNAL BPAANSACK (H'0094)
FROM TLP60 (H'3CD) EXE A IN LIM 004
TO SLP60 (H'374) EXE A IN LIM 004
NUMBER OF DATA BYTES IN SIGNAL = 2
WITH 0 1 2 3 4 5 6 7 8 9
000 00 C7
STACK ADDRESS = 00000000
SIGNAL SEND ADDRESS = 0200696C

USER STACK DUMP
0 1 2 3 4 5 6 7 8 9 A B C D E F
02 01 09 9A

TIME DATE ERROR CODE
17:59:35 01FEB05 H'14
JUMP TO ILLEGALSTATE
LOGICAL PROGRAM ERROR ADDRESS = 0203AB54
ENTER
SWSW A-LEVEL SIGNAL BPAANSACK (H'0094)
FROM TLP60 (H'3CD) EXE A IN LIM 004
TO SLP60 (H'374) EXE A IN LIM 004
NUMBER OF DATA BYTES IN SIGNAL = 2
WITH 0 1 2 3 4 5 6 7 8 9
000 24 C5
STACK ADDRESS = 00000000
SIGNAL SEND ADDRESS = 0200696C

USER STACK DUMP
0 1 2 3 4 5 6 7 8 9 A B C D E F
02 01 09 9A

TIME DATE ERROR CODE
17:55:47 01FEB05 H'14
JUMP TO ILLEGALSTATE
LOGICAL PROGRAM ERROR ADDRESS = 0203AB54
ENTER
SWSW A-LEVEL SIGNAL BPAANSACK (H'0094)
FROM TLP60 (H'3CD) EXE A IN LIM 004
TO SLP60 (H'374) EXE A IN LIM 004
NUMBER OF DATA BYTES IN SIGNAL = 2
WITH 0 1 2 3 4 5 6 7 8 9
000 9E A4

USER STACK DUMP
0 1 2 3 4 5 6 7 8 9 A B C D E F
02 01 09 9A

TIME DATE ERROR CODE
17:53:46 01FEB05 H'14
JUMP TO ILLEGALSTATE
LOGICAL PROGRAM ERROR ADDRESS = 0203AB54
ENTER
SWSW A-LEVEL SIGNAL BPAANSACK (H'0094)
FROM TLP60 (H'3CD) EXE A IN LIM 004
TO SLP60 (H'374) EXE A IN LIM 004
NUMBER OF DATA BYTES IN SIGNAL = 2
WITH 0 1 2 3 4 5 6 7 8 9
000 D5 8C
STACK ADDRESS = 00000000
SIGNAL SEND ADDRESS = 0200696C

USER STACK DUMP
0 1 2 3 4 5 6 7 8 9 A B C D E F
02 01 09 9A

TIME DATE ERROR CODE
17:53:27 01FEB05 H'14
JUMP TO ILLEGALSTATE
LOGICAL PROGRAM ERROR ADDRESS = 0203AB54
ENTER
SWSW A-LEVEL SIGNAL BPAANSACK (H'0094)
FROM TLP60 (H'3CD) EXE A IN LIM 004
TO SLP60 (H'374) EXE A IN LIM 004
NUMBER OF DATA BYTES IN SIGNAL = 2
WITH 0 1 2 3 4 5 6 7 8 9
000 8C 8A
STACK ADDRESS = 00000000
SIGNAL SEND ADDRESS = 0200696C

USER STACK DUMP
0 1 2 3 4 5 6 7 8 9 A B C D E F
02 01 09 9A

TIME DATE ERROR CODE
17:53:04 01FEB05 H'14
JUMP TO ILLEGALSTATE
LOGICAL PROGRAM ERROR ADDRESS = 0203AB54
ENTER
SWSW A-LEVEL SIGNAL BPAANSACK (H'0094)
FROM TLP60 (H'3CD) EXE A IN LIM 004
TO SLP60 (H'374) EXE A IN LIM 004
NUMBER OF DATA BYTES IN SIGNAL = 2
WITH 0 1 2 3 4 5 6 7 8 9
000 0A 87

USER STACK DUMP
0 1 2 3 4 5 6 7 8 9 A B C D E F
02 01 09 9A

TIME DATE ERROR CODE
17:52:32 01FEB05 H'14
JUMP TO ILLEGALSTATE
LOGICAL PROGRAM ERROR ADDRESS = 0203AB54
ENTER
SWSW A-LEVEL SIGNAL BPAANSACK (H'0094)
FROM TLP60 (H'3CD) EXE A IN LIM 004
TO SLP60 (H'374) EXE A IN LIM 004
NUMBER OF DATA BYTES IN SIGNAL = 2
WITH 0 1 2 3 4 5 6 7 8 9
000 B9 7A

USER STACK DUMP
0 1 2 3 4 5 6 7 8 9 A B C D E F
02 01 09 9A

TIME DATE ERROR CODE
17:52:05 01FEB05 H'14
JUMP TO ILLEGALSTATE
LOGICAL PROGRAM ERROR ADDRESS = 0203AB54
ENTER
SWSW A-LEVEL SIGNAL BPAANSACK (H'0094)
FROM TLP60 (H'3CD) EXE A IN LIM 004
TO SLP60 (H'374) EXE A IN LIM 004
NUMBER OF DATA BYTES IN SIGNAL = 2
WITH 0 1 2 3 4 5 6 7 8 9
000 32 6D

USER STACK DUMP
0 1 2 3 4 5 6 7 8 9 A B C D E F
02 01 09 9A

TIME DATE ERROR CODE
17:51:22 01FEB05 H'14
JUMP TO ILLEGALSTATE
LOGICAL PROGRAM ERROR ADDRESS = 0203AB54
ENTER
SWSW A-LEVEL SIGNAL BPAANSACK (H'0094)
FROM TLP60 (H'3CD) EXE A IN LIM 004
TO SLP60 (H'374) EXE A IN LIM 004
NUMBER OF DATA BYTES IN SIGNAL = 2
WITH 0 1 2 3 4 5 6 7 8 9
000 3A 5B

USER STACK DUMP
0 1 2 3 4 5 6 7 8 9 A B C D E F
02 01 09 9A

TIME DATE ERROR CODE
17:51:00 01FEB05 H'14
JUMP TO ILLEGALSTATE
LOGICAL PROGRAM ERROR ADDRESS = 0203AB54
ENTER
SWSW A-LEVEL SIGNAL BPAANSACK (H'0094)
FROM TLP60 (H'3CD) EXE A IN LIM 004
TO SLP60 (H'374) EXE A IN LIM 004
NUMBER OF DATA BYTES IN SIGNAL = 2
WITH 0 1 2 3 4 5 6 7 8 9
000 E1 53

USER STACK DUMP
0 1 2 3 4 5 6 7 8 9 A B C D E F
02 01 09 9A

TIME DATE ERROR CODE
17:50:29 01FEB05 H'14
JUMP TO ILLEGALSTATE
LOGICAL PROGRAM ERROR ADDRESS = 0203AB54
ENTER
SWSW A-LEVEL SIGNAL BPAANSACK (H'0094)
FROM TLP60 (H'3CD) EXE A IN LIM 004
TO SLP60 (H'374) EXE A IN LIM 004
NUMBER OF DATA BYTES IN SIGNAL = 2
WITH 0 1 2 3 4 5 6 7 8 9
000 34 4A

USER STACK DUMP
0 1 2 3 4 5 6 7 8 9 A B C D E F
02 01 09 9A

TIME DATE ERROR CODE
17:49:15 01FEB05 H'14
JUMP TO ILLEGALSTATE
LOGICAL PROGRAM ERROR ADDRESS = 0203AB54
ENTER
SWSW A-LEVEL SIGNAL BPAANSACK (H'0094)
FROM TLP60 (H'3CD) EXE A IN LIM 004
TO SLP60 (H'374) EXE A IN LIM 004
NUMBER OF DATA BYTES IN SIGNAL = 2
WITH 0 1 2 3 4 5 6 7 8 9
000 09 40


[/tt]
Does anybody have idea of it?
Rgrds.

 

[patcher]

Did you RFPUI:LIM=4,UNIT=SLP60;??? If still faulty you need to upgrade your switch to the latest CNI.

 

[HIREI]

Yes, of course,
1) Use (E)DSS1 protocol analyser, if it's no available goto 2
2) Use MD110 tracing and SAM tools to analyse, if no goto 3
3) Ask to trace the calls the AXE staff if no goto 4
4) Wait for Plex guru to answer
5) No more points available ;

 

[fcpli]

First of all, try to set SIG to e.g. 3111.....
Also in VARI: GFP towards PSTN (VARI D1=1)? Áre you sure UUS2 is not supported (D2=4)? A normal AXE definitely supports all UUS's. These 2 changes might not help. but it's worth trying.
Then, clear history (HIREI). Make a call (faulty one). Check HIMDP.
Print out pclop:unit=slp60;
Start a trace on SLP60, hopefully the traffic is low. Make a call. If it works OK, clear the trace, and try to get a trace on a non-working call. Copy the trace here ("raw" one, not interpreted).
Patcher: RFPUI? Nice trick... This is apparently a cni82. If it is, there is not much to upgrade (which helps in this case). Otherwise, if it is CNI71, the upgrade is necessary.

 

[cuneyt2020]

Hi all,
Thanks for answers,
to patcher: I restarted slp60 and tlp60 but no solution,but i don't think it's needed to upgrade because it was working properly till 3 days ago. even i RFLII LIM=4 but himdp is same.

to HIREI: i have TLU tracer and saw no errors on STUNI in "cause:" field. And also i will ask AXE staff to trace the calls.

to fcpli: i changed sig parameter to rocac:ROU=55,SIG=311110010030;

Would you please write here the new rodap, that you think to work properly so?
And here is pclop:unit=slp60

[tt]

<pclop:unit=slp60;
PATCH LOG DATA

UNIT: SLP60 LIM: 1
CI TYPE STATUS SIZE IA/SIGNO/ADDR CORRSTART
S63673A PROGRAM CONF 74 0002BEA2 00046D58
S63673A PROGRAM CONF 144 0002BEFC 00046DA2
S77583A PROGRAM CONF 46 000289BC 00046E32
S77583A PROGRAM CONF 86 000055C8 00046E60
S77679A REL DATA CONF 34 0000013A 00046EB6
S63871A PROGRAM CONF 60 0002D610 00046ED8
S63888A PROGRAM CONF 54 00002294 00046F14
S63888A PROGRAM CONF 54 000022D2 00046F4A
S63924A PROGRAM CONF 34 0001B3B6 00046F80
S63941A PROGRAM CONF 52 000044B2 00046FA2
S63948A PROGRAM CONF 50 00039B18 00046FD6
S63995A PROGRAM CONF 34 0002780C 00047008
S63995A PROGRAM CONF 52 00027872 0004702A
S64052A PROGRAM CONF 46 0002C852 0004705E
S64097A PROGRAM CONF 68 000261A2 0004708C
S64166A PROGRAM CONF 50 000362A4 000470D0
S65061A PROGRAM CONF 68 00001B7A 00047102
S65061A PROGRAM CONF 44 00001104 00047146
S64253A PROGRAM CONF 46 0000B0BC 00047172
S64253A PROGRAM CONF 48 0000B0C6 000471A0
S64702A PROGRAM CONF 42 0001D016 000471D0
S64702A PROGRAM CONF 42 0001D068 000471FA
S64751A PROGRAM CONF 118 00001EEC 00047224
S64831A PROGRAM CONF 50 0003C424 0004729A
S64831A PROGRAM CONF 50 0003C488 000472CC
S64831A PROGRAM CONF 98 00043BDA 000472FE
S64831A PROGRAM CONF 48 00045332 00047360
S64935A PROGRAM CONF 46 000096FA 00047390
S64935A PROGRAM CONF 46 0000970E 000473BE
S64935A PROGRAM CONF 46 00009D06 000473EC
S64935A PROGRAM CONF 46 00009D1A 0004741A
S64935A PROGRAM CONF 46 0000A0E8 00047448
S64935A PROGRAM CONF 46 0000A0FC 00047476
S65368A PROGRAM CONF 48 00000AE2 000474A4
S65439A PROGRAM CONF 46 00005368 000474D4
S65439A PROGRAM CONF 46 0000539C 00047502
S65444A PROGRAM CONF 40 0004496C 00047530
S65550A PROGRAM CONF 46 0000E25C 00047558
S65231A PROGRAM CONF 46 00008FB2 00047586
S65429A PROGRAM CONF 58 00005232 000475B4
S65532A PROGRAM CONF 42 0000CDC8 000475EE
S65970A PROGRAM CONF 94 00018BE2 00047618
S66205A PROGRAM CONF 54 0001305A 00047676
S66205A PROGRAM CONF 54 00013290 000476AC
S65689A PROGRAM CONF 38 00029AF0 000476E2
S65689A PROGRAM CONF 38 00029C42 00047708
S65788A PROGRAM CONF 60 00045776 0004772E
S67129A PROGRAM CONF 82 00039AA0 0004776A
S66304A PROGRAM CONF 46 0000239E 000477BC
S66304A PROGRAM CONF 46 000023D0 000477EA
S67272A PROGRAM CONF 46 00004598 00047818
S67887A PROGRAM CONF 66 000325AE 00047846
S68886A REL DATA CONF 34 00001843 00047888
S68968A PROGRAM CONF 104 000278D4 000478AA
S68988A PROGRAM CONF 52 0001181A 00047912
S69070A PROGRAM PASS 38 0000BFCE 00047946
S69257A PROGRAM CONF 64 0002EEC0 0004796C
S69257A PROGRAM CONF 34 000363D4 000479AC
S69259A PROGRAM CONF 46 00009828 000479CE
S69259A PROGRAM CONF 46 00009944 000479FC
S69259A PROGRAM CONF 46 000099D6 00047A2A
S69259A PROGRAM CONF 46 00009A1E 00047A58
S69259A PROGRAM CONF 46 00009A64 00047A86
S69259A PROGRAM CONF 48 00009F3C 00047AB4
S69259A PROGRAM CONF 46 0000B41A 00047AE4
S69259A PROGRAM CONF 48 0000BA38 00047B12
S69259A PROGRAM CONF 48 0000BB4C 00047B42
S69259A PROGRAM CONF 48 0000BBBA 00047B72
S69259A PROGRAM CONF 46 0001095C 00047BA2
S69259A PROGRAM CONF 46 00010978 00047BD0
S68643A PROGRAM CONF 58 00022AC2 00047BFE
S69406A PROGRAM CONF 94 0000AF10 00047C38
S69695A PROGRAM CONF 76 00009AB8 00047C96
S69807A PROGRAM CONF 46 00007328 00047CE2
S70314A PROGRAM CONF 160 000128D6 00047D10
S70314A PROGRAM CONF 156 00027458 00047DB0
S70616A PROGRAM CONF 60 00027814 00047E4C
S77338A PROGRAM CONF 40 0001BB96 00047E88
S77583A PROGRAM CONF 50 00029F04 00047EB0
S76525A PROGRAM CONF 52 00019224 00047EE2
S78787A PROGRAM CONF 60 000278E4 00047F16
S79225A REL DATA CONF 34 0000010C 00047F52
END
[/tt]


Now it's morning and this problem was occured in high traffic yesterday. So i'll try tracing and write here when the problem occurs in high traffic...


By the way another problem is the busy tone on GSM operator.
When i make a call to GSM operator, there is no busy tone.. i get again line locked out message.. But this is not a new case. It was as it was before. Can it be fixed by the parameters on md or is it AXE10 problem?
Rgrds.

 

[cuneyt2020]

Now after changing SIG parameter i gave hirei and now here is the himdp result

[tt]

<HIEDP;
TIME DATE
10:02:25 02FEB05
LIM EVENTS OVERWRITTEN OLDEST EVENT NEWEST EVENT
EVENTS
004 9 0 09:53:45 02FEB05 09:53:59 02FEB05

END
<HIMDP;

DIAGNOSTICS FROM OPERATING SYSTEM
TIME DATE
10:03:58 02FEB05
NO INFORMATION STORED IN LIM 001
NO INFORMATION STORED IN LIM 002
NO INFORMATION STORED IN LIM 003
DIAGNOSTICS FROM LIM 004

TIME DATE ERROR CODE
09:53:59 02FEB05 H'60
ADDRESS CONTROL FAILURE
LOGICAL PROGRAM ERROR ADDRESS = 02001002
ENTER
SWSW A-LEVEL SIGNAL CLEAR (H'0066)
FROM TLP60 (H'3CD) EXE A IN LIM 004
TO RMPS1 (H'319) EXE A IN LIM 004
NUMBER OF DATA BYTES IN SIGNAL = 7
WITH 0 1 2 3 4 5 6 7 8 9
000 24 B0 00 DA 03 CD 04


TIME DATE ERROR CODE
09:53:54 02FEB05 H'13
FAULTY POINTER
LOGICAL PROGRAM ERROR ADDRESS = 02002718
ENTER
SWSW A-LEVEL SIGNAL ACTRERTRUCMI (H'00D2)
FROM RMPS3 (H'31B) EXE A IN LIM 004
TO CMPS8 (H'2D9) EXE A IN LIM 004
NUMBER OF DATA BYTES IN SIGNAL = 19
WITH 0 1 2 3 4 5 6 7 8 9
000 FF 74 00 FF FF FF FF 00 FF FF
010 08 03 CD 00 00 FF FF FF FF


TIME DATE ERROR CODE
09:53:54 02FEB05 H'13
FAULTY POINTER
LOGICAL PROGRAM ERROR ADDRESS = 02000FC0
ENTER
SWSW A-LEVEL SIGNAL STORERMES (H'00B4)
FROM RMPS3 (H'31B) EXE A IN LIM 004
TO CMPS8 (H'2D9) EXE A IN LIM 004
NUMBER OF DATA BYTES IN SIGNAL = 20
WITH 0 1 2 3 4 5 6 7 8 9
000 FF 74 FF FF FF FF FF FF FF FF
010 FF FF FF FF FF FF FF FF FF 00
STACK ADDRESS = 02004DB4
SIGNAL SEND ADDRESS = 02008AAE


TIME DATE ERROR CODE
09:53:54 02FEB05 H'60
ADDRESS CONTROL FAILURE
LOGICAL PROGRAM ERROR ADDRESS = 02001002
ENTER
SWSW A-LEVEL SIGNAL CLEAR (H'0066)
FROM TLP60 (H'3CD) EXE A IN LIM 004
TO RMPS1 (H'319) EXE A IN LIM 004
NUMBER OF DATA BYTES IN SIGNAL = 7
WITH 0 1 2 3 4 5 6 7 8 9
000 23 AF 00 DB 03 CD 04


TIME DATE ERROR CODE
09:53:49 02FEB05 H'13
FAULTY POINTER
LOGICAL PROGRAM ERROR ADDRESS = 02002718
ENTER
SWSW A-LEVEL SIGNAL ACTRERTRUCMI (H'00D2)
FROM RMPS3 (H'31B) EXE A IN LIM 004
TO CMPS8 (H'2D9) EXE A IN LIM 004
NUMBER OF DATA BYTES IN SIGNAL = 19
WITH 0 1 2 3 4 5 6 7 8 9
000 FF 73 00 FF FF FF FF 00 FF FF
010 04 03 CD 00 00 FF FF FF FF


TIME DATE ERROR CODE
09:53:49 02FEB05 H'13
FAULTY POINTER
LOGICAL PROGRAM ERROR ADDRESS = 02000FC0
ENTER
SWSW A-LEVEL SIGNAL STORERMES (H'00B4)
FROM RMPS3 (H'31B) EXE A IN LIM 004
TO CMPS8 (H'2D9) EXE A IN LIM 004
NUMBER OF DATA BYTES IN SIGNAL = 20
WITH 0 1 2 3 4 5 6 7 8 9
000 FF 73 FF FF FF FF FF FF FF FF
010 FF FF FF FF FF FF FF FF FF 00


TIME DATE ERROR CODE
09:53:49 02FEB05 H'60
ADDRESS CONTROL FAILURE
LOGICAL PROGRAM ERROR ADDRESS = 02001002
ENTER
SWSW A-LEVEL SIGNAL CLEAR (H'0066)
FROM TLP60 (H'3CD) EXE A IN LIM 004
TO RMPS1 (H'319) EXE A IN LIM 004
NUMBER OF DATA BYTES IN SIGNAL = 7
WITH 0 1 2 3 4 5 6 7 8 9
000 25 AD 00 DC 03 CD 04
STACK ADDRESS = 0200295A
SIGNAL SEND ADDRESS = 0200FB60


TIME DATE ERROR CODE
09:53:45 02FEB05 H'13
FAULTY POINTER
LOGICAL PROGRAM ERROR ADDRESS = 02002718
ENTER
SWSW A-LEVEL SIGNAL ACTRERTRUCMI (H'00D2)
FROM RMPS3 (H'31B) EXE A IN LIM 004
TO CMPS8 (H'2D9) EXE A IN LIM 004
NUMBER OF DATA BYTES IN SIGNAL = 19
WITH 0 1 2 3 4 5 6 7 8 9
000 FF 71 00 FF FF FF FF 00 FF FF
010 FF FF FF 00 00 FF FF FF FF
STACK ADDRESS = 02004DB8
SIGNAL SEND ADDRESS = 02006B60


TIME DATE ERROR CODE
09:53:45 02FEB05 H'13
FAULTY POINTER
LOGICAL PROGRAM ERROR ADDRESS = 02000FC0
ENTER
SWSW A-LEVEL SIGNAL STORERMES (H'00B4)
FROM RMPS3 (H'31B) EXE A IN LIM 004
TO CMPS8 (H'2D9) EXE A IN LIM 004
NUMBER OF DATA BYTES IN SIGNAL = 20
WITH 0 1 2 3 4 5 6 7 8 9
000 FF 71 FF FF FF FF FF FF FF FF
010 FF FF FF FF FF FF FF FF FF 00
STACK ADDRESS = 02004DB4
SIGNAL SEND ADDRESS = 02008AAE


END

[/tt]
I don't know whether it's related with it or not.. Because there are two E1s in route 55 and one of them is in lim 3 and other one is lim4

 

[fcpli]

This is CNI82. The patches seem to be OK.
HIMDP:
Well, I don't see any relation here, this is rerouting to tie-line, and the cause is "faulty pointer".
The rodap vari could be 05400000, but if you actually ARE using GFP,keep the d1 as "1". Try to figure out (after the changes), if there are any changes in the fault frequency.
Also, besides SLP60, trace (at the same time) also TLP60!

good luck!

 

[cuneyt2020]

Well, the updated result is, our GSM operator says, some ports are blocked on their side even our side is seemed to be ok.
And they try to unblock them. So the calls which are going thrugh these blocked trunks are getting "line locked out" message.

Anyway we can not get busy tone from GSM operator, it's still problem. But succesfus calls are related with GSM operators trunks.

 

[patcher]

Okay, if its not to be upgraded; you trace it. Do you have SAM Tools? We need to use signal trace interpreter. This is the only way to pin point your problem rather than we wishi washi(trial&error approach).

Commands to use:

STISR;
STUNI:LIM=4,UNIT=SLP60,MSKSIG=A1&02,STORE=YES;
STTSS:TRI=1,SIZE=500;
STTSI:TRI=1,ROT=YES;

Then start making calls in LIM4. If the call fails then stop the trace using STTSE:TRI=1;

Print and log the trace using STRAP:TRI=1; Then use STI to interpret it.

Check the last call you made by checking the last send SETUP. In this signal you can see your number and also the dialled number. You can also use filter by selecting call reference id.

In this tool, you can pin point exactly what happen to the call and what reason and why the call fail.

 

[patcher]

Forgot, your system is BC9, you need to edit the file and change DLRDATA to DRLDATALONG so that STI will interpret it correctly.

 

[fcpli]

Cuney: For busy tone you could try this patch. If it doesn't help, just passivate it.

PCASI:UNIT=SLP60,CI=S66641A,REV=2-R4A,IA=12908,RA=12910,BYTE=0;
TST.B ($247E,A1); ! CSUPINBANDTONE !
BNE L1;
CMP.B #31,($13A,A6); !TCAUSE !
BEQ L1;
JMP (PROGSTART+$12960); ! LABEL1 !
L1:;
END;
!A;
PCACS:UNIT=SLP60,CI=S66641A;
Y;
PCCOS:UNIT=SLP60,CI=S66641A;
Y;

fcpli

 

[cuneyt2020]

Hi fcpli,
It's unfortunately not the solution ...i pcpas the patch...
Still same...
I ll send here the stuni result

Regards...

 

[cuneyt2020]

Well, i got the trace and saw that when i made an outbound call to GSM phone which is busy i got an error such as 9F Note that, we make calls from private network(Bc10 >>>>BC9>>>AXe10)

09.03.15.880
<- Incoming
Call Reference: #633
Message: SETUP
Bearer Capability
Coding Standard: CCITT
Information transfer capability: Speech
Transfer mode: Circuit mode
Information transfer rate: 64 kbit/s
User information layer 1 protocol: CCITT G.711 A-Law
B-Channel: 26
Facility
Network protocol profile: Networking Extensions
Progress Indicator
Coding Standard: ISO/IEC standard (ECMA)
Location: Network beyond the interworking point
Progress Description: 06
Network-specific facilities: 9FAA
Calling Party Number
Type of number: Unknown
Numbering plan: ISDN/telephony numbering plan
Presentation indicator: Presentation allowed
Screening indicator: User-provided, verified and passed
Digits: 89100
Called Party Number
Type of number: Unknown
Numbering plan: ISDN/telephony numbering plan
Digits: 821805325933362
Transit Counter: 0

09.03.15.960
-> Outgoing
Call Reference: #633
Message: CALL PROCEEDING
B-Channel: 26

09.03.16.000
-> Outgoing
Call Reference: #633
Message: PROGRESS
Progress Indicator
Coding Standard: ISO/IEC standard (ECMA)
Location: User
Progress Description: Interworking with a public network

09.03.20.400
-> Outgoing
Call Reference: #633
Message: ALERTING
Progress Indicator
Coding Standard: CCITT standardized coding
Location: Public network serving the remote user
Progress Description: In-band information is now available
Party Category: Unknown

09.03.22.280
-> Outgoing
Call Reference: #633
Message: DISCONNECT
Cause: Unknown Reason: 9F

09.03.22.520
<- Incoming
Call Reference: #633
Message: RELEASE

09.03.22.540
-> Outgoing
Call Reference: #633
Message: RELEASE COMPLETE




and get tri-tone

 

[patcher]

You confuse me now, why your trace is incoming setup? What we need is outgoing setup. And BTW why BC10 appear on a blue moon? Is the caller from BC10? You had to be exact. From your previous thread, there is no BC10 mentioned here. Where is the problem now? Is it busy when calling from BC10 or BC9 to AXE? You had to be exact so that we can fix your fault. If the fault is BC9 to AXE, we need outgoing setup(trace BC9) and not incoming setup from BC10.

 

[fcpli]

Patcher is right. This confuses me too. Also the trace seems to be (maybe) incoming AXE (?). If the call is from BC10, and not working, try to make a call from BC9. Is this working OK? If not, we need also rodap/rocap between BC9/BC10. And the trace!

 

[cuneyt2020]

Hi patcher,
Sometimes it's difficult to explain the whole topology here...When trying to explain the whole topology that's boring for people and not get any response. So i tried to explain the related configuration in my first message.
BC9 system is the tandem switch connected to AXE10...
The staff is in other location connected to BC10.
On my last response, i said that

"Note that, we make calls from private network(Bc10 >>>>BC9>>>AXe10)"

So, i make calls from BC10 system - a qsig connection between bc10 and bc9- first the call goes to the BC9 and then GSM network (AXE10)

So in trace result the incoming call means call comes from BC10 to this switch (BC9)
Then the trace says "there is an outgoing attempt" This is the outgoing attempt to AXE10 GSM network. But gets a disconnect tone with an error 9F... And then incoming "release" signal from AXE10..

Hope this is clear for your help..
Thanks for your interest
Rgrds.

 

[cuneyt2020]

Ok guys i'll try to make outbound call directly from BC9 to AXE10 and will localize the problem on monday at work..Also i'll send you the rodap rocap between bc9 and bc10
Rgrds.

 

[patcher]

Hello cuneyt2020, your trace is only incoming call from BC10 to BC9. The traffic scenario you've done is calling out from BC10 via BC9 to AXE. This means the trace you posted is only an incoming call from BC10 and the trace is collected in BC9. The outgoing message in the trace is from BC9 to BC10 because the call reference id are all the same. The same means, this is only 1 call direction. You need to STUNI it again in BC9 the call out. The trace should be outgoing setup. Remember the traffic scenario we are talking about here is calling AXE.

 

[cuneyt2020]

Hi all,
Now i got the trace again. The call direction is from BC9 to AXE10 But i can't see the calling number in this log .But The called number is my number and so the test is ok. I got the same error.

9.30.35.960
-> Outgoing
Call Reference: #312
Message: SETUP
Bearer Capability
Coding Standard: CCITT
Information transfer capability: Speech
Transfer mode: Circuit mode
Information transfer rate: 64 kbit/s
User information layer 1 protocol: CCITT G.711 A-Law
B-Channel: 10
Progress Indicator
Coding Standard: CCITT standardized coding
Location: User
Progress Description: Origination address is non ISDN
Called Party Number
Type of number: Unknown
Numbering plan: ISDN/telephony numbering plan
Digits: 05325933362

09.30.36.040
<- Incoming
Call Reference: #312
Message: CALL PROCEEDING
B-Channel: 23

09.30.36.360
<- Incoming
Call Reference: #312
Message: DISCONNECT
Cause: Unknown Reason: 9F
09.30.36.480
-> Outgoing
Call Reference: #312
Message: RELEASE

09.30.36.520
<- Incoming
Call Reference: #312
Message: RELEASE COMPLETE

Also another info is, when e person calls from DTS on BC9 system to AXE10, he gets "inter-digit time out" message on busy GSM numbers.No problem on idle GSM numbers.
But the problem is ,as i mentioned before, related with BC9 and AXE10 route system.

If you need BC10 and BC9 qsig parameters i can write here..
Thanks for your help

 

[patcher]

Its is very clear in your trace that AXE disconnect the call. And the caused value is unknown. Is there anybody in AXE side to trace it and pinpoint why they disconnect the call? For the meantime you cannot do anything in MD side unless the AXE guys will tell us what is wrong and why they disconnect it. Do they recieved this call? Let them trace it too.