Ben WIlliams writes:
> here is the dump, prefix 8 should use gateway number 2. Its not a big
> issue, I've managed to do it without LCR now.
>
> INSERT INTO `lcr_gw` VALUES
> (1,1,'chc','1.1.1.1',NULL,NULL,NULL,1,1,NULL,NULL,NULL,1,NULL),(2,1,'ak','2.2.2.2',NULL,NULL,NULL,1,1,NULL,NULL,NULL,1,NUL
Hi Juha,
here is the dump, prefix 8 should use gateway number 2. Its not a big
issue, I've managed to do it without LCR now.
INSERT INTO `lcr_gw` VALUES
(1,1,'chc','1.1.1.1',NULL,NULL,NULL,1,1,NULL,NULL,NULL,1,NULL),(2,1,'ak','2.2.2.2',NULL,NULL,NULL,1,1,NULL,NULL,NULL,1,NULL);
INSERT INTO `lcr_ru
On 02/29/2012 09:34 PM, Klaus Darilion wrote:
> Maybe you can catch the ACK before loose_route check with
> if (ACK && has_totag() && uri=myself) {
> # use load-balancer logic ...
> }
This, and an rr-param to manually distinguish between hop-by-hop and
end-to-end messages in case the Route heade
Am 29.02.2012 19:12, schrieb Andreas Granig:
On 02/29/2012 06:35 PM, Andreas Granig wrote:
If tm is used, it will take care of this by consuming the ACK and
generating a new one. It seems that we need some fixes for stateless
routing.
I already switched back to transaction stateful routing fo
On 02/29/2012 06:35 PM, Andreas Granig wrote:
>> If tm is used, it will take care of this by consuming the ACK and
>> generating a new one. It seems that we need some fixes for stateless
>> routing.
>
> I already switched back to transaction stateful routing for now until I
> get a better idea abo
On 02/29/2012 06:23 PM, Klaus Darilion wrote:
> That's really weird. It should not rewrite $ru. Maybe there is some
> special handling for ACK.
Yeah, I'm going to check the source.
> Anyway, if the Route header is consumed and pushed into $du it means
> that the "special behavior" which was done
On 29.02.2012 18:01, Andreas Granig wrote:
Hi Klaus,
On 02/29/2012 03:53 PM, Klaus Darilion wrote:
However if a 407 is relayed back from the registrar via the lb to the
UA, it sends an ACK, again with pre-loaded Route header like in the
initial INVITE, this time with to-tag. In that case, loo
On 02/29/2012 06:01 PM, Andreas Granig wrote:
> Proxy is running on 192.168.51.133:5060, and client (linphone-3) sends a
> header "Route: " in the ACK after 407
> ++ before loose-route, $du='' - M=ACK R=sip:testuser3@192.168.51.133
> ++ after successful loose-route, $du='sip:192.168.51.133;lr' -
On Wednesday 29 February 2012, Robert R wrote:
> The openser service died on my servers after "memory allocation failure".
> This issue has been occurred a couple of times on two different servers
> within the last two months.
>
> Feb 29 08:31:59 /usr/sbin/openser[7115]: ERROR:core:do_action: mem
Hi Klaus,
On 02/29/2012 03:53 PM, Klaus Darilion wrote:
>> However if a 407 is relayed back from the registrar via the lb to the
>> UA, it sends an ACK, again with pre-loaded Route header like in the
>> initial INVITE, this time with to-tag. In that case, loose_route()
>> returns true, but the $du
Hi Manuel!
With a trace (of SUBSCRIBE and NOTIFY) it is really difficult to
understand the problem.
Thus I suggest: Take a look at the SUBSCRIBE request on both Kamailio
proxies. Verify that record-route and contact headers are correct.
Then take a look at the NOTIFY also on both servers an
Hi,
The openser service died on my servers after "memory allocation failure".
This issue has been occurred a couple of times on two different servers
within the last two months.
Feb 29 08:31:59 /usr/sbin/openser[7115]: ERROR:core:do_action: memory
allocation failure
Feb 29 08:31:59 /usr/sbin/op
Thanks for your reply.
This is part of my config file:
request_route {
# per request initial checks
route(REQINIT);
# NAT detection
route(NATDETECT);
# handle requests within SIP dialogs
route(WITHINDLG);
### only initial requests (no To tag)
# CANCEL processing
if (is_method("CANCEL"))
{
if
Since Timo is most likely busy these days I will create an issue in the
tracker for that.
On 02/22/2012 08:48 PM, Andrew Pogrebennyk wrote:
> Hi,
> I noticed dialog module showing calls that have already been terminated
> with state=4.
> The kamailio version is 3.1.5, I'm aware of certain limitati
On 29.02.2012 14:34, Andreas Granig wrote:
Hi,
I ran into an interesting scenario when experimenting with kamailio 3.1
as a stateless proxy (no tm module used):
There is an initial INVITE without to-tag and with pre-loaded Route
header pointing to the external address of the lb. When I call
l
OK now I've upgraded to Kamailio 3.2 and it all works: sql_query (to
insert BYE into acc table) in event_route() doesn't crash anymore.
On 29/02/12 09:31, Yufei Tao wrote:
> Hi
>
> To summarize my questions:
>
> 1. What is the correct way to account for Kamailio internally-generated
> BYEs?
> 2.
Hi,
I ran into an interesting scenario when experimenting with kamailio 3.1
as a stateless proxy (no tm module used):
There is an initial INVITE without to-tag and with pre-loaded Route
header pointing to the external address of the lb. When I call
loose_route for that, it returns false and the R
Hi,
insert_hf doesn't work for CANCEL messages. It doesn't work either on 487
replies in failure_route..
Why? Is it because they are re-generated on every hop?
Is there a workaround?
Reda
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users m
Hi
To summarize my questions:
1. What is the correct way to account for Kamailio internally-generated
BYEs?
2. Using sql_query inside event_route() crashes Kamailio - is this a bug
or unexpected usage?
Thanks very much!
Yufei
On 28/02/12 17:06, Yufei Tao wrote:
> Hi
>
> Thanks for your reply!
>
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
21 matches
Mail list logo
