SAT>IP issues

[KayDiefenthal]

Hi Sub

Great to see see the Update
so can i Report it in the public

to SSDP
send 3x M-Search Messages!
second you should use MX: 2

send it not to Broadcast (Broadcast is 255.255.255.255 )
you must send it to 239.255.255.0:1900

as exsampe https://sourceforge.net/p/satip/code/HEA...pClient.cs

UnicastReceivecallback (Http Response) gives you that what you Need to create the capture
MulticastReceivecallback (M-Search Response || Notify Response)is only needed if you want react if the Sat>Ip Device Connection is lost so stopp demux and or Switch to other Sat>Ip Device

[KayDiefenthal]

sorry there was an typo it must be
you must send it to 239.255.255.250:1900

3.3.4 Client Search Requests
http://www.satip.info/sites/satip/files/..._1_2_2.pdf

[ATTACHMENT NOT FOUND]

here can you see the Problem the Triax Tss 400 isnt discovered in NextPvr but in my tool

[KayDiefenthal]

all Problems should be solved

Triax Tss 400 ,Telestar Digibit R1 and Digital Devices OctopusNet Sat>Ip Servers get now discoverd
Service Scan working too

[sub]

Thanks again for the help debugging the issues with using the Triax and OctopusNet devices. I've updated the installer to include that most recent patch.

[KayDiefenthal]

nothing to thanx you know that i want help you with that

on code or test side

but you want the man over the code to be so is for me only the Report and testing part possible but we had it fixed