[cisco-voip] Attendant Console Setting in CM

[Paul Yago]

I'm trying to use the Pilot Point and the Hunt Group setting, under the
Attendant Console Menu in CCM Admin.

 

 

And when I have the following:

 

            1) Pilot Point (8000) with 

                        Longest Idle Time algorithm

 

            2) TCD is configured with:

                        "Allow Routing with Unknown Line State" = True

 

            3) With acconfig.bat

                        "Enable Queuing" set to false.

 

            4) 2 phone extensions (A and B) in the hunt group

                        Both support 4 lines maximum with a busy trigger
of 2.

                        "Always Route Member" is False for both members.

 

 

..and would expect/like the following to occur:

            

            1) When Caller 1 dials the Pilot Point (8000), the call
should be directed to phone A and phone A and start ringing. 

            

            2) Then caller 2 dials 8000 immediately and the call is
directed to phone B. 

            

            3) Caller 3 dials 8000 immediately afterwards and phone A,
whose line 1 is already busy, rings on its second line. 

            

            

...what actually happens is:

            

            1) When Caller 1 dials the Pilot Point (8000), the call
should be directed to phone A and phone A and start ringing. 

            

            2) Then caller 2 dials 8000 immediately and the call is
directed to phone B. 

            

            3) Caller 3 dials 8000 and this number is queued frozen on
the display until a busy signal finally arrives.

 

 

What I've tried is:

 

            1) Allow Routing with Unknown Line State = False. 

                        Same result

            

            2) Allow Route Members is True for both members. All the
calls are routed to the first member regardess of the state (busy or
occupied). Phone A is certainly not the longest idle phone, yet a new
call is routed there instead of the Phone B. It seems that the Longest
Idle Time algorithm doesn't take the "Route All Calls" property into
consideration. I also changed "Allow Routing with an Unknown Call State"
to both True and False with the same problem.

            

            3) Tried -  Long Idle, Circular, and First Available all
with the same result.

            

            

Questions:

            

            1) Why doesn't the Longest Idle Hunt Group algorithm use the
second member?

            

            2) How is Idle Time determined for HG members?

            

            3) Without Always Route Member = True, can *multiple*
incoming calls be routed to an extension? And if not, then can the
property *Always Route Member* be set to False, where this HG member
does not eat up all the incoming calls?

            

            4) Can I somehow define my own line states and report on
them; having them return vales to which the hunt pilot/group can react?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20050603/7f8a7286/attachment.html