07-02-2013 06:29 AM - edited 03-18-2019 01:23 AM
Hi,
In MSE 8000 chases I have 8510 and 8710 cards. MCU 8510 supports Auto Attendant. If any voice call is placed on MCU 8510. Call can join the conference which is held on MCU 8510. I need to join a conference which is held on MCU 8710. I am unable to join conferences which are running on MCU 8710. Is there any way I can join MCU 8710 conference using MCU 8510. 8710 does not support Auto Attendant. Pls suggest.
Rdgs,
Shree Parashar
07-02-2013 09:33 AM
Hi Shree,
MSE 8710 does not support auto attendant, therefore, to join conference on this MCU, you should have it integrated with a Call Control, such as VCS or CallManager, so that the Call Control server will route calls to MCU propoerly and allow users to join in the conferences.
For example, let's assume you have a VCS as control server. In this case, MSE 8710 will register all its conferences numbers to VCS registration table, so that VCS will be able to route calls to those conferences created on 8710. Then, All the endpoints properly registered to VCS will ne able to join 8710's conferences.
Could you please describe better your environment? which telepresences components do you have?
Regards
Paulo Souza
Please rate replies and mark question as "answered" if applicable.Hi
07-02-2013 09:47 AM
I have TMS, TMSXE, VCS-C, VCS-E and CUCM 9.0. Polycom endpoints are register on VCS-C. Telepresence equipment’s are registered with CUCM.I have SIP trunk between VCS-C and CUCM. For Polycom endpoint we use, MCU 8510. For mix (Polycom and Telepresence) or Telepresence calls. We use MCU 8710.
Rdgs,
Shree Parashar
07-02-2013 10:15 AM
Shree,
As you are using TMS for scheduling, you must to register both MCUs 8510 and 8710 to VCS-C. So all the conference numbers you create on both MCUs will registered to VCS-C. Therefore endpoints registered to VCS, CUCM and to VCS-E will be able to dial the conference numbers on both MCUs.
I would suggest you to save a time to plan and design a dial plan. So you can configure all the routes, transforms, trunks, conference numbers, alias and etc - in order to allow the enviroment to work properly.
Regards
Paulo Souza
Please rate replies and mark question as "answered" if applicable.
07-02-2013 01:29 PM
I also agree, that maybe stepping one step back can be handy, what do you have, what do you need/want
and whats doable in which way. Some features might exclude each other in different deployments, but
most of the time something properly working can be found :-)
Thats one point why I can not understand that Cisco retired the IPGW, that one could have offered
you a IVR on IP.
If its ISDN calls you could use the IVR of the ISDN-GW
If its internal audio calls it should be fixable with a proper dial plan.
If you have enough public phone numbers you can also do some mapping.
If you need a voice IVR/AA, you should find 3rd party producs as well. For some private stuff I use
http://www.asterisk.org which works great :-)
Please remember to rate helpful responses and identify
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