Any way to use non-unique Multiway addresses on endpoints when using Conductor?
As per a previous thread, I've got Conductor + VCS + TP server working in a semi-test environment. The plan is to use this for Multiway.
The challenge I'm facing now it to be able to roll out a multiway address to all my endpoints. From what I can gather, each endpoint would need to be configured with a multiway address of:
[conference-prefix][something unique to the endpoint]@mydomain.com
The problem I have is that we have 100+ endpoints, at least half of which aren't permanently connected to the network (which means allot of phone calls to get them connected!). We also don't use TMSPE for our room based endpoints, so this can't be easily provisioned.
Is there a way I can provision the same Multiway address to all endpoints (I could do this with a TMS configuration template) then use something like a VCS search rule or CPL to add a unique identifier, perhaps a call serial number or something based on source URI, to append to the end of the search string? This would ensure each endpoint dials a unique conference on Conductor without having to individually provision Multiway addressing to every endpoint.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...