error when installing E1 / DIUN2

[slamet riyadi]

hi everyone ... can anyone help me with the following error. This is an error in openscape 4000 when installing the DIUN2 module. The following error message I took from HISTA:

<STA-HISTA:SEARCH,2019-10-01/15:00,2019-10-01/15:16;
STA-HISTA:SEARCH,2019-10-01/15:00,2019-10-01/15:16;
H500: AMO HISTA STARTED
H1: 00031 ERROR MESSAGES FOUND

F5645 E8 N6237 OUT SERV BPA CIRCUIT L1 ERROR S0 19-10-01 15:00:01
ALARM CLASS:SWU-PER:004
P202:LTG1 :LTU1 :010: 01 : 0 Q2344-X100 SLMU/1 BST:01 PLS:-16
REASON:03H LOST FRAME (RED) (LOCAL ALARM)
FORMAT:36 DEVICE NAME: ONLYSYM

F5992 E8 N6238 IN SERV BPA CIRCUIT LX ACTIVE S0 19-10-01 15:00:38
ALARM CLASS:SWU-PER:004
P202:LTG1 :LTU1 :010: 01 : 0 Q2344-X100 SLMU/1 BST:01 PLS:-16
REASON:07H LAYER 1 ACTIVE (GREEN)
FORMAT:36 DEVICE NAME: ONLYSYM

F5645 E8 N6239 OUT SERV BPA CIRCUIT L1 ERROR S0 19-10-01 15:01:39
ALARM CLASS:SWU-PER:004
P202:LTG1 :LTU1 :010: 01 : 0 Q2344-X100 SLMU/1 BST:01 PLS:-16
REASON:03H LOST FRAME (RED) (LOCAL ALARM)
FORMAT:36 DEVICE NAME: ONLYSYM

F5354 E8 N6240 OUT SERV BPA BOARD SECONDARY OUT ATTEND L 19-10-01 15:01:43
ALARM CLASS:CENTRAL:002
P205:LTG1 :LTU4 :006: 00 : 0 Q2196-X DIU-N2/1 BST:01 PLS:-07
FORMAT:22
6440AE012A1A00000000000406000100 01000000000000000000000000000000
00000000000000000000000000000000 00000000000000000000000000000000
00000000000000000000000000000000 00000000000000000000000000000000
0000000000

F5350 E8 N6241 IN SERV BPA BOARD SECONDARY IN ATTEND L 19-10-01 15:02:03
ALARM CLASS:CENTRAL:002
P205:LTG1 :LTU4 :006: 00 : 0 Q2196-X DIU-N2 BST:01 FW: ????-?
FORMAT:22
6440AE014F1A01000000000406014022 00000000000000000000000000000000
00000000000000000000000000000000 00000000000000000000000000000000
00000000000000000000000000000000 00000000000000000000000000000000
0000000000

F5412 E8 N6242 OUT SERV BPA CIRCUIT L1 ERROR 19-10-01 15:02:15
ALARM CLASS:CENTRAL:002
P205:LTG1 :LTU4 :006: 00 : 0 Q2196-X DIU-N2/1 BST:01 PLS:-07
REASON:04H NO SIGNAL (RED) (LOCAL ALARM)
FORMAT:36 DEVICE NAME: S2CONN

F5992 E8 N6243 IN SERV BPA CIRCUIT LX ACTIVE S0 19-10-01 15:02:16
ALARM CLASS:SWU-PER:004
P202:LTG1 :LTU1 :010: 01 : 0 Q2344-X100 SLMU/1 BST:01 PLS:-16
REASON:07H LAYER 1 ACTIVE (GREEN)
FORMAT:36 DEVICE NAME: ONLYSYM

F5645 E8 N6244 OUT SERV BPA CIRCUIT L1 ERROR S0 19-10-01 15:03:16
ALARM CLASS:SWU-PER:004
P202:LTG1 :LTU1 :010: 01 : 0 Q2344-X100 SLMU/1 BST:01 PLS:-16
REASON:03H LOST FRAME (RED) (LOCAL ALARM)
FORMAT:36 DEVICE NAME: ONLYSYM

F4684 E8 N6245 NO ACT BPA CDR MAINTENANCE 19-10-01 15:03:48
ALARM CLASS:CENTRAL:029
FORMAT:33
CDR: CDB POOL FULL - LOSS OF DATA IN SWU

F5992 E8 N6246 IN SERV BPA CIRCUIT LX ACTIVE S0 19-10-01 15:03:53
ALARM CLASS:SWU-PER:004
P202:LTG1 :LTU1 :010: 01 : 0 Q2344-X100 SLMU/1 BST:01 PLS:-16
REASON:07H LAYER 1 ACTIVE (GREEN)
FORMAT:36 DEVICE NAME: ONLYSYM

F5645 E8 N6247 OUT SERV BPA CIRCUIT L1 ERROR S0 19-10-01 15:04:54
ALARM CLASS:SWU-PER:004
P202:LTG1 :LTU1 :010: 01 : 0 Q2344-X100 SLMU/1 BST:01 PLS:-16
REASON:03H LOST FRAME (RED) (LOCAL ALARM)
FORMAT:36 DEVICE NAME: ONLYSYM

