12-03-2021 12:10 AM
Understood CUCM and CUCM SME is very similar except CUCM SME wont be used for phone registrations and used mainly for call routing between clusters or various devices as per below discussion link:
My question is, if I am going to add a new Voice Gateway to an existing CUCM SME, will it be the same process as adding a new Gateway/Trunk (for H323 and SIP) to a normal CUCM? Is there any other thing I need to take note of?
12-03-2021 07:07 AM
They're not very similar, they're the exact same thing, a regular CUCM install becomes an SME due to the role it plays in routing.
12-08-2021 08:40 PM - edited 12-08-2021 08:42 PM
Thank you for the reply. I appreciate it.
Is it safe to say that it's best practice for SME to configure the Device Pool, Trunk, Partition, CSS, etc. (and other Voice Gateway related config) on the SME itself if i'm adding a CUBE/H323 or MGCP VG for external calling? I do understand that it will depend to me but want to know the best practice on the real world scenario.
12-03-2021 09:53 AM
There exactly the same, so no difference at all in how you operate these.
12-08-2021 08:43 PM - edited 12-08-2021 08:43 PM
Understood, thank you for the reply. I appreciate it.
Is it safe to say that it's best practice for SME to configure the Device Pool, Trunk, Partition, CSS, etc. (and other Voice Gateway related config) on the SME itself if i'm adding a CUBE/H323 or MGCP VG for external calling? I do understand that it will depend to me but want to know the best practice on the real world scenario.
12-09-2021 10:04 AM
It’s is a regular CM, do as you would do for your leaf clusters.
12-09-2021 06:14 PM
Thank you Roger!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide