[cisco-voip] Attendant Console issue

[Ortiz, Carlos]

Last week (Tim Reimers I think) suggested to me that we set up a CM Hunt
pilot and just have it broadcast to the destination phones(in a line
group).  You still can use Attendant console to manage the calls, but I
think I actually like it better than using the AC broadcast feature.
I'd be interested to know what other folks are doing, especially when
you have a main DN that is being answered by multiple attendants.

 

Carlos

 

________________________________

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Brian Henry
Sent: Tuesday, January 31, 2006 6:56 AM
To: Jonathan Charles; cisco-voip at puck.nether.net
Subject: RE: [cisco-voip] Attendant Console issue

 

Look at this link for which I am sure you already have but you can
always download for your reference.

http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_administra
tion_guide_chapter09186a00803f3a8b.html#wp1146190

 

Brian

 

________________________________

From: cisco-voip-bounces at puck.nether.net on behalf of Jonathan Charles
Sent: Mon 1/30/2006 11:27 PM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] Attendant Console issue

We have a CCM 3.3(4)es22 that has a main number, x4100, which hits an
Attendant Console pilot point, and a hunt group with one member, x4199,
that goes to Unity.

If we bypass the AC Pilot Point, and go straight to Unity, everything is
peachy.

If we hit the AC Pilot Point, we get a fast busy... and the system
traces complain that no potential matches exist (instead matching the
[2-8]XXX pattern...

We are curious as to why the AC PP is not working, why the CCM doesn't
see the 4100 pattern as valid (even though it shows up quite clearly in
the route plan report)...


Any ideas?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20060131/1c40f7ad/attachment.html