rist2mpeg SIMPLE profile 'peer does not have an associated rtcp channel ignoring'
Trying to test with a listener for simple profile, however a RIST session is not correctly set up:
rist2mpeg -u udp://127.0.0.1:5555 -p 0 -s rist://@:5000 SIGEXIT(2) ↵ 10006 17:49:08
Configured with maxrate=100000 bufmin=1000 bufmax=1000 reorder=25 rttmin=50 rttmax=500 buffer_bloat=0 (limit:6, hardlimit:20)
1586274551.054333|140449386848272.0|0|[INIT] RIST Server Library v2.4.5
1586274551.054349|140449386848272.0|0|[INIT] Starting in server mode: rist://@:5000
1586274551.054355|140449386848272.0|0|[INIT] Processing default configuration values
[INIT] No hostname specified: listening to 0.0.0.01586274551.054375|140449386848272.0|0|[INFO] URL parsed successfully: Host , Port 5000
network: opening 0.0.0.0 datagram port 5000
1586274551.054413|140449386848272.0|0|[INIT] Starting in URL listening mode (socket# 3)
1586274551.054424|140449386848272.0|0|[INFO] Our cname is gijs-desktop
[INIT] No hostname specified: listening to 0.0.0.01586274551.054436|140449386848272.0|0|[INFO] URL parsed successfully: Host , Port 5001
network: opening 0.0.0.0 datagram port 5001
1586274551.054452|140449386848272.0|0|[INIT] Starting in URL listening mode (socket# 4)
1586274551.054458|140449386848272.0|0|[INFO] Our cname is gijs-desktop
1586274551.054463|140449386848272.0|0|[INFO] Created RTCP peer: host rist://@, port 5000, new_url rist://@:5001, 0
1586274551.054472|140449386848272.0|0|[INIT] Initialized Server Peer, listening mode ...
1586274551.054479|140449386848272.0|0|[INFO] Active Peer Information, IP:Port => 0.0.0.0:5001 (1), id: 0, ports: 5001->1969
1586274551.054487|140449386848272.0|0|[INIT] Initialized Server Peer, listening mode ...
1586274551.054492|140449386848272.0|0|[INFO] Active Peer Information, IP:Port => 0.0.0.0:5000 (1), id: 0, ports: 5000->1969
[INFO] URL parsed successfully: Host 127.0.0.1, Port 5555
Socket 1 is open
1586274551.054621|140449386848272.0|0|[INIT] Starting server protocol loop with 5 ms timer
1586274551.054949|140449386848272.0|0|[INIT] New RTCP peer connecting, flow_id 1562086818, peer_id 1, ports 5000<-1969
Peer has been authenticated, sending auth message: auth,192.168.88.134:12846,0.0.0.0:5000
1586274551.054974|0.0|1|Trying to send oob but oob was not enabled
1586274551.055518|140449386848272.0|0|[INFO] Peer with id #1 was configured with maxrate=100000/0 bufmin=1000 bufmax=1000 reorder=25 rttmin=50 rttmax=500 buffer_bloat=0 (limit:6, hardlimit:20)
1586274551.055539|140449386848272.0|0|[INIT] FLOW #1562086818 created
1586274551.055546|140449386848272.0|0|[INIT] Peer with id #1 associated with flow #1562086818
1586274551.055552|140449386848272.0|0|[INIT] Flow #1562086818 has now 1 peers.
1586274551.055602|140449386848272.0|2|[WARNING] Flow 1562086818 has not yet been authenticated by an RTCP peer!
1586274551.055609|140449386848272.0|2|[WARNING] Received data packet but this peer (1) does not have an associated rtcp channel, ignoring ...
1586274551.055616|140449386848272.0|0| [STATS]type=peerinstant,flowid=1562086818,dead=0,peer=1/1(1),received=0,missing=0,Q=100.00,recovered=0,n0=0,n1=0,n2=0,n3=0,n=0,n_avg=100,n_slope=0,n_inverted=0,reordered=0,dups=0,retries=0,recover_buffer_length=1000(ms),missing_queue_size=0/3571,rtt=0(us),avg_rtt=50(ms),bitrate=0(bps),avg_bitrate=0(bps)
1586274551.055609|140449386848272.0|0|[INFO] Starting data output thread with 5 ms max output jitter
1586274551.055638|140449386848272.0|0| [STATS]type=peertotal,flowid=1562086818,dead=0,peer=1/1(1),received=0,missing=0,Q=100.00,recovered=0,n0=0,n1=0,n2=0,n3=0,n=0,n_avg=12,n_slope=0,reordered=0,dups=0,retries=0
1586274551.055651|140449386848272.0|0| [STATS]type=flowinstant,flowid=1562086818,received=0,missing=0,Q=100.00,recovered=0,n0=0,n1=0,n2=0,n3=0,n=0,lost=0,reordered=0,dups=0,retries=0,min_ips=0,cur_ips=0,max_ips=0
1586274551.055662|140449386848272.0|0| [STATS]type=flowtotal,flowid=1562086818,received=0,missing=0,Q=100.00,recovered=0,n0=0,n1=0,n2=0,n3=0,n+=0,lost=0,reordered=0,dups=0,retries=0,min_ips=0,cur_ips=0,max_ips=0
1586274551.056105|140449386848272.0|2|[WARNING] Flow 1562086818 has not yet been authenticated by an RTCP peer!
1586274551.056111|140449386848272.0|2|[WARNING] Received data packet but this peer (1) does not have an associated rtcp channel, ignoring ...
1586274551.056687|140449386848272.0|2|[WARNING] Flow 1562086818 has not yet been authenticated by an RTCP peer!
1586274551.056693|140449386848272.0|2|[WARNING] Received data packet but this peer (1) does not have an associated rtcp channel, ignoring ...
1586274551.057271|140449386848272.0|2|[WARNING] Flow 1562086818 has not yet been authenticated by an RTCP peer!
1586274551.057277|140449386848272.0|2|[WARNING] Received data packet but this peer (1) does not have an associated rtcp channel, ignoring ...
1586274551.057852|140449386848272.0|2|[WARNING] Flow 1562086818 has not yet been authenticated by an RTCP peer!
1586274551.057858|140449386848272.0|2|[WARNING] Received data packet but this peer (1) does not have an associated rtcp channel, ignoring ...
1586274551.058438|140449386848272.0|2|[WARNING] Flow 1562086818 has not yet been authenticated by an RTCP peer!
1586274551.058443|140449386848272.0|2|[WARNING] Received data packet but this peer (1) does not have an associated rtcp channel, ignoring ...
1586274551.059022|140449386848272.0|2|[WARNING] Flow 1562086818 has not yet been authenticated by an RTCP peer!
1586274551.059028|140449386848272.0|2|[WARNING] Received data packet but this peer (1) does not have an associated rtcp channel, ignoring ...
Edited by Gijs Peskens