[OpenSIPS-Users] Opensips-cp with Postgres MDB2 Error: unknown error

[Turner, Rick]

Hi, I'm using OpenSIPS Control Panel 6.2 with a postgres database and running 
into some issues I cannot figure out. Hopefully someone can help.

When accessing the Users/Alias Management, Users/User Management or trying a 
search from the System/CDR Viewer screen, I get the error:

Failed to issue query, error message : MDB2 Error: unknown error

I can add users using the 'Add New' button and I see them when I manually look 
in the subscribers table. It just seems to be the selects that don't work.

My httpd error log just shows some variables that were empty but nothing 
helpful for this.

Got any hints on what is the best way to start troubleshooting this issue?

Thanks.
This message (and any attachments) is intended solely for the addressee and may 
contain confidential and privileged information. If you have received this 
message in error, please send it back to us, and immediately and permanently 
delete it. Do not use, copy or disclose the information contained in this 
message or in any attachment. For information about how we process data and 
monitor communications please see our Privacy Statement, and for terms of use 
please see our Terms of Use both located at 
https://www.westuc.com/en-gb/terms-conditions-policies. "West UC" or "West" is 
a subsidiary of West Corporation and the trading name of West UC Limited, a 
company registered in England & Wales with registered number 2775270 and whose 
registered office is at Unit 1 & 2 Sawmills End, Barnwood, Gloucester, GL4 3DL, 
UK. This email is sent on behalf of West UC Limited unless you have been 
notified otherwise.
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] yum install vs download manual install

[Nick Altmann]

Please look into /etc/sysconfig/opensips .

You could find OPTIONS variable, write there -m and -M arguments to control
opensips memory size.

2017-02-20 20:09 GMT+03:00 Jeff Wilkie :

> If using the yum install on Centos, what's the preferred method to control
> the mem size since those files do not appear to be present?
>
> Jeff
>
>
> On Mon, Feb 20, 2017 at 7:38 AM, Bogdan-Andrei Iancu 
> wrote:
>
>> Hi Jeff,
>>
>> The main different between packages versus tarballs is the OS integration
>> : while the tarball gives you OpenSIPS, the pacakges come with additional
>> scripts to help with the OS integration (like the init.d script, some
>> default settings)
>>
>> Regards,
>>
>> Bogdan-Andrei Iancu
>> OpenSIPS Founder and Developerhttp://www.opensips-solutions.com
>>
>> On 02/15/2017 08:22 PM, Jeff Wilkie wrote:
>>
>> What am I missing out on by installing via yum vs the way I've always
>> installed OPENSIPS by download extraction?  I notice some of the linking
>> files and MEMORY setting files are not to be located from the yum install
>> version but I'm afraid other important items might also be missing to
>> complete a full and successful implementation of OPENSIPS for production
>> use?  Recommendations?  Should I abandon the yum install?  I do like the
>> ease of the installation! lol  Is there a file to control MEM used and
>> threads?
>>
>> Thanks
>>
>> Jeff
>>
>>
>>
>>
>>
>> ___
>> 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] yum install vs download manual install

[Jeff Wilkie]

If using the yum install on Centos, what's the preferred method to control
the mem size since those files do not appear to be present?

Jeff


On Mon, Feb 20, 2017 at 7:38 AM, Bogdan-Andrei Iancu 
wrote:

> Hi Jeff,
>
> The main different between packages versus tarballs is the OS integration
> : while the tarball gives you OpenSIPS, the pacakges come with additional
> scripts to help with the OS integration (like the init.d script, some
> default settings)
>
> Regards,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developerhttp://www.opensips-solutions.com
>
> On 02/15/2017 08:22 PM, Jeff Wilkie wrote:
>
> What am I missing out on by installing via yum vs the way I've always
> installed OPENSIPS by download extraction?  I notice some of the linking
> files and MEMORY setting files are not to be located from the yum install
> version but I'm afraid other important items might also be missing to
> complete a full and successful implementation of OPENSIPS for production
> use?  Recommendations?  Should I abandon the yum install?  I do like the
> ease of the installation! lol  Is there a file to control MEM used and
> threads?
>
> Thanks
>
> Jeff
>
>
>
>
>
> ___
> 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

[OpenSIPS-Users] OpenSIPs 2.2.2 warnings

[Ramachandran, Agalya (Contractor)]

Hi Bogdan/Razvan,

My warnings are not stopped. I see it coming continuously all time. I am not 
running any load on these OpenSIPS servers.
I am using async rest_put in my config file and children process is configured 
as 24.
Even if I try to reduce my children process to 12/8/4, I see this warning 
continuously when I just do install on the 2.2.2 source code.
What  is causing these warning even if I don’t run a single call? Your guidance 
to stop these warnings would be great help for me.

