norstar mics 3.1/nam 4.1

[fireeater]

how do
this system has been running fine since 3.1 was new.
no real troubles.

caller are answered by AA ,dial ext number , and get "invalid ext" message,they dial 0 and the reception can transfer no problem

it is intermittent, i have a smdr on it now to track,
to see if it has a line or port in common

the question is has anyone had this sort of trouble with digit translation

i'm thinking (and trying to isolate) if it is a telco ,trk card , line port,or vmail port trouble

any other thoughts???

thanks in advance


HALLOWED ARE THE ORI

mike

http://www.ics-on.ca

 

[hawks]

Have you installed the Redirect DN Patch to the NAM?

 

[fireeater]

yes, that was done years ago , this trouble has just started

HALLOWED ARE THE ORI

mike

http://www.ics-on.ca

 

[gforce9]

I'm thinking the H.D. may be starting it's downward descent. I would have suggested a reboot, but that could be a risky proposition if the drive is going kaputski.

 

[curlycord]

Suggest do the patch again and/or check touch tone gate (if has) by going to F983/AA and press 1


=----(((((((((()----=
curlycord

http://www.curlycord.com

 

[fireeater]

system has been backed up (regularly)and has been rebooted a couple of times ,

will have to try the patch thing again(but is intermittent so the old patch is working)

touch tone gate is checked and proper(tried different settings, std and custom)

HALLOWED ARE THE ORI

mike

http://www.ics-on.ca

 

[fireeater]

update:still intermittent but happening more and more
happening on all (telco) lines and all (8) nam ports
call in , answered by aa (happens on all 3 tables being used)
dial ext number (lets say 2345)
sometimes goes through properly
sometimes get "invalid" message after entering the last digit(no delay)

and something that just happened to me a couple of times
using the example 2345 it sometimes happens I get the invalid message after I dial 23, other times I got the message after dialing the 2, and again other times dialing 234

pressing the 2 and getting invalid message is a little strange because they are using ccr with a path 2

i did find the patch and put it in again

now if it is with the vmail, do you think a reinstall(default) and restore the backup could fix it ,
or do you think the main os /drivers could be to blame




HALLOWED ARE THE ORI

mike

http://www.ics-on.ca

 

[curlycord]

Are you saying still happens after the patch again?

Reinstall does clear some bugs....you could try the restore but somtimes you restore the bug, if still does not work then reinstall and program from scratch.

Dont forget to back keys from 915.




=----(((((((((()----=
curlycord

http://www.curlycord.com

 

[fireeater]

yup still after the second patch
ya capabilities file would be nice to keep (grin)
will be doing the redo on monday night ,then time will tell

HALLOWED ARE THE ORI

mike

http://www.ics-on.ca

 

[fireeater]

update

defaulting and reloading backup (or clean install)
no change after a day it happened again

final fix ....replaced nam,(eqiv.to original) restored backup
so far (1 week later) no complaints

thanks all for the ideas

HALLOWED ARE THE ORI

mike

http://www.ics-on.ca

 

[curlycord]

Curious if hard drive

=----(((((((((()----=
curlycord

http://www.curlycord.com

 

[fireeater]

ya if i can get a replacement hard drive i'll try it in the office and see

HALLOWED ARE THE ORI

mike

http://www.ics-on.ca