INTERFACES AND REQUIREMENTS LBI-39039B
7
2. INTERFACES AND REQUIREMENTS
2.1. EDACS INTERFACE
An EDACS-originated call appears to the MD110 as an incoming DID call from an external T1/E1 ISDN trunk. One
external T1/E1 ISDN trunk is dedicated to EDACS; a TLU-77/1 (T1) or TLU-76/1 (E1) board in the MD110 provides the
trunk interface. This allows up to 23/30 simultaneous calls to be handled.
• For calls to another PBX or to the PSTN, the number may begin with an LCR code or an external destination code.
“9” is typically used to access an outside line.
• For calls to MD110 extensions, the number is the extension number.
2.2. PSTN/PBX INTERFACE
A PSTN-originated or PBX-originated call appears to the MD110 as an incoming trunk call. The PSTN interface can be
analog or digital, and it can be a CO or DID trunk. The PBX interface can be an analog or digital tie trunk.
Minimum Requirements for the PSTN/PBX Trunks
• The ability to perform end-to-end tone signaling while in the connected state.
• The ability to properly send and receive call clearing signals.
• Direct inward dialing to radios requires trunks capable of passing dialed digits to the MD110.
Trunks or lines with forward and backward line clearing, and B-answer supervision are highly recommended. See the
explanation below.
With Line Clearing Without Line Clearing
When the Network hangs up, the interconnect
call will clear and free interconnect and radio
resources.
When the Network hangs up, the radio must clear the
interconnect call or let it clear due to hang time
expiration or conversation limit expiration to free
interconnect and radio resources. This problem would
be very significant for full duplex calls, since the user
must clear the call or the call will clear only after the
conversation limit expiration.
With B-Answer Without B-Answer
• Radios will hear IMC-generated ringback for
outbound calls.
• Ringing duration on outbound calls will be
limited to the OUTBOUND_ALERTING
parameter limit in the CONFIG.DAT of the
PI.
• In applications where billing is performed,
the option to bill the customer only if the
called party answers exists.
• Radios will hear MD110 or Network ringback for
outbound calls.
• Ringing duration on outbound calls will not be
limited by the PI unless the phone-to-phone
CONV_LIMIT parameter is applicable as in call
forwarding scenarios.
• In applications where billing is performed, the
customer will be billed for calls even if the called
party does not answer.
T1 or E1 tie trunks are highly recommended for connecting the MD110 to another PBX.
Calls to EDACS require DISA access and the radio ID, and may require an LCR or EDACS trunk selector code. Calls to
MD110 extensions require an extension number.
To Next Page
Loading...
