Outcall not working on OV250

[WideTrac]

I have a Octel OV250 running Aria 03.01.02-1
Issue is the Outcalling to the cell phones have stopped working. The config note has been gone over with a fine tooth comb and is correctly setup per the CN:5400
The system does not show sieze line or anything when a message is sent. The mailboxes are setup correctly and I built a test mailbox and it will not outcall. The system has 8 ports and the first 7 or setup for outcall and the 8th port dedicated to MWI.
The customer stated that there was nothing done at the time the system stopped outcalling, this was on July 27th @ 2:01pm.
My question is: If the PBX. AT&T 85, was blocking the outcall or some issue with the switch would I still see the Octel trying to outcall using the CDR? I see no activity of the Octel trying to outcall on the CDR trace.

Any help would be appreciated.

 

[KenMeans]

you might try a garbage collect on the system

Ken Means

http://www.tel-is.com

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)

 

[WideTrac]

Been there done that, no help, ran Garbage collect, Validity test, drive test, etc.
Ran Dump on users mbx and can see msg(s) in box with correct response code set.
We set the EB this morning and toggled all feature bits to see if that will unfreeze are kill the bug in there somewhere, have not had time to test yet.

Anyone have a LARGE HAMMER?

 

[WideTrac]

Tested this morning again after feature bit toggle, still not outcalling
Turned Outcall feature "Off"
Tried to change phone number in user mbx and the system gives the error that Outcall Feature not set.
This verifies the system sees the outcall feature.
System changed back

C4 needed

 

[lakehouse]

Have your PBX tech verify ALL of the PBX station port programming noted in CN:5400 is correct for each Octel port. Those PBX ports connected to Octel are supposed to be configured as if it was connected to a 7405D set.

Finally, have the tech pull an Octel port cross-connect and attach a 7405D phone set to the PBX; attempt to make various outbound calls and see what happens (or doesn't).

 

[WideTrac]

System now outcalling ?
Someone was in the system yesterday and must have known how to get into the codes because all menu settings are still the same. The system reported the following error

21 AUG 06 12:34:21PM
*** Local Lock error - Clustering
>>> NOTIFY SUPPORT REPRESENTATIVE
00000 24C09500 FC010000 11001572 AEB50100 *$..........r....*
00010 55018CBE 00008DBE 00001C06 0000C053 *U..............S*
00020 0B008900 *.... *

The security was corrected so they rebooted and cleared the security breach. Have not been able to find out what was performed and may not ever know.

Thanks for all your input.
If I find any more info I will post.

 

[KenMeans]

thanks it sounds like someone may have been hacking the system to make it think it was in a cluster. the code is in the system for it but only used on the CO based octels

Ken Means

http://www.tel-is.com

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)