The Conference Factory Alias must be a SIP URI that is routable to this Cisco VCS by every endpoint that wants to initiate a Multiway conference.
The Conference Factory Alias will be registered to the Cisco VCS.
The Conference Factory Template must result in a SIP URI that is routable by every endpoint that may be asked to join a conference – whether it is a SIP device or an H.323 device. In an integrated environment where IP PBXs may be requested to join a conference, these IP PBXs must be able to route calls to this URI.
If the Template is creating a URI that will be routed to an H.323 MCU, typically the name part of the URI (name@domain) must produce a numeric only ID, as H.323 MCUs typically only support E.164 dialing.
If calls are to be made to an MCU that supports SIP, it will register %%@MCU.domain ... make sure that is unique for SIP calls, so that it does not match other dialable SIP destinations.
Make sure that the Template cannot generate URIs which match existing endpoint URIs or other Multiway conference URIs – otherwise calls may end up ringing endpoints or joining another conference.
The Template is not replicated across cluster nodes and must be configured independently and uniquely for each node. See the separate section on configuring Multiway in a clustered environment.
To ensure that the Conference Factory Alias is processed quickly, you are recommended to add a dedicated, high-priority search rule for this alias. The effect of this will be particularly beneficial in scenarios with many search rules and zones.
And actually I do not get the thought behind your deployment anyhow and some info are missing
(like which target zone you try to use with your search rules, why you add a h323 only search rule for it,
how you configured multiway on the endpoints, ...)
Also the log from endpoints and the vcs (also search and call history & details for the attempts)
What I would do:
* read the multiway deployment guide
* read the multiway deployment guide again
* properly implement URI dialing and domains, especially if you want to use sip
* see that you get encryption working and thats currently only possible with h323 towards the mcu (if you need encryped content) anyhow, h323 to the mcu still feels like a good idea on vcs deployments also for the
* properly set up the multiway uri on the endpoints (try to prefix it with the protocol you use, like h323: or sip: and also manually set the protocol, I would use the call protocol which you use as the default)
I'm not able to access my old voice mail messages all of a sudden. The recording says something like 'the message is currently not available'. This has never happened before in all the years I have been using this system. I have t...