cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
873
Views
4
Helpful
0
Comments
azoupas
Cisco Employee
Cisco Employee

hi all,

Cisco Unified Communications Manager (CUCM) is iconic collaboration solution by Cisco. It is selected and long-time trusted by many organizations worldwide, covering their IPTelephony & Unified Communications needs.
Now, as cloud collaboration services evolve rapidly, the question for CUCM customers is  : ''what are the evolution paths I could follow?".  In this brief article, I would like to add some high level thoughts on this topic.

1) Migrate to Cloud Calling (Webex Calling or Webex Calling DI)
First obvious path is to examine the migration to cloud calling.
Cisco provides two options : Webex Calling(WxC) and Webex Calling Dedicated Instance (WxC DI).
Webex Calling is the leading platform offering amazing innovation and benefits.
Webex Calling Dedicated Instance (DI) is a valuable option that allows you to run a ''cloud calling solution'' while keeping CUCM feature set (WxC DI solution is based on CUCM product).
Now if you move calling workload to the webex cloud, you could, of course, leverage other webex services in order to form a unique solution : Webex Messaging, Webex Meetings, Cloud registration of Video devices, Webex Contact Center, etc.

More details on the benefits you get to move CUCM to Webex Calling can be found here:
Why move to Webex Calling? (for existing onprem CUCM customers) (ppt)

Important note:
Note that you could move to cloud calling at your own pace. Could start with a small WxC trial, expand it to selected sites and then go for full roll out. Nice thing is that CUCM and WxC could coexist and interoperate. Plus, if you have Webex app as CUCM softphone then user migration is even easier (as CUCM and WxC are using same user app - Webex app).

If this path sounds interesting, contact your Cisco and partner team and ask for Webex Calling Demo and presentation.
Next step could be to proceed to Webex Calling trial that would allow you to see great benefits in practice.
--------------------------------------- ------------------------------------------------
2) Keep CUCM as onprem PBX and Webex app and other webex services // ''Hybrid story''
There are cases where certain requirements might dictate to keep CUCM as your onprem PBX but you are open to leverage other cloud components. Some examples that might lead you to this path:
Using large number of old IPPhone models that are CUCM compatible but not compatible with Webex Calling. And need more time to examine Phone refresh.
Need some special advanced IPPBX features that are only offered by CUCM.
You have existing cisco and/or 3rd-party integrations with CUCM that you don't want at this moment to move/redevelop for cloud.
At same time, you don't have a strong ''cloud only'' mandate (otherwise WxC DI would cover above aspects).
You might want less dependency on cloud.
C
hanging your Phone system does not seem to be one of your top priorities at this period.

Now good news is that you can still greatly evolve your calling services by keeping CUCM onprem and make below additions:
a) connect your CUCM to Webex cloud via Cloud Connected UC(CCUC) 
This gives you great benefits on Analytics/Troubleshooting/Monitoring and advanced features on MSFT calling integration (if desired). More details can be found here:
Webex Cloud Connected UC - connect your CUCM to Webex cloud
b) replace Jabber with Webex app (as CUCM softphone)
This brings amazing benefits to your users (noise removal, virtual background and many more) plus allows you to leverage Webex messaging and Meetings from single client. And again Webex app also provides advanced features on MSFT calling integration (if desired).
More details can be found in below articles:
Jabber to Webex app benefits (ppt) (soon to be published)
Webex app calling integration with Microsoft Teams

--------------------------------------- ------------------------------------------------
3) Keep CUCM as onprem PBX plus cloud components are not applicable/allowed
There are cases where due to vertical requirements or regulations, cloud components are not allowed. So you are forced to continue with a fully onprem(''airgapped'') solution. In this case, you can still keep CUCM as onprem PBX together with Jabber client. And of course you could also leverage CUCM IM&P for chat and CMS (Cisco Meetings Server) for onprem conferencing services (if desired).
--------------------------------------- ------------------------------------------------
A slide that summarizes 3 paths -->

Screenshot 2023-09-08 at 1.49.40 AM.png
--------------------------------------- ------------------------------------------------
Please rate if you find helpful.

Index of all my collab community posts --> Looking for info on Cisco Collab solutions ? 

thanks!
Alkiviadis

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: