SME or CUBE for sip normalization

[kbeelwar]

Hello,

I am migrating 12k users from Avaya 6.3 to CUCM 10.5. There are number of sites with old SCC/MCC with PRI.

I am hoping to follow these steps for migration.

1. Add a cube for central dialplan. I am torn between sme or cube which can be central solution??

2. Replace SCC/MCC with cisco 3945 and point the voice gateway to central CUBE using SIP.

3. Add cucm cluster

4. Add centralised SIP trunk and utilise site voice gateway3945 for SRST

5. Remove avaya phones off sites and put cisco phones

6. Decommisioning avaya system

7. Remove the SBC pair.

Pls let me know if these steps sound reasonable.

thank you

[dakeller · Accepted solution]

Looking at the steps you have listed, I'm not sure you'll accomplish what you want.

1) for a 'centralized' dialplan, most customers will use SME.  Because many of these customers have UCM already, SME makes sense since it's UCM w/o any endpoints, just aggregated dialplan and SIP trunks.  CUBE can be used, but CUBE typically serves as an SBC between the customer network and various service providers.

2) If you replace the SCC/MCC with a 3945, what is doing call control for the phones at the site.  If SCC/MCC is removed, will the phones register as SIP UA's to the 3945??  I would expect you to connect the SCC/MCC to the 3945 to provide connectivity to the SME (step 1) for centralization of the dialplan and PSTN access.

3) add a UCM cluster....that's needed to replace the Avaya :-)

4) not sure why make a SIP trunk here....should have been done as part of step 2.  Setting up 3945 as SRST is good for when you replace the avaya handsets with Cisco Phones.

5) After the endpoint replacement (and tested of course), the migration is done.  The last 2 steps are housekeeping. 

Since the steps described in your post are pretty general and not specific, I may have misread what you are planning on doing.  If so, please repost clarification and I will answer as best as I can.

Thanks,

Dan Keller

Technical Marketing Engineer