Hello, First, I know this isn't the libSRTP mailing list. But, that mailing list seems to be currently unoccupied so I'm giving this a shot here.
We've noticed a problem whereby an SRTP session cannot be decoded after 22 minutes. The scenario goes like this: 1) An SRTP call is established using SIP+TLS 2) 22 minutes passes 3) The sender changes SSRC 4) The receiver is no longer able to decode the session During stage #2, it looks like some internal variables in libSRTP "roll over" the magic mark of 65535 (according to the SRTP standard, the ROC should be incremented). But after this, the sender switches SSRC and the whole thing just goes down the tubes. I was wondering if anyone else here ran into a similar problem (knowing that this list is populated with people writing soft phones), and if so, did you find a fix and/or workaround? -- David Stuart, CounterPath Email: dstuart (at) counterpath (dot) com Phone: (613) 254-8886 x2234 Web: http://www.counterpath.com/ Address: 310 - 350 Terry Fox Drive, Kanata Ontario, K2K 2P5 _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
