![]() |
Сайт
PKU ![]() |
![]() |
![]() |
|
![]() |
![]() |
![]() |
![]() |
![]() |
Introduction
You can connect the Hicom 150 E Office Communications Server to other Siemens Hicom systems using T1 services. The system supports a six-digit, closed-numbering plan for unique dialing schemes between systems. An open-numbering plan is also supported for networks that use a leading digit and a common system dial plan for each location.
The table below lists the supported network options for the Hicom 150E systems
System |
System |
System |
System |
||||||||||||
Hicom 150 E |
To |
Hicom 150 E |
Point to Point |
||||||||||||
Hicom 150 E |
To |
Hicom 150 E |
To |
Hicom 150 E |
Star configuration |
||||||||||
Hicom 150 E |
To |
Hicom 150 E |
To |
Hicom 150 E |
To |
Hicom 150 E |
Mesh configuration |
||||||||
Hicom 150 E |
To |
Hicom 300 |
Point to Point |
||||||||||||
Hicom 150 E |
To |
Hicom 300 |
To |
Hicom 150 E |
Star configuration |
||||||||||
Hicom 150 E |
To |
Hicom 300 |
To |
Hicom 300 |
Star configuration |
||||||||||
Hicom 150 E |
To |
9006M |
To |
Hicom 150 E |
Star configuration |
||||||||||
Hicom 150 E |
To |
9006M |
To |
9006M |
Star configuration |
||||||||||
Hicom 150 E |
To |
9006M |
To |
Hicom 300 |
Mesh |
||||||||||
Hicom 150 E |
To |
Hicom 150 E |
To |
Hicom 300 |
Mesh |
||||||||||
Table notes:
|
The following is a list of equipment required for connecting a CorNet-N link to a Hicom 150 E system.
The OfficePro system supports a maximum of five T1 interfaces and may be used as a gateway, a tandem, or an end node. It is suggested that in a mixed installation of Hicom 300 systems and Hicom 150 systems, the Hicom 150 systems should be positioned as end node systems only.
The OfficeCom system supports one T1 interface and may be used as an end-node system only.
The following items should be considered when designing a CorNet-N network.
![]() |
Homogenous Hicom 150 E Office network or mixed system network |
![]() |
Network internal dialing plan The Hicom 150 E Office system uses a closed-numbering plan with a dial number from one to six digits in length. |
![]() |
Network direct inward dial plan When setting up the DID number plan, you should match the internal dialing plan as much as possible. DID numbers can be transmitted over the CorNet-N links or via a direct public network connection. |
![]() |
Answering positions locations |
![]() |
![]() |
Central answer position |
![]() |
![]() |
Call Center groups Calling Party information and DNIS information may have to be sent to the centralized group for CTI applications. |
![]() |
![]() |
Auto-attendant The connection to the AAX is analog ports. The ports may have to be configured as Phonemail ports to activate the in-band integration transmission. |
![]() |
![]() |
Central voice mail system The connection to the voice mail is analog ports. The ports may have to be configured as Phonemail ports to activate the in-band integration transmission. |
![]() |
![]() |
Interactive voice response (IVR) The connection to the IVR is analog ports. The ports may have to be configured as Phonemail ports to activate the in-band integration transmission. |
![]() |
![]() |
Distributed answer position |
![]() |
![]() |
Answer position at each location |
![]() |
![]() |
Distributed phonemail network |
![]() |
![]() |
Night answer positions |
![]() |
![]() |
Data applications |
![]() |
![]() |
ISDN networking over CorNet-N links ISDN Data applications are supported over CorNet-N links using the STLS4, STMD8, ILAN board. and S0 optiset adapter. |
![]() |
![]() |
Fractional T1 for external applications |
A Phonemail system will be shared by all sites and will be installed on the OfficePro system.
|
CorNet-N Example Configuration Data
![]() |
Customer has three locations in the network |
![]() |
Central location is a Hicom 150E OfficePro system |
![]() |
Two satellite systems are Hicom 150 E OfficeCom systems |
![]() |
One Digital T1 interface is connected from each of the OfficeCom systems to the central OfficePro system. |
![]() |
Pilot Number for the main system is 1-408-492-1000, which is a DID number |
![]() |
Extension numbers on the OfficePro system are in the 11XX series. |
![]() |
DID numbers for the OfficePro system are 408 492-11XX |
![]() |
Extension numbers at the OfficeCom system 1 are in the 12XX series |
![]() |
DID numbers for the OfficePro system are 408 492-12XX |
![]() |
Extension numbers at the OfficeCom system 2 are in the 16XX series |
![]() |
DID numbers for the OfficePro system are 408 492-16XX |
![]() |
Block of DID terminating in the Main system provide service for all locations |
Procedure Overview
The following sections describe the CorNet-N configuration sequence in detail.
Configuring CorNet-N |
|
---|---|
Step |
Task |
1. |
|
2. |
|
3. |
|
4. |
|
5. |
|
6. |
|
7. |
|
8. |
|
9. |
|
10. |
|
11. |
|
12. |
Use Hicom Assistant E to select and place the T1 boards in the desired card slot(s). For CorNet-N applications, you must select the TST1 Digital or TMST1 Digital card type.
The T1 board configuration should be set for TMST1 Digital
Operation Mode |
ESF |
B8ZS |
Assigning T1 interfaces in the OfficeCom system, follows the same procedure.
Configuring the Feature Using Hicom Assistant E
Step |
Action |
---|---|
1. |
System Status ->System Wide ->Switchover to ->Hardware expansion. |
To define the Route Group for the CorNet-N T1 spans you must do the following:
![]() |
Specify unique route groups for each T1 CorNet-N link |
![]() |
Set CorNet-N protocol type for T1 spans originating at the OfficePro system |
System |
Route Assignment |
Seizure Code |
Route Name |
Parameters > ISDN Flags |
---|---|---|---|---|
OfficePro TMST1 Board 1 123 |
Route 2 |
System 1 |
S2M CorNet-N Variant Master (H150.H118) |
|
OfficePro TMST1 Board 2 123 |
Route 3 |
System 2 |
S2M CorNet-N Variant Master (H150.H118) |
|
OfficeCom TMST1 Board 1 123 |
Route 2 |
CorNet |
S2M CorNet-N Variant Slave (H150.H118) |
|
OfficeCom TMST1 Board 1 123 |
Route 2 |
CorNet |
S2M CorNet-N Variant Slave (H150.H118) |
Configuring the Feature Using Hicom Assistant E
Step |
Action |
---|---|
1. |
Options ->Lines/networking ->Trunks |
2. |
Options ->Lines/networking ->Trunks ->Parameters ->ISDN Flags |
This option defines the number of B-channels that are used for the CorNet-N link. If you assign channels for external data applications then you should disable the incoming and external flags for the required channels.
System |
Channels |
Incoming |
Outgoing |
OfficePro TMST1 Board 1 |
123 |
All channels |
All channels |
OfficePro TMST1 Board 2 |
123 |
All channels |
All channels |
OfficeCom System 1 TST1 Board 1 |
123 |
All channels |
All channels |
OfficeCom System 2 TST1 Board 1 |
123 |
All channels |
All channels |
Configuring the Feature Using Hicom Assistant E
Step |
Action |
---|---|
1. |
Options ->Lines/networking ->Trunks ->Parameters ->ISDN flags -> B-channel mode |
This procedure assigns the following route characteristics:
![]() |
Display name to the CorNet-N route |
![]() |
Optional ISDN primary rate interface (PRI) number |
![]() |
Optional second CO access code |
Display Name
OfficePro |
OfficeCom 1 |
OfficeCom 2 |
|||||
Route |
Route Name |
Route |
Route Name |
Route |
Route Name |
||
2 |
CorNet-N One |
2 |
Main |
2 |
Main |
||
3 |
CorNet-N Two |
Optional PRI Number
If the system is configured with a primary rate interface, the primary call number for each of the sites should be entered. This field identifies and filters specific digit patterns for DID and display purposes.
In the example below, the primary number for the main location is 1-408-492-1000. The DID numbers are based on the last four digits sent from the telephone company, (1XXX).
PABX Number Main Site |
|
Country Code |
1 |
Local Area Code |
408 |
PABX Local Number (Prefix) |
492 |
This should be repeated at each of the satellite locations if a different number must be sent to the public network over ISDN services.
Optional Second CO Code
You should configure a second trunk access code if the trunk access code in the main switch is used. Each route can be assigned a second trunk access code to ensure the proper display and callback information is sent back to the main system.
If no second code is enter and RTE type is CO |
All digits dialed are subject to toll restriction |
If no second code is enter and RTE type is PBX |
No toll restriction is applied by originating PBX |
If no second code is enter and RTE type is CO |
All digits dialed are subject to toll restriction |
If no second code is enter and RTE type is PBX |
All digits dialed are subject to toll restriction after second trunk code |
Note: The above information is for reference only and is only for analog trunk environments |
Second CO Code |
9 |
Configuring the Feature Using Hicom Assistant E
Step |
Action |
---|---|
1. |
Options ->Lines/networking ->Routes ->Route name |
2. |
Options ->Lines/networking ->Routes ->PABX number (PRI interface only) |
3. |
Options ->Lines/networking ->Routes ->CO code |
Path replacement for transferred calls is only supported between Hicom 150 E Office systems. Path replacement for incoming calls that are forwarded from a satellite Hicom 150 E Office system to a Hicom 150 E, Hicom 300, or Siemens 9006M system is also supported.
The following table explains some of the options available through the Hicom Assistant E Routing Parameters dialog box.
Choose the options that apply.
Option |
Action |
Result |
Rerouting Change Route |
If yes |
Use of Alternate D channel for call setup to final destination is possible |
Route optimize active No If route is known Always |
Only one can be selected If yes If yes If yes |
On call forward from satellite to main two links are used On Call forward from satellite to main, if handshake procedure is successful and route in known in receiving system no B-channel is seized. On Call forward from satellite to main, if handshake procedure is successful and route in known in receiving system no B channel is seized. If no route is known the call is intercepted or the call is disconnected. |
No and type outgoing PABX |
Select this choice and enter access code in second trunk code box |
Used to determine the route access code for callback and informs the system to send the extension number back to the callback location. |
Route type CO PABX |
Select PABX in CorNet-N environment |
Determine the portion of the number that should be sent to the public network. For CorNet-N applications PABX number should be set for the CorNet-N trunk group(s)
No. And Type Outgoing |
|
Country Code |
|
Local Area Code |
|
PABX number |
|
Unknown |
Example: The extension originating the external call is 1520.
If Country Code is selected, then |
14084921520 is sent |
If Local Area Code is selected, then |
4084921520 is sent |
If PABX number is selected, then |
4921520 is sent |
If Unknown is selected, then |
1520 is sent |
Routing Flags
Define the routing flags required for the CorNet-N network installation
![]() |
Digit repeat on |
![]() |
Evaluation of 2nd audible signal |
![]() |
Intercept per route |
![]() |
Over. service 3.1 khz. audio |
![]() |
Add direction prefix |
Configuring the Feature Using Hicom Assistant E
Step |
Action |
---|---|
1. |
Options ->Lines/networking ->Routing parameters |
2. |
Options ->Lines/networking ->Routes ->Routing parameters ->No. and type outgoing |
3. |
Options ->Lines/networking ->Routes ->Routing parameters ->Routing flags |
You must set the Master Clock reference for each of the satellite systems.
The table is divided into an allowed numbers list and a denied numbers list. The allowed numbers list defines the clock-sources sequence as referenced by the slave systems. You can define four clock sources.
The Denied Numbers list defines the spans that should not be used as reference sources. If a primary (position 1) clock source fails, the system will immediately switch to the next highest clock source.
OfficePro System
Position |
Allowed Numbers List |
Position |
Denied Numbers List |
|
1 |
1 |
TMST1 6 (T1 to Com) |
||
2 |
2 |
TMST1 7 (T1 to Com) |
OfficeCom System
OfficeCom 1 |
OfficeCom 2 |
|||
Position |
Allowed Numbers List |
Position |
Allowed Numbers List |
|
1 |
TST1 6 |
1 |
TST1 6 |
|
2 |
2 |
Configuring the Feature Using Hicom Assistant E
Step |
Action |
---|---|
1. |
Options ->Lines/networking ->Clock parameters ->Clock ->Allowed list |
This section is required to map a class of service flag associated with a specific call type in theHicom 150 E system to a Hicom 300 or Siemens 9005 system. Refer to the Hicom 300 or 9006M configuration information for additional details. In a connection with another Hicom 150 E system, the dialed digits of the local public network access are evaluated in the denial list 1 of the target system. For connection to a Hicom 300, access is controlled via mapped network access lists.
Hicom 150 E Privileges |
Hicom 300 LCOS Indexes |
Internal |
1 to 64 |
External Incoming |
1 to 64 |
Allowed/Forbidden Lists |
1 to 64 |
Unrestricted Trunk |
1 to 64 |
Configuring the Feature Using Hicom Assistant E
Step |
Action |
---|---|
1. |
Options ->Lines/networking ->LCOSS |
This section defines the call routing procedure for setting up the CorNet-N dialing plan.
![]() |
CorNet-N uses the DID column in each system for digit translation. The Call number column is used for Intercom calling in the local switch only. |
CorNet-N Least Cost routing Example Configuration Data
![]() |
Customer has three locations in their network |
![]() |
Central location is a Hicom 150 E OfficePro system |
![]() |
Two satellite systems are Hicom 150 E OfficeCom systems |
![]() |
One Digital T1interface is connected from each of the OfficeCom systems to the central OfficePro system |
![]() |
Pilot Number for the main system is 1-408-492-1100, which is a DID number. |
![]() |
Extension numbers on the OfficePro system are in the 11XX series. |
![]() |
DID numbers for the OfficePro system are 408 492-11XX |
![]() |
Extension numbers at the OfficeCom system 1 are in the 12XX series |
![]() |
DID numbers for the OfficePro system are 408 492-12XX |
![]() |
Extension numbers at the OfficeCom system 2 will be in the 16XX series |
![]() |
DID numbers for the OfficePro system will be 408 492-16XX |
![]() |
Block of DID terminating in the Main system provides service for all locations |
![]() |
Phonemail system is shared by all sites and is installed on the OfficePro system. |
Set the Station Dial Plan for Each System
Main |
System 1 |
System 2 |
|||||
Call No. |
DID |
Call No. |
DID |
Call No. |
DID |
||
1100 |
1100 |
1200 |
1200 |
1600 |
1600 |
||
1101 |
1101 |
1201 |
1201 |
1601 |
1601 |
||
1102 |
1102 |
1202 |
1202 |
1602 |
1602 |
||
1103 |
1103 |
1203 |
1203 |
1603 |
1603 |
||
1104 |
1104 |
1204 |
1204 |
1604 |
1604 |
||
.. |
.. |
.. |
.. |
||||
1150 |
1150 |
1250 |
1250 |
1650 |
1650 |
Enable Least Cost Routing
This procedure activates Least Cost Routing in the systems.
Release LCR |
Digit Transmission |
Step by Step |
En-Bloc |
Define the LCR Dial Plan for Each Location
This procedure configures the basic dialing patterns supported for CorNet-N closed dialing plan. A closed dial plan means that each station in the network is configured with a unique call number. An open dial plan can also be setup using a unique leading digit plus a common station number plan for each location. For example location one could be 1200, location two could be 2200 and location three could be 3200.
Main |
System 1 |
System 2 |
|||||
Dialed Digits LCR Dlpn |
Route Table |
Dialed Digits LCR Dlpn |
Route Table |
Dialed Digits LCR Dlpn |
Route Table |
||
12XX |
1 |
11XX |
1 |
11XX |
1 |
||
16XX |
2 |
16XX |
2 |
12XX |
2 |
||
0Z |
3 |
0Z |
3 |
Define the Out-Dialing Rules for Each Location
This procedure instructs the system to prefix, suffix, or dial a set of dialing sequences.
![]() |
D informs the system to dial a set of digits |
![]() |
A informs the system to dial all remaining digits after the LCR access code. |
Refer to Chapter 7, Least Cost Routing (for U.S. Only)" for additional out dial commands.
Main Location |
||
Rule Name |
Outdial Rule |
Procedure |
Dial All CorNet-N |
E1A or A1
|
Corporate Network2
|
System 1 Location |
||
Rule Name |
Outdial Rule |
Procedure |
Dial All CorNet-N |
E1A or A |
Corporate Network |
Dial ATC3
|
D1100 |
Corporate Network |
System 1 Location |
||
Rule Name |
Outdial Rule |
Procedure |
Dial All CorNet-N |
E1A or A |
Corporate Network |
Dial ATC4
|
D1100 |
Corporate Network |
1 The Out-dial rule "E1A" will echo the first field (12XX and or 16XX) followed by additional digits. The Out-dial rule "A" will echo all digits entered after a timeout. Both entries are acceptable. In a network scenario where the satellite systems share public network facilities, the Out-dial rule "E1A" can be used for routing external call information as well. 2 For applications requiring CorNet-N calls to be overflowed to a Public Network trunk, the Outdial procedure should be MCL single stage. This allows the CorNet-N call to progress to the next route step in the Route Table. 3 The final Out-dial rule is an option for setting up dial 0 access to the attendant at the main system. The Attendant Code 0 must be deleted or changed from the System Parameters > Intercept / Attendant screen 4 Refer to previous footnote. |
Define the LCR Class of Service for Each Station in the Network
This table is defines the authorization level required to access each route group element.
The default LCR COS of 15 is assigned to all stations in this example.
Main Call Number |
System 1 Call Number |
System 2 Call Number |
Class Of Service |
1100 |
1200 |
1600 |
15 |
1101 |
1201 |
1601 |
15 |
1102 |
1202 |
1602 |
15 |
. |
. |
. |
15 |
Define a Time of Day Schedule for the CorNet-N Route Availability
A time of day schedule must be defined for the CorNet-N routes.
This example uses time schedule A, which is configured to allow access to the CorNet-N links from 12:00 am to 23.59 pm, Monday through Friday.
Day |
End time |
Schedule1
|
Monday |
23:59 |
A |
Tuesday |
23:59 |
A |
Wednesday |
23:59 |
A |
Thursday |
23:59 |
A |
Friday |
23:59 |
A |
Saturday |
23:59 |
A |
Sunday |
23:59 |
A |
1 The default entry for the LCR schedule tables is A. If there are no time of day routing requirements, the step is optional |
Define Route Group Table Parameters
This table consolidates the LCR parameters into an association table for each route selected.
System |
Route Table |
Route |
Out Dial Rule |
Min COS |
Schedule |
Warning |
Main |
1 |
System 1 |
Dial All CorNet-N |
15 |
A |
None |
Main |
2 |
System 2 |
Dial All CorNet-N |
15 |
A |
None |
System 1 |
1 |
CorNet-N |
Dial All CorNet-N |
15 |
A |
None |
System 1 |
2 |
CorNet-N |
Dial All CorNet-N |
15 |
A |
|
System 1 |
3 |
Dial ATC |
15 |
A |
None |
Dial ATC |
System 2 |
1 |
CorNet-N |
Dial All CorNet-N |
15 |
A |
None |
System 2 |
2 |
CorNet-N |
Dial All CorNet-N |
15 |
A |
None |
System 2 |
3 |
CorNet-N |
Dial ATC |
15 |
A |
None |
An additional route consisting of local CO service can be configured as a secondary selection if the CorNet-N channels are busy.
In some cases, the customer may request that calls between locations use the Public Network facilities to route calls when the CorNet-N links are busy. In this case, the out-dial rule procedure for the rule associated with the CorNet-N dial plan should be MCL Single Stage. An additional route element can then be added to the route group table for selecting an alternate path to the destination.
Configuring the Feature Using Hicom Assistant E
Step |
Action |
---|---|
1. |
Options > Set up station > Station |
2. |
Options > Least Cost Routing > Codes and flags |
3. |
Options > Least Cost Routing > Dial Plan |
4. |
Options > Least Cost Routing > Dialing Rules Table |
5. |
Options > Least Cost Routing > Classes of Service |
6. |
Options > Least Cost Routing > LCR-schedule |
7. |
Options > Least Cost Routing > Route Table |
For path replacement CorNet-N supports the following:
![]() |
Path replacement for calls forwarded from a satellite Hicom 150 E system to a Phonemail system connected to a main Hicom 300 or 9006M system |
![]() |
Path replacement for calls transferred from a satellite Hicom 150 E system back to a station on another Hicom 150 E system. |
The display option allows the trunk information to be displayed at the receiving telephone on a transferred call.
Configuring the Feature Using Hicom Assistant E
Step |
Action |
---|---|
1. |
Options ->System parameters ->Flags CMI ->Other switches |
2. |
Options ->System parameters ->Flags CMI ->Transit permission |
3. |
Options ->System parameters ->Flags CMI ->Display |
Assigning multiple-station appearance (MUSAP) keys and general Call keys is optional; however, following this procedure provides a visual line appearance for calls received over the CorNet-N link from stations in satellite offices as well as DID calls. A second key is suggested for Rollover purposes.
General Call keys can be used for local intercom calls, CorNet-N calls, and DID calls and can be assigned to all stations. The General Call key for a specific station can not be assigned to multiple stations.
The MUSAP key can be used for DID calls and CorNet-N calls and can be assigned to all stations for this function. The MUSAP key for a station can be assigned to other stations for coverage applications. The coverage station must be programmed into the covered stations ring group for proper operation.
Configuring the Feature Using Hicom Assistant E
Step |
Action |
---|---|
1. |
Options ->Set up station ->Key programming ->Key programming ->Key Code ->General Call Key |
2. |
Options ->Set up station ->Key programming ->Key programming -> Key code ->Assign stn. no |
Pseudo numbers are used for identification and steering purposes. A pseudo number is a call number/ DID number that is assigned to a port not associated with a physical device.
![]() |
Pseudo numbers are assigned in the station setup screen and can be configured with a name and call management steering information. |
![]() |
Pseudo numbers may not be programmed as repertory keys on the optiset stations. |
![]() |
Pseudo numbers may be forwarded using the Associated Services feature code (*83) from a station with the Associated Services feature bit activated. |
Define pseudo numbers for the Phonemail pilot, Forward to pilot, Direct Access, Call back and Guest access for the satellite system.
![]() |
The "Forward to" pseudo number must be forwarded to the direct access number for Phonemail at the main location |
![]() |
The Phonemail, Direct, Callback and Guest access pseudo numbers must be forwarded to the respective target call numbers at the main location using the associate feature code: *83 + pseudo number + *11 + destination.
|
System 2 |
||||||
Call No |
DID |
Name |
Inactive |
Parameter |
Type |
Ext. Type |
1650 |
1650 |
Phonemail MW |
No Port |
Phonemail 5 D |
||
1651 |
1651 |
Forward to |
No Port |
Ans. Machine |
||
1652 |
1652 |
Direct Access |
No Port |
Ans. Machine |
||
1653 |
1653 |
Callback Optional Rep Key |
No Port |
Ans. Machine |
||
1654 |
1654 |
Guest Access |
No Port |
Ans. Machine |
A station at the satellite system can use the Call Forward access code *1 to forward their calls immediately to the Phonemail system.
For applications requiring the call to ring at the target station for a predetermined ring cycle, the call destination list table can be used. Target 1 would be "*" representing the originally dialed number. Target 2 would be the pseudo number representing the Forward to destination, 1251 or 1651. Associated services must be used to forward the configured pseudo ports to their respective pilot numbers in the main system.
Least Cost Routing may be used to route calls back to the main system pseudo numbers instead of assigning pseudo ports at the satellite location. A pseudo port for the PhoneMail IBMN port is still required at each of the satellite locations.
![]() |
The Phonemail entry in each of the remote systems is used as the pseudo port for lighting the Mailbox LED on the stations and as the call back target for message retrieval. The Phonemail pseudo port should be forwarded to the Call back pseudo port on the main system. |
![]() |
The Forward To entry should be forwarded to the Phonemail Hunt group pilot number on the main system. |
![]() |
The Direct Access entry should be forwarded to the Direct access pseudo number on the main system. |
![]() |
The Guest Access entry should be forwarded to the Guest access pseudo number on the main system. Typically a DID number would be assigned for Guest access at the main system and this entry would no be required. |
![]() |
The Callback function is an optional repertory key used to retrieve messages. The Call back Repertory key should be programmed to dial the Callback pseudo number on the main system. |
Configuring the Feature Using Hicom Assistant E
Step |
Action |
---|---|
1. |
Options ->Set up station ->station |
2. |
Options ->Set up station ->station ->Parameters ->Type ->Extension type |
This step is required to define an intercept network position for calls that are not answered by a station destination.
In the Intercept position boxes, the default is station 100 for day and night applications. The entry needs to be updated based on the closed-number plan selected for each system. 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 Attendant Number Call Number External field entry, default = 9 in the USA, should be deleted to eliminate conflicts with LCR dialing patterns for external and CorNet-N calls.
Configuring the Feature Using Hicom Assistant E
Step |
Action |
---|---|
1. |
Options ->System parameters ->Intercept/attendant |
Listed below are the pinouts for the T1 interface boards for the Hicom 150E systems
Hicom 150E OfficeCom System TST1 Board |
Pins |
Hicom 150E OfficePro System TMST1 Board |
Pins |
Transmit |
1 |
Transmit |
18 |
Transmit |
2 |
Transmit |
43 |
Receive |
4 |
Receive |
22 |
Receive |
5 |
Receive |
47 |
Listed below are the primary features supported between Siemens Hicom systems
The listed information is subject to change.
Feature |
Hicom 150 E to Hicom 150 E |
Hicom 150 E to Hicom 300 |
Hicom 150 E to 9751 |
Access to central PSTN trunks |
Yes |
Yes |
Yes |
Call Back Set on Busy |
Yes |
Yes |
No |
Call back Set on No Answer |
Yes |
Yes |
No |
Call Back to sender |
Yes |
Yes |
No |
Call Forward |
Yes |
Yes |
Yes |
Call Hold |
Yes |
Yes |
Yes |
Call Recall on transfer |
Yes |
Yes |
Yes |
Call Transfer Unscreened |
Yes |
Yes |
Yes |
Call Transfer Supervised |
Yes |
Yes |
Yes |
Calling Name and Number |
Yes |
Yes |
Yes |
Camp On |
Yes |
Yes |
TBD |
Centralized DID services |
Yes |
Yes |
Yes |
Conference Call |
Yes |
Yes |
Yes |
Conservation of B channels on Call forward to hub PBX |
Yes |
Yes |
Yes |
Conservation of B channels on call transfer |
Yes |
No |
No |
ISDN Data at 128Kbps |
Yes |
Yes |
No |
ISDN Data at 64Kbps |
Yes |
Yes |
No |
Message Waiting notification |
Yes |
Yes |
Yes |
Send Text Message |
Yes |
NA |
NA |
Uniform Dialing 2 to 6 digits |
Yes |
Yes |
Yes |
Send ANI on incoming call |
Yes |
Yes |
Yes |
Send DNIS on incoming call |
Yes |
Yes |
Yes |
![]() |
For Hicom 150 E to Hicom 300 or 9006M the Protocol to select is S2M: CorNet-N variant slave (H300). |
1. | In a network environment, a connection from a H300 to H150 to H300 fails to send DTMF tones from the optiset phone on the H300 through the H150 back to the H300 to Phonemail. A call from the H150 to the Phonemail system on the H300 works correctly. Analog stations in all scenarios work correctly. |
2. | The CorNet-N application has been tested with the Hicom 300 6.4, 6.5 only. Issues concerning Phonemail integration and display information will be apparent on the Hicom 300 6.1 and 6.2 versions. All 9006 system with revisions lower than 6.4 must be upgraded to most current version of the 9006 system software levels. |
3. | With systems configured with analog trunks, calls transferred to Phonemail via a DID, Attendant assist or DNIS cannot be transferred across the CorNet-N link from Phonemail using a blind transfer. The Call will ring back to the Phonemail system. The same thing will happen with blind transfers from a station. An explicit transfer must be set up using the transfer function from the Optiguide keys. |
4. | In a CorNet-N or networked environment, where Hicom 150 E OfficeCom systems are positioned as end nodes, if the OfficeCom systems are installed with basic rate trunks using CACH EKTS or DMS100 Key Short Hunting, networked systems will not have access to the BRI services for outbound calls. This is due to the fact that no CACH or PDID values are reserved for the CorNet-N call. The tandem call will be intercepted to the OfficeCom |
5. | The OfficeCom system must always be used as an end-node. Connecting an OfficeCom directly to another OfficeCom via a T1 link is not supported at this time. |
6. | Transit timer problem: (CorNet-N involved at this site) On T1, even with both parameters for the warning tone and release set out to max values (85 total minutes) and despite fact that T1 is a digital circuit, long distance calls over T1 are disconnected in 22 minutes. 22 minutes is maximum talk time duration on the T span. Additionally, the warning tone is not handled correctly (that is, the H150 users hears silence [absence of battery] and the external party you are speaking with receives the warning tone). |
7. | Hicom 150 E site is Cornet'ed to a 9006 with centralized Phonemail. Hicom 150 E site has operator-answered groundstart trunks. If a call on these trunks is extended to a Hicom 150 E user at this site, the call will not forward up the CorNet-N to the user's Phonemail box. |
8. | CorNet-N Issue: 9006 user station forwards a call to a Hicom 150 E extension at the Hicom 150 E remote satellite site over CorNet-N. Internal calls follow forwarding and return to Phonemail if the Hicom 150 E extension rings no answer. External caller just rings to answer and will not return to Phonemail. External call through 9006 to Hicom 150 E will stop at Hicom 150 E, and RNA will not be sent back up the CorNet-N to centralized Phonemail. |
9. | CorNet-N Issue: Digital optiset extension: A 9006 H300 calls extension B in Hicom 150 E which is Call Forwarded to C (Phonemail) at the 9006 H300. Extension A dials extension B; C (Phonemail) answers as expected. However, when extension A presses any digits, C (Phonemail) does not hear / acknowledge the DTMF tones. If the station A is analog, everything works fine and DTMF tones are recognized. |
Note that the following 9006 stand-alone patches should be installed in the 9006 system. Contact 9006 TAC for access to these patches. Only 9006 versions 6.4 and 6.5 are supported
1. | The patch versions shown below ensure that the display is correct on Hicom 150 E to Hicom 150 E tandem calls through a 9006 hub. |
![]() |
![]() |
PS10G09 for 9006.4 |
![]() |
![]() |
PS10G26 for 9006.4 |
![]() |
![]() |
PS10J22 for 9006.4 |
![]() |
![]() |
PS10808 for 9006.5 |
2. | The patch shown below is only available currently on the 9006.4 release. This patch corrects a problem that only occurs in the 9006 in a centralized PhoneMail application with the Hicom 150 E. It solves an intermittent problem where when you transferred out of PhoneMail to a Hicom 150 E user, occasionally you would experience dead air. |
![]() |
![]() |
PS10J22 for 9006.4 only |
3. | Unresolved CorNet-N Issue. |
![]() |
![]() |
Hicom 150 E site is connected to a 9006 with centralized Phonemail. Hicom 150 E site has operator-answered ground-start trunks. If a call on these trunks is extended to a 150 user at this site, the call will not forward up the CorNet-N to the user's Phonemail box. |
![]() |
![]() |
CorNet-N Issue: 9006 user station forwards a call to a Hicom 150 E extension at the Hicom 150 E remote satellite site over CorNet-N. Internal calls follow forwarding and return to Phonemail if the Hicom 150 E extension rings no answer. External caller just rings to answer and will not return to Phonemail. External call through 9006 to Hicom 150 E will stop at Hicom 150 E, and RNA will not be sent back up the CorNet-N to centralized Phonemail. |
![]() |
![]() |
CorNet-N Issue: Digital optiset extension A in a 9006 Hicom300 calls extension B in Hicom150 which is Call Forwarded to C (Phonemail) at the 9006 Hicom300. extension A dials extension B; C (Phonemail) answers as expected. However, when extension A presses any digits, C (Phonemail) does not hear / acknowledge the DTMF tones. If the station A is analog, everything works fine and DTMF tones are recognized. |
![]() |
![]() |
CorNet-N Issue: Two OfficeComs connected via CorNet-N. OfficeCom 1 has BRI lines in its network. If the BRI line gets removed and OfficeCom 1 is shut down, OfficeCom 1 will not work. |
The 9005 - 9751 systems must be equipped load 9005.6.84 for proper operation. Please consult the TAC support page for information concerning upgrades to existing systems at http://tac.fld.rolm.com/9751/index.html.
External Page Equipment
In cases where the customer requires access to external page systems located at remote Hicom 150 E sites the following Valcom equipment is required:
![]() |
V2001,V2003 or V2006 zone adapter. |
![]() |
V9970 Centrex page adapter |
![]() |
VPB-412A power supply |
![]() |
||||
![]() |
||||
![]() |
![]() |
![]() |
||
![]() |
![]() |
||
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 |