Aastra Ascotel IntelliGate 2065 - Page 333

Ascotel IntelliGate 2025/2045/2065
Part 2 Call Routing 333
Fig. 2.92: Enquiry call and brokering, followed by three-party conference
Requirements
The following requirements have to be met for three-party connections in the
exchange to be activated:
• Basic accesses in point-to-multipoint operation (DSS1 only; QSIG and analogue
not supported).
• For Italy only: Basic accesses in point-to-point operation (DSS1 only; QSIG and
analogue not supported).
• The supplementary services required must be available at every basic access at
which the function is to be supported (subscription may be required).
• The enquiry call connection must be set up as an outgoing call by the internal
subscriber. It has to be routed via the same basic access as the first connection.
• Authorisations must be enabled (see "System Configuration", page 334).
PBX Response if the Procedure Fails in the Exchange:
Hold cannot be transferred to the exchange:
• The call is put on hold in the PBX.
• Any subsequently initiated three-party connections are carried out locally in the
PBX.
Three-party conference / call transfer in the exchange not carried out:
• The PBX cannot carry out the function locally as the call is on hold in the
exchange. The function cannot be carried out.
ISDNISDN
A
C
B
PBX
haz1221aaena0
ISDNISDN
A
C
B
PBX
haz1222aaena0