There are a couple of ways you could try to find it if you have some time. The quickest way though would be to contact your carrier.
If you have some time, the first thing I would do is to list your VDNs. If your VDNs are named decently you might be able to pick it out.
You could also try to deduce the VDN based on how the call is routed when you call it. If it goes to a specific area or skill group, you can probably trace it back to the VDN
If I were you I would call the carrier unless you have a relatively small PBX. Be careful with call volume. If the old usage was relatively light and the new usage will receive a lot more calls, you might run into trunking issues.
Dial the number and ask the agent what their phone display reads. If it has a name it is probably a VDN which you can easily find by doing a "list vdn".
Beginning in V9 you can do a 'list trace tac XXX' which will show you activity on the trunk group and what digits the carrier is sending. Best to do it during light traffic.
Hey 4merAvaya can you expand on the command please? I have S8700 v12 and when I use the command I have additional options to select - [or tac/a(atm), d(digits), q(qsig)].
I am new to this so what is the rest of the command looking for?
Thanks
S8700 & S8710 v12/CMIV/Octel 250/CMS v12/Intuity AUDIX/IP Agent/VOIP/Programming
==========================================================
Does anyone have a quarter, I need to make a phone call?
Use the command list trunk - this will give you all of your trunk groups and the TAC (Trunk Access Code) associated with each trunk group.
4merAvaya suggestion of 'list trace tac XXX' means that XXX should be replaced with the actual TAC of the trunk group that you wish to trace.
Susan "'I wish life was not so short,' he thought. 'Languages take such a time, and so do all the things one wants to know about.'"
- J. R. R. Tolkien, The Lost Road
Will that command work on a DNIS that has digits stripped and replaced at the trunk group level? I've worked on switches that had the entire DNIS stripped out and replaced with completely new VDN's.
I did so because they had a Definity installed to replace two PBX systems, one for admin traffic that was horrid (some Siemens/Rolm series that was as useful as a boat anchor) and an ancient Rockwell Galaxy. Their DID range and DNIS range were the same, although they were for two different switches.
So, rather than migrate 200 plus toll free numbers to new DNIS digits (choosing a new DID block was unacceptable), the DNIS digits were stripped from the incoming trunk group and replaced with 4 spiffy new VDN digits. Voila, DID/DNIS conflict was solved.
You can do this by changing the trunk group programming. I can't remember what page it's on, but I think it's around page 4 or 5 of the trunk group form. Pretty easy to do.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.