Is there anything in the config file, could lead these warning? I want to fix 
those. Can you please point out, what are the possible things I can check and 
fine tune to get away of these Warnings?

Feb 20 06:15:01 sturn-test /usr/local/sbin/opensips[16632]: 
WARNING:core:handle_timer_job: utimer job  has a 2 us delay in 
execution
Feb 20 07:00:07 sturn-test /usr/local/sbin/opensips[16631]: 
WARNING:core:handle_timer_job: utimer job  has a 2 us delay in 
execution
Feb 20 12:37:07 sturn-test /usr/local/sbin/opensips[16626]: 
WARNING:core:handle_timer_job: utimer job  has a 2 us delay in 
execution
Feb 20 13:59:59 sturn-test /usr/local/sbin/opensips[16632]: 
WARNING:core:handle_timer_job: utimer job  has a 2 us delay in 
execution
Feb 20 14:34:31 sturn-test /usr/local/sbin/opensips[16629]: 
WARNING:core:handle_timer_job: utimer job  has a 2 us delay in 
execution
Feb 20 15:19:26 sturn-test /usr/local/sbin/opensips[16632]: 
WARNING:core:handle_timer_job: utimer job  has a 6 us delay in 
execution
Feb 20 15:41:40 sturn-test /usr/local/sbin/opensips[16632]: 
WARNING:core:handle_timer_job: utimer job  has a 2 us delay in 
execution
Feb 20 16:04:01 sturn-test /usr/local/sbin/opensips[16623]: 
WARNING:core:handle_timer_job: timer job  has a 8 us delay in 
execution
Feb 20 16:32:21 sturn-test /usr/local/sbin/opensips[16632]: 
WARNING:core:handle_timer_job: utimer job  has a 2 us delay in 
execution

Regards,
Agalya

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

Re: [OpenSIPS-Users] yum install vs download manual install

[Bogdan-Andrei Iancu]

Hi Jeff,

The main different between packages versus tarballs is the OS 
integration : while the tarball gives you OpenSIPS, the pacakges come 
with additional scripts to help with the OS integration (like the init.d 
script, some default settings)


Regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com

On 02/15/2017 08:22 PM, Jeff Wilkie wrote:
What am I missing out on by installing via yum vs the way I've always 
installed OPENSIPS by download extraction? I notice some of the 
linking files and MEMORY setting files are not to be located from the 
yum install version but I'm afraid other important items might also be 
missing to complete a full and successful implementation of OPENSIPS 
for production use? Recommendations?  Should I abandon the yum 
install?  I do like the ease of the installation! lol  Is there a file 
to control MEM used and threads?


Thanks

Jeff





___
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] Warning handle_timer_job

[Bogdan-Andrei Iancu]

Hello,

The tm-utimer is the timer job performing the SIP retransmissions. And 
OpenSIPS reports an overload of this timer - basically 100ms were not 
enough for OpenSIPS to finish doing all the needed retransmissions. This 
is not an error, but an warning telling you that there are too many 
retransmissions to be performed, eating  a lot processing cycles.


I guess that the retransmissions are due some issues with the SIP traffic ?

Best regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com

On 02/19/2017 05:46 PM, sougol gheissi wrote:

Hello all,
I have a Pentium 3 Proxy server, configured with the opensips, any 
time I want to send more than 500 message per second via the proxy I 
get this warning and a lot of retransmissions occur. Here is a part of 
the log file:


Feb 19 18:43:41 [13020] WARNING:core:handle_timer_job: timer job 
 has a 2 us delay in execution
Feb 19 18:47:44 [13027] WARNING:core:handle_timer_job: timer job 
 has a 2 us delay in execution
Feb 19 19:00:41 [13023] WARNING:core:handle_timer_job: timer job 
 has a 3 us delay in execution
Feb 19 19:00:43 [13018] WARNING:core:handle_timer_job: timer job 
 has a 2 us delay in execution
Feb 19 19:00:43 [13017] WARNING:core:utimer_ticker: utimer task 
 already scheduled for 2504330 ms (now 2504430 ms), it may 
overlap..
Feb 19 19:00:48 [13020] WARNING:core:handle_timer_job: timer job 
 has a 4 us delay in execution
Feb 19 19:00:53 [13028] WARNING:core:handle_timer_job: timer job 
 has a 5 us delay in execution
Feb 19 19:00:53 [13030] WARNING:core:handle_timer_job: utimer job 
 has a 2 us delay in execution
Feb 19 19:01:07 [13027] WARNING:core:handle_timer_job: timer job 
 has a 2 us delay in execution


