Re: [OpenSIPS-Users] opensips 2.2.5 stop responding/processing requests. - Centos 6.5

[Mundkowsky, Robert]

This might help with debugging it.

https://blog.opensips.org/2017/09/20/troubleshooting-opensips-script/
[https://blogopensips.files.wordpress.com/2017/09/troubleshooting.jpg]

Troubleshooting OpenSIPS script – Drops of wisdom 
...
blog.opensips.org
What makes OpenSIPS such an attractive and powerful SIP solutions is its high 
level of programmability, thanks to its C-like configuration script.





From: Users  on behalf of Jonathan Hunter 

Sent: Monday, October 30, 2017 2:25 PM
To: OpenSIPS users mailling list
Subject: Re: [OpenSIPS-Users] opensips 2.2.5 stop responding/processing 
requests. - Centos 6.5


Hi Johan,


Thanks for the response I appreciate it.


We do use radius for accounting and fire all the information to a central 
server, but it appears all that was fine and connectivity/configuration was 
good at the time of the issue.


Anywhere in particular it could break things? I have seen it when opensips cant 
reach radius it starts to be none responsive, is that a scenario you have seen?


Many thanks


Jon



From: Users  on behalf of Johan De Clercq 

Sent: 30 October 2017 17:53
To: OpenSIPS users mailling list
Subject: Re: [OpenSIPS-Users] opensips 2.2.5 stop responding/processing 
requests. - Centos 6.5

If you use acc with radius, check radius config.

Br

On 30 Oct 2017 18:33, "Jonathan Hunter" 
> wrote:

Hi Guys,

Has anyone had the following behaviour with this release of opensips?

It has been running fine for a number of months, and then suddenly today the 
server which was running as the primary suddenly stopped responding to SIP 
requests, or stopped processing them, or there was a long pause in a sequence 
completing.

So in some cases, INVITES or REGISTER messages were ignored and the initial 
requests werent always logged in the opensips log file (even though we do this 
for all messages), however the SIP requests were hitting the server as I was 
tracing them.

In the logs I can see the following warnings we havent seen before;

Oct 30 13:31:25 sgw6 VU-SIP-Proxy[11159]: WARNING:core:utimer_ticker: utimer 
task  already scheduled for 9639891650 ms (now 9639891850 ms), it 
may overlap.
Oct 30 13:52:48 sgw6 VU-SIP-Proxy[11159]: WARNING:core:timer_ticker: timer task 
 already scheduled for 9640994180 ms (now 9641175280 ms), it may 
overlap..
Oct 30 13:52:48 sgw6 VU-SIP-Proxy[11159]: WARNING:core:timer_ticker: timer task 
 already scheduled for 9640980270 ms (now 9641175280 ms), it may 
overlap..

A restart of the opensips application didnt help, and service was only restored 
fully when I failed over to the secondary server.

Has anyone had these issues before? There are no obvious server level issues, 
and as I mentioned the logs dont contain anything too unusual.

Any help appreciated.

Many thanks

Jon


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users




This e-mail and any files transmitted with it may contain privileged or 
confidential information. It is solely for use by the individual for whom it is 
intended, even if addressed incorrectly. If you received this e-mail in error, 
please notify the sender; do not disclose, copy, distribute, or take any action 
in reliance on the contents of this information; and delete it from your 
system. Any other use of this e-mail is prohibited.


Thank you for your compliance.


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] opensips 2.2.5 stop responding/processing requests. - Centos 6.5

[Jonathan Hunter]

Hi Johan,


Thanks for the response I appreciate it.


We do use radius for accounting and fire all the information to a central 
server, but it appears all that was fine and connectivity/configuration was 
good at the time of the issue.


Anywhere in particular it could break things? I have seen it when opensips cant 
reach radius it starts to be none responsive, is that a scenario you have seen?


Many thanks


Jon



From: Users  on behalf of Johan De Clercq 

Sent: 30 October 2017 17:53
To: OpenSIPS users mailling list
Subject: Re: [OpenSIPS-Users] opensips 2.2.5 stop responding/processing 
requests. - Centos 6.5

If you use acc with radius, check radius config.

Br

On 30 Oct 2017 18:33, "Jonathan Hunter" 
> wrote:

