08-02-2013 02:48 AM - edited 03-16-2019 06:40 PM
I have CUCM 8.0.3 and CME 9.1 on Cisco 2951 ISR.
I've added 2951 as H.323 Gateway to CUCM.
Calls, routing, dial-pears etc are fine.
Problem is:
I can't put on hold or tranfer of create a conference for a call between CME and CUCM.
I've cheked same operations between phones registered to CME - they work.
Explaine me pleaze why does it happen? What have I missed?
08-02-2013 04:54 AM
The CME SRND has an entire chapter on this sort of mess which you can avoid by using SIP instead of H.323. The problem comes down to differences in how CUCM and CME perform transfer and conference operations with H.323. If you're determined for this to happen over H.323 we'll need to know the CME configuration as well as the exact call scenario you're trying. Walk us through it step-by-step.
Please remember to rate helpful responses and identify helpful or correct answers.
08-07-2013 02:46 AM
Now I'll try to walk you as you asked.
Phones registered on CME.
Here is config:
voice service voip
.....
telephony-service
max-ephones 165
max-dn 300
ip source-address 10.38.255.255 port 2000
user-locale RU
network-locale RU
load 6921 SCCP69xx.9-2-4-3.loads
load 8941 SCCP8941_8945.9-3-2-11
time-format 24
date-format dd-mm-yy
max-conferences 8 gain -6
transfer-system full-consult
transfer-pattern T
.....
ephone-dn 200
number 1600
name Alexey Martyschenko
ephone 200
device-security-mode none
mac-address E05F.B9C4.6759
button 1:200
ephone-200[199] Mac:E05F.B9C4.6759 TCP socket:[33] activeLine:0 whisperLine:0 REGISTERED in SCCP ver 15/12 max_streams=1
mediaActive:0 whisper_mediaActive:0 startMedia:0 offhook:0 ringing:0 reset:0 reset_sent:0 paging 0 debug:0 caps:8
IP:10.20.8.18 * 35892 6921 keepalive 236 max_line 2 available_line 2
button 1: cw:1 ccw:(0)
dn 200 number 1600 CH1 IDLE
Preferred Codec: g711ulaw
Lpcor Type: none
08-07-2013 03:01 AM
CME connects to HQ CUCM 8.0 via DMVPN channels from this interface
interface GigabitEthernet0/2.300
description -= WAN HQ =-
encapsulation dot1Q 300
ip address 10.38.0.50 255.255.255.248
ip ospf priority 255
h323-gateway voip interface
h323-gateway voip bind srcaddr 10.38.0.50
Here is dialpeer
dial-peer voice 101 voip
description -= Ent Telephony | HQ CUCM1 =-
destination-pattern 8......
session target ipv4:10.20.8.5
dtmf-relay h245-alphanumeric
On the side of CUCM H.323 is added
08-07-2013 03:14 AM
Kiev_DP has
CMGroup2 has CallManagers:
1. CM_10.20.8.5
2. CM_10.20.8.6
dpg_cme_CSS leads to Dneprog_PT
There are Translations in Dneprogor_PT:
8xxxxxx is adding 8+officecode to Calling party (Output for my phone will be 8561600) and keep searching in Interoffice_PT.
Translations in Inteoffice_PT:
8
In these translations 8+officecode is removed from Called party and sent to corresponding PT.
08-02-2013 06:25 AM
The first place to start is to disable h450.2 and h450.3 on your CCME because as Jonathan pointed out, CCM and CCME perform transfer using seperate methods. CCME uses h450.2 while cucm doesnt support this.
conf t
voice service voip
supplementary-service h450.12
When you enable h450.12, it automatically disables h450.2 and .3 and only enabled them when the far end endpoint supports them..
Try that and let us know
Please rate all useful posts
"opportunity is a haughty goddess who waste no time with those who are unprepared"
08-07-2013 02:30 AM
Sorry for pause after your replies. I'm in business trip.
Now I've tried to do what you recommended.
voice service voip
allow-connections h323 to h323
allow-connections h323 to sip
allow-connections sip to h323
allow-connections sip to sip
supplementary-service h450.12
fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback none
It's pity but no result. Transfer,hold buttons don't work.
I understood that the problem could be in H.450.x protocol, but I don't know how to use it.
08-07-2013 02:39 AM
I've decided to do it via sip
This is usual dialpeer:
dial-peer voice 101 voip
description -= Ent Telephony | HQ CUCM1 =-
destination-pattern 8......
session target ipv4:10.20.8.5
dtmf-relay h245-alphanumeric
I've added dialpeer exclusive for my number and make it via sip:
dial-peer voice 8441100 voip
destination-pattern 8441100
session protocol sipv2
session target ipv4:10.20.8.5
And via sip it works.
09-18-2014 07:30 AM
You need to configure MTP because H.323 does not support Hold/Transfer and that's where you need MTP resources to support.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide