sundance-communications.com/forum Forums TDM Business Telephone Systems Comdial Telephones & Systems ARS Modify Digits

I'm missing something here, and I'm guessing it's something pretty simple.

FXII 17E. Using ARS, trying to figure out the Modify Digits method. I haven't done this in a long time, and probably only once since they changed to the 16A-style Modify Digits format.

Can someone please give me a simple run-down on how to add digits to the beginning of a dialed string, and then adding digits to the end of a dialed string? I think I understand the Delete Digits part, but for some reason I'm having trouble getting it to add digits. I have the string pointing to a different route table, which uses Modify Digits Table 2 (all else using Route 1, Modify 1), and yes, ARS is enabled. What am I missing here?

Thanks!

Example:

If you have a centrex application and you don't want to double dial 9 then your string would look like this:

I:9p CR

Insert: 9 pause CR initiates string insert into ARS call

Okay, then I'm missing something else. Here's what I was doing to test:

In the restriction table, following all other entries, I put 1212. I setup this entry to use Route Table 2, which used Modify Table 2.

Route Table 2 uses same line group. Modify Table 2 has "I:555,CR". The end result should be 555-1212, when I dial 1212. The call is going through as 1212, which of course comes back as not a valid number recording from the carrier.

Not sure if it matters, but since this is a PRI, I'm setting up other entries in the restriction table as discussed in the last couple posts of this previous topic .

Shouldn't that work, or is there something in the restriction table that's causing it to fail?

How would the ARS know the difference between a 1212 call and a 1212-xxx-xxxx call?

Based on the other entries in the ARS table, that's how it would know. The entries preceding the "1212" entry are "2@@@@@@", "3@@@@@@", thru "9@@@@@@", as well as "1@@@@@@@@@@" and others. These other entries allow the ARS to wait until enough digits are entered before proceeding with the Dialing Complete timer.

I know that it recognizes 1212, because it puts the call thru to the carrier after the dialing complete timer has expired (4 seconds after dialing 1212).

Call me dense but as I see it your 2@@@@@@ would be local nxx calls starting with 2 etc. Your 1@@@@@@@@@@ would be 1 plus LD calls. Your 1212 would look like the start of a New York long distance call and is timing out expecting to receive more digits.

Looks like you need to use Toll/ARS dialing Pause.
Turn this on in system parms. then add a P to then end of the 1212 string.

I had tried that as well. Same results. I think the problem might have something to do with the other entries.

The dialing pause is designed for that reason.

You can enter a pause at the end of a toll restricted number to indicate that dialing is complete. For ARS purposes, the pause lets the system distinguish between similar numbers. This feature merely enables the dialing pause; you still must enter the pauses where necessary in each toll restricted number.


It is matching some other entry. Remove or Deny all entries that match. Then add them back one at a time to see which one its matching.

Put the dialing rule 1212p before any other 1+ rule. That will triger a match. Also make sure that ARS is re-activated after the rule change.
All other advise given above is correct. I would also set the puase timmer out to at least 2 sec.