Octel 200 RELEASE S.4 question

[smetse]

When I try to modify or delete the mailbox, I get this error message:
"User 3001 is currently LOGGED-ON or DIRECTORY IN USE".
And I am not allowed to do anything with this mailbox.

Can anybody please help me?

 

[doktor]

Try to post the ".L SLOT table". It will show the hardware installed in the system.
I am mostly interested in watching if you are using analog lines or digital lines between th OCTEL and the Definity.
These lines between the systems could be disconnected for a while, an dthen reconnected to get your mailbox out of the dead-lock.
A restart will of course unlock this dead-lock connection, but (maybe) disconnecting the lines between the systems, also can do this.
///doktor

 

[smetse]

doktor,

Here is the SLOT table:


SLOT CARD TYPE PORT EXTENSION# COS MODE OUTCALL TEST SYS
---- ---------- ---- ---------- --- ---- ------- ---- ---
1 PICATT 1 6050 254 AX YES NO 1
2 6051 254 AX YES NO 2
3 6052 254 AX YES NO 3
4 6053 254 AX YES NO 4
5 6054 254 AX YES NO 5
6 6055 254 AX YES NO 6
7 6056 254 AX YES NO 7
8 6057 254 AX YES NO 8
9 6058 254 AX YES NO 9
10 6059 254 AX YES NO 10
11 6060 254 AX YES NO 11
12 6061 254 AX YES NO 12

Message Waiting Link= NONE

LSP table: PIC_AT&T
PRIMARY SYNC RECEIVER OF CLOCK



SLOT CARD TYPE PORT EXTENSION# COS MODE OUTCALL TEST SYS
---- ---------- ---- ---------- --- ---- ------- ---- ---
2 PICATT 1 6062 254 AX YES NO 13
2 6063 254 AX YES NO 14

Message Waiting Link= 2 ** DEFAULT **
COS= 10 11 15 20 21

LSP table: PIC_AT&T
SECONDARY SYNC RECEIVER OF CLOCK

And here is the first page of the "display station 6050" from the Definity:

display station 6050 Page 1 of 5
STATION

Extension: 6050 Lock Messages? n BCC: 0
Type: 7405D Security Code: TN: 1
Port: 01B1101 Coverage Path 1: COR: 81
Name: D-6050 Coverage Path 2: COS: 2
Hunt-to Station:

STATION OPTIONS
Loss Group: 2
Data Module? n Message Lamp Ext: 6050
Display Module? y Feature Module? n
Display Language: english Coverage Module? n

Media Complex Ext:
IP SoftPhone? n


Hope it makes sense for you.
Thank you very much.

 

[doktor]

Yes, it makes sense.
Try to call from your PBX, the AVAYA Definity G3si V8.2 to the OCTEL 200 on extension number 6057 (=port 8).
According to the @PS you posted earlier, this port should be busy.
If you for a short while remove the cable on the back of the OCTEL 200 in SLOT=1,(this is SLOT P1 at the back of the OCTEL 200) and put it back again, you should be able to get the system out of this dead-lock.

Let me know your progress.

///doktor

 

[jon24422531]

Perhaps when that is done it might be an idea to check that the system is correctly patched up. What software release is it at now, and what patches are applied (if any)?

The software relaease can be found at the top of the screen when logging in or else lsit the features
@L F

The patches can be found by typing
@PAT STAT

Jon

http://www.telecom-stuff.com

http://www.jonschofield.com

 

[doktor]

Yes! We will also need to know, what Jon is asking...
///doktor

 

[smetse]

doktor,
When I call 6057, sometimes it is busy, but most of the time it just rings and rings, and it never lets me through. So I think you are right (as usual!), this is the faulty port. I will unplug and plug in the cable today after work hours, and I will let you know the result.


Jon,

Here is what you are asking for:


@l f

---------------- SYSTEM SOFTWARE RELEASE S.4.0.0-2 (04/30/99) ----------------
WED 11/15 09:06:44 2006 DIGIDES ID:xxxxxx S/N:xxxxxx PBX:23

MODEL TYPE: OCTEL 200
SERIAL NUMBER: xxxxxx
FEATURE PACKAGES:
SW-40001 SW-40003 SW-40004 SW-40007 SW-40008 SW-40009 SW-40019 SW-40023
SW-40031 SW-40034 SW-40047
--------------------------------------------------------------
Authorized Used Unused Installed
---------------------------------------------------
Ports : Analog -- 0 0 0
Fax -- 0 0 0
DSP 20 0 20 0
PIC 14 14 0 24

