At the risk of sounding unhelpful, if you are having to modify the
request/status line, there's probably something more deeply wrong here,
and you should probably endeavour to fix the problem in a somewhat more
realistic manner.
Furthermore, it must be said that proxies do not make a particularly
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
Hi Daniel / Muhammad ,
Thanks for your great support
The problem now only got fixed ,the solution is children=1 changes in
kamailio.cfg
I have tested Ubuntu 12 and Centos 5.7 both having the issue and
solution will be the above
I am continuing testing with Asterisk 1.8 Real time
ok I'll try it.
Speaking of workarounds, is there any reason that call_function to core
module functions should not work?
5(11462) DEBUG: [sr_module.c:680]: find_export_record:
not found
5(11462) ERROR: app_python [python_support.c:132]: python_exec2: Unhandled
exception in the Python code:
R
A quick workaround - open file 'app_python/python_msgobj.c' with any text
editor, find function 'msg_rewrite_ruri' and
change a line (inside this function):
from
act.val[0].type = STR_ST;
to:
act.val[0].type = STRING_ST;
then recompile, it should work.
I will commit to git for v4 in a som
Thanks Konstantin, much appreciated. I am using 3.x... I'll jump up to 4
and wait your feedback.
On 15 February 2013 17:39, Konstantin M. wrote:
> Hello,
>
> Ok, bug is confirmed.
> I will fix it a soon.
>
> Can I ask you - are you using now v4 or still using 3.x ?
>
>
>
> 2013/2/15 V Tone
>
>
Hello,
Ok, bug is confirmed.
I will fix it a soon.
Can I ask you - are you using now v4 or still using 3.x ?
2013/2/15 V Tone
> Hi,
>
> I'm having problems getting started with the app_python module. I'm
> getting the following in the logs:
>
> 5(8890) : [action.c:785]: BUG: do_action: bad
Peter, before need to implement HEPv3 into siptrace module. Currently it has
only HEPv1/v2 support.
Can you please contact me in gtalk, we can do it together step by step.
Wbr,
Alexandr
-Original Message-
From: sr-users-boun...@lists.sip-router.org
[mailto:sr-users-boun...@lists.sip-rou
Actually, the sipcapture module does use the Kamailio message parsing.
It looks like only a few small changes will be required to make it
recognise and handle HTTP and MSRP.
I will look into doing this.
Regards,
Peter
On 15/02/13 15:56, Peter Dunkley wrote:
OK. So sipcapture parses the mes
OK. So sipcapture parses the messages itself instead of using the
Kamailio's message parsing (which does handle HTTP and MSRP)?
Regards,
Peter
On 15/02/13 15:47, Dragos Dinu wrote:
Sipcapture can't handle it, because it parses the data as SIP message.
If sipcapture would be able to handle i
Sipcapture can't handle it, because it parses the data as SIP message.
If sipcapture would be able to handle it and get it into the DB,
Webhomer will be able to show it, because it shows all the entries that
you write into the DB.
You can, for example, write the MSRP message into the 'msg' colu
Hi,
I'm having problems getting started with the app_python module. I'm getting
the following in the logs:
5(8890) : [action.c:785]: BUG: do_action: bad set*() type 14
5(8890) ERROR: [action.c:1568]: run action error at: :0
5(8890) ERROR: app_python [python_msgobj.c:115]: Error in do_action
I know that the HEP3 protocol is designed to handle different message
types, so I am curious as to whether the implementation of the capture
node can handle it.
Also, if the capture node can handle it and it does go into the DB will
it cause problems for webhomer, or will webhomer simply ignor
Hi,
As far as I know, although making siptrace encapsulate different types
of messages is not something very difficult, the sipcapture module is
developed to write SIP messages into database.
Webhomer 3 reads SIP-related data from DB, so it displays only SIP.
Regards,
Dragos
On 02/15/2013 0
Also, what about stuff from event_route[xhttp:request]?
On 15/02/13 14:45, Peter Dunkley wrote:
Hello,
Is there any reason why I couldn't use the existing siptrace()
function in event_route[msrp:frame-in] to relay all MSRP messages to a
SIP Capture node?
Will the SIP Capture node handle re
Hello,
Is there any reason why I couldn't use the existing siptrace() function
in event_route[msrp:frame-in] to relay all MSRP messages to a SIP
Capture node?
Will the SIP Capture node handle receiving these messages?
What will end up in the WebHomer display in these cases?
Regards,
Peter
I am seeing this error lately.
/usr/local/sbin/kamailio[28559]: WARNING: tm [t_lookup.c:1543]: WARNING:
script writer didn't release transaction
What does this mean?
Krish Kura
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
Hi,
I'm trying to limit concurrent calls through kamailio using following script:
#!ifdef WITH_CALL_LIMIT
if (is_method("INVITE")) {
dlg_manage();
$var(100) = 0;
get_profile_size("callquota", "$fd", "$var(100)");
if ($var(100)
18 matches
Mail list logo
