Getting DNIS error in "Rabbit-Hole" configuration

[ben-matson]

I've got our ATLAS 500 all configured with the "Rabbit-Hole" configuration and are able to make and receive calls, but when I connect the unit to our alarm receiver and do a test call it reports it isn't getting a valid DNIS.  When I connect a test set and call the unit when I pick up the line I get a single string of DTMF, but according to my receiver guide I need a 500msec pause, send DNIS, a 2000msec pause, then send ANI, so I should be able to hear a pause between the the DNIS and ANI DTMF, but all I hear is one long string of DTMF.  Is there any settings I'm missing to set this timing?

Thank you,

Ben

[Anonymous]

The ATLAS rabbit-hole configuration does not have any "pause" by default. The DTMF digit has a duration of roughly 75 ms, with an interdigit delay of roughly 75 ms as well. The DTMF digits are in the format of *ANI*DNIS* with the asterisk (*) being transmitted at the beginning of the digit string, in between the ANI and DNIS, and then to signify the end of the digit string. The ANI is transmitted first, followed by the DNIS.

It may be possible to add a pause under the DIAL PLAN in the SUBSTITUTION TEMPLATE to some extent. A comma (,) can be used to introduce a 1/2 second delay, but the comma is also considered a "digit" so you will have to adjust the DID DIGITS TRANSFERRED to include the comma(s). The asterisks (*) will be transmitted and cannot be removed in the substitution template, as they are the delimiters to indicate the start of the digit string, the separation between ANI and DNIS, and the end of the digit string. This is the ATLAS' implementation of Feature Group D using DTMF tones (as opposed to MF tones - and the ATLAS 550 does not support MF tones).

So to add a 500 ms delay before the DNIS, you can set up the SUBSTITUTION TEMPLATE with a DNIS ORIG # of "XXXX" and a DNIS SUBST # of ",XXXX".

Hope this helps to clear a few things up,

Patrick

[ben-matson]

I need to verify the Adtran is sending the ANIDNIS* with 500ms of

answering, and do I need to answer the call after the second ring or can I

answer it after the first ring?

-Ben

[Anonymous]

Yes, the ATLAS begins transmitting the *ANI*DNIS* digit string within 500 ms of the call being answered.

It is actually preferable to answer the call after the first ring. If you wait until after the second ring you run the risk of an ISDN timer expiring prior to the call being answered.

[ben-matson]

Patrick,

We recorded a call and it looks like the Atlas 550 is not sending the *ANI*DNIS* with 500ms of the call being answered.  Is there a setting where we can adjust this?

-Ben

[Anonymous]

The short answer is that no, there is no way in the ATLAS to speed up the transmission of the DTMF digits.

The ATLAS begins transmitting the DTMF digits approximately 75-100 ms after the WINK has been detected, and the WINK lasts approximately 200 ms. The "rabbit-hole" ads delay, so the only way to speed it up would be to add an external device to Take the RBS T1 from the ATLAS and break out the FXS lines.

[ben-matson]

Patrick,

Thank you for your support, unfortunately I have not been able to get this project working.  I was hoping to be able to contact support directly but the Atlas 550 is out of warranty and from what I've read support is only provided (even pay support) for this product if under warranty.  Can you please let me know if this is true or if there is some kind of paid support we can get because we are really needing to get this working?

Thank you,

Ben Kiser

[Anonymous]

Phone support for out of warranty products is available, but require the purchase of PSVs (professional service vouchers). The details for purchasing the PSVs can be found at https://www.adtran.com/psv. The charge is 2 PSVs per hour with a minimum charge of 2 PSVs. Configuration assistance has the same charge (during regular business hours) but must be scheduled.