Hi Guys,

Has anyone had the following behaviour with this release of opensips?

It has been running fine for a number of months, and then suddenly today the 
server which was running as the primary suddenly stopped responding to SIP 
requests, or stopped processing them, or there was a long pause in a sequence 
completing.

So in some cases, INVITES or REGISTER messages were ignored and the initial 
requests werent always logged in the opensips log file (even though we do this 
for all messages), however the SIP requests were hitting the server as I was 
tracing them.

In the logs I can see the following warnings we havent seen before;

Oct 30 13:31:25 sgw6 VU-SIP-Proxy[11159]: WARNING:core:utimer_ticker: utimer 
task  already scheduled for 9639891650 ms (now 9639891850 ms), it 
may overlap.
Oct 30 13:52:48 sgw6 VU-SIP-Proxy[11159]: WARNING:core:timer_ticker: timer task 
 already scheduled for 9640994180 ms (now 9641175280 ms), it may 
overlap..
Oct 30 13:52:48 sgw6 VU-SIP-Proxy[11159]: WARNING:core:timer_ticker: timer task 
 already scheduled for 9640980270 ms (now 9641175280 ms), it may 
overlap..

A restart of the opensips application didnt help, and service was only restored 
fully when I failed over to the secondary server.

Has anyone had these issues before? There are no obvious server level issues, 
and as I mentioned the logs dont contain anything too unusual.

Any help appreciated.

Many thanks

Jon


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] opensips 2.2.5 stop responding/processing requests. - Centos 6.5

[Johan De Clercq]

If you use acc with radius, check radius config.

Br

On 30 Oct 2017 18:33, "Jonathan Hunter"  wrote:

> Hi Guys,
>
> Has anyone had the following behaviour with this release of opensips?
>
> It has been running fine for a number of months, and then suddenly today
> the server which was running as the primary suddenly stopped responding to
> SIP requests, or stopped processing them, or there was a long pause in a
> sequence completing.
>
> So in some cases, INVITES or REGISTER messages were ignored and the
> initial requests werent always logged in the opensips log file (even though
> we do this for all messages), however the SIP requests were hitting the
> server as I was tracing them.
>
> In the logs I can see the following warnings we havent seen before;
>
> Oct 30 13:31:25 sgw6 VU-SIP-Proxy[11159]: WARNING:core:utimer_ticker:
> utimer task  already scheduled for 9639891650 ms (now 9639891850
> ms), it may overlap.
> Oct 30 13:52:48 sgw6 VU-SIP-Proxy[11159]: WARNING:core:timer_ticker: timer
> task  already scheduled for 9640994180 ms (now 9641175280 ms), it
> may overlap..
> Oct 30 13:52:48 sgw6 VU-SIP-Proxy[11159]: WARNING:core:timer_ticker: timer
> task  already scheduled for 9640980270 ms (now 9641175280 ms), it
> may overlap..
>
> A restart of the opensips application didnt help, and service was only
> restored fully when I failed over to the secondary server.
>
> Has anyone had these issues before? There are no obvious server level
> issues, and as I mentioned the logs dont contain anything too unusual.
>
> Any help appreciated.
>
> Many thanks
>
> Jon
>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] opensips 2.2.5 stop responding/processing requests. - Centos 6.5

[Jonathan Hunter]

Hi Guys,

Has anyone had the following behaviour with this release of opensips?

It has been running fine for a number of months, and then suddenly today the 
server which was running as the primary suddenly stopped responding to SIP 
requests, or stopped processing them, or there was a long pause in a sequence 
completing.

So in some cases, INVITES or REGISTER messages were ignored and the initial 
requests werent always logged in the opensips log file (even though we do this 
for all messages), however the SIP requests were hitting the server as I was 
tracing them.

In the logs I can see the following warnings we havent seen before;

Oct 30 13:31:25 sgw6 VU-SIP-Proxy[11159]: WARNING:core:utimer_ticker: utimer 
task  already scheduled for 9639891650 ms (now 9639891850 ms), it 
may overlap.
Oct 30 13:52:48 sgw6 VU-SIP-Proxy[11159]: WARNING:core:timer_ticker: timer task 
 already scheduled for 9640994180 ms (now 9641175280 ms), it may 
