[cisco-voip] Attendant Console issue

[Brian Henry]

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_administration_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/2e78bdf6/attachment.html