One of the UAC changed its listen port from 5060 to 5070 and sent a new
subscription however before the subscription made it to UAS, UAS sent a NOTIFY
to UAC to port 5060 and then immediately another NOTIFY to UAC to port 5070
Old setup:
UAC (5060) <---> opensips(proxy) (5060) <---> UAS (5059)
N
Hi Bogdan, thanks for clarifying the behavior. In our implementation, we need
those user defined headers to make it through the proxy, is there any way to
populate the stateful CANCEL with the incoming user-defined headers ?
Thanks
Rahul
From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
Se
Hi Răzvan, It was happening at least once a day. It started to happen when
we reach ~80 registered terminals, not a big load. Now I'm using the
event_rabbitmq module with 400 terminals and it's working fine.
The event is a custom one, I called "E_REGISTERED", it's just to notify an
external proces
Hi Jonathan,
I guess the ul_flush will serve your purpose - if the contact is not
DIRTY, it means it was already flushed into DB, so no sense to flush it
again.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 23.04.2015 20:30, Jonathan Hunter
DB mode 2 should be fine, 3K dialogs should not be such a burn. It
depends on the DB performance IMHO.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 08.05.2015 14:04, Max Mühlbronner wrote:
~3000 Dialogs. The DB is supposed to be fast, at le
Hi all,
During the OpenSIPS Summit in Amsterdam, on the evening of 12th of May,
starting with 19:00, we have an open social event at Gollem pub -
http://cafegollem.nl/overtoom/ - if you could indicate if you are
interested in participating, it will be great for making a realistic
reservation
~3000 Dialogs. The DB is supposed to be fast, at least slow query
logging did not reveal anything when testing earlier.
Currently the plan is to try a different/locally installed DB Server to
also rule out the possibility of network problems/lags.
BR
Max M.
On 08.05.2015 12:16, Bogdan-An
Hi, Federico!
Is this easily replicating, or it happens once in a while? Also, what
events are you raising?
Best regards,
Răzvan Crainea
OpenSIPS Solutions
www.opensips-solutions.com
On 04/24/2015 05:44 PM, Federico Edorna wrote:
Just in case somebody deal with the same issue, the problem se
Yes indeed, it looks like flushing dialog info into DB. How many dialog
do you have ongoing and how fast your db is ??
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 08.05.2015 13:05, Max Mühlbronner wrote:
Here is a pastebin of the bt (atten
Here is a pastebin of the bt (attendant process, while restarting).
Seems to be the database operations/dialogs?
http://pastebin.com/9zHQjMMq
BR
Max M.
On 08.05.2015 11:01, Bogdan-Andrei Iancu wrote:
Max,
What you can do is to try to attach with GDB to the attendant process
while doing
Hi all,
Just for the sake of completion, this problem was fixed in all OpenSIPS
versions, after Jock's report:
https://github.com/OpenSIPS/opensips/issues/479
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 24.04.2015 00:38, Jock McKechnie
Hi Ibrahim,
The call-id is changed at call level, so it will be the same for all
resulting branches. Even after TH, the branches still belong to the same
call.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 27.04.2015 12:48, ibrahim tunali w
Hi Domenico,
I just tested 1.11.4 and the flags seems to work properly. I set the
tcp_connection_lifetime to 10 secs and a REGISTER with 300 secs. I run
both cases (with and without the flag) and monitor the status of the tcp
conns by "opensipsctl fifo list_tcp_conns" .
Could you do the same
Max,
What you can do is to try to attach with GDB to the attendant process
while doing the cleanup. It will be interesting to see what is going on.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 08.05.2015 09:58, Max Mühlbronner wrote:
Hi,
Hello,
Following the release of 2.1.0 stable yesterday, here is the update:
- 1.8, 1.10 are not longer maintained (1.8.8 and 1.10.5 are the
last minor releases on those branches)
- 1.11 LTS is still maintain, the last minor release being 1.11.5
- 2.1.0 is the latest stable release (
15 matches
Mail list logo