Failed Daily Call and emuproxy

[rosie]

Hi guys,

When I had some recent reboot problems here http://www.tivoland.com/forum/viewtopic.php?f=8&t=1587 By disabling mfs_ftp I was able to fix the problem. While I was there I thought I would be clever and disable all the hacks that where listed here http://www.tivoland.com/forum/viewtopic.php?f=16&t=1087&p=10323 in green, shown as started in altepg, but CAN BE DISABLED.

After a week or so I noticed that my daily call was failing every time. My TiVo connects using a network card. Symptoms were that I could still telnet into the box and use TivoWeb...a quick search here and someone pointed out to someone else having the same exact problem that maybe their emuproxy process had died. ChaChing, I re-enabled my emuproxy hack and it now connects and is downloading data, all good.

So, am I correct in saying that emuproxy is required for TiVo to phone home over the network? If so, can someone change the 'List of Hacks' thread pointed to above to make that clear so someone else doesn't make the mistake?

Thanks,
Jeff

[healeydave]

Yes, emuproxy is required by default in an AltEPG image for connection to the AltEPG server.

emuproxy is a hack that makes for a more reliable connection to the backend server due to issues with legacy http headers.
It is possible to disable emuproxy and use the old original connection method but if you do so, you also need to change your dialling code to point directly to the IP of the AltEPG server as the default dialling code routes all communication to the local loopback IP which emuproxy uses.
If you disable emuproxy and don't change the dialling code, you daily calls with fail, exactly as you experienced.