Buying Shared Multiparty Licensing with TelePresence Endpoint

[ronlewis]

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)

[Taranjit Singh Dhaliwal]

Thanks Sri.

Few more queries:

1. The Migrate SKU 'R-UCL-UCM-MIG-K9' lets you upgrade between basic/enhanced/enhanced plus (Feature upgrade options).

However no options exist to upgrade existing UCL licenses (basic/enhanced/enhancedPlus) to TP Room.

Is there a way to go about upgrading unused UCL's to TP room licenses?

2. Secondly, as per the 'At a glance' doco: http://www.cisco.com/c/dam/en/us/solutions/collateral/collaboration/pervasive-conferencing/at-a-glance-c45-729835.pdf

Regardless of whether a integrator decides to offer user based CUWL-PRO 25 minimum or SMP 25 Starter kit to leverage the TP portfolio licensing (TMS/Conductor/TPS) as per use-case, we still need the TP-Room licensing in addition to CUWL PRO or SMP for MX/EX series endpoints.

3. The Cisco Video PMP-A licensing document at https://communities.cisco.com/docs/DOC-56000, casts further doubts and questions as it mentions:

"What do you get  with 25 PMP-A users order?

a) 13 screen licenses for Telepresence Server MCU (this provides 13 Full HD or 26 HD or 52 SD ports)"

Should we assume the above document is outdated and invalid? I tried clarifying it with the Cisco source who published it but apparently comments are disabled.

4. I'm trying to search from online documentation if the inbuilt bridge for MP-Video on EX series is also available on the MX series. Any idea?

Thanks in advance for your assistance. This will go a long way in clarifying doubts about TP licensing for all Cisco Partners selling/positioning TP.

[skilambi]

1. Since no option is provided, you cannot upgrade to TP room licenses

2. SMP license when purchased with the endpoint is the only way to get TP room license at no cost. SMP starter kit is purely infrastructure license like TMS/Conductor and is not endpoint licensing

3. That link is no longer relevant. PMP-A is now folded into CUWL PRO and doesn't count SL anymore. A user can host a meeting of any size as long as they don't exceed the capacity of the blade.

4. Yes MX series have built in multi site license. Check the data sheet that shows the resolution for example with 4 parties is different from 3 parties. You can order it through CCW. Multi site license is not a part of PRO or SMP

[Taranjit Singh Dhaliwal]

Cheers mate. Appreciate the quick reply.

For 3. Would be good to officially mark it out-dated as a lot of people searching for TP come across it. Maybe replace it with the link to this url or any updated version.

[CedricF]

Hi all,

Could you confirm me :

1/ SMP licenses works with VCS C / Conductor and TMS solution, without UCM and TMS-PE ?

2/ PMP licenses works with TMS and TMS-PE / VCS / Conductor, without UCM ?

Many thanks.

[skilambi]

1) SMP can work with ucm or vcs . TMS PE should be needed if you want to do personal cmr

2) no PMP needs ccm since it's based on CUWL pro

Thanks

Srini

[ronlewis]

And RMS licenses purchased with SMP are good for Expressway C&E only, at this point....can't use for traversal on VCS C&E....

Ron Lewis

Product Manager, CVTG

[CedricF]

Thanks everybody for your feedback and your clarifications.

[ASHKER NADAKKAL]

Hi Ron,

When the above offer, the screen license to SMP migration, will be possible ?

What will be ratio of SL to SMP ?

[Sebastian Leuser]

Hi Ashker,

the ratio will be 1:1. Some more details can be found there New Multiparty offering - Sept2015

What about existing customers with Screen licenses?

These will be offered a migration path to convert Screen licenses to SMP licenses.

Migration is very attractive since plan is to provide 1 SMP per existing Screen license.

Will follow up with details on this...

Sebastian

[Umair Ahmed Burney]

I have a customer who is planning to add 14x Sx20 with 10x cp8845 phone with be6k call control.

what will be the best solution to make customer possible to have 14 concurrent calls.

Plz confirm.

[ASHKER NADAKKAL]

Thanks Sebastian...

[skilambi]

In the new program concurrent calls don't count in terms of licensing like screen licenses in the old model. If your hardware can support X calls, you are licensed for the maximum. So the key is understanding how will the users use this model. The 8800 phones are usually personal devices and if used to start/host/schedule a meeting should be licensed as PRO. So that could be one way to handle it and based on if this is a net new customer or existing, Cisco has many programs in play.

Now for the SX20 generally those are in shared rooms. The idea there is any user could walk in and use it. If you can guarantee that any one of the CUWL PRO users will use the SX20 by either launching a scheduled meeting or PMR meeting by dialing their URI, then you will remain PMP and life is good. But if they try an ad hoc from that room(and in which case that endpoint owner ID in UCM isn't assigned to that user since it's a shared resource and assuming 10.5.2 or greater) then they will take SMP. If they also dial a rendeavous ID from that endpoint, it will be SMP. So in short one SMP will be good to have to cover these corner use cases.

If you buy just 1 SMP and no PRO, then you could have a 1 meeting with any number of participants as long as the server can support it and when buying SMP with the endpoint the cost is greatly reduced and you also get TP room license which you don't get with PRO. So cheapest way assuming net new customer will be 1 SMP assuming 1 meeting at any time is enough. You will also need to buy a starter pack since conductor/TMS comes by default with PRO but not with SMP unless you buy the starter pack. If you want more meetings increase the SMP count. Cisco recommends 1 SMP per endpoint but that could be excessive since unless the customer is having 14 meetings (not participants) at the same time it isn't needed.

So do the math different ways and see what fits the customer's budget and use cases.

Also see my posts above

Buying Shared Multiparty Licensing with TelePresence Endpoint

[btmulgrew]

Hi - I cant see the LIC-TP-SMP-EP SKU when ordering CTS-IX5200 (it is under MX series) - but the IX is referenced in the doc

http://www.cisco.com/c/dam/en/us/solutions/collateral/collaboration/pervasive-conferencing/at-a-glance-c45-729835.pdf

Thanks

Brian

[skilambi]

They mentioned this is a known issue and there have been delays with this endpoint. It’s to be fixed soon

[btmulgrew]

Hi Srinivasan - Am i correct in thinking existing customers will require below to support PMP/SMP:

TP Conductor 4.0

TMS 15.0

CUCM 10.5

http://www.cisco.com/c/dam/en/us/td/docs/telepresence/infrastructure/conductor/release_note/TelePresence-Conductor-Relea…

TP Conductor 4 may also introduce additional compatibility requirements:

https://tp-tools-web01.cisco.com/start/d160

Thanks

Brian