PRI issues 3

[curlycord]

MICS 5.0 NAM 4.0
2 PRI Circuits

Symptoms are once every blue moon for about an hour but becoming worse lately:

Outbound busy signals, just busy....they don't get the "NO FREE LINES" displayed.

Inbound is Ring No Answer

No Alarms or Events!!!

I am thinking corruption or 5.0 not good with PRI but also the Telco not seeing any alarms either?.

Trying to see if anyway possible to resolve without upgrading due to expense and NAM involved etc as need to stretch it for another year.

We are all puzzled at the office.
Since they call out on one PRI and calls in on the other and no alarms for both of us I cant see it being the circuits themselves.

Wondering if I am missing something.




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

http://www.curlycord.com

 

[luv2ski]

I think i had an account "Goin back about 7 yrs maybe" with same issue with same software rel
Uopgraded nam 4.1 and switch to 6.1 and still had same problem...Etas said it was corruption so 2 of us spent a fri retrieving all data from 100 plus stations and did a startup and reprog from scratch starting at 5pm...Thank god we were both norstar techs cause it was done before midnite.

6 months until ski season starts...sadly i must resign myself to the warmer weather"this will include a normal 8-5 work day, 5 days a week"

 

[norstarboy125]

Curly get off that 5.0 software. I've had more problems with 5.0 and PRI's then I'd like to admit.

Jeremy J. Carter
Charm City Communications

http://www.charmcitycommunications.com

Norstar. BCM. CS1000 Programmer

 

[exsmogger]

That would be my recommendation as well. Take the software to at least R6.1 MR. If that's not possible due to the need to also upgrade the NAM, and you have a recent backup, I'd try doing a STARTUP to clear out the database and then restore your backup.

Brian Cox
Oregon Phone

http://www.OregonPhone.com

http://www.linkedin.com/in/briancox1952

 

[curlycord]

Same issue after upgrade.
Now they are 7.1, 4.1 NAM

This time we see alarms, 50 of them, and they say "fast busy signal and blank display screen"

They have 2 PRI's so hard to blame one circuit or one DTI card?

If a PRI goes completely down it should grab the second PRI, maybe it does not see the PRI as being totally down.

The 50 alarms in last 2 days, I see about 6 posts but no resolution:

310: Dti_cart_event P5 'B' TestLog
310: | CAUSE:
310: | 1)Bad Stimulus message received by dti from KSU
310: | Parameters are: Source file (eCpQinpEh {value 30})
310: | error number (0)
310: | 2)Bad encapsulated Stimulus 2 byte message received by dti
310: | from KSU. Parameters are: Source file (eCpQinpEh {value 30})
310: | error number (4)
310: | 3)Bad encapsulated Stimulus multibyte message received by
310: | dti from KSU. Parameters are: Source file
310: | (eCpQinpEh {value 30}) error number (4)
310: | ENVIRONMENT:
310: | 1)Occurs on DTI cartridge only.
310: | 2,3)Occurs on DTI cartridge only.
310: | HUMAN ACTION:
310: | Check DTI connections. If problem persists call
310: | operating company.








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

http://www.curlycord.com

 

[Phonehed]

Are you using a release 2 or higher NVRAM pack?

Phonehed in Dallas

 

[curlycord]

Yes, was at 1 then went to 2 with 7.1 upgrade.

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

http://www.curlycord.com

 

[curlycord]

Going to swap the 2nd DTI card and see what happens.
If still an issue we might reverse the 2 DTI's in programming to see if now a problem with incoming or instead split up the 2 PRI's into 2 pools....if it happens again we tell them to dial out on the 1st PRI-A via second dest code.
This may narrow it down a little.


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

http://www.curlycord.com