Daily call not working

**MelissaH** · 15-03-2007, 05:41 PM

Hi,
I followed Peter's suggestions and the tclient log is below. I'm with Netspace. The date/time on the tivo is still incorrect though...?

Cheers,
Melissa.

Jun 16 10:31:27 (none) tcphonehome[144]: Log file rotation complete.
Jun 16 10:31:27 (none) tcphonehome[144]: TClient success
Jun 16 10:31:27 (none) comm[144]: CallStatusReporter: Phase: Prepare_Data, Status Succeeded
Jun 16 10:31:27 (none) comm[144]: CallStatusReporter: sending message "EX|49"
Jun 16 10:31:27 (none) tcphonehome[144]: Sending dialup event, subtype 7, msg Succeeded
Jun 16 10:31:27 (none) tcphonehome[144]: setCallStatus called with: Succeeded state 0
Jun 16 10:31:27 (none) tcphonehome[144]: LastCallAttempt at 1173976404
Jun 16 10:31:27 (none) tcphonehome[144]: last attempt in future; set it to now: -995462913
Jun 16 10:31:27 (none) tcphonehome[144]: status is 'Succeeded' == 'Succeeded'
Jun 16 10:31:27 (none) tcphonehome[144]: setting last success time to -995462913
Jun 16 10:31:27 (none) tcphonehome[144]: setting call status to: Succeeded
Jun 16 10:31:27 (none) tcphonehome[144]: setting call in progress to 0 (second successCount)
Jun 16 10:31:27 (none) tcphonehome[144]: setting LastSuccessPgdCall to -995462913
Jun 16 10:31:27 (none) tcphonehome[144]: Setting callActive to 0
Jun 16 10:31:27 (none) comm[144]: CallStatusReporter: sending data changed event 20
Jun 16 10:31:27 (none) tcphonehome[144]: destroying CommGlobals!
Jun 16 10:31:28 (none) tcphonehome[144]: pCommMempool empty
Jun 16 10:31:34 (none) tcphonehome[144]: Setting MCP PhoneHome action: ENABLED

**Darren King** · 15-03-2007, 06:46 PM

Originally Posted by MelissaH

The date/time on the tivo is still incorrect though...?

Ensure you have port 37 forwarded on your firewall otherwise the TiVo won't be able to set the correct time.

**petestrash** · 15-03-2007, 11:37 PM

According to your current tclient log, your last daily call was successful so no info was displayed.

In this case post your otclient log which will show what happened.

You say the time was still not updated. the 2nd ntpdate command I gave you should have shown some messages when it was run.

Peter.

**petestrash** · 16-03-2007, 02:35 AM

As a side issue, have you tried contacting netspace and asking them to remove 131.244.9.101 from thier proxies as the proxy is not handling http/1.0 requests properly.

First level customer support won't know what you are talking about, but if they push it up to a technician you should be able to get them to do it.

This would save all these hassles.

Peter.

**TimesOwn** · 16-03-2007, 05:24 AM

Ensure you have port 37 forwarded on your firewall otherwise the TiVo won't be able to set the correct time.

Darren are you saying the firewall should map external WAN port 37 to a TiVo's IP port 37 to ensure correct time setting? If so how do multiple TiVo's get mapped? Because the time request comes internally I would not have expected an external port need be open for this. Can you clarify please?

**Darren King** · 16-03-2007, 09:06 AM

Ummm... on my Billion 7402VGP I just told it to allow port 37 through to all IP addresses on the network..... Maybe a better choice of words would have been "ensure port 37 is open on the firewall".

**MelissaH** · 18-03-2007, 10:37 PM

Originally Posted by MattCallow

But you are currently using emuproxyZA, so instead change the line

Code:

127::127.0.0.1:8000:::

to

Code:

127::202.63.38.134:8000:::

I tried this, but the file is read only? A thousand apologies for my ignorance here... this is clearly not my area of expertise...

The otclient log is attached..

Also, this was the result when I tried to update the date/time (it's still incorrect on the tivo and I can't manually record) :

[TiVo [p0] ~]# /bin/ntpdate -b -v 132.163.4.103 192.43.244.18 129.6.15.29
oztivo ntpdate $Revision: 1.21 $
Our postcode is 03000. Found matching timezone Australia/Melbourne
Offset 36000 for timezone EST, daylight saving is 0
Connecting to time server 132.163.4.103
Setting the local time to Sun Mar 18 21:21:42 2007
[TiVo [p0] ~]#

I shall call Netspace this week and see how I go.

Thanks,
Melissa.

**petestrash** · 19-03-2007, 04:10 AM

the manual ntpdate command worked for a while (shows 18MAR), according to your otclient log. but the ntpdate which is run during the daily call is killing this as it's not connecting with the server for the correct IP addresses.

To follow matts suggestion we need to change the instructions, you need to do the following.

First we create sysinit.conf

cd /etc
rw
cp dflt_sysinit.conf sysinit.conf

Then disable emuproxyZA, by editing sysinit.conf and changing the line:

emuproxy_enable="YES" # Start one of the emuproxy programs:

to:

emuproxy_enable="NO" # Start one of the emuproxy programs:

and save the file.

Now edit tclient.conf, and change:

127::127.0.0.1:8000:::

to:

#127::127.0.0.1:8000:::
127::202.63.38.134:80:::

Save the file, then ro to make it read only again, then reboot.

Peter

**Darren King** · 19-03-2007, 07:23 AM

Originally Posted by MelissaH

I tried this, but the file is read only?

You need to put the TiVo into read/write first. Issue the command rw. Then make the changes and afterwards put the TiVo back into read only with the command ro

**MelissaH** · 19-03-2007, 06:09 PM

Ok, I made the changes to sysinit.conf and tclient.conf. Am I meant to end up with extra files called sysinit.conf~ and tclient.conf~ that have the old info in them?

The daily call now says 'Failed. No dial-in number chosen.'

The tclient log is attached.

I still have the following in /var/hack/etc/emuProxyZA.conf
proxyIP=210.15.254.253
proxyPort=8080

I called Netspace and they wouldn't do anything (yet), they said the proxy was 'proxy.netspace.au' and the DNS was 210.15.254.253 on port 8080 if that helps at all?

Thanks (for your patience),
Melissa.