MBXs : Voice 475 464 11 5000
Non-Voice 4536 5 4531 5000
VMB 0 0 0 5000
Fax 0 0 0 5000

Storage : Hours 35 18 17 203
--------------------------------------------------------------

MAXIMUM NUMBER OF DRIVES: 3
MAXIMUM NUMBER OF PORTS: 64
MAXIMUM NUMBER OF SCHEDULE TABLE ENTRIES: 8
NUMBER OF LANGUAGES: 1



@pat stat

Patch# Date Applied Target File name
______ __________________ ____________________ ______________
1 04/30/99 14:04:09 CPU memory, disk PATS400.001
4 04/30/99 14:04:44 CPU memory, disk PATS400.004
5 04/30/99 14:05:15 CPU memory, disk PATS400.005
6 04/30/99 14:05:46 CPU memory, disk PATS400.006
7 04/30/99 14:06:38 CPU memory, disk PATS400.007
8 04/30/99 14:07:11 CPU memory, disk PATS400.008
9 04/30/99 14:07:42 CPU memory, disk PATS400.009
10 04/30/99 14:08:54 CPU memory, disk PATS400.010
11 12/14/99 20:19:29 CPU memory, disk PATS400.011
12 04/30/99 14:09:08 CPU memory, disk PATS400.012
13 04/30/99 14:01:02 CPU memory, disk PATS40V.013
15 04/30/99 14:09:34 CPU memory, disk PATS400.015
16 04/30/99 14:10:06 CPU memory, disk PATS400.016
18 12/14/99 20:20:00 CPU memory, disk PATS400.018
19 12/14/99 20:20:29 CPU memory, disk PATS400.019
20 12/14/99 20:20:59 CPU memory, disk PATS400.020
21 12/14/99 20:21:20 CPU memory, disk PATS400.021
25 12/14/99 20:21:49 CPU memory, disk PATS400.025
29 12/14/99 20:22:20 CPU memory, disk PATS400.029
34 12/14/99 20:22:51 CPU memory, disk PATS400.034
39 12/14/99 20:23:25 CPU memory, disk PATS400.039
41 12/14/99 20:23:55 CPU memory, disk PATS400.041
42 12/14/99 20:24:25 CPU memory, disk PATS400.042
44 01/11/06 22:03:55 CPU memory, disk PATS400.044
45 12/14/99 20:25:14 CPU memory, disk PATS400.045
47 12/14/99 20:25:44 CPU memory, disk PATS400.047
49 12/14/99 20:26:04 CPU memory, disk PATS400.049
52 01/11/06 22:04:32 CPU memory, disk PATS400.052
56 12/14/99 20:26:37 CPU memory, disk PATS400.056
58 01/11/06 22:05:02 CPU memory, disk PATS400.058
59 12/14/99 20:26:56 CPU memory, disk PATS400.059
61 01/11/06 22:05:22 CPU memory, disk PATS400.061
64 12/14/99 20:27:18 CPU memory, disk PATS400.064
65 12/14/99 20:27:47 CPU memory, disk PATS400.065
66 01/11/06 22:05:52 CPU memory, disk PATS400.066
67 12/14/99 20:28:18 CPU memory, disk PATS400.067
68 01/11/06 22:06:24 CPU memory, disk PATS400.068
72 12/14/99 20:29:48 CPU memory, disk PATS400.072
73 01/11/06 22:07:05 CPU memory, disk PATS400.073
77 01/11/06 22:07:37 CPU memory, disk PATS400.077
78 01/11/06 22:08:08 CPU memory, disk PATS400.078
84 01/11/06 22:08:40 CPU memory, disk PATS400.084
85 12/17/99 09:22:22 CPU memory, disk PATS400.085
88 12/14/99 20:30:08 CPU memory, disk PATS400.088
89 01/11/06 22:09:04 CPU memory, disk PATS400.089
90 01/11/06 22:09:29 CPU memory, disk PATS400.090
91 12/17/99 09:22:44 CPU memory, disk PATS400.091
94 12/14/99 20:30:29 CPU memory, disk PATS400.094
96 01/11/06 22:09:51 CPU memory, disk PATS400.096
97 12/17/99 09:23:10 CPU memory, disk PATS400.097
101 01/11/06 22:10:21 CPU memory, disk PATS400.101
103 12/17/99 09:23:30 CPU memory, disk PATS400.103
105 12/14/99 20:31:28 CPU memory, disk PATS400.105
106 12/14/99 20:31:48 CPU memory, disk PATS400.106
109 12/14/99 20:32:17 CPU memory, disk PATS400.109
110 12/14/99 20:32:48 CPU memory, disk PATS400.110
112 01/11/06 22:10:52 CPU memory, disk PATS400.112
113 12/17/99 09:24:35 CPU memory, disk PATS400.113
114 01/11/06 22:11:21 CPU memory, disk PATS400.114
115 12/14/99 20:33:23 CPU memory, disk PATS400.115
116 01/11/06 22:11:42 CPU memory, disk PATS400.116
118 01/11/06 22:12:02 CPU memory, disk PATS400.118
119 01/11/06 22:12:26 CPU memory, disk PATS400.119
120 01/11/06 22:12:55 CPU memory, disk PATS400.120
122 01/11/06 22:13:27 CPU memory, disk PATS400.122
123 01/11/06 22:13:57 CPU memory, disk PATS400.123
126 01/11/06 22:14:18 CPU memory, disk PATS400.126
127 01/11/06 22:14:29 CPU memory, disk PATS400.127
129 01/03/00 08:50:43 CPU memory, disk PATS400.129
130 01/11/06 22:14:48 CPU memory, disk PATS400.130
134 01/11/06 22:26:09 CPU memory, disk PATS400.134
135 01/11/06 22:26:29 CPU memory, disk PATS400.135
137 01/11/06 22:26:49 CPU memory, disk PATS400.137
138 01/11/06 22:27:24 CPU memory, disk PATS400.138
141 01/11/06 22:27:45 CPU memory, disk PATS400.141
143 01/11/06 22:28:11 CPU memory, disk PATS400.143
146 01/11/06 22:28:34 CPU memory, disk PATS400.146
148 01/11/06 22:29:07 CPU memory, disk PATS400.148
149 01/11/06 22:29:28 CPU memory, disk PATS400.149
151 01/11/06 22:29:48 CPU memory, disk PATS400.151
154 01/11/06 22:30:08 CPU memory, disk PATS400.154
160 01/11/06 22:30:34 CPU memory, disk PATS400.160
162 01/11/06 22:30:55 CPU memory, disk PATS400.162
163 01/11/06 22:31:15 CPU memory, disk PATS400.163
166 01/11/06 22:31:37 CPU memory, disk PATS400.166
167 01/11/06 22:32:07 CPU memory, disk PATS400.167
169 01/11/06 22:32:37 CPU memory, disk PATS400.169
170 01/11/06 22:33:06 CPU memory, disk PATS400.170
173 01/11/06 22:33:16 CPU memory, disk PATS400.173
174 01/11/06 22:33:37 CPU memory, disk PATS400.174
175 01/11/06 22:33:58 CPU memory, disk PATS400.175
177 01/11/06 22:34:28 CPU memory, disk PATS400.177
178 01/11/06 22:35:07 CPU memory, disk PATS400.178
184 01/11/06 22:35:38 CPU memory, disk PATS400.184
186 01/11/06 22:35:58 CPU memory, disk PATS400.186
198 01/11/06 22:36:19 CPU memory, disk PATS400.198
215 01/11/06 22:36:49 CPU memory, disk PATS400.215
217 01/11/06 22:37:10 CPU memory, disk PATS400.217
218 01/11/06 22:37:29 CPU memory, disk PATS400.218
221 01/11/06 22:38:01 CPU memory, disk PATS400.221
227 01/11/06 22:38:34 CPU memory, disk PATS400.227
228 01/11/06 22:42:59 CPU memory, disk PATS400.228
241 01/11/06 22:43:35 CPU memory, disk PATS400.241
244 01/11/06 22:44:06 CPU memory, disk PATS400.244
250 01/11/06 22:44:27 CPU memory, disk PATS400.250