overlap..
Oct 30 13:52:48 sgw6 VU-SIP-Proxy[11159]: WARNING:core:timer_ticker: timer task 
 already scheduled for 9640980270 ms (now 9641175280 ms), it may 
overlap..

A restart of the opensips application didnt help, and service was only restored 
fully when I failed over to the secondary server.

Has anyone had these issues before? There are no obvious server level issues, 
and as I mentioned the logs dont contain anything too unusual.

Any help appreciated.

Many thanks

Jon

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Optimal trunk capacity filling algorithm or capacity-aware LCR

[Alex Balashov]

The simplest and lowest-hanging fruit here is profit margin protection. Don't 
return routes from the LCR whose cost exceeds the sell rate. This will ensure 
that client 1 is never routed out Trunk 2, period - if Trunk 1 is exhausted, 
you don't complete the calls.

Then, add some logic to ensure that any given client's calls cannot monopolise 
more than x% of Trunk X, perhaps activated only if Trunk X is at least y% 
utilised. Make it possible to tune this on a per-client and per-trunk basis. 
You can use the dialog module to enforce all these thresholds.

That should get you to a good result. 

-- Alex

--
Sent via mobile, please forgive typos and brevity. 

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Can't add bin_listen interface to script

[Matine Tinthaitae]

Thank you, that works perfectly.

There is a difference in the documentation between these two pages which
caused my error:
https://www.opensips.org/html/docs/modules/2.2.x/proto_bin.html
https://www.opensips.org/Documentation/Interface-Binary-2-2

//Matine

2017-10-30 13:16 GMT+01:00 Vlad Patrascu :

> Hi,
>
> The "bin_listen" parameter was removed in OpenSIPS 2.2.X and bin listeners
> should be defined using "listen = bin:a.b.c.d:".
>
> Regards,
>
> Vlad Patrascu
> OpenSIPS Developerhttp://www.opensips-solutions.com
>
> On 10/30/2017 11:11 AM, Matine Tinthaitae wrote:
>
> Hi,
>
> I'm trying to use the Binary Interface to replicate dialogs in OpenSIPS
> 2.2.5.
> When ever i add "bin_listen = a.b.c.d:" opensips fails to start.
>
> Oct 30 10:08:27 [26532] CRITICAL:core:yyerror: parse error in config file
> /usr/local//etc/opensips/opensips.cfg, line 143, column 1-11: syntax error
> Oct 30 10:08:27 [26532] CRITICAL:core:yyerror: parse error in config file
> /usr/local//etc/opensips/opensips.cfg, line 143, column 1-11:
> Oct 30 10:08:27 [26532] ERROR:core:main: bad config file (2 errors)
> Oct 30 10:08:27 [26532] NOTICE:core:main: Exiting
>
> Is the binary interface not available in 2.2.5 or what am i doing wrong?
>
> Thank you in advance!
>
> //Matine
>
>
> ___
> Users mailing 
> listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Can't add bin_listen interface to script

[Vlad Patrascu]

Hi,

The "bin_listen" parameter was removed in OpenSIPS 2.2.X and bin 
listeners should be defined using "listen = bin:a.b.c.d:".


Regards,

Vlad Patrascu
OpenSIPS Developer
http://www.opensips-solutions.com

On 10/30/2017 11:11 AM, Matine Tinthaitae wrote:

Hi,

I'm trying to use the Binary Interface to replicate dialogs in 
OpenSIPS 2.2.5.

When ever i add "bin_listen = a.b.c.d:" opensips fails to start.

Oct 30 10:08:27 [26532] CRITICAL:core:yyerror: parse error in config 
file /usr/local//etc/opensips/opensips.cfg, line 143, column 1-11: 
syntax error
Oct 30 10:08:27 [26532] CRITICAL:core:yyerror: parse error in config 
file /usr/local//etc/opensips/opensips.cfg, line 143, column 1-11:

Oct 30 10:08:27 [26532] ERROR:core:main: bad config file (2 errors)
Oct 30 10:08:27 [26532] NOTICE:core:main: Exiting

Is the binary interface not available in 2.2.5 or what am i doing wrong?

Thank you in advance!

//Matine


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users