User`s guide

Troubleshooting
Common problems and their solutions
MultiVoice Gateway for the MAX— User’s Guide Preliminary November 23, 1998 A-15
If the line interface is not equipped with an internal CSU, the Length parameter is
displayed. It can specify a cable length, of 1-133, 134-266, 267-399, 400-533, or 534-655,
in feet, which should correspond to the distance between the MultiVoice Gateway and the
WAN interface equipment, typically a CSU or multiplexer.
Note: T1 PRI ports not equipped with internal CSUs require an external CSU or other
equipment approved for the metallic interface between the MultiVoice Gateway and the WAN
facility.
The Net/BRI lines do not dial or answer calls
Do not connect the MultiVoice Gateway unit’s Net/BRI ports directly to U-interface BRI lines.
The MultiVoice Gateway unit’s Net/BRI ports require carrier-approved Network Terminating-
type 1 (NT1) equipment between the MultiVoice Gateway and BRI lines. Note that Net/BRI
outbound calls require the use of trunk groups.
No Logical Link status
If you notice that the status of a Net/BRI line in the Line Status display is No Logical Link, you
might or might not have a problem.
In some countries outside the U.S., it is common for no logical link to exist before the
MultiVoice Gateway places a call. In the U.S., when you first plug a line into the MultiVoice
Gateway or switch power on, the central office switch can take as long as 15 minutes to
recognize that the line is now available. You might have to wait that long for the line state to
change to Active (A). The physical link can exist without a logical link up.
If you wait longer than 15 minutes and the line is still not available:
1 Determine whether all the ISDN telephone cables are wired straight through.
If you are running multipoint (passive bus) on your switch, all of the ISDN telephone
cables must be wired straight through. If any of the cables are wired to cross over, you will
not be able to place calls.
2 Verify that 100% termination is provided on each ISDN line.
3 Determine whether you have correctly specified the Service profile Identifiers (SPIDs) in
the Line profile for each line. If the SPIDs are not correctly specified, the line status might
indicate No Logical Link. Check with your system manager or carrier representative to
obtain the SPID or SPIDs for your line. To specify your SPIDs, use the Pri SPID and Sec
SPID parameters in the Line profile.
WAN calling errors occur in outbound Net/BRI calls
Should you encounter a problem in which the Call Status window immediately indicates a
WAN calling error when the MultiVoice Gateway places a call on a Net/BRI module, proceed
as follows to resolve the problem:
1 Check the value of the Data Svc parameter in the Call or Connection profile.
Try both the 64K and 56K options for Data Svc, to see whether using a different value
solves the problem.
2 Verify that you are using the correct dialing plan.
Depending on how the BRI lines are configured, you might need to type four, seven, or ten
digits to communicate with the remote end.