Day Announcment not being played 2

[vulcanccit]

I am new to vectoring. Our vendor has one of our Avaya markets set up like this:

Number: 90 Name: ELP Main Line
Multimedia? n Attendant Vectoring? y Meet-me Conf? n Lock? y
Basic? y EAS? n G3V4 Enhanced? y ANI/II-Digits? y ASAI Routing? y
Prompting? y LAI? n G3V4 Adv Route? y CINFO? y BSR? n Holidays? y
Variables? n 3.0 Enhanced? n
01 wait-time 2 secs hearing ringback
02 goto vector 91 @step 1 if service-hours not-in table 9
03 goto vector 91 @step 1 if holiday in table 2
04 queue-to attd-group
05 wait-time 30 secs hearing ringback
06#announcement 8890424
07 goto vector 91 @step 1 if unconditionally

During the day, the day announcement never plays so if no one is at the attendant, it just rings and rings.. does the programming look correct? 8890424 is recorded.

what is the best way to trace the call flow? would be list trace vector 8890900 (which is the main number vector.

I saw another example here on this forum where the wait-time step proceeded the queue-to step... I have a message into our vendor but I have not heard back, I thought I would try this forum..

 

[Tolson]

The problem is the announcement is commented out. If you look on line 6 you will see a # symbol. You need to remove it before the announcement will play.

 

[vulcanccit]

Wow, so easy! I saw that there and I am familiar with comments in other programming languages but was not sure if that was a comment or why it was there. Our vendor must of put that in there during some kind of test during our rollout. Thank you so much for being a second set of eyes on this! Happy New Year to you!

 

[vulcanccit]

I uncommented that line and it still just rings and rings...

here is the vector:

Number: 90 Name: ELP Main Line
Multimedia? n Attendant Vectoring? y Meet-me Conf? n Lock? y
Basic? y EAS? n G3V4 Enhanced? y ANI/II-Digits? y ASAI Routing? y
Prompting? y LAI? n G3V4 Adv Route? y CINFO? y BSR? n Holidays? y
Variables? n 3.0 Enhanced? n
01 wait-time 2 secs hearing ringback
02 goto vector 91 @step 1 if service-hours not-in table 9
03 goto vector 91 @step 1 if holiday in table 2
04 queue-to attd-group
05 wait-time 30 secs hearing ringback
06 announcement 8890424
07 goto vector 91 @step 1 if unconditionally
08







trace is below of the VDN

Number: 90 Name: ELP Main Line
Multimedia? n Attendant Vectoring? y Meet-me Conf? n Lock? y
Basic? y EAS? n G3V4 Enhanced? y ANI/II-Digits? y ASAI Routing? y
Prompting? y LAI? n G3V4 Adv Route? y CINFO? y BSR? n Holidays? y
Variables? n 3.0 Enhanced? n
01 wait-time 2 secs hearing ringback
02 goto vector 91 @step 1 if service-hours not-in table 9
03 goto vector 91 @step 1 if holiday in table 2
04 queue-to attd-group
05 wait-time 30 secs hearing ringback
06#announcement 8890424
07 goto vector 91 @step 1 if unconditionally


If I manually dial the announcement it is recorded and plays correctly.

 

[vulcanccit]

ooops I didnt paste the trace...here is the trace
time prt st data

11:36:37 TRACE STARTED 01/07/2013 CM Release String cold-00.1.510.1-19736
11:36:49 0 0 ENTERING TRACE cid 10955
11:36:49 90 1 vdn e8890900 bsr appl 0 strategy 1st-found override y
11:36:49 90 1 wait 2 secs hearing ringback
11:36:51 90 2 goto vec 91 @step 1 if service-hours not-in table 9
11:36:51 90 2 Time before adjusting: MON 11:36
11:36:51 90 2 Time after adjusting: MON 11:36
11:36:51 90 3 goto vec 91 @step 1 if holiday in table 2
11:36:51 90 4 queue-to
11:36:51 90 4 LEAVING VECTOR PROCESSING cid 10955
11:36:51 90 4 TRACE COMPLETE cid 10955

 

[bleebrant]

When you are doing the test call is it actually ringing at the attendant console? If so, then the vector steps are considered complete as shown in your trace. If the attendant is already on a call when your test call is placed, then the call is queued and steps 5 and 6 are processed (caller hears 30 seconds of ringing, then announcement 8890424 and then directed to vector 91)
Does the attendant press the Position Busy button when leaving the consolez/

 

[vulcanccit]

This system is in another city. I found out two things. First that announcement was commented out for a reason, there is a second vector, 91 which is the actual Day Message and Night message vector. So the announcement never should play from Vector 90 And as you said BeeBrant, the position busy was not pushed so it never would go to 91. So all is well. I thank you all for helping!!