BTW, I have searched through the Internet, I have increased the 
children to 12, but the problem still exist. I also don't have a 
radius server which was another solution given.

I really need help.
Thank you


___
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] Transactional REGISTER processing with 2.1

[Maxim Sobolev]

Hi Razvan, this is the code from SER 2.0. There is no equivalent for
"s:digest_challenge" or "s:contact" AVPs as far as I can tell looking to
the code in question in OpenSIPS.

-Max

On Mon, Feb 20, 2017 at 12:25 AM Răzvan Crainea  wrote:

> Hi, Maxim!
>
> The code you are using now should do what you request. t_newtran() returns
> 0 for retransmissions, therefore for the second message (retransmission)
> that will run the script, t_newtran() will immediately absorb the message
> and return without executing any further instructions.
>
> Best regards,
>
> Răzvan Crainea
> OpenSIPS Solutionswww.opensips-solutions.com
>
> On 02/17/2017 09:15 PM, Maxim Sobolev wrote:
>
> P.S. python_exec("www_authenticate") does not do any magic here, it's
> just figures out the right domain to use based on some business rules and
> then calls www_authenticate() with that parameter.
>
> On Fri, Feb 17, 2017 at 11:12 AM, Maxim Sobolev 
> wrote:
>
> Hi guys,
>
> We are underway to migrate from ancient SER-2.0.0 to more modern OpenSIPS
> and one of the question that is still in my TODO list is implementing
> transactional processing of the REGISTER requests. In the old SER we had
> something along those lines:
>
> route[3] {
> # Ensure that all incoming messages contain auth info
> xlog("L_INFO", "processing %rm received from %si:%sp");
> if (!t_newtran()) {
> sl_send_reply("500", "could not create transaction");
> break;
> };
> if (!python_exec("www_authenticate")) {
> xlog("L_INFO", "challenging %ct");
> if (is_avp_set("s:digest_challenge")) {
> append_to_reply("%$digest_challenge");
> };
> t_reply("401", "Unauthorized");
> break;
> };
>[some more unrelated processing and checks...]
> xlog("L_INFO", "saving contact %ct into the database");
> save_noreply("location");
> if (is_avp_set("s:contact")) {
> append_to_reply("%$contact");
> };
> t_reply("$code", "$reason");
> }
>
> The idea here is to avoid possibly costly DB lookup and other checks on
> each possible re-transmit. What would be the proper way of doing this with
> the OpenSIPS 2.1? Or if it's not possible to replicate such scheme, what
> would be the best way to implement this which to get the change accepted
> into the OpenSIPS mainline?
>
> Any ideas, pointers, hints are greatly appreciated. Thanks in advance!
>
> -Maxim
>
>
>
>
> --
> Maksym Sobolyev
> Sippy Software, Inc.
> Internet Telephony (VoIP) Experts
> Tel (Canada): +1-778-783-0474
> Tel (Toll-Free): +1-855-747-7779
> Fax: +1-866-857-6942
> Web: http://www.sippysoft.com
> MSN: sa...@sippysoft.com
> Skype: SippySoft
>
>
> --
Maksym Sobolyev
Sippy Software, Inc.
Internet Telephony (VoIP) Experts
Tel (Canada): +1-778-783-0474
Tel (Toll-Free): +1-855-747-7779
Fax: +1-866-857-6942
Web: http://www.sippysoft.com
MSN: sa...@sippysoft.com
Skype: SippySoft
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] Transactional REGISTER processing with 2.1

[Maxim Sobolev]

Hi guys,

We are underway to migrate from ancient SER-2.0.0 to more modern OpenSIPS
and one of the question that is still in my TODO list is implementing
transactional processing of the REGISTER requests. In the old SER we had
something along those lines:

route[3] {
# Ensure that all incoming messages contain auth info
xlog("L_INFO", "processing %rm received from %si:%sp");
if (!t_newtran()) {
sl_send_reply("500", "could not create transaction");
break;
};
if (!python_exec("www_authenticate")) {
xlog("L_INFO", "challenging %ct");
if (is_avp_set("s:digest_challenge")) {
append_to_reply("%$digest_challenge");
};
t_reply("401", "Unauthorized");
break;
};
   [some more unrelated processing and checks...]
xlog("L_INFO", "saving contact %ct into the database");
save_noreply("location");
if (is_avp_set("s:contact")) {
append_to_reply("%$contact");
};
t_reply("$code", "$reason");
}

The idea here is to avoid possibly costly DB lookup and other checks on
each possible re-transmit. What would be the proper way of doing this with
the OpenSIPS 2.1? Or if it's not possible to replicate such scheme, what
would be the best way to implement this which to get the change accepted
into the OpenSIPS mainline?

