Thanks Iñaki, > > 2010/11/19 Iñaki Baz Castillo <i...@aliax.net>: >> 2010/11/19 Danny Dias <ing.diasda...@gmail.com>: >>> I start Kamailio with /etc/init.d/kamailio restart: >>> >>> <Kamailio-Testing> r...@kamailio-danndp:~# /etc/init.d/kamailio restart >>> Restarting Kamailio SIP server: kamailioListening on >>> udp: 212.230.19.191 [212.230.19.191]:5060 >>> Aliases: >>> udp: Kamailio-DANNDP:5060 >> >> The daemonized mode of Kamailio 3.X has been improved so it would >> result in error exit status in case the main process fails to start >> (so by invoking init service you would receive an error and exit >> status != 0). > That's good to know. > >> >> However in Kamailio 1.5.X this is not true, and the daemon mode exits >> with zero (success) without waiting for the main process to properly >> start, so you get "success" after invoking the init service but >> Kamailio fails to start (due to errors in modules configuration, >> listening IP's....). > I decided to comment the following lines in my kamailio.cfg:
#loadmodule "auth.so"
#loadmodule "auth_db.so"
#loadmodule "alias_db.so"
#modparam("auth_db", "calculate_ha1", yes)
#modparam("auth_db", "password_column", "password")
And now, restarting kamailio works:
<Kamailio-Testing> r...@kamailio-danndp:/home# /etc/init.d/kamailio restart
Restarting Kamailio SIP server: kamailioListening on
udp: 212.230.19.191 [212.230.19.191]:5060
Aliases:
udp: Kamailio-DANNDP:5060
<Kamailio-Testing> r...@kamailio-danndp:/home# ps -ef | grep kamailio
root 20482 1 0 19:22 ? 00:00:00 /usr/sbin/kamailio -P
/var/run/kamailio/kamailio.pid -m 64 -u root -g root
root 20483 20482 0 19:22 ? 00:00:00 /usr/sbin/kamailio -P
/var/run/kamailio/kamailio.pid -m 64 -u root -g root
root 20484 20482 0 19:22 ? 00:00:00 /usr/sbin/kamailio -P
/var/run/kamailio/kamailio.pid -m 64 -u root -g root
root 20485 20482 0 19:22 ? 00:00:00 /usr/sbin/kamailio -P
/var/run/kamailio/kamailio.pid -m 64 -u root -g root
root 20486 20482 0 19:22 ? 00:00:00 /usr/sbin/kamailio -P
/var/run/kamailio/kamailio.pid -m 64 -u root -g root
root 20487 20482 0 19:22 ? 00:00:00 /usr/sbin/kamailio -P
/var/run/kamailio/kamailio.pid -m 64 -u root -g root
root 20488 20482 0 19:22 ? 00:00:00 /usr/sbin/kamailio -P
/var/run/kamailio/kamailio.pid -m 64 -u root -g root
root 20489 20482 0 19:22 ? 00:00:00 /usr/sbin/kamailio -P
/var/run/kamailio/kamailio.pid -m 64 -u root -g root
root 20490 20482 0 19:22 ? 00:00:00 /usr/sbin/kamailio -P
/var/run/kamailio/kamailio.pid -m 64 -u root -g root
root 20491 20482 0 19:22 ? 00:00:00 /usr/sbin/kamailio -P
/var/run/kamailio/kamailio.pid -m 64 -u root -g root
root 20492 20482 0 19:22 ? 00:00:00 /usr/sbin/kamailio -P
/var/run/kamailio/kamailio.pid -m 64 -u root -g root
root 20493 20482 0 19:22 ? 00:00:00 /usr/sbin/kamailio -P
/var/run/kamailio/kamailio.pid -m 64 -u root -g root
root 20495 20429 0 19:23 pts/0 00:00:00 grep kamailio
By the way, in my kamctlr i have the #STORE_PLAINTEXT_PW=1, that means
that it wont store the the passwords in the subscriber table...right¿?
Also, the REGISTER are having the same result:
interface: any
filter: (ip or ip6) and ( port 5060 )
match: 100
#
U 2010/11/19 19:25:14.239925 212.230.253.164:10091 -> 212.230.19.191:5060
REGISTER sip:212.230.19.191 SIP/2.0'
Via: SIP/2.0/UDP 10.134.16.164:10091;branch=z9hG4bK1590232060;rport'
From: <sip:1...@212.230.19.191>;tag=1251867918'
To: <sip:1...@212.230.19.191>'
Call-ID: 2022066534-1646...@ba.bde.bg.bge'
CSeq: 6878 REGISTER'
Contact:
<sip:1...@10.134.16.164:10091>;reg-id=2;+sip.instance="<urn:uuid:00000000-0000-1000-8000-000B821FA066>"'
Authorization: Digest username="101", realm="212.230.19.191",
nonce="4ce5bb3800000047aa806944ef2f6754dbff9fb1757db9ae",
uri="sip:212.230.19.191", response="1f0f04efa3e0271c6937007dc9fd77e7",
algorithm=MD5'
Max-Forwards: 70'
User-Agent: Grandstream GXV3140 1.0.1.1'
Supported: path'
Expires: 3600'
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, INFO,
REFER, UPDATE, MESSAGE'
Content-Length: 0'
'
#
U 2010/11/19 19:25:18.247925 212.230.253.164:10091 -> 212.230.19.191:5060
REGISTER sip:212.230.19.191 SIP/2.0'
Via: SIP/2.0/UDP 10.134.16.164:10091;branch=z9hG4bK1590232060;rport'
From: <sip:1...@212.230.19.191>;tag=1251867918'
To: <sip:1...@212.230.19.191>'
Call-ID: 2022066534-1646...@ba.bde.bg.bge'
CSeq: 6878 REGISTER'
Contact:
<sip:1...@10.134.16.164:10091>;reg-id=2;+sip.instance="<urn:uuid:00000000-0000-1000-8000-000B821FA066>"'
Authorization: Digest username="101", realm="212.230.19.191",
nonce="4ce5bb3800000047aa806944ef2f6754dbff9fb1757db9ae",
uri="sip:212.230.19.191", response="1f0f04efa3e0271c6937007dc9fd77e7",
algorithm=MD5'
Max-Forwards: 70'
User-Agent: Grandstream GXV3140 1.0.1.1'
Supported: path'
Expires: 3600'
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, INFO,
REFER, UPDATE, MESSAGE'
Content-Length: 0'
'
.
.
.
And never receiving and answer from Kamailio, attached you will find
my kamailio.cfg, if you can check it and tell me what should i check i
would appreciate it!!!
Regards
>
>>
>>
>>
>> --
>> Iñaki Baz Castillo
>> <i...@aliax.net>
>>
>
>
>
> --
> Ing. Danny Dias
> www.DannTEL.net
>
--
Ing. Danny Dias
www.DannTEL.net
kamailio.cfg
Description: Binary data
_______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
