script variable can have only integer or string values. Even
the length can be higher, these functions truncate at first 0. But
internally all should be kept, just not passed to config variables.
Have you tried exec_msg(), that should pass entire msg?
Otherwise, I presume there is need for some C c
Hello,
I´m searching for a way to keep track about success or failure of locally
generated SUBSCRIBE transactions, which are typically triggered by the RLS
module. In case that a subscription is rejected by the subscribee with any
negative response code or the transaction is timing out, I have to
ember 2014 um 18:38
> geschrieben:
>
>
>
> On 10 Nov 2014, at 16:46, Klaus Feichtinger wrote:
>
> > Hello,
> >
> > does kamailio offer any possibility for adding / replacing SIP headers in
> > locally built SIP requests? In detail: SIP OPTIONS requests that
Hi Alex,
no - these messages are not intercepted there. I´ve already tried diverse routes
before.
Klaus
> Alex Balashov hat am 10. November 2014 um 16:47
> geschrieben:
>
>
> On 11/10/2014 10:46 AM, Klaus Feichtinger wrote:
>
> > Therefore, I´ll ask again: does ka
Hello,
does kamailio offer any possibility for adding / replacing SIP headers in
locally built SIP requests? In detail: SIP OPTIONS requests that are built by
the DISPATCHER module for probing the configured targets. I have to extend these
messages with "Accept" SIP header fields (which are marked
or protocol) than the
address from where the request was sent, Via header specifying where
it should be sent.
Cheers,
Daniel
On 11/06/14 21:32, Klaus Feichtinger wrote:
Hello,
I wonder if it is allowed using transport protocol UDP for SIP NOTIFY
requests (which are generated by Kamailio
Hello,
I wonder if it is allowed using transport protocol UDP for SIP NOTIFY
requests (which are generated by Kamailio/presence module), when the
SUBSCRIBE dialog was established using TCP as transport protocol.
In other words: this is a principal question if it is allowed changing
the transpo
tch to be reviewed?
>
> Cheers,
> Daniel
>
> On 07/05/14 13:15, Klaus Feichtinger wrote:
>
> > > Hi Daniel,
> >
> > I think we´ve found the reason, why this problem occurs!
> >
> > The problem is caused in the "agregate_xmls
Hi Daniel,
I think we´ve found the reason, why this problem occurs!
The problem is caused in the "agregate_xmls" function in file "notify_body.c" of
the "presence_dialoginfo" module:
/* loop over all bodies and create the aggregated body */
for(i=0; ichildren) {
for (node = p
sip:117103@172.31.60.87
a.1399360111.20480.4.0
regards,
Klaus
> Daniel-Constantin Mierla hat am 5. Mai 2014 um 17:37
> geschrieben:
>
> Can you try with the latest version 4.1.x? It is where I looked in the code
> and seemed to walk through all
2014 um 13:27
> geschrieben:
>
> Hello,
>
> I haven't meet that case yet, but xml aggregation in presence_dialoginfo
> seems to walk through all children of root note for each xml doc. Maybe you
> can post here the output with debug=3.
>
> Cheers,
> Daniel
Hi,
during simulating scenarios in relation with the notify problem I have so far, I
became unsure, if Kamilio (in principal) is supporting handling of PUBLISH
requests (event "dialog") that contain _more than_ one (1) dialog entry. I know
that it can generate notify requests with a message body t
quick look in the code seems to use all xml nodes. Mybe you can add some
> debug messages in presence_dialoginfo/notify_body.c in agregate_xmls()
> functions and see what is not executing.
>
> Daniel
>
> On 29/04/14 20:39, Klaus Feichtinger wrote:
>
> > &g
Hi,
I have a question regarding the presence + presence_dialoginfo modules
of Kamailio (tested with version 3.2.x and 3.3.x).
My SIP user agents are generating SIP PUBLISH requests for the event
"dialog" and some of these PUBLISH requests contain multiple dialog
elements in the message body.
regards
klaus
On 06.11.2013 21:16, Klaus Feichtinger wrote:
Hello list,
I have troubles with serial forking in kamailio 3.2.4, which is mixed
with parallel forking. In the scenario that an initial INVITE message,
which is addressed to sip:A, is coming in to the server, it is doing a
lookup in
Hello Daniel,
I´ve patched the code and found that the return value of the 'sleep' command is
- as expected - differing in the scenarios. For scenario 1 (no provisional
response), the return value is '0' and for scenario 2, the return value is '2'
(see log output):
scenario 1:
Nov 7 12:40:51 sip
Hello list,
I have troubles with serial forking in kamailio 3.2.4, which is mixed
with parallel forking. In the scenario that an initial INVITE message,
which is addressed to sip:A, is coming in to the server, it is doing a
lookup in the DB and forking (parallel) the request to e.g. 3 SIP user
Hello list,
I have troubles using the function "usleep(x)" or "sleep(x)" (the
behaviour is the same) of the "cfgutils" module
(http://kamailio.org/docs/modules/3.2.x/modules_k/cfgutils.html#idp76968) in
the failure_route. According documentation, this function could be used
in any route, incl
- is this a bug in Kamailio parsing functions?
> - is this a design issue of Kamailio text parsers (as binary data are
> allowed acc. RFC3261) - does anybody know a solution for this problem?
> This "bug" is causing big troubles
>
> Thanks in advance,
> Klaus Feichtin
e message body does not contain 0x00, it is working fine!
My question is:
- is this a bug in Kamailio parsing functions?
- is this a design issue of Kamailio text parsers (as binary data are
allowed acc. RFC3261) - does anybody know a solution for this problem?
This "bug" is causin
9f408a73011e280056c205642ae68
--uniqueBoundary
Original-Nachricht
Betreff:
Re: [SR-Users] 'subst' request for message body (SDP)
Datum:
Fri, 05 Jul 2013 17:01:56 +0200
Von:
Klaus Darilion
<mailto:klaus.mailingli...@pernau.at>
An:
Kamailio (SER) - Users Maili
Hello,
can anybody give me a hint, how I could delete the _empty_ (blank) last
line of the message body / SDP (it consists of #012#015 only)? This blank
line is the rest of the original MIME message, which was reduced to a
standard message with content SDP only by kamailio-3.3.4, which is
principa
to port it back to 3.3.x (which is
currently in use), too.
Thanks a lot and best regards,
Klaus Feichtinger
Hello,
there is a patch attempting to set the tos for IPv6:
-
http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=084be456bc0fab015cf9964ac85651fa60ea77c9
For now is
ise SIP in IPv6 with kamailio?
Thanks in advance,
Klaus Feichtinger
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
...I think in worst case a controlled local loop (which was helpful in
other situations, too), could be a solution for fixing the UAC problem.
1. UAC (module) sending the created request to the SIP server again (loop)
2. the server is doing textops and
3. is finally forwarding the request to the
I know that it is an untypical way and that a B2BUA would be the best
solution - that is absolutely clear. But because of a missing framework
and time I decided to try it with Kamailio that I've used in many other
projects, too.
Textops is still used and working fine for any headers (except re
Hi,
I have a very specific situation that the implementation of a customer
SIP user agent is absolutely not standards conform. Therefore, I use
Kamailio as a SIP protocol adapter between the non-standard conform user
agent(s) and the typical RFC3261 compliant user agents. Most conversions
are
be
> appreciated. If all goes fine, then I will backport.
>
> Cheers,
> Daniel
>
>
>
> On 1/31/12 4:25 PM, Klaus Feichtinger wrote:
>> Hello list,
>> I`ve found a negative phenomenon during startup of kamailio 3.1.x
>> (orgininally found in version 3.1.5) that
Hello list,
I`ve found a negative phenomenon during startup of kamailio 3.1.x
(orgininally found in version 3.1.5) that results in a core dump,
triggered by the snmpstats module.
During startup of the SIP proxy server machine the linux service
"heartbeat" is responsible for starting required resso
> Hi Klaus,
>
> i understand.
>
>> In case that the dispatcher-target is responding with a negative
>> response code (as it was until now), all targets are sequentially
>> addressed within a time of lower than 1 second until the error message
>> of the TM module is interrupting that process.
>
> 1s
> On Sunday 03 July 2011, Klaus Feichtinger wrote:
>> I have a problem in my scenario where I use the dispatcher module for
>> (round-robin based) distribution of incoming calls to 15 (!) different
>> gateways. In idle case (= all gateways are up and running or just a
>&
Hi,
I have a problem in my scenario where I use the dispatcher module for
(round-robin based) distribution of incoming calls to 15 (!) different
gateways. In idle case (= all gateways are up and running or just a
couple of them does not accept calls) my solution is working fine. The
solution is ve
If yes, then one question for Klaus D. in this case ... the body is
> build in pua_dialoginfo with the placeholder and presence_dialoginfo
> expects that? I had not dug in the code yet, just double-checking here.
>
> Thanks,
> Daniel
>
> On 3/31/11 11:03 AM, Klaus Feichtinger wrote:
string-length of the
placeholder is used all time and in the situations above filled with space
characters.
Regards,
Klaus
> Hello,
>
> On 3/30/11 3:01 PM, Klaus Feichtinger wrote:
>> Hello list,
>>
>> I have a special situation in which string characters of the
>> &
Hello list,
I have a special situation in which string characters of the "root-line"
of the notify-body are overwritten by Kamailio. In detail: the root-line
of the NOTIFY message sent to the subscriber looks like:
instead of
In other words: the string
state="full" is overwritten by space charac
Hi,
Juha - you said last year, that the kamctl-LCR-commands should be DISABLED
for SR 3.1.x, because the kamctl script was not yet adapted to your new DB
structure for LCR tables.
http://lists.sip-router.org/pipermail/sr-dev/2010-October/009356.html
http://lists.sip-router.org/pipermail/sr-dev/20
l add this functionality to git-Trunk in the next few days;
> however, since it is a new feature, i will not backport it (but i can
> provide patches for 3.1).
>
> Kind regards,
> Carsten
>
>
>
> 2011/2/24 Klaus Feichtinger :
>> Hello list,
>>
>&g
Hello list,
I have a question to the dispatcher module in Kamailio version 3.0.4.
In my integration I use this module for distributing calls to a set of
gateways (with the round robin algorithm). Sometimes a gateway does not
react or send back a negative response. In that case I use the function
Hello,
does anybody have an idea, what this error messages could mean?
Feb 16 11:23:27 SipSrvLstI1 kernel: [429767.707165] kamailio[10758]:
segfault at 4 ip b78ba6e5 sp bfacece0 error 4 in dialog.so[b78a+32000]
Feb 16 13:40:42 SipSrvLstI1 kernel: [438003.071797] kamailio[24880]:
segfault at 4
Hi,
I have built a similar solution with only one difference: I am using
HEARTBEAT instead of ucarp. In heartbeat it is possible moving
"haresources" from one active host to another. So, I activate MONIT (and
mysql + kamailio) only when the resources (e.g. virtual IP address) are
switched from one
t it is a useful way :-)
regards,
Klaus
>
>
> Am 16.12.2010 12:41, schrieb Klaus Feichtinger:
>> Hello,
>>
>> I want to ask if you know any possibility in changing the text of the
>> SIP reason header in CANCEL requests. Is the limitation still the same
>> as descr
Hello,
I want to ask if you know any possibility in changing the text of the SIP
reason header in CANCEL requests. Is the limitation still the same as
described in the mail below from May 2010?
For my scenario I have to use the TM module, because incoming requests
from the PSTN gateway are parall
Hello list,
has anybody else tried using SIREMIS 2.0 for administrating LCR tables in
kamailio 3.1.0?
I am not happy with the form / input boxes that are presented in the web
browser, because some fields are not as expected.
Following points are - from my point of view - incorrect:
1) tabl
spatcher", "dst_avp", "$avp(AVP_DST)")
>> modparam("dispatcher", "grp_avp", "$avp(AVP_GRP)")
>> modparam("dispatcher", "cnt_avp", "$avp(AVP_CNT)")
>> modparam("dispatcher", "ds_ping_from
44 matches
Mail list logo
