It seems that NOTIFY request is sent to the same adres where the M-SEARCH request came from. For some implementation of UPnP for Android it works. But on Windows it doesn't. The request has to be sent to 239.255.255.250:1900
Here we get address from the request (M-SEARCH) and we pass this to address to on_recv() method which uses it to send NOTIFY request which seems to be incorrect.
Changing this to 239.255.255.250:1900 fixes the issue, Windows is able to receive NOTIFY request, and fetch the device description xml file from LOCATION header
It seems that
NOTIFYrequest is sent to the same adres where theM-SEARCHrequest came from. For some implementation ofUPnPforAndroidit works. But onWindowsit doesn't. The request has to be sent to239.255.255.250:1900Here we get address from the request (
M-SEARCH) and we pass this to address toon_recv()method which uses it to sendNOTIFYrequest which seems to be incorrect.Changing this to
239.255.255.250:1900fixes the issue, Windows is able to receiveNOTIFYrequest, and fetch the device description xml file fromLOCATIONheader