11-15-2010 10:03 AM - edited 03-16-2019 01:56 AM
Hi Guys,
I am experiencing a strange problem that I need assistance with.
I have a QSIG connection on an H323 gateway that links to a 3rd party CUCM. When I call a phone on their side both parties names display on each phone, however when the 3rd party calls me I can see their name, but they cannot see mine.
I have run a debug isdn q931 when the 3rd party calls me and can see the facility i message being sent to me (I see the calling party name), but I am not sending a facility i message back to them. I have gone through the config on the CuCM (7.1) and have made sure that the IE Delivery options at the gateway level and the route pattern level are all allowed.
Any ideas will be greatly appreciated.
Cheers,
Phil
11-15-2010 05:44 PM
Hi Phil,
It would be helpful if you could provide the topology & config for the h323 gateway here.
does it connect this way Phone<->PBX<->QSIG<->H323 GW<->CUCM<->IP Phone ?
probably what you need are these two commands:
h225 display-ie ccm-compatible
isdn supp-service name calling
Read more here:
11-16-2010 03:30 AM
HI Alex,
Configuration is as follows Phone <>CUCM<>H323 GW<>QSIG<>MGCP GW<>CUCM<>Phone
I'll try the commands you suggested and let you know how I get on.
Cheers,
Phil
11-16-2010 07:25 AM
Hi Alex,
I added both commands that you suggested, but it didn't work. Below is a debug isdn q931 from my gateway when the 3rd party calls me. As you can see I receive a Facility i message, but I do not send one back hence the calling name not being sent:
009280: Nov 16 15:16:52.205 GMT: ISDN Se0/1/1:15 Q931: RX <- SETUP pd = 8 callref = 0x0009
Sending Complete
Bearer Capability i = 0x8090A3
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA9839F
Exclusive, Channel 31
Facility i = 0x9FAA06800100820100A11C020100060528EC2C00008010436872697320537479637A796E736B69
Calling Party Number i = 0x0081, '1471'
Plan:Unknown, Type:Unknown
Called Party Number i = 0x80, '2955'
Plan:Unknown, Type:Unknown
009281: Nov 16 15:16:52.205 GMT: ISDN Se0/1/1:15 **ERROR**: isdn_init_fac_data: No Opval 0
009282: Nov 16 15:16:52.205 GMT: ISDN Se0/1/1:15 **ERROR**: isdn_init_fac_data: No Opval 0
009283: Nov 16 15:16:52.217 GMT: ISDN Se0/1/1:15 Q931: TX -> CALL_PROC pd = 8 callref = 0x8009
Channel ID i = 0xA9839F
Exclusive, Channel 31
009284: Nov 16 15:16:52.333 GMT: ISDN Se0/1/1:15 Q931: TX -> ALERTING pd = 8 callref = 0x8009
Progress Ind i = 0x8188 - In-band info or appropriate now available
009285: Nov 16 15:16:55.473 GMT: %ISDN-6-CONNECT: Interface Serial0/1/1:30 is now connected to 1471 N/A
Interestingly I do get some new errors that I didn't get before - 009281: Nov 16 15:16:52.205 GMT: ISDN Se0/1/1:15 **ERROR**: isdn_init_fac_data: No Opval 0
Could this be a H323 - MGCP compatibility issue?
Phil
11-17-2010 07:13 PM
Hi Phil,
Can you verify that, the gateway setting on ur cucm have "Display IE Delivery" options checked?
whereas for the 3party cucm, please verify is the "Display IE delivery" options checked
on the MGCP gateway.
reason for this is due name display information delivered in an H.323 Facility message is not
interpreted by CUCM, and by enable that option, it will send the calling name in display IE
instead of Facility IE.
by the way, how is the qsig is configured? which side is network? you might need the commands
"isdn supp-service name calling" & "isdn outgoing display-ie" under your interface config
i don't think that is H323-MGCP compatibility issue, however i might be wrong.
let try this and see is this helps.
Alex
11-18-2010 07:21 AM
Hi Alex,
I meant to say I think it is a H323-QSIG compaibility issue.
I can confirm that all IE Delivery options are ticked, or allowed at the gateway and route pattern level on both CUCMs.
The network side for the QSIG is on the MGCP GW.
I have put all of the suggested commands on the interface and I still get the same result. I may have to convert the gateway to MGCP to see if I can get it resolved that way.
Phil
11-24-2010 02:35 AM
Hi Guys,
I thought i'd let you know that the problem was solved by converting the GW from H323 to MGCP.
It's worth bearing in mind if you're thinking of using H323 with QSIG links.
Cheers,
Phil
11-25-2010 06:56 PM
Hi Phil,
Thanks for updating us on this and glad that you solved it.
I believe calling name over h323 & qsig is achievable, will do a
test lab for this if possible.
Cheers,
Alex
05-05-2011 08:12 AM
Hi Alex
Did test this as I`m having the same issue with H323 and Qsig?
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