Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

failure when RTP sequence number switches from 65535 -> 0 #29

Closed
dziny opened this issue Jun 24, 2013 · 6 comments
Closed

failure when RTP sequence number switches from 65535 -> 0 #29

dziny opened this issue Jun 24, 2013 · 6 comments

Comments

@dziny
Copy link

dziny commented Jun 24, 2013

See here https://issues.asterisk.org/jira/browse/ASTERISK-16898
This issue still exists and the claim is that it is caused by libsrtp. In my case I'm using the latest wheezy libsrtp 1.4.4+20100615~dfsg-2 on i386. As described in the link above there is a loss of audio on average around 10 min mark (depending on the initial sequence number) with Nokia phones <-> Asterisk that uses libsrtp. The audio is lost one way, the Nokia still receives and plays audio but Asterisk rejects incoming SRTP packets.
Can this be fixed in your release? Thanks.

@jfigus
Copy link
Contributor

jfigus commented Jul 23, 2013

There isn't much detail in the asterisk bug report on this. The one comment about TLS and 3DES is a bit confusing since libsrtp supports neither of these. Perhaps the problem is in Asterisk.

Given the limited information in the bug report, this looks like the roll-over counter (ROC) logic isn't working. If the ROC were broken in libsrtp, it's difficult to imagine that nobody else would have experienced the same problem.

@marcelloceschia
Copy link

@jfigus this issue depens on the client implementation of srtp.
E.g. all nokia s60 devices have this issue and it is 100% reproducible with this devices.
Some nokia s40 phones with do not have this issue, but newer nokia phones do also have.
I saw this issue on some other devices too, but do not know the exact device model at the moment.

@franko-franicevich
Copy link

Just as an FYI, my test suite using libsrtp has one test that does 1 million encode/decodes on the same stream, which obviously causes the sequence number to roll over around 16 times - This always succeeds... Implies the issue is not in libsrtp. Maybe the nokia phones are doing something nonstandard (but not forbidden by RTP) like changing the ssrc when the sequence number rolls over - I've seen similar oddities in the past, and that would certainly cause decryption to break.

@marcelloceschia
Copy link

Alexander Traud (@traud) did some patches to fix this issue (see: https://issues.asterisk.org/jira/browse/ASTERISK-16898).
At the moment I did not had the time to test the patches, but I will report the result after some tests.

@dziny
Copy link
Author

dziny commented Oct 4, 2014

I have tested the patch with Nokia E66. I had to modify the recognition string in the asterisk patch since the E66 uses "E66-1 RM-343 510.21.009".
But the patch does work and fixes the issue.

@jfigus jfigus added the wontfix label Oct 8, 2014
@jfigus
Copy link
Contributor

jfigus commented Oct 8, 2014

Closing this since there are no plans to patch libsrtp.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants