tones are not received on ISDN PRI 30 and/or digital extension w VMPRO

[ZebrAYA]

Yikes - tones are not received on ISDN PRI 30 and/or digital extensions with VMPRO –

I let you know some weird behaviour of a IP 500 with 90 + 16 DS and 8 analog Ext..

When calling from outside landline, the AutoAttendant answers, but it doesnt receive the dialed tones, later it goes to timeout option (operator), when she answers the call is cut at once.

Anyway if making the same from a mobile phone, the system Works right.


When calling from a internal (DS) extensión, to the AutoAttendant (by shortcode *90) the vmpro doesn’t receive the dialed tones.

Anyway if I call from an analog extensión, system Works right.


Both PBX and VMPRO servides were already restarted but problem continues.

Which can be the solution and how to avoid this kina of problem?


[Always Close your threads for avoiding other people to entangle]

 

[ZebrAYA]

Apparently the failure is located on a DS 30 expansion module.

Extensions in any of the other three modules don’t show any kind of similar problem.

Also I find that when pbx is rebooted some DS sets don’t connect but remain as –unplugged- most of them are plugged in to the suspicious module.
One has to unplug the phone, take it to another port, wait until rebooted and take it back to its original work place.

This module gave us trouble since beginning and we thought it was a ground problem, now all modules are connected to a good ground, but failure on module # 2 remains.


[Always Close your threads for avoiding other people to entangle]

 

[ZebrAYA]

Zebraya again...

closing the thread

I just wanna say that this case was horrible because lead us to think of Avaya as a very weak platform.
Anyway we escalate this problem to tier 3 and 4, and an avaya engineer told us to make a SSA log and a system monitor log.

Problems that were related with this case were:
1) in some modules tone was nos transmitted after call was established
2) in other modules when system were rebooted, digital phones remained with display on, but in the system they appeared as unplugged, and were unable to make or receive calls, (the user only notice it when making a call)
3) trying to login and logout and login again (and we have only two test users with login enabled) SYSTEM REBOOTED!

Final Solution was to upgrade the system from 4.0 (10) to 4.0 (14) as recommended from the Avaya Eng.
It fixed the 1) and 2), the 3 is not checked yet.

Quick brute force method to fix this issue was to downgrade the module (without rebooting) and later upgrade back to the actual release, it worked meanwhile!



[Always Close your threads for avoiding other people to entangle]

 

[TomMills]

downgrade the dodgy modules to 3.299999 loader.

then put back to version 4.whatever

common issues. surprised avaya didnt ask you to do this

its not a weak platform. it is however easy to get it wrong

 

[ZebrAYA]

Tom

Believe it or not Avaya never suggested me to do the downgrade back and forth.
I have to discover it myself by tweaking!
(and tweaking on hot with more than a hundred users talking )


Note: I give my apologies for putting this topic in this forum, I put the back reference in this new thread

http://www.tek-tips.com/viewthread.cfm?qid=1478917&page=1

[Always Close your threads for avoiding other people to entangle]