![]() |
Сайт
PKU
![]() |
![]() |
![]() |
|
![]() |
![]() |
![]() |
![]() |
![]() |
In private and public networks, switching operations are performed by trunk interfaces, numbering plans, least cost routing functions, and station number translations.
Hicom 150 E Office provides networking on digital trunks using the CorNet-N (from Section 7.13.4) or QSig (Section 7.13.19) networking protocol.
CorNet-N is a data protocol from Siemens AG for digital communication between Hicom 150 E Office, Hicom 300 E and other private communications servers from Siemens AG.
QSig is a data protocol for digital communication between Hicom 150 E Office, Hicom 300 E and the communications servers of other manufacturers.
The Hicom 150 E Office system (OfficeCom and OfficePro) can be connected to other Communications Servers to form private networks. The system can use analog tie lines (TIEL board in OfficePro) or digital T1 services (TST1 in OfficeCom, TMST1 in OfficePro) to support network call traffic. Varying degrees of network functionality, from basic call routing to transparent user features, can be achieved, depending on the signaling format. Software features for basic connectivity through advanced CorNet-N ISDN networking come standard in the basic Hicom 150 E Office system.
![]() |
For examples of maximum possible distances from the CO for CorNet-N direct networking, refer to Table 2-7 on page 2-18. |
Satellite Tie Line
The Hicom 150 E Office can be configured for basic call handling between other communications systems supporting common E&M signalling protocol. The Hicom 150 E LCR features can be implemented to support a coordinated dialing plan in simple network designs. The Hicom 150 E supports off-premise call forwarding over these types of tie-trunk circuits and can be used to route inbound call traffic to remote answering destinations.
While this simple network design does not afford feature transparency, economical call routes using analog E&M tie lines or standard T1/D4 tie lines can be used. The OfficeCom does not support an analog tie-line interface card.
CorNet-N Network
The following sections only refer to the OfficeCom and OfficePro models. The OfficePoint system does not support private networking.
![]() |
CorNet-N call traffic and signalling (for U.S. Only) |
![]() |
CorNet-N and international links |
![]() |
CorNet-N on fractional T1 |
![]() |
CorNet-N and data applications |
![]() |
CorNet-N network topologies |
![]() |
CorNet-N network and Hicom 150 E system feature compatibility |
Definition
Users can connected the Hicom 150 E Office system to an existing communications server (CS) as a satellite CS and use the functions of the second CS.
Tie trunk traffic can be processed via direct connections between the CSs as well as via public trunks and dedicated lines. In addition, with Hicom 150 E OfficePro, users can process tie trunk traffic via E&M trunks.
Basic interconnection of two communication systems can be formed by connecting analog station interfaces from one system to loop start analog trunks of the other system. This type of connection provides only basic connectivity between systems. To support such connectivity, the Hicom 150 E provides a configurable trunk flash which changes the flash from a ground signal to an open loop to signal the other system.
The Hicom Assistant T parameter CO or PBX or the Hicom Assistant E Office Trunk Type parameter changes the flash from long to short.
Model-Specific Data
Requirements and Conditions
Configuration Options
This feature can be configured using Hicom Assistant T or Hicom Assistant E Office.
Configuring the Feature Using Hicom Assistant T
Configure the feature using Hicom Assistant T as follows:
Configuring the Feature Using Hicom Assistant E Office
Configure the feature using Hicom Assistant E Office as follows:
Step |
Action |
---|---|
1. |
Set trunk type Options |
2. |
Lines/networking |
3. |
Routing parameters |
4. |
Set ISDN parameters Options |
5. |
Lines/networking |
6. |
Trunks |
7. |
Parameters, Flags |
8. |
Routes |
Testing the Feature
Check the feature for error-free functioning as follows:
Step |
Action |
---|---|
1. |
Call a station in another networked system. |
Definition
The TIEL (Tie Line Ear & Mouth) board supports tie traffic with other private communication systems and contains four two-way analog tie trunks with E&M signaling for Hicom 150 E OfficePro. Each tie trunk has eight connections: two incoming speech paths, two outgoing speech paths, two incoming signaling paths, and two outgoing signaling paths.
The speech paths can switch between four-wire and two-wire modes. To ensure high-quality transmission, a four-wire connection should be used for analog networks. The advantage of providing separate speech paths for incoming and outgoing calls is that it helps maintain call stability (echo). Repeaters in the transmission equipment can also compensate for attenuation losses.
The E&M signaling paths exchange signals that control connection setup and cleardown. Depending on the requirements of the remote system or the transmission equipment, you can use different types of interfaces that have a different number of wires or different potentials.
Before placing a tie trunk in service, you must determine which interface type the two participating systems should share. Details can be found in Section 3.3.11.
Model-Specific Data
Subject |
Pro |
Com |
Point |
One (not for U.S.) |
Start (not for U.S.) |
---|---|---|---|---|---|
Feature available in |
x |
- |
- |
- |
- |
HW requirements |
TIEL board |
- |
- |
- |
- |
SW requirements |
Rel.1.0 or later |
- |
- |
- |
- |
Configuration Options
This feature can be configured using Hicom Assistant T or Hicom Assistant E Office.
Definition
In private networks, users can assign station numbers, trunk access codes, and feature codes according to a customer-defined numbering plan.
Hicom 150 E Office supports both closed and open numbering. If unique extension numbers are used within the network, any user in the network can call another extension by dialing its extension number.This is a closed numbering plan.
CorNet-N dial plans support extension numbering. In the CorNet-N network, users assign unique private extension numbers of up to six digits. This type of numbering is also called closed numbering.
An open numbering plan is also supported for networks that use a leading digit and a common system dial plan for each location.
Model-Specific Data
Subject |
Pro |
Com |
Point |
One (not for U.S.) |
Start (not for U.S.) |
---|---|---|---|---|---|
Feature available in |
x |
x |
x |
- |
- |
HW requirements |
- |
- |
- |
- |
- |
SW requirements |
Rel 1.0 or later |
- |
- |
Requirements and Conditions
Subject |
Requirement or Condition |
---|---|
Numbering |
Users can change internal numbering only using Hicom Assistant E. |
Configuration Options
This feature can be configured using Hicom Assistant E Office.
Configuring the Feature Using Hicom Assistant E Office
Configure the feature using Hicom Assistant E Office as follows:
Step |
Action |
---|---|
1. |
Options |
2. |
Set up station |
3. |
Station |
4. |
Automatic LCR |
Testing the Feature
Check the feature for error-free functioning as follows:
Step |
Action |
---|---|
1. |
Call the internal number of another networked station. |
Definition
Hicom 150 E Office supports satellite CS traffic via CorNet-N. The system can be operated as a node (CS without CO access, CorNet-N trunk group only), transit node (CS with at least two CorNet-N trunk groups, no central office), and gateway (CS with CO and CorNet-N trunk groups).
In addition to the basic call functions (outgoing and incoming calls), the CorNet-N system supports the toll restriction feature.
If users operate the Hicom 150 E Office in networked environments, the user's toll restriction is checked, transmitted, or received in the incoming direction (class-of-service transfer) when a CorNet-N trunk is seized. To a gateway system, the system performs standard class-of-service toll restrictions for outgoing calls and when an extension answers.
A station's toll restriction class of service (COS) is passed from communication server to communication server within a CorNet-N network. When a call originating in a remote system is destined for an external trunk route, the Hicom 150 E performs COS checking of the calling party before allowing the call to proceed.
Model-Specific Data
Requirements and Conditions
Configuration Options
This feature can be configured using Hicom Assistant T or Hicom Assistant E Office.
Configuring the Feature Using Hicom Assistant T
Configure the feature using Hicom Assistant T as follows:
Step |
Action |
---|---|
1. |
Configure toll restriction |
2. |
15-1 => Toll restriction - Restriction, day |
3. |
15-2 => Toll restriction - Restriction, night |
4. |
15-3 => Toll restriction - Allowed lists |
5. |
15-4 => Toll restriction - Denied lists |
6. |
17-14 => Networking - Trunk type CO/CS |
7. |
23-6 => Codes - Second trunk access code |
Configuring the Feature Using Hicom Assistant E Office
Configure the feature using Hicom Assistant E Office as follows:
Step |
Action |
---|---|
1. |
Configure toll restriction Options |
2. |
Classes of service |
3. |
Station |
4. |
Allowed/denied numbers |
5. |
Lines/networking, Routing parameters, Routes |
Testing the Feature
Check the feature for error-free functioning as follows:
Step |
Action |
---|---|
1. |
Dial an external, outgoing connection from the satellite CS via the main CS. |
2. |
Outgoing connections are possible if permitted by the subscriber class of service. |
Definition
In a networked environment, each system records call details locally. Networking does not affect call detail recording in Hicom 150 E Office. Call details continue to be recorded for outgoing calls provided they are transmitted by the main CS. In environments with satellite CSs without a separate central office, the main CS centrally records call details that originate within the main CS (call detail recording central [CDRC]).
In addition, CDRC logs call detail information received for incoming calls (for example, transfer of a toll call from a networked system).
In networked environments, a centralized call accounting device can be used to record all calls originated or in transit through the hub system.
Each system can only record calls that are routed through its own trunks or transit calls. A centralized CDR device can be used to collect CDR data from each individual systems' RS-232 interface.
CDR data that originates in one node is not transmitted to another network node. The secondary CDR collecting devices located at each node are typically polled by a main CDR device located at the main node to collect the stored data. Siemens' responsibility is limited to the data provided out of the RS-232 port. Integration of external devices must be confirmed with Siemens ICN prior to installation.
Model-Specific Data
Subject |
Pro |
Com |
Point |
One (not for U.S.) |
Start (not for U.S.) |
---|---|---|---|---|---|
Feature available in |
x |
x |
x |
- |
- |
HW requirements |
- |
- |
- |
- |
- |
SW requirements |
Rel 1.0 or later |
- |
- |
Requirements and Conditions
Subject |
Requirement or Condition |
---|---|
Buffer box |
If a system in a network has local trunk accesses, a local buffer box can be used for the call charges. |
Call via the trunk gateway of the remote CS |
If a station in a CS conducts an outgoing call via the CO access of the remote CS, the call details that apply to the CS in which the trunk is seized are output as call type 6 (direct outward dialing). |
Configuration Options
This feature can be configured using Hicom Assistant T or Hicom Assistant E Office.
Configuring the Feature Using Hicom Assistant T
Configure the feature using Hicom Assistant T as follows:
Step |
Action |
---|---|
1. |
Configure call charge factor |
2. |
11-4 => CDR - Call charge factor |
3. |
Configure ISDN call detail recording |
4. |
11-5 => CDR - Call charge factor ISDN |
5. |
Configure currency designation |
6. |
11-6 => CDR - Currency |
Configuring the Feature Using Hicom Assistant E Office
Configure the feature using Hicom Assistant E Office as follows:
Step |
Action |
---|---|
1. |
Configure call charges System status |
2. |
Call charges |
3. |
Output format |
Testing the Feature
Check the feature for error-free functioning as follows:
Step |
Action |
---|---|
1. |
Conduct a chargeable call. The call charges are displayed as configured. |
Definition
CorNet-N handles incoming calls the same way as any other internal calls. Users can configure digit analysis in the networked system so that they can reach all Hicom 150 E Office extensions by dialing the prefix.
The extension number corresponds to the external numbering plan and is analyzed accordingly. When the connection is made, the following information is passed to the remote CS placing the call:
![]() |
Toll restriction |
![]() |
Extension number |
![]() |
Station name |
Model-Specific Data
Subject |
Pro |
Com |
Point |
One (not for U.S.) |
Start (not for U.S.) |
---|---|---|---|---|---|
Feature available in |
x |
x |
x |
- |
- |
HW requirements |
- |
- |
- |
- |
- |
SW requirements |
Rel 1.0 or later |
- |
- |
Configuration Options
This feature does not have to be explicitly configured.
Testing the Feature
Check the feature for error-free functioning as follows:
Step |
Action |
---|---|
1. |
Call a networked station via CorNet-N. |
2. |
If the name of the station dialed is entered in the networked system, it appears on the display. |
Definition
When users activate consultation hold between a Hicom 150 E Office station and a station in a networked system, the consultation hold is initially set up via a second B channel. Whenever possible, the connection is set up by path replacement (path replacement activates after connection). If path replacement is not possible, the connection remains on the second B channel.
When an external call is transferred to a station connected via CorNet-N, the station number, name, and class of service for the A and C stations are transmitted.
Users can pick up from the networked system if the call is identified as a consultation call. If the consulted party picks up the call, the request from the main CS causes the call to be switched in transit, and the system disconnects the consulting party. If the consulted party disconnects the consultation call, the consultation is automatically reconnected to the last call on hold.
Unscreened transfer is possible to a busy or idle station in a remote node.
Model-Specific Data
Subject |
Pro |
Com |
Point |
One (not for U.S.) |
Start (not for U.S.) |
---|---|---|---|---|---|
Feature available in |
x |
x |
x |
- |
- |
HW requirements |
- |
- |
- |
- |
- |
SW requirements |
Rel 1.0 or later |
- |
- |
Requirements and Conditions
Subject |
Requirement or Condition |
---|---|
Unscreened transfer |
Unscreened transfer is possible on a free or busy station in a networked system. |
Call pickup groups with fractional T1s |
If you are using a portion of B channels on a T1 for data applications (for example, with a data server), you must bar the data B channels from being used for call pickup groups. Do this by deselecting the B channel modes incoming and outgoing in Assistant E. (Refer to the table on page 7-393 for information on how to configure this feature with Hicom Assistant E Office). |
Configuration Options
This feature does not have to be explicitly configured.
Configure the feature using Hicom Assistant E Office as follows:
Step |
Action |
---|---|
1. |
Configure Fractional T1 with call pickup groups Options |
2. |
Lines/networking |
3. |
Parameters |
4. |
B channel mode |
5. |
Incoming/outgoing (deselect B channels used for data) |
Definition
The system initiates a recall if the network cannot perform an unscreened transfer. The recall applies locally and not network-wide.
In homogeneous Hicom 150 E networks, an unanswered call from one node to another recalls the initiating station in the originating node.
In non-homogeneous networks, an unanswered call to a non-Hicom 150 E system recalls at the transferring system's intercept position or originator, depending on the system configuration.
Model-Specific Data
Subject |
Pro |
Com |
Point |
One (not for U.S.) |
Start (not for U.S.) |
---|---|---|---|---|---|
Feature available in |
x |
x |
x |
- |
- |
HW requirements |
- |
- |
- |
- |
- |
SW requirements |
Rel 1.0 or later |
- |
- |
Configuration Options
This feature does not have to be explicitly configured.
Definition
Networked systems handle call waiting the same way as internal call waiting.
Corresponding D channel messages are generated for waiting calls.
Model-Specific Data
Subject |
Pro |
Com |
Point |
One (not for U.S.) |
Start (not for U.S.) |
---|---|---|---|---|---|
Feature available in |
x |
x |
x |
- |
- |
HW requirements |
- |
- |
- |
- |
- |
SW requirements |
Rel 1.0 or later |
- |
- |
Configuration Options
This feature does not have to be explicitly configured.
Testing the Feature
Check the feature for error-free functioning as follows:
Step |
Action |
---|---|
1. |
Call a networked station that is busy. |
2. |
If internal call waiting is enabled for this station, the station is camped-on. |
Definition
The calls are evaluated in the network and signaled accordingly.
CorNet-N calls are handled and signaled the same as internal calls.
Distinctive internal and external ring types are provided over CorNet-N.
Network station-to-station calls provide internal ringing patterns, whereas external trunk calls routed over CorNet-N provide external ringing patterns.
Model-Specific Data
Subject |
Pro |
Com |
Point |
One (not for U.S.) |
Start (not for U.S.) |
---|---|---|---|---|---|
Feature available in |
x |
x |
x |
- |
- |
HW requirements |
- |
- |
- |
- |
- |
SW requirements |
Rel 1.0 or later |
- |
- |
Configuration Options
This feature does not have to be explicitly configured.
Testing the Feature
Check the feature for error-free functioning as follows:
Step |
Action |
---|---|
1. |
Call a networked station. |
2. |
This station receives the same call signaling as it would for an internal call. |
Definition
Users can activate the Hicom 150 E Office callback feature across systems. The user interface is the same as for internal callback. Instead of the internal extension number, the number of the networked station is stored and displayed.
If an open-numbering scheme is used, this feature only operates in a CorNet-N network of two Hicom 150 E systems, where at least one system is an OfficePro.
Model-Specific Data
Subject |
Pro |
Com |
Point |
One (not for U.S.) |
Start (not for U.S.) |
---|---|---|---|---|---|
Feature available in |
x |
x |
x |
- |
- |
HW requirements |
- |
- |
- |
- |
- |
SW requirements |
Rel 1.0 or later |
- |
- |
Configuration Options
This feature does not have to be explicitly configured
Testing the Feature
Check the feature for error-free functioning as follows:
Step |
Action |
---|---|
1. |
Call a busy or free user in the networked system. |
2. |
Initiate callback and hang up. |
3. |
When the user is free or lifts the handset, the system calls you back. |
Definition
In addition to the calling station's number, Hicom 150 E Office transmits the calling station's name via CorNet-N. When a name is available for incoming calls, the station displays the name instead of the station number.
This feature supports both uppercase and lowercase letters. In addition, users can configure whether the telephone display shows the caller's name or station number.
The Hicom 150 E sends both the calling station number and calling station name (if applicable) via the ISDN D channel.
If external and internal calls are routed via CorNet-N to another node, it is necessary to split the B channels of a T1 span for internal and external traffic. This can lead to the situation that for certain calls not all 23 B channels are available.
In an incoming call from another node's ISDN trunk, the calling party's Caller ID is received on the Hicom 150 E optiset E.
An ISDN trunk call transferred or redirected from the Hicom 150 E (either by a station or by a voice processing device) passes the calling party's Caller ID to the next node.
Model-Specific Data
Subject |
Pro |
Com |
Point |
One (not for U.S.) |
Start (not for U.S.) |
---|---|---|---|---|---|
Feature available in |
x |
x |
x |
- |
- |
HW requirements |
- |
- |
- |
- |
- |
SW requirements |
Rel 1.0 or later |
- |
- |
Requirements and Conditions
Subject |
Requirement or Condition |
---|---|
Station number suppression |
Each user can use the station number suppression function to activate or deactivate station number and name display. |
Configuration Options
This feature can be configured using Hicom Assistant T or Hicom Assistant E Office.
Configuring the Feature Using Hicom Assistant T
Configure the feature using Hicom Assistant T as follows:
Step |
Action |
---|---|
1. |
Configure name/station number |
2. |
19-16 => Displays - Names/stn. numbers |
Configuring the Feature Using Hicom Assistant E Office
Configure the feature using Hicom Assistant E Office as follows:
Step |
Action |
---|---|
1. |
Configure name/station number Options |
2. |
System parameters |
3. |
Display |
Testing the Feature
Check the feature for error-free functioning as follows:
Step |
Action |
---|---|
1. |
Call a networked station. |
2. |
You see either the station name or the station number. |
Definition
Calls can be rerouted for call forwarding via CorNet-N to optimize B channel utilization.
For example, station A in CS 1 calls station B in CS 2. Station B then forwards the call to station C in CS 1. The two B channels between CSs 1 and 2 are released. This means that the connection is set up directly within CS 1. For this to be possible, both CSs must activate rerouting.
Hicom 150 E users can forward their incoming internal and/or external calls to users within their own system, to a node within the private network, or off-site (if the feature is allowed in the system administration). Call forwarding-no answer is possible using Call Management pseudo ports in the Hicom 150 E system.
Pseudo numbers are used for identification and steering purposes. A pseudo number is a call number/DID number assigned to a port not associated to a physical device. The pseudo numbers are assigned in the Set up station screen (Hicom Assistant E Office) and can be configured with a name and Call Management steering information. Pseudo numbers cannot be programmed as Repertory Dial (Repdial) keys on the optiset E telephones. Pseudo numbers can be forwarded using the Associated Services feature code (*83) from a station with the Associated Services authorization flag activated.
Route optimization can be defined in the database as follows:
![]() |
Rerouting is deactivated |
![]() |
Reroute only if the route is known |
![]() |
Rerouting is always activated
|
Refer to the CorNet-N Configuration Notes for the proper setting.
Model-Specific Data
Configuration Options
This feature can be configured using Hicom Assistant T or Hicom Assistant E Office.
Configuring the Feature Using Hicom Assistant T
Configure the feature using Hicom Assistant T as follows:
Step |
Action |
---|---|
1. |
Configure CF with rerouting |
2. |
17-17-1 => Networking - Rerouting - Rerouting active |
Configuring the Feature Using Hicom Assistant E Office
Configure the feature using Hicom Assistant E Office as follows:
Step |
Action |
---|---|
1. |
Configure CF with rerouting Options |
2. |
Lines/networking |
3. |
Routing parameters |
Testing the Feature
Check the feature for error-free functioning as follows:
Step |
Action |
---|---|
1. |
Forward a call to station C in the main CS from station B in the satellite CS. |
2. |
Call station B in the satellite CS from station A in the main CS. |
3. |
If possible, the trunks to the satellite CS are released. |
Definition
The conditions described under Section 7.2.3, Toggle also apply to networked systems. That is, station users can use the Toggle feature to toggle between callers, including those originated or received on CorNet-N call routes.
Model-Specific Data
Subject |
Pro |
Com |
Point |
One (not for U.S.) |
Start (not for U.S.) |
---|---|---|---|---|---|
Feature available in |
x |
x |
x |
- |
- |
HW requirements |
- |
- |
- |
- |
- |
SW requirements |
Rel 1.0 or later |
- |
- |
Requirements and Conditions
Subject |
Requirement or Condition |
---|---|
Call hold |
A station on hold cannot toggle between calls. |
Configuration Options
This feature does not have to be explicitly configured.
Testing the Feature
Check the feature for error-free functioning as follows:
Step |
Action |
---|---|
1. |
Set up a call. |
2. |
Activate consultation hold. |
3. |
Set up a second call via CorNet-N. |
4. |
Switch between the two parties called using toggle. |
Definition
The conditions described in Section 7.2.6, Conference also apply to networked systems.
Voice station users on the Hicom 150 E can establish internal and external conference calls using local and CorNet-N call routes as needed. The system limits the number of conferees in a conference to five. A party in another node connected to the conference via CorNet-N is allowed to add additional parties within its own node using its own conference circuit. Members of a conference within another node will not be updated with the conference display information (number of conferees in the conference) of the Hicom 150 E system.
Model-Specific Data
Subject |
Pro |
Com |
Point |
One (not for U.S.) |
Start (not for U.S.) |
---|---|---|---|---|---|
Feature available in |
x |
x |
x |
- |
- |
HW requirements |
- |
- |
- |
- |
- |
SW requirements |
Rel 1.0 or later |
- |
- |
Requirements and Conditions
Subject |
Requirement or Condition |
---|---|
Conference |
A conference can be set up between voice stations only. |
Configuration Options
This feature does not have to be explicitly configured.
Testing the Feature
Check the feature for error-free functioning as follows:
Step |
Action |
---|---|
1. |
Set up a call. |
2. |
Activate consultation hold. |
3. |
Set up a second call via CorNet-N. |
4. |
Set up a conference using the input procedure. |
5. |
If you want to include additional stations in the conference, place the conference on hold, set up another call, and activate the conference. |
Definition
A central attendant console supports the switch and recall functions in the network. A local intercept position can redirect intercepted calls via a networked station (with call forwarding).
Pseudo numbers can also be entered that are forwarded to a remote system for centralized answering applications. The Associated Service feature must be used to call forward the pseudo number to the target location.
The console display shows the calling party number if available. There is no indication specific display for intercept-same display as for incoming external calls.
Model-Specific Data
Subject |
Pro |
Com |
Point |
One (not for U.S.) |
Start (not for U.S.) |
---|---|---|---|---|---|
Feature available in |
x |
x |
x |
- |
- |
HW requirements |
- |
- |
- |
- |
- |
SW requirements |
Rel 1.0 or later |
- |
- |
Configuration Options
This feature does not have to be explicitly configured.
Definition
Satellite CSs can share the system speed-dialing destinations in a gateway system. However, the local telephone directory cannot display the system speed-dialing numbers of the gateway system.
There are some restrictions, depending on the type of system in the network. Refer to the Configuration Notes prior to installation.
The satellite station user must dial the gateway system's speed-dialing number. Service code conflicts must not exist between the nodes. The service code is analyzed via LCR and sent to the destination node
Model-Specific Data
Subject |
Pro |
Com |
Point |
One (not for U.S.) |
Start (not for U.S.) |
---|---|---|---|---|---|
Feature available in |
x |
x |
x |
- |
- |
HW requirements |
- |
- |
- |
- |
- |
SW requirements |
Rel 1.0 or later |
- |
- |
Configuration Options
This feature does not have to be explicitly configured.
Testing the Feature
Check the feature for error-free functioning as follows:
Step |
Action |
---|---|
1. |
From the satellite CS, dial the system speed-dialing code for the main CS. |
Definition
Users in a networked system can program call forwarding to a central voice mail server. Hicom 150 E Office stations are informed of calls received by means of the message waiting indication (either the optiset E LED, the optiset E display, or the OfficePro analog telephone's broken dial tone or message).
The central voice mail server can be queried in DTMF mode.
In a homogeneous Hicom 150 E network, the centralized voice mail system must be located at the OfficePro system. Special attention should be taken during the presales investigation concerning the amount of traffic from all nodes to the voice mail server. The Hicom 150 E supports a maximum of 8 VMIe analog ports connected from the voice mail server to the OfficePro.
With the Siemens PhoneMail system, users can assign one mailbox to up to six independent telephones so that the Message Waiting indication is turned on at all telephones assigned to this mailbox. These telephones can be part of different systems that are served by the same PhoneMail system. The Plus Feature package is required for this function. The PhoneMail SW level must be 6.3 or above.
If external and internal calls are routed via CorNet-N, it is necessary to split the CorNet-N link B channels for internal and external traffic. This can lead to a situation where, for certain calls, not all B channels are available.
Model-Specific Data
Subject |
Pro |
Com |
Point |
One (not for U.S.) |
Start (not for U.S.) |
---|---|---|---|---|---|
Feature available in |
x |
x |
x |
- |
- |
HW requirements |
- |
- |
- |
- |
- |
SW requirements |
Rel 1.0 or later |
- |
- |
Requirements and Conditions
Subject |
Requirement or Condition |
---|---|
Follow the configuration guidelines. |
Configuration Options
This feature does not have to be explicitly configured.
Testing the Feature
Check the feature for error-free functioning as follows:
Step |
Action |
---|---|
1. |
Activate call forwarding from a networked station to the central voice mail server. |
2. |
Call the forwarded station. The call is forwarded to voice mail. |
Definition
CorNet-N is usually the protocol used for networking Hicom CS' with each other. QSIG, the cross-vendor signaling protocol available throughout Europe, is used for networking Hicom and non-Hicom CS'. In homogeneous networks, Hicom 150 E Office supports the following basic features.
In QSIG environments, you can operate Hicom 150 E Office as an end node, transit node, or gateway.
The QSIG protocol used is based on the following specifications:
![]() |
ECMA V1.0: Release 2.2 and earlier |
![]() |
ECMA V1.0 and ECMA V2.0 (for the MWI feature only): Release 3.0 or later. |
![]() |
Partial specifications - ETS 300172: Basic Call/ECMA 143 - ETS 300239: Generic Functions/ECMA 165 |
These networked systems collectively act like a single system, transmitting the following over the S0 trunk:
![]() |
Callback option |
![]() |
Station number |
![]() |
Name |
![]() |
Party category |
![]() |
Transit counter |
Called parties with toll restriction 0 (no direct trunk access) for a QSIG trunk, cannot answer an incoming QSIG call for another station (call pickup, trunk key). However, direct calls and forwarded calls to the B party are possible.
Interworking With Other Protocols
![]() |
CorNet-N All existing features implemented for both CorNet-N and QSIG support interworking in the QSIG direction and vice-versa. The only exception is the callback feature (CCBS/CCNR) because the message flows between the two protocols and the ones between two nodes are too different. |
![]() |
ETSI The requirements for interworking between CorNet-N and ETSI apply here as well. |
Numbering plan
![]() |
ISDN numbering plan |
![]() |
The system does not support a private numbering plan. |
Call detail recording
Direct inward dialing (external)
![]() |
In the local system: Same as before. |
![]() |
There is no transfer of call charges in transit traffic. |
Consultation hold
![]() |
In the local system: Same as before. |
![]() |
To remote system: Consultation calls over a second trunk are possible, that is the calls are switched from the local system over two B channels, and they can be transferred. When a user releases the call, the call last placed on hold becomes active. |
Callback
![]() |
Users can activate completion of calls - no reply (CCNR) or completion of calls to busy subscribers (CCBS) to the remote system. They can activate CCNR if the other party does not answer or if a call is waiting. They can activate CCBS in the following situations: The other party is busy with one or multiple calls, engaged in a consultation call or a conference, or has activated do not disturb. |
![]() |
Users cannot set a callback to a call forwarding destination, a member of a group call or hunt group, a room monitor, or an entrance telephone. |
![]() |
Callback calls are deleted manually, when the CS is reset, a trunk fails, a port is reprogrammed. The same applies to calls from A to B and from B to A. |
Call forwarding
![]() |
The system supports only the CFU (call forwarding unconditional) QSIG version. |
![]() |
To optimize B channel usage a forwarded call to a telephone of the main PBX is handled in accordance with the specifications for Call Forwarding/Partial Rerouting. If partial rerouting is rejected, forward switching is used. |
![]() |
If Hicom 150 E Office is a gateway, forward switching is implemented. |
Name display
![]() |
Only UPPERCASE letters are transferred. Users can specify whether a transferred name or the caller's station number is displayed. |
This function is available in transit only.
For operation in networked environments, users can configure an external station number as the attendant console or intercept position in Hicom 150 E Office. If an intercept occurs in a CS, based on the locally valid intercept criteria, the call is forwarded to the external station number programmed in the CS or discarded.
The central attendant console intercepts calls according to the CINT (call interception) QSIG specification. The cause of the intercept, which is transferred in encoded format, is an important item of data.
The attendant always intercepts calls via a second B channel, because problems could otherwise occur in a network with different CSs.
The dialed digits or the station number of the party originating the intercept can be sent to the intercept destination as the originator of the intercept.
In the Hicom 150 E Office system, users specify only the number of the station where the intercept originated. In the case of call forwarding and hunt groups, this is the original station dialed. No information is transferred if the caller dials an incorrect or incomplete number.
An authorized network station (such as the central attendant position or a Hicom 150 E Office Rel.2.0 station with override authorization) can override a call being conducted at a busy station in the network. Users cannot override conference calls in Hicom 150 E Office Rel.2.0. The feature is implemented according to QSIG specification CI (call intrusion).
The Hicom 150 E Office Rel.2.0 system handles a busy override according to QSIG in a network just like an internal busy override. This means that every user who is authorized to override busy calls is authorized to do so throughout the network. The override operation transforms a two-party call into a three-party call.
This feature activates a recall to the originating station in the network, for example if a transfer was unsuccessful. The feature is implemented according to QSIG specification RE (recall).
This feature allows you to activate and delete the Mailbox key (callback signaling).
It supports the sending of messages (using the service menu or a code) from the idle, ringing, busy and talk states, and message reception. You cannot select text messages. Because the protocol does not support the transmission of text information, the receiving end always receives and displays the "Please call back" message.
A central voice mail server in the QSig network can also initiate a message. In this case, the name administered for this voice mail server for callback access is displayed. It is not possible to send a message to voice mail.
In the case of Octopus E 300/800, message waiting indication is supported either for voice mail or for other stations. If the feature is activated for voice mail, it must be deactivated for other stations.
This feature is supported only in the direction of an Octopus E 300/800 system (A6, Release 6.3 or later) from Deutsche Telekom AG. The destination of cross-system busy signaling can only be the central Octopus E 300/800 attendant console (AC).
Systems in the QSig network can report the operating states of selected stations to the central attendant console of a CS (can be main CS or satellite CS). The following operating states can be signaled for the telephones:
![]() |
Free |
![]() |
Busy internally |
![]() |
Busy externally |
![]() |
Defective |
The numbering plan in this network must be closed and it must be possible to access the CS via the first administered QSig port on the remote system.
Operating states cannot be transmitted via CSs functioning as gateway or transit nodes.
Model-Specific Data
Subject |
Pro |
Com |
Point |
One (not for U.S.) |
Start (not for U.S.) |
---|---|---|---|---|---|
Feature available in |
x |
x |
x |
- |
- |
HW requirements |
- |
- |
- |
- |
- |
SW requirements |
Rel. 2.0 or later |
- |
- |
Configuration Options
This feature can be configured using Hicom Assistant T or Hicom Assistant E Office.
Configuring the Feature Using Hicom Assistant T
Configure the feature using Hicom Assistant T as follows:
Step |
Activity |
---|---|
1. |
Configure QSIG |
2. |
20-4-1 => S0 port configuration (QSIG=7) or 20-4-2 => S2m port configuration (QSIG=4) |
3. |
20-5-2-11 => protocol type (QSIG=22) |
Configuring the Feature Using Hicom Assistant E Office
Configure the feature using Hicom Assistant E Office as follows:
Step |
Activity |
---|---|
1. |
Configure QSIG |
2. |
Lines/Networking |
3. |
Double-click trunk parameters |
4. |
ISDN-flags => Protocol |
![]() |
||||
![]() |
||||
![]() |
![]() |
![]() |
||
![]() |
![]() |
||
Hicom 150 H V1.0 - Hicom 150 E Office Rel.2.0-3.0 Service Manual | Siemens Part No.: P31003-M1550-X403-3-7620 | Conversion Date: 2000-08-24 |
![]() |
![]() |
||
Contact: E-Doku-Team | © Siemens AG 2001 |