Loading Profile...
Conference is scheduled to be broken down automatically in FIVE minutes.
My favorite podcast, The Lost Lowdown, utilizes your service, Talkshoe, to record their programs. Their podcast regularly reaches lengths of more than five hours. After a certain arbitrary period (most recently 3 hours, 32 minutes) the following message is played: "Conference is scheduled to be broken down automatically in FIVE, minutes. To extend the time by 60 minutes, press star 8". I have never used Talkshoe and have no experience with your system, but as long as the Talkcast is active and you're hearing sound, is it really necessary to have this distracting interruption?
2
people have this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
The best answer from everyone
-
Actually, I must correct Rob (below) on this one. The TalkShoe system does NOT contain either that audio message or that notification function. *8, also known as *T (as in Talk), is our "request to talk" command.
We allow calls to run for 24-hours without interruption, although recording will run for just 5 hours (note to interested parties: you may restart recording after 5 hours by pressing *2*1 but must contact me [daven@talkshoe.com -- indicating your 5-digit call ID) to ask that the second/third/fourth... recording(s) be retrieved and posted manually.
In our history, we had one other incident like this (http://getsatisfaction.com/talkshoe/t...). Upon investigation, it turned out that one of the callers was apparently bridging in another conferencing service using 3-way calling on his phone. The message was coming from that service. If you're using TalkShoe Live Pro, the name of that caller should be highlighted as the message plays (our See Who's Talking feature).
We highly recommend that all participants phone into TalkShoe directly, to avoid issues like this, and to allow TalkShoe's advanced audio processing capabilities (auto-gain-control, echo cancellation, etc.) to be applied individually to every caller.
I hope that helps.
The company says
this answers the question
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Since most podcasts or talkcasts do not exceed the recording limits, this message is built in to automatically shutdown a show that maybe the host forgot to end. In this manner, sometime after the 3 hour mark, this message will appear to allow the host to extend their show by an additional 60 minutes. If they fail to respond to the prompt, then they might not be there and the show will automatically be shutdown to prevent long recordings with "dead air" being recorded. You should only hear this message after a show has been going for more than 3 hours. -
Inappropriate?Actually, I must correct Rob (below) on this one. The TalkShoe system does NOT contain either that audio message or that notification function. *8, also known as *T (as in Talk), is our "request to talk" command.
We allow calls to run for 24-hours without interruption, although recording will run for just 5 hours (note to interested parties: you may restart recording after 5 hours by pressing *2*1 but must contact me [daven@talkshoe.com -- indicating your 5-digit call ID) to ask that the second/third/fourth... recording(s) be retrieved and posted manually.
In our history, we had one other incident like this (http://getsatisfaction.com/talkshoe/t...). Upon investigation, it turned out that one of the callers was apparently bridging in another conferencing service using 3-way calling on his phone. The message was coming from that service. If you're using TalkShoe Live Pro, the name of that caller should be highlighted as the message plays (our See Who's Talking feature).
We highly recommend that all participants phone into TalkShoe directly, to avoid issues like this, and to allow TalkShoe's advanced audio processing capabilities (auto-gain-control, echo cancellation, etc.) to be applied individually to every caller.
I hope that helps.
The company says
this answers the question
-
Inappropriate?Both of us were dialed in directly to Talkshoe, and we have never heard such messages coming from our own phone service. Could it be because we were using a private group call? -
Inappropriate?Furthermore, we have made files longer than 5 hours, one of them was 8 hours long, no buttons (besides what this complaint describes) and no emailing anyone.
-
Inappropriate?Let me look at the call logs. What is your 5-digit call ID?1 Comment Add a comment
This answers the question
-
21637 -
Inappropriate?During the OSD-Obsessive Sneaker Disorder show on Jan. 7, 2009, EP64, I heard the same message and I use SIP and X-Lite to host OSD. -
Inappropriate?OSD had 30 callers. It will be far easier to trace this problem on Justin's call since it had just two callers. Let me focus there and report the results.
-
-
Inappropriate?We listened to the Justin's "Lost" recording around 3:32, plus and minus 4 minutes either way and there's no evidence of the reported message. We believe that any message must have come from outside of TalkShoe, perhaps not even over the phone line. Again, we use star 8 for "request to talk" --- and it has no associated confirmation audio message. Further, we do not impose length restrictions on call length until 5 hours or longer.
The message: "Conference is scheduled to be broken down automatically in FIVE, minutes. To extend the time by 60 minutes, press star 8" makes no sense to us here.
I’m confident
-
Inappropriate?I edited the version Stephen heard. So the time was different than the original file on talkshoe, The message is there, I did not add anything to the file. I don't actually know what the original time was, but I think it would be about 5 or 6 minutes later than what Stephen said.
-
Inappropriate?Hi Dave. I'm the other co-host for this podcast. That message is at 3:38:05 in "podcast 52" http://recordings.talkshoe.com/TC-216...
Thanks for your help and interest with this problem!
I’m excited this issue might actually get fixed!
-
Inappropriate?Thanks for the pointer. I've grabbed the snippet with the announcement and sent it to the equipment manufacturer for investigation.
-
-
Inappropriate?Our equipment manufacturer believes that it was indeed their audio message, and also that they've had no other reports of it being randomly triggered. We've found no way to reproduce the problem which makes it virtually impossible to diagnose.
However, we thoroughly enjoyed listening to your comments about the glitch when it originally occurred. LOL.
As of now, we're not actively pursuing this. If it occurs again, or if you have ideas about how to trigger the issue, we'll certainly reengage. -
Inappropriate?We've had it happen on almost all of our Talkshoe sessions. It seems to usually occur shortly before the 4 hour mark, though it isn't quite that predictable. It seems that all you need to trigger it is to stay on Talkshoe for an extended period of time. Also, after the first time, it repeats once an hour, as indicated in the message.
It happened on the podcast after the one you listened to, and it will surely happen on the next one. I can come back and report the time if it will be helpful.
