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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Trunk group to VDN Names

Status
Not open for further replies.

notbrokedontchangeit

Technical User
Jun 21, 2005
111
GB
I have three departments and have ddi's coming in on 3 seperate vdn's which point to the same vector. The calls come in and process through to the vector with no problems. They are answered by the attendant which see's the trunk group name irrespective of which vdn they have come through on. I need them to see the vdn so they can handle the calls correctly.
VDN overide is on and they are using attendant vectoring. Any ideas?
 
You can try this:
Change your att vectors to normal vectors, wright additional vectors and point your 3 vdns to the new vectors(each vdn must go to its own vec for the route to number step) add listed directory numbers for your diff VDN's (cant use Att vec with Listed direc numbers) in your vectors insert the step route to number xxxx (ldn no) try it, im sure this will display the name at the switchboard.
 
HAve you tried turning on the VDN Override in the VDN form.
 
SAfrica/Caper68 -
Cheers guys, the LDN works but the problem I have now is that I have a route to step and really need it to stay as an attendant vector because there are provisions set in case that call is not answered and there is no coverage for an LDN. I noticed on a trace that the LEC is not sending CLI, could this be the cause for it not using the vdn names?
Keep em comin guys it is all helping.
 
Hi,

Try turning VDN override off (set to N) on all the vdns and see if that works - it sounds weird but I just had to do the same thing and it worked for me, thought I dont know why...

:)

Heather
 
Na, tried that the problem being that as soon as I turn VDN override off and put attendant vectoring on it sets the vdn override back to yes. If I leve the attendant vectoring off I am back to the same scenario as I am in now.
I really need the attendant vectoring so that it follows the later steps within the vector.
Thanks for all of your advice, I really appreciate it
 
Can you use vector variables? What version PBX?

When you say "I really need the attendant vectoring so that it follows the later steps within the vector.' makes me think maybe a way to keep att vectoring turned off and route by vdn variables. Any way you can post the vdn and vector?
 
It is with Avaya at the moment, I will post the result that they suggest. Thanks for your advice
 
It turns out that for it to work properly the LEC has to support DNIS so its not really a switch problem.
Cheers Guys
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top