Hybrid CMR concurrent SIP connections to WebEx failing

[William McDonough]

Hello all!

I am pleased to say that I have Hybrid CMR standing and it is working great.  We have an alias range for booking Hybrid CMR meetings, all users are enabled for this feature (we haven't announced it yet) and all test cases work great.... except that if I have a user with an active Hybrid CMR meeting connection (SIP) to webex and another user has booked this same type of call the entire conference that is already going will be terminated and the new conference will fail to start.  This is the only scenario where this happens.  I am thinking I have missed something that allows for concurrent meetings, any one have any ideas?  I have read the guide over and over and I have seen nothing about this.

Thanks,

Liam McDonough

Senior Collaboration Engineer

Cimpress

[William McDonough]

I forgot to mention the Telepresence servers in question are not at capacity when this occurs so it is not the TPS thinking that they don't have room.  We have over 120 screen licenses available for these conferences.

Conductor on V3  (upgrading in Feb)

Telepresence servers on 4.1

TMS 14.6.2   (upgrading in March)

Thanks,

Liam

[dpetrovi]

Hi Liam,

Let me move this post to Telepresence community. This community is for Cisco WebEx Meetings Server and Cisco Unified MeetingPlace products and is not observed by TP experts. 

I hope this will get you the answers you need faster.

Kind regards,

-Dejan

[Patrick Sparkman]

TMS should use the different conference alias when a conference is scheduled, unless the conference alias is static. 

Can you describe how you have the aliases setup for these WebEx conferences?

How do you have the extended settings for Conductor as well as it's aliases configured in TMS?

[William McDonough]

Patrick

After diving in deeper I have found that it is smart scheduler causing the issue, or rather any conference booked through smart scheduler using the conductor so we can remove webex as a cause.  

Conductor Settings:

IN TMS

Alias Pattern 8887%@domain.net

Numeric base - 1000

Numeric step - 1

On Conductor

Alias -(8887[^@]*@domain\.net).*

Conference name - Company WebEx enabled Telepresence (should this be regex for conference names as they all will be identical?)

Priority - 1

Conference template:

Name - Scheduled MeetMe

Conference type - Meeting

Call policy mode - off

Service preference - Scheduled preferences (Main pool)

Cascades - 0 (no need for now plenty of space per server)

NOT LIMITING PARTICIPANTS

Max screens - 2

Scheduled conference - yes

It is important to note that our ADhoc CMR is not effected by this only when a scheduled meeting is launched where another scheduled meeting is active that they both terminate.  I feel I am missing something simple here as the scheduling works, the range is clearly being used on the scheduling side as all bookings show the range being used properly (88871000,88871001 and so on) but as soon as the calls are on at the same time it terminates.  

Telepresence Conductor is the default conferencing platform for all conferencing in TMS general settings.

I am curious.. would the conference name be what is causing the issue here since it is technically the same across all booked conferences?  If that might be the issue what would be a good REGEX solution to the naming convention.

Thanks,

Liam

[Patrick Sparkman · Accepted solution]

Conductor should use unique identifiers to reference conferences and it's changes to them.  Have you looked at the full details of one of these WebEx conference within TMS that's scheduled using the Smart Scheduler.  Does anything stand out when comparing it to a conference scheduled through the full TMS scheduler?

Looking at your Conductor configuration, I would at least make the following changes:

• Alias: (8887\d{4})(@domain\.net)?
• Name: Company WebEx enabled Telepresence - \1

The first part of the alias will match 8887 and your 4 digit TMS variable, ex: 88871000, where \d{4} will match any number that is 4 digits long.  You could even change this to be 88871\d{3} if you want to get more granular since your TMS variable will always have a 1 in it unless you just happen to schedule over 1000 conferences at the same time.

The way I have the alias broken up into two parts with the parenthesis, ie: (8887\d{4}) and (@domain\.net)? will allow the numeric section to be matched with and without a domain.  This will also allow the numeric section of the alias to be added to the conference name, so it's easily identifiable if you happen to log into the conference bridge for any reason, and it won't create any confusion or possible conflict if any should arise.

[William McDonough]

I hade the name change and this solves the immediate problem.  I will definitely make the alias change this week end but since we have a few high level meetings tomorrow I am not going to modify it for now.  This works great and I knew I was missing something obvious but I am not great a REGEX.  Do you have an recommended resources for wrapping ones mind around REGEX?

Thanks,

Liam

[Patrick Sparkman]

There is a regular expression reference in the back of the Conductor Admin Guides.

I also use the website RegEx101 to help build and test regex expressions.