Re: [OpenSIPS-Users] 183 to 180 manipulation without external application

[Nick Altmann]

You can try to use
https://opensips.org/docs/modules/3.3.x/sipmsgops.html#change_reply_status
, for example.

--
Nick

> Just rewerite the status line ?
> On 3/03/2023 14:19, Antonis Psaras wrote:
>
> I am trying to figure a way to translate 183 mes
>
> ___
> 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] 183 to 180 manipulation without external application

[johan]

Just rewerite the status line ?

On 3/03/2023 14:19, Antonis Psaras wrote:


I am trying to figure a way to translate 183 mes
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] 183 to 180 manipulation without external application

[Antonis Psaras]

Dear Team

 

I am trying to figure a way to translate 183 message to 180 or send a new
"fake" 180 following 183. I want to do that within opensips script to
minimize overhead in comparison with an external application. I saw the perl
example but the traffic is very high on that system and executing an
external script for each call will be very heavy.

 

Is there any thoughts/suggestion?

 

Best regards

 

 

Antonis Psaras

 

14 Iteas Str., Argyroupoli, 16452, Athens, Greece 
Tel: +30.21200.05300 | Fax: +30.21200.05800 
  www.microbase.gr 

 


 

Disclaimer. Privileged/Confidential information may be contained in this
message and may be subject to legal privilege. Access to this email by
anyone other than the intended recipient is unauthorized. If you are not the
intended recipient (or responsible for delivery of the message to such
person), you may not use, copy, distribute or deliver to anyone this message
(or any part of its contents) or take any action in reliance on it. In such
case, you should destroy this message, and notify us immediately. All
reasonable precautions have been taken to ensure no viruses are present in
this email. As we cannot accept responsibility for any loss or damage
arising from the use of this email or attachments we recommend that you
subject these to your virus checking procedures prior to use. The views,
opinions, conclusions and other information such us personal data (EE
2016/679- GDPR) expressed in this electronic mail are not given or endorsed
by Microbase unless otherwise indicated by an authorized company
representative independent of this message. Microbase.

 

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

[OpenSIPS-Users] Question related to sst module

[Wadii ELMAJDI | Evenmedia]

Hello,

I noticed a segmentation fault is caused by sst module :
Client B2BUA (UAC) invite has : Session-Expires: 1000 Min-SE: 90
Opensips SST min_se configured at 1800s, dialog has sst_flag.
This causes Opensips to crash :

opensips log :

Mar  3 13:06:10 test-boxopensips /usr/sbin/opensips[6088]: 
CRITICAL:core:sig_usr: segfault in process pid: 6088, id: 6
Mar  3 13:06:11 test-boxopensips /usr/sbin/opensips[6082]: 
INFO:core:handle_sigs: child process 6088 exited by a signal 11
Mar  3 13:06:11 test-boxopensips /usr/sbin/opensips[6082]: 
INFO:core:handle_sigs: core was not generated
Mar  3 13:06:11 test-boxopensips /usr/sbin/opensips[6082]: 
INFO:core:handle_sigs: terminating due to SIGCHLD

Sys log :

Mar  3 13:06:58 test-boxopensips kernel: [ 9969.171168] opensips[6185]: 
segfault at 968 ip 7f3da464b901 sp 7ffe8aec6f00 error 4 in 
tm.so[7f3da4617000+46000]
Mar  3 13:06:58 test-boxopensips kernel: [ 9969.173758] Code: 89 44 24 68 31 c0 
81 fa c7 00 00 00 0f 87 17 02 00 00 41 8d 84 24 d4 fe ff ff 83 f8 63 0f 86 0e 
01 00 00 48 8b 85 f0 00 00 00 <8b> 80 68 09 00 00 41 33 85 68 09 00 00 a8 01 0f 
85 39 01 00 00 4c

I have already solved the scripting problem by using sstCheckIn to adapt 
SessionExpire value to Opensips's min_se value.
Also, if the the UAC changes its session expires value to any value identical 
or higher than the one configured in OpenSIPS min_se value solves the problem.

My question : is this a normal behavior for opensips to completely crash ?

Opensips version :

version: opensips 3.2.11 (x86_64/linux)
flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, Q_MALLOC, 
F_MALLOC, HP_MALLOC, DBG_MALLOC, FAST_LOCK-ADAPTIVE_WAIT
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, 
MAX_URI_SIZE 1024, BUF_SIZE 65535
poll method support: poll, epoll, sigio_rt, select.
main.c compiled on  with gcc 10

Thank you.


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

[OpenSIPS-Users] problem with Qrouting

[Антон Ершов]

Hi guys,

I'm experimenting with the Qrouting module and got a strange result. it
blocks the use_next_gw function and returns $rc -1.

when calling the drouting() function in the debug log, I see:

DBG:qrouting:qr_sort_dynamic_weights: score for dst type 1, i: 0 is 1.00
DBG:qrouting:qr_sort_dynamic_weights: score for dst type 1, i: 1 is 1.00

order 1 works at this moment

when calling use_next_gw and must work order 0 i see

DBG:qrouting:qr_acc: engaging accounting for rule 0x7fb9a0061da0, cr: -1,
gw: 0
DBG:drouting:use_next_gw: new RURI set to  via
socket <10.153.5.38>

and get $rc -1

if in opensips-cli call qr_enable_dst or qr_disable_dst gw gets status -1

DBG:qrouting:qr_sort_dynamic_weights: score for dst type 1, i: 0 is
-1.00
DBG:qrouting:qr_sort_dynamic_weights: score for dst type 1, i: 1 is
-1.00

and drouting() can't get available gw

in q_profile all threshold have value -1 which indicates that the metric
should not be taken into account. but gw becomes unavailable

what am I doing wrong?
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users