Buying Shared Multiparty Licensing with TelePresence Endpoint

[#1]

The Shared Multiparty (SMP) Licensing offered with TelePresence endpoints supports Multiparty conferencing using TelePresence infrastructure components on customers premises. The customer acknowledges by purchasing SMP license that they have already or plan to deploy the necessary hardware to support Multiparty Conferencing.

Each SMP license allows for one concurrent meeting with unlimited participants, deployed using Cisco Meeting Server or Cisco Telepresence Server. The SMP license also includes 1 Expressway Rich Media Sessions (RMS), and the CUCM/Expressway TP Room License. A single RMS licenses now only needed on Expressway-E with version X8.8 and higher.

For Multiparty conferencing using the SMP License requires one of these options deployed;

• Cisco Meeting Server(s) with an activation key (R-CMS-K9, included with CMS1000 bundle)
• Cisco TelePresence Server without screen licenses, Cisco Telepresence Conductor, and Cisco TelePresence Management Suite (TMS) with Provisioning Engine (TMS-PE).

New customers without CUWL Pro or Meetings, should look at the SMP Starter Kit to get initial package licenses.

Existing customers can just add additional SMP License to their Meeting Server or Conductor.

For deployment details, see here http://www.cisco.com/c/en/us/support/conferencing/collaboration-meeting-rooms-premises/model.html

More information on SMP along with Personal Multiparty for CUWL-Pro customers, see this at a glance.

Ordering guide with CCO login at http://cisco.com/go/meetingserver

(This note is for CCW users ordering SMP needing more information)

[#2]

Ron

When you say 2 RMS, will it be 2 for Expressway-E and 2 on C or 1 on C and E? In the old model if you remember this was a point of confusion

[#3]

For recommended deployments, 2 RMS, which is usually good for one traversal, though Expressway C & E.

[#4]

Got it thanks.

Thanks

Srini

[#5]

Ron,

For customers who have TP screen licenses, is there a migration path to SMP license?

Thanks,

George

[#6]

Yes we do plan to offer screen license customers a migration to SMP, later this month, via the Product Upgrade Tool with a valid support contract.

[#7]

As well as TP Server screen licence migration to SMP are there details of how MCU media ports can be converted to SMP for customers who wish to migrate from MCU to Conductor/TelePresence Server.

[#8]

Hi, the SMP licenses are available for a customer with HCS? As far I understand, the PMP are not available for HCS's customers, but for the SMP if the Conductor, TS and TMS are on premise

And another question: If the customer already has a vTS with SL, conductor and TMS, can he use his conductor (medium size) and TMS or he have to buy the starter kit?

[#9]

Is it correct to assume that the 25 devices in the starter pak are 25 TP room licenses for CUCM?

[#10]

No the starter pack is TMS TMS XE TMS PE only

If you have CUWL PRO in the mix you wouldn't order this since that comes with it too

This is mainly for pure SMP customers most likely vcs customers or those who only have shared rooms

Only way to get TP license is to buy the new SMP EP bundle with the endpoint or ala carte like before

Thanks

Srini

[#11]

So, TP Server licenses that would be part of CUWL-Pro are able to be shared with the TP Rooms without the need for extra/SMP licenses for the TP servers?

[#12]

Conductor is operating in a new mode called Multi party Mode. Inside that you have PMP/SMP licenses which are allocated based on the scenarios such as shared room adhoc vs user CMR vs user adhoc and so on. Telepresence server works with conductor to allocate as needed. This isn't like the old where TP server had screen licenses that couldn't be shared with PMP-B OR PMP-A licenses and it had to separate resource pools. This can all be one pool managed by conductor. If you have TP servers using "legacy" Screen licensing model then that would be a separate pool but can be managed still by the same conductor. Hope that helps

[#13]

On the 'at a glance' PDF it states that each SMP licence supports one concurrent meeting.  What is the definition of 'one concurrent meeting'?  How many participants can join this conference?  What call quality is supported eg 1080p60 or 720p30 and would this increase/decrease the number of participants?

I am thinking of a situation where there are 25 room bases systems (MX300 etc).  Can I get 10 SMP licences and have a conference with all 25 End Points?

Thanks

Rob

[#14]

Each concurrent SMP meeting supports unlimited participants, any resolution, up to what TS hardware handles. With all 25 endpoints, with one SMP, in license. With 5 SMP, 5 meetings; 3 or more participants each does not matter, using multiple TS servers, as Conductor is counting concurrent meetings. If 5 SMP, any number of participants ok. If a 6th SMP meeting starts, then license violation, alarmed/flagged.

Hope this helps to explain,

Ron Lewis

Cisco

[#15]

Still confused.  If a customer is a CUWL-Pro customer (new customer), they will have a bunch of Personal Multiparty licenses on the Telepresence Server(s).  They'll have Conductor, TMS, etc.  If they purchase a new SX80, for example, and want to add it to CUCM AND want to use ports on the TS, do they need to purchase both a CUCM TP Room license and a SMP license?  Or, can they just purchase the TP Room license and use the available ports on the TS already there from the CUWL-Pro users?

[#16]

The issue is first defining personal versus shared room space. Usually sx80 will be a shared room endpoint. The question here is will a user who is assigned as CUWL pro walk over to the room that has the sx and use their personal cmr uri. If so you don't need a SMP

On the other hand if it's any user who isn't licensed you use SMP

So basically if you have a CUWL PRO user already licensed and they walk over to the SX80 and use their personal CMR, you will use PMP. If on the other hand they dial a rendeavous ID it will be SMP.

If they do scheduled and TMS send the GUID which matches the user GUID on the conductor database it will be PMP otherwise SMP

If they do adhoc and the SX80 isn't assigned to them in CUCM as the owner ID field it will be SMP otherwise PMP. Usually you will only see personal devices like DX or Jabber assigned to users and not a SX80 so most likely it will use SMP for adhoc

So the important thing is to define the use case, how will the endpoint be used, will the user using that room be licensed or it will be used by any user who isn't PRO will determine usage. Cisco recommends to have 1 SMP at least so that if there is a use case you didn't think of or the customer used it a certain way you didn't think of then it will use that SMP as a fallback to PMP. Today you have just license violations so even if you make a mistake its not like the system shuts down but future could more stricter enforcement

Hope that helps

Thanks

Srini