If you use this product, we'll add it to your dashboard. If you work for the company that makes this product, we'll connect you with other employees. Got it, thanks!
I cannot upload my show, and I have been trying since Saturday, Oct. 4. It is now Oct. 7. Can someone please get back to me on this. I have tried from multiple computers.
I have 2 episodes that were recorded live. When I go to my account it shows the shows, the time, but no listen to recording or download button? The account name is ColderICE...Please advise?
Yesterday Morning, We added 33% more phone ports to our network - which has fixed the busy signals during our busy times on the network.
As Dave mentions on the Company Blog, this is a big step at resolving the system full issue on one-third of the nights on TalkShoe. You want more people to call in? Now we can handle even more callers, up to 300!
Dave also mentioned some statistics on the blog post about this, see it for the details.
How long does it take for an ended Podcast to be available for Download? Is it a specific time, or does the time of the Podcast? Will factors such as time of day affect anything?
Trying to pull up Talkshoe.com I get a network timeout error. Trying to ping talkshoe.com gives me a timeout error. Traceroute for both www and recordings does this:
1 1 ms 1 ms 1 ms 192.168.10.1
2 * * * Request timed out.
3 11 ms 12 ms 9 ms gig2-1-1.buffnyngr-pe02.nyroc.rr.com [98.0.0.169]
4 11 ms 9 ms 9 ms ten1-2-1.buffnyntw-pe01.nyroc.rr.com [98.0.1.105]
5 15 ms 12 ms 11 ms ten10-2-1.buffnylkw-pe03.nyroc.rr.com [98.0.1.157]
6 13 ms 12 ms 12 ms ten2-2-1.buffnylkw-pe01.nyroc.rr.com [98.0.1.173]
7 * 24 ms 19 ms ge-0-1-0.albynywav-rtr03.nyroc.rr.com [24.24.7.229]
8 25 ms 26 ms 24 ms ae-5-0.cr0.nyc30.tbone.rr.com [66.109.6.74]
9 38 ms 36 ms 25 ms ae-1-0.pr0.nyc20.tbone.rr.com [66.109.6.163]
10 40 ms 44 ms 32 ms te2-1.mpd01.jfk05.atlas.cogentco.com [154.54.13.185]
11 31 ms 53 ms 31 ms te2-4.ccr02.jfk02.atlas.cogentco.com [130.117.0.53]
12 31 ms 47 ms 31 ms te8-2.ccr02.dca01.atlas.cogentco.com [66.28.4.126]
13 30 ms 34 ms 42 ms vl3493.mpd01.dca02.atlas.cogentco.com [154.54.7.230]
14 34 ms 37 ms 40 ms te3-2.ccr02.iad01.atlas.cogentco.com [154.54.1.78]
15 31 ms 31 ms 31 ms gi2-0-0.core01.iad01.atlas.cogentco.com [154.54.5.33]
16 36 ms 41 ms 43 ms po6-0.core01.pit02.atlas.cogentco.com [154.54.3.26]
17 220 ms 53 ms 222 ms gi-3-2.a02.pitbpa05.us.ce.verio.net [199.239.218.202]
18 39 ms 38 ms 39 ms 72.22.31.250.nauticom.net [72.22.31.250]
19 39 ms 40 ms 37 ms 72.22.30.113.nauticom.net [72.22.30.113]
20 53 ms 39 ms 38 ms 72.22.30.113.nauticom.net [72.22.30.113]
21 38 ms 41 ms 41 ms 72.22.30.113.nauticom.net [72.22.30.113]
22 39 ms 41 ms 41 ms 72.22.30.113.nauticom.net [72.22.30.113]
23 41 ms 40 ms 72 ms 72.22.30.113.nauticom.net [72.22.30.113]
24 38 ms 37 ms 58 ms 72.22.30.113.nauticom.net [72.22.30.113]
25 39 ms 41 ms 39 ms 72.22.30.113.nauticom.net [72.22.30.113]
26 49 ms 38 ms 42 ms 72.22.30.113.nauticom.net [72.22.30.113]
27 46 ms 41 ms 41 ms 72.22.30.113.nauticom.net [72.22.30.113]
28 41 ms 40 ms 47 ms 72.22.30.113.nauticom.net [72.22.30.113]
29 39 ms 38 ms 41 ms 72.22.30.113.nauticom.net [72.22.30.113]
30 40 ms 37 ms 48 ms 72.22.30.113.nauticom.net [72.22.30.113]
I'm assuming that my show will start up as scheduled since the phone service is answering. My show is scheduled for 8:30pm. I do know that the site was up until just around noon today and then stopped responding.
I host OSD- Obsessive Sneaker Disorder and our weekly talk show took place last night. We ran into an issue around 10 pm EST with some people logging into the show and those that wanted to stream the show couldn't hear it.
Was there something going on with the servers that may have caused this issue?
Secondly, I checked my call stat numbers and it's only crediting me for 1 Live Audio Streamer, when I know I had at least 11 through Talkshoe.
I look forward to hearing from someone soon. Peace!
Getting "on the call" via VOIP, using SIP client software on Linux, was working fine until precisely last Sunday; now I get error "Remote user cleared the call", which apparently means the Talkshoe system is disconnecting me. Prior to this Sunday past, things were working fine, but now I get the same error repeatedly. FWIW the SIP client software is 'Ekiga'. Has TalkShoe cut me off for some reason?
I am organizing a series of Talkcasts featuring some high profile spiritual teachers. We may well get telephone audiences in or around the max of 250 and webcast audiences in the thousands. Can someone reassure me that the system will be reliable for such big audiences?
Also, what happens if the audience is larger than the Talkshoe capacity? E.g., if more than 250 callers call in, what will happen? Will the 251st and beyond callers get an error message? Will they be told to try the audio webcast? Similarly, what would happen if, say, 10,000 people tried to listen to the audio webcast? Is there a max number, beyond which participants would be shut out of the webcast? (ie, would they receive a message saying the webcast is full?) I want to be reassured that in the event we get a very large audience, the whole system won't crash.
I would like to see a new feature where live podcasts have an internet radio stream.
Currently the chat page enables people to listen to the show, but often it is difficult to get working properly, if at all. Utilizing a simple audio stream would allow people to use the audio player of their choice to get the content.
If the chat page is having issues, which seems pretty common, the only way to listen to a show live is via a voip client.
The voip client utilizes two-way communication, even if it is muted from within the client. A radio stream would be uni-directional, and would be much much easier for listeners to use.
While it may add an extra layer of complexity on the server side, it should help with bandwidth issues on your service. It would also make listening to a live podcast much much easier since most computers can handle radio streams without problem.
With less bandwidth wasted, quality and stability may improve for Talkshoe.
I am the host of a regularly scheduled show, but I want to be able to establish a co-host, allowing another member to record and control the show in my absence. How can I do that?