Setting up Multiple Locations

Last Updated : Oct 07, 2026 |
Prolog information
Metadata
Keywords:
Before you begin
Ensure that the Multiple Locations field on the System Parameters Customer-Options (Optional Features) screen is set to
  • , go to the Avaya Support website at http://support.avaya.com for more information. If you are setting up locations across international borders, you must ensure that the Multinational Locations field on the System Parameters Customer-Options (Optional Features) screen is also set to
    • Multiple locations are supported only in the dedicated instance deployment. In case of multitenant deployment, each tenant is limited to one location.
    Ensure your daylight saving rules are administered. Daylight Saving Rule numbers are located on the Daylight Saving Rules screen.
    You can define a location number for:
    • Remote Offices
    • Gateways
    • IP network regions, used by IP stations and IP trunks
    You can create numbering plans and time zone and daylight saving plans that are specific for each location. Choose your main location, and offset the local time for each location relative to the system clock time. The main location is typically set to have offset 0.
    For example, we will set up multiple locations for Communication Manager server with media gateways in Chicago and New York. Location 1 is assigned to the media gateway in Chicago, our main office, so Central Standard Time is used for our main location. Location 2 is assigned to the media gateway in New York. We’ll define the numbering plan area (NPA) for the Chicago and New York locations, and set the time zone offset for NY to show the difference in time between Eastern Standard Time and Central Standard Time.
    Tip:
    Type list media gateway to see the Media Gateway screen and a list of media gateways and their locations.
    To define locations for media gateways in Chicago and New York:
    1. Type change locations.
    2. Press Enter.
      STEP RESULT:
      The system displays the Locations screen.
    3. Type y in the ARS Prefix 1 required for 10-digit NANP calls field.
      ADDITIONAL INFORMATION:
      Our dial plan requires users to dial a 1 before all 10-digit (long distance) NANP calls.
    4. Type Chicago in the Name field in the Number 1 row.
      ADDITIONAL INFORMATION:
      Use this field to identify the location.
    5. Type +00:00 in the TimeZone Offset field in the Number 1 row.
      ADDITIONAL INFORMATION:
      In our example, the system time and the Chicago location time are the same.
    6. Type 1 in the Daylight Saving Rule field in the Number 1 row.
      ADDITIONAL INFORMATION:
      In our example, daylight saving rule 1 applies to U.S. daylight saving time.
      Tip:
      Use the display daylight-savings-rules command to see what rules have been administered on Communication Manager.
    7. Type 312 in the Number Plan Area Code field in the Number 1 row.
      ADDITIONAL INFORMATION:
      In our example, 312 is the local area code for Chicago, location 1.
    8. Type New York in the Name field in the Number 2 row
    9. Type -01:00 in the TimeZone Offset field in the Number 2 row.
      ADDITIONAL INFORMATION:
      In our example, subtract one hour from the system clock in Chicago to provide the correct time for the location in New York.
    10. Type 1 in the Daylight Saving Rule field in the Number 2 row.
      ADDITIONAL INFORMATION:
      In our example, daylight saving rule 1 applies to U.S. daylight saving time, and both locations use the same rule.
    11. Type 212 in the NANP field in the Number 2 row.
      ADDITIONAL INFORMATION:
      In our example, 212 is the local area code for New York, location 2.
    12. Press Enter to save your changes.
      ADDITIONAL INFORMATION:
      For more information about the Multiple Locations feature, see Avaya Aura® Communication Manager Feature Description and Implementation.