I did some more investigation on this topic I didn't solve it yet but I would like to share with you what I discovered. I implement a splitcomb and master clock to have a rtp packet produced at regular interval (ie each 20ms in my case) and this is working perfectly. I even trace the time the udp packet are sent (sys_sendto) and it is sent as expected. But on the router and even sniffing the wifi traffic in promiscuous mode in can see it is not the case. On mobile phone running Android 4.1/4.2 I use to see 2 packets sent in the same Ms each 40ms. Using Android 4.4 the situation is worst at the beginning it is send as in 4.1/4.2 but after a while I have 6 packets in a burst afetr 120ms. This is not acceptable for the network I'm integrating. Could it be due to the process priority on Android which is downgraded? Some IO problem? Some internal OS thread scheduling on the IO? Any hint? Fran?ois On Wed, Nov 5, 2014 at 6:46 PM, Francois Goffin <francois.goffin at gmail.com> wrote: > Hi, > I'm using your library in a project called CSipSimple and I'm having > some troubles. I would like to know if you already experience this and may > have a solution. > The problem I have is that it looks the android devices send the RTP > packet by burst. Even if with ptime set to 20ms, on our test device(Samsung > S5/Sony Z2) I can see X packets sent in the same ms each X*20ms. It looks > that this is creating an issue on the border gateway that introduce some > comfort noise. As a result on the end the voice is not good at all (MOS > rated to 2). > Thanks in advance for your help. > > Fran?ois > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20141110/e3c6aeee/attachment.html>
