Hi, Jim,  Thanks for the update.  I'm pretty sure that my problem lies with
Asterisk, or the box it is running on....I installed the TrixBox 1.2.3, and
nmap shows that it isn't listening on 4569 at all.  SIP UDP shows up at
5060, but TCP is not showing...I'm not sure if it requires TCP.   I've got
no firewall configured on the Trixbox, so something obviously is not
working. I can't get out to VoicePulse or FWD on IAX2, or VoicePulse on SIP.
SIP extensions inside the router work fine between each other, and out to
the PSTN via an X100P card. 

I had FWD working many moons ago, directly from a Grandstream phone, so I
know that it all used to work....and H.323 videoconferencing and SightStream
also worked fine.  So, right now, I'm not blaming the internet connection or
Comcast.
-- L   

-----Original Message-----
From: Vermont Area Group of Unix Enthusiasts [mailto:[EMAIL PROTECTED] On
Behalf Of Jim Lawson
Sent: Sunday, November 19, 2006 1:29 PM
To: [email protected]
Subject: Re: comcast anyone?

Hi Larry,

FWIW, I "moved" from Adelphia to Comcast IPs and DNS servers on Thursday 
night, and although I had to change a few DNS forwarders, I haven't had 
any troubles.  I run a Linksys WRT54G running OpenWRT, a Debian server 
which also runs Asterisk, and various other machines.  I haven't had any 
troubles with inbound IAX2 (udp 4569) via Comcast, although I haven't 
tried SIP yet.  None of the ports I used under Adelphia have been 
blocked.  Adelphia did block inbound TCP port 80 and 25 long ago, so I 
had moved those to alternate ports - where they still work under Comcast.

Give me a ring on FWD (812316) if you want to try it out.

Jim

Lawrence Keyes wrote:
> Interesting..I just noticed that myself, that the Adelphia stuff was
moved,
> and Comcast took over.  Now, I'm wondering if the upstream DNS servers
etc.
> have all been changed. In any case, I didn't notice any change in
behavior;
> it was only when I hit Shields-up that I found my public IP address (which
> is usually pretty sticky) had changed. 
>
> That I could deal with.  However, I'm trying to get my Asterisk box to
work
> with a VOIP provider and need to have ports 5060 and 4569 open and
according
> Shields-Up these are both closed  I can't tell yet, if this is rather due
to
> my router (a DLink  DI-604) or if in fact they *are* blocking those ports.
> Putting the box in the router's DMZ doesn't seem to help.   
>
> If anyone has insight on how to troubleshoot this....I'd love to know.   
>   

Reply via email to