[cisco-voip] Attendant Console issue

[Jonathan Charles]

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/20060130/68fc287f/attachment.html