Problems: 1. SER do not start properly after reboot. 2. Can´t not log on to SIP-server trough NAT.
Description: 1. SER do not start properly after reboot. First of all i must point out that i have no more than a couple of weeks experience. I downloaded the "Admin guide" and the "Dan Austin howto" as reference dokumentation to set up a basic SER server. I followed it step by step and tested it. I found out that ive got some problem with ser when i restarted the machine. I restarted the machine, startted ser with "ser start" witch gived me:
Listening on: 127.0.0.1[127.0.0.1]:5060 192.168.1.3[192.168.1.3]:5060
But when i was checking the status with "serctl monitor" It semed to me as ether the ser server or the ser_fifo was down cause it dident give me any status att all.
when i checked the lokal processes with "ps aux" it dident give me anything on "ser start" as it usualy do. So i tried out the default ser.cfg and it worked.... ps aux gived me "ser start". Then i tried the default ser.cfg with mysql auth support and it worked. I rebooted and the same problem all over again.
2. Can not log on to SIP-server trough NAT. I can make local connections and initiate calls but not trough my dial.mine.nu adress. I have routed port 5060-5062 in my firewall against the server machine.(i think it would be sufficient to at least log on) I can make connections against iptel.org reference server but not against my local server.
Enviromental variables: OS: Slackware 9.1 (Linux) client: Kphone and W-messenger. server: ser 0.8.12 Host-name:SIPserver.hasselan Domain: hasselan SIP-domain: SIPserver.hasselan Mysql: 4.0.18 external domain: dial.mine.nu
configurationsfile= default ser.cfg + auth modules and mysql support. following lines were edited:
www_authorise =SIPserver.hasselan www_challenge SIPserver.hasselan
Check the logs (usually /var/log/daemon or /var/log/messages), there should be some trace of unsuccessful SER startup.
Jan.
On 31-05 19:02, hasseman@slackware.se wrote:
Problems:
- SER do not start properly after reboot.
- Can´t not log on to SIP-server trough NAT.
Description:
- SER do not start properly after reboot.
First of all i must point out that i have no more than a couple of weeks experience. I downloaded the "Admin guide" and the "Dan Austin howto" as reference dokumentation to set up a basic SER server. I followed it step by step and tested it. I found out that ive got some problem with ser when i restarted the machine. I restarted the machine, startted ser with "ser start" witch gived me:
Listening on: 127.0.0.1[127.0.0.1]:5060 192.168.1.3[192.168.1.3]:5060
But when i was checking the status with "serctl monitor" It semed to me as ether the ser server or the ser_fifo was down cause it dident give me any status att all.
when i checked the lokal processes with "ps aux" it dident give me anything on "ser start" as it usualy do. So i tried out the default ser.cfg and it worked.... ps aux gived me "ser start". Then i tried the default ser.cfg with mysql auth support and it worked. I rebooted and the same problem all over again.
- Can not log on to SIP-server trough NAT.
I can make local connections and initiate calls but not trough my dial.mine.nu adress. I have routed port 5060-5062 in my firewall against the server machine.(i think it would be sufficient to at least log on) I can make connections against iptel.org reference server but not against my local server.
Enviromental variables: OS: Slackware 9.1 (Linux) client: Kphone and W-messenger. server: ser 0.8.12 Host-name:SIPserver.hasselan Domain: hasselan SIP-domain: SIPserver.hasselan Mysql: 4.0.18 external domain: dial.mine.nu
configurationsfile= default ser.cfg + auth modules and mysql support. following lines were edited:
www_authorise =SIPserver.hasselan www_challenge SIPserver.hasselan
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
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.
On 03-06 09:31, hasseman@slackware.se wrote:
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.
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.
-
hasseman＠slackware.se -
Jan Janak