CME SIP calls forward to CallManager?

jrossouw · ‎03-04-2007

I'm running CME 3.3 on a 1760 gateway with IOS 12.4(8). This gateway is registered to an external SIP registrar. Making and receiving calls while using a phone registered to CME works OK. Further to this I have CCM 4.2(3) configured with a SIP trunk pointing to this gateway for outbound calls. This works very well outbound, although I have a problem with passing inbound calls from the CME box to CCM. I have attached the config on my gateway and a debug of the dial-peers. As you can see the call does hit the gateway but does not pass it on to Callmanager. Does anyone know how to overcome this problem either by sending the call via SIP or H.323 to callmanager?

###########################

!

dial-peer voice 1 voip

description SIP_Outbound

destination-pattern .T

voice-class codec 1

session protocol sipv2

session target sip-server

session transport udp

incoming called-number .T

dtmf-relay rtp-nte

no vad

!

dial-peer voice 2 pots

incoming called-number 843408

direct-inward-dial

!

dial-peer voice 3 voip

destination-pattern 843408

session target ipv4:192.168.40.6

!

sip-ua

authentication username 843408 password XXXXXX

no remote-party-id

retry invite 3

retry register 3

registrar dns:draytel.org expires 3600

sip-server dns:draytel.org

!

telephony-service

max-ephones 1

max-dn 100

max-conferences 4 gain -6

!

ephone-dn 100

number 843408

name draytel

!

##########################

router#debug voip dialpeer

voip dialpeer default debugging is on

Mar 4 19:56:17.170: //-1/3FAB43C380EE/DPM/dpAssociateIncomingPeerCore:

Calling Number=07748780355, Called Number=843408, Voice-Interface=0x0,

Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,

Peer Info Type=DIALPEER_INFO_SPEECH

Mar 4 19:56:17.170: //-1/3FAB43C380EE/DPM/dpAssociateIncomingPeerCore:

Result=Success(0) after DP_MATCH_INCOMING_DNIS; Incoming Dial-peer=1

Mar 4 19:56:17.186: //-1/3FAB43C380EE/DPM/dpMatchPeersCore:

Calling Number=, Called Number=843408, Peer Info Type=DIALPEER_INFO_SPEECH

Mar 4 19:56:17.186: //-1/3FAB43C380EE/DPM/dpMatchPeersCore:

Match Rule=DP_MATCH_DEST; Called Number=843408

Mar 4 19:56:17.186: //-1/3FAB43C380EE/DPM/dpMatchPeersCore:

Result=Success(0) after DP_MATCH_DEST

Mar 4 19:56:17.190: //-1/3FAB43C380EE/DPM/dpMatchPeersMoreArg:

Result=SUCCESS(0)

List of Matched Outgoing Dial-peer(s):

1: Dial-peer Tag=20001

2: Dial-peer Tag=3

3: Dial-peer Tag=1

router#

##########################

router#sh dial-peer voice sum

dial-peer hunt 0

AD PRE PASS OUT

TAG TYPE MIN OPER PREFIX DEST-PATTERN FER THRU SESS-TARGET STAT PORT

1 voip up up .T 0 syst sip-server

20001 pots up up 843408$ 0 50/0/100

2 pots up up 0 down

3 voip up up 843408 0 syst ipv4:192.168.40.6

##########################

paolo bevilacqua · ‎03-04-2007

Hi,

I think that if you want to route SIP incoming calls to CCM, again with sip or H.323, you may need an IP-to-IP gateway image, that is not available for the 1760.

jrossouw · ‎03-04-2007

Thanks for that. I take it something like the 2800 series would support that? Could you supply me with the necessary config to achieve this?

paolo bevilacqua · ‎03-04-2007

Under "voice service voip", you will have "allow-connections sip to sip" or "sip to h.323" as necessary.

Under "dial-peer", you will have "codec transparent", unless you are doing transcoding, that requires additional configuration of dspfarm service.

That is basically. Then "debug ccsip message" is your friend to see how the box is talking to the other elements.

You may want to give it a try using a recent 12.4T image even using the current 1760, let us know how it goes.

Please remember to rate useful posts!

paolo bevilacqua · ‎03-04-2007

Thank you for the reduced ranking given to my suggestions, I will try to commensurate with an equal level of support to your future questions.