VM: if all ports are being used disco, without any tone.

[unconcerned]

If all ports of vmpro (my case 12 ports) are being used in queues, the next caller forwarded into a VMpro queue gets disconnected without any notice..There is no buzy tone given nor from VMpro nor from the system..Just a *Click* disconnect.

So it seems some incomming calls have the same disconnect if they are transfered from VMpro queue *hold* to *still hold*
Last problem only occures wenn the VMpro ports are full or almost full.

sys ip 406 v3.1

does updating solve these problems or is there an other solvation?

 

[ProviderReborn]

Try putting a Fallback in the incoming call route. But it cant be a group with queing or you will hit the same issue as you already have.

ACA - IP Office Implement
ACA - IP Telephony
ACS - IP Office Implement (Aug 30th)

 

[unconcerned]

tnx for the fast reply. only its not an option in this case. as it is a callcenter for 5 doctors and the chemist shop.

The only groups without queue are the emergency-hotline and the emergency-reflection group towards the hospital and backwards. Those have to be free at all cost.

actually its not such a big problem if incommings are disconnected wenn vmpro is full. only thing is that people should get the normal disconnect tone or the buzy tone, as long as it isnt a silence (deadline).

 

[ProviderReborn]

What about creating a dummy user. And putting the fallback to that dummy user.

You could then put that user in DND (hope fully your on a software build which sends the call to VM)
You could then record busy tone as the greeting and save as a continuous loop option 4.
Or you could limit the number of people you hold in the queue to say 9 (Have some spare for VM access or any thing else) This should return a busy tone too.

ACA - IP Office Implement
ACA - IP Telephony
ACS - IP Office Implement (Aug 30th)

 

[unconcerned]

tnx going to try it that way now TheProvider

 

[intrigrant]

A fallbackuser does not help.
This is fuzzy logic, if all VM Pro ports are busy then VM Pro can still handle calls but as soon as the call needs a speech channel and there is no channel available it will drop the call. For IP Office the call is already connected to VM Pro and cannot be rerouted.

The only solution is either to open a case by Avaya or buy additional channels.

 

[ProviderReborn]

The queue limit will help though surely this would return a busy tone NO?

ACA - IP Office Implement
ACA - IP Telephony
ACS - IP Office Implement (Aug 30th)

 

[unconcerned]

Just to Inform.

Limiting the queue lenght to 7 has worked for me.
This way VMp handles 10 calls at times the queue is full. VMpro has 2 ports to give the caller the buzy output and a disconnect.
Last 3 days there have been no complains.

tnx for the input

 

[JAVSPT]

Hi,
I see your problem only today, but if you not yet fix issue.
If you upgrade for 3.2 (any) you can creat a Hunt Group with the same name you have on VM module.( without numbers)
Put the agents or peaple inside, then when the VMChannels are in work the calls go´s to that group.
Of Course in this case only hear ringing.