Aastra OpenCom 130 User Guide - Page 152

Putting a Cascaded PBX into Operation, System: Data Backup, Telephony: Ports: Slots, Slave

Page 152 highlights

PBX Cascading Putting a Cascaded PBX into Operation 11.3 Putting a Cascaded PBX into Operation Proceed as follows to put a cascaded PBX system into operation: 1. Take the additional slave system out of its packaging and place it in immediate proximity to the master system. Connect a system telephone to the slave system for a later performance check. Use the Upn1 press-fit terminal of the basic module (only OpenCom 130) or one of the Upn ports of an interface card. 2. Back up the master system data. For further information, refer to the online help topic System: Data Backup. 3. Switch off the master system if it is operating. Disconnect the module from the power supply by pulling out the mains plug. 4. If necessary, install the add-on module for the master system. If you use an OpenCom 130 as the slave system, you also have to install an add-on module. 5. Connect the two modules by means of two suitable cables as described above. 6. Power on the two PBXs. The order in which you do this does not matter. 7. In the Telephony: Ports: Slots dialogue of the master system's Configurator, click on Slave. Select the slave Type in the Slave: Change dialogue. If a possible slave system was detected when the system was started, there is an additional entry in the Type field ("Online: PBX type"). If you select this entry, the settings for Type and MAC address are applied automatically. Please note: If you change the type of slave system later on, the port settings that have been made will be deleted. The master system then initialises the slave system. This may involve transfer of firmware (operating software) from the master system to the slave system. The transfer process is only executed for two OpenCom 130 / 150 PBXs. This can take a few minutes. 8. Configure the system telephone connected to the slave system for testing purposes in the Configurator. In the Telephony: Ports: Upn dialogue, click on one of the additionally displayed entries of the type Upn 1/0/n (1: slave system, n: Upn port number). 150

  • 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
150
11.3
Putting a Cascaded PBX into Operation
Proceed as follows to put a cascaded PBX system into operation:
1.
Take the additional slave system out of its packaging and place it in immediate
proximity to the master system. Connect a system telephone to the slave
system for a later performance check. Use the U
pn
1 press-fit terminal of the
basic module (only OpenCom 130) or one of the U
pn
ports of an interface card.
2.
Back up the master system data. For further information, refer to the online
help topic
System: Data Backup
.
3.
Switch off the master system if it is operating. Disconnect the module from the
power supply by pulling out the mains plug.
4.
If necessary, install the add-on module for the master system. If you use an
OpenCom 130 as the slave system, you also have to install an add-on module.
5.
Connect the two modules by means of two suitable cables as described above.
6.
Power on the two PBXs. The order in which you do this does not matter.
7.
In the
Telephony: Ports: Slots
dialogue of the master system’s Configurator,
click on
Slave
. Select the slave
Type
in the
Slave: Change
dialogue.
If a possible slave system was detected when the system was started, there is
an additional entry in the
Type
field (“Online: PBX type”). If you select this
entry, the settings for
Type
and
MAC address
are applied automatically.
Please note:
If you change the type of slave system later on, the port set-
tings that have been made will be deleted.
The master system then initialises the slave system. This may involve transfer of
firmware (operating software) from the master system to the slave system. The
transfer process is only executed for two OpenCom 130 / 150 PBXs. This can
take a few minutes.
8.
Configure the system telephone connected to the slave system for testing pur-
poses in the
Configurator
. In the
Telephony: Ports: Upn
dialogue, click on
one of the additionally displayed entries of the type
Upn 1/0/n
(1: slave
system, n: U
pn
port number).