I have a fairly minor, but annoying issue with configuring some translation patterns on my ASR 1006 that is acting as a CUBE.
I'm attempting to prepend an area code and extension to a 5-digit dialed number. My translation pattern on my CUBE looks like this:
This replaces an extension (as an example, 34567) a number that's routable - 555-123-4567
However, trying this on my ASR, I cannot use the same pattern, as I get an invalid syntax error if I include the $ in the match pattern. So /^3....$/ gives a syntax error at the start of the first match, but /^3..../ does not.
The issue with leaving it as /^3..../ is that if I have a number that starts with 3 and is MORE than 5 digits, it still prepends the 55512 to that number.
So my question is, what is the appropriate syntax on the ASR to ensure that the translation rule matches only a 5 digit number? Or have I encountered a bug?
Actually, it was very simple.
I talked to TAC, they suggested turning off "shell processing full". Apparently these ASRs have a shell interpreter built into them. All I had to do was escape the $ character in my match.
So the correct command was /^3....\$/ /55512&/
Might be useful for anyone else who runs into this problem