The 256byte RTP payload is too large! Standard ULAW RTP w/ ptime 20ms should be 160bytes

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Start wireshark packet capture
2. Make call
3. View RTP packets in Wireshark

What is the expected output?
160byte RTP payload
What do you see instead?
256byte RTP payload

What version of the product are you using?
It has versions? I think it's R2... I just downloaded the sip.zip file.

On what operating system?
64bit Debian Linux

Please provide any additional information below.

Many SIP devices do not accept 256byte payloads.

Original issue reported on code.google.com by jgarl...@gmail.com on 7 Jan 2009 at 3:34

[GoogleCodeExporter]

RTP timestamps aren't incrementing properly either.

I tried setting audio_frame_size=160 in sip.cfg and I get a 160byte payload, 
and then
a 96byte payload, 160, then 96, 160, then 96, etc....

I also noticed that the timestamps increment on the RTP packets are NOT 
anywhere near
correct.

Original comment by jgarl...@gmail.com on 7 Jan 2009 at 4:33

[GoogleCodeExporter]

Time stamps should increment by steps of 256 instead of 32... its samples not 
milliseconds. 

Best case is to buffer the audio and send 160 byte payloads and increment the 
time stamp by 160 also. 

/b

Original comment by brian.w...@gmail.com on 7 Jan 2009 at 5:10

[GoogleCodeExporter]

have you tried this parmater in sip.cfg
audio_frame_size=160

in Openfire project i managed to change RTP frame siaze using this paramter

Original comment by lior.her...@gmail.com on 7 Feb 2009 at 6:23