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!

Bug in VDN/Vectoring 1

Status
Not open for further replies.

telecomadmin12

Technical User
Apr 27, 2012
406
DE
I discovered that all my VDN/Vectoring doesn't work reliably. I might dial a VDN and everything happens as desired but every now and then(too often) when I dial a VDN nothing would happen, no vector processing, just silence.
What's wrong? I have CM3.0
Thanks
 
Doubt it is a bug

Are you using an IP set to make the call or digital?

Run a list trace when you make the call - what do you see? Any variation between good calls/bad calls?

Make other test calls to other destinations both internal/external - do you receive silence any where else?
 

I did a list trace on this vector. It is a Meet-me conference vector.
For the most part it works fine, however in the first example below (which looks like example two) the vector didn't process as shown in the list trace. I dialed the VDN and in fact I didn't hear the announcement 3968("enter 6-digit code") but after a few seconds the vector went to step 8 and connected me to the meeting right away without me having entered digits at all. Now how can that be??
01 collect 6 digits after announcement 3968
02 goto step 8 if digits = meet-me-access
03 collect 6 digits after announcement 3969
04 goto step 8 if digits = meet-me-access
05 collect 6 digits after announcement 3972
06 goto step 8 if digits = meet-me-access
07 goto step 5 if unconditionally
08 goto step 13 if meet-me-idle
09 goto step 16 if meet-me-full
10 announcement 3971
11 route-to meetme
12 stop
13 announcement 3970
14 route-to meetme
15 stop
16 disconnect after announcement 3973



time vec st data

20:54:52 0 0 ENTERING TRACE cid 6476
20:54:52 50 1 vdn e3170 bsr appl 0 strategy 1st-found override n
20:54:52 50 1 collect
20:54:52 50 1 announcement: board 02A16 ann ext: 3968
20:55:03 50 2 goto
20:55:03 50 8 goto
20:55:03 50 9 goto
20:55:03 50 10 announcement
20:55:03 50 10 announcement: board 02A16 ann ext: 3971
20:55:08 50 11 route-to Meet-me Conference
20:55:08 50 11 TRACE COMPLETE cid 6476


time vec st data

20:57:22 0 0 ENTERING TRACE cid 6482
20:57:22 50 1 vdn e3170 bsr appl 0 strategy 1st-found override n
20:57:22 50 1 collect
20:57:22 50 1 announcement: board 02A16 ann ext: 3968
20:57:26 50 2 goto
20:57:26 50 8 goto
20:57:26 50 9 goto
20:57:26 50 10 announcement
20:57:26 50 10 announcement: board 02A16 ann ext: 3971
20:57:32 50 11 route-to Meet-me Conference
20:57:32 50 11 TRACE COMPLETE cid 6482
 

Sounds like an announcement issue, not a vector issue. The vector executed all the steps you expected.

What happens if you dial announcement extension 3968 directly? Does it play? Are you using announcement groups? If so, are you sure the announcement is recorded on all of the boards in the group?

You can also check the announcement length if you execute: list integr


- Stinney

Quoting only proves you know how to cut and paste.
 

That is my announcement Board with 3968 being the announcement skipped frequently. Dialing the announcement directly works fine. Any more ideas?
02A16 ANNOUNCEMENT TN750C 000007 01 02 03 04 05 06 07 08
09 10 11 12 13 14 15 16
u

1 3960 integrated 0 1 VM Out of Serv y NA n 32 02A16
2 3973 integrated 0 1 Meet-me full n NA n 32 02A16
3 3968 integrated 0 1 Meet-Me enter digits n NA n 32 02A16
4 1 1 n
5 3963 integrated 0 1 Meet-Me try again 1st n NA n 32 02A16
6 1 1 n
7 1 1 n
8 3967 integrated 0 1 Non-working # y NA y 32 02A16
9 1 1 n
10 3969 integrated 0 1 meetme try again y NA y 32 02A16
11 3970 integrated 0 1 meetmefirst member n NA y 32 02A16
12 3971 integrated 0 1 meet me in progress n NA n 32 02A16
13 3972 integrated 0 1 try again digits y NA n 32 02A16
 

Sorry guys,
I need your help on this. I inserted a new announcement board but that didn't resolve my issue. I give you the following example:
I dial the VDN, I hear nothing for a few seconds (but the list trace vector shows me that I should have heard an announcement). In fact annoucements 3961 and 3963 I didn't hear at all, nor did I enter digits after 3961 and 3963. Any ideas?
1:49:48 0 0 ENTERING TRACE cid 15339
11:49:48 50 1 vdn e2127 bsr appl 0 strategy 1st-found override n
11:49:48 50 1 collect
11:49:48 50 1 announcement: board 03A14 ann ext: 3961
11:49:51 50 2 goto
11:49:51 50 3 collect
11:49:51 50 3 announcement: board 03A14 ann ext: 3962
11:49:54 50 4 goto
11:49:54 50 5 collect
11:49:54 50 5 announcement: board 03A14 ann ext: 3963
11:49:56 50 6 goto
11:49:56 50 7 disconnect
11:49:56 50 7 announcement: board 03A14 ann ext: 3964
11:49:56 50 8 LEAVING VECTOR PROCESSING cid 15339
11:49:56 50 8 TRACE COMPLETE cid 15339
 
