We have a client that is using AMIS quite successfully here in
North America in a Unity 3.1(4)/CCM3.2.2(c) meets Avaya
environment.
The new twist is that they would like to add an international
location to the AMIS mix.
The client would like to continue to use the same location
codes throughout the enterprise, regardless if the Unity
system is domestic or international.
In NA, an AMIS destination is assigned a location code that
is provisioned to dial the remote AMIS node using a trunk
access code or 9, the direct dial code of 1, and then the
remaining XXX-XXX-XXXX digits. Unity dutifully replicates
this entry across all of our Unity nodes both domestically
and internationally.
It seems that this issue could occur domestically with clients
that have different trunk access codes in different locations
as well.
We believe that we could use a translation pattern in CCM
to replace the 9 and 1 with appropriate information for the
international location to dial out for an AMIS transaction.
Is there a better method to provide for this? Or is it advisable
to use multiple location codes to represent the same remote
location with the difference being how the call is placed?
---Thanks---