SWA-SUBSEC DID
(A)....................... (B).................
(C)........................... (D) (E)
-----------------------------------------------------------------
E R R O R
FMM NAME : (3)..................... ID : (4)..
ERRORTYPE : (5) GSM : (6).....
ERROR NUMBER : (7).. SOURCE : (8).....
==> (9)
I SCO-TYPE(11)I (12)I SUBG I FACIL I TOC
I P I I (19)I DESTDID (20)I (21).............
-------------------------------------------------------------------
I (24)... I (25) I (26) I I I I I(31)I(32)
(35).... (36).... (37).... (38).... (39).. (40).. (41)..........
REPORT REFERENCE NUMBER = 6085
| Par. No. | Meaning | Remarks |
|---|---|---|
| (A) | Command name | |
| (B) | Main execution result | |
| (C) | Result part type | |
| (D) | Result part number | |
| (E) | Continuation indicator | |
| (3) | FMM Name | Only for system expert |
| (4) | FMM oder SSM ID | Only for system expert |
| (5) | Error type | Only for system expert |
| (6) | GSM | Only for system expert |
| (7) | error point | Location of the error, only for
system expert |
| (8) | Source | Only for system expert |
| (9) | Single report | |
| (11) | Source type header | will only be displayed, if the
DID task depends on the source type |
| (12) | Incoming trunkgroup number header | will only be displayed if the DID
task depends on the incoming trunkgroup number |
| (19) | Outgoing trunkgroup number header | will only be displayed if the DID
task depends on the outgoing trunkgroup number |
| (20) | Destination for DID header | will only be displayed if the DID
task depends on the Destination for DID (-> prefix) |
| (21) | DID task header | |
| (24) | source type | |
| (25) | Incoming trunkgroup number | |
| (26) | Subscribergroup | |
| (31) | Outgoing trunkgroup number | |
| (32) | Destination for DID | |
| (35) | DID task | |
| (36) | Timer ID | |
| (37) | Nature of address | |
| (38) | Tone type | |
| (39) | 1. value | |
| (40) | 2. value | |
| (41) | Digits |
| Key Parameter | Contents / Meaning | Action | ||
|---|---|---|---|---|
| 1 | 2 | 3 | ||
| (9) | DATA UPDATE TRANSACTION CAN NOT BE CLOSED . . . . | D | ||
| (9) | DATA UPDATE TRANSACTION CAN NOT BE OPENED . . . . | D | ||
| (9) | DATA UPDATE TRANSACTION CAN NOT BE ROLLED BACK . . | D | ||
| (9) | DEPENDENCY IS NOT GIVEN COMPLETELY . . . . . . . . | C | ||
| (9) | KEY PARAMETER DOES NOT EXIST . . . . . . . . . . . | E | ||
| (9) | REFERENCE DOES NOT EXIST . . . . . . . . . . . . . | A | ||
| (9) | THE DID ORJ DATA ARE NOT INITIALIZED . . . . . . . | F | ||
| (9) | TOO MANY NEW DEPENDENCIES . . . . . . . . . . . . | B | ||
| Action | Meaning |
|---|---|
| A | Use an existing reference of the key parameter and repeat the command. |
| B | You can only increase the dependency one time with one command. A higher increase of the dependency has to be created with several sequential commands. |
| C | Repeat the command with all key parameters which the concerning DID task depends on. |
| D | Repeat the command after some minutes. If this error occurs several times, you should inform the system expert. |
| E | Select an existing key parameter and repeat the command. |
| F | Start the initialization (START-INIT-DID) and repeat the command. |