what if you dial your announcement extensions directly? i.e dial 3961, 3962, 3963, 3964 - try this a number of times and measure the success rate.
 

Dialing the announcement extensions directly seems to be working fine. Couldn't detect any failures. But when dialing the VDN it happens frequently (not always though, 30% of the time). I am really at a loss here.
 
Why don`t you try creating a new vdn just with that meet me in it , put it on a totally different number range and test , also are you using the same handset for testing each time ? if you are try a different set on a different board.

APSS (SME)
ACSS (SME)
 
sorry i meant new vdn and new vec with only that meet me sequence in the vec.

APSS (SME)
ACSS (SME)
 
Something I was trained by Avaya to do was to start the vector off with "wait 0 seconds hearing silence". Grant this was on the older systems and I have just stuck with it. It use to get the system ready for data collection (ie collect statements in vectors).
 

Tolson has a point, I was taught that a long time ago as well. Some people say it's not needed now, but I've seen it cause issues when it's not there.

Another example of having something in the first line, we have an IVR that has to hear ringback to know that transfers are working, so if the vector doesn't have 2 sec ringback in the first line it won't transfer the call.

The other think you can look for is events. Run the command: disp event

Leave the category as vector, fill in the report period with a date and time range when you know it has failed (would be good to do a test until it fails, then you know where to search), and fill in the vector number.

See if you get any events that tell you what the failure is.

- Stinney

Quoting only proves you know how to cut and paste.
 

So I have tried a couple of things. I did the "wait 0 seconds hearing silence" and the problem persisted. I did "wait 1 seconds hearing ringback" and it seems to be working much better, but I still had announcements being skipped or one following the other without interruption. So I have "wait 1 seconds hearing ringback" before each of the first few announcements and everything seems to be good. I hope it stays that way.
Thanks a lot guys, this is a great site.

1 wait-time 1 secs hearing ringback
02 collect 6 digits after announcement 5890
03 goto step 14 if digits = meet-me-access
04 wait-time 1 secs hearing ringback
05 collect 6 digits after announcement 5891
06 goto step 14 if digits = meet-me-access
07 wait-time 1 secs hearing ringback
08 collect 6 digits after announcement 5892
09 goto step 14 if digits = meet-me-access
10 wait-time 1 secs hearing ringback
11 collect 6 digits after announcement 5893
12 goto step 14 if digits = meet-me-access
13 disconnect after announcement 5894
14 goto step 19 if meet-me-idle
15 goto step 22 if meet-me-full
16 announcement 5895
17 route-to meetme
18 stop
19 announcement 5896
20 route-to meetme
21 stop
22 disconnect after announcement 5897

 

And I do have older equipment by the way. Avaya 8700m, 20 years old and CM3.0. So maybe that's why I had these issues.
 

"or one following the other without interruption"

Check your system parmeters. Use command: disp sys feat

Check under Vectoring for Prompting Timeout (secs). Sounds like the system isn't waiting for digit input.

- Stinney

I love learning and passing on knowledge. "Because knowing is half the battle"....
 

VECTORING


Prompting Timeout (secs): 10

What would that mean exactly?
 

System will wait 10 seconds after a collect step for user input. That's a long time IMHO.

When you said the call at times was skipping right to the next announcement one after another, it sounded like the timeout wasn't set, so there was no pause for a user to put in anything.

Looking at your trace, this doesn't seem to make sense if you didn't enter any digits after 3961 or 3963 there should have been 10 seconds of delay before moving on. It looks like it's only waiting 3 seconds...

11:49:48 50 1 collect
11:49:48 50 1 announcement: board 03A14 ann ext: 3961
11:49:51 50 2 goto
11:49:51 50 3 collect
11:49:51 50 3 announcement: board 03A14 ann ext: 3962
11:49:54 50 4 goto
11:49:54 50 5 collect
11:49:54 50 5 announcement: board 03A14 ann ext: 3963
11:49:56 50 6 goto
11:49:56 50 7 disconnect

If you call the vector and don't make an entry, it should wait 10 seconds before it moves on.


- Stinney

I love learning and passing on knowledge. "Because knowing is half the battle".... ??GI JOOOOOE??
 

Yes, this doesn't make any sense. But I have had a lot of list traces where I didn't hear the first announcement and after 10 seconds of waiting I heard the second announcement. So the problem was mainly that my first announcement was not audible, though the vector said it was played. I also had announcements being played one after another with no pause in between at all. But I hope it is all solved now with the "wait 1 seconds hearing ringback" solution.
Thanks again, that was great help.
 

If you are curious to find out why the announcements were playing one after the other and not waiting, you can see if there were erroneous digits being detected.

Add a variable (command: ch var) that is a collect variable and add it to the vector.

If you are using C as variable you would change the type to collect, change the scope to L (for local), Length to 16 (just to make sure you capture all the digits), Start to 1 (to start at the first digit).

Then change your vector collect steps to: collect 6 digits after announcment xxxx for C

Then remove your ring steps in between the collect steps (leave the first one there) and do a list trace of the vector again.

Now the trace will show you what digits are collected by displaying the variable value.



- Stinney

I love learning and passing on knowledge. "Because knowing is half the battle".... ??GI JOOOOOE??
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top