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 derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Routing VDNs to Extns and Then To Voicemail
- Thread starter rtsoi
- Start date
If the VDN is 5555 and voicemail hunt is 99, then queue to a hunt group and if unanswered, then go to that mailbox from within the vector with a "messaging split 99 for extension 5555"
Or, route to a station that appears on the phone(s) you like that covers to voicemail and that appearing station is a secondary mailbox for the VDN mailbox, or cover to another VDN/vector with the messaging split 99 thing.
Or, route to a station that appears on the phone(s) you like that covers to voicemail and that appearing station is a secondary mailbox for the VDN mailbox, or cover to another VDN/vector with the messaging split 99 thing.
- Thread starter
- #3
I'm a little confused by your response.
Currently:
VDN 1234 goes directly to a voicemail box.
I would like it to ring at Extn 5678 and if unanswered, go back to 1234's mailbox.
Currently, calls direct to x5678 go to it's own mailbox.
Are you saying to change x5678's coverage path to route to another VDN?
Currently:
VDN 1234 goes directly to a voicemail box.
I would like it to ring at Extn 5678 and if unanswered, go back to 1234's mailbox.
Currently, calls direct to x5678 go to it's own mailbox.
Are you saying to change x5678's coverage path to route to another VDN?
No, I'm saying VDN 1234 can either route to 5678 and follow 5678's coverage.
Or, VDN 1234 can queue to a hunt of which 5678 is a member, and if unanswered, go to 1234's mailbox
Or, VDN 1234 can route to 5677, of which a bridged appearance lives on 5678's set and if unanswered, go to 5677's mailbox. Or have 5677 be a secondary mailbox of 1234, or have 5677's coverage path go to a vdn that routes to "messaging split 99 for 1234"
Or, 1234 can be a X ported station with a bridged appearance on 5678.
All to say, you need an extra step in between routing from the VDN to 5678 and getting to the mailbox for 1234 and having 5678's direct calls go to 5678's mailbox.
Or, VDN 1234 can queue to a hunt of which 5678 is a member, and if unanswered, go to 1234's mailbox
Or, VDN 1234 can route to 5677, of which a bridged appearance lives on 5678's set and if unanswered, go to 5677's mailbox. Or have 5677 be a secondary mailbox of 1234, or have 5677's coverage path go to a vdn that routes to "messaging split 99 for 1234"
Or, 1234 can be a X ported station with a bridged appearance on 5678.
All to say, you need an extra step in between routing from the VDN to 5678 and getting to the mailbox for 1234 and having 5678's direct calls go to 5678's mailbox.
- Thread starter
- #5
yeah, to do it within the vector, after hunt group queuing fails, it would follow the hunt group coverage path where the hunt group extn would need to be secondary to the VDNs mailbox to make voicemail answer with the right greeting.
But you got the idea!
*edit - come to think of it, the hunt group thing may have been bad advice and unnecessary. If the hunt group was ACD and no cov path and unanswered, then you'd follow the vector.
If you wanted to have 1234 make a key ring on a set but if it didn't answer, go to the voicemail of 1234, and without using up a spare set license, a hunt group or other extension in the dialplan that can use a coverage path would do it - but the hunt groups cov path would need to point to v2222 where VDN 2222 went to vector xxx and vector xxx had "messaging split 99 for extension 1234".
All to say you can do it without burning a set license if that's important to you
But you got the idea!
*edit - come to think of it, the hunt group thing may have been bad advice and unnecessary. If the hunt group was ACD and no cov path and unanswered, then you'd follow the vector.
If you wanted to have 1234 make a key ring on a set but if it didn't answer, go to the voicemail of 1234, and without using up a spare set license, a hunt group or other extension in the dialplan that can use a coverage path would do it - but the hunt groups cov path would need to point to v2222 where VDN 2222 went to vector xxx and vector xxx had "messaging split 99 for extension 1234".
All to say you can do it without burning a set license if that's important to you
- Thread starter
- #7
I programmed the coverage path to ring to another VDN that points to VDN 1234's mb and it worked.
However, I have several extns that want this same configuration (ring to x5678, then to VM) but I can't program the VDN to "messaging split to extn Active". It has to specify which MB.
I guess this means I have to program a Hunt/CP/VDN/Vector for each extn.
However, I have several extns that want this same configuration (ring to x5678, then to VM) but I can't program the VDN to "messaging split to extn Active". It has to specify which MB.
I guess this means I have to program a Hunt/CP/VDN/Vector for each extn.
There's got to be a simpler way. What if instead of VDNs you used virtual stations? They don't use licenses either, but they also don't have call appearances - so they can't make calls or do anything but follow a coverage path.
Suppose that coverage path said for virtual station 1234 had as a first point station 5678 for 2 rings and then as a second point hunt 99 for voicemail.
5678 could be the station, or you could make a cover answer group and have it ring a few people, or a vdn, etc. Depending on what user problem you're trying to solve - and how many times you need to do it for however many users you have, that might change how you approach a solution.
Suppose that coverage path said for virtual station 1234 had as a first point station 5678 for 2 rings and then as a second point hunt 99 for voicemail.
5678 could be the station, or you could make a cover answer group and have it ring a few people, or a vdn, etc. Depending on what user problem you're trying to solve - and how many times you need to do it for however many users you have, that might change how you approach a solution.
- Thread starter
- #9
Just don't double cover from the virtual to the station to the station's coverage path. Make sure each virtual has a coverage path to ring the station you want twice and then to voicemail all within a single coverage path.
Otherwise you'll get funky results!
Otherwise you'll get funky results!
- Status
Similar threads
