Migrate from Legacy PRI isdn to IP SIP TRUNKING

[Jean Paul Enerst]

Hi all,

We're getting ready to jump into the SIP trunking wagon... I hope the ride will be as smooth as possible. Here it's, we have UC(10.5) and H323 voice GW.

Call Flow is: UC ----> VOICE-GW ---> PSTN

Extension from remote to remote or/and remote to HQ is under VPLS. And if PRI at one remote site is down, calls are routed to HQ, then HQ route them to PSTN.

We have 5 site connected connected in full meshed with VPLS... And of course, UC is impletemented in cluster but each site currently has their PRI. Now we are moving to SIP TRUNKING... looking for some insights, suggestions, advices(good,bad experience).

And yes, i have read a bunch about sip in the last few months yet there is still have some gray area...

Requirements:

1. Minor to no change at all in UC(CUCM,UNITY,UCCX);therefore, call flow from UC to voice GW to main H323

2.Convert Current voice-GW into CUBE(mode border-element under the service voip).

    Current IOS 15.2(4)M3 but planning to upgrade to 15.4-3M2

3. Need to keep PRI in place during testing and at least for a few weeks after switch over. So Dial-peer with preference number is required for call routing, right?

4. Even we have full meshed VPLS with the same provide, should i be concerned about Security? If so, please provide best practices(thx).

5. Current platform 2901 and 2911 ISR G2 with UCK9 permanent license.

6. Now with UCK9 license, does it require a separate license for SIP sessions(FL-CUBEE-100). We have less than 100 employee at each site, except HQ.

Thank you so much all,

[Terry Cheema]

1) Yes you will not much change in UC side apart from creating SIP trunks/call routing.

2) Yes you will need to turn on the CUBE functionality on the voice gateway and need to buy CUBE licenses.

3) Yes you can use dial-peer preference if needed.

4) Since you will not be running SIP over internet, Firewalls will be over kill, you can use the standard access-lists/toll-fraud features available in the CUBE.

5) UC9 is fine but you will need CUBE licenses as already mentioned

6) Yes it does. You will have the option to choose FL-CUBEE-5, FL-CUBEE-25, FL-CUBEE-100

Refer to ordering guide - Section 2.2:

http://www.cisco.com/c/en/us/products/collateral/unified-communications/unified-border-element/order_guide_c07_462222.html

Let me know if you have any more questions.

-Terry

Please rate all helpful posts and mark the thread as answered if you have no other queries.

[Jean Paul Enerst]

Thanks a lot Terry for the help...

However, i do need a quick clarification on point one( change in UC).

i am not sure that i need to configure SIP trunk(call routing). Reason being that i want to keep GW-TO UC on H323 and let the GW doing the transcoding being H323 TO SIP, SIP-TO H323 as i have enought DSP resources for that.

[Terry Cheema · Accepted solution]

Appologies somehow I skipped this query, you may be sorted by now, but I will still answer:

Yes you can have H323 from CUCM to VG and SIP to your ITSP.

Generally speaking though its better to do end to end SIP where possible for various reasons but if you have H323 leg from CUCM to VG it will work as well.

Hope this answers your query.

-Terry

Please rate all helpful posts and mark the thread as answered if you have no other queries