Hello,
I thought some people may have spare cycles and are willing to help with
the documentation. Here is some updates I would like to get for modules:
1) adding ids for parameters, functions, and other sections of the
docbook xml files. Now we generate the alphabetic indexes pointing to
the online html readmes, would be better to point directly to the exact
section. Practically, for example, sections such as next from async module:
<section>
<title><varname&…
[View More]gt;workers</varname> (int)</title>
should become:
<section id="async.p.workers">
<title><varname>workers</varname> (int)</title>
To get unique ids over all files, I suggest using following pattern:
[module name] [dot] [type] [dot] [title]
The [type] should be:
- p - parameters
- f - functions
- m - mi commands
- r - rpc commands
- s - statistics
2) Add RPC commands to readmes -- some of modules already do, but many
don't. There is a perl script that should get the list of RPC commands
from source code, but it requires some patch to a perl lib, not working
on all systems. Moreover, the output is quite minimalistic, not easy to
improve the content or add examples. Last generated index is:
- http://www.kamailio.org/docs/docbooks/3.4.x/rpc_list/rpc_list.html
3) Document selects -- although their name are quite suggestive, a bit
of text around won't harm.
- http://www.kamailio.org/wiki/cookbooks/devel/selects
Because 1) and 2) requires git access, the easiest way to contribute is
to provide patches to the xml files. If anyone commits to do an
extensive work on these tasks in short term, we may eventually arrange
for git access. The 3) is in the wiki, everyone can register an account
and then update the pages.
I would recommend these guidelines to be followed from now on by
developers when adding new elements to the module documentation.
Cheers,
Daniel
--
Daniel-Constantin Mierla - http://www.asipto.comhttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio World Conference, April 16-17, 2013, Berlin
- http://conference.kamailio.com -
[View Less]
i built latest master and got error when trying to load websocket
module:
0(10759) ERROR: <core> [sr_module.c:588]: ERROR: load_module: could not open module </usr/lib/sip-proxy/modules/websocket.so>: /usr/lib/sip-proxy/modules/websocket.so: undefined symbol: ws_keepalive_mechanism
is there a bug in websocket module or am i missing something? i read
websocket readme and didn't find anything missing.
i have not defined keepalive_mechanism variable in config.
-- juha
Module: sip-router
Branch: master
Commit: 2168999d8f198268526404946b0def97b87fd8f5
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=2168999…
Author: Hugh Waite <hugh.waite(a)crocodile-rcs.com>
Committer: Hugh Waite <hugh.waite(a)crocodile-rcs.com>
Date: Fri Apr 5 09:33:38 2013 +0100
Merge remote branch 'origin/hpw/branch_failure_route'
* origin/hpw/branch_failure_route:
modules/tm: Fix t_next_contact_flow return value
modules/tmx: Add $…
[View More]T_reply_ruid pv to return ruid for a branch reply
modules/tm: Make ruid available in uac structure
modules/registrar: Allow unregister for ruids in branch_failure_route
modules/usrloc: Fix get_urecord_by_ruid to return static aor
modules/tm: Fix setting instance in uac branches
modules/tm: Enable retrieving of branch instance id from uac structure
modules/xprint: Updated to use the new get_branch()/next_branch() functions
modules/pv: Updated to use the new get_branch()/next_branch() functions
modules/permissions: Updated to use the new get_branch()/next_branch() functions
modules/domain: Updated to use the new get_branch()/next_branch() functions
core: Update get_branch() to return instance from appended branches
modules/tm: Update t_next_contact_flows for use in branch_failure event_route
core: Add defines required for a new branch_failure_route type
modules/tm: Create branch-failure event route
Revert "core: Initial revision of branch_failure_route"
core: Initial revision of branch_failure_route
modules/tm: Initial revision of branch_failure_route
---
[View Less]
Hi All,
The following in Makefile.defs is incorrect IMO:
# setting LDFLAGS
ifeq ($(CC_NAME), gcc)
ifeq ($(LDTYPE), solaris)
# solaris ld
LDFLAGS+=-O2 $(PROFILE)
MOD_LDFLAGS:=-G $(LDFLAGS)
LIB_LDFLAGS:=-G $(LDFLAGS)
LIB_SONAME=-Wl,-h,
LD_RPATH=-Wl,-R,
else
#gcc and maybe others, => gnu ld
LDFLAGS+=-Wl,-O2 -Wl,-E $(PROFILE)
MOD_LDFLAGS:=-shared $(LDFLAGS)
LIB_LDFLAGS:=-shared $(LDFLAGS)
LIB_SONAME=-Wl,-soname,
LD_RPATH=-Wl,-rpath,
endif
endif
Solaris GCC supports the standard -shared flag …
[View More]parameter. TBH, I'm not sure
where the -G came from and why? If nobody has any objections I would like
to remove -G switch for Solaris GCC???
ps. the -G switch works fine when building 32 bit but breaks when building
64 bit with errors like:
fatal: relocation error: R_AMD64_PC32: .... value 0x2800c20d934 does not fit
Cheers
Jason
[View Less]
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#278 - usrloc module stops updating some records in db_mode 2
User who did this - Daniel-Constantin Mierla (miconda)
----------
Have you been able to compare the db queries in 3.1 vs. 3.3? Just wondering, maybe I overlooked something and I should investigate in other direction. I don't have any 3.1 going on anymore.
----------
More information can be found at the following URL:
http://sip-router.org/…
[View More]tracker/index.php?do=details&task_id=278#comment819
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
[View Less]