Nortel-networks NN43001-121 Bedienungsanleitung Seite 174
- Seite / 304
- Inhaltsverzeichnis
- FEHLERBEHEBUNG
- LESEZEICHEN
Bewertet. / 5. Basierend auf Kundenbewertungen
174 Configuration
LD 17: Configure AML Link
Prompt Response Description
REQ CHG Change existing data.
TYPE ADAN
ADAN <new ELAN #> A new AML link; the link is an ELAN type. The link number
can be from 32 to 47 on a small system and from 32 and
127 on a large system. An AML link number within the
above range implies that the transport is over a TCP link.
CTYP ELAN Card Type: ELAN
To verify that the AML link is up and running, use the STAT ELAN command
from LD 48:
LD 48
STAT ELAN
ELAN #: 032 DES: CDLCS
APPL_IP_ID: 47 .164 .116 .43 : 0000F600 LYR7: ACTIVE EMPTY
APPL ACTIVE
For more information on the STAT ELAN command, see Software Input
Output Reference — Maintenance (NN43001-711).
ATTENTION
For redundancy, one AML link is required for each Front End within the node,
regardless of whether the Front End is a leader or a follower.
LD 17: Configure VAS (Value Added Server)
Prompt Response Description
REQ CHG Change existing data
TYPE VAS Value Added Server
VAS NEW
VSID <VAS#> VAS ID, ranges from 32 to 47 on a small system and from
32 to 127 on a large system
ELAN <LINK #> AML ELAN link number provisioned when the AML link
was created
SECU YES Security For Meridian Link Applications. Enable this for the
TR/87 FE application on the Signaling Server to acquire
DNs
Nortel Communication Server 1000
Nortel Converged Office Fundamentals — Microsoft Office Communications Server 2007
NN43001-121 01.03 Standard
Release 5.0 30 April 2008
Copyright © 2005–2008, Nortel Networks
.
- Nortel Converged Office 1
- Fundamentals — Microsoft 1
- Office Communications Server 1
- Contents 3
- Installation 101 5
- Configuration 111 5
- Maintenance 209 6
- Troubleshooting 215 6
- Appendix C Abbreviations 297 7
- Procedures 7
- New in this release 9
- Revision History 10
- How to get help 11
- 12 How to get help 12
- Introduction 13
- 14 Introduction 14
- Component overview navigation 15
- Converged Office 15
- Enterprise Voice 17
- OCS 2007 Voice components 18
- Media Gateways 19
- Mediation Server 20
- Mediation Server 21 21
- Figure 4 21
- Figure 5 23
- Personal Call Assistant 25
- Access Edge Ser ver 27
- OCS 2007 snap-in 27
- CDR data collection 28
- SIP CTI (TR/87) Protocol 29
- Figure 8 30
- SIP diagram 30
- Hardware Load Balancer 31
- Office Communicator 2007 32
- Documentation References 32
- Planning and engineering 35
- Network configuration 36
- Small network 37
- Medium network 38
- Large network 39
- Multiple customer network 40
- Network configuration 41 41
- Figure 13 41
- Multiple location network 42
- Load Balancer planning 43
- Load Balancer requirements 44
- Load Balancer planning 45 45
- Capacity planning 46
- Capacity planning navigation 47
- OC 2007 client requirements 47
- 48 Planning and engineering 48
- Mediation server requirements 49
- Signaling Server requirements 49
- Call Server requirements 50
- General requirements 51
- Server topology 52
- Operating System Requirements 52
- Hardware Requirements 53
- Virtual Server 2005 54
- SIP access port 55
- Basic Client Configuration 58
- Port use 58
- Security 59
- OC client authentication 59
- 60 Planning and engineering 60
- Figure 17 60
- Signaling security 60
- Dial Plan considerations 61
- Computer (SIP) Calls 61
- Phone (RCC or TR/87) Calls 62
- Dialstrings 63
- 64 Planning and engineering 64
- Figure 20 64
- North American format 64
- Figure 21 64
- Outside North America format 64
- Within North America 65
- Outside North America 65
- Capacity 67
- Redundancy 67
- SIP routing 67
- Feature Interactions 68
- Figure 23 69
- Computer call 69
- 70 Planning and engineering 70
- 72 Planning and engineering 72
- Single node Redundancy 78
- Campus redundancy 78
- Geographic redundancy 78
- Client considerations 82
- Converged Office functionality 82
- MCM 2.0 to MCM 3.0 84
- Load balancer considerations 84
- Prerequisites 85
- Migration process 86
- Unified Messaging 90
- 98 Planning and engineering 98
- Figure 25 98
- Signaling integrated 98
- Unified Messaging 99 99
- Figure 26 99
- Signaling non-integrated 99
- 100 Planning and engineering 100
- Installation 101
- Installation navigation 102
- NN43001-121 01.03 Standard 103
- Release 5.0 30 April 2008 103
- 104 Installation 104
- Figure 28 104
- Installing the CS 1000 system 105
- ATTENTION 105
- Active Directory 106
- OCS Proxy server installation 107
- Load Balancer installation 108
- MCM installation 109
- 110 Installation 110
- Configuration 111
- Active Directory configuration 112
- Defining users 114
- Figure 32 115
- Figure 33 117
- Enable Remote call control 117
- 118 Configuration 118
- Figure 34 118
- Figure 35 119
- Load Balancer configuration 120
- Voice Properties configuration 120
- Enabling dual forking–by user 121
- Applying policy 122
- OCS configuration procedures 122
- Configuration of Static Routes 122
- Front End server 123
- 124 Configuration 124
- Figure 37 124
- Figure 38 125
- Routing tab 125
- 126 Configuration 126
- Figure 39 126
- Figure 40 127
- 128 Configuration 128
- Figure 41 128
- Mediation Server configuration 133
- Configuring a Mediation Server 133
- MCM 3.0 configuration 134
- MCM architecture 135
- 136 Configuration 136
- Figure 43 136
- MCM Direct configuration 137
- MCM management console 137
- 138 Configuration 138
- MCM menu options 139
- 140 Configuration 140
- Figure 45 140
- MCM configuration window 140
- MCM 3.0 configuration 145 145
- Figure 48 145
- Get SIP URI 145
- 146 Configuration 146
- Figure 49 146
- Get phone 146
- MCM 3.0 configuration 147 147
- Figure 50 147
- MCM 3.0 configuration 149 149
- 150 Configuration 150
- Figure 51 150
- Call Server configuration 151
- Configuring the Codec 151
- Loss Plan configuration 152
- Caller ID table configuration 157
- DNS Server configuration 159
- SIP Trunk configuration 160
- Domain naming 163
- 164 Configuration 164
- Figure 56 164
- SIP Trunk Domain name 164
- URI Mapping 165
- 166 Configuration 166
- Figure 58 166
- SIP URI Map 166
- Figure 59 167
- SIP GW CLID Parameters 167
- 168 Configuration 168
- NRS configuration 169
- CDR configuration 170
- Computer Calls (SIP Gateway) 170
- Example 2 (North America) 171
- Phone number normalization 171
- 172 Configuration 172
- CS 1000 configuration 173
- Configuring the AML 173
- Configuring a station 175
- Signaling Server configuration 177
- Node parameter configuration 178
- 180 Configuration 180
- Figure 65 180
- DNS configuration 180
- Parameter: Service Enabled 182
- Parameter: Customer Number 182
- SIP CTI Dial Plan prefixes 184
- Parameter: Dialing Plan 185
- 186 Configuration 186
- 188 Configuration 188
- Figure 67 188
- Configuring the SIP URI Map 189
- Configuring CDR 190
- Phone Calls (SIP CTI) 190
- Figure 70 191
- SIP INFO message 191
- Normalizing phone numbers 192
- Creating Normalization rules 193
- 194 Configuration 194
- Normalizing phone numbers 195 195
- Figure 71 195
- 196 Configuration 196
- Figure 72 196
- Normalizing phone numbers 197 197
- Figure 73 197
- Figure 74 197
- Redundancy configuration 198
- 200 Configuration 200
- Figure 75 200
- Figure 76 201
- UM Address 201
- 202 Configuration 202
- Figure 77 202
- Dial plan window 202
- Figure 78 203
- Adding Exchange UM 204
- Figure 80 205
- 206 Configuration 206
- Figure 81 206
- Dial Plan window 206
- Figure 82 207
- 208 Configuration 208
- Maintenance 209
- Remote Call Control 210
- Troubleshooting 215
- 216 Troubleshooting 216
- SIP Dialog not established 217
- SIP CTI service is down 218
- Reconfigure SIP CTI service 219
- 222 Troubleshooting 222
- OC client not registered 223
- Pop-up not displayed 223
- Two pop-ups are displayed 224
- Delay for a SIP Gateway call 224
- Capturing traces and logs 225
- MCM logs 228
- Activating MCM logging 229
- MCM log file output 230
- MCM Event log 230
- Resetting MCM debug trace 231
- OCS logs 231
- Activating OCS logs 232
- OC client start-up debugging 233
- Case checklists 234
- Appendix A 237
- Message sequence 238
- Call flow 239
- Figure 94 240
- Call Forward by OC client 244
- Remote Call Control Call Flow 245
- Supported features 246
- Appendix B 249
- Configuration Examples 249
- Setting up the lab 250
- Collecting required data 251
- Configuring the Call Server 252
- Screen output: 253
- Screen output 260
- Screen Output: 260
- Signaling Server checklist 262
- Standard Edition 263 263
- Figure 102 263
- Figure 103 263
- Figure 104 264
- SIP GW Settings 264
- Standard Edition 265 265
- Figure 105 265
- Figure 106 266
- SIP CTI Services 266
- Standard Edition 267 267
- Figure 107 267
- Standard Edition 269 269
- Figure 109 269
- Host Authorization 269
- Figure 110 270
- General user properties 270
- Standard Edition 271 271
- Figure 111 271
- Communications properties 271
- Figure 112 272
- User Options 272
- Standard Edition 273 273
- Figure 113 273
- MCM Application 273
- Figure 114 274
- Enterprise Edition 275
- OCS Management Console 278
- Figure 118 280
- General tab settings 281
- Security/Certificates 282
- Figure 122 284
- Enterprise Edition 285 285
- Figure 123 285
- Routing for Enterprise Pool 285
- Configuring DNS 286
- Enterprise Edition 287 287
- Figure 125 287
- Installing and configuring MCM 289
- Figure 128 290
- RTC Server Local Group 290
- Configuring NRS 293
- Figure 132 294
- MCM endpoints 294
- Normalizing Phone Numbers 295
- Book Service is available 296
- Appendix C 297
- Abbreviations 297
- 298 Appendix C Abbreviations 298
- Appendix C Abbreviations 299 299
- 300 Appendix C Abbreviations 300
- Appendix C Abbreviations 301 301
- 302 Appendix C Abbreviations 302
- Communications Server 2007 304
Verwandte Produkte und Handbücher für Computers Nortel-networks NN43001-121
(342 Seiten)© 2020, manymanuals.de. Alle Rechte vorbehalten. | 0.065 s |
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Kommentare zu diesen Handbüchern