Aastra OpenCom 510 User Guide - Page 158

Connection via Q.SIG.IP, PBX Configuration, Trunks, Bundle, Configurator, Access type, Protocol

Page 158 highlights

PBX Networking Types of Point-to-Point Connections PBX 1 L1 slave L2 slave L3 master Public network L1 master L2 master PBX 2 L1 slave L2 slave L3 slave Point-to-point connection via a public network 14.2.4 Connection via Q.SIG.IP If you are operating a fast and continuous internet connection at two or more locations, you can establish the TK system networking via internet connection as well. The OpenCom 510 uses the Q.SIG protocol, for use with ISDN point-to-point connections and transports the protocol and voice data via IP connections. The number of simultaneous conversations possible will depend on the capacity of the internet connection and the compression method used. A multiple S2M point-to-point connection is simulated for each Q.SIG-IP bundle. This means that 5 virtual D channels and up to 120 voice channels are available. Both Media Gateway Card channels and the Media Gateway software function can be used for Q.SIG-IP. Q.SIG-IP connection data are subject to codec compression (please refer to Voice over IP (VoIP) chapter regarding Fundamentals starting on page 116). Q.SIG-IP also transfers the voice data directly from terminal to terminal via the RTP protocol. In certain cases, for example, when an incoming external call is placed via multiple TK systems, one or more RTP proxies may be used to forward the connection. Currently, there are no standards for the necessary extensions to the Q.SIG protocol. This means that you can only use Q.SIG-IP between OpenCom 510 systems (exception: OpenCom 1000). Networking two OpenCom 510 systems using Q.SIG-IP requires 2 licenses - one license per system. The number of possible voice connections is not restricted by the license. Go to the PBX Configuration: Trunks: Bundle page in the Configurator to set up a Q.SIG-IP connection. Create a new bundle and select the Access type "System Access". Select "Q.SIG-IP" under Protocol. Configure the IP address of the other system, the port numbers to be used, the number of possible voice connections and select a VoIP profile for the codec selection. Please refer to the relevant help topics in the Online Help for the OpenCom 510 as well. 156

  • 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

PBX Networking
Types of Point-to-Point Connections
156
Point-to-point connection via a public network
14.2.4
Connection via Q.SIG.IP
If you are operating a fast and continuous internet connection at two or more
locations, you can establish the TK system networking via internet connection as
well. The OpenCom 510 uses the Q.SIG protocol, for use with ISDN point-to-point
connections and transports the protocol and voice data via IP connections.
The number of simultaneous conversations possible will depend on the capacity
of the internet connection and the compression method used. A multiple S
2M
point-to-point connection is simulated for each Q.SIG-IP bundle. This means that 5
virtual D channels and up to 120 voice channels are available. Both Media Gateway
Card channels and the Media Gateway software function can be used for Q.SIG-IP.
Q.SIG-IP connection data are subject to codec compression (please refer to
Voice
over IP (VoIP)
chapter regarding
Fundamentals
starting on page 116). Q.SIG-IP also
transfers the voice data directly from terminal to terminal via the RTP protocol. In
certain cases, for example, when an incoming external call is placed via multiple TK
systems, one or more RTP proxies may be used to forward the connection.
Currently, there are no standards for the necessary extensions to the Q.SIG pro-
tocol. This means that you can only use Q.SIG-IP between OpenCom 510 systems
(exception: OpenCom 1000).
Networking two OpenCom 510 systems using Q.SIG-IP requires 2 licenses – one
license per system. The number of possible voice connections is not restricted by
the license.
Go to the
PBX Configuration
:
Trunks
:
Bundle
page in the
Configurator
to set up
a Q.SIG-IP connection. Create a new bundle and select the
Access type
“System
Access”. Select “Q.SIG-IP” under
Protocol
. Configure the IP address of the other
system, the port numbers to be used, the number of possible voice connections
and select a VoIP profile for the codec selection. Please refer to the relevant help
topics in the Online Help for the OpenCom 510 as well.
PBX 1
L1 slave
L2 slave
L3 master
PBX 2
L1 slave
L2 slave
L3 slave
Public
network
L1 master
L2 master