|Summary:||ASTERISK-01276: CVS-HEAD rtp issues cause choppy audio! We are working on it! :)|
|Date Opened:||2004-03-23 05:32:07.000-0600||Date Closed:||2011-06-07 14:05:20|
|Description:||When upgrading to the newest CVS we get choppy sound on our Snom105 and Snom200 Phones when Dialling to ISDN oder get called from ISDN. The ISDN caller has no sound choppiness, that means the problem is only sip->isdn. We use the newest chan_chapi from junghanns.net (0.3.1).|
To trackdown the problem we tried several codecs and packet sizes, with no or minimal impact. It seems more that the grade of choppiness is more or less random.
For sure it work again clearly on booth sides with a cvs downgrade to 1 month ago.
|Comments:||By: Brian West (bkw918) 2004-03-23 14:15:36.000-0600|
Yes this is already reported its an issue in rtp and has more than one bug open on this very same issue.
By: togg (togg) 2004-03-23 14:18:40.000-0600
Good to know, i just wanted to ensure it doesnt gets overseen :-)
By: Mark Spencer (markster) 2004-03-23 18:34:53.000-0600
Is it only when going to ISDN? Have you recompiled it?
By: togg (togg) 2004-03-24 01:15:16.000-0600
We dont use other channels than chan_sip (or chan_sip2) and chan_capi.
I recompiled the complete package, also the chan_capi. Since we depend on the asterisk-functionality (obscure enough I use the newest cvs, I know ;) I had not
much time testing the parameters on which quality is better oder badder. But from my few tests it seems that a connection with less traffic on the line (Ethernet line!) produces less choppy sound.
SIP->SIP is really no problem at all for us. SIP->CAPI or CAPI->SIP makes choppy sound.
By: Mark Spencer (markster) 2004-03-27 13:26:59.000-0600
The CAPI->SIP issue should be fixed in chan_capi version 0.3.2
By: rburkholder (rburkholder) 2004-03-27 21:19:20.000-0600
Perhaps the change in 1312 may fix this.
By: Mark Spencer (markster) 2004-03-31 15:04:13.000-0600
Can you confirm that chan_capi version 0.3.2 fixes the problem?
By: togg (togg) 2004-03-31 17:36:57.000-0600
where do you got chan_capi 0.3.2? on http://www.junghanns.net/asterisk/ I only see 0.3.1.
By: Mark Spencer (markster) 2004-04-02 02:14:31.000-0600
I don't know, that's just what kapejod told me.
By: Mark Spencer (markster) 2004-04-03 20:27:18.000-0600
Well, in any case this is a chan_capi issue, so I guess it needs to be taken up with kapejod. I'm going to go ahead and close this one out, although I can tell you that the fix just involves setting the delivery field (delivery.tv_sec, delivery.tv_usec) to zero in chan_capi in the read routine.