06-10-2014 05:43 PM - edited 03-18-2019 03:04 AM
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.
I'm using:
VCS X7.2
Conductor XC2.3
TP Server 4.0
Any help much appreciated :)
12-06-2014 11:39 AM
12-06-2014 08:46 PM
Hi George, unfortunately not, I ended up configuring every endpoint individually. Massive pain!
12-06-2014 08:48 PM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide