sr-users

sr-users@lists.kamailio.org

42 participants
37519 discussions

TSILO on Kamailio 5.2.0
by Володимир Іванець 29 Jan '19

29 Jan '19

Hello! I am trying to repeat awesome configuration provided by Federico Cabiddu https://www.youtube.com/watch?v=4XIrR9bwUkM but only got it to work partially. So I'm wondering if someone else has same problem as me on latest Kamailio? I have two clients configured on 100-test account. Only one is registered. When *ts_store()* is executed on INVITE I get: *Jan 28 19:17:46 test /usr/sbin/kamailio[11204]: DEBUG: tsilo [ts_store.c:80]: ts_store(): storing transaction 29157:1612520187 for r-uri: 100-test* *Jan 28 19:17:46 test /usr/sbin/kamailio[11204]: DEBUG: tsilo [ts_hash.c:264]: insert_ts_urecord(): urecord entry 0x7f2bfcf7dd78* *Jan 28 19:17:46 test /usr/sbin/kamailio[11204]: DEBUG: tsilo [ts_handlers.c:56]: ts_set_tm_callbacks(): registered TMCB for transaction 29157:1612520187* *Jan 28 19:17:46 test /usr/sbin/kamailio[11204]: DEBUG: tsilo [ts_store.c:103]: ts_store(): transaction 29157:1612520187 (ruri: 100-test) inserted* *# kamcmd ts.dump*: *{* * Size: 2048* * R-URIs: {* * R-URI: 100-thirdlane* * Hash: 451001090* * Transactions: {* * Transaction: {* * Tindex: 29157* * Tlabel: 1612520187* * }* * }* * }* * Stats: {* * RURIs: 1* * Max-Slots: 1* * Transactions: 1* * }* *}* When second UAC registers, *ts_append("location", "$tU")* in route *PUSHJOIN* is executed. It throws following error: *Jan 28 19:18:10 test /usr/sbin/kamailio[11210]: ERROR: tsilo [tsilo.c:199]: ts_check_uri(): bad uri [100-test]* At same time running *kamcmd ts.lookup 100-test* command returns expected result: *{* * Transaction: {* * Tindex: 29157* * Tlabel: 1612520187* * }* *}* Thanks a lot!

2 2

Kamailio IMS Deployment
by Yağız AYDIN 29 Jan '19

29 Jan '19

Hello everyone, I'm new to Kamailio environment, and trying to implement Kamailio IMS services with FHoSS HSS on a single Ubuntu 18.04 . I have followed instructions on the Kamailio website, but faced some issues. I have managed to install FHoSS, but when I try to start HSS, i got following errors: [Thread-24] ERROR de.fhg.fokus.diameter.DiameterPeer.peer.StateMachine - StateMachine: Peer icscf.mnc001.mcc001.3gppnetwork.org:3869 not responding to connection attempt [Thread-24] ERROR de.fhg.fokus.diameter.DiameterPeer.peer.StateMachine - StateMachine: Peer scscf.mnc001.mcc001.3gppnetwork.org:3870 not responding to connection attempt I have started CSCFs by following commands: root@ulak-HP-ZBook-15:/opt/OpenIMSCore/FHoSS/deploy# kamailio -f /etc/kamailio/pcscf/kamailio-pcscf.cfg loading modules under config path: /usr/lib/x86_64-linux-gnu/kamailio/modules Listening on udp: 10.3.0.188 [10.3.0.188]:5060 Aliases: *: pcscf.mnc001.mcc001.3gppnetwork.org:* ************************************************ root@ulak-HP-ZBook-15:/opt/OpenIMSCore/FHoSS/deploy# kamailio -f /etc/kamailio/scscf/kamailio-scscf.cfg loading modules under config path: /usr/lib/x86_64-linux-gnu/kamailio/modules Listening on udp: 10.3.0.188 [10.3.0.188]:6060 Aliases: *: scscf.mnc001.mcc001.3gppnetwork.org:* *********************************************** root@ulak-HP-ZBook-15:/opt/OpenIMSCore/FHoSS/deploy# kamailio -f /etc/kamailio/icscf/kamailio-icscf.cfg loading modules under config path: /usr/lib/x86_64-linux-gnu/kamailio/modules Listening on udp: 10.3.0.188 [10.3.0.188]:4060 tcp: 10.3.0.188 [10.3.0.188]:4060 Aliases: *: icscf.mnc001.mcc001.3gppnetwork.org:* How do I ensure that CSCFs work? And also how can I troubleshoot error that I've faced on FHoSS. I have attached my config files. Any helps will be appreciated. Best regards, Yağız --