F5992 E8 N6248 IN SERV BPA CIRCUIT LX ACTIVE S0 19-10-01 15:05:31
ALARM CLASS:SWU-PER:004
P202:LTG1 :LTU1 :010: 01 : 0 Q2344-X100 SLMU/1 BST:01 PLS:-16
REASON:07H LAYER 1 ACTIVE (GREEN)
FORMAT:36 DEVICE NAME: ONLYSYM

F5645 E8 N6249 OUT SERV BPA CIRCUIT L1 ERROR S0 19-10-01 15:06:32
ALARM CLASS:SWU-PER:004
P202:LTG1 :LTU1 :010: 01 : 0 Q2344-X100 SLMU/1 BST:01 PLS:-16
REASON:03H LOST FRAME (RED) (LOCAL ALARM)
FORMAT:36 DEVICE NAME: ONLYSYM

F5412 E8 N6250 OUT SERV BPA CIRCUIT L1 ERROR 19-10-01 15:06:55
ALARM CLASS:CENTRAL:002
P205:LTG1 :LTU4 :006: 00 : 0 Q2196-X DIU-N2/1 BST:01 PLS:-07
REASON:06H REMOTE ALARM (YELLOW) (DISTANT ALARM)
FORMAT:36 DEVICE NAME: S2CONN

F5418 E8 N6251 IN SERV BPA CIRCUIT LX ACTIVE 19-10-01 15:06:55
ALARM CLASS:CENTRAL:002
P205:LTG1 :LTU4 :006: 00 : 0 Q2196-X DIU-N2/1 BST:01 PLS:-07
REASON:07H LAYER 1 ACTIVE (GREEN)
FORMAT:36 DEVICE NAME: S2CONN

F5412 E8 N6252 OUT SERV BPA CIRCUIT L1 ERROR 19-10-01 15:06:55
ALARM CLASS:CENTRAL:002
P205:LTG1 :LTU4 :006: 00 : 0 Q2196-X DIU-N2/1 BST:01 PLS:-07
REASON:04H NO SIGNAL (RED) (LOCAL ALARM)
FORMAT:36 DEVICE NAME: S2CONN

F5418 E8 N6253 IN SERV BPA CIRCUIT LX ACTIVE 19-10-01 15:06:56
ALARM CLASS:CENTRAL:002
P205:LTG1 :LTU4 :006: 00 : 0 Q2196-X DIU-N2/1 BST:01 PLS:-07
REASON:07H LAYER 1 ACTIVE (GREEN)
FORMAT:36 DEVICE NAME: S2CONN

F5418 E8 N6254 IN SERV BPA CIRCUIT LX ACTIVE 19-10-01 15:06:56
ALARM CLASS:CENTRAL:002
P205:LTG1 :LTU4 :006: 00 : 0 Q2196-X DIU-N2/1 BST:01 PLS:-07
REASON:09H LAYER 3 ACTIVE
FORMAT:36 DEVICE NAME: S2CONN


thanks

 

[Moriendi]

The last messages show it's working

F5418 E8 N6253 IN SERV BPA CIRCUIT LX ACTIVE 19-10-01 15:06:56
ALARM CLASS:CENTRAL:002
P205:LTG1 :LTU4 :006: 00 : 0 Q2196-X DIU-N2/1 BST:01 PLS:-07
REASON:07H LAYER 1 ACTIVE (GREEN)
FORMAT:36 DEVICE NAME: S2CONN

F5418 E8 N6254 IN SERV BPA CIRCUIT LX ACTIVE 19-10-01 15:06:56
ALARM CLASS:CENTRAL:002
P205:LTG1 :LTU4 :006: 00 : 0 Q2196-X DIU-N2/1 BST:01 PLS:-07
REASON:09H LAYER 3 ACTIVE
FORMAT:36 DEVICE NAME: S2CONN

What's the problem?

 

[slamet riyadi]

@Moriendi
the status is still GNNR / CP. and now the status is ready ... but when making a call you can only ring but there is no sound. I do the integration between Openscape 4000 (DIUN2) with Openscape Business Server.

 

[adibv]

GENNR status means : generated but not ready.
Try with:
REST-DSSU:BCHAN...
or
ACT-DSSU:BCHAN ...

 

[Moriendi]

Yes for GENNR I'd res-dssu with BCHAN (1&&30), and I'd probably do it with PEN as well.

If it was completely dead though, you wouldn't be able to make a call, but you can, so that's strange, but then there is no speech, which is also strange. Sometimes no speech on QSIG circuit is caused by mismatched channels in the QSIG protocol, some protocols indicate 1&&30 in the D channel, some use 1&15, 16 for sig, 17&&31. They both work fine 1&&15, but if you start to use the channels on the 17&&31 side (like when you have chosen descending channel selection), one side puts the voice on 30, the other on 31. With a tester you can hear the audio on the two different channels. Solution is to make sure both sides are using the same QSIG variant.

So check your busy channel with dis-sdsu when you have a bad call in progress, is it choosing channels ASCending or DeSCending (in 4K, that parameters is SRCHMODE in TDCSU). Although how you got a call on it with GENNR status, I have no idea.