TiVo Community
TiVo Community
TiVo Community
Go Back   TiVo Community > Main TiVo Forums > TiVo Help Center
TiVo Community
Reply
Forum Jump
 
Thread Tools
Old 12-21-2013, 03:32 PM   #1
BobCamp1
Registered User
 
Join Date: May 2002
Posts: 992
Series 1 download issues again

It's that time of the year.

My series 1 keeps dropping the daily call with "call interrupted". It happened on Dec. 14 & 15, then worked normally until the 19th. It gives a "call interrupted" about 10 seconds after the status swtiches to "downloading." Any other ancient Tivo owners (the Tivo is old, not the owner) having this issue?

I'll try PPP over serial on Monday. It doesn't want to work with a USB to serial adapter. I tried Windows 7 and Virtual XP mode. I've got to borrow a Windows XP notebook PC with a genuine serial port from work.

It's funny how this issue always happens at the end of the year. Unless it's just me this time and my Tivo is finally dying.
BobCamp1 is offline   Reply With Quote
Old 12-21-2013, 05:47 PM   #2
vjquan
Registered User
 
Join Date: Feb 2009
Posts: 16
Me too.

I'm having the same problem - stopped updating a couple of days ago. I'm using a series 1 with turbonet. Test calls are fine, however, when making a call, it connects to retrieve account status, update clock, etc., but fails when downloading data. Message is Failed, call interrupted.

I restarted the recorder and I got a message saying the dial in number I was using is no longer valid and to select another. When trying to retrieve dial in numbers, it fails there in the same way, so I can't even get that. I contacted Tivo and they said nothing has changed and there was nothing more they can do. They also said by opening the box to install turbonet, warranty is void and support is no longer obligated. They suggested I email WeaKnees, which I did.

Response from WeaKnees:
"I think this is a problem on TiVo's side. We have heard from multiple people with this problem."

Hopefully Tivo will get enough calls to fix the problem. I hate to think that it's the end of life for this series 1.

Any Tivo reps reading this? TivoJerry used to be pretty good with support here on the forums, but don't know if he's still around.
vjquan is offline   Reply With Quote
Old 12-21-2013, 06:40 PM   #3
Series1Ron
Registered User
 
Join Date: Dec 2013
Posts: 4
Series 1 "Call Interrupted" me too

Series 1 Lifetime; tried both landline and ooma/modem. tried internal modem and weeknees external modem.

I'm experiencing the same recently.

1st Daily test call works (dial>connecting>downloading>hanging up>done) - works

2nd Connecting (preparing to call> dial>connecting> set clock> getting account status>done) - works

3rd Downloading works for 15 seconds then "Fail. Call Interrupted"

For landline from Series 1:
1) using the telephone turned off call forwarding *73
2) using the telephone turned off call waiting *70
3) set tivo dial prefix to blank
4) set tivo call waiting to blank
5) set tivo detections to off

For landline using weaknees external modem:
1) using the telephone turned off call forwarding *73
2) using the telephone turned off call waiting *70
3) set tivo dial prefix to ,#319 (also tried ,#357 ,#334 ,#396)
4) set tivo call waiting to blank
5) set tivo detections to off

I've also tried calling through Ooma (must have call waiting prefix: *99). Same results. However, I get more connection problems since family members are using the internet while I'm trying to download.

I've unplugged tivo and let it reboot.

This appears to have happened since the beginning of Tivo forums (2005).

I've spent a day (while watching football) trying different parameters.

I'm wondering if holiday gifts are being opened early and the lines are jammed?
Series1Ron is offline   Reply With Quote
Old 12-22-2013, 07:45 AM   #4
steve614
what ru lookin at?
 
steve614's Avatar
 
Join Date: May 2006
Location: Dallas, TX
Posts: 10,722
Maybe TiVo is surreptitiously trying to get people to upgrade.
__________________
The Man Prayer: I'm a man ...... I can change ...... If I have to ...... I guess.



To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.


To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.

F*CK CANCER!
steve614 is offline   Reply With Quote
Old 12-22-2013, 01:19 PM   #5
pianoman
:-|
 
