With an amazing 2015 almost gone, I am using this moment to give my
thanks and greetings to the people involved in Kamailio project, old and
new friends, developers, contributors, the engaged and warm community
members.
Very soon 2016 will arrive, Kamailio will celebrate 15 years of
development, therefore we are looking to a special year ahead!
Merry Christmas and Happy Winter Holidays!
Daniel
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
To test, create the following event_route in your script:
event_route[tcp:closed] {
xlogl("L_INFO", "TCP connection closed: si=$si sp=$sp conid=$conid proto=$proto\n");
}
Then connect to the server via TCP, TLS, WS, or WSS, and explicitly kill the connection between kamailio and the client using tcpkill or something similar, or alternatively, time out the TCP connection by unplugging a SIP phone or inserting IPtables rules to block traffic. You should see event_route[tcp:closed] get executed.
Please let me know if you find issues with this approach. Thanks!
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/commit/4cc9545b0056bcacf8a303259e629df…
On some systems compiling cnxcc we get:
cnxcc.h:36:12: warning: inline function �timestamp2isodt� declared but never defined
inline int timestamp2isodt(str *dest, unsigned int timestamp);
^
cnxcc.h:35:21: warning: inline function �get_current_timestamp� declared but never defined
inline unsigned int get_current_timestamp();
^
cnxcc.h:34:13: warning: inline function �get_datetime� declared but never defined
inline void get_datetime(str *dest);
and then at runtime:
ERROR: <core> [sr_module.c:576]: load_module(): could not open module </usr/lib64/kamailio/modules/cnxcc.so>: /usr/lib64/kamailio/modules/cnxcc.so: undefined symbol: get_current_timestamp
The present patch moves the definition of the inline functions into the .h file.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/453
-- Commit Summary --
* cnxcc: define inline functions in cnxcc.h
-- File Changes --
M modules/cnxcc/cnxcc.c (24)
M modules/cnxcc/cnxcc.h (27)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/453.patchhttps://github.com/kamailio/kamailio/pull/453.diff
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/453
Dear friends,
I am working on a program on Kamailio and rtpengine proxy. I am wondering whether can I set Kamailio and rtpengine daemon on different physical machines. For example, I set Kamailio on a machine with IP address:10.109.247.80, and launch rtpengine daemon on another machine with interface parameter as 10.109.247.90 and ng port 7723. I set parameter in Kamailio.cfg with modparam(“rtpengine”, “rtpengine_sock”, “udp:10.109.247.90:7723”).
Unfortunately I got debug message like this:
ERROR: rtpengine [rtpengine.c:1710]: send_rtpp_command(): can't send command to a RTP proxy
ERROR: rtpengine [rtpengine.c:1746]: send_rtpp_command(): proxy <udp:10.109.247.90:7723> does not respond, disable it
ERROR: rtpengine [rtpengine.c:1616]: rtpp_test(): proxy did not respond to ping
And, I also tried to set Kamailio and rtpengine daemon in a same machine,and use modparam(“rtpengine”, “rtpengine_sock”, “udp:localhost:7723”). And Kamailio can work functionally under this situation. rtpengine daemon can receive ping message from Kamailio and rtpengine daemon can work as suspected. So for the later case, is it supposed that Kamailio be in the same machine with same localhost address? Otherwise, what’s the reason for my ERROR?
------------------------------------
北京邮电大学网络技术研究院
网络与交换技术国家重点实验室
田军
+86 18810315790
mozillafire(a)bupt.edu.cn
------------------------------------