11-16-2010 07:39 AM - edited 03-16-2019 01:57 AM
Hi everyone,
In a new instalation, configured on the CUCM version 7.1 a H323 gateway to another vendors voice network. It's working ok in terms of everything except for the NO RINGBACK when calling from a Cisco IP phone to any destination through the H323 Gateway. It works fine the other way around.
Already been here:
http://www.cisco.com/en/US/tech/tk1077/technologies_tech_note09186a0080094c33.shtml
And configured the ToSendH225UserInfoMsg - Use ANN for Ring Back
...still not working.
Any ideas?
Thanks,
Francisco
11-16-2010 09:53 AM
Hi Francisco,
Could you just confirm that you have configured the following parameters on the voice dial-peers on your H323 gateway?
tone ringback alert-no-PI
progress_ind alert enable 8
progress_ind progress enable 8
progress_ind connect enable 8
It should force the gateway to generate the ringback locally.
Regards,
Nick
11-17-2010 01:08 AM
Hi Nick,
The H323 Gateway is not a cisco IOS Gateway. I configured it being the other vendors phone gateway IP address and i have no access to it's configuration.
Thanks
11-17-2010 02:05 AM
Are you sure that CUCM get the alerting message? It could explain why there is no ringback.
By looking in the SDI traces of the callmanager service, you should see this message from the gateway.
Otherwise, you may want to look on the gateway debugs.
11-17-2010 06:12 AM
11-17-2010 06:59 AM
It seems indeed that we receive an alerting here:
11/16/2010 12:56:09.925 CCM|In Message -- H225AlertMsg -- Protocol= H225Protocol|<:STANDALONECLUSTER><:10.227.32.130><:SIGNIFICANT><:0040>
11-17-2010 07:21 AM
Francisco,
The h323 gateway is sending it's h245 address in the h225 Alerting Message. This causes CUCM to negotiate the media stream. You'll need to go back and check with the provider to see if they deliver ringback tone inband. If they don't, then they need to remove the h245 address from the Alerting message so that the CUCM tells the phone to play ringback locally.
-Felipe
Excerpt from CUCM traces:
11/16/2010 13:15:00.327 CCM|{
h323-uu-pdu
{
h323-message-body alerting :
{
protocolIdentifier { 0 0 8 2250 0 2 },
destinationInfo
{
vendor
{
vendor
{
t35CountryCode 61,
t35Extension 0,
manufacturerCode 1010
},
productId '416C636174656C204F6D6E695043583434 ...'H,
versionId '31342E32352020'H
},
mc FALSE,
undefinedNode FALSE
},
h245Address ipAddress :
{
ip '0AFA6045'H,
port 31000
},
callIdentifier
{
guid '80FFE420C47521CE05001B020AE3210D'H
}
},
h245Tunneling FALSE
}|<:STANDALONECLUSTER><:10.227.32.130><:STATE transition=""><:0100>
11-18-2010 03:19 AM
Thanks Felipe,
Do you know if there's anyway to configure on the CallManager side to ignore that IP information or to force it to play the ringback locally?
Regards,
Francisco
11-18-2010 07:03 AM
I'm not aware of a method in CUCM to do it. Can you check on the h323 gateway/PBX?
-Felipe
02-09-2014 11:19 PM
Hi All
I got the same issue, i have resolved this by enabling Outbound FastStart on H323 GW.
Regds
$
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