Hello to all!
I need a little help with our ser installation (ser-2.0.0-rc1).
Due some network restrictions, we need to force every call to pass trought
rtpproxy.
Could someone point me to the right place where to force it?
Please an example based on our config would be really helpful, but in t
On 5/5/11 4:43 PM, Alex Balashov wrote:
On 05/05/2011 10:40 AM, Daniel-Constantin Mierla wrote:
There is an workaround for your version as well, just copy the
content of the branch route in the 'route[xyz] {...}' and then
execute route(xyz); in the branch route. Should work, it is the way I
h
On 05/05/2011 10:40 AM, Daniel-Constantin Mierla wrote:
There is an workaround for your version as well, just copy the
content of the branch route in the 'route[xyz] {...}' and then
execute route(xyz); in the branch route. Should work, it is the way I
have my configs.
That's what I do. But I'
On 5/5/11 12:40 PM, Sebastian Damm wrote:
Hi,
On Wed, May 4, 2011 at 8:33 PM, Daniel-Constantin Mierla
mailto:mico...@gmail.com>> wrote:
Wouldn't the same onreply_route be conserved for every branch?
I can't see how any of our implementations would actually
work if
Hello,
after Robert reported and provided a patch to fix, there should be no
more thread-unsafe conenction. The warning messages were added by me and
kept for short time just to spot such cases and investigate if they are
still problems, but when the warning is printed a new connection is crea
Hi Torge,
I think it's better to send your mail to the mailinglist, then more
people can have a look at your problem.
I'm not really familiar with the kamailio source code. Just started
using Kamailio about 8 months back. I came across a problem with
requesting information from a postgresql
Hi,
On Wed, May 4, 2011 at 8:33 PM, Daniel-Constantin Mierla
wrote:
> Wouldn't the same onreply_route be conserved for every branch? I can't see
>> how any of our implementations would actually work if that weren't the case.
>>
> Yes, the onreply_route will be conserved for the entire transactio
