Audix System NOT working........HELP!

[narsman]

I have an Avaya IA 770 Intuity Audix

When calling voice mail user get fast busy. (seems like no channels available)

When I look at the Verify System Status - System Verification page:

Verification Info :


System status of VM

AUDIX(R) IN SERVICE

System status of mtce

Begin System Verification Checks -
File System Capacity Check Passed
IPC queue check passed

System status of vs

Voice System is Up
Number of Purchased Voice Ports 4
Number of Voice Ports In Service 0
Available Hours of Speech 129
Used Hours of Speech 6
Maximum Hours of Speech 135
Number of Available Text-to-Speech Sessions 4


When I look at the Voice Channel Monitor page:

I see the column headings, but the area where the channels should be is blank.

This system is affectively down and I need to know what the hell is going on. LOL

Cheers,



Steve

I don't mind coming to work, but that eight hour wait to go home is a bitch.

 

[smokinjoe2938]

yes it will work on older systems, and yes do a reset system 4.

acss sme acis sme acss cm 5.2.1 acss cm and cmm acss aura messaging.

 

[narsman]

Will do.

Let you know how it goes........fingers crossed.

Steve

I don't mind coming to work, but that eight hour wait to go home is a bitch.

 

[mattKnight]

Trunk group 1 (ISDN) shows to be in service and idle. This is used for their outside calls.
It's the only trunk group.

If you have IA770 - you will need a second trunk group. If you do not have one, no amount of reset system 4 is going to help

Take Care

Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.

 

[narsman]

I did find a group 99 that is identified as audix.
There are 4 channels, but they are all OOS/FE-idle.

Any help on putting them "in-service"? (maybe it's just that simple)


Steve

I don't mind coming to work, but that eight hour wait to go home is a bitch.

 

[smokinjoe2938]

busy trunk group 99/ release trunk group 99/ status trunk group 99 and then pray!

acss sme acis sme acss cm 5.2.1 acss cm and cmm acss aura messaging.

 

[narsman]

I busy out. It passed.
I release. It passed.
I status. It still says OOS/FE - idle.

The good views is I can now see the channels in the mess admin software.
They all show *on hook.

I do like the ASA. Thanks for the tip.

What do you suggest my next step to be?

Steve

I don't mind coming to work, but that eight hour wait to go home is a bitch.

 

[smokinjoe2938]

Reboot the pbx!!

acss sme acis sme acss cm 5.2.1 acss cm and cmm acss aura messaging.

 

[smokinjoe2938]

Any word on how you made out?

acss sme acis sme acss cm 5.2.1 acss cm and cmm acss aura messaging.

 

[narsman]

After rebooting........I cold rebooted it.....Seems that nothing has changed.

I appreciate your following up.

I've attached some screenshots.......something seems a bit strange.

Customer still receives busy signal when attempting to call VM.



<iframe width="480" height="360" src="

http://s1313.photobucket.com/user/Steve_Wininger/embed/slideshow/"></iframe>

Steve

I don't mind coming to work, but that eight hour wait to go home is a bitch.

 

[AvayaTier3]

sounds like you need professional help

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

40 years Bell, AT&T, Lucent, Avaya
Tier 3 for 30 years and counting
[URL unfurl="true"]http://bshtele.com[/url]

 

[narsman]

That's probably true and I'll see the shrink as soon as this is fixed.

Any comments on the screenshots??

Steve

I don't mind coming to work, but that eight hour wait to go home is a bitch.

 

[AvayaTier3]

By then it may be too late. Must not be critical.

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

40 years Bell, AT&T, Lucent, Avaya
Tier 3 for 30 years and counting
[URL unfurl="true"]http://bshtele.com[/url]

 

[wpetilli]

What about the Signalling group associated to the Trunk Group you busied.

 

[narsman]

the signaling group shows to be in far-end bypass?

I busied it out...passed
I released it.....passed.

status signaling-group 99....far-end bypass.

nice suggestion............keep them coming!!!

It's critical in a Palm Springs kind of way. Things are a little slower here, but I'm running out of time.

Steve

I don't mind coming to work, but that eight hour wait to go home is a bitch.

 

[kyle555]

I might be wrong as IA770 goes back a ways for me, but I remember fixing this a couple of times...

Login to CLI in linux (telnet to port 23, not 5023) with your dadmin account. Run the command "uptime" and if its a year or 3, or 4, do "stop -r".

Stop -r will reboot the server. Now, this "reset system 4" and "stop/start messaging" from the webpage only reboot the PBX application and voicemail application running on the server, not the server OS itself. If the thing hasn't been turned off and on again in a few years, that's a recipe to see something grind to a screeching halt.

*check your backups, test your backups before doing anything...

 

[narsman]

I was able to correct the issue......thanks to everyone who worked so hard to help.

The integrated messaging IP address was blank when I looked at it last week. (the system must have crashed and when it returned from the dead, the field was blank) I had no idea what address to use, so I programmed one that was labeled on the front of the machine. That is when I saw the channels, buy it still wasn't happy. I found a command in the GEDI that allowed me to find the correct IP addresses. "list node-names" The IP had been defined there and when I put it in the Integrated Messaging screen and restarted messaging, the channels magically went in-service.

All seems to be right with the world once again!

Thanks again to everyone that contributed.

Steve

I don't mind coming to work, but that eight hour wait to go home is a bitch.