[cisco-voip] Antw: Re: Ringback stops after first ring

[Ryan West]

Robert,

Thanks for the info.  It seems that the 6.1.2(1106-1) ES fixes the bug.

Thanks,

-ryan

-----Original Message-----
From: Robert Schuknecht [mailto:rschuknecht at gmx.de]
Sent: Friday, September 12, 2008 4:05 AM
To: cisco-voip at puck.nether.net; Ryan West
Subject: Antw: Re: [cisco-voip] Ringback stops after first ring

Hi Ryan,

you should find the timer "DelayBeforeRinging" in the Menu "Device" -> "Remote Destinations".

HTH

/Robert

>>> Ryan West<rwest at zyedge.com> schrieb am Freitag, 12. September 2008 um 03:58 in
Nachricht fd2e41255bc65bc6bab0348176f8e7c2:
> I found a bug ID (CSCsq67485) that seems to be what we're hitting.  I have
> tried moving "Send Progress Timer" to 6000 from 3000, but it does not appear
> to be helping.  Here are the details:
>
> No ringback tone for SNR calls incoming through the H323 gateway Symptom:
>
> Callers get no ringtone when SNR users with their deskphones/ softphones
> unregisterd with Callmanager.
>
> Conditions:
>
> Noticed with Incoming calls through H.323 gateways only.
>
>
> Workaround:
>
> Make sure to set the service parameter "Send Progress Timer" to 1 sec more
> than DelayBeforeRinging Timer
>
> If H323 ICT is used, this "Send progress Timer" should be adjusted to 1 sec
> more than DelayBeforeRinging Timer in clusters in the call path
>
>
> Where can I find the DelayBeforeRinging Timer.  I don't see anything in the
> service parameters for this.
>
> -ryan
>
> From: cisco-voip-bounces at puck.nether.net
> [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Ryan West
> Sent: Thursday, September 11, 2008 9:13 PM
> To: cisco-voip at puck.nether.net
> Subject: [cisco-voip] Ringback stops after first ring
>
> Inbound calls to users with remote destination profiles enabled, to ring a
> cell phone etc.., only get the first ringback and then dead air.  We have
> received several complaints about this issue and I have experienced myself
> when calling several SE's within Cisco.  It seems this happens when the voice
> gateway is H323.  Has anyone come across a fix for this?
>
> Thanks,
>
> -ryan