What happens when all audix ports are in use?

[WGross]

We recently expanded our operations...occasionaly when we dial into audix to retreive voicemails the extension just rings. Also sometime extensions will not forward to voicemail and continue to ring. I believe we are maxed out on ports....is there a way that i can see usage? What do you suggest i do to determine whats going on. I though maybe the card had low voltage and wasnt "hearing" the rings....avaya has replaced the card and we are having the same problem.

 

[lopes1211]

"list measurements load day" will show you the max number of ports used. If this equals your total number of ports, you are maxed. If not, you may just have a bad port. You can also put in a date, then next page through and see a history for the past month or so.

-CL

 

[IPSI]

You may also want to check your Audix hunt group and see if you have a queue length greater than 1. If the problem is that all of your Audix ports are actually in use, adding to the allowed queue length will allow a call to be held by the hunt group until a port opens. If you do NOT have a hunt group size greater than 1, when a call gos to Audix and there is no port available they will not be allowed into the hunt group and they will continue to ring, get turkey tone,a busy signal, or whatever based on the type of call and the default treatment, but they will never go back to the audix hunt group.

I hope this helps!

IPSI

 

[1a22ip]

WGross

We must remember that the Audix ports are a two way street. You need then same number of ports on the pbx as you have installed in the audix. An unblanced number will cause issues as well.

Just a thought
ED

1a2 to ip I seen it all

 

[Bobg1]

ED
Could you explain what you mean with that post.
I think it lost something in the translation.....

 

[1a22ip]

Bobg1

The audix has voice cards that relate to the members in the hunt group. For example my audix has twelve voice ports two iv6 cards. The pbx hunt group for voicemail has 12 members If the PBX had 13 members there is a chance that the 13 caller would get ring till they hung up. Your hunt group must match your voice ports.

Hope this helps
ED

1a2 to ip I seen it all

 

[Bobg1]

I was hoping that is what you were saying.
Just wanted to make sure.

 

[avayaman]

I've never tried it, but I wonder how it would work if you assigned a coverage path in the Audix Hunt group & set a RNA of about 5 rings? I think it would ignore it, since in effect you've entered the hunt group via coverage anyway. Instead, I would assign a second point of coverage in the coverage group accessing VM. If the call fails it will follow that. The usual destination would be the attendant, if there is one.

Paul Beddows

Consulting, Avaya/EAS implementation, Training
Vancouver, Canada
E-mail avaya@vancouver.hm

 

[cmcdan1523]

The problem is going to lie in the programming on the Audix hunt group in the PBX. Make the hunt group queue is sufficient to handle the queue number. I have been able to replicate the problem on callers going above the maximum queue. What happens is that if the queue is set at 4, the first 4 callers will hear ringing until a port becomes avaialable. The fifth caller will hear ringing forever, because the system does not recognize them as a valid caller in queue. He will not get a busy signal or turkeytone, he will simply hear ringing until they finally hang up and holler at the administrators.

This is a very annoying problem, but this will fix that problem. Obviously, you should look at adding additional voice ports if you consistently send callers into queue.