CUCM 4.2 integ with SIP Provider

[SJ SJ]

I have terminated a SIP trunk on the voice gateway and configured it as CUBE. What configuration is required at Call manger 4.2 ? 

Regards

[Jaime Valencia]

An h323 or SIP trunk to your CUBE, bear in mind that the SIP capabilities on 4.x were a lot more limited to those of current releases.

[SJ SJ]

Can we use the existing H323 gateway in CUCM 4.2 and Create SIP dial peers with the ITSP.

If yes will it require any additional resoures.

[Chris Deren]

Sure, you will need to allow sip to h323 connections under voip service.

Chris

[SJ SJ]

I've created a route pattern in CUCM 4.2 with wildcard 7!. This is pointing to a route list with H323 gateway. 

On the gateway i've created a dial peer :

dial-peer voice 40 voip

description **Outgoing Call to SIP Trunk

destination-pattern 7.T

session protocol sipv2

session target ipv4: 1.1.1.1

dtmf-relay rtp-nte sip-notify h245-alphanumeric

codec g711ulaw

no vad

----------- Is it enough to match the sip voip dial peer on gateway.

[Jaime Valencia]

Yes, assuming that´s what your telco is expecting to receive.

Try placing a call, if it doesn´t work, enable debugs to look at the failure cause.