Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
One vector for a time check for all vdns
- Thread starter Phoneman2
- Start date
Cannot say I have ever found a way to do this one either.
I sometimes use a manual approach, in which I set up a dummy queue with 1 agent ID and put a login/logout button for that agent ID on a supervisor's phone. I then set a condition line in the vector to goto or route-to a vector or extension number if the "staffed-agents" in split x is >=0.
That way the supervisor can manually divert the callers for that vector or all vectors with that condition to another service or VDN.
Also, for only two lines in each vector, I could use the following:
1. goto vector x if time-of-day is all 17:00 to all 08:00
2. goto vector x if time-of-day is fri 17:00 to mon 08:00
Not much help but another alternative.
Netcon1
I sometimes use a manual approach, in which I set up a dummy queue with 1 agent ID and put a login/logout button for that agent ID on a supervisor's phone. I then set a condition line in the vector to goto or route-to a vector or extension number if the "staffed-agents" in split x is >=0.
That way the supervisor can manually divert the callers for that vector or all vectors with that condition to another service or VDN.
Also, for only two lines in each vector, I could use the following:
1. goto vector x if time-of-day is all 17:00 to all 08:00
2. goto vector x if time-of-day is fri 17:00 to mon 08:00
Not much help but another alternative.
Netcon1
- Thread starter
- #3
The VDN Return Destination feature allows an incoming trunk call to be placed back in vector processing after all parties, except the originator, drop. This feature is activated through switch administration of the VDN form. It is an optional system feature, and as such, it must be optioned on the System-Parameters/Customer-Options form.
A field on the VDN form allows the user to enter a VDN extension as a Return Destination. In this section, the VDN which has the Return Destination field administered
will be called the "VDN with this feature active." The Return Destination VDN (the one specified in the new field) will be referred to as the "Return Destination."
Every incoming trunk call that is processed through a VDN with this feature active will be placed back in vector processing when all parties on the call, except the originator, drop.
For this feature, the "originator" is the incoming party that originated the call at the time the call entered the VDN with this feature active.
NOTE:
Incoming calls on DCS ties do not go to VDN Return Destination.
The VDN that the call will be placed in (when the originator is the only remaining party) is determined by the "Return Destination". This VDN may be the same or different than the original VDN.
More information on that and a scenario can be found in the call vectoring section of the R10 admin documents.
You can find this at support.avaya.com under online services/documentation.
Netcon1
A field on the VDN form allows the user to enter a VDN extension as a Return Destination. In this section, the VDN which has the Return Destination field administered
will be called the "VDN with this feature active." The Return Destination VDN (the one specified in the new field) will be referred to as the "Return Destination."
Every incoming trunk call that is processed through a VDN with this feature active will be placed back in vector processing when all parties on the call, except the originator, drop.
For this feature, the "originator" is the incoming party that originated the call at the time the call entered the VDN with this feature active.
NOTE:
Incoming calls on DCS ties do not go to VDN Return Destination.
The VDN that the call will be placed in (when the originator is the only remaining party) is determined by the "Return Destination". This VDN may be the same or different than the original VDN.
More information on that and a scenario can be found in the call vectoring section of the R10 admin documents.
You can find this at support.avaya.com under online services/documentation.
Netcon1
scottyjohn
Technical User
We have a number of VDNs which come from different brands we have and they have different opeing hours. We have the VDNs point to their own brand vector with its opening hours and then go to another vector which has no time of day just queing treatments. Works not too bad but it can get messy if ops come up with some "additional requirements" here and there. Its a bit different from what you need though. You could set up the vectors the same way as another guy handles a different problem, using the ANI of the VDN to route to a specific vector depending on its value. see thread690-335290 for details. if you need the config he has sent then give me your e-mail and Ill pass it on. As you can see from the thread I think he has been sending out enough! John
- Status
Similar threads
- Locked
- Question
