Aastra OpenCom 130 User Guide - Page 114

Call Set-up, 9.2.6 Useful Services, Telephony, Extended, profile, Data analogue

Page 114 highlights

Voice over IP (VoIP) Fundamentals 9.2.5 Call Set-up Various IP-based protocols are used for system telephony via the Internet protocol ("IP") (see also Start Procedure starting on page 129). Multiple TCP connections are made between an IP telephone and OpenCom 100 for the telephone's start procedure, registration and signalling. All voice data are directly exchanged between IP telephones using the RTP ("Realtime Transport Protocol") protocol. Channels on a Media Gateway (MGW) are allocated for making a telephone connection with an ordinary terminal or for dial tones. The MGW converts IP voice data into PCM data streams used with conventional telephony and vice versa. For this, IP voice data are exchanged between the IP telephone and the gateway. Tip: Switching between voice data channels may cause a slight delay in some circumstances. For example: when accepting a call on an IP telephone, headset users should wait about one second before answering. 9.2.6 Useful Services The type of data compression used for VoIP prevents these types of connections from using certain services. Take these notes into account especially if you want to use connections made via Q.SIG-IP or SIP: ■ ISDN data services can not be used ■ Faxes can only be sent using the uncompressed G.711 codec ■ DTMF dial tones are only received by the other party if the uncompressed G.711 codec is used. Alternatively, DTMF dial tones can be transferred using the Internet standard RFC 2833/4733. For this, the "DTMF (RFC4733)" codec needs to be activated for the codec configuration on the Telephony: Extended: VoIP profile page. ■ Analogue modems can not be used Tip: Configure the actual usage for the a/b ports, e.g. set them to Fax or Data (analogue). Connections from and to these a/b ports will then be made using uncompressed or ISDN connec- tions where possible. 112

  • 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

Voice over IP (VoIP)
Fundamentals
112
9.2.5
Call Set-up
Various IP-based protocols are used for system telephony via the Internet protocol
(“IP”) (see also
Start Procedure
starting on page 129). Multiple TCP connections are
made between an IP telephone and OpenCom 100 for the telephone’s start pro-
cedure, registration and signalling. All voice data are directly exchanged between
IP telephones using the RTP (“Realtime Transport Protocol”) protocol.
Channels on a
Media Gateway (MGW)
are allocated for making a telephone con-
nection with an ordinary terminal or for dial tones. The MGW converts IP voice
data into PCM data streams used with conventional telephony and vice versa. For
this, IP voice data are exchanged between the IP telephone and the gateway.
Tip:
Switching between voice data channels may cause a slight
delay in some circumstances. For example: when accepting a
call on an IP telephone, headset users should wait about one
second before answering.
9.2.6
Useful Services
The type of data compression used for VoIP prevents these types of connections
from using certain services. Take these notes into account especially if you want to
use connections made via Q.SIG-IP or SIP:
ISDN data services can not be used
Faxes can only be sent using the uncompressed G.711 codec
DTMF dial tones are only received by the other party if the uncompressed
G.711 codec is used. Alternatively, DTMF dial tones can be transferred using the
Internet standard RFC 2833/4733. For this, the “DTMF (RFC4733)” codec needs
to be activated for the codec configuration on the
Telephony
:
Extended
:
VoIP
profile
page.
Analogue modems can not be used
Tip:
Configure the actual usage for the a/b ports, e.g. set them to
Fax
or
Data (analogue)
. Connections from and to these a/b
ports will then be made using uncompressed or ISDN connec-
tions where possible.