Aastra OpenCom 130 User Guide - Page 153

Notes, PBX Networking, Resetting the System Data

Page 153 highlights

PBX Cascading Putting a Cascaded PBX into Operation Note: Changes to the configuration while initialising the slave system may trigger error reports referring to the ongoing initialisation. You can see that the initialisation has been completed from the display on the system telephone connected to the slave system. 11.3.1 Notes Observe the following when operating a cascaded PBX system: ■ All Upn, S0 and a/b ports of the slave system can be used with appropriate telephones. All features of system telephones on Upn ports are available without restriction. ■ The S0 ports of the slave system can also be used for trunk lines or for PBX networking (see PBX Networking starting on page 153). ■ It is not possible to operate a DECT base station on one of the Upn ports of the slave system. ■ The COM, actor/sensor and LAN ports of the slave system cannot be used. The LAN ports on the add-on module of slave system can be used without restriction. ■ The two communications systems must have a direct Ethernet connection or be connected via a hub in order to exchange data. They cannot be connected through a router. ■ The OpenCom 150 is equipped with the PCM2 port in order to realize cascading of a third PBX with a future release. Use one of the two LAN0 ports, to connect the OpenCom 150 to the Local Area Network. ■ The slave system cannot be addressed directly through a LAN. For configuration, always use the Web console of the master system. ■ A memory card installed in the slave system (OpenVoice, OpenAttendant) cannot be used. ■ To operate the slave system again normally, you must reset it to its factory settings (refer to Resetting the System Data starting on page 87). 151

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244

PBX Cascading
Putting a Cascaded PBX into Operation
151
Note:
Changes to the configuration while initialising the
slave system may trigger error reports referring to the ongo-
ing initialisation.
You can see that the initialisation has been completed from the display on the
system telephone connected to the slave system.
11.3.1 Notes
Observe the following when operating a cascaded PBX system:
All U
pn
, S
0
and a/b ports of the slave system can be used with appropriate tele-
phones. All features of system telephones on U
pn
ports are available without
restriction.
The S
0
ports of the slave system can also be used for trunk lines or for PBX net-
working (see
PBX Networking
starting on page 153).
It is not possible to operate a DECT base station on one of the U
pn
ports of the
slave system.
The COM, actor/sensor and LAN ports of the slave system cannot be used. The
LAN ports on the add-on module of slave system can be used without
restriction.
The two communications systems must have a direct Ethernet connection or
be connected via a hub in order to exchange data. They cannot be connected
through a router.
The OpenCom 150 is equipped with the PCM2 port in order to realize cas-
cading of a third PBX with a future release. Use one of the two LAN0 ports, to
connect the OpenCom 150 to the Local Area Network.
The slave system cannot be addressed directly through a LAN. For configu-
ration, always use the Web console of the master system.
A memory card installed in the slave system (OpenVoice, OpenAttendant)
cannot be used.
To operate the slave system again normally, you must reset it to its factory set-
tings (refer to
Resetting the System Data
starting on page 87).