pianoman's Avatar
 
Join Date: Jun 2002
Location: Metairie, LA
Posts: 3,663
I also experienced the same thing very recently - I had a drive crash on my Series 1, and after I rebuilt it, I was unable to get it to complete guided setup. It would fail with "Failed- Call Interrupted".

I was eventually able to get through guided setup by using area code (000).
__________________
You inspired me, Pianoman! -- M82A1A
Pianoman, you have inspired me. -- hefe
Pianoman, that's not very inspiring. -- edhara
pianoman is offline   Reply With Quote
Old 12-22-2013, 04:00 PM   #6
unitron
Registered User
 
unitron's Avatar
 
Join Date: Apr 2006
Location: semi-coastal NC
Posts: 13,436
Since this seems to happen every year around this time of year, you'd think that TiVo would have been able to figure out the cause by now, so I can't help but suspect that it's due to something someone is doing on purpose, like maybe a rolling suspension of telephone line leasing to save money until the first of the year.
__________________
(thisismysigfile)


"I am altering the deal. Pray I don't alter it any further."

Darth TiVo, 14 February, 2011
unitron is online now   Reply With Quote
Old 12-22-2013, 04:11 PM   #7
ashipkowski
Registered User
 
Join Date: Oct 2008
Posts: 3
I, too, am seeing this with my SVR-2000; trying to get PPP over serial to work but am not having any success ("Failed. Service not answering." on the test screen, doing a lot of debugging, let's keep this thread focused on the failure mode.) I'm curious if anyone with an S1 who has jumped to PPP is having that work for them.
ashipkowski is offline   Reply With Quote
Old 12-22-2013, 09:56 PM   #8
unitron
Registered User
 
unitron's Avatar
 
Join Date: Apr 2006
Location: semi-coastal NC
Posts: 13,436
I think there's something on TiVo's end that, when it finds out it's talking to a Series 1, can't be bothered. The mystery is why it gets that way about this time every year.
__________________
(thisismysigfile)


"I am altering the deal. Pray I don't alter it any further."

Darth TiVo, 14 February, 2011
unitron is online now   Reply With Quote
Old 12-22-2013, 09:58 PM   #9
pianoman
:-|
 
pianoman's Avatar
 
Join Date: Jun 2002
Location: Metairie, LA
Posts: 3,663
Forgot to mention that my failure was with a Turbonet card, so it doesn't seem to be isolated to "phone line" calls. (The modem in this unit has been dead for years.)
__________________
You inspired me, Pianoman! -- M82A1A
Pianoman, you have inspired me. -- hefe
Pianoman, that's not very inspiring. -- edhara
pianoman is offline   Reply With Quote
Old 12-23-2013, 06:48 PM   #10
glen_a_stewart
Registered User
 
Join Date: Jan 2010
Posts: 5
A little debug log

Quote:
Originally Posted by pianoman View Post
Forgot to mention that my failure was with a Turbonet card, so it doesn't seem to be isolated to "phone line" calls. (The modem in this unit has been dead for years.)
Same setup here. Some log info from /var/log/tcdebuglog

Dec 24 00:30:13 (none) comm[141]: BackhaulRqst verify start
Dec 24 00:30:13 (none) comm[141]: BackhaulRqst parseBody
Dec 24 00:30:13 (none) comm[141]: XferRqst Verify() done: (#8 fopen=T fclose=T fverify=T feval=F fopenstatus=F verifystatus=F evalstatus=0x0 nread=1043 nwrite=128 nreaderr=0 nwriteerr=0)
Dec 24 00:30:13 (none) comm[141]: NetAgent: drainGetPostQ: doXfer ok (enqueuing evalQ: BackHaul)
Dec 24 00:30:13 (none) comm[141]: XferRqst XferRqstQ(eval) adding (#8 type=1 ipaddr=204.176.49.9 port=80 name=BackHaul dataname=thumbs log infile=/var/persist/thumbslog.log.gz.bfg outfile=)
Dec 24 00:30:13 (none) comm[141]: NetAgent: Process: drainPostQ err 0
Dec 24 00:30:13 (none) comm[141]: NetAgent: drainGetPostQ: starting doXfer(#6 type=1 ipaddr= port=8080 name=HttpGet dataname=/var/packages/AC-513-v23.slice infile= outfile=/var/packages/AC-513-v23.slice)
Dec 24 00:30:13 (none) comm[141]: FileRqst opened output file /var/packages/AC-513-v23.slice
Dec 24 00:30:13 (none) comm[141]: XferRqst Open() done: (#6 fopen=T fclose=F fverify=F feval=F fopenstatus=F verifystatus=F evalstatus=0x0 nread=0 nwrite=0 nreaderr=0 nwriteerr=0)
Dec 24 00:30:13 (none) comm[141]: NetAgent: doXfer: tmk tcp socket failed 327685
Dec 24 00:30:13 (none) comm[141]: NetAgent: Process: drainGetQ err 327685
Dec 24 00:30:13 (none) comm[141]: NetAgent: flushing all queues
Dec 24 00:30:13 (none) comm[141]: CallService: InCall: err 327685
Dec 24 00:30:15 (none) comm[141]: CallService: EndCall returns 327685
Dec 24 00:30:15 (none) comm[141]: CallService: EndCall: err 327685
Dec 24 00:30:15 (none) comm[141]: commglobals fBackhaulCallM = 1, evalOK = 0
Dec 24 00:30:15 (none) comm[141]: commglobals FBackhaulDone=F
Dec 24 00:30:19 (none) aval_pp[141]: NukeOrphanedRecordings found 0 orphans
Dec 24 00:30:19 (none) comm[141]: CallService: CleanupCall: Cleanup err 0


From /var/log/tclient:


Dec 24 00:30:07 (none) comm[141]: CallStatusReporter: Phase: Backhaul, Status In Progress
Dec 24 00:30:07 (none) comm[141]: CallStatusReporter: sending message "ST|34"
Dec 24 00:30:08 (none) comm[141]: CommUtil: connection to host 204.176.49.9, port 80, err 0x0
Dec 24 00:30:08 (none) comm[141]: Uploading HTTP Header for BackHaul of thumbs log: POST /tivo-service/uploadFile.cgi?type=.45014.th_us.3-0&pp=.gz.bfg&fn=SPECIFY_TOKEN&mso=tivo&an=1&prv=1 HTTP/1.0^M Content-Length: 906^M ^M
Dec 24 00:30:09 (none) comm[141]: read HTTP Header: HTTP/1.1 200 OK^M Date: Tue, 24 Dec 2013 00:30:09 GMT^M Server: Apache^M Connection: close^M Content-Type: text/plain
Dec 24 00:30:13 (none) comm[141]: Status: ok
Dec 24 00:30:13 (none) comm[141]: CallStatusReporter: Phase: Download, Status In Progress
Dec 24 00:30:13 (none) comm[141]: CallStatusReporter: sending message "DL|38"
Dec 24 00:30:13 (none) comm[141]: CommUtil: connection to host , port 8080, err 0x50005
Dec 24 00:30:13 (none) comm[141]: tmk tcp connect failed, reason = Bad file descriptor
Dec 24 00:30:13 (none) comm[141]: drainGetPostQ: doXfer failed err=327685 (0x50005)
Dec 24 00:30:13 (none) comm[141]: CallService: NetAgent Process err 327685
Dec 24 00:30:13 (none) comm[141]: CallService: NetAgent failed, status 0x50005
Dec 24 00:30:13 (none) comm[141]: CallService: EndCall start


...and the last interesting log from /var/log/kernel


Dec 24 00:29:50 (none) kernel: turbonet2: call log: attempting to connect (port 80)...
Dec 24 00:29:50 (none) kernel: turbonet2: call log: connect succeeded (port 80)...
Dec 24 00:29:50 (none) kernel: turbonet2: call log: POST /tivo-service/mlog.cgi HTTP/1.0
Dec 24 00:29:50 (none) kernel: turbonet2: call log: HTTP/1.1 200 OK
Dec 24 00:29:51 (none) kernel: turbonet2: call log: attempting to connect (port 80)...
Dec 24 00:29:51 (none) kernel: turbonet2: call log: connect succeeded (port 80)...
Dec 24 00:29:51 (none) kernel: turbonet2: call log: POST /tivo-service/TCD411.cgi HTTP/1.0
Dec 24 00:29:51 (none) kernel: turbonet2: call log: HTTP/1.1 200 OK
Dec 24 00:29:51 (none) kernel: turbonet2: call log: attempting to connect (port 80)...
Dec 24 00:29:51 (none) kernel: turbonet2: call log: connect succeeded (port 80)...
Dec 24 00:29:51 (none) kernel: turbonet2: call log: POST /tivo-service/HServer.cgi HTTP/1.0
Dec 24 00:29:53 (none) kernel: turbonet2: call log: HTTP/1.1 200 OK
Dec 24 00:30:01 (none) kernel: turbonet2: call log: NTP request...
Dec 24 00:30:01 (none) last message repeated 2 times
Dec 24 00:30:02 (none) kernel: turbonet2: call log: NTP response.
Dec 24 00:30:02 (none) kernel: turbonet2: call log: NTP response.
Dec 24 00:30:02 (none) kernel: turbonet2: call log: NTP request...
Dec 24 00:30:02 (none) kernel: turbonet2: call log: NTP request...
Dec 24 00:30:02 (none) kernel: turbonet2: call log: NTP response.
Dec 24 00:30:02 (none) kernel: turbonet2: call log: NTP request...
Dec 24 00:30:02 (none) kernel: turbonet2: call log: NTP response.
Dec 24 00:30:02 (none) kernel: turbonet2: call log: NTP request...
Dec 24 00:30:02 (none) kernel: turbonet2: call log: NTP response.
Dec 24 00:30:02 (none) kernel: turbonet2: call log: NTP request...
Dec 24 00:30:02 (none) kernel: turbonet2: call log: NTP response.
Dec 24 00:30:02 (none) kernel: turbonet2: call log: NTP request...
Dec 24 00:30:03 (none) kernel: turbonet2: call log: NTP response.
Dec 24 00:30:03 (none) kernel: turbonet2: call log: NTP request...
Dec 24 00:30:03 (none) kernel: turbonet2: call log: NTP response.
Dec 24 00:30:03 (none) kernel: turbonet2: call log: NTP request...
Dec 24 00:30:03 (none) kernel: turbonet2: call log: NTP response.
Dec 24 00:30:03 (none) kernel: turbonet2: call log: NTP request...
Dec 24 00:30:04 (none) kernel: turbonet2: call log: NTP response.
Dec 24 00:30:05 (none) last message repeated 2 times
Dec 24 00:30:05 (none) kernel: turbonet2: call log: attempting to connect (port 80)...
Dec 24 00:30:06 (none) kernel: turbonet2: call log: connect succeeded (port 80)...
Dec 24 00:30:06 (none) kernel: turbonet2: call log: POST /keydist.cgi?CALLTYPE=1&UPGRADE=0 HTTP/1.0
Dec 24 00:30:07 (none) kernel: turbonet2: call log: HTTP/1.1 200 OK
Dec 24 00:30:07 (none) kernel: turbonet2: call log: attempting to connect (port 80)...
Dec 24 00:30:08 (none) kernel: turbonet2: call log: connect succeeded (port 80)...
Dec 24 00:30:08 (none) kernel: turbonet2: call log: POST /tivo-service/uploadFile.cgi?type=.45014.th_us.3-0&pp=.gz.bfg&fn=SPECIFY_TOKEN&mso=tivo&an=1&prv=1 HTTP/1.0
Dec 24 00:30:09 (none) kernel: turbonet2: call log: HTTP/1.1 200 OK
Dec 24 00:30:13 (none) kernel: tcp_keepalive: call keepopen(0x803739c0)
Dec 24 00:30:13 (none) kernel: tcp_keepalive: call keepopen(0x80e64a00)
Dec 24 00:30:22 (none) kernel: connect failed, reason = Connection timed out
Dec 24 00:30:22 (none) kernel: Internal error #R
Dec 24 00:30:22 (none) kernel: /gotomydvr/etc/rc.gotomydvr: .: filename argument required
Dec 24 00:30:22 (none) kernel: .: usage: . filename
Dec 24 00:30:22 (none) kernel: *** Empty KNOWN_HOST configuration ***
Dec 24 00:30:38 (none) kernel: CodeFromNec(40bf12e0) is meaningless

Dec 24 00:31:28 (none) kernel: tcp_keepalive: call keepopen(0x80e64a00)
Dec 24 00:32:43 (none) kernel: tcp_keepalive: call keepopen(0x80e64a00)
Dec 24 00:33:58 (none) kernel: tcp_keepalive: call keepopen(0x80e64a00)
Dec 24 00:35:13 (none) kernel: tcp_keepalive: call keepopen(0x80e64a00)
Dec 24 00:36:28 (none) kernel: tcp_keepalive: call keepopen(0x80e64a00)
Dec 24 00:37:43 (none) kernel: tcp_keepalive: call keepopen(0x80e64a00)
Dec 24 00:38:58 (none) kernel: tcp_keepalive: call keepopen(0x80e64a00)


I can't advise on the exact cause, but hope these logs are informative to someone.
glen_a_stewart is offline   Reply With Quote
Old 12-23-2013, 07:18 PM   #11
JudyLew
Registered User
 
Join Date: Dec 2013
Posts: 13
Yikes, just joined TiVo community & no idea what I'm doing! I prepared a long sob story of trouble getting daily update. Let's see if THIS message posts successfully!
JudyLew is offline   Reply With Quote
Old 12-23-2013, 07:26 PM   #12
JudyLew
Registered User
 
Join Date: Dec 2013
Posts: 13
Last successful daily update was Wed. morning 12/18/2013. I've had many "call interrupted" messages, an occasional "service not answering". Many reboots. Attempts to select another dial-in # fail with "call interrupted" message when trying to get list of available numbers. Test calls are successful. (???) About an hour ago, I contacted support chat. Agent said "no problem here" than admitted TiVo is "having an outage re telephone connections" Not able to say how long til trouble will B fixed. Agent's final advice was "Keep trying to connect and it will eventually go through". Grrrr!
JudyLew is offline   Reply With Quote
Old 12-24-2013, 12:12 AM   #13
bobwojo
Registered User
 
Join Date: Jan 2011
Posts: 7
Same problem

I have two Series1's with the same problem, have only 3 days of program data left....Will Be sending TIVO a note soon to see what they say...
bobwojo is offline   Reply With Quote
Old 12-24-2013, 12:15 AM   #14
bobwojo
Registered User
 
Join Date: Jan 2011
Posts: 7
Same here, only 3 days data left...
bobwojo is offline   Reply With Quote
Old 12-24-2013, 12:58 AM   #15
Jay_E
Registered User
 
Join Date: Dec 2013
Location: Florida
Posts: 1
2nd stage failure - unable to get new dial-in numbers

Hi there,

Got a message that the dial-in number is no longer valid.

Yup, Have been getting the Connect failure message.
Call this "Stage 1".

OK.
Then I go through the procedure to get the list of dial-in numbers...
Tivo Central -> Message & Setup -> Recorder & Phone Setup ->
Phone Connection -> Set Dial-in number.

I enter 407

Then get Connection failure.
Call this "Stage 2".


After several attemps I listened in on my phone.
I modem did answer - not a "you dialled a disconnected number' message".

So. Any suggestions on how to get a new,valid number.
There *used* to be a URL under Tivo that listed the numbers.
I can't find it.
It probably was deleted?

Suggestions??


Jay
(12/24/2013)

PS
Also tried to get numbers for area code 321 and 352.
These attempts also failed.

Last edited by Jay_E : 12-24-2013 at 12:59 AM. Reason: fix typ. Clarify
Jay_E is offline   Reply With Quote
Old 12-24-2013, 02:10 AM   #16
brendag4
Registered User
 
Join Date: Apr 2005
Posts: 92
Philips series one also can't connect

Having the same problem.. gets to downloading then says failed call interrupted

Read where someone said their problem was fixed by Clearing Program Data and To Do List. I did that, now I have no program data and it still won't connect to Tivo.

I connect over cable internet. Turbocard.

Tried to change the local phone number even though I didn't think that would have anything to do with my problem. It cannot complete the phone list call. It gets call interrupted when it is trying to connect. The test call works.

Of course I also tried resetting and removing cable modem
brendag4 is offline   Reply With Quote
Old 12-24-2013, 02:30 AM   #17
brendag4
Registered User
 
Join Date: Apr 2005
Posts: 92
possible fix?

I had this problem before. I found an old post of mine about it. It linked to a post I think by TivoJerry. He wanted certain info to go to the Engineers. His original post about what they needed is gone.

I found my private response to TivoJerry about how I fixed the problem. It involves renaming the log file. Is there a way to clear the log without pulling the drive? I don't have easy access to an old desktop to even try this suggestion. I see log files listed on TivoWebPlus but I am afraid to delete them with no way to back them up.

part of my old message to TivoJerry is below:

Finally broke down and pulled the drive.

I renamed the log directory, and was able to get out of Guided Setup with 2 calls.

Other people have reported fixing call interrupted error this way, but state it eventually comes back.
brendag4 is offline   Reply With Quote
Old 12-24-2013, 03:39 AM   #18
ggieseke
Registered User
 
Join Date: May 2008
Posts: 2,980
I finally retired the last of my S1s, but in previous years the only real solution was to force a daily call over & over until it completes. As long as you don't do a test connection the data it gets on each call is cumulative and it will eventually get the full download.

One time it took over 20 tries.
ggieseke is offline   Reply With Quote
Old 12-24-2013, 06:54 AM   #19
JudyLew
Registered User
 
Join Date: Dec 2013
Posts: 13
Jeekers, U folks! Glad to see it's not just me! BUT if we all keep contacting TiVo support people, maybe they will fix. I truly believe the problem is on TiVo end and, not with our old dear machines. Last nite I saw another post suggesting that maybe TiVo is trying 2 force us to ask Santa for a Roamio or some such. LOL
JudyLew is offline   Reply With Quote
Old 12-24-2013, 08:18 AM   #20
brendag4
Registered User
 
Join Date: Apr 2005
Posts: 92
Quote:
Originally Posted by ggieseke View Post
As long as you don't do a test connection the data it gets on each call is cumulative and it will eventually get the full download.

One time it took over 20 tries.
I left it on the Phone Connection screen. I tried over 30 times. I don't know if you had any guide data when it took you 20 tries. I have no guide data.

Before I did this, I renamed /var/log. (The log dir got renamed not the /var of course.) I don't know if there are logs in more than one location. Did not work. (updated to my previous post)

Last edited by brendag4 : 12-24-2013 at 08:19 AM. Reason: clarification
brendag4 is offline   Reply With Quote
Old 12-24-2013, 08:43 AM   #21
JudyLew
Registered User
 
Join Date: Dec 2013
Posts: 13
Oh, dear Brenda! This is awful!! Please, everybody, contact the TiVo support place and complain. This must not continue. I have a few days of guide data, but daily calls are failing continually. "Call interrupted" Good luck to all and Merry Christmas.
JudyLew is offline   Reply With Quote
Old 12-24-2013, 09:01 AM   #22
brendag4
Registered User
 
Join Date: Apr 2005
Posts: 92
I had several days of Guide data too. But I read a suggestion that someone cleared their guide data and then it worked. Didn't work for me, so now I have no guide data.

I have now tried over 45 times.

I have contacted support. But I am afraid they will say since there is a Turbocard I won't get any support.

When I had this problem before, I did Guided Setup, then got stuck there. I had to pull the drive from the Tivo, delete the logs, then do 2 calls and finally got back to normal. (I couldn't telnet in when I was in Guided Setup)

WeaKnees blog post on this situation. They say the techs are out until Monday.. but it was posted on Monday so does that mean we have to wait another week?! (remove the space before the www)

http:// http://www.wkblog.com/tivo/2013/12/s...omment-page-1/

Last edited by brendag4 : 12-24-2013 at 09:03 AM. Reason: clarification
brendag4 is offline   Reply With Quote
Old 12-24-2013, 09:14 AM   #23
pianoman
:-|
 
pianoman's Avatar
 
Join Date: Jun 2002
Location: Metairie, LA
Posts: 3,663
In desperation (when I was running guided setup after my recent drive failure), I changed the dial-in area code to (000), even though I'm not using the phone line at all. I'm using a Turbonet card, and have been for years.

The call appeared to complete, then a message appeared that (000) was not a valid area code. However, I was then given several options, one of which included indicating that I was a retailer. I decided to select this option, and the call completed successfully. Since then, I have been able to make the daily call. This is obviously not a desirable long-term solution, but it might help others who are struggling.

I'm also unsure if you can get to this option without running Guided Setup.
__________________
You inspired me, Pianoman! -- M82A1A
Pianoman, you have inspired me. -- hefe
Pianoman, that's not very inspiring. -- edhara
pianoman is offline   Reply With Quote
Old 12-24-2013, 09:42 AM   #24
brendag4
Registered User
 
Join Date: Apr 2005
Posts: 92
Quote:
Originally Posted by pianoman View Post
The call appeared to complete, then a message appeared that (000) was not a valid area code. However, I was then given several options, one of which included indicating that I was a retailer.
I tried the 000 idea earlier and it didn't work for me. I was not using Guided Setup though. I cannot even connect to get the dial up numbers. (But I get to the downloading message on the daily call, so a connection is getting made)

I don't think repeatedly trying to call is going to work in my situation. I have now tried over 50 times.

Possibly because I renamed the log directory, or maybe it got nothing from the 000.. I got a message saying there were no valid dial up numbers. I could not dial out to get the list. I don't know if this requires a phone cable. I don't know if it even matters because I am using a Turbocard. There should be valid numbers in my area.. the last time I looked there were several.

Last edited by brendag4 : 12-24-2013 at 09:44 AM. Reason: remembered what happened when I did 000
brendag4 is offline   Reply With Quote
Old 12-24-2013, 10:00 AM   #25
brendag4
Registered User
 
Join Date: Apr 2005
Posts: 92
Well after my 50 attempts to get guide data, it works to get the list of numbers using 000. (I mean it successfully completed instead of it saying it failed.)

It says the 000 has no dial in numbers. 2 choices, try another area code, or done trying.

Done trying gives choices of try another code and Sales and Marketing program

Sales and Marketing says the recorder is not authorized as part of the sales and marketing program.

Going back to original area code just gives the same error as before on Connecting (failed call interrupted)

I am wondering if not having a valid number (or at least the Tivo thinks it isnt) would stop a download of Guide data that is going through the internet not the phone.
brendag4 is offline   Reply With Quote
Old 12-24-2013, 10:26 AM   #26
brendag4
Registered User
 
Join Date: Apr 2005
Posts: 92
I was able to find a link to see what numbers are valid in your area from an old post. (The one on the Tivo site doesn't work) I thought other people might need this link.

The number that my Tivo is trying to call is not on this list. I wouldn't figure that would even matter for cable internet.

https://www.tivo.com/email-sub/popfinder.do
brendag4 is offline   Reply With Quote
Old 12-24-2013, 11:53 AM   #27
JudyLew
Registered User
 
Join Date: Dec 2013
Posts: 13
Thanks for your thoughts, folks! I just looked at my "to do" list and got an onscreen message "only 7 days of guide data, Please make a daily call" IF ONLY !!! I would laugh if I weren't crying so much! I had tried again this morning, got thru setting clock, checking account status, downloading for a short time. Then TiVo hung up on me & gave "Call interrupted" message. Call sure wasn't interrupted from my end!

I'm going to contact the TiVo support folks again, when I can take a break from Christmas preparations.

This is truly the PITS!
JudyLew is offline   Reply With Quote
Old 12-24-2013, 12:38 PM   #28
Series1Ron
Registered User
 
Join Date: Dec 2013
Posts: 4
A Christmas Miracle!! I got past Call Interrupted - Set Area Code '000'

My setup: Series 1 Lifetime; internal modem and calling on Ooma (internet)

After setting my area code to '000', Tivo completed the 'Setup Call".

Here's where I started (I rebooted and cleared the entire Tivo drive [1 hour] and not recommended):

Step 1:

Screen: "setup Call (10-20 min)"
[I'm using Series 1 internal modem and Ooma (internet)]:

1) set area code to '000' and go to 'Yes-change telephone options'

On the 'Setup Call' screen:

2) since I'm in 'Setup Call' there is no 'set Dial-In Number'

3) set tivo dial prefix to',#019'

4) set tivo call waiting to '*99' [I connect to Ooma Voip]

5) set tone/pulse to 'tone'

6) set both detections to off


Step 2:

Test phone connection to verify the settings work.

Step 3:

On the 'Phone dialing options' choose 'use these dialing options' at the top of the screen.

Step 4:

After completing the 'setup call'

including Connecting>Downloading>Hanging Up>Importing> Indexing

I hit select button and the next screen is titled "Dial-In Number"

Choose 'Done trying area codes'

Step 5:

The next screen is titled 'No local numbers'

Choose 'Sales & Marketing program'

Step 6:

I didnt screen shot the next screen few screens (I was too excited lol) but they were like 'Choose your cable company'; the next screen was 'Choose the channels' [I selected 'all'] and finally got to 'Program Call (20-30 min)'

Step 7:

After about 20-30 min I got to the 'Congratulations' screen.

However, my tivo remote is not getting past this screen. I can see the tivo green light on the front change from green to yellow when I press select but nothing happened.

I physically pulled the plug from the back of the tivo.

Step 8:

After rebooting, tivo now shows the green main menu screen.

I then did 'Test phone connection' again and it worked.

After 1 week without success, I'm now 'downloading...phone in use'

Special thanks to Pianoman for recommending setting the area code to '000'


I hope this brings a Christmas Miracle to you!!
Series1Ron is offline   Reply With Quote
Old 12-24-2013, 01:33 PM   #29
JudyLew
Registered User
 
Join Date: Dec 2013
Posts: 13
Thanks, Series1Ron. Sounds complicated & time consuming but if it works, YAY for you!

I'm kinda busy now getting ready 4 tomorrow, but may call the TiVo folks who helped me in summer 2012 at 877 367-8486. As U may see below, the agent at "on-line support chat" was not much use yesterday.

More later. ♥ ♥
JudyLew is offline   Reply With Quote
Old 12-24-2013, 02:22 PM   #30
pianoman
:-|
 
pianoman's Avatar
 
Join Date: Jun 2002
Location: Metairie, LA
Posts: 3,663
Quote:
Originally Posted by Series1Ron View Post
After setting my area code to '000', Tivo completed the 'Setup Call".

...

Special thanks to Pianoman for recommending setting the area code to '000'


I hope this brings a Christmas Miracle to you!!
Glad it worked out for you! It seems to be the combination of area code "000" and choosing the "Sales & Marketing" program that bypasses the problem. Hopefully TiVo will chime in once they've fixed the actual problem on their end.
__________________
You inspired me, Pianoman! -- M82A1A
Pianoman, you have inspired me. -- hefe
Pianoman, that's not very inspiring. -- edhara
pianoman is offline   Reply With Quote
Reply
Forum Jump




Thread Tools


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Advertisements

TiVo Community
Powered by vBulletin® Version 3.6.8
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
vBulletin Skins by: Relivo Media

(C) 2013 Magenium Solutions - All Rights Reserved. No information may be posted elsewhere without written permission.
TiVoŽ is a registered trademark of TiVo Inc. This site is not owned or operated by TiVo Inc.
All times are GMT -5. The time now is 12:55 AM.
OUR NETWORK: MyOpenRouter | TechLore | SansaCommunity | RoboCommunity | MediaSmart Home | Explore3DTV | Dijit Community | DVR Playground |