Changing an extension’s scope from local to global – AltiGen MAXCS 7.0 Update 1 ACM Administration User Manual
Page 350
Ext
System A
(Domain Master)
System B
System C
100
Global
Remote
Remote
200
Remote
Global
Remote
300
Remote
Remote
Global
Managing Domain Users
334
MaxCS 7.5 Administration Manual
In the event that multiple systems have a same extension or group number created, the following situations
may occur:
Ext
System A
System B
System C
Scope
Note
401
Local
Not Found
Not Found
Local
1
402
Local
Local
Not Found
Local
2
403
Global
Local
Local
Conflict
3
404
Global
Global
Local
Conflict
4
1.
Extension 401 is created in System A for local purposes. Users in Systems B and C cannot dial and ring
extension 401.
2.
Extension 402 is created in both Systems A and B. You may intentionally set it up this way so that System
A and B users can dial 402 for their local purposes. Ext. 402 may be used for connecting to a paging
device, for example.
3.
Extension 403 is created in all systems. It is defined as Global when created in System A and not defined
as Global when created in Systems B and C. This conflict requires resolution, or else System B and C
users cannot dial to the Global extension in System A.
4.
Extension 404 is created in Systems A and B as Global prior to the creation of the VoIP domain. This
conflict also requires resolution to determine which system will host the Global extension.
Changing an Extension’s Scope from Local to Global
If you need to resolve a conflict by making a Local extension into a Global extension, follow these steps:
1.
Select the extension in the User panel, and click the Resolve tab.
2.
Select the server name/extension where you would like the Global extension to reside.
3.
Click the Change to Global button.