This document was generated from CDN thread
Created by: Sergei Gorbunov on 04-07-2011 05:53:52 AM
Good day!
I am trying to record a sound via CCM recordig feature. My recorder app works fine, but sometimes recorder recieves very very strange packets:
1. Recording sound from local device to IVR call. This befaviour reproduced very well. Recording device send valid RTP packets, but last packet looks like this:
prev packet: Version=2 Padding=0 Extension=0 CC=0 Marker=0 Payload=0 Seq=7913 Timestamp=179312 SS=2188969425
last packets: Version=2 Padding=0 Extension=0 CC=0 Marker=1 Payload=0 Seq=7914 Timestamp=3059456 SS=2188969425
As you can see last packet tells us (as i can understand from RFC) that my app need to generate a silence for about 6 minutes. But call length is about 30 seconds! This is sure wrong packets.
2. Recording sound from local to local device call. This behaviour is hard to reproduce, but sometimes this happens. This packets is from middle of call recording:
Packet: Version=2 Padding=0 Extension=0 CC=0 Marker=0 Payload=0 Seq=63100 Timestamp=468315742 SS=1247720682
Packet: Version=2 Padding=0 Extension=0 CC=0 Marker=1 Payload=0 Seq=63101 Timestamp=3488670291 SS=1247720682
Packet: Version=2 Padding=0 Extension=0 CC=0 Marker=0 Payload=0 Seq=63102 Timestamp=3488670451 SS=1247720682
The same thing happens i think... but in the middle of recording, not a last packet. I am confused with this behaviour and dont understand what can i do with that... Now i can only close my eyes on timestamp when it changes so much.
Can anyone tell me what happens there? Any suggestions will be appreciated.
Thanks for advance!
Subject: RE: Wrong timestamps in recorded rtp packets
Replied by: Alexander Anoshin on 27-07-2011 12:55:11 AM
This bug solved in firmware 9.1.1 and above