Vector not processing the same for all call types

[CaptObvious26]

We have two vectors setup for our call center. If I call either internally it will play an announcement, then ring back while it waits for the hunt group to answer. If the call comes from outside the pbx and is transferred to the vector it will not ring back after the announcement. Weirder yet, if the caller is off pbx and dials the vector directly instead of being transferred from an operator, it will play the ring back fine. Thoughts? is there a setting that I need to change in the vectors? Perhaps the operator stations need adjusted.


display vector 12 Page 1 of 6
CALL VECTOR

Number: 12 Name: CallCenterSvc
Multimedia? n Attendant Vectoring? n Meet-me Conf? n Lock? n
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 step 20 if time-of-day is sat 00:01 to sat 08:00
03 goto step 20 if time-of-day is sat 16:00 to sun 23:59
04 goto step 20 if time-of-day is all 18:00 to all 07:30
05 announcement 1723
06 wait-time 2 secs hearing ringback
07 queue-to split 26 pri l
08 collect 1 digits after announcement 1727
09 wait-time 1 secs hearing ringback
10 goto step 19 if digits = 1
11 goto step 13 if unconditionally
12 stop
display vector 12 Page 2 of 6
CALL VECTOR
13 announcement 1725
14 announcement 1728
15 announcement 1729
16 announcement 1730
17 announcement 1731
18 stop
19 messaging split 98 for extension 1652
20 messaging split 98 for extension 1650
21
22

display hunt-group 26 Page 1 of 60
HUNT GROUP

Group Number: 26 ACD? n
Group Name: Call Center Queue? y
Group Extension: 1650 Vector? y
Group Type: ucd-mia
TN: 1
COR: 1 MM Early Answer? n
Security Code: Local Agent Preference? n
ISDN/SIP Caller Display:

Queue Limit: unlimited
Calls Warning Threshold: Port:
Time Warning Threshold: Port:

 

[montyzummer]

i dont think the link is your issue.

the latest firmware for the gw is 32.26.0 disp media-gateway x to find this. Your ds1 board is also out the latest firmware is 53.

Your cm is quite a few sp behind the latest one is 02.0.823.0-21388 ,there will be a new kernal patch and bash shell shock , system platform will need patching also unless you are in a VMware environemt.

I would look at getting this lot upgraded and if the fault persists .. log with avaya as im pretty positive your programming is air tight , so this is leading to a bug or as mentioned corruption in the db.

APSS (SME)
ACSS (SME)
ACIS (UC)

 

[CaptObvious26]

http://www.tek-tips.com/viewthread.cfm?qid=1693265

This sounds like our issue... I'm contacting our telecom vendor to update our system.

 

[smokinjoe2938]

it also mentions system par coverage

 

[montyzummer]

Good decision ,,, then kick there arse and ask them why they are not doing this as per your maintenance agreement on a regular basis (once every 6months is how we do it with our customers)

APSS (SME)
ACSS (SME)
ACIS (UC)