This functionality is useful for temporarily
suspending access to a feature. During the technology life cycle, a server will reach a period where it will
be retired and replaced with a newer model. During that transitional period, one of the systems may
need to be online but not necessarily taking production traffic. As the new UM server comes online, via
the Enable-UMServer cmdlet, the old server will be disabled via the Disable-UMServer cmdlet. The
Disable-UMServer only requires the name of the server to disable. Because the Identity parameter is
positional, the Identity itself is not required, just the value. If a confirmation before disable is required,
the Confirm parameter can be used. However, if an immediate termination of all calls is necessary,
using the Immediate parameter set to $true will drop all calls.
The first UM server contains a share that contains all of the custom WAV files that are created for
custom prompts. Before the first UM server in the organization is retired, the custom prompts will
need to be moved to a different UM server and then have their publishing point updated. Using
the Copy-UMCustomPrompt will copy the files to a new location and update the publishing point.
Copy-UMCustomPrompt requires either a source path location, specified by the Path parameter, or the
TargetPath designates which WAV file to copy from a publishing point and UMAutoAttendant ,
or the UMDialPlan .
Pages:
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424