[OpenSIPS-Users] Dialog default timeout issue
Dear all,
I have been using the automatic dialog termination feature by setting the
dialog default timer (modparam("dialog", "default_timeout", 1800) and
create_dialog(“B”). This function had been working normally for weeks but it
turned abnormal in the last few days. Specifically, the OpenSIPS server
would terminate the calls later than the time at which the timer expired
(e.g., the timeout value is 30 minutes but the server terminated the calls
after the calls have been lasting 35 minutes).
When running opensipsctl fifo dlg_list, I found the timeout was correct but
kept varying (increased slowly and sometime stayed fixed). Besides, the
following messages are shown in the log many times
CRITICAL:core:timer_ticker: timer handler lasted (272 us)
for more than timer tick (100 us) -> potential timer shifting
CRITICAL:core:timer_ticker: timer handler lasted (381 us) for
more than timer tick (100 us) -> potential timer shifting
I had no idea about any relevance between ``late call termination’’ and
``timer shifting’’. I use OpenSIP version 1.9.0. Does anyone encounter
similar issue? Any comment is greatly appreciated.
Best wishes,
Chen-Che
--
View this message in context:
http://opensips-open-sip-server.1449251.n2.nabble.com/Dialog-default-timeout-issue-tp7595155.html
Sent from the OpenSIPS - Users mailing list archive at Nabble.com.
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Dialog default timeout issue
Hi Chen-Che,
Those logs are really relevant to your dialog expire problem. What those
logs say is that some timer routines (like ds-pinger or tm-timer) took
very long to execute ( like 2 or 4 seconds) and this leads to delays in
the execution of the following timer routines (the timer process gets
delayed). This is a limitation of 1.x OpenSIPS versions, where timers
are executed in sequential order in a single process (and if one gets
slow, it will affect the other too).
The ides is to address the timer routines reported as being slow. The
tm-timer can be moved into a separate process :
http://www.opensips.org/html/docs/modules/1.9.x/tm.html#id294499
For the dispatcher pinger - how many destinations do you have in the
list ? also, do you have some TCP destinations in there ?
Best regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 03.02.2015 10:05, microx wrote:
Dear all,
I have been using the automatic dialog termination feature by setting the
dialog default timer (modparam("dialog", "default_timeout", 1800) and
create_dialog(“B”). This function had been working normally for weeks but it
turned abnormal in the last few days. Specifically, the OpenSIPS server
would terminate the calls later than the time at which the timer expired
(e.g., the timeout value is 30 minutes but the server terminated the calls
after the calls have been lasting 35 minutes).
When running opensipsctl fifo dlg_list, I found the timeout was correct but
kept varying (increased slowly and sometime stayed fixed). Besides, the
following messages are shown in the log many times
CRITICAL:core:timer_ticker: timer handler lasted (272 us)
for more than timer tick (100 us) -> potential timer shifting
CRITICAL:core:timer_ticker: timer handler lasted (381 us) for
more than timer tick (100 us) -> potential timer shifting
I had no idea about any relevance between ``late call termination’’ and
``timer shifting’’. I use OpenSIP version 1.9.0. Does anyone encounter
similar issue? Any comment is greatly appreciated.
Best wishes,
Chen-Che
--
View this message in context:
http://opensips-open-sip-server.1449251.n2.nabble.com/Dialog-default-timeout-issue-tp7595155.html
Sent from the OpenSIPS - Users mailing list archive at Nabble.com.
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Opensips tls and certificate issue
Hi Martin, The relevant log is: Feb 3 06:18:36 [3626] ERROR:core:tls_accept: New TLS connection from 123.12.28.14(my_ip):50761 failed to accept: rejected by client So, the client opens a connection to OpenSIPS, OpenSIPS accepts the connection, but the connection setup fails as the client rejects the certificate sent by OpenSIPS. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 03.02.2015 05:24, martin-n martin-n wrote: Hello. I'am pretty new with opensips, so installed the latest opensips version *opensips 2.1.1dev-tls (x86_64/linux), *to make a sip server. I configured it to use tls. I generated the certificates according to this tutorial: https://github.com/antonraharja/book-opensips-101/blob/master/content/3.2.%20SIP%20TLS%20Secure%20Calling.mediawiki Then i did setup the blink. I took *cacert.pem* from rootCA folder and set it up as a *Certificate Authority File. *In the account options i did setup the certificate file, *server-calist.pem*. I also did add the private key to the client version of *server-calist.pem* file. But when i try to log-in to my server i get: Feb 3 06:18:36 [3630] DBG:core:probe_max_sock_buff: getsockopt: snd is initially 425984 Feb 3 06:18:36 [3630] INFO:core:probe_max_sock_buff: using snd buffer of 416 kb Feb 3 06:18:36 [3630] INFO:core:init_sock_keepalive: -- TCP keepalive enabled on socket Feb 3 06:18:36 [3630] DBG:core:print_ip: tcpconn_new: new tcp connection to: 123.12.28.14(my_ip) Feb 3 06:18:36 [3630] DBG:core:tcpconn_new: on port 50761, type 3 Feb 3 06:18:36 [3630] DBG:core:tls_tcpconn_init: entered: Creating a whole new ssl connection Feb 3 06:18:36 [3630] DBG:core:tls_tcpconn_init: looking up socket based TLS server domain [my_server_ip:7061] Feb 3 06:18:36 [3630] DBG:core:tls_find_server_domain: virtual TLS server domain not found, Using default TLS server domain settings Feb 3 06:18:36 [3630] DBG:core:tls_tcpconn_init: found socket based TLS server domain [0.0.0.0:0] Feb 3 06:18:36 [3630] DBG:core:tls_tcpconn_init: Setting in ACCEPT mode (server) Feb 3 06:18:36 [3630] DBG:core:tcpconn_add: hashes: 795, 1 Feb 3 06:18:36 [3630] DBG:core:handle_new_connect: new connection: 0x7fb5b3e82170 25 flags: 0002 Feb 3 06:18:36 [3630] DBG:core:send2child: to tcp child 0 0(3626), 0x7fb5b3e82170 rw 1 Feb 3 06:18:36 [3626] DBG:core:handle_io: We have received conn 0x7fb5b3e82170 with rw 1 Feb 3 06:18:36 [3626] DBG:core:io_watch_add: [TCP_worker] io_watch_add op on 21 (0x89a400, 21, 8, 0x7fb5b3e82170,1), fd_no=2 Feb 3 06:18:36 [3626] DBG:core:tcp_read_req: Using the global ( per process ) buff Feb 3 06:18:36 [3626] DBG:core:tls_update_fd: New fd is 21 Feb 3 06:18:36 [3626] ERROR:core:tls_accept: New TLS connection from 123.12.28.14(my_ip):50761 failed to accept: rejected by client Feb 3 06:18:36 [3626] DBG:core:io_watch_del: [TCP_worker] io_watch_del op on index 1 21 (0x89a400, 21, 1, 0x10,0x3) fd_no=3 called Feb 3 06:18:36 [3626] INFO:core:io_watch_del: [TCP_worker] size=3, fd array is 17 21 3 Feb 3 06:18:36 [3626] INFO:core:io_watch_del: [TCP_worker] size=3, prio array is 2 2 3 Feb 3 06:18:36 [3626] INFO:core:io_watch_del: [TCP_worker] size=2, fd array is 17 3 Feb 3 06:18:36 [3626] INFO:core:io_watch_del: [TCP_worker] size=3, prio array is 1 1 2 Feb 3 06:18:36 [3626] DBG:core:release_tcpconn: releasing con 0x7fb5b3e82170, state -2, fd=21, id=1 Feb 3 06:18:36 [3626] DBG:core:release_tcpconn: extra_data 0x7fb5b3e822f0 Feb 3 06:18:36 [3630] DBG:core:handle_tcp_child: reader response= 7fb5b3e82170, -2 from 0 Feb 3 06:18:36 [3630] DBG:core:tcpconn_destroy: destroying connection 0x7fb5b3e82170, flags 0002 Feb 3 06:18:36 [3630] DBG:core:tls_close: closing TLS connection Feb 3 06:18:36 [3630] DBG:core:tls_update_fd: New fd is 25 Feb 3 06:18:36 [3630] DBG:core:tls_shutdown: shutdown successful Feb 3 06:18:36 [3630] DBG:core:tls_tcpconn_clean: entered My config looks like so: auto_aliases=no listen=udp:my_server_ip:7060 # CUSTOMIZE ME disable_tcp=no disable_tls=no listen=tls:my_server_ip:7061 # CUSTOMIZE ME tls_verify_server= 0 tls_verify_client = 1 tls_require_client_certificate = 1 #tls_method = TLSv1 tls_method = SSLv23 tls_certificate = "/usr/local/etc/opensips/tls/server/server-cert.pem" tls_private_key = "/usr/local/etc/opensips/tls/server/server-privkey.pem" tls_ca_list = "/usr/local/etc/opensips/tls/server/server-calist.pem" Basically i want to verify if the client has right certificate. Can you help me? Thanks. ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] MSILO Module can't work
Hi Tin,
Once again, can you post the full REGISTER request here ? are you sure
that REGISTER do advertise "MESSAGE" in the Allow header
Also , you could enable full debug for the m_dump() function:
set_debug(4);
m_dump();
set_debug();
In this case, you may get a clue why the function does not send out the
stored messages.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 03.02.2015 03:05, tin wrote:
Dear Bogdan,
Thanks for all your reply and kindly help. I definitely saw
the record in DB. here are the records on my DB:
mysql> select * from silo where ctype = 'text/plain';
+--+-+-+--+-+++--++---+
| id | src_addr| dst_addr| username |
domain | inc_time | exp_time | snd_time | ctype |
body |
+--+-+-+--+-+++--++---+
| 3659 | sip:008@118.193.154.214 | sip:010@118.193.154.214 | 010
| 118.193.154.214 | 1422859611 | 1422895611 |0 | text/plain
| coi |
| 3667 | sip:008@118.193.154.214 | sip:010@118.193.154.214 | 010
| 118.193.154.214 | 1422860496 | 1423119696 |0 | text/plain
| ggg |
| 3669 | sip:008@118.193.154.214 | sip:010@118.193.154.214 | 010
| 118.193.154.214 | 1422860514 | 1423119714 |0 | text/plain
| qqq |
| 3671 | sip:008@118.193.154.214 | sip:010@118.193.154.214 | 010
| 118.193.154.214 | 1422860599 | 1423119799 |0 | text/plain
| b |
| 3719 | sip:003@118.193.154.214 | sip:010@118.193.154.214 | 010
| 118.193.154.214 | 1422868318 | 1423127518 |0 | text/plain
| 456 |
| 3718 | sip:003@118.193.154.214 | sip:010@118.193.154.214 | 010
| 118.193.154.214 | 1422868210 | 1423127410 |0 | text/plain
| 123 |
| 3717 | sip:003@118.193.154.214 | sip:010@118.193.154.214 | 010
| 118.193.154.214 | 1422867734 | 1423126934 |0 | text/plain
| 999 |
The username is : 010
Domain is : 118.193.154.214
They match the AOR of the user that register later.
*Here is how i test offline message:*
The user of sip:008@118.193.154.214 is online, And another user of
sip:010@118.193.154.214 is offline, When the user of
sip:008@118.193.154.214 is sending message to another user of
sip:010@118.193.154.214, the message is saved to DB and not reached
to destination since another user of sip:010@118.193.154.214 is
offline. The records for offline messages are saved to DB as above.
I could not found anything wrong with records, could you please help
me to double check ? appreciate!!!
*The problem that i am facing now:*
The problem i am facing is that record is saved successfully to DB
but not offline message shown up on linphone android app when offline
user goes back to online. this issue has already cost us a lot of
time but not good news, i appreciate all your help so much,your help
gives us hope.
The function m_dump() has already be added on my opensips.cfg script,
and the following log for success is received. *
**log("MSILO: offline messages dumped - if they were\n"); ***
*my opensips.cfg script
*The following is my full opensips.cfg scrip, i hope it might help.
could you please help me to double check the script if anything
wrong? I really could not find out the reason why offline message is
not sending from DB to android app when user go back to online. By
the way, this script can be run successfully on my opensips v1.11
and has no error.
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] MSILO Module can't work
Hi Tin, Those are TCP related errors, saying your OpenSIPS is trying to open a TCP connection to a destination which does not accept the connection. This is not related to msilo stuff at all. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 03.02.2015 08:40, tin wrote: hi, Sometimes the messages can't store into DB, And log has some error like this: Feb 3 14:36:20 mySer /usr/sbin/opensips[24989]: ERROR:tm:msg_send: tcp_send failed Feb 3 14:36:20 mySer /usr/sbin/opensips[24989]: ERROR:tm:t_forward_nonack: sending request failed Feb 3 14:36:20 mySer /usr/sbin/opensips[24989]: ERROR:tm:w_t_relay: t_forward_nonack failed Feb 3 14:36:20 mySer /usr/sbin/opensips[24989]: ERROR:tm:_reply_light: failed to generate 500 reply when a final 477 was sent out Feb 3 14:36:20 mySer /usr/sbin/opensips[24989]: ERROR:signaling:sig_send_reply_mod: failed to send reply with tm module Feb 3 14:36:31 mySer /usr/sbin/opensips[25000]: ERROR:core:tcp_blocking_connect: timeout 9 s elapsed from 10 s Feb 3 14:36:31 mySer /usr/sbin/opensips[25000]: ERROR:core:tcpconn_connect: tcp_blocking_connect failed Feb 3 14:36:31 mySer /usr/sbin/opensips[25000]: ERROR:core:tcp_send: connect failed Feb 3 14:36:31 mySer /usr/sbin/opensips[25000]: ERROR:tm:msg_send: tcp_send failed Feb 3 14:36:31 mySer /usr/sbin/opensips[25000]: ERROR:tm:t_forward_nonack: sending request failed Feb 3 14:36:31 mySer /usr/sbin/opensips[25000]: INFO:core:probe_max_sock_buff: using snd buffer of 255 kb Feb 3 14:36:31 mySer /usr/sbin/opensips[25000]: INFO:core:init_sock_keepalive: -- TCP keepalive enabled on socket Feb 3 14:36:45 mySer /usr/sbin/opensips[25000]: ERROR:core:tcp_blocking_connect: timeout 9 s elapsed from 10 s Feb 3 14:36:45 mySer /usr/sbin/opensips[25000]: ERROR:core:tcpconn_connect: tcp_blocking_connect failed Feb 3 14:36:45 mySer /usr/sbin/opensips[25000]: ERROR:core:tcp_send: connect failed Feb 3 14:36:45 mySer /usr/sbin/opensips[25000]: ERROR:tm:msg_send: tcp_send failed Feb 3 14:36:45 mySer /usr/sbin/opensips[25000]: ERROR:tm:t_forward_nonack: sending request failed Feb 3 14:36:45 mySer /usr/sbin/opensips[25000]: INFO:core:probe_max_sock_buff: using snd buffer of 255 kb Feb 3 14:36:45 mySer /usr/sbin/opensips[25000]: INFO:core:init_sock_keepalive: -- TCP keepalive enabled on socket Feb 3 14:36:59 mySer /usr/sbin/opensips[25000]: ERROR:core:tcp_blocking_connect: timeout 9 s elapsed from 10 s Feb 3 14:36:59 mySer /usr/sbin/opensips[25000]: ERROR:core:tcpconn_connect: tcp_blocking_connect failed Feb 3 14:36:59 mySer /usr/sbin/opensips[25000]: ERROR:core:tcp_send: connect failed Feb 3 14:36:59 mySer /usr/sbin/opensips[25000]: ERROR:tm:msg_send: tcp_send failed Feb 3 14:36:59 mySer /usr/sbin/opensips[25000]: ERROR:tm:t_forward_nonack: sending request failed Feb 3 14:36:59 mySer /usr/sbin/opensips[25000]: ERROR:tm:w_t_relay: t_forward_nonack failed Feb 3 14:36:59 mySer /usr/sbin/opensips[25000]: ERROR:tm:_reply_light: failed to generate 500 reply when a final 477 was sent out Feb 3 14:36:59 mySer /usr/sbin/opensips[25000]: ERROR:signaling:sig_send_reply_mod: failed to send reply with tm module At 2015-02-03 08:15:45, "tin" wrote: Hi: The REGISTER look likenormal; Tow REGISTER can communicate with each other when they online; Thanks At 2015-02-02 17:36:42, "Bogdan-Andrei Iancu" mailto:bog...@opensips.org>> wrote: And how does the REGISTER look like ? Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 02.02.2015 11:33, tin wrote: Hi,Bogdan: yes,the DB has the record. and the username match the AOR of the user that register later, the record as below: mysql> select * from silo where ctype = 'text/plain'; +--+-+-+--+-+++--++---+ | id | src_addr| dst_addr | username | domain | inc_time | exp_time | snd_time | ctype | body | +--+-+-+--+-+++--++---+ | 3659 | sip:008@118.193.154.214 | sip:010@118.193.154.214 | 010 | 118.193.154.214 | 1422859611 | 1422895611 | 0 | text/plain | coi | | 3667 | sip:008@118.193.154.214 | sip:010@118.193.154.214 | 010 | 118.193.154.214 | 1422860496 | 1423119696 | 0 | text/plain | ggg | | 3669 | sip:008@118.193.154.214 | sip:010@118.193.154.214 | 010 | 118.193.154.214 | 1422860514 | 1423119714 | 0 | text/plain | qqq | | 3671 | sip:008@118.193.154.214 | sip:010@118.193.154.214 | 010
[OpenSIPS-Users] Opensips 1.11.3-latest 1:1 NAT Registration issue
Dear all, I have installed Opensips 1.11-3 on 1:1 NAT Server but registration fails with "too many hops". I am using the advertised_address feature with IP: 185.46.X.X but its not working. The configuration file with registration procedure is working fine on a host with public IP. I have tested the same setup with opensips 1.8.x version and the problem is also there. also have tested with or without alias feature enabled. opensips config == advertised_address="185.46.x.x" #public IP here advertised_port=5060 listen=udp:192.168.70.109:5060 == I am sending you a pastebin url of debug: 5 - http://pastebin.com/VWr68982 Thank you for your support Vasilios Tzanoudakis ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Dialog default timeout issue
Hi Bogdan-Andrei,
Thanks for your reply. The delays resulted from some unknown issue in our
testing infrastructure rather than a number of destinations. I had set
modparam("tm", "own_timer_proc", 1) to make tm module run its own timer?!
but the problem remains. Anyway, as long as the long delays issue is
resolved, this issue should not exist. Thanks again.
Kind wishes,
Chen-Che
--
View this message in context:
http://opensips-open-sip-server.1449251.n2.nabble.com/Dialog-default-timeout-issue-tp7595155p7595164.html
Sent from the OpenSIPS - Users mailing list archive at Nabble.com.
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] Errors on opensips 1.11.3 (Logging and db_text)
I have 2 issues:
1. I have set my log to DEBUG but I don’t see then displayed. Notice
that the below snipped shows INFOR and ERROR logs only.
debug=6
log_stderror=no
log_facility=LOG_LOCAL0
2. I am trying to use the dbtext module and Here is the error I get:
Stopping opensips: not running [WARNING]
Starting opensips: [FAILED]
Feb 3 09:08:19 test_server opensips: INFO:core:shm_mem_init: allocating
SHM block
Feb 3 09:08:19 test_server opensips: INFO:core:init_tcp: using epoll_lt as
the TCP io watch method (auto detected)
Feb 3 09:08:19 test_server /usr/sbin/opensips[14637]: NOTICE:core:main:
version: opensips 1.11.3-tls (x86_64/linux)
Feb 3 09:08:19 test_server /usr/sbin/opensips[14637]: INFO:core:main:
using 32 Mb shared memory
Feb 3 09:08:19 test_server /usr/sbin/opensips[14637]: INFO:core:main:
using 2 Mb private memory per process
Feb 3 09:08:19 test_server /usr/sbin/opensips[14637]:
INFO:core:evi_publish_event: Registered event
Feb 3 09:08:19 test_server /usr/sbin/opensips[14637]:
INFO:core:evi_publish_event: Registered event
Feb 3 09:08:19 test_server /usr/sbin/opensips[14637]:
INFO:core:evi_publish_event: Registered event
Feb 3 09:08:19 test_server /usr/sbin/opensips[14637]: INFO:sl:mod_init:
Initializing StateLess engine
Feb 3 09:08:19 test_server /usr/sbin/opensips[14637]: INFO:tm:mod_init: TM
- initializing...
Feb 3 09:08:19 test_server /usr/sbin/opensips[14637]:
NOTICE:signaling:mod_init: initializing module ...
Feb 3 09:08:19 test_server /usr/sbin/opensips[14637]:
INFO:maxfwd:mod_init: initializing...
Feb 3 09:08:19 test_server /usr/sbin/opensips[14637]:
INFO:textops:mod_init: initializing...
Feb 3 09:08:19 test_server /usr/sbin/opensips[14637]:
INFO:sipmsgops:mod_init: initializing...
Feb 3 09:08:19 test_server /usr/sbin/opensips[14637]:
INFO:db_text:dbt_init: using database at: /tmp/opensipsdb
Feb 3 09:08:19 test_server /usr/sbin/opensips[14637]:
ERROR:db_text:dbt_query: table does not exist!
Feb 3 09:08:19 test_server /usr/sbin/opensips[14637]:
ERROR:core:db_table_version: error in db_query
Feb 3 09:08:19 test_server /usr/sbin/opensips[14637]:
ERROR:dispatcher:init_ds_db: failed to query table version
Feb 3 09:08:19 test_server /usr/sbin/opensips[14637]:
ERROR:dispatcher:mod_init: failed to init database support
Feb 3 09:08:19 test_server /usr/sbin/opensips[14637]: ERROR:core:init_mod:
failed to initialize module dispatcher
Feb 3 09:08:19 test_server /usr/sbin/opensips[14637]: ERROR:core:main:
error while initializing modules
Feb 3 09:08:19 test_server /usr/sbin/opensips[14637]: INFO:core:cleanup:
cleanup
Feb 3 09:08:19 test_server opensips: INFO:core:daemonize: pre-daemon
process exiting with -1
Snipped from my opensips.cfg:
loadmodule "db_text.so"
modparam("db_text", "db_mode", 1)
modparam("dispatcher", "db_url", "text:///tmp/opensipsdb")
/tmp/opensipsdb has a chmod of 777:
drwxrwxrwx 2 root root 4096 Feb 3 09:07 opensipsdb
my test dispatcher file:
[root@ test_server tmp]# ls -ltr opensipsdb/dispatcher
-rw-r--r-- 1 root root 218 Feb 3 09:13 opensipsdb/dispatcher
[root@ test_server tmp]# cat opensipsdb/dispatcher
id(int,auto) setid(int) destination(string) socket(string,null) state(int)
weight(int) attrs(string) description(string)
1:1:sip\:1.2.3.4\:5060:null:0:51:line1:server11
2:1:sip\:1.2.3.4\:5070:null:0:49:line2:server12
Any help/direction is appreciated.
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] MSILO Module can't work
Hi, I am use opensips 1.11.3 on centos5.11,it's everything is ok . I want to deploy the MSILO Module ,loadmodule、add route script in the "cfg" the user A send message to B who was offline;the message save to the server; when the user B online,the message didn't from server sent to B user,why? ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Dialog default timeout issue
Hi Chen-Che,
You mean after having TM with its own timer process, you still get the
logs on tm-timer, but the dialog is no longer affected ?
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 03.02.2015 16:20, microx wrote:
Hi Bogdan-Andrei,
Thanks for your reply. The delays resulted from some unknown issue in our
testing infrastructure rather than a number of destinations. I had set
modparam("tm", "own_timer_proc", 1) to make tm module run its own timer?!
but the problem remains. Anyway, as long as the long delays issue is
resolved, this issue should not exist. Thanks again.
Kind wishes,
Chen-Che
--
View this message in context:
http://opensips-open-sip-server.1449251.n2.nabble.com/Dialog-default-timeout-issue-tp7595155p7595164.html
Sent from the OpenSIPS - Users mailing list archive at Nabble.com.
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Opensips 1.11.3-latest 1:1 NAT Registration issue
Hi Vasilios, The "too many hops" reply typically indicates a looping of the REGISTER through OpenSIPS - OpenSIPS is sending that REGISTER to itself via loopback interface. Why ? because of a configuration error - the SIP domain in REGISTER RURI is not recognized by OpenSIPS as a local domain, but it points to the OpenSIPS IP via DNS. Be sure the domain you have in RURI is set as local domain in OpenSIPS cfg . The 185.46.X.X IP you have there should be configured as "alias" in OpenSIPS. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 03.02.2015 15:14, Vasilios Tzanoudakis wrote: Dear all, I have installed Opensips 1.11-3 on 1:1 NAT Server but registration fails with "too many hops". I am using the advertised_address feature with IP: 185.46.X.X but its not working. The configuration file with registration procedure is working fine on a host with public IP. I have tested the same setup with opensips 1.8.x version and the problem is also there. also have tested with or without alias feature enabled. opensips config == advertised_address="185.46.x.x" #public IP here advertised_port=5060 listen=udp:192.168.70.109:5060 == I am sending you a pastebin url of debug: 5 - http://pastebin.com/VWr68982 Thank you for your support Vasilios Tzanoudakis ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Errors on opensips 1.11.3 (Logging and db_text)
Hi Alfred,
1) I suspect a configuration issue with your syslog daemon - maybe the
debug level is skipped for default log file.
2) in /tmp/opensipsdb you need to have the "version" table too.
Best regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 03.02.2015 19:28, Alfred Rudrapati wrote:
I have 2 issues:
1.I have set my log to DEBUG but I don’t see then displayed. Notice
that the below snipped shows INFOR and ERROR logs only.
debug=6
log_stderror=no
log_facility=LOG_LOCAL0
2.I am trying to use the dbtext module and Here is the error I get:
Stopping opensips: not running [WARNING]
Starting opensips: [FAILED]
Feb 3 09:08:19 test_server opensips: INFO:core:shm_mem_init:
allocating SHM block
Feb 3 09:08:19 test_server opensips: INFO:core:init_tcp: using
epoll_lt as the TCP io watch method (auto detected)
Feb 3 09:08:19 test_server /usr/sbin/opensips[14637]:
NOTICE:core:main: version: opensips 1.11.3-tls (x86_64/linux)
Feb 3 09:08:19 test_server /usr/sbin/opensips[14637]: INFO:core:main:
using 32 Mb shared memory
Feb 3 09:08:19 test_server /usr/sbin/opensips[14637]: INFO:core:main:
using 2 Mb private memory per process
Feb 3 09:08:19 test_server /usr/sbin/opensips[14637]:
INFO:core:evi_publish_event: Registered event
Feb 3 09:08:19 test_server /usr/sbin/opensips[14637]:
INFO:core:evi_publish_event: Registered event
Feb 3 09:08:19 test_server /usr/sbin/opensips[14637]:
INFO:core:evi_publish_event: Registered event
Feb 3 09:08:19 test_server /usr/sbin/opensips[14637]:
INFO:sl:mod_init: Initializing StateLess engine
Feb 3 09:08:19 test_server /usr/sbin/opensips[14637]:
INFO:tm:mod_init: TM - initializing...
Feb 3 09:08:19 test_server /usr/sbin/opensips[14637]:
NOTICE:signaling:mod_init: initializing module ...
Feb 3 09:08:19 test_server /usr/sbin/opensips[14637]:
INFO:maxfwd:mod_init: initializing...
Feb 3 09:08:19 test_server /usr/sbin/opensips[14637]:
INFO:textops:mod_init: initializing...
Feb 3 09:08:19 test_server /usr/sbin/opensips[14637]:
INFO:sipmsgops:mod_init: initializing...
Feb 3 09:08:19 test_server /usr/sbin/opensips[14637]:
INFO:db_text:dbt_init: using database at: /tmp/opensipsdb
Feb 3 09:08:19 test_server /usr/sbin/opensips[14637]:
ERROR:db_text:dbt_query: table does not exist!
Feb 3 09:08:19 test_server /usr/sbin/opensips[14637]:
ERROR:core:db_table_version: error in db_query
Feb 3 09:08:19 test_server /usr/sbin/opensips[14637]:
ERROR:dispatcher:init_ds_db: failed to query table version
Feb 3 09:08:19 test_server /usr/sbin/opensips[14637]:
ERROR:dispatcher:mod_init: failed to init database support
Feb 3 09:08:19 test_server /usr/sbin/opensips[14637]:
ERROR:core:init_mod: failed to initialize module dispatcher
Feb 3 09:08:19 test_server /usr/sbin/opensips[14637]:
ERROR:core:main: error while initializing modules
Feb 3 09:08:19 test_server /usr/sbin/opensips[14637]:
INFO:core:cleanup: cleanup
Feb 3 09:08:19 test_server opensips: INFO:core:daemonize: pre-daemon
process exiting with -1
Snipped from my opensips.cfg:
loadmodule "db_text.so"
modparam("db_text", "db_mode", 1)
modparam("dispatcher", "db_url", "text:///tmp/opensipsdb")
/tmp/opensipsdb has a chmod of 777:
drwxrwxrwx 2 root root 4096 Feb 3 09:07 opensipsdb
my test dispatcher file:
[root@ test_server tmp]# ls -ltr opensipsdb/dispatcher
-rw-r--r-- 1 root root 218 Feb 3 09:13 opensipsdb/dispatcher
[root@ test_server tmp]# cat opensipsdb/dispatcher
id(int,auto) setid(int) destination(string) socket(string,null)
state(int) weight(int) attrs(string) description(string)
1:1:sip\:1.2.3.4\:5060:null:0:51:line1:server11
2:1:sip\:1.2.3.4\:5070:null:0:49:line2:server12
Any help/direction is appreciated.
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] segfault returning values from cachedb_redis
OS Version: CentOS Linux release 7.0.1406 (Core)Linux
3.10.0-123.20.1.el7.x86_64 x86_64
redis_version:2.8.14Opensips Version: NOTICE:core:main: version: opensips
1.11.3-notls (x86_64/linux) (cloned from GitHub 2015-02-02)
Description of Problem: Attempting to implement cachedb_redis key/value store.
When Redis queries return NULL (no matching key in Redis) script runs fine,
when a value is returned from Redis it causes a segmentation fault (output
below). Able to reproduce using "cache_fetch" as well as "cache_raw_query." I
am passing Redis an IP address as a key and originally thought the "." was
causing the segfault, however, I used a substitution to replace "." with "_"
and the segfault still occurs. Further testing showed that removing matching
keys from Redis allowed the script to carry on which leads me to believe it is
the return from Redis causing the seg fault and not the format of the key.
Relevant config lines:loadmodule "cachedb_redis.so"modparam("cachedb_redis",
"cachedb_url","redis:group1://localhost:6379/")#...$avp(s_ip) = $si;
avp_subst("$avp(s_ip)/$avp(s_ip_format)","/\./_/g");
cache_fetch("redis:group1","$avp(s_ip_format)",$avp(host_type));#also
tried:#cache_raw_query("redis:group1","HGET known_hosts
$avp(s_ip_format)","$avp(host_type)");
Relevant log output:Feb 3 13:09:22 localhost /usr/local/sbin/opensips[12528]:
NOTICE:cachedb_redis:destroy: destroy module cachedb_redis ...Feb 3 13:09:23
localhost /usr/local/sbin/opensips[12489]: ERROR:core:cachedb_fetch: Wrong
argument - no cachedb system with this name registeredFeb 3 13:09:23
localhost kernel: opensips[12489]: segfault at 0 ip (null) sp
7fff5bc53678 error 14 in opensips[40+1f1000]Feb 3 13:09:23 localhost
/usr/local/sbin/opensips[12486]: INFO:core:handle_sigs: child process 12489
exited by a signal 11Feb 3 13:09:23 localhost /usr/local/sbin/opensips[12486]:
INFO:core:handle_sigs: core was generatedFeb 3 13:09:23 localhost
/usr/local/sbin/opensips[12486]: INFO:core:handle_sigs: terminating due to
SIGCHLD
Here is the monitor output from Redis (replaced the actually IP addresses being
dipped). This shows that, prior to the segmentation fault Opensips properly
queried Redis and received a NULL response (since 192.168.1.1 is not a valid
key while 192.168.1.2 is) and the second query create the
segfault:1422997762.024040 [0 127.0.0.1:54187] "GET"
"192_168_1_1"1422997762.047668 [0 127.0.0.1:54189] "GET" "192_168_1_2"
Core Info (I may be doing this incorrectly):(gdb) bt full#0 0x
in ?? ()No symbol table info available.#1 0x7fc7423d4484 in ?? ()No symbol
table info available.#2 0x7fc743d57de8 in ?? ()No symbol table info
available.#3 0x004ecc44 in ?? ()No symbol table info available.#4
0x0010 in ?? ()No symbol table info available.#5
0x8000a43ac8f1 in ?? ()No symbol table info available.#6
0x7fc743d57de8 in ?? ()No symbol table info available.#7
0x7fc743d4d1ef in ?? ()No symbol table info available.#8
0x7fff5bc53760 in ?? ()No symbol table info available.#9
0xcccd in ?? ()No symbol table info available.#10
0x7fc743d2e7f0 in ?? ()No symbol table info available.#11
0x004f21db in ?? ()No symbol table info available.#12
0x7fc743d4e1b8 in ?? ()No symbol table info available.#13
0x in ?? ()No symbol table info available.
Thanks!
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Dialog default timeout issue
Hi Bogdan-Andrei,
I meant that I set modparam("tm", "own_timer_proc", 1) in the first place
but the dialogs were affected. From your previous reply, I though that
setting modparam("tm", "own_timer_proc", 1) enables TM have its own timer
and dialogs can be prevented from being affected. So, setting modparam("tm",
"own_timer_proc", 1) should be effective in preventing dialogs from being
affected by long delays? Or I misunderstand it?
PS. In the my config, I just write
if (is_method("INVITE"))
create_dialog("B"); and do not call t_newtran()
Thanks.
Kind wishes,
Chen-Che
--
View this message in context:
http://opensips-open-sip-server.1449251.n2.nabble.com/Dialog-default-timeout-issue-tp7595155p7595187.html
Sent from the OpenSIPS - Users mailing list archive at Nabble.com.
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] MSILO Module can't work
Hi,Bogdan:
1)the REGISTER header like below:
Via: SIP/2.0/TCP 10.0.2.10:1024;rport;branch=z9hG4bK2004555300
From: ;tag=1091770352
To:
Call-ID: 1031630591
CSeq: 3 REGISTER
Contact:
Max-Forwards: 70
User-Agent: LinphoneAndroid/2.0.2 (eXosip2/3.6.0)
Expires: 3600
Content-Length: 0
the e-mail is too big ,so i have to send you two,this is one.
At 2015-02-03 18:05:43, "Bogdan-Andrei Iancu" wrote:
Hi Tin,
Once again, can you post the full REGISTER request here ? are you sure that
REGISTER do advertise "MESSAGE" in the Allow header
Also , you could enable full debug for the m_dump() function:
set_debug(4);
m_dump();
set_debug();
In this case, you may get a clue why the function does not send out the stored
messages.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 03.02.2015 03:05, tin wrote:
Dear Bogdan,
Thanks for all your reply and kindly help. I definitely saw the record
in DB. here are the records on my DB:
mysql> select * from silo where ctype = 'text/plain';
+--+-+-+--+-+++--++---+
| id | src_addr| dst_addr| username | domain
| inc_time | exp_time | snd_time | ctype | body |
+--+-+-+--+-+++--++---+
| 3659 | sip:008@118.193.154.214 | sip:010@118.193.154.214 | 010 |
118.193.154.214 | 1422859611 | 1422895611 |0 | text/plain | coi |
| 3667 | sip:008@118.193.154.214 | sip:010@118.193.154.214 | 010 |
118.193.154.214 | 1422860496 | 1423119696 |0 | text/plain | ggg |
| 3669 | sip:008@118.193.154.214 | sip:010@118.193.154.214 | 010 |
118.193.154.214 | 1422860514 | 1423119714 |0 | text/plain | qqq |
| 3671 | sip:008@118.193.154.214 | sip:010@118.193.154.214 | 010 |
118.193.154.214 | 1422860599 | 1423119799 |0 | text/plain | b |
| 3719 | sip:003@118.193.154.214 | sip:010@118.193.154.214 | 010 |
118.193.154.214 | 1422868318 | 1423127518 |0 | text/plain | 456 |
| 3718 | sip:003@118.193.154.214 | sip:010@118.193.154.214 | 010 |
118.193.154.214 | 1422868210 | 1423127410 |0 | text/plain | 123 |
| 3717 | sip:003@118.193.154.214 | sip:010@118.193.154.214 | 010 |
118.193.154.214 | 1422867734 | 1423126934 |0 | text/plain | 999 |
The username is : 010
Domain is : 118.193.154.214
They match the AOR of the user that register later.
Here is how i test offline message:
The user of sip:008@118.193.154.214 is online, And another user of
sip:010@118.193.154.214 is offline, When the user of sip:008@118.193.154.214
is sending message to another user of sip:010@118.193.154.214, the message is
saved to DB and not reached to destination since another user of
sip:010@118.193.154.214 is offline. The records for offline messages are saved
to DB as above.
I could not found anything wrong with records, could you please help me to
double check ? appreciate!!!
The problem that i am facing now:
The problem i am facing is that record is saved successfully to DB but not
offline message shown up on linphone android app when offline user goes back to
online. this issue has already cost us a lot of time but not good news, i
appreciate all your help so much,your help gives us hope.
The function m_dump() has already be added on my opensips.cfg script, and the
following log for success is received.
log("MSILO: offline messages dumped - if they were\n");
my opensips.cfg script
The following is my full opensips.cfg scrip, i hope it might help. could you
please help me to double check the script if anything wrong? I really could not
find out the reason why offline message is not sending from DB to android app
when user go back to online. By the way, this script can be run successfully
on my opensips v1.11 and has no error.
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] MSILO Module can't work
Hi,
There has a stauts about 401 Unauthorized:
SIP/2.0 401 Unauthorized
Via: SIP/2.0/TCP
10.0.2.10:1024;received=59.36.45.241;rport=9782;branch=z9hG4bK1450910565
From: ;tag=2014338328
To: ;tag=5c2831c51ae0c72390d6fc905fc065f7.ab7b
Call-ID: 1547875337
CSeq: 3 REGISTER
WWW-Authenticate: Digest realm="118.193.154.214",
nonce="54d192cf001ce25c63b4ab2f9483e02d77ebc3ebeede"
Server: OpenSIPS (1.11.3-notls (x86_64/linux))
Content-Length: 0
At 2015-02-03 18:05:43, "Bogdan-Andrei Iancu" wrote:
Hi Tin,
Once again, can you post the full REGISTER request here ? are you sure that
REGISTER do advertise "MESSAGE" in the Allow header
Also , you could enable full debug for the m_dump() function:
set_debug(4);
m_dump();
set_debug();
In this case, you may get a clue why the function does not send out the stored
messages.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 03.02.2015 03:05, tin wrote:
Dear Bogdan,
Thanks for all your reply and kindly help. I definitely saw the record
in DB. here are the records on my DB:
mysql> select * from silo where ctype = 'text/plain';
+--+-+-+--+-+++--++---+
| id | src_addr| dst_addr| username | domain
| inc_time | exp_time | snd_time | ctype | body |
+--+-+-+--+-+++--++---+
| 3659 | sip:008@118.193.154.214 | sip:010@118.193.154.214 | 010 |
118.193.154.214 | 1422859611 | 1422895611 |0 | text/plain | coi |
| 3667 | sip:008@118.193.154.214 | sip:010@118.193.154.214 | 010 |
118.193.154.214 | 1422860496 | 1423119696 |0 | text/plain | ggg |
| 3669 | sip:008@118.193.154.214 | sip:010@118.193.154.214 | 010 |
118.193.154.214 | 1422860514 | 1423119714 |0 | text/plain | qqq |
| 3671 | sip:008@118.193.154.214 | sip:010@118.193.154.214 | 010 |
118.193.154.214 | 1422860599 | 1423119799 |0 | text/plain | b |
| 3719 | sip:003@118.193.154.214 | sip:010@118.193.154.214 | 010 |
118.193.154.214 | 1422868318 | 1423127518 |0 | text/plain | 456 |
| 3718 | sip:003@118.193.154.214 | sip:010@118.193.154.214 | 010 |
118.193.154.214 | 1422868210 | 1423127410 |0 | text/plain | 123 |
| 3717 | sip:003@118.193.154.214 | sip:010@118.193.154.214 | 010 |
118.193.154.214 | 1422867734 | 1423126934 |0 | text/plain | 999 |
The username is : 010
Domain is : 118.193.154.214
They match the AOR of the user that register later.
Here is how i test offline message:
The user of sip:008@118.193.154.214 is online, And another user of
sip:010@118.193.154.214 is offline, When the user of sip:008@118.193.154.214
is sending message to another user of sip:010@118.193.154.214, the message is
saved to DB and not reached to destination since another user of
sip:010@118.193.154.214 is offline. The records for offline messages are saved
to DB as above.
I could not found anything wrong with records, could you please help me to
double check ? appreciate!!!
The problem that i am facing now:
The problem i am facing is that record is saved successfully to DB but not
offline message shown up on linphone android app when offline user goes back to
online. this issue has already cost us a lot of time but not good news, i
appreciate all your help so much,your help gives us hope.
The function m_dump() has already be added on my opensips.cfg script, and the
following log for success is received.
log("MSILO: offline messages dumped - if they were\n");
my opensips.cfg script
The following is my full opensips.cfg scrip, i hope it might help. could you
please help me to double check the script if anything wrong? I really could not
find out the reason why offline message is not sending from DB to android app
when user go back to online. By the way, this script can be run successfully
on my opensips v1.11 and has no error.
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] MSILO Module can't work
Hi,Bogdan:
the e-mail is too big ,so i have to send you two,this is two.
2)this code add to the script:
xlog("m_dump is starting!!");
setdebug(4);
m_dump();
setdebug();
xlog("m_dump was end!!");
And the user 003 was didn't receive the offline message;another i should see
the log like below:
Feb 4 11:38:23 mySer /usr/sbin/opensips[14888]: Register ok
:sip:003@118.193.154.214
Feb 4 11:38:23 mySer /usr/sbin/opensips[14888]: m_dump is starting!!
Feb 4 11:38:23 mySer /usr/sbin/opensips[14888]: DBG:core:parse_headers:
flags=8000
Feb 4 11:38:23 mySer /usr/sbin/opensips[14888]: DBG:msilo:m_dump: user
online - expires=3600
Feb 4 11:38:23 mySer /usr/sbin/opensips[14888]: DBG:core:parse_headers:
flags=
Feb 4 11:38:23 mySer /usr/sbin/opensips[14888]: DBG:core:parse_headers:
flags=
Feb 4 11:38:23 mySer /usr/sbin/opensips[14888]:
DBG:msilo:check_message_support: Allow message: 0
Feb 4 11:38:23 mySer /usr/sbin/opensips[14888]: DBG:core:parse_headers:
flags=80
Feb 4 11:38:23 mySer /usr/sbin/opensips[14888]: DBG:core:get_hdr_field: found
end of header
Feb 4 11:38:23 mySer /usr/sbin/opensips[14888]:
DBG:db_mysql:mysql_raise_event: MySQL status has not changed: connected
Feb 4 11:38:23 mySer /usr/sbin/opensips[14888]: DBG:core:db_new_result:
allocate 48 bytes for result set at 0x2ac45c768a80
Feb 4 11:38:23 mySer /usr/sbin/opensips[14888]:
DBG:db_mysql:db_mysql_get_columns: 6 columns returned from the query
Feb 4 11:38:23 mySer /usr/sbin/opensips[14888]: DBG:core:db_allocate_columns:
allocate 168 bytes for result columns at 0x2ac45c768148
Feb 4 11:38:23 mySer /usr/sbin/opensips[14888]:
DBG:db_mysql:db_mysql_get_columns: RES_NAMES(0x2ac45c768178)[0]=[id]
Feb 4 11:38:23 mySer /usr/sbin/opensips[14888]:
DBG:db_mysql:db_mysql_get_columns: use DB_INT result type
Feb 4 11:38:23 mySer /usr/sbin/opensips[14888]:
DBG:db_mysql:db_mysql_get_columns: RES_NAMES(0x2ac45c768188)[1]=[src_addr]
Feb 4 11:38:23 mySer /usr/sbin/opensips[14888]:
DBG:db_mysql:db_mysql_get_columns: use DB_STRING result type
Feb 4 11:38:23 mySer /usr/sbin/opensips[14888]:
DBG:db_mysql:db_mysql_get_columns: RES_NAMES(0x2ac45c768198)[2]=[dst_addr]
Feb 4 11:38:23 mySer /usr/sbin/opensips[14888]:
DBG:db_mysql:db_mysql_get_columns: use DB_STRING result type
Feb 4 11:38:23 mySer /usr/sbin/opensips[14888]:
DBG:db_mysql:db_mysql_get_columns: RES_NAMES(0x2ac45c7681a8)[3]=[body]
Feb 4 11:38:23 mySer /usr/sbin/opensips[14888]:
DBG:db_mysql:db_mysql_get_columns: use DB_BLOB result type
Feb 4 11:38:23 mySer /usr/sbin/opensips[14888]:
DBG:db_mysql:db_mysql_get_columns: RES_NAMES(0x2ac45c7681b8)[4]=[ctype]
Feb 4 11:38:23 mySer /usr/sbin/opensips[14888]:
DBG:db_mysql:db_mysql_get_columns: use DB_STRING result type
Feb 4 11:38:23 mySer /usr/sbin/opensips[14888]:
DBG:db_mysql:db_mysql_get_columns: RES_NAMES(0x2ac45c7681c8)[5]=[inc_time]
Feb 4 11:38:23 mySer /usr/sbin/opensips[14888]:
DBG:db_mysql:db_mysql_get_columns: use DB_INT result type
Feb 4 11:38:23 mySer /usr/sbin/opensips[14888]: DBG:core:db_allocate_rows:
allocate 416 bytes for result rows and values at 0x2ac45c7665d8
Feb 4 11:38:23 mySer /usr/sbin/opensips[14888]: DBG:db_mysql:db_mysql_str2val:
converting INT [4836]
Feb 4 11:38:23 mySer /usr/sbin/opensips[14888]: DBG:db_mysql:db_mysql_str2val:
converting STRING [sip:010@118.193.154.214]
Feb 4 11:38:23 mySer /usr/sbin/opensips[14888]: DBG:db_mysql:db_mysql_str2val:
converting STRING [sip:003@118.193.154.214]
Feb 4 11:38:23 mySer /usr/sbin/opensips[14888]: DBG:db_mysql:db_mysql_str2val:
converting BLOB [
active text/plain
60 ]
Feb 4 11:38:23 mySer /usr/sbin/opensips[14888]: DBG:db_mysql:db_mysql_str2val:
converting STRING [application/im-iscomposing+xml]
Feb 4 11:38:23 mySer /usr/sbin/opensips[14888]: DBG:db_mysql:db_mysql_str2val:
converting INT [1423019838]
Feb 4 11:38:23 mySer /usr/sbin/opensips[14888]: DBG:db_mysql:db_mysql_str2val:
converting INT [4838]
Feb 4 11:38:23 mySer /usr/sbin/opensips[14888]: DBG:db_mysql:db_mysql_str2val:
converting STRING [sip:010@118.193.154.214]
Feb 4 11:38:23 mySer /usr/sbin/opensips[14888]: DBG:db_mysql:db_mysql_str2val:
converting STRING [sip:003@118.193.154.214]
] 4 11:38:23 mySer /usr/sbin/opensips[14888]: DBG:db_mysql:db_mysql_str2val:
converting BLOB [hi,i am 010!
Feb 4 11:38:23 mySer /usr/sbin/opensips[14888]: DBG:db_mysql:db_mysql_str2val:
converting STRING [text/plain]
Feb 4 11:38:23 mySer /usr/sbin/opensips[14888]: DBG:db_mysql:db_mysql_str2val:
converting INT [1423019849]
Feb 4 11:38:23 mySer /usr/sbin/opensips[14888]: DBG:msilo:m_dump: dumping [2]
messages for !!!
Feb 4 11:38:23 mySer /usr/sbin/opensips[14888]: DBG:msilo:msg_list_check_msg:
checking msgid=4836
Feb 4 11:38:23 mySer /usr/sbin/opensips[14888]: DBG:msilo:msg_list_check_msg:
msg already in sent list
Re: [OpenSIPS-Users] MSILO Module can't work
Hi,Bogdan: I test again ,the head like below: REGISTER sip:118.193.154.214 SIP/2.0 Via: SIP/2.0/TCP 10.0.2.10:1024;rport;branch=z9hG4bK189760539 From: ;tag=1892155303 To: Call-ID: 1489433135 CSeq: 1 REGISTER Contact: Max-Forwards: 70 User-Agent: LinphoneAndroid/2.0.2 (eXosip2/3.6.0) Expires: 3600 Content-Length: 0 REGISTER sip:118.193.154.214 SIP/2.0 Via: SIP/2.0/TCP 10.0.2.10:1024;rport;branch=z9hG4bK1625593069 From: ;tag=1892155303 To: Call-ID: 1489433135 CSeq: 2 REGISTER Contact: Authorization: Digest username="003", realm="118.193.154.214", nonce="54d1b3a90087b0d1245da49b53e193368d0b76f4358c", uri="sip:118.193.154.214", response="9557d32405a7991c33735aff9d54fcae", algorithm=MD5 Max-Forwards: 70 User-Agent: LinphoneAndroid/2.0.2 (eXosip2/3.6.0) Expires: 3600 Content-Length: 0 SIP/2.0 401 Unauthorized Via: SIP/2.0/TCP 10.0.2.10:1024;received=59.36.45.241;rport=1273;branch=z9hG4bK1505113328 From: ;tag=1892155303 To: ;tag=5c2831c51ae0c72390d6fc905fc065f7.c43f Call-ID: 1489433135 CSeq: 3 REGISTER WWW-Authenticate: Digest realm="118.193.154.214", nonce="54d1b3aa0089f875fca1bb2d1287147d37c160ac1921" Server: OpenSIPS (1.11.3-notls (x86_64/linux)) Content-Length: 0 SIP/2.0 200 OK Via: SIP/2.0/TCP 10.0.2.10:1024;received=59.36.45.241;rport=1273;branch=z9hG4bK1183991583 From: ;tag=1892155303 To: ;tag=5c2831c51ae0c72390d6fc905fc065f7.cae6 Call-ID: 1489433135 CSeq: 4 REGISTER Contact: ;q=1;expires=3600;received="sip:59.36.45.241:1273;transport=TCP" Server: OpenSIPS (1.11.3-notls (x86_64/linux)) Content-Length: 0 thanks a lot! At 2015-02-04 13:44:16, "tin" wrote: Hi, There has a stauts about 401 Unauthorized: SIP/2.0 401 Unauthorized Via: SIP/2.0/TCP 10.0.2.10:1024;received=59.36.45.241;rport=9782;branch=z9hG4bK1450910565 From: ;tag=2014338328 To: ;tag=5c2831c51ae0c72390d6fc905fc065f7.ab7b Call-ID: 1547875337 CSeq: 3 REGISTER WWW-Authenticate: Digest realm="118.193.154.214", nonce="54d192cf001ce25c63b4ab2f9483e02d77ebc3ebeede" Server: OpenSIPS (1.11.3-notls (x86_64/linux)) Content-Length: 0 thanks a lot! At 2015-02-03 18:05:43, "Bogdan-Andrei Iancu" wrote: Hi Tin, Once again, can you post the full REGISTER request here ? are you sure that REGISTER do advertise "MESSAGE" in the Allow header Also , you could enable full debug for the m_dump() function: set_debug(4); m_dump(); set_debug(); In this case, you may get a clue why the function does not send out the stored messages. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 03.02.2015 03:05, tin wrote: Dear Bogdan, Thanks for all your reply and kindly help. I definitely saw the record in DB. here are the records on my DB: mysql> select * from silo where ctype = 'text/plain'; +--+-+-+--+-+++--++---+ | id | src_addr| dst_addr| username | domain | inc_time | exp_time | snd_time | ctype | body | +--+-+-+--+-+++--++---+ | 3659 | sip:008@118.193.154.214 | sip:010@118.193.154.214 | 010 | 118.193.154.214 | 1422859611 | 1422895611 |0 | text/plain | coi | | 3667 | sip:008@118.193.154.214 | sip:010@118.193.154.214 | 010 | 118.193.154.214 | 1422860496 | 1423119696 |0 | text/plain | ggg | | 3669 | sip:008@118.193.154.214 | sip:010@118.193.154.214 | 010 | 118.193.154.214 | 1422860514 | 1423119714 |0 | text/plain | qqq | | 3671 | sip:008@118.193.154.214 | sip:010@118.193.154.214 | 010 | 118.193.154.214 | 1422860599 | 1423119799 |0 | text/plain | b | | 3719 | sip:003@118.193.154.214 | sip:010@118.193.154.214 | 010 | 118.193.154.214 | 1422868318 | 1423127518 |0 | text/plain | 456 | | 3718 | sip:003@118.193.154.214 | sip:010@118.193.154.214 | 010 | 118.193.154.214 | 1422868210 | 1423127410 |0 | text/plain | 123 | | 3717 | sip:003@118.193.154.214 | sip:010@118.193.154.214 | 010 | 118.193.154.214 | 1422867734 | 1423126934 |0 | text/plain | 999 | ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] MSILO Module can't work
Hi,Bogdan: I test again ,the head like below: 2913:52:11.99011359.36.45.241118.193.154.214SIP608Request: REGISTER sip:118.193.154.214 (1 binding) | 3813:52:11.990706118.193.154.21459.36.45.241SIP507Status: 401 Unauthorized | 5013:52:12.02445759.36.45.241118.193.154.214SIP817Request: REGISTER sip:118.193.154.214 (1 binding) | 6213:52:12.041409118.193.154.21459.36.45.241SIP784Status: 200 OK (1 binding) | 7013:52:12.08397259.36.45.241118.193.154.214SIP612Request: REGISTER sip:118.193.154.214 (1 binding) | 7613:52:12.084421118.193.154.21459.36.45.241SIP508Status: 401 Unauthorized | 8413:52:12.12568859.36.45.241118.193.154.214SIP820Request: REGISTER sip:118.193.154.214 (1 binding) | 9013:52:12.131621118.193.154.21459.36.45.241SIP787Status: 200 OK (1 binding) | thanks a lot! At 2015-02-03 18:05:43, "Bogdan-Andrei Iancu" wrote: Hi Tin, Once again, can you post the full REGISTER request here ? are you sure that REGISTER do advertise "MESSAGE" in the Allow header Also , you could enable full debug for the m_dump() function: set_debug(4); m_dump(); set_debug(); In this case, you may get a clue why the function does not send out the stored messages. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 03.02.2015 03:05, tin wrote: Dear Bogdan, Thanks for all your reply and kindly help. I definitely saw the record in DB. here are the records on my DB: mysql> select * from silo where ctype = 'text/plain'; +--+-+-+--+-+++--++---+ | id | src_addr| dst_addr| username | domain | inc_time | exp_time | snd_time | ctype | body | +--+-+-+--+-+++--++---+ | 3659 | sip:008@118.193.154.214 | sip:010@118.193.154.214 | 010 | 118.193.154.214 | 1422859611 | 1422895611 |0 | text/plain | coi | | 3667 | sip:008@118.193.154.214 | sip:010@118.193.154.214 | 010 | 118.193.154.214 | 1422860496 | 1423119696 |0 | text/plain | ggg | | 3669 | sip:008@118.193.154.214 | sip:010@118.193.154.214 | 010 | 118.193.154.214 | 1422860514 | 1423119714 |0 | text/plain | qqq | | 3671 | sip:008@118.193.154.214 | sip:010@118.193.154.214 | 010 | 118.193.154.214 | 1422860599 | 1423119799 |0 | text/plain | b | | 3719 | sip:003@118.193.154.214 | sip:010@118.193.154.214 | 010 | 118.193.154.214 | 1422868318 | 1423127518 |0 | text/plain | 456 | | 3718 | sip:003@118.193.154.214 | sip:010@118.193.154.214 | 010 | 118.193.154.214 | 1422868210 | 1423127410 |0 | text/plain | 123 | | 3717 | sip:003@118.193.154.214 | sip:010@118.193.154.214 | 010 | 118.193.154.214 | 1422867734 | 1423126934 |0 | text/plain | 999 | ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] segfault returning values from cachedb_redis
Please ignore my previous submission. The segfault was the result of undeleted references to older cache modules which I was no longer including. Apologies.___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
