After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 761807 - rtp session: (depending on where installed) "on-ssrc-active"/"on-bye-ssrc" signals are (or not) called although RTP/RTCP stream exists
rtp session: (depending on where installed) "on-ssrc-active"/"on-bye-ssrc" si...
Status: RESOLVED INVALID
Product: GStreamer
Classification: Platform
Component: gst-plugins-good
1.6.2
Other Windows
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2016-02-10 08:04 UTC by Mikel
Modified: 2016-02-17 09:56 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Mikel 2016-02-10 08:04:01 UTC
We have developed in Windows a RTP/RTCP stream (from A to B, and from B to A). The stream works correctly in 2 sockets (one for RTP, another one for RTCP) between 2 differents probes.
To calculate the statistics we extract the data once the signals "on-ssrc-active"/"on-bye-ssrc" signal are called (when we have RTCP traffic), we obtain the session with "get-internal-session" signal, the ssrc from  "get-source-by-ssrc", and finally the statistics with "stats" signal.
We have succesfully tested the development in our laboratory, and in another environment.
But in another one, although we have the RTP/RTCP streams in both directions, the "on-ssrc-active"/"on-bye-ssrc" are not called, and we don´t calculate the stats.
Has anyone had this problem? 
Can the RTP stream statistics be calculated in another way?
Comment 1 Sebastian Dröge (slomo) 2016-02-16 15:46:51 UTC
Can you provide a testcase to show this behaviour?
Comment 2 Mikel 2016-02-17 09:36:50 UTC
We have resolved this problem yesterday. 
The problem was not in gstreamer development. Instead, it was in sdp previous negotiation.
The RTP/RTCP stream occurs after a session negotiation, with sdp parameters exchanged in SIP INVITE and UPDATE commands.
When "RS" and "RR" parameters were set to "0", RTCP packets worked OK (sent and received) for most telco operators. But in another Telco operators RTCP packets were sent (but not received). If RTCP packets were not received, the signals "on-ssrc-active"/"on-bye-ssrc" were not executed.
After setting these sdp parameters to correct values, it has worked correctly.
Thanks.