TelePresence Conductor and numerical alias dialling

[mnour401917_2]

Hi All

I have been trying hard to figure out how to get this working, I have TelePresence Conductor XC2.0 , VCSc 7.2.1 , TMS 14.1.1 and also MCU.

There is a requirement to call using numerical alias and also URI alias for example.

Meet.cisco.HD@cisco .com or 9555@cisco.com and calling these two aliases from different end points should end up on same conference. The new deployment guide for TelePresence Conductor shows an example of this and also testing scenario but I’m suspecting it is missing some steps.

VCSc search rule (Alias String) = (meet|teach|student)\..*@cisco.com

Conductor Alias pattern = (955.|meet\..*\.HD)@cisco.com

meet.cisco.HD@cisco .com ---- Works Perfectly

9555@cisco.com ---- NOT working

My questions are.

1.0   Does anyone have this working? And if yes I would really appreciate if you can let me know how it is done.

2.0   If you have it working, where you able to schedule it from TMS and participants dial using both numerical and URI aliases.

Test Examples from the Deployment Guide is as below. Your help will be much appreciated.

  ========================================================================

http://www.cisco.com/en/US/docs/telepresence/infrastructure/conductor/config_guide/Cisco_TelePresence_Conductor_Cisco_TelePresence_VCS_Deployment_Guide_XC2-0.pdf

====================================================================================

Creating a meeting

To test that two or more endpoints can join an HD TelePresence MCU conference based on a template with

a type of Meeting, dial 5432@<SIP domain> or meet.test.HD@<SIP domain> from each endpoint. Both

endpoints should be taken to the same conference.

To test that two or more endpoints can join an HD TelePresence Server conference based on a template with

a type of Meeting, dial 6432@<SIP domain> or meetts.test.HD@<SIP domain> from each endpoint. Both

endpoints should be taken to the same conference.

====================================================================================

Creating a lecture

To test that two or more endpoints can use different aliases to join the same TelePresence MCU conference

based on a template with a type of Lecture, have one endpoint dial 2311@<SIP domain> or

teach.test@vcs.domain to represent the teacher and have the other endpoint dial 3881@<SIP domain> or

student.test@vcs.domain. All endpoints should be taken to the same conference. The endpoints that dialed

3881@vcs.domain or student.test@vcs.domain will see a blank screen until the endpoint that dialed

2311@vcs.domain or teach.test@vcs.domain enters the conference.

To test that two or more endpoints can use different aliases to join the same TelePresence Server

conference based on a template with a type of Lecture, have one endpoint dial 2321@<SIP domain> or

teachts.test@vcs.domain to represent the teacher and have the other endpoint dial 3891@<SIP domain> or

studentts.test@vcs.domain. All endpoints should be taken to the same conference. The endpoints that

dialed 3891@vcs.domain or studentts.test@vcs.domain will see a blank screen until the endpoint that dialed

2321@vcs.domain or teachts.test@vcs.domain enters the conference.

[gubadman]

It looks like your search rule on VCS wont match the number and send that to Conductor - needs to start with meet|teach|student in your search rule

We have a similar setup, however we have an ENUM zone on VCS - http://www.cisco.com/en/US/docs/telepresence/infrastructure/vcs/config_guide/Cisco_VCS_ENUM_Dialing_Deployment_Guide_X7-2.pdf - to do the convertion from number to URI, and then only send the URI to Conductor.

Thanks,

Guy

[Justin Ferello]

Hello,

The following alias match on the Conductor should do what you want.  Also need to do what Guy suggested.

Match 1:

Incoming alias: (9555|meet\..*)@cisco.com

Conference name: 9555

Thank you,

Justin Ferello
Technical Support Specialist
KBZ, a Cisco Authorized Distributor
e/v: justin.ferello@kbz.com

[Martin Koch]

The history / logging / debugging features can help you here to find out where it fails.

Besides that, it might be handy to make your self clear how your conductor dialplan should look like.

What do dial and what needs to be triggered.

The way Justin describes does not look as it would work well.  It would bound all aliases to one

virtual meeting rooms, which is most likely not wanted for the meet.* addresses, but they would also

land into 9555.

Further it depends a bit if you want additional meeting rooms with numerical addresses or a mapping

of a name and a number with the same room.

For the first one you could handle nicely with search rules and conference aliases.

If you want to use a binding in between the name and the number it might be easier to use enum

then to manually create each and every conference as a static mapping on the conductor

(not sure, what is the limit for conference aliases? at least it does not scale well).

What you would do there as Guy describes, have something which is generating

name based meeting rooms and then make a mapping via either enum or a vcs policy pointing

from the name to the given number. Works fine for us as well.

[mnour401917_2]

Hi All,

Thans for your help, it looks like we need to have ENUM setup for this to work properly.

Should have mensioned it on my original post, what we are trying to achive is if conference is scheduled for example meet.cisco.HD@cisco.com , then is should be able to join that meeting from CUCM IP Phones, PSTN via Mobile or from any VCSc registered endpoint.

The other workaround is if i get the Conference ID of TMS to Match the number ID created on MCU's, right now i can call the AA of MCU and if i know the numeric ID in MCU i can join the conference. Issue is TMS doesn't seem to pass the Conference ID to Conductor, but it is able to pass the Conference PIN.

Thanks

Mohammed