3510 and E.164 alias

[Febo]

Can the 3510 MCU be assigned an E.164 alias?

We have an Avaya MCU with some IP extensions that we would like to cascade to a 3510 using one of the aforementioned extensions. Inviting the Avaya MCU via the web browser for the 3510 has not been succesful. Since we have not been able to detrmine if and or how the 3510 has an E.164 alias we can't call it yet.

The Avaya uses a Radvision L2W-323 Gateway to provide the translation for the IP extensions (its primarily used for H.320 calls).

We're trying to build a hybrid conference (H.320 & H.323 endpoints) where we either invite the 3510 to join via one of the IP extensions or have it 'invite' the Avaya to an on-going conference in the 3510.

Although the 3510 MCU and the Radvision are at the same site they are on different networks.The setup for the Radvision has the 3510 defined as a neighbor GK and the 3510 also appears in the Zone defintion table of the Radvision's setup. Conversely, the Radvison is defined as a neighbor GK in the 3510's set up but there is nothing in the Zone definition table for the 3510.

Any assistacne would be greatly appreciated.

Thanks.

[ciscomoderator]

Since there has been no response to your post, it appears to be either too complex or too rare an issue for other forum members to assist you. If you don't get a suitable response to your post, you may wish to review our resources at the online Technical Assistance Center (http://www.cisco.com/tac) or speak with a TAC engineer. You can open a TAC case online at http://www.cisco.com/tac/caseopen

If anyone else in the forum has some advice, please reply to this thread.

Thank you for posting.

[sachon]

The 3510 supports service prefixes. Service prefixes can be appended with a conference ID. Together, the prefix+conference ID make up the e.164 address of the box. If properly configures, GK should route any call with the proper service prefix to the MCU.