Any ideas, pointers, hints are greatly appreciated. Thanks in advance!

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

Re: [OpenSIPS-Users] Transactional REGISTER processing with 2.1

[Maxim Sobolev]

P.S. python_exec("www_authenticate") does not do any magic here, it's just
figures out the right domain to use based on some business rules and then
calls www_authenticate() with that parameter.

On Fri, Feb 17, 2017 at 11:12 AM, Maxim Sobolev 
wrote:

> Hi guys,
>
> We are underway to migrate from ancient SER-2.0.0 to more modern OpenSIPS
> and one of the question that is still in my TODO list is implementing
> transactional processing of the REGISTER requests. In the old SER we had
> something along those lines:
>
> route[3] {
> # Ensure that all incoming messages contain auth info
> xlog("L_INFO", "processing %rm received from %si:%sp");
> if (!t_newtran()) {
> sl_send_reply("500", "could not create transaction");
> break;
> };
> if (!python_exec("www_authenticate")) {
> xlog("L_INFO", "challenging %ct");
> if (is_avp_set("s:digest_challenge")) {
> append_to_reply("%$digest_challenge");
> };
> t_reply("401", "Unauthorized");
> break;
> };
>[some more unrelated processing and checks...]
> xlog("L_INFO", "saving contact %ct into the database");
> save_noreply("location");
> if (is_avp_set("s:contact")) {
> append_to_reply("%$contact");
> };
> t_reply("$code", "$reason");
> }
>
> The idea here is to avoid possibly costly DB lookup and other checks on
> each possible re-transmit. What would be the proper way of doing this with
> the OpenSIPS 2.1? Or if it's not possible to replicate such scheme, what
> would be the best way to implement this which to get the change accepted
> into the OpenSIPS mainline?
>
> Any ideas, pointers, hints are greatly appreciated. Thanks in advance!
>
> -Maxim
>



-- 
Maksym Sobolyev
Sippy Software, Inc.
Internet Telephony (VoIP) Experts
Tel (Canada): +1-778-783-0474
Tel (Toll-Free): +1-855-747-7779
Fax: +1-866-857-6942
Web: http://www.sippysoft.com
MSN: sa...@sippysoft.com
Skype: SippySoft
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Transactional REGISTER processing with 2.1

[Răzvan Crainea]

Hi, Maxim!

The code you are using now should do what you request. t_newtran() 
returns 0 for retransmissions, therefore for the second message 
(retransmission) that will run the script, t_newtran() will immediately 
absorb the message and return without executing any further instructions.


Best regards,

Răzvan Crainea
OpenSIPS Solutions
www.opensips-solutions.com

On 02/17/2017 09:15 PM, Maxim Sobolev wrote:
P.S. python_exec("www_authenticate") does not do any magic here, it's 
just figures out the right domain to use based on some business rules 
and then calls www_authenticate() with that parameter.


On Fri, Feb 17, 2017 at 11:12 AM, Maxim Sobolev > wrote:


Hi guys,

We are underway to migrate from ancient SER-2.0.0 to more modern
OpenSIPS and one of the question that is still in my TODO list is
implementing transactional processing of the REGISTER requests. In
the old SER we had something along those lines:

route[3] {
# Ensure that all incoming messages contain auth info
xlog("L_INFO", "processing %rm received from %si:%sp");
if (!t_newtran()) {
sl_send_reply("500", "could not create transaction");
break;
};
if (!python_exec("www_authenticate")) {
xlog("L_INFO", "challenging %ct");
if (is_avp_set("s:digest_challenge")) {
append_to_reply("%$digest_challenge");
};
t_reply("401", "Unauthorized");
break;
};
   [some more unrelated processing and checks...]
xlog("L_INFO", "saving contact %ct into the database");
save_noreply("location");
if (is_avp_set("s:contact")) {
append_to_reply("%$contact");
};
t_reply("$code", "$reason");
}

The idea here is to avoid possibly costly DB lookup and other
checks on each possible re-transmit. What would be the proper way
of doing this with the OpenSIPS 2.1? Or if it's not possible to
replicate such scheme, what would be the best way to implement
this which to get the change accepted into the OpenSIPS mainline?

Any ideas, pointers, hints are greatly appreciated. Thanks in advance!

-Maxim




--
Maksym Sobolyev
Sippy Software, Inc.
Internet Telephony (VoIP) Experts
Tel (Canada): +1-778-783-0474
Tel (Toll-Free): +1-855-747-7779
Fax: +1-866-857-6942
Web: http://www.sippysoft.com
MSN: sa...@sippysoft.com 
Skype: SippySoft


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