case,
CANCEL in yours). It seems like it would be possible for OpenSIPS to use a
call-id or tag to determine where to relay the message though.
Russell Bierschbach
em: rbierschb...@telepointglobal.commailto:rjphill...@telepointglobal.com,
im: rbierschb...@hotmail.commailto:rbierschb
That SIP message is actually OpenSIPS receiving the BYE from the customer, the
problem is OpenSIPS is not forwarding/relaying that BYE message to the Asterisk
server that is handling the call, so Asterisk doesn't know the call ended, and
it's still letting the phone ring (and possibly be
I'm having difficulty handling a BYE message when you would normally expect a
CANCEL message. According to the RFC a BYE is valid at this point...
-INVITE
-TRYING
-183 Progress
-BYE
My config is here: http://pastebin.com/8Lz696wB
Lines 77 to 107 are the lines in question, specifically the
command, it will also help.
Regards,
Bogdan
Russell Bierschbach wrote:
1.6
version: opensips 1.6.0dev0-notls (x86_64/linux)
-Original Message-
From: users-boun...@lists.opensips.org
[mailto:users-boun...@lists.opensips.org] On Behalf Of Bogdan-Andrei Iancu
Sent: Friday, September
list
Subject: Re: [OpenSIPS-Users] Load Balance Module URI Limit
Hi Russell,
So, if there are more than 34 records in DB, the LB will fails? by
failing what you mean ? it does not start or load_balance() returns
false all the time?
Regards,
Bogdan
Russell Bierschbach wrote:
The load_balance
-Users] Load Balance Module URI Limit
OK - I will try to reproduce it. BTW, trunk or 1.5 ?
Regards,
Bogdan
Russell Bierschbach wrote:
The load_balance() call returns false when there are 34 or more records in
the table.
-Original Message-
From: users-boun...@lists.opensips.org
The load_balance() call always fails if there 34 or more entries in the
load_balancer table. I have confirmed that it's not a problem with the
entries themselves (I've tried other entries that all work when there are 33
or less records). I have also changed the shared memory from the default of
