Hi Daniel,
Just to make sure, did you backport it? Will it be released in 3.2.3?
Thanks
Reda
On Mon, Mar 12, 2012 at 11:42, Daniel-Constantin Mierla
wrote:
> Hello,
>
> I will patch and backport during next days -- I was mostly out of the
> office during past weeks.
>
> Cheers,
> Daniel
>
>
Hello,
I will patch and backport during next days -- I was mostly out of the
office during past weeks.
Cheers,
Daniel
On 3/12/12 11:30 AM, Reda Aouad wrote:
Hi Daniel,
Any plans to backport this to 3.2 ?
I could still do the changes manually before compilation if you don't
have time to do
Daniel, It works with flag 28.
Can you confirm that flag 28 isn't used by another module?
If so, can you patch it? When is the next release scheduled for?
The following are the changes I made:
modules_k/call_control.c: flag changed to 28
---
#define FL_USE_
A quick grep on flags FL_* in the sources shows the following :
Flag 29 is used by acc module, 31 by nat_traversal, 0 to 12 in the parser.
Thus I assume that it is safe to test using flag 28.
I'll keep you posted on the test result.
You'll also find below warnings in msg_parser.h for the used flag
That should be. Try changing one of them to (1<<29) and see if all works
fine.
On another hand, defining and using core msg flags in a module is a
risk, a different solution has to be done, a simple one is to move the
definition of these flags in the core, so there will be no overlap in
the f
Daniel, I sent you the log file by private email, for privacy concerns.
I took a quick look at the log files, and didn't see any call to mediaproxy
module.
Though, the mediaproxy log file indicates a media session engaged, and
CDRTool shows media information for the established session.
The media
I looked in detail in the source of the call control module and didn't find
anything related to the mediaproxy module neither..
I'll send you the output of cfgtrace soon.
Reda
On Fri, Feb 24, 2012 at 23:46, Daniel-Constantin Mierla
wrote:
> A quick grep over the callcontrol sources didn't rev
A quick grep over the callcontrol sources didn't reveal a point where
mediaproxy is engaged.
Can you load debugger module and enable cfgtrace, then run such a
scenario and send out the output from cfgtrace to see all the config
actions executed?
Cheers,
Daniel
On 2/24/12 7:56 PM, Reda Aouad
It would be great Daniel if you could do it.
I will be more than happy to test it.
A function parameter would be more flexible than a module parameter.
I expect it shouldn't affect the behavior of the external application
CallControl.
Thanks in advance :)
Reda
On Fri, Feb 24, 2012 at 08:09, Da
Hello,
I am not using mediaproxy at all (but nathelper/rtpproxy), neither the
call control module, but making an option (module parameter or function
parameter) for call control to bind to another module like media proxy,
should not be big deal if it is all you are looking for -- I can look
o
First, I am posting about the wrong behavior of CallControl (or most
probably Kamailio modules) which leaves no option. I should be the only one
deciding about how to handle timeouts. If I decide to take some risk, no
module should oblige me to do otherwise.
Mediaproxy detects ONLY RTP timeouts fr
Reda-
> It's clear but not necessary. It can look at radius records fixed by
> mediaproxy on RTP timeout to debit the correct balance as well. And why
> also force it on postpaid calls which it doesn't control at all ?
I don't understand how you plan to tear down Kamailio calls that suffer RTP
t
It's clear but not necessary. It can look at radius records fixed by
mediaproxy on RTP timeout to debit the correct balance as well. And why
also force it on postpaid calls which it doesn't control at all ?
What happens is cost and performance issues for additional calls passing
through my mediapr
Reading from the module docs its clear why it needs to engage media/rtp
proxy to start,stop billing or timer of a call. so what happens when it
engages mediaproxy on unwanted calls !? audio-issues?
On Thu, Feb 23, 2012 at 1:21 PM, Reda Aouad wrote:
> Thanks Sammy. I didn't get any reply yet.
>
>
Thanks Sammy. I didn't get any reply yet.
CallControl is an application used with CDRTool for prepaid calls. It
calculates the maximum call duration based on the user's balance. Once the
call's duration limit is reached, it sends BYE to both calling parties,
terminating the call. At the end of a p
Hi,
I can see you posting multiple times on both proxies listings so I'm sure
you havent heard back from anyone.I am not at all familiar with your
functions in email but could it be possible for you to determine on which
calls you need to engage mediaproxy and on which not to, then on the base
of t
Hi,
When I use the function call_control( ) of the call_control module, it
automatically engages mediaproxy if it finds the mediaproxy module loaded.
If the mediaproxy module is not loaded, call_control doesn't even try to
engage it.
I need mediaproxy for NAT traversal in some cases, but don't wa
Hi,
I noticed that calling call_control( ) function forces engage_media_proxy(
).
Is there a way to disable this behavior ?
Thanks
Reda
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://list
18 matches
Mail list logo
