Aastra OpenCom 131 User Guide - Page 163

Technical Details, default, Telephony: Settings, QSIG linking, System Info: Telephony: Trunks

Page 163 highlights

PBX Networking Technical Details A default entry in the numbering table makes it possible to seize a "default route" for all remaining unassigned numbers. In particular, this simplifies configuration of the OpenCom 100 as a subsidiary system: the only entry you assign to the default entry is the route to the host system PBX c 100-199 d b 4: b a D: c PBX e 200-299 f 3: e h 5: h g D: d PBX 300-399 k 5: k D: f PBX 400-499 D: a PBX i 500-599 3: i D: g D:Default Route Example of closed numbering tables The automatic switching of call requests (i.e. routing) by means of bundle overflow or default numbering can lead to "circular switching". To avoid this, a "transit" counter is incremented whenever a connection is switched through on Q.SIG lines. When the configured maximum value is reached, further switching stops. 12.4 Technical Details A different PBX number must be set for each OpenCom 100 in a PBX network. This setting can be found in the Web console, in the menu Telephony: Settings under the heading QSIG linking. You can also set the maximum value for the transit counter there. This value depends on the topology of the PBX network and should allow the system to have the maximum number of further connections possible. You can display the connection status of the lines at any time in the Configurator menu System Info: Telephony: Trunks. You should check this in particular after making changes to a configuration to see whether all the lines used for system networking are operable. Some of the features possible in Q.SIG are not supported by OpenCom 100 with all their options, for example callback on busy within the Q.SIG network. The call categories defined in Q.SIG (e.g. Emergency Call, Operator, Normal) and the Q.SIG name transmission feature ("user names") are fully supported. The code digits to be used for seizing a route with open numbering are not transmitted to the destination PBX and thus cannot be evaluated by it. To reseize a 161

  • 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 Networking
Technical Details
161
A
default
entry in the numbering table makes it possible to seize a “default route”
for all remaining unassigned numbers. In particular, this simplifies configuration of
the OpenCom 100 as a subsidiary system: the only entry you assign to the
default
entry is the route to the host system
Example of closed numbering tables
The automatic switching of call requests (i.e. routing) by means of bundle overflow
or default numbering can lead to “circular switching”.
To avoid this, a “transit” counter is incremented whenever a connection is
switched through on Q.SIG lines. When the configured maximum value is reached,
further switching stops.
12.4
Technical Details
A different PBX number must be set for each OpenCom 100 in a PBX network. This
setting can be found in the Web console, in the menu
Telephony: Settings
under
the heading
QSIG linking
. You can also set the maximum value for the transit
counter there. This value depends on the topology of the PBX network and should
allow the system to have the maximum number of further connections possible.
You can display the connection status of the lines at any time in the Configurator
menu
System Info: Telephony: Trunks
. You should check this in particular after
making changes to a configuration to see whether all the lines used for system
networking are operable.
Some of the features possible in Q.SIG are not supported by OpenCom 100 with all
their options, for example callback on busy within the Q.SIG network. The call cate-
gories defined in Q.SIG (e.g. Emergency Call, Operator, Normal) and the Q.SIG
name transmission feature (“user names”) are fully supported.
The code digits to be used for seizing a route with open numbering are not trans-
mitted to the destination PBX and thus cannot be evaluated by it. To reseize a
PBX
200-299
PBX
500-599
PBX
300-399
PBX
100-199
PBX
400-499
D: a
4: b
D: c
3: e
5: h
D: d
3: i
D: g
5: k
D: f
a
b
c
d
e
f
g
h
i
k
D:Default
Route