Auto Attendant frustration
azrobert:
Do you receive CallerID for the other DID's?
If yes, route those to PH and default everything else to the AA.
{(xx.):ph},{aa}
ianobi:
I now have the complete answer :)
{(?|anon@@.):aa},{ph} Peer Number blank routes to aa, Peer Number “anonymous” and any Peer Number starting “anon” routes to aa. All other numbers routes to ph. This is a good solution to the problem.
The reason my other attempts failed is because "anonymous" and "strange" and "stra" all contained reserved letters - in this case "m" and/or "s". putting single quotes around them fixes this. So:
{(?|anony'm'ou's'):aa},{ph} also works.
@jimates - another observation from cutting and pasting. I tried pasting anony'm'ou's' from a word doc and it did not work. letters work fine, but punctuation marks don't for some reason. Typing direct into the OBi X_InboundCallRoute worked fine. That's two times I have been caught that way!
QBZappy:
ianobi,
Quote from: ianobi on August 31, 2012, 08:42:47 am
The reason my other attempts failed is because "anonymous" and "strange" and "stra" all contained reserved letters - in this case "m" and/or "s". putting single quotes around them fixes this. So:
{(?|anony'm'ou's'):aa},{ph} also works.
Indeed reserved letters has come up before. Nice work. Just for curiosity, in what context are these reserved letters used?
ianobi:
That's a good question! m, M, s, S, x, X are the letters quoted on page 183 of the latest AdminGuide. I can only really see "x" being relevant to InboundCallRoute.
Hortoristic:
Pretty genious of you!
So it this right - any number beginning with 1604, blank or begins with "anon" will go to AA?
{(1604xxxxxxx|?|anon@@.):aa},{ph}
Navigation
[0] Message Index
[#] Next page
[*] Previous page