ISDN Red and Yellow alarms

[Okkie26]

My customer is expiriencing issues that ystem status is generating red and yellow alarms on their PRI trunk.

When I check system monitor, I can see the log:
1405863038mS ISDNL1Evt: v=5 peb=5,F2 F1
1405863040mS ISDNL1Evt: v=5 peb=5,F3 F2
1405863042mS ISDNL1Evt: v=5 peb=5,F1 F3
1405863044mS ISDNL1Evt: v=5 peb=5,F2 F1
1405863045mS ISDNL1Evt: v=5 peb=5,F3 F2
1405863046mS ISDNL1Evt: v=5 peb=5,F1 F3


Now, all connections are fine, no phone calls are dropped or whatever.

I replaced the PRI board. rebooted the IP500V2. Moved the PRI modem so that it's near the IP Office. But still no joy here.

Provider checked the line, but all seems fine. Only issue are the alarms that are raised each day.

 

[IPGuru]

Now, all connections are fine, no phone calls are dropped or whatever.

Yet...

this is almost certainly a problem from the network provider but I doubt you will get any action until the circuit finally fails

A Maintenance contract is essential, not a Luxury.
Do things on the cheap & it will cost you dear

 

[amriddle01]

Yellow is an alarm received from the other end of the connection (the providers end) telling you it has issues with it's connection and Red is when it's totally down from your perspective...this will be an issue with the providers NTE

 

[Okkie26]

I agree on both of you guys.

But still, if red alarm means a total down, you would expect that calls are disconnected. But this doesn't occur. Not even the dialup gets disconnected.

Also, the provider went on site some weeks ago, but according to them, the line is 100% okay (surprise!!!)

 

[amriddle01]

A red alarm can be for a slit seconds loss of synching, between calls or even while one is in progress on another channel in your case

 

[Okkie26]

Yes of course. Didn't think of that one.

Still, everyting looks like a provider issue.

 

[amriddle01]

Because it is, you just need to ignore it until it escalates into a service effecting issue

 

[Okkie26]

The point is, the customer is aware of the issue, and wants a solution before is escalates

 

[amriddle01]

It's not your issue to fix no matter how much he shouts, he needs to pester the provider and keep paying them when they say "no fault found" if that's his attitude ....but in the end they'll need to wait until you have an issue you can actually prove is one piece of kit or the other

Been there many times and it was always the provider (BT), other alternative is to keep swapping your kit and showing nothing changes but keeping tally, and when you finally prove it's the provider hit them with the bill

 

[Okkie26]

No worrie. My customer isn't shouting. He just needs to be convinced that it is a provider issue.

 

[IPGuru]

My customer isn't shouting. He just needs to be convinced that it is a provider issue.

Yes
I once told a customer I suspected a line provider issue(BT) & the cust responded "They say everything is fine, I have this every time ii report a line problem."

after checking our history I responded.
"You have had 6 outages in the last year, each time BT said NFF and on every occasion the fault was finally rectified by BT, why do you continue believe them & not me?"



A Maintenance contract is essential, not a Luxury.
Do things on the cheap & it will cost you dear

 

[Okkie26]

Yes I know. Providers are a pain in the ........ eeeh.. somewhere you don't want the pain..