Router: Linux Suse 9.2
Konfig Firewall # Erlaube SIPGATE
$IPTABLES -N sip_gate $IPTABLES -A INPUT -m udp -p udp -i $DEV_INET --dport 5060 -j sip_gate $IPTABLES -A INPUT -m udp -p udp -i $DEV_INET --dport 5004:5011 -j sip_gate $IPTABLES -A sip_gate -j ACCEPT
Konfiguration Grandstream and Sipproxd like Online Doc, Chapter 6.2.
Message of siproxd:
15:55:00 INFO:siproxd.c:189 siproxd-0.5.11-3032 i686-pc-linux-gnu starting up 15:55:00 INFO:sock.c:65 bound to port 5060 15:55:00 INFO:siproxd.c:262 siproxd-0.5.11-3032 i686-pc-linux-gnu started 15:55:19 ERROR:sock.c:175 sendto() [217.10.79.9:5060 size=537] call failed: Operation not permitted 15:55:19 ERROR:sock.c:175 sendto() [217.10.79.9:5060 size=537] call failed: Operation not permitted 15:55:21 ERROR:sock.c:175 sendto() [217.10.79.9:5060 size=537] call failed: Operation not permitted
Any Idea?
Greets Qli
Are you using SELinux? http://www.nsa.gov/selinux/
There seem to be other applications that show a similar behavior (failing sendto() call) with SELinux enabled Linux. Check http://www.google.ch/search?hl=de&q=SELinux+sendto+EPERM&btnG=Suche&meta=
/Thomas
Log in to post a comment.
Router: Linux Suse 9.2
Konfig Firewall
# Erlaube SIPGATE
$IPTABLES -N sip_gate
$IPTABLES -A INPUT -m udp -p udp -i $DEV_INET --dport 5060 -j sip_gate
$IPTABLES -A INPUT -m udp -p udp -i $DEV_INET --dport 5004:5011 -j sip_gate
$IPTABLES -A sip_gate -j ACCEPT
Konfiguration Grandstream and Sipproxd like Online Doc, Chapter 6.2.
Message of siproxd:
15:55:00 INFO:siproxd.c:189 siproxd-0.5.11-3032 i686-pc-linux-gnu starting up
15:55:00 INFO:sock.c:65 bound to port 5060
15:55:00 INFO:siproxd.c:262 siproxd-0.5.11-3032 i686-pc-linux-gnu started
15:55:19 ERROR:sock.c:175 sendto() [217.10.79.9:5060 size=537] call failed: Operation not permitted
15:55:19 ERROR:sock.c:175 sendto() [217.10.79.9:5060 size=537] call failed: Operation not permitted
15:55:21 ERROR:sock.c:175 sendto() [217.10.79.9:5060 size=537] call failed: Operation not permitted
Any Idea?
Greets Qli
Are you using SELinux? http://www.nsa.gov/selinux/
There seem to be other applications that show a similar behavior
(failing sendto() call) with SELinux enabled Linux. Check http://www.google.ch/search?hl=de&q=SELinux+sendto+EPERM&btnG=Suche&meta=
/Thomas