Caller ID won't forward if vector coverage set to Y.

[dudecrush]

I have a Definity G3R. I set up a simple vector for our HR Employment Verification line. It works just fine, but when I set the coverage to "Y" in the route-to statement, I lose caller ID. Here is the vector:


01 Wait time 2 seconds hearing ringback
02 Collect 1 digits after announcment 7792
03 Route-to number 2362 with cov y if digit = 1
04 Stop

Ext. 2362 is someone's extension, and that extension has bridged appearences on 4 other phones. I had to set the coverage to Y because they wanted it to flow to her voice-mail. As you might have noticed, this vector doesn't use or route to any particular skill-sets.

I set the "Allow VDN Override" to Y in the VDN, but that hasn't fixed the problem. Do I need to change something on the station side to make this work?

 

[tfp2006]

Did you get this to work? I have the same issue on CM 6.

 

[dudecrush]

No sir, I did not. I was spending too much time on it and it wasn't that important to begin with, so I just dropped it. I have a feeling it will come up again, though.

If you're using CM6, I'd say that this is not a bug with my ancient version but a feature which has carried through. There's gotta be a way to turn it off (or on, as the case may be).

 

[bleebrant]

Is it the VDN name that you're not seeing when the coverage is set to y? If so, this is apparently how it is supposed to work. I've copied below a note from the Call Center Call Vectoring and EAS Guide. Instead of routing directly to x7792 would routing to a phantom extension that covers to 7792 work for you?

Note from Avaya Doc:
1. When the with coverage option is set to y, the call is removed from vector processing when the route-to step is
reached, regardless of facility or remote switch availability. The call is taken out of any split queue, and any
feedback, such as music or ringback, is removed, even if the destination is not available. If the call is subsequently
rejected by the receiving switch vector, subsequent call treatment is defined by the rejection command (either busy
or forced disconnect). The call is treated as though the destination is directly dialed (see footnote 3 for related
information). This includes coverage, forwarding, treatments for calls that cannot be completed (busy reorder, and
intercept) and displays. The answering station sees only caller name and number, unless the Display VDN for
route-to DACS option is enabled (for more information, see Displaying VDN names for vector-initiated DACs on
page 663). A call routed with an adjunct routing link command is treated the same way as a call that is routed using a route-to with coverage y command.

Footnote 3:

3. A call that routes to a VDN using the route-to number with cov = y unconditionally command behaves
like a directly- dialed call instead of a VDN call. Therefore, the terminating station’s display only shows the
originating station information and does not show the VDN information (for other types of VDN calls, the terminating
station would see the VDN name

 

[dudecrush]

Nice catch bleebrant! That certainly looks to be it. I'll give it a try sometime and let you know.