Phoneguy15
Vendor
I am trying to set up and test a simple VDN and I need the name of the VDN to appear in the display of the destination extension(s). How do I get the name to appear at the destination, or can it be done?
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!
VDN name display
- Thread starter Phoneguy15
- Start date
- Status
In order to have this displayed on the agents or staion telephone, set the Allow VDN Override? to "N" this will allow for the display of the VDN name on the set who answers it.
It gets more complicated as more VDN's and Vectors come into play. If this is the case, make sure all the "Allow VDN overrides are set to yes through the call flow with the exception of the one you want to display on the agent or telephone set.
Try this and see how it goes.
Netcon1
It gets more complicated as more VDN's and Vectors come into play. If this is the case, make sure all the "Allow VDN overrides are set to yes through the call flow with the exception of the one you want to display on the agent or telephone set.
Try this and see how it goes.
Netcon1
- Thread starter
- #3
Phoneguy15
Vendor
I have only set up 1 VDN(7711) that goes to 1 vector(100). When I call the VDN (with allow vdn overrides set to yes), all it show in the display is the calling number. Right now the vector is set up to go directly to my station. Is there a setting on the vector page for this as well?
- Thread starter
- #5
Phoneguy15
Vendor
I have tried settiing VDN override to yes and to no and it does not show the name of the VDN in the display of my set. I am using a 6416d+. Would the set type make a difference? I am running G3si R7, by the way.
I apologize for that. I tried it myself and you are correct. It will not work this way.
As per the vector/vdn documentation in the manual....
The call is removed from vector processing (that is, the call is taken out of any split queue, and any
feedback, such as music or ringback, is removed) for with coverage y interactions, even if the
destination is not available. The call is treated as though the destination was directly dialed. This
includes coverage, forwarding, treatments for calls that cannot be completed (busy, reorder, and
intercept) and displays (answering station sees only caller name and number). See note 3 in this
chapter for related information. Specifically, the call is taken out of vector processing when the step
is reached, regardless of facility or remote switch availability. If the call is subsequently “rejected” by
the receiving switch vector, the call is given the treatment defined by the “rejection” command (either
busy or forced disconnect). Finally, note that a call routed via an adjunct routing command is treated
the same way as a call that is routed via a route-to with coverage y command.
3. A call that routes to a VDN via the route-to number with coverage = “yes 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).
You may want to try a phantom station with coverage to your station. That might give you the name display.
Netcon1
As per the vector/vdn documentation in the manual....
The call is removed from vector processing (that is, the call is taken out of any split queue, and any
feedback, such as music or ringback, is removed) for with coverage y interactions, even if the
destination is not available. The call is treated as though the destination was directly dialed. This
includes coverage, forwarding, treatments for calls that cannot be completed (busy, reorder, and
intercept) and displays (answering station sees only caller name and number). See note 3 in this
chapter for related information. Specifically, the call is taken out of vector processing when the step
is reached, regardless of facility or remote switch availability. If the call is subsequently “rejected” by
the receiving switch vector, the call is given the treatment defined by the “rejection” command (either
busy or forced disconnect). Finally, note that a call routed via an adjunct routing command is treated
the same way as a call that is routed via a route-to with coverage y command.
3. A call that routes to a VDN via the route-to number with coverage = “yes 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).
You may want to try a phantom station with coverage to your station. That might give you the name display.
Netcon1
- Thread starter
- #7
Phoneguy15
Vendor
Well,
I am using Phantom exstensions already. The application I am trying to set up is to replace Phantom Extensions.
Right now we have 5 branch offices that have their lead phone number remote call forwarded to a DID(phantom ext) number here at Corporate. The phantom extensions have coverage to our small call center. That way the name of the branch shows in the display of the agents phone so they know where the call is coming from.
This works great, but now the big wigs want to start tracking the Call Center, specifically the number of calls they are receiving and handling for each branch. So, the only way I know to track the calls accurately would be to set up VDNs for each branch and then do reports from BCMS. But, they need(read: want) to have at least the same functionallity(read: branch names displayed).
Are there any other creative ways to accomplish this?
I am using Phantom exstensions already. The application I am trying to set up is to replace Phantom Extensions.
Right now we have 5 branch offices that have their lead phone number remote call forwarded to a DID(phantom ext) number here at Corporate. The phantom extensions have coverage to our small call center. That way the name of the branch shows in the display of the agents phone so they know where the call is coming from.
This works great, but now the big wigs want to start tracking the Call Center, specifically the number of calls they are receiving and handling for each branch. So, the only way I know to track the calls accurately would be to set up VDNs for each branch and then do reports from BCMS. But, they need(read: want) to have at least the same functionallity(read: branch names displayed).
Are there any other creative ways to accomplish this?
Well, there are ways around this. Your call centre must be pretty small to just route the calls to extensions. I would have thought that there would have been a small queue or hunt group of agents answering the calls. If this were the case then you could go as simple as putting aux-work buttons on their phones. and pointing all the DID vdn numbers to that queue. Then who ever is available would get the call and see what it says on the display.
If the boss wants call centre information. Set it up as a true call centre!!!
Re-think it!!!...
Perhaps empty hunt groups that cover to those extensions, if a call centre setup is out of the question. Problem there is the BCMS reporting.
Netcon1
If the boss wants call centre information. Set it up as a true call centre!!!
Re-think it!!!...
Perhaps empty hunt groups that cover to those extensions, if a call centre setup is out of the question. Problem there is the BCMS reporting.
Netcon1
- Status
Similar threads
- Locked
- Question