CPU Patches Not Yet Applied
_______________________________
* none *
@

 

[doktor]

I like this "So I think you are right (as usual!)"...
Ok, 13 years working with this product, gives one a clue, where to look...
It seems to me that all patches are applied, as they should. Jon will know this better.
I am looking forward to hear about your success with diconnecting and reconnecting the cable between the systems.
///doktor

 

[smetse]

doktor,
Disconnecting/Reconnecting the cable on the slot P1 did not work. The mailbox 3001 is still busy, and the extension 6057 doesn't work either.
I disconnected the cable for 30 seconds. Is this enough time?

 

[jon24422531]

Is that mailbox in use by another application? I have just read through the thread again and I see no mention of listing the references. It is generally good practice to list any mailbox references before deleting so as to avoid deleting an important box.
@ L ref and enter the mailbox number (3001)

Not too sure about 30 seconds being enough as I don't know how soon the PBX would notice the disconnection, but you don't need to disconnect the whole Amphenol cable, just pull out extn 6057 at the frame and punch it back in later.

Jon

http://www.telecom-stuff.com

http://www.jonschofield.com

 

[doktor]

In most PBX and voice mail systems, you can block and de-block ports, if these ports do not work.
With the OCTEL 200 the command is:
@TE L 2.
This command is a bit dangerous! It can lock your ports.
So first check system paramter 46 with .L SYS 46.
In this field the command for de-activating a forwarding of a telephone in the Definity should be written.
If the PBX was an Ericsson MD110, the command for de-activating a forwarding of a telephone is #21#.
So using the "@TE L 2" command, all ports in the OCTEL will go off-hook, and the digits for de-activating a forwarding will be entered on the actual port.

