7 Jun
2004
7 Jun
'04
8:09 a.m.
On 03-06 09:31, hasseman(a)slackware.se wrote:
So what exactly is (or is not) happening ? Does ser get any messages
from outside ? Use ngrep to see if there is any SIP traffic.
Jan.
Check the logs
(usually /var/log/daemon or /var/log/messages), there
should be some trace of unsuccessful SER startup.
Jan.
I switched on debuglevel 9 in my ser.cfg. It gived me "unable to
connect
to mysql db". So i wonderd what that might be and tried to log on with
mysqlcc to determine possible auth problems. Ehum... the user ser didnt
log on to the mysql db with proper password....shame on me!
Regarding the NAT issue im still not quiet shure... The server is behind a
NAT firewall that is not SIP-aware. All of the issues ive seen so far has
being about SIP-Clients behind NAT-firewall but in my case it is (so far)
the server behind firewall and the clients behind modems. I guess
client,server or whatever the NAT still ignore the SIP packages eaven
though the port 5060 is forwaded properly to the SER-server. Ive found
some ipmasquerading hints regarding SIP so my next logical step if nothing
comes up ill just configure a linux router.