Calls Stuck In Hunt Group

[medicshelley]

Here's my scenario A front desk admin transfers a call to the hunt group extension instead of the VDN extension and the call gets stuck within the hunt group. I have RONA enabled but that doesn't help the issue. What should I do to make sure if a call gets transferred to the hunt group extension that the call doesn't sit there for ever and eventually hang up?

 

[banerjeebidyut]

Hello Shelley ,

Can you provide a list trace of a bad call

 

[Stinney]

Add an entry in the ars digit-conversion table to convert the Hunt Group extension to the VDN you want the call transferred to?

So if the hunt group extension is 12345 and the VDN is 45678 your ars digit-conversion entry would be:

ch ars digit 12345

then enter in the table:

Matching Pattern___Min___Max___Del___Replacement String___Net___Conv___ANI Req

12345_____________5_____5____5_____45678_____________ext____n_______n


- Stinney

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

 

[montyzummer]

Stinney how is the call going to know to enter ARS tables ?( i just dont think that would work)

The RONA time must obviously have a valid vdn assigned underneath the entry and acd must be y on on pg1 of the hunt group form , as suggested can you post a trace of a stuck call?

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

 

[Stinney]

It wouldn't, sorry about that, wasn't thinking.

The call won't RONA if it's not delivered in the first place, so would it really matter if RONA isn't defined?

What if you put the attendant in her own COR and your hunt groups in a new COR and then restrict the attendant's COR from calling the hunt group's cor? Then she would have to transfer to the VDN.

- Stinney

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

 

[Armstrong2012]

I have a weird problem. I have a hunt group and some people are reporting that when they call into the hunt group they hear our loop of messages in the call vector 2 times and then are cut off. Does anyone see anything wrong in the programming that would cause this?

If no one is logged into the hunt group would that cause a busy signal?



------------------------

VECTOR DIRECTORY NUMBER

Extension: 43266
Name*: FA
Vector Number: 202
Attendant Vectoring? n
Meet-me Conferencing? n
Allow VDN Override? n
COR: 1
TN*: 1
Measured: none



HUNT GROUP

Group Number: 12 ACD? y
Group Name: FA Queue? y
Group Extension: 52212 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: 1 Port:
Time Warning Threshold: Port:




CALL VECTOR

Number: 202 Name: FA
Multimedia? n Attendant Vectoring? n Meet-me Conf? n Lock? n
Basic? y EAS? n G3V4 Enhanced? y ANI/II-Digits? y ASAI Routing? n
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 16 if holiday in table 1
03 goto step 16 if time-of-day is fri 17:00 to mon 08:15
04 goto step 16 if time-of-day is all 18:00 to all 08:15
05#announcement 52408
06 queue-to split 12 pri m
07 wait-time 4 secs hearing silence
08 announcement 52424
09 wait-time 4 secs hearing silence
10 announcement 52414
11 wait-time 4 secs hearing silence
12 collect 1 digits after announcement 52406
13 goto vector 200 @step 1 if digits = #
14 goto step 5 if unconditionally
15 stop
16 disconnect after announcement 52189