Attendant Console Queue issue

Unanswered Question
Feb 8th, 2010

/* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-qformat:yes; mso-style-parent:""; mso-padding-alt:0cm 5.4pt 0cm 5.4pt; mso-para-margin-top:0cm; mso-para-margin-right:0cm; mso-para-margin-bottom:10.0pt; mso-para-margin-left:0cm; line-height:115%; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:"Times New Roman"; mso-fareast-theme-font:minor-fareast; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;}

Hi All

I have be requested to set up the following:- If all Agents are logged out of the attendant Console, the Call routes to a hunt Group, (to achieve this I had to create a CTI Route point that forwards to the Hunt List) which is selected to an always route member. This hunt list contains the option to Log in/out. If all members are busy or logged out the call queues on the Attendant console pilot point and caller hears music on hold.

This issue I have is as follows  when all agents are logged out of the attendant console :- All works well until a user has been in the queue for more than around 50 to 60 seconds; the system just keeps the caller on hold indefinitely regardless if the call can be routed or not. When a second call comes in it routes fine (until the 50/60 second hold time is reached.)

Has anyone experienced this as well or is there an enterprise parameter that needs to be adjusted.

Software running is  CallManger

Many thanks


I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)


This Discussion