H.323 and SIP work on Same Gateway

[wilsonsant]

Hi Guys,

Hi Guys,

My Customer today have a Gateway H.323 with carrier X and will change for SIP with carrier Y. I know that in the CUCM side is need create SIP Trunk, change routes, and another things. My question is: in gateway what change need to do? Is possible SIP and H323 work in the same time, until that my Customer finish the contract with carrier X?

Thanks,

Wilson

[Georgios Fotiadis · Accepted solution]

Yes, H.323 and SIP can work at the same time. You will have to enable CUBE to your ISR and allow sip-to-sip connections. How do you currently connect to the ITSP? A PRI line or a H.323 trunk?

[wilsonsant]

Hi Georgios,

Thanks a lot for Your contact. Today the H.323 is using E1 connection with the carrier. When You say "You will have to enable CUBE ", what command is used?

controller E1 0/1/0
 framing NO-CRC4
 ds0-group 0 timeslots 1-15,17-30 type r2-digital r2-compelled ani
 cas-custom 0
  country brazil
  metering
  collect-call-enable
  category 2
  answer-signal group-b 1

Thanks,

Wilson

[Georgios Fotiadis]

This is a good guide that explains the basics of CUBE: CUCM to CUBE Integration Configuration Example. You can start with that.

[R0g22]

So you will be keeping your E1-R2 circuit with your Telco and change CUCM-GW protocol to SIP ? Or you are doing away with this circuit and getting a sip trunk from your ISP ?

[wilsonsant]

Hi Nipun,

Thanks a lot for Your contatct. Answering Your ask: My Customer will change H.323 to SIP and not more will be use the H323. But, I need test first SIP to see worked fine then cancel the H323 with carrier.

Thanks,

Wilson

[Georgios Fotiadis]

I think you are confused a little bit here. As per your sayings, now you have:

CUCM - (H323) - VG - (PRI) - ITSP; i.e. your connection to the ITSP is ISDN PRI and not H323.

You want go to CUCM - (SIP) - VG - (SIP) - ITSP; for this you will need CUBE enabled at your VG.

[R0g22]

I believe you are not using H323 with your carrier. You are using the following which a E1 CAS circuit -

controller E1 0/1/0
framing NO-CRC4
ds0-group 0 timeslots 1-15,17-30 type r2-digital r2-compelled ani
cas-custom 0
country brazil
metering
collect-call-enable
category 2
answer-signal group-b 1

Can you attach a "show run" from your GW here please ?

[wilsonsant]

Hi Guys,

Follow the configuration.

Thanks,

Wilson

[R0g22]

Per your config, your topology is -

CUCM >> H.323 >> GW >> E1 CAS >> ISP

What part are you planning to change ?

[wilsonsant]

Hi Nipun,

As I told previously my Customer need that H323 and SIP work in the same time. When SIP is validated the H323 will cancel with the Carrier. I have keep this configuration simultaneously.

Thanks,

Wilson

[R0g22 · Accepted solution]

Just a suggestion. You are not using H.323 with your carrier so you need to stop referencing it that way. This part has been causing confusion. H.323 to SIP change will be internal to your UC network and your Telco will not have visibility about this.

For SIP, you need to -
1. Create a SIP trunk on CUCM pointing to this GW
2. On the GW you would need to add SIP VoIP dial-peers. You can copy your existing VoIP dial-peers and create new ones with "session protocol sipv2" command added to them.
3. Depending upon whether you want to use SIP or H.323 at the moment, you can configured "preferences" on your dial-peers. The higher the preference, the least preferred a particular dial-peer will be.