The Adtran community holiday season is starting next week! The holiday period will span from December 21, 2024 to January 6, 2025. During this time, responses to feedback form submissions may be delayed. If you are encountering product issues, you can reach out to Adtran support at any time.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
cmw3670
New Contributor

Atlas 830 No Dial Tone, DSP Resources

Jump to solution

I understand that the Atlas 830 is limited when doing RBS links by its 27 DSPs. Specifically, we are encountering no dial tone events which we think are due to greater than 27 simultaneous calls that are either off-hook or doing progress (We have 5 PRIs on the network side and 5 RBS T1s connected to channel banks on the user side doing individual loop start DS0s in the user dialplan). We're wondering if there is any option that adds DSPs to the Atlas 830 or if there is another product that would be more scalable for our application. Thanks!

0 Kudos
1 Solution

Accepted Solutions
Anonymous
Not applicable

Re: Atlas 830 No Dial Tone, DSP Resources

Jump to solution

While we don't have an ATLAS with more than 27 DSP resources, that only prevents more than 27 SIMULTANEOUS calls.

I'm also afraid there is no way to add DSP resources to the ATLAS.

The DPS resources are used to "generate dial tone, generate Ring back, generate digits to be propagated out of the unit." So as long as the calls aren't initiated at the same time, you can have more than 27 calls active at the same time. The ATLAS 830 actually supports 10 PRI to RBS conversions (but the DSP resource limits it to providing dial tone to only 27 channels at a time).

The dial tone is independent of the PRIs. So the USER TERM RBS T1's should provide dial tone regardless of the state of the PRIs. (This is because calls can be routed to other USER TERM entries, or possibly out various NETWORK TERM entries - so the RBS T1 will stay "up" and provide dial tone no matter what the condition of the other interfaces.)

I suggest either monitoring to see if specific channels are failing to provide dial tone, or even going through each T1 channel to verify every channel receives dial tone. You can monitor the T1 in the ATLAS to verify it sees the channel go off hook as well.

Hope this helps a little,

Patrick

View solution in original post

0 Kudos
2 Replies
Anonymous
Not applicable

Re: Atlas 830 No Dial Tone, DSP Resources

Jump to solution

While we don't have an ATLAS with more than 27 DSP resources, that only prevents more than 27 SIMULTANEOUS calls.

I'm also afraid there is no way to add DSP resources to the ATLAS.

The DPS resources are used to "generate dial tone, generate Ring back, generate digits to be propagated out of the unit." So as long as the calls aren't initiated at the same time, you can have more than 27 calls active at the same time. The ATLAS 830 actually supports 10 PRI to RBS conversions (but the DSP resource limits it to providing dial tone to only 27 channels at a time).

The dial tone is independent of the PRIs. So the USER TERM RBS T1's should provide dial tone regardless of the state of the PRIs. (This is because calls can be routed to other USER TERM entries, or possibly out various NETWORK TERM entries - so the RBS T1 will stay "up" and provide dial tone no matter what the condition of the other interfaces.)

I suggest either monitoring to see if specific channels are failing to provide dial tone, or even going through each T1 channel to verify every channel receives dial tone. You can monitor the T1 in the ATLAS to verify it sees the channel go off hook as well.

Hope this helps a little,

Patrick

0 Kudos
cmw3670
New Contributor

Re: Atlas 830 No Dial Tone, DSP Resources

Jump to solution

Thanks for the information. Yes, we have validated that it isn't any particular channel(s). A channel will get no dialtone and then immediately work the next time it tries to dial (say, 30-60 seconds later). They also do come off hook and go back on hook consistently from the Atlas's perspective with no issues.

It's just a simultaneous call issue problem. Out of 144 channels (6 user RBS), we just experience conditions where more than 27 come off hook at the same time. Anyway, I do appreciate the information as that does close a loop as far as whether or not there's a different Atlas we should be using.

Thanks,

Christian