[cisco-voip] Attendant Console configuration questions

Sun Feb 4 16:39:14 EST 2007

Everything works (calls can be made and all internal calls monitored, 
directory is good, etc.), other than I get reorder tone when dialing the 
Pilot Point for the AC Hunt Group.  I've checked everything in the F&SG 
checklists -- CcmLineLinkState is 11, ac user password is 12345, TCD and 
CTIManager have been restarted, Pilot Point and all DNs on all AC user 
devices are associated with ac, Pilot Point is unique, etc.  Tried to use 
Trace to see what TCD and CTIManager were doing, but got no SDL entries and 
"Document empty or invalid!!" for SDI entries. Any ideas?

Based on what I've seen so far, things work as I assumed as far as user 
lines and DNs go, but until I can actually use the Hunt Group, I'm doing a 
lot of guessing.

Mike

> Date: Sat, 3 Feb 2007 14:34:39 -0500
> From: "Mike Armstrong" <mfa at crec.ifas.ufl.edu>
> Subject: Re: [cisco-voip] Attendant Console configuration questions
> To: <cisco-voip at puck.nether.net>, "Ryan Ratliff" <rratliff at cisco.com>
> Message-ID: <057901c747ca$5957f150$0402a8c0 at crec.ifas.ufl.edu>
> Content-Type: text/plain; format=flowed; charset="iso-8859-1";
> reply-type=original
>
> Thanks, Ryan.  I assume then that if I have all 6 lines in the hunt group,
> but the user logs in on a phone with only 2 lines, then lines 3-6 will
> return busy, and the hunt will move on?  I could then define several ac
> users -- say, ac1, ac2, ... ,ac6, with the corresponding number of lines,
> and the user could log in and assume responsibility for handling "n"
> simultaneous calls?
>
> Mike
>
>> Date: Sat, 3 Feb 2007 11:37:34 -0500
>> From: Ryan Ratliff <rratliff at cisco.com>
>> Subject: Re: [cisco-voip] Attendant Console configuration questions
>> To: Mike Armstrong <mfa at crec.ifas.ufl.edu>
>> Cc: cisco-voip at puck.nether.net
>> Message-ID: <F16FA688-EE0F-4FD5-95BF-7695FD62E3AC at cisco.com>
>> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
>>
>> 1) AC user in the CCM directory needs to have password and pin of
>> '12345'.  PIN doesn't really matter but the password must be '12345'
>> unless you use acconfig.bat to change it.
>>
>> 2) There is no correlation whatsoever between an AC user and a user
>> in the global directory.  You can make them the same if you wish.
>>
>> 3) The line number on a 7960 is going to be something from 1-6.  It
>> is not the DN of the line.    If you have all 6 of the user's lines
>> added to the hunt group then yes it will hunt on all 6 lines.  This
>> is done so that the AC user can switch phones and the hunt group will
>> use the new lines with no extra configuration necessary.  If the user
>> is controlling a phone with only 1 line that that line will be the
>> only one that receives calls.
>>
>> -Ryan
>>
>> On Feb 3, 2007, at 11:26 AM, Mike Armstrong wrote:
>>
>> I'm hoping to bring up Attendant Console on a 4.1(3) system on
>> Monday, and
>> have limited test time tomorrow to work it out.  Can anyone answer the
>> following questions?  Or, can you recommend a better reference that the
>> Features and Services Guide?
>>
>> 1) When configuring the "ac" user, Step 6 in the F&SG says "Enter a
>> PIN and
>> telephone number."  Is there any particular DN one should enter?  Or
>> will
>> any random number work?
>>
>> 2) When configuring Attendant Console Users, F&SG says "attendant
>> console
>> user IDs and passwords are _not_ the same as Directory users...".
>> Does that
>> mean they _must not_ be the same?
>>
>> 3) When adding Hunt Group members, if the member to be added is a "user
>> member", a User Name and Line Number is required.  I assume the User
>> Name is
>> an "attendant console user ID" configured as in (2).  What is the Line
>> Number?  The physical line appearance on the phone the User is currently
>> associated with?  If so, does that mean a User associated with a 7960
>> will
>> receive AC calls on all 6 lines, regardless of DN?  Or is it a
>> logical line
>> of some kind?  If the User is currently associated with a phone
>> having only
>> a single line appearance, but it is configured to accept 6 simultaneuous
>> calls, can I use Lines 1 to 6 when configuring the user member?  In
>> either
>> case, what happens to "lines" 2-6 if she's associated with a one line,
>> one-call only phone?
>>
>> Thanks (I hope)...
>>
>> Mike Armstrong
>> UF/IFAS CREC
>> Lake Alfred, FL
>>
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>>
>> ------------------------------
>>
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>>
>> End of cisco-voip Digest, Vol 48, Issue 19
>> ******************************************
>
>
>
> ------------------------------
>
> Message: 2
> Date: Sat, 3 Feb 2007 15:38:54 -0500
> From: Ryan Ratliff <rratliff at cisco.com>
> Subject: Re: [cisco-voip] Attendant Console configuration questions
> To: "Mike Armstrong" <mfa at crec.ifas.ufl.edu>
> Cc: cisco-voip at puck.nether.net
> Message-ID: <38AD72FB-2E33-48E9-939F-EA969AAB6F2B at cisco.com>
> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
>
> Honestly I've never tried it the way you describe.  I'd hope that AC
> simply would ignore the unavailable lines but I'd recommend testing
> it before putting into production.
>
> -Ryan
>
> On Feb 3, 2007, at 2:34 PM, Mike Armstrong wrote:
>
> Thanks, Ryan.  I assume then that if I have all 6 lines in the hunt
> group, but the user logs in on a phone with only 2 lines, then lines
> 3-6 will return busy, and the hunt will move on?  I could then define
> several ac users -- say, ac1, ac2, ... ,ac6, with the corresponding
> number of lines, and the user could log in and assume responsibility
> for handling "n" simultaneous calls?
>
> Mike
>
>> Date: Sat, 3 Feb 2007 11:37:34 -0500
>> From: Ryan Ratliff <rratliff at cisco.com>
>> Subject: Re: [cisco-voip] Attendant Console configuration questions
>> To: Mike Armstrong <mfa at crec.ifas.ufl.edu>
>> Cc: cisco-voip at puck.nether.net
>> Message-ID: <F16FA688-EE0F-4FD5-95BF-7695FD62E3AC at cisco.com>
>> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
>>
>> 1) AC user in the CCM directory needs to have password and pin of
>> '12345'.  PIN doesn't really matter but the password must be '12345'
>> unless you use acconfig.bat to change it.
>>
>> 2) There is no correlation whatsoever between an AC user and a user
>> in the global directory.  You can make them the same if you wish.
>>
>> 3) The line number on a 7960 is going to be something from 1-6.  It
>> is not the DN of the line.    If you have all 6 of the user's lines
>> added to the hunt group then yes it will hunt on all 6 lines.  This
>> is done so that the AC user can switch phones and the hunt group will
>> use the new lines with no extra configuration necessary.  If the user
>> is controlling a phone with only 1 line that that line will be the
>> only one that receives calls.
>>
>> -Ryan
>>
>> On Feb 3, 2007, at 11:26 AM, Mike Armstrong wrote:
>>
>> I'm hoping to bring up Attendant Console on a 4.1(3) system on
>> Monday, and
>> have limited test time tomorrow to work it out.  Can anyone answer the
>> following questions?  Or, can you recommend a better reference that
>> the
>> Features and Services Guide?
>>
>> 1) When configuring the "ac" user, Step 6 in the F&SG says "Enter a
>> PIN and
>> telephone number."  Is there any particular DN one should enter?  Or
>> will
>> any random number work?
>>
>> 2) When configuring Attendant Console Users, F&SG says "attendant
>> console
>> user IDs and passwords are _not_ the same as Directory users...".
>> Does that
>> mean they _must not_ be the same?
>>
>> 3) When adding Hunt Group members, if the member to be added is a
>> "user
>> member", a User Name and Line Number is required.  I assume the User
>> Name is
>> an "attendant console user ID" configured as in (2).  What is the Line
>> Number?  The physical line appearance on the phone the User is
>> currently
>> associated with?  If so, does that mean a User associated with a 7960
>> will
>> receive AC calls on all 6 lines, regardless of DN?  Or is it a
>> logical line
>> of some kind?  If the User is currently associated with a phone
>> having only
>> a single line appearance, but it is configured to accept 6
>> simultaneuous
>> calls, can I use Lines 1 to 6 when configuring the user member?  In
>> either
>> case, what happens to "lines" 2-6 if she's associated with a one line,
>> one-call only phone?
>>
>> Thanks (I hope)...
>>
>> Mike Armstrong
>> UF/IFAS CREC
>> Lake Alfred, FL
>>
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>>
>> ------------------------------
>>
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>>
>> End of cisco-voip Digest, Vol 48, Issue 19
>> ******************************************
>
>
> ------------------------------
>
> Message: 3
> Date: Sat, 3 Feb 2007 21:50:21 +0100
> From: "Bernhard Albler" <balbler at nts.at>
> Subject: [cisco-voip] web admin problems with 5.1
> To: <cisco-voip at puck.nether.net>
> Message-ID: <5A8C69748176434F92F1EECD7D21F72CA3C179 at srvgraz03.nts.at>
> Content-Type: text/plain; charset="us-ascii"
>
> Hi all,
>
> this is kind of a non issue, still i would be interested if someone else
> has seen this (if it is worth to report this to tac as a bug):
> We recently installed a lab system with 5.0(4) and then upgraded to 5.1.
> Now the web interface seems to show only lookup keys in some areas
> instead of the correct entries, such as(see attached screenshot for
> example):
>   * MLPP States: MLPP_DEFAULT instead of just Default in the dropdown
>   * Application Server Names (see screenshot)
>   * Etc...
>
> Kind of strange. I rebootet the box to the 5.0(4) install on the
> inactive partition, there all fields are correctly populated.
> Anyone seen this already?
>
> Regards
> bernhard
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: ccmadmin_error.PNG
> Type: image/png
> Size: 21559 bytes
> Desc: ccmadmin_error.PNG
> Url : 
> https://puck.nether.net/pipermail/cisco-voip/attachments/20070203/43214245/attachment.png
>
> ------------------------------
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
> End of cisco-voip Digest, Vol 48, Issue 21
> ****************************************** 