2 1

TM Module - Unfortunately error on sending to next hop occurred (477/TM)
by Ilie Soltanici 28 Jan '19

28 Jan '19

Hello, Can someone help me to understand this error given by TM Module? I have a Kamailio SIP Proxy running in front of a few Asterisk boxes. On average, he is processing 70-80 requests per second. The problem is that sometimes (90-100 times/day) - I see such errors in the logs: 500 I'm terribly sorry, server error occurred (1/SL) 477 Unfortunately error on sending to next hop occurred (477/TM) Trying to investigate this error - I found that this is happening randomly and for INVITES coming from the Asterisk Box. For ex, the INVITE below: 192.168.180.10 - Kamailio Server 192.168.180.36 - Asterisk Server INVITE sip:1001@192.168.180.10:5060 SIP/2.0 Via: SIP/2.0/UDP 192.168.180.36:5060;branch=z9hG4bK4624ab4e;rport Max-Forwards: 70 From: "Anonymous" <sip:anonymous@192.168.180.10>;tag=as11bed8a6 To: <sip:1001@192.168.180.10:5060> Contact: <sip:anonymous@192.168.180.36:5060> Call-ID: 0ea8535d3a5ecaa6432912a2566c807f(a)192.168.180.10 CSeq: 102 INVITE User-Agent: MYCOMPANY Date: Mon, 28 Jan 2019 16:01:56 GMT Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE Supported: replaces, timer Content-Type: application/sdp Content-Length: 251 v=0 o=SIP 2139556641 2139556641 IN IP4 192.168.180.36 s=MYCOMPANY PBX c=IN IP4 192.168.180.36 t=0 0 m=audio 14674 RTP/AVP 8 0 101 a=rtpmap:8 PCMA/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ptime:20 a=sendrecv Kamailio is replying back with 100 Trying and then with 500/477 errors: SIP/2.0 100 Trying Via: SIP/2.0/UDP 192.168.180.36:5060 ;branch=z9hG4bK4624ab4e;rport=5060;received=192.168.180.36 From: "Anonymous" <sip:anonymous@192.168.180.10>;tag=as11bed8a6 To: <sip:1001@192.168.180.10:5060> Call-ID: 0ea8535d3a5ecaa6432912a2566c807f(a)192.168.180.10 CSeq: 102 INVITE Server: MYCOMPANY SBC Content-Length: 0 SIP/2.0 500 I'm terribly sorry, server error occurred (1/SL) Via: SIP/2.0/UDP 192.168.180.36:5060 ;branch=z9hG4bK4624ab4e;rport=5060;received=192.168.180.36 From: "Anonymous" <sip:anonymous@192.168.180.10>;tag=as11bed8a6 To: <sip:1001@192.168.180.10:5060>;tag=9dd61ff61e802d8e2bef5f14621ef3c2.2e93 Call-ID: 0ea8535d3a5ecaa6432912a2566c807f(a)192.168.180.10 CSeq: 102 INVITE Server: MYCOMPANY SBC Content-Length: 0 SIP/2.0 477 Unfortunately error on sending to next hop occurred (477/TM) Via: SIP/2.0/UDP 192.168.180.36:5060 ;branch=z9hG4bK4624ab4e;rport=5060;received=192.168.180.36 From: "Anonymous" <sip:anonymous@192.168.180.10>;tag=as11bed8a6 To: <sip:1001@192.168.180.10:5060>;tag=a6a1c5f60faecf035a1ae5b6e96e979a-2e93 Call-ID: 0ea8535d3a5ecaa6432912a2566c807f(a)192.168.180.10 CSeq: 102 INVITE Server: MYCOMPANY SBC Content-Length: 0 And I cannot actually get what is wrong with this INVITE - and why Kamailio cannot process it? Other calls for the same extension are working fine, this is happening randomly and with different extensions. Load on the server is very low: [root@kamailio root]# nproc 8 [root@kamailio root]# uptime 17:49:15 up 8 days, 21:17, 6 users, load average: 0.66, 0.56, 0.52 [root@kamailio root]# free -m total used free shared buff/cache available Mem: 7981 4283 142 818 3556 2581 Swap: 6141 137 6004 [root@kamailio root]# ss -4 -n -l | grep 5060 udp UNCONN 0 0 192.168.180.10 :5060 *:* udp UNCONN 0 0 127.0.0.1:5060 *:* tcp LISTEN 0 128 192.168.180.10 :5060 *:* tcp LISTEN 0 128 127.0.0.1:5060 *:* In the kamailio logs I found that kamailio was able to get the contact address: kamailio[18168]: INFO: {INVITE (1) Contacts loaded for 1001} kamailio[18168]: INFO: {INVITE (1) t_next_contacts - Only one contact found for 1001, calling} kamailio[18168]: INFO: {INVITE (1) Next Hop: <192.168.180.211:3126>} I don't know how to reproduce this - I tried to disconnect the phone from the power source - and made a call to that extension, and it is giving timeouts - like it is supposed to be. What could be the problem and how I can fix it? Thank You.

