Re: [SR-Users] Change in RTP Payload time on the fly - sr-users

19 Sep 2010

Hello,

Thank you for your comments.
My answers are inline.

...
  Hello,

 ptime and also the z flag are ms values, so a values of 6 or 8 ms are not
 the recommended length of time, it should be an integer
 multiple of 5 ms. I havn't yet a look the the source, but the nathelper
 doc
 say ZNN, maybe only the 12 is taken from your 120? 
The 'ZNN' in the documentation might be misleading, since I tried with
'Z120' and the variable 'requested_nsamples' is set to 960 samples
(120/10*80).
This variable is used by RTP resizer to resize the RTP packets.

...
  But in fact the doc confuse with ZNN and an example of
100ms. Could you
 try
 again with 90?

I tried with ptime=80ms and ptime=60ms.
But, I still have the similar results, i.e. I get occasional packets with
ptime=40 and sometimes ptime=20ms.

Regards,
Pranav Desai

...
  regards,
 Andreas

 2010/9/18 Pranav Desai &lt;pdesai(a)signalogic.com&gt;

 Hello,

 We have a proxy server setup that runs Kamailiov3.0.1 + RTPProxyv1.2.1.
 Nathelper support has been enabled in Kamailio.

 On a certain route, we call force_rtp_proxy("z120"), i.e. with resizing
 parameter 'z' and argument 120ms. During a call where endpoints have
 negotiated the use of G729, RTPProxy sends packets with ptime=12
 (120ms),
 however occasionally rtpproxy sends packets with ptime 6(60ms), 8(80ms),
 4(40ms).

 Under what circumstance would RTPProxy send packets with ptime < 12 ?

 Regards,
 Pranav Desai

 _______________________________________________
 SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
 sr-users(a)lists.sip-router.org
 http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users