Opened 11 years ago

Closed 9 years ago

#8767 closed Patch - Bug Fix (fixed)

Problem with rtp sources

Reported by: Octavio Ascanio <oascanio@…> Owned by: stuartm
Priority: minor Milestone: 0.25
Component: MythTV - Recording Version: Master Head
Severity: low Keywords: rtp problem
Cc: Ticket locked: no


I have a problem with mythtv receiving rtp sources. I have found comparing the sources of iptvfeederudp.cpp and iptvfeederrtp.cpp (my provider has changed from udp to rtp) that iptvfeederrtp::Open needs the next line:

ReceivingSocketAddr? = our_inet_addr(;

Just previous to Groupsock *socket = new Groupsock(*_live_env, addr, parse.port(), 0);

Without this line my backend machine does not receive the network stream. My machine has three network adapters with one dedicated to iptv. The default route is in the ppp0 interface. I don't know if this is causing receiving problems when ReceivingSocketAddr? has the ANY values....

Please, can you check it?

Change History (4)

comment:1 Changed 11 years ago by robertm

Component: MythTV - GeneralMythTV - Recording
Owner: set to danielk
Status: newassigned

comment:2 Changed 9 years ago by stuartm

Milestone: unknown0.25
Type: defectPatch - Bug Fix

Based on the description this looks like a one-line copy/paste error in iptvfeederrtp that shouldn't take more than a couple of minutes to verify and fix. I don't know the iptv code at all however so I'm leaving it to Daniel.

comment:3 Changed 9 years ago by danielk

Owner: changed from danielk to stuartm

Stuart, feel free to fix & verify. I'm planning on ripping out all the existing IPTV code and replacing it with a completely new implementation from the rtp branch in 0.26.

comment:4 Changed 9 years ago by Github

Resolution: fixed
Status: assignedclosed

Fix RTP IPTV with multiple IPTV interfaces. 1ed419ad applied a fix for udp IPTV where more than one interface was available, it didn't apply the fix for rtp which uses the same socket code. Fixes #8767, Refs #3873

Branch: master Changeset: 37cacb609357d785145f0f1a463d627feb6852f5

Note: See TracTickets for help on using tickets.