[VoIP] SIP/firewall problem - the saga

[Ian Jolly]

Chad asked if I'd got NAT=yes  - I have!

The Fritz AVM router works OK through one of its two VoIP ports but does 
that work through the NAT ? Or is it on the 'dirty' side of the NAT?

That is a point about the SPA end being NAT'ed - I'm sure it will be.   I'll 
try changing the 'nat=   ' setting and see if we have any success!  My 
sip.conf settings (excluding the individual settings)

[general]
context=default           ; Default context for incoming calls
bindport=5060           ; UDP Port to bind to (SIP standard port is 5060)
bindaddr=0                ; IP address to bind to (0.0.0.0 binds to all)
srvlookup=yes           ; Enable DNS SRV lookups on outbound calls
qualify=yes
externip = 81.174.170.48  ; Address that we're going to put in outbound SIP 
messages
                                  ; if we're behind a NAT - My fixed IP
localnet=192.168.1.0/255.255.255.0; All RFC 1918 addresses are local 
networks
nat=yes                         ;Global NAT settings  (Affects all peers and 
users)

I'll let you know how we get on!

Tnx

Ian


----- Original Message ----- 
From: "Chad Perkins" <chad at maine.maine.edu>
To: "Voice Over IP Tandem for Analog Switches" <voip at ckts.info>
Sent: Monday, November 13, 2006 4:37 AM
Subject: Re: [VoIP] SIP/firewall problem - the saga


>> 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
>