1 0

Playing with Diameter - Error opening connection to :3868
by Steve Bucklin 28 Jan '19

28 Jan '19

Hello all, I am brand new to this list and I am also on a steep learning curve with Kamailio and Diameter.... so please be gentle as I am just starting! I am trying to look at the Diameter signaling and have a glimpse into the information passed. I have set up a compiled 5.2 on CentOS 7. I suspect that I am missing something obvious, but not sure what. I am seeing this error: INFO: cdp [peerstatemachine.c:525]: I_Snd_Conn_Req(): I_Snd_Conn_Req(): Peer peer_connect(): peer_connect(): Error opening connection to :3868 >Name or service not known It looks like the FQDN in the diameter.xml under 'peer' is not being resolved, as it is seeing port 3868? Any pointers would be greatly taken :-) Here is my diameter: <?xml version="1.0" encoding="UTF-8"?> <DiameterPeer FQDN="mra1.testservers.xxx" Realm="testservers.xxx" Vendor_Id="10415" Product_Name="CDiameterPeer" AcceptUnknownPeers="1" DropUnknownOnDisconnect="1" Tc="30" Workers="16" QueueLength="32" TransactionTimeout="5" SessionsHashSize="128" DefaultAuthSessionTimeout="3600" MaxAuthSessionTimeout="3600" > <peer FGDN="mra2.testservers.xxx" Realm="testservers.xxx" proto="sctp" port="3868"/> <Acceptor port="3868" bind="192.168.1.20"/> <Auth id="16777251" vendor="10415"/>  <SupportedVendor vendor="10415" /> </DiameterPeer> And here is what I am getting on the startup: Jan 28 14:19:35 telco-lon1-02 kamailio: INFO: <core> [core/tcp_main.c:4722]: init_tcp(): using epoll_lt as the io watch method (auto detected) Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22778]: INFO: <core> [main.c:2649]: main(): processes (at least): 29 - shm size: 67108864 - pkg size: 8388608 Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22778]: INFO: cdp [cdp_mod.c:240]: cdp_child_init(): CDiameterPeer child starting ... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22783]: INFO: cdp [worker.c:332]: worker_process(): [1] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22778]: INFO: cdp [cdp_mod.c:242]: cdp_child_init(): ... CDiameterPeer child started Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22790]: INFO: cdp [worker.c:332]: worker_process(): [8] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22784]: INFO: cdp [worker.c:332]: worker_process(): [2] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22786]: INFO: cdp [worker.c:332]: worker_process(): [4] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22793]: INFO: cdp [worker.c:332]: worker_process(): [11] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22794]: INFO: cdp [worker.c:332]: worker_process(): [12] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22796]: INFO: cdp [worker.c:332]: worker_process(): [14] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22788]: INFO: cdp [worker.c:332]: worker_process(): [6] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22799]: INFO: cdp [receiver.c:455]: receiver_process(): receiver_process(): [] Receiver process doing init on new process... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22799]: INFO: cdp [receiver.c:188]: add_serviced_peer(): add_serviced_peer(): Adding serviced_peer_t to receiver for peer [] Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22799]: INFO: cdp [receiver.c:460]: receiver_process(): receiver_process(): [] Receiver process starting up... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22791]: INFO: cdp [worker.c:332]: worker_process(): [9] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22792]: INFO: cdp [worker.c:332]: worker_process(): [10] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22785]: INFO: cdp [worker.c:332]: worker_process(): [3] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22787]: INFO: cdp [worker.c:332]: worker_process(): [5] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22795]: INFO: cdp [worker.c:332]: worker_process(): [13] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22782]: INFO: cdp [worker.c:332]: worker_process(): [0] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22789]: INFO: cdp [worker.c:332]: worker_process(): [7] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22797]: INFO: cdp [worker.c:332]: worker_process(): [15] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22798]: INFO: cdp [receiver.c:455]: receiver_process(): receiver_process(): [] Receiver process doing init on new process... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22798]: INFO: cdp [receiver.c:460]: receiver_process(): receiver_process(): [] Receiver process starting up... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22800]: INFO: cdp [acceptor.c:81]: acceptor_process(): Acceptor process starting up... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22800]: WARNING: cdp [tcp_accept.c:121]: create_socket(): create_socket(): Trying to open/bind/listen on 192.168.1.20 port 3868 Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22800]: WARNING: cdp [tcp_accept.c:146]: create_socket(): create_socket(): Successful socket open/bind/listen on 192.168.1.20 port 3868 Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22800]: INFO: cdp [acceptor.c:95]: acceptor_process(): Acceptor opened sockets. Entering accept loop ... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22801]: INFO: cdp [timer.c:205]: timer_process(): Timer process starting up... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22802]: INFO: ctl [io_listener.c:214]: io_listen_loop(): io_listen_loop: using epoll_lt io watch method (config) Jan 28 14:19:36 telco-lon1-02 journal: [Diameter Routing Agent][22801]: INFO: cdp [peerstatemachine.c:525]: I_Snd_Conn_Req(): I_Snd_Conn_Req(): Peer Jan 28 14:19:36 telco-lon1-02 journal: [Diameter Routing Agent][22801]: WARNING: cdp [receiver.c:866]: peer_connect(): peer_connect(): Error opening connection to :3868 >Name or service not known Thanks, Steve

