Re: [OpenSIPS-Users] Mid_registrar forking issue when push notifications enabled

[Sugar]

Is there a private place to upload debug log including config (in case some 
sanitation of sensitive info is missed)? Can you provide where to send? Thanks 
in advance. And yes it appears the register matching part is not occurring. Can 
also provide pcap of call when contact is pn enabled on one test extension that 
is being called as well. Let me know where I can send. And thank you again for 
responding.Also while the column size was fixed in the usrloc table, the dialog 
table was not fixed, it still has char(255). I updated my schema to fix it (was 
using mysql db to save dialogs for testing and possible expansion to two 
opensips instances in dev environment.
 Original message From: Liviu Chircu  Date: 
1/17/22  2:11 PM  (GMT-06:00) To: users@lists.opensips.org Subject: Re: 
[OpenSIPS-Users] Mid_registrar forking issue when push notifications enabled 
Hi,

Answers inline,


On 17.01.2022 10:18, Sugar wrote:


  
  
  
  The log shows the push notification is successful
using rest client, 1 second after successful android push
notification, the client registers but the call is not forked
(it appears no transaction branch injection occurs).

So everything worked except for the last
  step: the REGISTER-INVITE matching part.  Could you post some full
  DEBUG logs of a call sequence, including the final Re-REGISTER
  triggered by the PN?  I need to understand why the event_routing
  module is not properly matching that Re-REGISTER to the halted
  INVITE.

  
  
  Mid_registrar_save params are p0c2f
  
  
  Mid_registrar_lookup called with m flag only when
si is from main registrar.
  
  
  Mid registrar mode 2
  
  
  Pn enabled with default values.
  
  
  E_UL_contact_refresh properly raised
  
  
  Usrloc fr_timeout raised to 10 seconds
  
   pn_process_purr is not enabled.

Settings "sound" OK.  Perhaps including them
  could help to some degree.  I am actually doing some testing on
  this 3.2.4 code these days as well, so expect more feedback to
  come, as I run through the same flows.

  
  
  PS storing call dialog in a database requires the
contact fields to be changed from char(255) to text when pn
enabled. It has been really hard trying to find where to alert
opensips about that. If someone has that info can you let me
know (ie github, developer list, other support avenue).

Per the timely suggestions of John Quick,
this limitation of the DB schema was already fixed and
backported to 3.1+ five months ago, see here[1].
[1]:
https://github.com/OpenSIPS/opensips/commit/70e8b24b
Best Regards,

-- 
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com
  

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

Re: [OpenSIPS-Users] Mid_registrar forking issue when push notifications enabled

[Liviu Chircu]

Hi,

Answers inline,

On 17.01.2022 10:18, Sugar wrote:


The log shows the push notification is successful using rest client, 1 
second after successful android push notification, the client 
registers but the call is not forked (it appears no transaction branch 
injection occurs).
So everything worked except for the last step: the REGISTER-INVITE 
matching part.  Could you post some full DEBUG logs of a call sequence, 
including the final Re-REGISTER triggered by the PN?  I need to 
understand why the event_routing module is not properly matching that 
Re-REGISTER to the halted INVITE.


Mid_registrar_save params are p0c2f

Mid_registrar_lookup called with m flag only when si is from main 
registrar.


Mid registrar mode 2

Pn enabled with default values.

E_UL_contact_refresh properly raised

Usrloc fr_timeout raised to 10 seconds

 pn_process_purr is not enabled.
Settings "sound" OK.  Perhaps including them could help to some degree.  
I am actually doing some testing on this 3.2.4 code these days as well, 
so expect more feedback to come, as I run through the same flows.


PS storing call dialog in a database requires the contact fields to be 
changed from char(255) to text when pn enabled. It has been really 
hard trying to find where to alert opensips about that. If someone has 
that info can you let me know (ie github, developer list, other 
support avenue).


Per the timely suggestions of John Quick, this limitation of the DB 
schema was already fixed and backported to 3.1+ five months ago, see 
here^[1] .


[1]: https://github.com/OpenSIPS/opensips/commit/70e8b24b

Best Regards,

--
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com

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

Re: [OpenSIPS-Users] Facing some issue while running opensips 3.2 latest branch with openssl-1.1.1

[Ben Newlin]

Saurabh,

You had originally mentioned you were using openssl 1.1.1, and my workaround 
was concerning that. I see now that you are trying to use openssl 3. I will 
defer to the OpenSIPS team on this, but as it is 2 major versions newer I would 
expect that openssl version would need explicit support from OpenSIPS, as many 
of the interfaces and APIs are likely very different from openssl 1, which is 
what OpenSIPS currently supports. I would not expect it to just work out of the 
box.

Since OpenSIPS has started moving to a different crypto library, I’m not sure 
whether openssl 3 support is planned.

Ben Newlin

From: Users  on behalf of Saurabh Chopra 

Date: Monday, January 17, 2022 at 8:58 AM
To: OpenSIPS users mailling list 
Subject: Re: [OpenSIPS-Users] Facing some issue while running opensips 3.2 
latest branch with openssl-1.1.1
Hi All,

Workaround given by Ben has done some part. Opensips 3.2.3 is compiled with 
latest openssl version 3.0.1 but still I am not able to run my configuration 
file. Errors coming like below:-

Jan 17 13:30:05 ip-192-168-0-56 opensips: ERROR:core:sr_load_module: could not 
open module : 
/usr/local/lib64/opensips/modules/tls_openssl.so: undefined symbol: 
OPENSSL_sk_num
Jan 17 13:30:05 ip-192-168-0-56 opensips: ERROR:core:load_module: failed to 
load module
Jan 17 13:30:05 ip-192-168-0-56 opensips: Traceback (last included file at the 
bottom):
Jan 17 13:30:05 ip-192-168-0-56 opensips: 0. 
/usr/local/etc/opensips/opensips_webrtc_proxy.cfg
Jan 17 13:30:05 ip-192-168-0-56 opensips: CRITICAL:core:yyerror: parse error in 
/usr/local/etc/opensips/opensips_webrtc_proxy.cfg:74:13-14: failed to load 
module tls_openssl.so

Could you please help us resolve this?

Best Regards
Saurabh Chopra
+918861979979


On Sat, Jan 15, 2022 at 9:27 PM Ben Newlin 
mailto:ben.new...@genesys.com>> wrote:
Apologies, I misspoke. It is not due to any change in OpenSIPS. It is caused by 
the change to openssl-1.1.1. We actually encountered the issue using OpenSIPS 
2.4, which still uses the shared libraries

Ben Newlin

From: Users 
mailto:users-boun...@lists.opensips.org>> on 
behalf of Ben Newlin mailto:ben.new...@genesys.com>>
Date: Saturday, January 15, 2022 at 10:54 AM
To: OpenSIPS users mailling list 
mailto:users@lists.opensips.org>>, Răzvan Crainea 
mailto:raz...@opensips.org>>, 
li...@opensips.org 
mailto:li...@opensips.org>>
Subject: Re: [OpenSIPS-Users] Facing some issue while running opensips 3.2 
latest branch with openssl-1.1.1
We ran into this too. I assume it is due to the change from using openssl as a 
shared library to a statically linked one.

We were able to resolve by setting the environment variable “LDFLAGS” to a 
value of “-pthread” before the make command.

$ LDFLAGS=-pthread make …

or

$ export LDFLAGS=-pthread
$ make …

I’m not a C expert, but that could possibly be added to the standard OpenSIPS 
build configuration.

Ben Newlin

From: Users 
mailto:users-boun...@lists.opensips.org>> on 
behalf of Saurabh Chopra mailto:saura...@3clogic.com>>
Date: Saturday, January 15, 2022 at 2:48 AM
To: OpenSIPS users mailling list 
mailto:users@lists.opensips.org>>, Răzvan Crainea 
mailto:raz...@opensips.org>>, 
li...@opensips.org 
mailto:li...@opensips.org>>
Subject: Re: [OpenSIPS-Users] Facing some issue while running opensips 3.2 
latest branch with openssl-1.1.1
Hi Opensips Team/ Razvan,

Thanks for the response, but when i tried to compile opensips version (3.2.3) 
with latest openssl version (3.0.1 14 Dec 2021) on Centos 7 machine, it throws 
me erros,

Linking opensips
main.o: In function `pthread_mutex_init':
/opt/opensips-codechanged-3.2/ssl_tweaks.h:32: undefined reference to 
`pthread_mutexattr_setpshared'
/opt/opensips-codechanged-3.2/ssl_tweaks.h:38: undefined reference to 
`pthread_mutexattr_destroy'
/opt/opensips-codechanged-3.2/ssl_tweaks.h:26: undefined reference to 
`pthread_mutexattr_init'
main.o: In function `pthread_rwlock_init':
/opt/opensips-codechanged-3.2/ssl_tweaks.h:64: undefined reference to 
`pthread_rwlockattr_setpshared'
/opt/opensips-codechanged-3.2/ssl_tweaks.h:70: undefined reference to 
`pthread_rwlockattr_destroy'
/opt/opensips-codechanged-3.2/ssl_tweaks.h:58: undefined reference to 
`pthread_rwlockattr_init'
collect2: error: ld returned 1 exit status
make: *** [opensips] Error 1

Same errors found on the GITHUB ticket 
https://github.com/OpenSIPS/opensips/issues/2088
 but the machine was Debian. And the package dependencies in the answer given 
by Liviu let us install openssl version 1.0.2, which we don't want to, because 
if we do, it will compile the opensips with 1.0.2 openssl version.

Kindly help us in this matter, we are stuck here.

Best Regards
Saurabh Chopra
+918861979979


On Mon, Jan 3, 2022 at 2:06 PM Răzvan Crainea 
mailto:raz...@opensips.org>> wrote:
Hi, Sasmita!

You probably compiled opensips 3.2 with a previous openssl 

[OpenSIPS-Users] Python and avp

[Alberto]

Hi,

I'm using opensips 3.4 and I'm looking to set avp variables from a python
script, looking at https://github.com/OpenSIPS/opensips/issues/1893 seems
this feature was available from after 3.0.
Is there any documentation on how to do it?

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

Re: [OpenSIPS-Users] Facing some issue while running opensips 3.2 latest branch with openssl-1.1.1

[Saurabh Chopra]

Hi All,

Workaround given by Ben has done some part. Opensips 3.2.3 is compiled with
latest openssl version 3.0.1 but still I am not able to run my
configuration file. Errors coming like below:-





*Jan 17 13:30:05 ip-192-168-0-56 opensips: ERROR:core:sr_load_module: could
not open module :
/usr/local/lib64/opensips/modules/tls_openssl.so: undefined symbol:
OPENSSL_sk_numJan 17 13:30:05 ip-192-168-0-56 opensips:
ERROR:core:load_module: failed to load moduleJan 17 13:30:05
ip-192-168-0-56 opensips: Traceback (last included file at the bottom):Jan
17 13:30:05 ip-192-168-0-56 opensips: 0.
/usr/local/etc/opensips/opensips_webrtc_proxy.cfgJan 17 13:30:05
ip-192-168-0-56 opensips: CRITICAL:core:yyerror: parse error in
/usr/local/etc/opensips/opensips_webrtc_proxy.cfg:74:13-14: failed to load
module tls_openssl.so*

Could you please help us resolve this?

Best Regards
Saurabh Chopra
+918861979979


On Sat, Jan 15, 2022 at 9:27 PM Ben Newlin  wrote:

> Apologies, I misspoke. It is not due to any change in OpenSIPS. It is
> caused by the change to openssl-1.1.1. We actually encountered the issue
> using OpenSIPS 2.4, which still uses the shared libraries
>
>
>
> Ben Newlin
>
>
>
> *From: *Users  on behalf of Ben Newlin <
> ben.new...@genesys.com>
> *Date: *Saturday, January 15, 2022 at 10:54 AM
> *To: *OpenSIPS users mailling list , Răzvan
> Crainea , li...@opensips.org 
> *Subject: *Re: [OpenSIPS-Users] Facing some issue while running opensips
> 3.2 latest branch with openssl-1.1.1
>
> We ran into this too. I assume it is due to the change from using openssl
> as a shared library to a statically linked one.
>
>
>
> We were able to resolve by setting the environment variable “LDFLAGS” to a
> value of “-pthread” before the make command.
>
>
>
> $ LDFLAGS=-pthread make …
>
>
>
> or
>
>
>
> $ export LDFLAGS=-pthread
>
> $ make …
>
>
>
> I’m not a C expert, but that could possibly be added to the standard
> OpenSIPS build configuration.
>
>
>
> Ben Newlin
>
>
>
> *From: *Users  on behalf of Saurabh
> Chopra 
> *Date: *Saturday, January 15, 2022 at 2:48 AM
> *To: *OpenSIPS users mailling list , Răzvan
> Crainea , li...@opensips.org 
> *Subject: *Re: [OpenSIPS-Users] Facing some issue while running opensips
> 3.2 latest branch with openssl-1.1.1
>
> Hi Opensips Team/ Razvan,
>
>
>
> Thanks for the response, but when i tried to compile opensips version
> (3.2.3) with latest openssl version (3.0.1 14 Dec 2021) on Centos 7
> machine, it throws me erros,
>
>
>
>
>
>
>
>
>
>
>
>
> *Linking opensips main.o: In function `pthread_mutex_init':
> /opt/opensips-codechanged-3.2/ssl_tweaks.h:32: undefined reference to
> `pthread_mutexattr_setpshared'
> /opt/opensips-codechanged-3.2/ssl_tweaks.h:38: undefined reference to
> `pthread_mutexattr_destroy' /opt/opensips-codechanged-3.2/ssl_tweaks.h:26:
> undefined reference to `pthread_mutexattr_init' main.o: In function
> `pthread_rwlock_init': /opt/opensips-codechanged-3.2/ssl_tweaks.h:64:
> undefined reference to `pthread_rwlockattr_setpshared'
> /opt/opensips-codechanged-3.2/ssl_tweaks.h:70: undefined reference to
> `pthread_rwlockattr_destroy' /opt/opensips-codechanged-3.2/ssl_tweaks.h:58:
> undefined reference to `pthread_rwlockattr_init' collect2: error: ld
> returned 1 exit status*
>
> *make: *** [opensips] Error 1*
>
>
>
> Same errors found on the GITHUB ticket 
> *https://github.com/OpenSIPS/opensips/issues/2088
>  *but the machine was
> Debian. And the package dependencies in the answer given by *Liviu* let
> us install openssl version 1.0.2, which we don't want to, because if we do,
> it will compile the opensips with 1.0.2 openssl version.
>
>
>
> Kindly help us in this matter, we are stuck here.
>
>
> Best Regards
>
> Saurabh Chopra
>
> +918861979979
>
>
>
>
>
> On Mon, Jan 3, 2022 at 2:06 PM Răzvan Crainea  wrote:
>
> Hi, Sasmita!
>
> You probably compiled opensips 3.2 with a previous openssl version, then
> replaced it with the new one.
> You need to re-compile tls_openssl with the new version to get this fixed.
>
> Best regards,
>
> Răzvan Crainea
> OpenSIPS Core Developer
> http://www.opensips-solutions.com
>
> On 12/21/21 12:30, Sasmita Panda wrote:
> > Hi All ,
> >
> > I have taken opensips 3.2 latest code and configure with tls_openssl to
> > support proto_tls proto_wss and tls_gm .
> > I have installed openssl-1.1.1 . (Rtpeninge latest branch is not
> > suported with older version of openssl , so I have taken the newer
> > version here )
> >
> >
> > Installation is successful . While running the opensips process I am
> > getting the below error .
> > *ERROR:core:sr_load_module: could not open module
> > :
> > /usr/local/lib64/opensips/modules/auth.so: undefined symbol:
> EVP_MD_CTX_free
> >   ERROR:core:load_module: failed to load module
> >   Traceback (last included file at the bottom):
> >   0. /usr/local/etc/opensips/opensips_webrtc_reg.cfg
> >   CRITICAL:core:yyerror: parse error in
> > 

[OpenSIPS-Users] Mid_registrar forking issue when push notifications enabled

[Sugar]

Hello. I am trying to implement mid_registrar with little success and need 
assistance.If the called contact is not pn enabled, the other internal 
extension rings and call is successful.If the called contact is push enabled it 
will not ring.Mid_registrar_lookup returns 2 and I do not t_relay itThe log 
shows the push notification is successful using rest client, 1 second after 
successful android push notification, the client registers but the call is not 
forked (it appears no transaction branch injection occurs).Mid_registrar_save 
params are p0c2fMid_registrar_lookup called with m flag only when si is from 
main registrar.Mid registrar mode 2Pn enabled with default 
values.E_UL_contact_refresh properly raisedUsrloc fr_timeout raised to 10 
secondsDoes pn_inv_refresh need to be increased when fr_timeout is increased. I 
have config and packet capture from opensips for when 1 contact is pn enabled 
and one is not. Using mid_registrar and dialog module and if anyone needs more 
info to assist. pn_process_purr is not enabled.Using opensips 3.2.4, Can 
someone please assist? Thanks in advance.I am hoping I don't have to switch to 
flexisip since I have spent a lot of time tweaking.PS storing call dialog in a 
database requires the contact fields to be changed from char(255) to text when 
pn enabled. It has been really hard trying to find where to alert opensips 
about that. If someone has that info can you let me know (ie github, developer 
list, other support avenue).___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users