Discussion:
Is Comcast blocking my VOIP?
(too old to reply)
M.L.
2008-08-05 08:45:32 UTC
Permalink
I was successfully using my Voicestick voip to call out when I had AT&T dsl.
However, now that I've switched to a wireless LAN using Comcast, I can't
make my outbound calls with my Voicestick softphone. It gives me a code
12002 timeout error when I try to authenticate.

I've tried connecting with my software firewall to allow, and with it
completely turned off. I tried port-forwarding the recommended Voicestick
ports to my computer while my software firewall was off. I finally tried
putting my computer in the router's DMZ with my software firewall turned
off. I just couldn't get a call to go through. I can't think of anything
that's stopping the show except Comcast. Could there be another reason?
Thanks.
Thomas T. Veldhouse
2008-08-05 13:04:51 UTC
Permalink
Post by M.L.
I was successfully using my Voicestick voip to call out when I had AT&T dsl.
However, now that I've switched to a wireless LAN using Comcast, I can't
make my outbound calls with my Voicestick softphone. It gives me a code
12002 timeout error when I try to authenticate.
I've tried connecting with my software firewall to allow, and with it
completely turned off. I tried port-forwarding the recommended Voicestick
ports to my computer while my software firewall was off. I finally tried
putting my computer in the router's DMZ with my software firewall turned
off. I just couldn't get a call to go through. I can't think of anything
that's stopping the show except Comcast. Could there be another reason?
Thanks.
Comcast and 3rd party VoIP works just fine. You almost certainly have your
router and/or adapter (stick) configured incorrectly. Can you hook that
"VoiceStick" directly to your cable modem [or is it a USB bit that connects to
a PC}?
--
Thomas T. Veldhouse

Religion is a crutch, but that's okay... humanity is a cripple.
M.L.
2008-08-05 18:48:16 UTC
Permalink
Post by Thomas T. Veldhouse
Post by M.L.
I was successfully using my Voicestick voip to call out when I had AT&T dsl.
However, now that I've switched to a wireless LAN using Comcast, I can't
make my outbound calls with my Voicestick softphone. It gives me a code
12002 timeout error when I try to authenticate.
I've tried connecting with my software firewall to allow, and with it
completely turned off. I tried port-forwarding the recommended Voicestick
ports to my computer while my software firewall was off. I finally tried
putting my computer in the router's DMZ with my software firewall turned
off. I just couldn't get a call to go through. I can't think of anything
that's stopping the show except Comcast. Could there be another reason?
Thanks.
Comcast and 3rd party VoIP works just fine. You almost certainly have your
router and/or adapter (stick) configured incorrectly. Can you hook that
"VoiceStick" directly to your cable modem [or is it a USB bit that connects to
a PC}?
I'm not using the stick, just their softphone.
Thomas T. Veldhouse
2008-08-06 17:15:52 UTC
Permalink
Post by M.L.
I'm not using the stick, just their softphone.
Firewall issue ... either on your computer or on your router ... I am about
100% sure of this. I am 100% sure that Comcast is not blocking VoIP. They
took enough heat with their interference with torrents to even consider
blocking VoIP for anti-competitive reasons.
--
Thomas T. Veldhouse

Religion is a crutch, but that's okay... humanity is a cripple.
M.L.
2008-08-07 02:16:27 UTC
Permalink
Post by Thomas T. Veldhouse
Post by M.L.
I'm not using the stick, just their softphone.
Firewall issue ... either on your computer or on your router ... I am about
100% sure of this. I am 100% sure that Comcast is not blocking VoIP.
They
took enough heat with their interference with torrents to even consider
blocking VoIP for anti-competitive reasons.
Thanks for your reply. I had already tried shutting down my router and
software firewalls with no success. Turns out that my WinXP Telephony
service was set to Manual. After setting it to Started->Automatic and
rebooting, I could make outgoing calls.
RP
2009-07-30 04:45:32 UTC
Permalink
I believe VoIP does not work if you are using a private IP address (NAT)
behind your router/firewall. It could also be a software issue with your
router. Check with your router vendor for VoIP support and NAT.

http://www.velocityreviews.com/forums/t233646-the-trouble-with-nat-and-voip.html

RP
Post by M.L.
I was successfully using my Voicestick voip to call out when I had AT&T
dsl. However, now that I've switched to a wireless LAN using Comcast, I
can't make my outbound calls with my Voicestick softphone. It gives me a
code 12002 timeout error when I try to authenticate.
I've tried connecting with my software firewall to allow, and with it
completely turned off. I tried port-forwarding the recommended Voicestick
ports to my computer while my software firewall was off. I finally tried
putting my computer in the router's DMZ with my software firewall turned
off. I just couldn't get a call to go through. I can't think of anything
that's stopping the show except Comcast. Could there be another reason?
Thanks.
M.L.
2009-08-07 12:33:45 UTC
Permalink
Post by RP
Post by M.L.
I was successfully using my Voicestick voip to call out when I had AT&T
dsl. However, now that I've switched to a wireless LAN using Comcast, I
can't make my outbound calls with my Voicestick softphone. It gives me a
code 12002 timeout error when I try to authenticate.
I've tried connecting with my software firewall to allow, and with it
completely turned off. I tried port-forwarding the recommended Voicestick
ports to my computer while my software firewall was off. I finally tried
putting my computer in the router's DMZ with my software firewall turned
off. I just couldn't get a call to go through. I can't think of anything
that's stopping the show except Comcast. Could there be another reason?
I believe VoIP does not work if you are using a private IP address (NAT)
behind your router/firewall. It could also be a software issue with your
router. Check with your router vendor for VoIP support and NAT.
http://www.velocityreviews.com/forums/t233646-the-trouble-with-nat-and-voip.html
Thanks for your reply. I found the problem was that the Telephony
Service was not turned on on my system.

Loading...