We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF or read online on Scribd
You are on page 1/ 5
Chapter 2 General presentation
+ from the public network to users of PCXs C and D
These calls are established by:
+ public or private break-in -> private
+ private break-out -> private or public
The transmission acts as an access between the different protocols used; the level of service offered
depends on the protocols implied by the cal
+ QSIG <-> ISVPN: services offered by QSIG.
+ ISVPN on public line <> ISVPN on leased line: ISVPN services
+ ISDN <> ISVPN or QSIG: ISDN services
Centralized attendant service
An incoming call, in transit on a PCX or transferred whilst ringing (unsupervised transfer) on a leased
line, which is not answered after a certain amount of time, is automatically re-directed to the operator of
the system which received the call
The CENTRALIZED OPERATOR, the name given to this feature, is organized around the PCXs
connected to the network over leased lines. One of the PCXs, configured as the “Master”, will have the
CENTRALIZED OPERATOR STATION. The other "Satellite" PCXs may also have local operators.
DDI call TLD! (option)
(station B)
SSATELLITIBYSTEM
MASTER SYSTEM
1. Losed ne Ses ]
Cal fom 8
Local
OPERATOR,
Environment
When installing this feature on a PCX network, the following must be taken into account:
+ A specific programming procedure, performed for each PCX in the network, makes it possible to
configure a Master PCX and Satellite PCXs. The operator of the PCX configured as the Master
becomes the Centralized Operator.
+ Only incoming calls issued from the TO or T2 network interfaces of the Master PCX go through the
centralized operator mechanism. Nevertheless, Satellite PCXs can be equipped with network
junctors and a local operator thus enabling autonomous management of their traffic,
+ An incoming call routed to the centralized attendant benefits from the welcome message
mechanism, itis active
+ The display on the centralized attendant is usually provided for incoming calls which are routed to it
+ An incoming call which is considered as “non telephone" by the system, is not subject to the
centralized attendant service. For example, an incoming TO ISDN call a G4 Fax service
Configuring a network with external lines on only one PCX
BAL91206USAL -Ed. 1 - October 2022 - Expert Documentation: Private Networks 16/51Chapter 2 General presentation
DLTWDLT2
Cantratzed
Operator
To redirect the call to the centralized attendant, there are two possible solutions: the "ReroutOpe"
function of the transit system (PCX1), or dynamic routing/attendant forwarding of PCX2
Using ReroutOpe:
= Configure a time-out value before re-routing through PCX1:
‘System Miscellaneous -> Memory Read/Write -> Misc. Labels -> ReroutOpe.
Default value: 00 00: rerouting of in transit calls towards the centralized attendant is inactive.
Configuration example: ReroutOpe = C8 00 (200x100ms=20seconds).
Any call in transit towards the satelite, in the event of no reply, will be rerouted to the centralized
operator on PCX1 after 20 seconds (PCX1 releases the line to PCX2).
Note:
‘Only DDI calls routed directly to PCX2 (break-in) fall under ReroutOpe time-out (this mechanism does not apply to
a network line under call distribution).
If PCX2 users are using dynamic routing (for example towards the Voice Mail unil), the ReroutOpe time-out value
‘must be superior to the dynamic routings used by PCX2 users.
Dynamic routing/Attendant group routing:
Itis also possible to re-route calls from PCX1 to PCX1 using dynamic routing on PCX2 stations and the
‘Attendant group routing function within the time ranges of PCX2.
= Configuring a collective speed dial number in PCX2 (n° 8000 for example) with PCX1's operator as
destination.
The trunk group assigned to this number must be an homogenous logical direction for opti
be effective.
ization to
Time ranges -> Destination for time ranges = 8000; Attendant Diversion = Yes within forwarding
time ranges
- Configuring PCX2 stations supporting dynamic routing on attendant group:
BAL91206USAL -Ed. 1 - October 2022 - Expert Documentation: Private Networks 47151Chapter 2 General presentation
tails -> Dyn routing -> Timeout T2 = XX ;
‘orwarding to general level” and “Diversion
Users/Base stations List -> Station (choose station) ->!
External calls column - Level 2: check “Use Timer
apply”
This configuration offers the same operation as ReroutOpe time-out but is more flexible for choosing
which calls are rerouted or not to the centralized attendant:
by choosing dynamic routing of PCX2 users, itis possible to choose which calls, internal or external,
are rerouted to the centralized operator.
this configuration can be customized for each station (for example by suppressing dynamic routing
at general level for an analog device equipped with a fax)
Itis possible to choose different re-routing time-outs (T1, T2) for each user.
Configuring a network with external lines on each PCX
DLTODLT2
centraiized|
Operator
If there is no local operator in PCX 2, use the programming shown in the previous example (dynamic
routing/attendant group routing).
When there is a local operator in PCX 2, in addition to the attendant diversion to PCX1 using the
attendant group diversion by time range function described earlier, it is possible to perform a forced
diversion using the "Attendant Diversion” function.
+ to program an “Attendant Forwarding" key.
Users/Base stations List -> user (select Attendant) -> Details -> Keys -> Type = Function Key ->
Function = Attendant Forwarding, Number = 8000 (speed dial n° corresponding to a call to the cen-
tralized attendant),
Set up from the Attendant:
+ press the "Attendant Forwarding” key
+ attendant code (help1954 by default); the LED associated with the key flashes.
+ to cancel: same operation
Call handling
The table below describes the reactions of a Centralized Attendant network with or without a satellite
internal attendant.
BAL91206USAL - Ed. 1 - October 2022 - Expert Documentation: Private Networks 18/51Chapter 2
General presentation
SITUATION
SAT, WITHOUT INTERNAL AT-
TENDANT
SAT, WITH INTERNAL ATTEND-
ANT
The call No. in the satellite does not,
exist or is incomplete
The centralized attendant is rung
The time-out (ReroutOpe) starts
up
The internal attendant is rung
No connection rights
The called party is released
The called party is released
The time-out (ReroutOpe) starts up
The set
is rung
The called party is grade 1 busy
The time-out (ReroutOpe) starts
up
Ifthe satellite has the right to
camp on, then the call is camped
on; if not, the centralized attend-
ants rung
The time-out (ReroutOpe) starts
up
Ifthe satellite has the right to
camp on, then the call is camped
On; if not, the internal attendant is
rung if the destination’s dynamic
routing is inferior to the
tOpe" time-out,
‘The called party is grade 2 busy
The call No. is out of service
The called party is in DND
The centralized attendant is rung
The time-out (ReroutOpe) starts
up
The internal attendant is rung
‘The time-out (ReroutOpe) expires
The call is directed to the centralized attendant
The incoming call is transferred to
the satellite
The time-out (Trar
insfeTim) starts up
The set is rung
The time-out (TransfeTim) expires
Depending on configuration of "Master recall” to the centralized at-
tendant ti
+ either routed to the centralized
+ of routed to the initiator of
the calli:
attendant
the transfer. When the time-out
(Duration of Hold Recall Ringing) has lapsed, the call is directed
to the centralized attendant
Noe:
BAL91206USAL - Ed. 1 - October 2022 - Expert Documentation: Private Networks
By default, the "ReroutOpe" time-out is equal to 00 00; fora re-routing to the central attendant after 20 seconds for
example, the configuration must be "ReroutOpe” = C8 00.
For normal operation, the "ReroutOpe" time-out must be inferior to the dynamic routing time-outs of the slave
system.
External forwarding of attendant calls
This service makes it possible to forward all attendant calls (internal calls, public and private incoming
calls, attendant recalls, dynamic forwardings) to a public or private external destination.
For a more detailed description, see the relevant section in "Telephone Features"
‘Automatic callback on busy trunk group
19/51Chapter 2 General presentation
Ifa call goes through ARS mechanisms and if all the configured trunk groups are busy, itis possible to
activate an automatic callback request on a busy trunk group. The user is called back as soon as a line
in the first trunk group (traffic sharing) proposed by the ARS operations is released.
Distribution in a private digital network
+ The handiing of external calls (on public lines) and internal calls (on leased lines) can be configured
differently,
+ by OMC (Expert View), select: External lines-> incoming Call Handling, For each type of line, you
can define the actions (call released or forwarded to the attendant) in the following situations:
+ depending on whether the caller is public or private
+ called party busy 2nd degree
+ other called party status (in Do Not Disturb forwarding, out-of-service, recall situation following a
transfer failure)
+ misdial
In the case of unanswered calls on leased lines, the dynamic forwarding operations of an intemal
(local) call relative to the called set are applied.
Presentation of calls
+ Presentation to the called party
You can select the presentation mode for private calls:
+ presentation as internal call:
+ internal ringer
+ number of the caller not stored in the directory of last callers (except if the call has a UUS)
+ no welcome message option
+ presentation as extemal call:
+ extemal ringer
+ number of the caller stored in the directory of last callers
+ welcome message option
n> Private Call
+ by OMC (Expert View), select: System Miscellaneous -> Feature De
Presentation
+ Presentation to the caller
On the caller's set, the display always shows the number dialed by the user (not the one after
modifications by the ARS),
The number can be replaced by the name (name received if ISVPN, or name in the personal or system
speed dial numbers).
+ Transfer
In case of a transfer within an ISVPN network, the ISVPN subscribers’ displays are handled as if they
were in the same system, Especially after a transfer of an incoming call from user A to user B in a
different node, the display of B indicates the external caller rather than the user A.
+ Forwarding/Dynamic routing
If an incoming call to user A is redirected to user B in a different node, the call is presented to B with
the name of A on the display (or, failing that, the number of A)
CALLED PARTY STATUS
BAL91206USAL -Ed. 1 - October 2022 - Expert Documentation: Private Networks 20/51