Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Unity 3.1.x and AMIS Destinations

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


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?



Re: Unity 3.1.x and AMIS Destinations

The piece of the puzzle that you are missing is where the outbound calls will actually originate. Even tough Unity nodes in domestic locations will learn of the AMIS delivery location object and (depending on configuration) subscriber will be able to address it, the messages will still be sent from the Unity node that owns the location. So the customer will be able to maintain the same delivery location ID but it might come with a trade off of long distance toll changes.

But then again maybe you are making long distance calls between locations over the IP network so it's all the same. ;-)

It's cheaper as far as Unity licensing goes with this model because only one Unity node needs a license for AMIS and the others can then share it.

Hope that helps,


CreatePlease login to create content