VOIP/SIP issues

Report wireless and/or network connectivity problems in this forum.

Moderator: Moderators

Post Reply
virusmoere
Posts: 3
Joined: Wed Jun 06, 2012 8:12 am

VOIP/SIP issues

Post by virusmoere »

Hi everyone,

I currently try to get my SIP PBX (Siemens Gigaset C470IP) running. Unfortunately only outgoing calls are working. Incomming calls arrive at the pppoe (tcpdump) interface but will not be redirected to the SIP PBX. I think it is a NAT/conntrack issue...

Does anyone have a SIP device running with gargoyle?

There are screenshots of the PBX configuration attached.


Thanks and best regards,
Daniel
c470_2.JPG
c470_2.JPG (16.23 KiB) Viewed 4788 times
c470_1.JPG
c470_1.JPG (56.45 KiB) Viewed 4788 times

pbix
Developer
Posts: 1373
Joined: Fri Aug 21, 2009 5:09 pm

Re: VOIP/SIP issues

Post by pbix »

I am using a SIP phone behind Gargoyle for many years and use no special settings to make it work.

I have a DSL link with bridged modem. Do you have that? I think perhaps a bridged modem is necessary as Gargoyle needs to have the public IP address and not be double nated.

Also, I have noticed that only one SIP device on the LAN can work. If I have more than one then only the last one that registers seems to work.

If you need more than one SIP registered device behind Gargoyle you probably need to install siproxd and properly configure.

This is a subject you should take up over at OpenWRT.org if you need more help since Gargoyle depends on OpenWRT in this regard. Any SIP routing that is done is handled by OpenWRT.
Linksys WRT1900ACv2
Netgear WNDR3700v2
TP Link 1043ND v3
TP-Link TL-WDR3600 v1
Buffalo WZR-HP-G300NH2
WRT54G-TM

virusmoere
Posts: 3
Joined: Wed Jun 06, 2012 8:12 am

Re: VOIP/SIP issues

Post by virusmoere »

Hi,

i found this in the kernel log:

Code: Select all

Jun  6 21:12:55 SkyNet user.emerg kernel: nf_ct_sip: dropping packetIN= OUT=br-lan SRC=212.227.18.131 DST=192.168.1.3 LEN=1988 TOS=0x10 PREC=0x00 TTL=58 ID=33175 PROTO=UDP SPT=5060 DPT=5060 LEN=1968
Jun  6 21:12:55 SkyNet user.emerg kernel: nf_ct_sip: dropping packetIN= OUT=br-lan SRC=212.227.18.131 DST=192.168.1.3 LEN=1988 TOS=0x10 PREC=0x00 TTL=58 ID=33176 PROTO=UDP SPT=5060 DPT=5060 LEN=1968
Jun  6 21:12:56 SkyNet user.emerg kernel: nf_ct_sip: dropping packetIN= OUT=br-lan SRC=212.227.18.131 DST=192.168.1.3 LEN=1988 TOS=0x10 PREC=0x00 TTL=58 ID=33177 PROTO=UDP SPT=5060 DPT=5060 LEN=1968
Jun  6 21:12:59 SkyNet user.emerg kernel: nf_ct_sip: dropping packetIN= OUT=br-lan SRC=212.227.18.131 DST=192.168.1.3 LEN=1988 TOS=0x10 PREC=0x00 TTL=58 ID=33178 PROTO=UDP SPT=5060 DPT=5060 LEN=1968
Jun  6 21:12:59 SkyNet user.emerg kernel: nf_ct_sip: dropping packetIN= OUT=br-lan SRC=212.227.18.132 DST=192.168.1.3 LEN=1988 TOS=0x10 PREC=0x00 TTL=58 ID=54147 PROTO=UDP SPT=5060 DPT=5060 LEN=1968
Jun  6 21:13:00 SkyNet user.emerg kernel: nf_ct_sip: dropping packetIN= OUT=br-lan SRC=212.227.18.132 DST=192.168.1.3 LEN=1988 TOS=0x10 PREC=0x00 TTL=58 ID=54148 PROTO=UDP SPT=5060 DPT=5060 LEN=1968
Jun  6 21:13:01 SkyNet user.emerg kernel: nf_ct_sip: dropping packetIN= OUT=br-lan SRC=212.227.18.132 DST=192.168.1.3 LEN=1988 TOS=0x10 PREC=0x00 TTL=58 ID=54149 PROTO=UDP SPT=5060 DPT=5060 LEN=1968
Jun  6 21:13:03 SkyNet user.emerg kernel: nf_ct_sip: dropping packetIN= OUT=br-lan SRC=212.227.18.132 DST=192.168.1.3 LEN=1988 TOS=0x10 PREC=0x00 TTL=58 ID=54150 PROTO=UDP SPT=5060 DPT=5060 LEN=1968
Anyone know what this mean? 192.168.1.3 is the C470IP. These loglines appear if someone tries to call one of my SIP Numbers...


Regards,
Daniel

virusmoere
Posts: 3
Joined: Wed Jun 06, 2012 8:12 am

Re: VOIP/SIP issues

Post by virusmoere »

Hi,

does no one know what the lines in the kernel log mean?


Thanks!


Regards,
Daniel

razor85
Posts: 1
Joined: Sun Jul 22, 2012 6:30 am

Re: VOIP/SIP issues

Post by razor85 »

Hi,

I think that I've encountered similar issue.
Check what is your registration interval to sip server. In my case it was 3600s. and lifetime for UDP connections in Gargoyle is by default sorter (300s or sth.) the connection timed out before next registration could happen.
I've changed registration interval to 600s and UDP timeout to 900s - now everything works perfectly.

Hope that helps!

Post Reply