<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML dir=ltr><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=unicode">
<META content="MSHTML 6.00.2715.400" name=GENERATOR></HEAD>
<BODY>
<DIV id=idOWAReplyText96227 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2>Look at this link for which I
am sure you already have but you can always download for your
reference.</FONT></DIV>
<DIV dir=ltr><A
href="http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_administration_guide_chapter09186a00803f3a8b.html#wp1146190">http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_administration_guide_chapter09186a00803f3a8b.html#wp1146190</A></DIV>
<DIV dir=ltr> </DIV>
<DIV dir=ltr>Brian</DIV></DIV>
<DIV dir=ltr><BR>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> cisco-voip-bounces@puck.nether.net on
behalf of Jonathan Charles<BR><B>Sent:</B> Mon 1/30/2006 11:27 PM<BR><B>To:</B>
cisco-voip@puck.nether.net<BR><B>Subject:</B> [cisco-voip] Attendant Console
issue<BR></FONT><BR></DIV>
<DIV>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.<BR><BR>If we bypass the AC Pilot Point, and go straight to Unity,
everything is peachy.<BR><BR>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...<BR><BR>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)...<BR><BR><BR>Any
ideas?<BR></DIV></BODY></HTML>