[VoIP] SIP/firewall problem - the saga

[Chad Perkins]

> Hi All
> from the other side of the Pond!
> Glad to know that we aren't the only ones having problems with SIP.
> 
> When I do a 'sip show peers' mine are all 5060.  However when I do an
> 'iax2 show peers' I've got one  on Port 37657, it is on my own network
> - AT323/AT323      81.174.170.48   (D)  255.255.255.255  37657 OK (833 ms)
> 
> We've had success with one single CNET number off my *box working with
> SIP to a Fritz AVM router with two VoIP ports on it.  Works OK
> bothways (although we haven't sorted out the dyndns set yet).
> 
> However if we transfer exactly the same settings to a Sipura 2000 at
> the same location - it will not register and I can't see it when I do
> a 'sip show peers'.
> 
> Anyone any ideas?  Anyone got a working configuration for a Sipura
> 2000 end?

Is the SPA nated?  Do you have 'nat=yes' in sip.conf for that device (that killed my 
first one).  I wouldn't think the 2000 would be all that different from the 2002 I posted 
the other day.

[snip] 
> I am hosting another ATA - a Draytek 2600V with two VoIP ports one of
> which is on CNET. We've got the SIP working OK bothways but every so
> often  I get the following message at the CLI>-
> 
> Nov 12 19:35:35 NOTICE[2485]: chan_sip.c:11328 sip_poke_noanswer: Peer
> 'jgriffiths' is now UNREACHABLE!  Last qualify: 226 Nov 12 19:35:45
> NOTICE[2485]: chan_sip.c:9689 handle_response_peerpoke: Peer
> 'jgriffiths' is now REACHABLE! (214ms / 2000ms)
> 
> The Draytek becomes 'unreachable for ten seconds at a time every few
> minutes. During this period you can't dial into the number.  However
> it doesn't interrupt an existing call.  Anyone any idea what is
> causing this 'unreachable/reachable' situation?  Incidentally the
> 'chan_sip.c:11328' and 'sip.c:9689'  are always the same in the error
> messages - are they SIP ports?
> Ian Jolly

No.  I think they are code line numbers.  This message is usually a sign that the 
network is "down" somewhere and they can't communicate; but if you able to talk as 
this problem comes and goes then that is weird.

chad
 
> ----- Original Message ----- 
> From: "Jayson Smith" <ratguy at bellsouth.net>
> To: "Voice Over IP Tandem for Analog Switches" <voip at ckts.info>
> Sent: Saturday, November 11, 2006 6:33 PM
> Subject: Re: [VoIP] SIP/firewall problem - the saga
> 
> 
> > Hi,
> > HMMM, sound familiar?  Of course, in my situation, I'm appearing to
> > be accepting IAX2 connections on a random high port rather than 4569
> > (is that the right port or am I losing my mind too?).  Yeah, some
> > NAT systems do really strange things! Jayson.
> >
> > ----- Original Message ----- 
> > From: "Chad Perkins" <chad at maine.maine.edu>
> > To: "Voice Over IP Tandem for Analog Switches" <voip at ckts.info>
> > Sent: Saturday, November 11, 2006 12:33 PM Subject: Re: [VoIP]
> > SIP/firewall problem - the saga
> >
> >
> >> > I hate SIP.
> >> > I don't know if this will help, but, when I do a "sip show
> >> > peers," I get some really odd ports for Dennis and for Jim:
> >> >
> 
> 
> _______________________________________________
> VoIP mailing list
> VoIP at ckts.info
> http://lists.ckts.info/mailman/listinfo/voip
> Project Web Page: http://www.ckts.info/
> 
> 
> 
> -- 
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.1.409 / Virus Database: 268.14.3/530 - Release Date:
> 11/11/06
>