Revision: 5881
http://openser.svn.sourceforge.net/openser/?rev=5881&view=rev
Author: henningw
Date: 2009-06-22 09:13:04 +0000 (Mon, 22 Jun 2009)
Log Message:
-----------
- fix CDR for accounting, reported from Mark Kent, markmac at noc dot mainstreet dot net
Modified Paths:
--------------
branches/1.5/etc/kamailio.cfg
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
Revision: 5880
http://openser.svn.sourceforge.net/openser/?rev=5880&view=rev
Author: henningw
Date: 2009-06-22 09:08:13 +0000 (Mon, 22 Jun 2009)
Log Message:
-----------
- fix a bunch of docs errors, wrong module name in modparam
- reported from Carlos A. Alvarez, carlos dot alvarez at commxinc dot com
Modified Paths:
--------------
branches/1.5/modules/siputils/README
branches/1.5/modules/siputils/doc/siputils_admin.xml
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
i gave sr invalid mi fifo command "foo" and got crash.
-- juha
Jun 22 10:38:47 localhost /usr/sbin/sip-router[12222]: ERROR: mi_fifo [fifo_fnc.c:466]: fifo command foo is not available
Jun 22 10:38:50 localhost kernel: [10840.769580] sip-router[12222]: segfault at 2 ip b72842c6 sp bfa4e430 error 4 in kex.so[b7280000+6000]
Jun 22 10:38:51 localhost /usr/sbin/sip-router[12238]: : <core> [pass_fd.c:283]: ERROR: receive_fd: EOF on 31
Program terminated with signal 11, Segmentation fault.
[New process 12222]
#0 0xb72842c6 in mi_debug (cmd=0x83e6338, param=0x0) at mi_core.c:336
336 new_debug = *((int*)vval);
(gdb) where
#0 0xb72842c6 in mi_debug (cmd=0x83e6338, param=0x0) at mi_core.c:336
#1 0xb72a898a in mi_fifo_server (fifo_stream=0x9ad5458)
at ../../lib/kmi/mi.h:89
#2 0xb72aa404 in fifo_process (rank=1) at mi_fifo.c:235
#3 0xb72aa67d in mi_child_init (rank=0) at mi_fifo.c:199
#4 0x080de71b in init_mod_child (m=0x822c2d8, rank=0) at sr_module.c:807
#5 0x080de690 in init_mod_child (m=0x822c3b8, rank=0) at sr_module.c:784
#6 0x080de690 in init_mod_child (m=0x822c498, rank=0) at sr_module.c:784
#7 0x080de690 in init_mod_child (m=0x822c570, rank=0) at sr_module.c:784
#8 0x080de690 in init_mod_child (m=0x822c728, rank=0) at sr_module.c:784
#9 0x080de690 in init_mod_child (m=0x822c838, rank=0) at sr_module.c:784
#10 0x080de690 in init_mod_child (m=0x822c910, rank=0) at sr_module.c:784
#11 0x08088115 in main_loop () at main.c:1386
#12 0x0808a9b7 in main (argc=135968704, argv=0x5) at main.c:2101
Hello!
Our company seeking for programmer who can create module for flexible database access.
I call it db_rest. This module must provide internal database API for other modules like db_auth.
For access to external data it must use HTTPS-server and use REST-style data access
(http://en.wikipedia.org/wiki/Representational_State_Transfer).
Instead of making query like "SELECT f1,f2,f3 FROM tableA WHERE f4 = 'somevalue'" it must call
HTTPS-server like this:
GET http://hostname/database/tableA&c=f1,f2,f3&k=f4&op=eq&v=somevalue
Server must return delimiter-separated data.
Similarly (using POST) it must implement support for insert, update and so on.
Of course we would like to see this module inside the main project repository.
If you are interested please contact me for details (requirements, $$).
--
Konstantin
Bugs item #2810005, was opened at 2009-06-21 21:51
Message generated for change (Tracker Item Submitted) made by nobody
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=743020&aid=2810005&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: core
Group: ver 1.5.x
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: exec_msg produces critical unknown address family message
Initial Comment:
In the kamailio.cfg file, I have a line
exec_msg("/usr/local/etc/kamailio/100out"); and every time it runs (every 10 seconds), it produces the following messages in the syslog. Since it is being executed from the local machine, the log message needs reviewing.
Jun 21 06:31:20 sipserver /usr/local/sbin/kamailio[20969]: CRITICAL:exec:ip_addr2a: unknown address family 0
Jun 21 06:32:00 sipserver last message repeated 4 times
Jun 21 06:33:00 sipserver last message repeated 6 times
Jun 21 06:34:00 sipserver last message repeated 6 times
Jun 21 06:35:00 sipserver last message repeated 6 times
Jun 21 06:36:00 sipserver last message repeated 6 times
Jun 21 06:37:00 sipserver last message repeated 6 times
Jun 21 06:38:00 sipserver last message repeated 6 times
Jun 21 06:38:30 sipserver last message repeated 3 times
The file 100out contains:
#!/bin/bash
# buld a FIFO command to PUBLISH number of users, load, system CPU usage
# and freem memory in the system
#
#config values
OP_SYSUSER="100(a)sip.nzvrs.co.nz"
OP_SIPURI="sip:$OP_SYSUSER"
OP_EXPIRES="12"
#build reply fifo file
rm -f /tmp/kamailio_fifo_reply
mkfifo /tmp/kamailio_fifo_reply
cat /tmp/kamailio_fifo_reply&
cat >/tmp/kamailio_fifo <<EOF
:pua_publish:kamailio_fifo_reply
$OP_SIPURI
$OP_EXPIRES
presence
application/pidf+xml
.
.
<?xml version='1.0' encoding='UTF-8'?><presence xmlns='urn:ietf:params:xml:ns:pidf' xmlns:dm='urn:ietf:params:xml:ns:pidf:data-model' xmlns:rpid='urn:ietf:params:xml:ns:pidf:rpid' xmlns:c='urn:ietf:params:xml:ns:pidf:cipid' xmlns:lt='urn:ietf:params:xml:ns:location-type' entity='pres:$OP_SYSUSER'><tuple id='102(a)sip.nzvrs.co.nz_on_Peter-PC'><note>dnd - Not currently operating</note><status><basic>open</basic></status><contact priority='1'>$OP_SIPURI</contact></tuple><dm:person id='pdb42f565'><rpid:activities><rpid:busy/></rpid:activities><dm:note>Closed - Please wait</dm:note></dm:person></presence>
EOF
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=743020&aid=2810005&group_…
Bugs item #2809998, was opened at 2009-06-21 21:29
Message generated for change (Tracker Item Submitted) made by nobody
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=743020&aid=2809998&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: modules
Group: ver 1.5.x
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: pua:pres_process_body: No more memory
Initial Comment:
The mi_pua_publish appears to run out of memory. The syslog is shown below.
Every 10 seconds, the following command is run from the configuration file
exec_msg("/usr/local/etc/kamailio/100avail");
This causes the error message "CRITICAL:exec:ip_addr2a: unknown address family 0" (This bug will be identified in a separate bug report)
The file 100avail is based on the example http://www.kamailio.org/dokuwiki/doku.php/presence:pua-modules#publish_deta…
This configuration has been running for 3-4 days before this problem showed up.
Jun 21 12:45:40 sipserver /usr/local/sbin/kamailio[20975]: CRITICAL:core:mk_proxy: pkg memory allocation failure
Jun 21 12:45:40 sipserver /usr/local/sbin/kamailio[20975]: ERROR:tm:uri2proxy: bad host name in URI <sip:100@sip.nzvrs.co.nz>
Jun 21 12:45:40 sipserver /usr/local/sbin/kamailio[20975]: ERROR:tm:uri2su: failed create a dst proxy
Jun 21 12:45:40 sipserver /usr/local/sbin/kamailio[20975]: ERROR:tm:t_uac: no socket found
Jun 21 12:45:40 sipserver /usr/local/sbin/kamailio[20975]: ERROR:pua:send_publish: in t_request tm module function
Jun 21 12:45:40 sipserver /usr/local/sbin/kamailio[20975]: ERROR:pua_mi:mi_pua_publish: sending publish failed
Jun 21 12:45:40 sipserver /usr/local/sbin/kamailio[20975]: ERROR:core:init_mi_tree: no more pkg mem
Jun 21 12:45:40 sipserver /usr/local/sbin/kamailio[20975]: ERROR:mi_fifo:mi_fifo_server: command (pua_publish) processing failed
Jun 21 12:45:50 sipserver /usr/local/sbin/kamailio[20969]: CRITICAL:exec:ip_addr2a: unknown address family 0
Jun 21 12:45:50 sipserver /usr/local/sbin/kamailio[20975]: CRITICAL:core:mk_proxy: pkg memory allocation failure
Jun 21 12:45:50 sipserver /usr/local/sbin/kamailio[20975]: ERROR:tm:uri2proxy: bad host name in URI <sip:100@sip.nzvrs.co.nz>
Jun 21 12:45:50 sipserver /usr/local/sbin/kamailio[20975]: ERROR:tm:uri2su: failed create a dst proxy
Jun 21 12:45:50 sipserver /usr/local/sbin/kamailio[20975]: ERROR:tm:t_uac: no socket found
Jun 21 12:45:50 sipserver /usr/local/sbin/kamailio[20975]: ERROR:pua:send_publish: in t_request tm module function
Jun 21 12:45:50 sipserver /usr/local/sbin/kamailio[20975]: ERROR:pua_mi:mi_pua_publish: sending publish failed
Jun 21 12:45:50 sipserver /usr/local/sbin/kamailio[20975]: ERROR:core:init_mi_tree: no more pkg mem
Jun 21 12:45:50 sipserver /usr/local/sbin/kamailio[20975]: ERROR:mi_fifo:mi_fifo_server: command (pua_publish) processing failed
Jun 21 12:46:00 sipserver /usr/local/sbin/kamailio[20969]: CRITICAL:exec:ip_addr2a: unknown address family 0
Jun 21 12:46:00 sipserver /usr/local/sbin/kamailio[20975]: ERROR:pua:pres_process_body: NO more memory
Jun 21 12:46:00 sipserver /usr/local/sbin/kamailio[20975]: ERROR:pua:send_publish: while processing body
Jun 21 12:46:00 sipserver /usr/local/sbin/kamailio[20975]: ERROR:pua:send_publish: NULL body
Jun 21 12:46:00 sipserver /usr/local/sbin/kamailio[20975]: ERROR:pua_mi:mi_pua_publish: sending publish failed
Jun 21 12:46:00 sipserver /usr/local/sbin/kamailio[20975]: ERROR:core:init_mi_tree: no more pkg mem
Jun 21 12:46:00 sipserver /usr/local/sbin/kamailio[20975]: ERROR:mi_fifo:mi_fifo_server: command (pua_publish) processing failed
The workaround I have invoked is to use the uac_req_send(); functions instead of using the fifo.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=743020&aid=2809998&group_…
Hi, as part of my personal battle against SIP ALG routers, I've created an
utility to detect such routers:
http://dev.sipdoc.net/wiki/sip-stuff/SIP-ALG-Detector
It has two parts: client and server:
Basically, the client node running into the LAN sends an INVITE to the server
node (running in a host with public IP).
The request could be modified by the LAN router if SIP ALG is enabled.
The server encodes the received request in Base64 and appends it to the SIP
response.
The client receives the response, decodes the body and gets the request as it
arrived to the server.
Then it creates a diff between the original request and the the request the
server node received. These differences are displayed in the screen.
Both, UDP and TCP, tests are performed.
The client node is coded in Ruby and should work in any operating system (if
Ruby is installed).
The server node is also coded in Ruby.
For those interested in try it, I have a server node running in my personal
server:
87.98.230.161:5060
You can test the client against my server.
Feedback is welcome :)
Regards.
--
Iñaki Baz Castillo <ibc(a)aliax.net>