Hello,
following past discussions about different formats resulted when
generating readme files for modules on various systems, which typically
led to conflicts when backporting, I put in place a cron job running on
kamailio.org to fetch from github the docbook files, generate the readme
and push them back.
The cron job is running every 15min.
>From now on it is no longer needed to generate the readme yourself. Just
commit the changes to xml files and push them to git repository. The
readme will be refreshed automatically in a bit.
The commits in this case are done by a generic git account named
kamailio-dev.
The commit message looks like:
modules: readme files regenerated - app_mono ...
Only the first module that has the readme updated is listed (in this
example being app_mono).
The readmes are automatically generated for master and 4.4 branches.
If you do consistent changes to the docbook file, you can generate the
readme locally to be sure there is no error, then restore the old
version before committing - relevant commands:
make modules-readme modules=modules/async
rm modules/async/README
git checkout modules/async/README
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://www.asipto.com - http://www.kamailio.orghttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
I'll come back to mem/tlsf_malloc.c issue. Camille asked if the
compiler warnings on mem/tlsf_malloc.c were occurring on x86 32 bit
machine. I now tried and, yes, they do not appear on i386 jessie, but
not on amd64 jessie. So looks like this is the same issue that Ovidiu
has reported.
-- Juha
Was this fixed on master?
Jun 8 08:12:46 sars /usr/bin/sip-proxy[19017]: : tls [tls_init.c:557]: init_tls_h(): ERROR: tls: init_tls_h: installed openssl library version is too different from the library the Kamailio tls module was compiled with: installed "OpenSSL 1.0.1t 3 May 2016" (0x1000114f), compiled "OpenSSL 1.0.1k 8 Jan 2015" (0x100010bf).#012 Please make sure a compatible version is used (tls_force_run in kamailio.cfg will override this check)
Jun 8 08:12:46 sars /usr/bin/sip-proxy[19017]: CRITICAL: <core> [main.c:2514]: main(): could not initialize tls, exiting...
If so, please backport to 4.4 since it is now impossible to start
kamailio on debian jessie.
-- Juha
Dear kamailio community,
I have a problem that seems really weird. i have the same problem using kamailio 4.3 and 4.4.1.
The scenario is the following: I make a call from a sip phone to kamailio. kamailio routes the Invite to an asterisk server. After a while asterisk sends a Bye request to kamailio. Now instead of routing the Bye to the sip phone, I want to create a re-invite request from kamailio and send it to the sip phone. The purpose of the re-invite is to connect the sip phone to another sip phone that already has an active call. This part is working fine but the problem occurs after the sip phone sends the ‘200 OK’ message for the re-invite. Kamailio sends an ACK for the 200 message but this ACK has a ‘CSCall-id’ header instead of the ‘Call-id’ header.
To create the re-invite I am using the UAC module with one change to the source code. In the uac.c file found in the tm module folder, I added 2 lines of code to the request function in order to stop the UAC module from creating a from tag(attached). I also attached a trace that shows the ack message with cscall-id.
Thank you,
Rawad
Hi Team,
The SIP packets are fine ,we are able to establish SIP session ,
As long the RTP Proxy not get involved and we are not able to hear
audio,So How to do the proper configuration RTP Proxy,what to do in
RTP Proxy to get the voice for the connected sip session
Regards
Admin
Arnab
Hi team,
I like to know the source code documention of kamailio,
I like to customize textops.c,like to get the variables and structure
documents
gparam_p, etc..
Regards
Jeff
Has anyone been successful in getting Yealink BLF's to work with
Kamailio presence
It appears that the xml format being sent is not compatible with
Yealink, butr I can't find how to change the format of the body.
Bill