ATLAS FAQs

Version 4

    Q: Are the ATLAS 550 modules and the ATLAS 800 modules interchangeable?

    A: No.

     

     

    Q: Are the option modules for the ATLAS hot-swappable.?

    A: Yes, This means that modifications can be made to the base unit without disturbing functioning modules already in place.

     

     

    Q: Can I have multiple Incoming # Accept List entries for one Dial Plan entry?

    A: Yes, you can have up to 99 entries in the Incoming # Accept List for one Dial Plan.

     

     

    Q: Can I use a single T1 interface to support both dedicated and switched bandwidth?

    A: Yes, a common application is to allocate several DSOs in the T1 for mapped data and the remainder of the DSOs for switched voice traffic.

     

     

    Q: Can I use a single T1 interface to support multiple dial plan entries?

    A: Yes, if you are using Robbed Bit Signaling (RBS) on that T1, you can actually have a Dial Plan entry for each DS0. If, however, the T1 is a PRI you can only have one Dial Plan entry since the 24th DS0 is always the D channel and there can be only one D channel per PRI.

     

     

    Q: Can you assign a priority to calls? For example, can you guarantee that the CEO never gets a busy signal?

    A:  No. ATLAS was designed to never interrupt a call in progress in order to service a higher priority client. If you require that the CEO always have network capacity available, you will need to configure the system to allocate bandwidth just for that particular client.

     

     

    Q:  What is the default timing source for the ATLAS?

    A:  The Atlas defaults to internal timing. If you have a circuit that provides timing, you should go to System Config and set the Primary Timing Source to that circuit.

     

     

    Q: Does ATLAS support the SPID-less 5ESS switch type?

    A:  No, all ATLAS BRI endpoints require at least one SPID.

     

     

    Q: Does installation of the back-up power supply interrupt operation of the ATLAS?

    A: No. The back-up power supply begins to provide immediate output when installed, balancing the power load with the primary supply without interruption to normal ATLAS operation.

     

     

    Q: Does mapping available DS0s on a T1 interrupt data flow on DS0s already in use on my ATLAS?

    A:  No, data on DS0s already in use are not affected by mapping available DS0s.

     

     

    Q: Does the ATLAS have alarm contacts?

    A:  All ATLAS units have alarm contacts except the ATLAS 800 and the ATLAS 800 Plus.

     

     

    Q: What is the MOS score for voice compression in the the ATLAS?

    A:  The Mean Opinion Score (MOS) is an opinion rating frequently employed to assess the speech quality of communication systems. Numerical values are calculated using the numbers 5 to 1, (5=excellent, 1=bad). The score, averaged over a number of words and listeners, is called the Mean Opinion Score (MOS).The MOS for voice compressed using the G.723.1 algorithm that the ATLAS 800 series and 550 VCOM module uses is 3.9. For reference, G.726 voice compression (32 kbps ADPCM) achieved an MOS rating of 4.2. Note: The ATLAS 800 base unit does not support voice compression

     

     

    Q:  What kind of cable should I use to connect my PBX to a T1/PRI port on the ATLAS?

    A:  You should use a T1 crossover cable. The ATLAS comes with a red crossover cable that can be used for this application. If this cable is not long enough, you can make a T1 crossover cable by crossing pins 1&4 and 2&5.

     

     

    Q:  What SPID format should I use when configuring User Termination BRIs on my ATLAS?

    A:   Bellcore ISDN specifications define, and the ATLAS will support, a SPID as 9 to 20 numeric characters. Most service providers have implemented a standard SPID" format of NXX-NXXXXXX0101 in a simplification effort. This format is ideal for most ATLAS applications.

     

     

    Q:  When do I need to turn on RBS in a Dedicated Map connection on my ATLAS?

    A:  Robbed Bit Signaling (RBS) "robs" the least significant, or eighth bit of each DS0 in the 6th and 12th frames of every superframe to provide inband, or channel associated signaling. This is a common form of voice signaling for T1 applications (vs. PRI). Set the signaling parameter to RBS for any ATLAS Dedicated Map entry involving voice circuits over T1 facilities.

     

     

    Q:  When will I need HDLC resources when using the Atlas series?

    A:  The Atlas series provides 35 HDLC resources for allocating to any application requiring an HDLC (Note: The Atlas 800 Base has no built-in HDLC resources and the 800+ has 4 built-in, 2 of which are reserved for the on-board T1 ports). There are 3 singular HDLC resources that can each support up to 2048kbps worth of bandwidth.  However, they must be allocated to a single T1 or E1.  The remaining 32 HDLC's (56/64k each) can each support a single DS0 worth of bandwidth, for a total of 2048kbps of resources.  HDLC resources are needed for any ISDN connection for the D-channel (PRI and BRI), any Frame Relay endpoint, and any PPP endpoint. All 550 and 800 series BRI U and S/T modules have built-in HDLC (64k) resources for the Dchannel and the 800 series T1/PRI modules have four built-in HDLC (64k) resources that would cover 4 D-channels. For example, if there are 2 T1's of Frame Relay data (i.e. 1536kpbs each) connected to an Atlas 550, two of the 3 singular HDLC's would be consumed. If you then had 10 PRIs connected to the same Atlas 550 in the Dial Plan, you would have 1 full (2048kbps) HDLC resource and 22 singular (56/64k) HDLC resources remaining.

     

     

    Q:  Why does the ATLAS ignore four-digit calls after I have added them to the Accept lists in the Dial Plan?

    A: Besides adding four-digit calls to the Accept lists of the Dial Plan, you must make an addition to the Global Parameters of the Dial Plan as well. Within the Global Parameters is the Number Complete Template. This template is used by the ATLAS as recognizable patterns for sending digits. In order to have the ability for the ATLAS to send four digit calls, there must be an entry in the Number Complete Templates to specify those four digit calls. You can use XXXX to accomplish this, but a more specific list of calls is advised.

     

     

    Q: With an ATLAS at the host and an IQ product at the remote site, can I manage the remote IQ unit via inband DLCI?

    A: No, the remote menu access via the inband DLCI is not supported. To get to the menus of the remote IQ unit, you would have to telnet to the IP address in the remote IQ unit.

     

     

    Q:  Which ISDN switches is the ATLAS compatible with?

    A:  For PRI, the Atlas is compatible with Lucent 4ESS Custom and 5ESS® Custom, Nortel DMS-100 Custom, and National ISDN-2. The Atlas can also emulate any of these switch/protocol types.

    For BRI, the Atlas is compatible with Lucent 5ESS Custom, Nortel DMS-100 Custom, and National ISDN-1. The Atlas can also emulate any of these switch/protocol types.

    The Atlas has been tested with and found to be compatible with the GTD-5 switch in PRI mode. The Atlas must be configured for National ISDN-2 when operating with the GTD-5.

     

     

    Q: How do I configure the Incoming # Accept List to only accept calls from a particular source?

    A:  The Source ID option can be used to provision switching based on the source (ATLAS end point). First, you must assign a Source ID to the call entrance port in the Interface Configuration. Then, simply assign a matching single-digit Source ID to the desired Incoming # Accept List.

     

     

    Q: How do I determine when I should use the Dedicated Maps versus using the Dial Plan when configuring my ATLAS?

    A:  The Dedicated Maps should be used for any DACS application in which the Atlas does not need to provide switching. The Dial Plan is used when you need the Atlas to route calls based on dialed numbers.

     

     

    Q: How do I determine which timing source the ATLAS is using?

    A: In the System Status menu, locate the System Timing Source. This will indicate the source to which the Atlas timing is locked.  The Primary/Backup corresponds to what is configured under the System Config Primary Timing Source and Backup Timing Source.

     

     

    Q: How do I factory default my Express 5000 Series Product?

    A:  To set an Express 5xxx unit to factory default settings, press the quick key (#) while powering the unit on. After the unit has completed its initialization, it will display an exclamation point next to the Express 5xxx listing on the LCD display as an indication of a successful factory default.

     

     

    Q: How do I view T1 performance data on my ATLAS?

    A: Under the Modules menu, press <Enter> on the appropriate [+] sign under the Menu column that corresponds to the T1/PRI module. Next, select Performance Current to view the results.  You can also view Performance 15 Minute and Performance 24 Hour.

     

     

    Q: How do you convert the U-Interface on an ATLAS BRI module to S/T-Interface?

    A: With a network termination device such as the ADTRAN NT1 ACE?

     

     

    Q: How many T3 modules can an ATLAS 800/800Plus/810Plus support?

    A: Two, although the total amount of bandwidth "mapped" through ATLAS cannot exceed 30 T1s.

     

     

    Q: Will the L1 "1st Generation" ATLAS 550 Base Unit support the new L2 "2nd Generation" T1/PRI Modules?

    A: Yes, they are fully supported if you have firmware C.09.02 loaded in your ATLAS 550 Base Unit.

     

     

    Q: How many VCOM (Voice Compression) Modules can I install in the ATLAS?

    A:  The ATLAS 800 (P/N 1200180L1) does not support voice compression. All other Atlas units will support no more than two VCOM Modules with a maximum of 64 ports per system, except for the Atlas 550 which has a maximum of 32 ports per system.

     

     

    Q:  How much Frame Relay Bandwidth does the ATLAS 550 support?

    A:  The ATLAS 550 supports two Full T1s or 3 Mbps of Frame Relay data.

     

     

    Q:  If my service provider sends seven digits over my T1/PRI and my internal numbering plan is four digits, how do I configure the Atlas?

    A:  There are two ways of implementing this application using either the User Term or the Network Term of the Dial Plan. Both methods require changing the Called Digits Transferred field which is located in the Interface Config menu for the interface that the call is going through.

     

     

    If the Called Digits Transferred of the Network Term is set to four, then the Atlas Dial Plan User Term In#Accept lists must be populated with the internal four digit numbering plan. This causes the PRI to only accept the last four digits of the Called Party Number in the ISDN Setup message and switch the call based on these four numbers. 

     

    If the Called Digits Transferred of the Network Term is set to 'All' or 'Seven' and the Called Digits Transferred of the User Term is set to four, then the Atlas Dial Plan User Term In#Accept must be populated with the seven digit number plan from the service provider. The difference between the two alternatives lies in the setup of the Dial Plan. The Dial Plan provides the Atlas with the numbering plan it uses to route calls across the switchboard.

     

     

    Q:  Is a backup power supply available for the ATLAS 800/800Plus/810Plus and, if so, where is it installed in the chassis?

    A: A backup power supply for the ATLAS 800/800Plus/810Plus is available separately from the base unit and must be installed in slots seven and eight of the chassis.

     

     

    Q:  Is it necessary to add an entry in the Out # Accept list in the Network Termination of a Dial Plan in order to place outgoing calls on my ATLAS?

    A:  Yes, in order to pass numbers to a network interface you must specify a specific type of numbering scheme or use a "$" to represent all numbers.

     

     

    Q: Does the Atlas FXS/FXO interface support message waiting indicator?

    A: No, please see the TSU 1XX, 600 product line for message waiting indicator support.

     

     

    Q: Does the Atlas dail plan in the 550, 830 or 890 support flash hook?

    A: The Atlas Dial plan does not support flash hook.  Flash hook will work in Dedicated Maps only (TDM).

     

     

    Q: Does the Atlas dialplan support stutter dial tone?

    A: The Atlas will not create or pass stutter dial tone via the dial plan.  Stutter dial tone will pass in dedicated maps only.

     

     

    Q: Does the Atlas family support Dual Tone Multi Frequency (DTMF)?

    A: Yes, DTMF is supported in the Atlas 550, 830, 890, 800/810 Plus, 800.

     

     

    Q: Does the Atlas family support multi frequency (MF)?

    A: Multi frequency (MF) is supported in the Atlas 830, 890, 800/810 Plus, and the 800 units but NOT in the Atlas 550.

     

     

    Q: Does the Atlas support call distribution through the dial plan?

    A: The Atlas 550 supports call distribution in a circular - round robin use of channels on the FXS, FXO, E&M, & PRI (b channels).  Atlas 550 firmware C.07.01 is required.

     

     

    Q: Does the Atlas dial plan support DS0 alignment on calls as they are processed?

    A: The Atlas 500, 830, & 890 does support  DS0 selection - aligned, giving you the ability to maintain DS0 alignment on T1 RBS interfaces in the dial plan. Atlas 550 requires firmware C.01  This is not supported in the 800/801 Plus.

     

     

    Q: Can the Atlas BRI S/T module be configured in the DIAL PLAN - USER TERM?

    A: Yes, the BRI S/T module was designed as a USER TERM only module and the cables are straight-through to the user equipment.

     

     

    Q: What types of E&M does the Atlas 550 E&M module support?

    A: The Atlas E&M module supports E&M types I-V.