AltiGen comm ACM 5.1 manual Changing an Extension’s Scope from Local to Global, Conflict

Chapter 25: Enterprise VoIP Network Management

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 it set 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.

Note: You must take the voice mail box and extension configuration into consideration when you change an extension to Global. In making this change, you will be deleting the voice mail box and extension settings on the home system of the “other” Local extension. A warning box will pop up when you click the Change to Global button, asking for confirmation:

348AltiWare ACM 5.1 Administration Manual