Hello,
I am trying to put in place auth_identity between 2 SER proxies and it doesn't work well.
The first one manages to add identity and identity_info fields and to send the INVITE to the other proxy.
But when the other proxy receive the message and does his tests there is an issue.
It sends back a 436 Bad Identity Info. The error happens during the "vrfy_get_certificate" function (function which downloads the certificate thanks to identity_info URL).
On my proxy logs, I can see this : AUTH_IDENTITY:retrieve_x509: DER Certificate error:0D0680A8:asn1 encoding routines:ASN1_CHECK_TLEN:wrong tag
I really don't know what to do, do you have any idea?
Thanks,
Regards,
Jérôme HERVE
Hi,
according to our last IRC meeting [1] we want to release a minor release for
the 1.4 branch in the next days. We've did already over 40 changes in this
branch, many of them for important bugs, so i propose the next thursday, the
11th december as the date for 1.4.3. So if you have any important backports
or other fixes that should go into this release, please commit them until
this day.
While already on the release topic, the code freeze period for the 1.5.0
release will be start in the mid of Januar, roughly in about 6 weeks from
now. So if you like to contribute something that should be included in this
release, please commit it to our repository or upload the patch to the
tracker for review. Already finished features and the roadmap can be found as
usual in our wiki at [2, 3].
If you like to give the new features a try, then you find prebuild packages
for several debian releases here [4]. Please report any bugs you find to our
developer list.
Best regards,
Henning
[1]
http://www.kamailio.org/mos/view/News/NewsItem/IRC-Devel-Meeting-Summary---…
[2] http://www.kamailio.org/dokuwiki/doku.php/features:new-in-1.5.x
[3] http://www.kamailio.org/dokuwiki/doku.php/roadmap:1.5.x
[4] devel.kamailio.org
Hi,
in order to reduce the number of modules that needs to be maintained we
integrated several small modules into existing ones. This applies only to the
devel (trunk) version. No functionality was removed, it can be now just found
in a different place.
1. gflags module
The functionality of this module was integrated into the cfgutils module.
The internal functionality, function names and MI commands are the same, the
parameter “initial” was renamed to “initial_gflags”.
2. options module
The functionality of this module was integrated into the siputils module. The
function name was not changed, all parameters were prefixed with
the "options_” string.
3. uri module
The functionality of this module was integrated into the siputils module. The
function names were not changed, internal functionality is the same.
So starting from the release 1.5 you'll need to fix your "loadmodule"
statements and some parameter prefixes in your config if you use one of the
mentioned modules. Documentation for the functions can be found in the usual
place [1, 2].
Cheers,
Henning
[1] http://www.kamailio.org/docs/modules/devel/cfgutils.html
[2] http://www.kamailio.org/docs/modules/devel/siputils.html
Hi all,
My OpenSER system seems to run out of TCP handlers all the time. It
looks to me that I need two child processes for each local IP and peer
combination, because to and back communication do not use the same TCP
channel.
I have a lot of TCP clients which would lead to more than 100 child
processes.
Does it make sense to reduce tcp_connection_lifetime? This would
increase TCP overhead, but would allow me to have fewer child processes,
right?
Any help is welcome. Thanks guys!
Regards
Hello,
I am trying to setup Kamailio to publish xcap-diff payload to a client.
However, the xcap-diff event is not supported (receives a SIP 489 answer),
even though it says Kamailio supports it. What am I missing? How does the
mi_xmlrpc module works?
For reference, I use Openxcap and it is correctly (theorically at least) set
to use Kamailio.
Best regards,
John
Hello,
the TM module introduces two new features:
- access to SIP request attributes while processing a reply belonging to
same transaction
- access to SIP reply attributes while processing a request belonging to
same transaction
Functionalities come as pseudo-variables, $T_req(pv) and $T_rpl(pv) -
where pv can be any pseudo-variable, check documents at:
http://www.kamailio.org/dokuwiki/doku.php/pseudovariables:devel#tm_module_p…
The new pseudo-variables can be used:
- in failure_route to get the attributes of the reply causing the
failure route. You can take decisions what to do with the request based
on reply details
- in onreply_route to get the attributes of the request. you can take
decision what to do with the reply based on request attributes.
- in acc to store data from reply
- in C code (modules)
Note that couple of PV are disabled for these cases (PV will return
null) - these are the PV that alter/depend on the context of the
processed message, like $Ts, $Tf (but you can use $TS and $TF), $time,
destination set attributes. The $avp() will be current avps, as they
are stored in a global list. Also, in case there is a timeout or other
reply generated by kamailio itself, $T_rpl(pv) will return null as there
is no real reply structure behind.
Example, print the source ip of the reply in failure route:
failure_route[1] {
xlog("reply received from: $T_rpl($si)\n");
}
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://www.asipto.com
Hello,
as promised there is a first release candidate for the 1.1 release of
the SIP Express Media Server available:
Source:
http://ftp.iptel.org/pub/sems/1.1/rc1/src/sems-1.1.0-rc1.tar.gz
Debian packages:
http://ftp.iptel.org/pub/sems/1.1/rc1/packages/debian/
This RC1 was created from SVN rev 1193.
With the version 1.1 SEMS gets
- DSM state machine scripting (it's cool!)
- an (experimental) ISDN gateway module
- binrpc: MT (SER->) and connection pool (->SER)
- MT xmlrpc server
- controlled server shutdown
- improved logging
- g722 in 8khz compat mode
- out of dialog request handling for modules & dialogs without sessions
- audio file autorewind, AmAudio mixing
- SIP and media IP separately configurable
- UID/DID support for voicemail/-box/annrecorder
- and quite some bugs and mem leaks fixed, documentation, etc.
You are welcome to test this release candidate, and give feedback on the
SEMS mailing list (sems(a)iptel.org), the semsdev list (semsde(a)iptel.org),
or the bug tracker: http://tracker.iptel.org.
Thanks to all contributions and patches, this time from
Stefan Sayer, Raphael Coeffic, Grzegorz Stanislawski,
Bogdan Pintea, Greger Teigre, Rui Jin Zheng,
Alfred E Heggestad, Juha Heinanen, Peter Lemenkov,
Robert Szokovacs, Jeremy A, Alex Gradinar
Best Regards
Stefan Sayer
--
Stefan Sayer
VoIP Services
stefan.sayer(a)iptego.com
www.iptego.com
IPTEGO GmbH
Am Borsigturm 40
13507 Berlin
Germany
Amtsgericht Charlottenburg, HRB 101010
Geschaeftsfuehrer: Alexander Hoffmann
Henning Westerholt wrote:
> On Monday 08 December 2008, Juan Asencio wrote:
>
>> Hi, I'm trying to install from source Kamailio on Red Hat 4, and I need
>> to include mysql as a database and carrierroute.
>>
>> When I check on the directory of modules, I can't see mysql.so or
>> carrierroute.so, how can I include them?
>>
>> Best regards,
>>
>
> Hi Juan,
>
> have you compiled and installed the db_mysql and the carrierroute module?
> There excluded in the default installation, because they need some extra
> libraries.
>
> Cheers,
>
> Henning
>
Hi again, I have another question :)
I have download the kamailio-1.4.1-notls_linux_i386.tar.gz
Put it on the directory: /usr/src and there I did: tar zxvf kamai...tar.gz
A list of directories and files are created, but I can't find the
Makefile and I can't "make all" or "make" anything.
In my small Linux experience, when I tar xvf... something.tar.gz a
directory of something is created and then I usually can find the
makefile there.
Why I can't find it now? I'm trying to follow the instructions on
http://www.kamailio.org/mos/view/Installation-Notes/ but I can't do it.
Can anyone please give some suggestions?
Thanks in advance,
Juan.-
Hi, I'm trying to install from source Kamailio on Red Hat 4, and I need
to include mysql as a database and carrierroute.
When I check on the directory of modules, I can't see mysql.so or
carrierroute.so, how can I include them?
Best regards,
Juan.-