Hi,
Just a small patch to synchronize the name of the expired contact event to the documentation.
Documentation refers to 'usrloc:contact-expired', the registrar code to 'usrloc:expired-contact'.
I thought it was easier to update the code rather than all the documentation.
if(ul.register_ulcb != NULL)
{
- reg_expire_event_rt = route_lookup(&event_rt, "usrloc:expired-contact");
+ reg_expire_event_rt = route_lookup(&event_rt, "usrloc:contact-expired");
if (reg_expire_event_rt>=0 && event_rt.rlist[reg_expire_event_rt]==0)
reg_expire_event_rt=-1; /* disable */
Regards,
Giacomo
Truphone Limited, registered in England and Wales (registered company number: 04187081). Registered office: 4 Royal Mint Court, London EC3N 4HJ. VAT No. GB 851 5278 19
This e-mail, and any attachment(s), may contain information which is confidential and/or privileged, and is intended for the addressee only. If you are not the intended recipient, you may not use, disclose, copy or distribute this information in any manner whatsoever. If you have received this e-mail in error, please contact the sender immediately and delete it.
Hi!
Got a bit surprised again - but I've always been confused by the build system... ;-)
I ran
make
make modules
and then
make install
At "make install" Kamailio builds the .so modules again but even more importantly - it seems to build kamcmd from scratch by compiling the source code. I think this should be done at "make".
I haven't gone through all the output to check for other utilities, but if some Makefile guru can look at this and there's no opinion about why it should be this way, I suggest we fix it so that we build everything at "make", all modules are built and linked at "make modules" and let "make install" just install and not build.
/O
CC (gcc) [U kamcmd] parse_listen_id.o
CC (gcc) [U kamcmd] sercmd.o
LD (gcc) [U kamcmd] kamcmd
sed -e "s#sercmd#kamcmd#g" \
-e "s#sip-router#kamailio#g" \
< sercmd.8 > /usr/local/share/man//man8/kamcmd.8
chmod 644 /usr/local/share/man//man8/kamcmd.8
touch /usr/local/sbin//kamcmd
Hi!
The README example for the xhttp_rpc_buf_size parameter lacks a full example (the value is left out) and the explanation does not specificy a unit - is it bytes, kilobytes or terabytes?
/O
Module: sip-router
Branch: master
Commit: 7f5b6c26d4bf1f50b1890d177121f4c4fd65428c
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=7f5b6c2…
Author: Ovidiu Sas <osas(a)voipembedded.com>
Committer: Ovidiu Sas <osas(a)voipembedded.com>
Date: Wed Feb 6 23:39:27 2013 -0500
xhttp_pi: documentation updates
---
modules/xhttp_pi/README | 4 ++--
modules/xhttp_pi/doc/xhttp_pi_admin.xml | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/modules/xhttp_pi/README b/modules/xhttp_pi/README
index 9381257..0bf12d4 100644
--- a/modules/xhttp_pi/README
+++ b/modules/xhttp_pi/README
@@ -260,8 +260,8 @@ modparam("xhttp_pi", "xhttp_pi_root", "pi")
6.2. xhttp_pi_buf_size (int)
- It specifies the maximum length of the buffer used to write in the HTML
- reply information in order to build the HTML response.
+ It specifies the maximum length of the buffer (in bytes) used to write
+ in the HTML reply information in order to build the HTML response.
Default value is 0 (auto set to 1/3 of the size of the configured pkg
mem).
diff --git a/modules/xhttp_pi/doc/xhttp_pi_admin.xml b/modules/xhttp_pi/doc/xhttp_pi_admin.xml
index 4b7475e..4c8c841 100644
--- a/modules/xhttp_pi/doc/xhttp_pi_admin.xml
+++ b/modules/xhttp_pi/doc/xhttp_pi_admin.xml
@@ -301,7 +301,7 @@ modparam("xhttp_pi", "xhttp_pi_root", "pi")
<section>
<title><varname>xhttp_pi_buf_size</varname> (int)</title>
<para>
- It specifies the maximum length of the buffer used
+ It specifies the maximum length of the buffer (in bytes) used
to write in the HTML reply information in order to
build the HTML response.
</para>