Anyway if the setting of the sys par 46 is the command for
activating a forwarding in the PBX, all ports will be forwarded, and no-one can enter the voice mail system, after having called the voice mail group number.
///doktor

 

[smetse]

Jon and doktor,

I disconnected extension 6057 at the 66 block for 30 minutes. After reconnecting it, I ran the following commands:

@l ref (option 6)

* INDIVIDUAL PORT STATISTICS *
--------------------------------------------------

PORT PORT INCOMING OUTGOING SECONDS SELFTEST
NUMBER TYPE COS CALLS/FAXES CALLS/FAXES BUSY FAILED
------ ---- --- ----------- ----------- ------- --------
1 VOC 254 12521 879 449040 0
2 VOC 254 12499 907 455532 0
3 VOC 254 12489 922 445670 0
4 VOC 254 12450 889 465784 0
5 VOC 254 12507 938 441668 0
6 VOC 254 12478 941 449424 0
7 VOC 254 12427 880 455526 0
8 VOC 254 11998 828 *** 0
9 VOC 254 12530 938 428810 0
10 VOC 254 12428 871 456174 0
11 VOC 254 12482 863 443234 0
12 VOC 254 12453 721 468940 0
13 VOC 254 12433 322 420188 0
14 VOC 254 3 992 143276 0


@ps

CH 1 CH 2 CH 3 CH 4 CH 5 CH 6 CH 7 CH 8
MOD AIC IDL AIC IDL IDL IDL CON

CH 9 CH 10 CH 11 CH 12 CH 13 CH 14
IDL IDL IDL IDL IDL IDL

As you can see, the port 8 is still not working.
Did I miss anything here?

At this point, this problem with the port 8 is more important to me than the busy mailbox 3001.

What would be the next step in the troubleshooting process?

 

[doktor]

It seems that a call locks the the port 8 (ext 6057) and your mailbox 3001. Still HDD, patches and commands (config) - to me - seems to be OK.
I can now only recommend a restart by using the command @RESTA

The port=8 can be taken out of the voice mail group hunt in the Definity, while you are trying to solve this problem.
By doing this callers do not end up in "silence" (dead end).

Let us hear about your success!
///doktor.

 

[jon24422531]

I agree with the Doktor. It must be time to consider a restart. Very unusual in an Octel, but I can't see any other way if we want to unlock whatever is jamming it. Save the config to floppy first (of course!) and allow 45 mins for the system to do a complete restart with the @Resta 2 command.



Jon

http://www.telecom-stuff.com

http://www.jonschofield.com

 

[smetse]

doktor, Jon, and Chuck.

The restart cleared the port 8 problem.
I have been learned so much from you through this troubleshooting process.
Thank you very, very much for all your help!

 

[jon24422531]

So can you delete that mailbox?



Jon

http://www.telecom-stuff.com

http://www.jonschofield.com

 

[smetse]

Yes, now I can do whatever I want with that mailbox.

Thanks again.

 

[doktor]

A restart (even though seldom used) clears these problem with loops etc.
Case closed, fault cleared.
///doktor