2 2

database reconnection db_unixodbc
by Karthik Srinivasan 27 Jan '19

27 Jan '19

Hello, I am testing how kamailio reacts to various database conditions. One such condition is if the database engine is simply shut down (that is, database server process no longer running, tcp listening socket closed, etc...) I am utilizing the db_unixodbc module to connect to an Informix database engine. I am currently running on Kamailio version 5.0. I have a test query that executes against the database engine every 10 seconds. Here is what i have noticed if i shut down the database engine at some point after i run Kamailio. the first test query that attempts to run against the db engine fails; it tries to reconnect and fails. The second test query (10 seconds after the 1st) results in a SIG_CHILD and shuts down the entire Kamailio process. Has anyone experienced this? Is there a solution to this? Ideally the second query should also fail and return gracefully; and ideally queries continue to fail until the database engine is back up. See logs below: Jan 17 20:07:25 [29297]: INFO: (s) SQL query: FIRST TEST QUERY Jan 17 20:07:25 [29297]: ERROR: db_unixodbc [dbase.c:135]: db_unixodbc_submit_query(): rv=-1. Query= FIRST TEST QUERY Jan 17 20:07:25 [29297]: ERROR: db_unixodbc [connection.c:220]: db_unixodbc_extract_error(): unixodbc:SQLExecDirect=08S01:1:-11020:[Informix][Informix ODBC Driver]Communication link failure. Jan 17 20:07:25 [29297]: ERROR: db_unixodbc [dbase.c:59]: reconnect(): Attempting DB reconnect Jan 17 20:07:25 [29297]: ERROR: db_unixodbc [dbase.c:74]: reconnect(): failed to connect Jan 17 20:07:25 [29297]: ERROR: db_unixodbc [connection.c:220]: db_unixodbc_extract_error(): unixodbc:SQLDriverConnect=08002:1:0:[unixODBC][Driver Manager]Connection name in use Jan 17 20:07:25 [29297]: ERROR: db_unixodbc [connection.c:220]: db_unixodbc_extract_error(): unixodbc:SQLDriverConnect=HY010:2:-11067:[Informix][Informix ODBC Driver]Function sequence error. Jan 17 20:07:25 [29297]: ERROR: <core> [db_query.c:181]: db_do_raw_query(): error while submitting query Jan 17 20:07:25 [29297]: ERROR: sqlops [sql_api.c:265]: sql_do_query(): cannot do the query FIRST TEST QUERY Jan 17 20:07:25 [29297]: INFO: (s) [123] SQL ret: fail (-1) Jan 17 20:07:25 [29297]: INFO: (s) [123] SQL res: no rows Jan 17 20:07:35 [29297]: INFO: (s) [123] SQL query: 10 seconds later the SECOND TEST QUERY (it's the same query as the first one) Jan 17 20:07:35 [29301]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 28 Jan 17 20:07:35 [29283]: ALERT: <core> [main.c:744]: handle_sigs(): child process 29297 exited by a signal 11 Jan 17 20:07:35 [29283]: ALERT: <core> [main.c:747]: handle_sigs(): core was not generated Jan 17 20:07:35 [29283]: INFO: <core> [main.c:759]: handle_sigs(): terminating due to SIGCHLD Jan 17 20:07:35 [29301]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29295]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29291]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29288]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29300]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29284]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29286]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29293]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29289]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29287]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29292]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29296]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29298]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29299]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29285]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29294]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29290]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29283]: INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized Thank you, Karthik

2 5

Why kamailio can not be a consumer of RabbitMQ?
by CuiGang 26 Jan '19

26 Jan '19

Hello every one. I noticed that module RABBITMQ just implements the publish functions. It means kamailio can only as a producer of RabbitMQ. My question is Why RABBITMQ module not implement consumer functions? As NSQ, let kamailio can be a consumer receive messages from RabbitMQ. Regards. CuiGang cuigang0120(a)aliyun.com

2 1

DMQ errors
by Aleksandar Sosic 25 Jan '19

25 Jan '19

Hi, when I have only one node and dmq enabled I've got this errors: ``` 17(45) ERROR: dmq [notification_peer.c:337]: add_server_and_notify(): error adding notification node 17(45) ERROR: dmq [dmq_funcs.c:516]: ping_servers(): cannot retrieve initial nodelist from sip:dmq-router-service.alex.svc.cluster.local:5062 ``` On the second node booting after this one I don't get any of these errors. Is there any flag/option to turn off this error on the `cannot retrieve initial nodelist` in case I have only one node for a period of time? Thanks, -- Aleksandar Sosic linkedin.com/in/alexsosic/ mail: alex.sosic(a)evosip.cloud

2 2

Re: [SR-Users] kamailio-lb fails after topos enabled.
by Daniel Tryba 25 Jan '19

25 Jan '19

On Fri, Jan 25, 2019 at 10:19:45AM -0300, Marcos Pytel wrote: > Could you help me to catch the coredump file? Please keep the mailinglist in the loop. > When I execute bt full the systems shows "no symbols". What package i need to perform it? I don't know what the sipwise config is, but it if is (anything like) debian the normal kamailio package is strippped of debugging symbols. You'll need to install the debug package (kamailio-dbg in debian).

1 0

kamailio-lb fails after topos enabled.
by Marcos Pytel 25 Jan '19

25 Jan '19

Hi team! I'm using Kamailio version: kamailio 5.1.6 (x86_64/linux). When I enabled topos, after a few minutes i get this erros in the log file and the LB Service goes down.: Jan 24 13:20:21 sipwise lb[30130]: ERROR: ndb_redis [redis_client.c:903]: redisc_exec_argv(): Redis error: Server closed the connection Jan 24 13:21:36 sipwise lb[30132]: ERROR: ndb_redis [redis_client.c:903]: redisc_exec_argv(): Redis error: Server closed the connection Jan 24 13:29:06 sipwise lb[30135]: ERROR: ndb_redis [redis_client.c:903]: redisc_exec_argv(): Redis error: Server closed the connection Jan 24 13:31:36 sipwise lb[30133]: ERROR: ndb_redis [redis_client.c:903]: redisc_exec_argv(): Redis error: Server closed the connection Jan 24 13:34:41 sipwise lb[30130]: ERROR: ndb_redis [redis_client.c:903]: redisc_exec_argv(): Redis error: Server closed the connection Jan 24 13:43:06 sipwise lb[30134]: ERROR: ndb_redis [redis_client.c:903]: redisc_exec_argv(): Redis error: Server closed the connection Jan 24 13:45:21 sipwise lb[30136]: ERROR: ndb_redis [redis_client.c:903]: redisc_exec_argv(): Redis error: Server closed the connection Jan 24 13:47:06 sipwise lb[30132]: ERROR: ndb_redis [redis_client.c:903]: redisc_exec_argv(): Redis error: Server closed the connection Jan 24 13:47:21 sipwise lb[30136]: ERROR: topos [tps_storage.c:340]: tps_storage_link_msg(): bad sip message or missing Contact hdr Jan 24 13:47:35 sipwise lb[30163]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 23 Jan 24 13:47:35 sipwise lb[30066]: ALERT: <core> [main.c:738]: handle_sigs(): child process 30120 exited by a signal 6 Jan 24 13:47:35 sipwise lb[30066]: ALERT: <core> [main.c:741]: handle_sigs(): core was generated I attached the coredump file. I tried to get bt full but i think that i need something else to catch it. Thank you! Marcos.

2 2

ERROR while using KEMI - Python
by Prabhat Kumar 25 Jan '19

25 Jan '19

Hi, I am getting this error message while starting kamailio. Enviroment: OS- Ubuntu 16.04.5 LTS (Xenial Xerus) python 2.7 ERROR: app_python [app_python_mod.c:164]: mod_init(): failed to load python script ERROR: <core> [core/sr_module.c:990]: init_mod(): Error while initializing module app_python (/usr/local/lib64/kamailio/modules/app_python.so)

2 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users