- Basic call
- Direct calls from one shelf to another will be routed through central
office (e.g. calls from the host system to an access point will be automatically
routed via the CO).
- Name and number display: Incoming and outgoing calls - When the payload
survivability route is used:
- The calling party will see for basic call the called number and name
on the first line.
- The called party will see for basic call the calling number and name
on the first display line.
- When the payload survivability route is used, called party hears the "external
call ring" despite the fact that it is an internal call.
- If CO connection will breakdown during a call between different shelfs,
the call will have no payload and will be disconnected after 90s.
- The name is not shown on TIE calls.
IMPORTANT:
Signaling and Payload Separation (SPS) is released for
standalone systems only! In networked environment a project specific
release (PSR) is required and only basic call is possible!
- Hunt Group
- Parallel hunt group is not supported.
- Hunt group specific functionality is covered - linear/cyclic, master/pilot,
activate/deactivate hunt, overflow.
- Hunt group members must be located on the same branch.
- Hunting group stations are reached over LAN if calling party and
hunt group member are in the same shelf. In case that calling party and
hunt group member are in a different shelf hunting group station is reached
over Central Office.
- Charging:
The calling party will be charged if a hunting group station that is located
on a different shelf will answer. For external (CO) calls the paying
party is a default virtual route code destination and the destination
is the ALR number.
- Incoming calls to hunt group - When the payload survivability route
is used:
- The calling party will see the name and number of the hunting group
on the first line and the alerting hunt group member number and name
on second the line.
- The connected party will see the hunt group member number and name
on the first line.
- The alerting hunt group member will seethe calling number and name
on the first display line and the name and number of the hunting group
on the second line of the display.
- The connected hunt group member will see the connected number and
name on the first display line.
Overflow scenario:
- The calling party will see the name and number of the hunting group on
the first line and the last alerting hunt group member name and number
on the second line.
- The connected party will see the hunt group member number and name
on the first line.
- Forwarding for hunt group members is not supported (LVAFTEXT =N)*
- Announcement with hunting group call queue is not supported due CO
resource limitations.
- Execute call forwarding from hunt group parameter EXECCFW
will be ignored if the calling party and hunting group station with activated
call forward are located on different shelves.
- Call Pick Up
- Pick up specific functionality is covered (display of the calling user
(DISTNO), delayed notification ring (NOTRNG).
- Call pick up members must be located on the same branch.
- A station/user can pick up calls which belong to the pickup group.
For call scenarios where the calling party is located on a different shelf
than the called and picking party the CO route will be used. The calling
party will be charged.
For external (CO) calls the paying party is a default virtual route
code destination and the destination is the ALR number.
- Display The picking party will see on the display the name and number
of the calling partner.
- When the payload survivability route is used, the called party hears
the "external call ring" despite the fact that it is an internal call.
- Directed call pickup is not supported.
- Networkwide call pickup groups are not supported.
- Call Back
-
A station user can set a call back request to a party located on a different
shelf.
- Callback busy/no answer/free/mailbox is possible for calls between different
branches over CO.
- When callback is initiated (called party become free), calling party
hears the "internal call ring" despite the fact that it is an internal
call.
- When callback is executed, called party hears the "external call
ring" despite the fact that it is an internal call.
- Callback from/to network partner is not possible - "Callback" menu
will not be offered
- Call Forwarding
-
The user can forward calls to a party located on a different shelf.
- Call forwarding busy/no answer is possible in the same system. To stations
located on different branches the call will be routed over CO.
- Call forwarding to Xpressions is possible independent of shelf location
when a TIE trunk to Xpressions is configured.
- For Call forward scenarios no CO resources will be used if the calling
party and forward destination station are located on the same shelf.
- Charging
The calling party will be charged if the forward destination is located
on a different branch.
Forward Unconditional/Busy - The forward destination is located
on a different branch than the calling party
- The calling party will see the called name and number on the first line
display.
- Diverted-to party will see the calling party name and number on the
first line.
Forward no reply - If forward destination is located on a different
branch than the calling party:
- The calling party will see the called name and number on the first line
display and diverted-to party name and number on the second line display.
- Diverted-to party will see the calling party name and number on the
first line.
- Call forwarding indication at diverted-to party is not shown on the
display.
- Transfer and Toggle
- The user can transfer calls to a party located on a different shelf.
Transfer of incoming and outgoing external calls is possible to stations
located on a different shelf. In this case the call will be routed over
CO.
The calling party will see after transfer the called party name and number
and the transfered to party will see the calling party name and number
on the first line display.
If the calling party and transferring party are located on different shelves
the transferred party hears the "external call ring" independent of the
location of the transferred party (local, network).
- Conference
- The user can initiate a conference or be a conference member.
- Display
If all members of a conference are located on the same branch as the conference
master the display will show the correct information.
- The members of a conference which are located in another branch as the
conference master will see on the display only one connection to the
conference master.
- ALR route name will be shown instead of party name for members of
a conference which are located in another branch as the conference master.
- Keyset
- All Keysets can be reached via the main station number and can initiate
calls using primary line.
- Primary, Secondary and phantom line must be located in the same source
group.
- Name and number display
- One Number Service (ONS)
- An ONS member can pick up calls which belong to the ONS group.
- ONS group members must be located on the same branch.
- For call scenarios where the calling party, ONS master and picking
party are on the same shelf no CO route will be used.
- For call scenarios where the calling party is located on a different
shelf than the ONS master and ONS slave the CO route will be used. the
calling party will be charged.
- Tones
- The RING TYPE applied to ONS members is the same as the one of the ONS
master.
- When the payload survivability route is used, the called party hears
the "external call ring" despite the fact that it is an internal call.
- Fax-Modem
- Call Waiting
- Call Log
- OpenScape Xpressions basic scenarios
- ComAssistant basic scenarios
