Search results for query: *

check also this thread: http://www.tek-tips.com/viewthread.cfm?qid=1316603&page=3

Not sure if there is one... But an autodial button with the feature access code should work fine...

If I'm not mistaking you will have to dial the corresponding pickup-group number you have entered in your "extended-pickup-group screen", after dialling the FAC. This is NOT the same number as the actual pickup-group number. Check the "extended-pickup-group" screen.

Looking at the screen reference in the Admin Guide shows me: Holiday Coverage This field determines when to redirect call to coverage for an inside or outside call. Valid entries Usage y Type y to send the call to an announcement. n Type n to send the call to the next point in the coverage...

Did you try to adjust the volume of the telsets of the users? Volume control on the phone itself will adjust this.

Uhm... are you really having customers waiting in queue for over 60 minutes?? wow, these must be the worlds most patient callers. Average abandon time overhere is 10 minutes max...

in that case: can you do an ANI check in the vector and route to a disconnect step if the ANI is in vector routing table x? In VRT x you enter the numbers you want to block.

maybe can you use VDN variables for this? RONA destination: a new VDN, with variables (these could be there mobile numbers) Build an extra VDN to which the people can call to adjust the active variable of the former VDN.

You need to setup an extra set of route-patterns for your outgoing calls. On the route-patterns you can assign a FRL and the system compares this FRL to the FRL in the COR of the calling extension (if the FRL in the COR is equal to or higher than the FRL in the route-pattern, the call is...

The easiest way to restrict outside numbers to call your system is to talk to your provider. That way those calls will never reach your system at all.

Am I reading this correctly 1. no answer on group --> call-forward to handset (or is this actually coverage??) 2. handset call-forward to virtual extension 3. coverage path to mobile In other words: forward-forward-coverage... (or is it coverage-forward-coverage... if so: this will not work...

I would start with looking at your alarm log and error log and look for trunk-related entries. Look them up in the manual and test and repair accordingly.

Indeed, after the first coverage path the call will not go through another coverage path. And because a VDN is a final coverage point in a coverage path, adding another coverage point in the first won't help eighter. Perhaps the following approach can be helpful: in the first vector route-to...

Another approach could be to assign this station a new COR. With the "Called Party Restriction" parameter on the first page of the COR you can restrict calls from the public network.

ah all right, I missed that part... using the hunt-ns will follow the night destination (if entered). When there is no night destination filled out the system considers the hunt as busy which makes it able for the call to follow the coverage path. Obviously, my suggestion will not work in your...

behind the hunt-ns button you should enter the hunt-group number you want to put into night service (by doing this you make the huntgroup busy, which makes you able to assign a coverage path with the busy criterium). Also make sure you have entered a coverage path on the 1st hunt form. And of...

another approach could be: use a coverage path (containing the desired destination) on the hunt-group form in combination with a hunt-ns button on the station form.

Hmmm too bad... Avaya said it was an undocumented feature... in other words: lucky you if it works but we don't guarantee it will work in newer versions... guess it just doesn't anymore...

You could try to just add the collect digits step to your vector and do nothing with these digits. Simply queue-to skill and when the agent receives the call watch his display. I know this trick worked a couple years ago on a R11 system with Callmaster phone. Good luck!

Indeed, only stations and agent login-ID's. But you can prevent them from appearing in the directory by using special characters such as @ or _