[cisco-voip] Issue with Meetme number and Conf Bridge

[Nathan Reeves]

Hitting my head against the wall on this one.  If anyone has any
suggestions, I'd love to know about them.  Scenario as follows:

Have a Meetme number that's been in use without issue.  Had a report
this morning that it is giving a fast busy when trying to setup a
meetme conf via a phone.  I setup a phone as per the site (It's remote
to me) and found the same issue.  If I go one number down, things
work.  Eg, meetme number is 9599 which doesn't work, 9598 does work.
The meetme number range is setup as 959[6-9] in CCM.

Things I've checked / done:
   - The route plan report to make sure no-one has used this number.
The report only shows it in use in the meetme number range.
   - Run the number through DNA and I get it marked as a Meetme number.
   - Reset the dspfarm on the router that hosts the CFB
   - Reset the CFB from the CCM Admin pages.
   - Checked all CFB's we have running via perfmon and no-one has any
open meetme conferences in operation.
   - No route patterns or translation patterns include this number pattern.
   - Deleted the meetme range and set it up again.
   - Done a debug isdn q931 on the site's voice router and haven't
seen it try and call out when I dial 9599.
   - Checked open bugs against our running version [CCM4.1(3)sr3a] and
found nothing I can see which is related.

The only notable item is that if I dial the 9599 number from a phone
without trying a meetme setup, I get "Your call could not be completed
as dialled....".  If I dial 9598 (which works as a meetme) I just get
a straight fast busy.

I tries a trace without much luck.  Can see the call being made into
9699 but can't see a reason for denial at the CFB end. I may have the
trace parameters setup wrong.

No changes (that I know of) have been made that might cause this issue.

Any suggestions welcome.

Cheers