THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#140 - bug in $snd and $sndto pseudo variable
User who did this - Klaus Darilion (klaus3000)
----------
$snd(ip) and $sndto(ip) is correct now.
I wonder if to_ip is affected as well.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=140#comment238
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.
Hi guys,
I'm currently working on SIP-to-Jingle Gateway for Kamailio SIP server which
is part of my master thesis at Wroclaw University of Technology. I already
had occasion to take a closer look at source code, not only in XMPP module.
I even create my own idea for Jingle-SIP Gateway. After close code revision
of XMPP Gateway I can say that those two gateways have similar attributes
and protocol translation algorithm.
I decide to start a Jingle extension as a part of XMPP module. I would
appreciate a lot any documentation which has some higher level of details
then this one available in REDME file in mentioned module.
Best regards,
Jedrzej
Hello list,
when using xmlrpc I get a memory error in kamailio's log:
22(26427) ERROR: xmlrpc [xmlrpc.c:581]: No memory left: 9134
If the error occurs or not depends on the RPC command, which is to be
executed and it occurs especially then, if long output text is expected.
After taking a look at xmlrpc.c I suppose the executing TCP process runs
out of memory while trying to generate the xmlrpc reply.
pkg_malloc seems to allocate some sort of private memory (=> increasing
shm size with -m will not help), so I think private memory size has to
be increased:
e.g.
http://www.kamailio.org/dokuwiki/doku.php/troubleshooting:private-memory-si…
Is it possible to increase private memory size without recompiling or do
you think there is another reason for the memory error?
Thanks
Jasmin
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#139 - #!define does not work in $hdr()
User who did this - Daniel-Constantin Mierla (miconda)
----------
Parsing pseudo-variables use different states in the lex parser -- not mapping to IDs or STRINGs, so the preprocessor directives can't substitute there. I will look to see if something can be changed here.
Meanwhile, there is an option for this case, you can use:
pv_printf("$var(hdr)", "$hdr(HEADER)");
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=139#comment237
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.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
Daniel-Constantin Mierla has taken ownership of the following task:
FS#140 - bug in $snd and $sndto pseudo variable
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=140
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.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#140 - bug in $snd and $sndto pseudo variable
User who did this - Daniel-Constantin Mierla (miconda)
----------
Last two patches should fix the issue. If you can test and report whether it works or not, would be great, then it can be backported.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=140#comment236
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.