Search results for query: *

you are correct i forgot the 0 ` version 4.0.10 it is

BTW if i make a SC *93 to go to module XX1 in both 406 and 500 and i dial it i get the generisch and then get forwarded to the mobile (0)06543N it works

Test case: Using version 4.1 and manager 6.1 with vmpro module XX1 has 1 generisch and then transfers to a mobilephone (0)06543N situation 406 with configuration: incomming callroute line-id 0 incoming number: 1234567 destination VM:XX1 SC: 0N dial N id=0 ---------------------------------...

at a site we had to make a email notification and we got a code 3. that was a security issue with windows server 2003. i therefore suppose this is a security issue aswell. Look up if all ness ports for avaya are open. In our case this worked.

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

tnx going to try it that way now TheProvider

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...

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...

I suppose you only want a selective group of people to be able to get out of the queue. creative way: Make incomming calls CLI dependent. if the CLI matches... your caller will never be put in the queue. No reason to get out of it either.