Coverage path issue, possible double coverage 1

[smokinjoe2938]

Help I have a CM 6.3 and have a station with send all calls activated, with a coverage path of 203 that goes to a hunt group with no members with a coverage path of 17 that route to a vdn to a vector. If I call the hunt group directly or vdn directly, coverage works great, however when the primary station is called I get the send all calls cover tone ok but that receive a fast busy,a trace just shows me hitting point 1 for coverage path 203, any help would be most appreciated

acss sme acis sme acss cm 5.2.1 acss cm and cmm acss aura messaging.

 

[wpetilli]

Definitely sounds like a double coverage scenario.

 

[AvayaTier3]

To enter an extension that is assigned as a vector directory number (VDN) as the
last point in the coverage path, you must make an administration change. For
more information, see Avaya Aura? Call Center 5.2 Call Vectoring and Expert
Agent selection (EAS) Reference, 07-600780.

The double coverage restriction is lifted as of CM 5.1 when involving VDNs.
On the coverage path form, there is a new setting called "Cvg Enabled for VDN
Route-To Party?" Setting it to Y allows the 2nd coverage to work when it is a
VDN. However, you cannot have a triple coverage.

Double coverage didn't work until 5.2.1 SP3. I personally started using it in
5.2.1 SP4. Per the SP4 release notes (page 51 of the PDF) it states that it
fixed this: The "Cvg Enabled for VDN Route-To Party?" feature on "Coverage-path"
worked only for the first "route-to" step in a vector.
--------------------------------------------------------------------------------
VDN In a Coverage Path
About VICP
VDN in a Coverage Path (VICP) enhances call coverage and call vectoring. If you
enable Call Vectoring (Basic) or Call Prompting, you can assign a VDN as the
last point in a coverage path. A vector or Call Prompting processes calls that
reach this coverage point.

VICP considerations

- A VDN is not allowed to be a member of a coverage answer group.
- A coverage answer group can only be a point in a coverage path. A vector
cannot route a covered call to a coverage answer group.
- Removing a VDN from the system with the remove vdn <extension> command
automatically removes the VDN from any coverage paths.
- By default, features such as Call Coverage, Call Forwarding, RONA, or Night
Service cannot redirect calls that cover to a VDN. Therefore the route-to digits
or routeto number command with cov set to y is treated the same as cov set to n.
- The Cvg Enabled for VDN Route-to Party field on the Coverage Path screen
allows a second redirection (if needed) when a route-to command with cov = y
vector step processes a previously covered call routed to a VDN. The default is
n which retains the single redirection operation. If you set the field to y and
the call has covered only once, the call redirects again as though the call was
placed directly to the VDN. For example, the following second redirection can
occur:
a. the destination has a coverage path or another redirection feature.
b. the calling user presses the go-to-cover button while the destination rings
the principal phone on the second coverage path. The call stops ringing at the
second principal phone and moves to the next coverage path.
c. the second principal phone's Hunt-to Station path is checked for possible
hunt before coverage or hunt after coverage redirection.


A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

40 years Bell, AT&T, Lucent, Avaya
Tier 3 for 30 years and counting
[URL unfurl="true"]http://bshtele.com[/url]

 

[AvayaTier3]

Cvg Enabled for VDN Route-to Party

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

40 years Bell, AT&T, Lucent, Avaya
Tier 3 for 30 years and counting
[URL unfurl="true"]http://bshtele.com[/url]

 

[smokinjoe2938]

Thanks AvayaTier3 does sound like from my example that in fact I did have a triple coverage, thanks for the help, most appreciated!

acss sme acis sme acss cm 5.2.1 acss cm and cmm acss aura messaging.