date:20220103

Re: [OpenSIPS-Users] B2B logic with forked calls

2022-01-03 Thread Bogdan-Andrei Iancu


Hi Denys and A Happy New Year,

Let me check the pcap you PM'ed me.

Best regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  https://www.opensips-solutions.com
OpenSIPS eBootcamp 2021
  https://opensips.org/training/OpenSIPS_eBootcamp_2021/

On 12/22/21 10:18 AM, Denys Pozniak wrote:

Hello!

Yes, that's right, the documentation did not indicate that TH should 
generate different Call-IDs for different incoming branches...


But now there is still an open question about the work of the B2B 
module. It just generates separate Call-IDs, but does not forward the 
SIP CANCEL message (I will share the trace in a private message).


Happy upcoming holidays!


вт, 21 дек. 2021 г. в 17:28, Bogdan-Andrei Iancu >:


Hi Denys,

Doing TH with dialog does not provide you with different call-ids
for each branch. The TH (or changing) is done between in (caller)
and out (callee) sides. There is no doc stating that each branch
will get a different Call-ID (I hope :D).

Best regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com  
OpenSIPS eBootcamp 2021
   https://opensips.org/training/OpenSIPS_eBootcamp_2021/  


On 12/14/21 2:13 PM, Denys Pozniak wrote:

Hello!

Bogdan,
I tested the combination of dialog + TH modules and found out
that this also does not work correctly if the incoming call was
forked.
Outgoing legs have the same Call-ID and tag, although I would
expect them to be different.

The configuration is exactly the same as in the
Documentation/Tutorials-Topology-Hiding
[root@f-proxy opensips]$ opensips -V
version: opensips 3.2.3 (x86_64/linux)


ср, 6 окт. 2021 г. в 12:18, Bogdan-Andrei Iancu
mailto:bog...@opensips.org>>:

Hi Denys,

Before diving into the B2B dark corners, I would strongly
suggest to use OpenSIPS with dialog + topology hiding
modules, rather than B2B. The B2B is not so friendly with
parallel forking.

And as time as you only need TH, dialog + TH is be best way
to do it.

Best regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com  

OpenSIPS eBootcamp 2021
   https://opensips.org/training/OpenSIPS_eBootcamp_2021/  


On 9/7/21 2:14 PM, Denys Pozniak wrote:

Adding a scheme of the current call-flow scenario maybe it
is not completely clear from the previous message:

FreeSWITCH --(1-call)--> Fork Proxy --(N-branches)--> SEMS
--(N-calls)--> Edge Proxy > N-devices


вт, 7 сент. 2021 г. в 12:57, Denys Pozniak
mailto:denys.pozn...@gmail.com>>:

Hello!

Our service delivery logic is as follows:
Each user has an internal extension, under which there
are several devices with their own identifier.
With an incoming call to such a subscriber, FreeSWITCH
adds custom SIP headers with these device identifiers.
Further on these fields the superior Proxy forks legs
and then these legs pass through the Sems to become
completely separate calls.

Now there is a task to replace Sems with OpenSIPS.
The script below works fine, but only if the incoming
calls are not forked

/### Routing Logic 

route{

  if (is_method("INVITE") && !has_totag()) {
        b2b_init_request("top hiding");
        exit;
    }
}

route[b2b_logic_request] {
        b2b_pass_request();
        exit;
}/

If there is a fork with an answer on some device, then
OpenSIPS does not forward the SIP CANCEL (Reason:
SIP;cause=200;text="Call completed elsewhere") to the
rest and these devices keep ringing until timeout
(Reason: SIP;cause=480;text="NO_ANSWER")
Please help understand the nature of this behavior.

version: opensips 3.2.2 (x86_64/linux)

*Incoming SIP INVITE:*
2021/09/07 11:38:30.737456 192.168.27.84:5060
 -> 192.168.27.84:5080

INVITE
sip:qq2s92mnbrda@192.168.27.126:5060;transport=udp SIP/2.0
Record-Route:


Record-Route: 
Via: SIP/2.0/UDP
192.168.27.84;branch=z9hG4bKcc18.ec9a363ccc70d07691e11293d160cca6.1
Via: SIP/2.0/UDP
192.168.27.126;branch=z9hG4bKcc18.accd8d8bac35ac66a172f6ce173c9a34.0

Re: [OpenSIPS-Users] mid_registrar errors

2022-01-03 Thread Bogdan-Andrei Iancu


Hi Pavel,

OK, I will ask Liviu to take a deeper look into this, thanks for the report.

Best regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  https://www.opensips-solutions.com
OpenSIPS eBootcamp 2021
  https://opensips.org/training/OpenSIPS_eBootcamp_2021/

On 1/3/22 7:47 PM, Pavel Eremin wrote:
Thanks for your answer I suppose there is some little mistake in the 
code of mid_registrar due to this error easylly reproducing on the new 
opensips installation.
Conditions are simple: centos 7 or debian 10, opensips 3.2 ver, use 
mid_registrar (mode=2 or 1) and registrar in the same script.
For example for REGISTER with tU like 1000 we will make 
mid_registrar_save and for 2 we will do save().

In case of save() we will get those errors in logs.

I have created an 
issue(https://github.com/OpenSIPS/opensips/issues/2716 
) on github about that.




пн, 3 янв. 2022 г. в 21:34, Bogdan-Andrei Iancu >:


Hi Alexey,

What the errors say is that mid-registrar, upon deleting/expiring
a registered AOR, it is not able to push forward the un-register
to the main registrar. This happens as some internal key (attached
to the AOR) is not found by the mid-registrar.

Not sure how this may be related to the changing of the IPs, but I
guess this issue went away after some time, right? if not, you may
stop opensips mid-registrar, purge the "location" table (or how
you named it) and start opensips back. This will flush all the
pending (potential bogus records) and give you a fresh start. Note
that your device will have to re-register in order to have the
calling working again.

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com  
OpenSIPS eBootcamp 2021
   https://opensips.org/training/OpenSIPS_eBootcamp_2021/  


On 12/27/21 10:15 AM, Alexey Kazantsev via Users wrote:

Hi list.
What do these errors mean?
This started after migrating the virtual machine and changing IP
addresses.
Everything else remain unchanged.
Version 3.2.2
ERROR:mid_registrar:unregister_record: 'from' key not found,
skipping De-REGISTER
ERROR:mid_registrar:mid_reg_aor_event: failed to unregister contact
---
BR, Alexey
https://alexeyka.zantsev.com/ 

___
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



___
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] mid_registrar errors

2022-01-03 Thread Pavel Eremin

Thanks for your answer I suppose there is some little mistake in the code
of mid_registrar due to this error easylly reproducing on the new opensips
installation.
Conditions are simple: centos 7 or debian 10, opensips 3.2 ver, use
mid_registrar (mode=2 or 1) and registrar in the same script.
For example for REGISTER with tU like 1000 we will make mid_registrar_save
and for 2 we will do save().
In case of save() we will get those errors in logs.

I have created an issue(https://github.com/OpenSIPS/opensips/issues/2716)
on github about that.



пн, 3 янв. 2022 г. в 21:34, Bogdan-Andrei Iancu :

> Hi Alexey,
>
> What the errors say is that mid-registrar, upon deleting/expiring a
> registered AOR, it is not able to push forward the un-register to the main
> registrar. This happens as some internal key (attached to the AOR) is not
> found by the mid-registrar.
>
> Not sure how this may be related to the changing of the IPs, but I guess
> this issue went away after some time, right? if not, you may stop opensips
> mid-registrar, purge the "location" table (or how you named it) and start
> opensips back. This will flush all the pending (potential bogus records)
> and give you a fresh start. Note that your device will have to re-register
> in order to have the calling working again.
>
> Regards,
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>   https://www.opensips-solutions.com
> OpenSIPS eBootcamp 2021
>   https://opensips.org/training/OpenSIPS_eBootcamp_2021/
>
> On 12/27/21 10:15 AM, Alexey Kazantsev via Users wrote:
>
> Hi list.
>
> What do these errors mean?
> This started after migrating the virtual machine and changing IP addresses.
> Everything else remain unchanged.
>
> Version 3.2.2
>
> ERROR:mid_registrar:unregister_record: 'from' key not found, skipping
> De-REGISTER
> ERROR:mid_registrar:mid_reg_aor_event: failed to unregister contact
>
>
> ---
> BR, Alexey
> https://alexeyka.zantsev.com/
>
> ___
> 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] mid_registrar errors

2022-01-03 Thread Bogdan-Andrei Iancu


Hi Alexey,

What the errors say is that mid-registrar, upon deleting/expiring a 
registered AOR, it is not able to push forward the un-register to the 
main registrar. This happens as some internal key (attached to the AOR) 
is not found by the mid-registrar.


Not sure how this may be related to the changing of the IPs, but I guess 
this issue went away after some time, right? if not, you may stop 
opensips mid-registrar, purge the "location" table (or how you named it) 
and start opensips back. This will flush all the pending (potential 
bogus records) and give you a fresh start. Note that your device will 
have to re-register in order to have the calling working again.


Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  https://www.opensips-solutions.com
OpenSIPS eBootcamp 2021
  https://opensips.org/training/OpenSIPS_eBootcamp_2021/

On 12/27/21 10:15 AM, Alexey Kazantsev via Users wrote:

Hi list.
What do these errors mean?
This started after migrating the virtual machine and changing IP 
addresses.

Everything else remain unchanged.
Version 3.2.2
ERROR:mid_registrar:unregister_record: 'from' key not found, skipping 
De-REGISTER

ERROR:mid_registrar:mid_reg_aor_event: failed to unregister contact
---
BR, Alexey
https://alexeyka.zantsev.com/

___
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] Compiling for arm v7

2022-01-03 Thread Bogdan-Andrei Iancu


Hi Micael and Happy New Year ;)

This is more an cross-compiling issue. The arm v6 and 7 obsoleted the 
swp/swpb instructions - this is what the warning are saying. The problem 
is that your compiler is generating asm code with those instruction; and 
the warnings are reported by assembler (which knows that those 
instructions are not valid).


I'm not a cross-compiling export (not even closer :P), but I guess you 
are passing some wrong compiling flags, leading to this conflict here.


Best regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  https://www.opensips-solutions.com
OpenSIPS eBootcamp 2021
  https://opensips.org/training/OpenSIPS_eBootcamp_2021/

On 1/1/22 11:48 AM, Micael wrote:

Hi all,

(Happy New Year!)

I am trying to cross compile 3.2.4 for armv7. Now, I'm new to opensips,
so I have no previous experience to fall back on..

In short: I have issues, getting this warning when compiling
"swp{b} use is deprecated for ARMv6 and ARMv7"


What I have done is:
export 
CC_EXTRA_OPTS="--sysroot=/opt/toolchains/gcc-arm-10.2-2020.11-x86_64-arm-none-linux-gnueabihf/arm-none-linux-gnueabihf/libc

-I /volt001/tmp/sysroots-components/cortexa8hf-neon/openssl/usr/include"


export LD_EXTRA_OPTS="-L 
/volt001/tmp/sysroots-components/cortexa8hf-neon/openssl/usr/lib"


export 
CC="/opt/toolchains/gcc-arm-10.2-2020.11-x86_64-arm-none-linux-gnueabihf/bin/arm-none-linux-gnueabihf-gcc 
-marm -march=armv7-a -mthumb-interwork -mfloat-abi=hard -mfpu=neon"


export CPU=armv7a


I then had to remove the following section in Makefile.defs, otherwise 
it would add strongarm1100 as cpu.


---8<-8<--
ifeq    ($(CC_CLASS), 4.x)
    CFLAGS+=-mcpu=strongarm1100 -ftree-vectorize
else
#if gcc 3.0+
ifeq    ($(CC_CLASS), 3.x)
    CFLAGS+= -mcpu=strongarm1100
else
ifeq    ($(CC_CLASS), 2.9x) #older gcc version (2.9[1-5])
$(warning Old gcc detected ($(CC_SHORTVER)), use  gcc 3.0.x \
for better results)

    CFLAGS+=
else
    #really old version
$(warning    You are using an old and unsupported gcc \
 version ($(CC_SHORTVER)), compile at your own risk!)

endif    # CC_CLASS, 2.9x
endif    # CC_CLASS, 3.x
---8<-8<--






Once I have done that, everything compiles, but with one and the same 
warning (lots, and lots of them);



e.g.:

Compiling ip_addr.c
/tmp/ccj7cheW.s: Assembler messages:
/tmp/ccj7cheW.s:1857: swp{b} use is deprecated for ARMv6 and ARMv7
/tmp/ccj7cheW.s:1892: swp{b} use is deprecated for ARMv6 and ARMv7
/tmp/ccj7cheW.s:1928: swp{b} use is deprecated for ARMv6 and ARMv7
/tmp/ccj7cheW.s:2171: swp{b} use is deprecated for ARMv6 and ARMv7
/tmp/ccj7cheW.s:2206: swp{b} use is deprecated for ARMv6 and ARMv7
/tmp/ccj7cheW.s:2242: swp{b} use is deprecated for ARMv6 and ARMv7
Compiling ipc.c
Compiling main.c
Compiling map.c
/tmp/cc6q8n3v.s: Assembler messages:
/tmp/cc6q8n3v.s:6001: swp{b} use is deprecated for ARMv6 and ARMv7
/tmp/cc6q8n3v.s:6036: swp{b} use is deprecated for ARMv6 and ARMv7
/tmp/cc6q8n3v.s:6072: swp{b} use is deprecated for ARMv6 and ARMv7
Compiling md5.c
Compiling md5utils.c


I guess I must not be the only one compiling for arm, so I hope 
someone can point me closer to whats wrong.



Any help appreciated,
  Micael

___
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] Incorrect tls port

2022-01-03 Thread Bogdan-Andrei Iancu


Hello Sergey,

Could you provide a SIP capture (and calling scenario) to underline the 
issue you have ?


Best regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  https://www.opensips-solutions.com
OpenSIPS eBootcamp 2021
  https://opensips.org/training/OpenSIPS_eBootcamp_2021/

On 12/30/21 2:50 PM, Sergey Pisanko wrote:

Hello!

I try to realize the next scenario with UAs, Opensips-2.4 and Asterisk.
UAs are registered onto Asterisk through Opensips and also - on 
Opensips if the 200 OK is came back from Asterisk.

Calls between UAs are relayed to Asterisk by Opensips.
This scenario works fine with udp. But it needs to do with tls. And 
here I have the problem. What happens.
Unlike udp, tcp cannot listen its port and create clients connection 
at the same time. Opensips listens tls port for clients connection
whereas it creates dynamic tcp port to connect to Asterisk. As a 
result, I see that port in Record-Route header in 200 OK addressed to 
caller.
Thus, callers ACK comes to that dynamic port instead of Opensips 
listened port and Opensips dropped it.

And question is how to force Opensips to put right port for caller?

Regards,
Serhii Pysanko.



Mailtrack 
 
	Sender notified by
Mailtrack 
 
	12/30/21, 02:49:47 PM 	



___
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] how to change mysql data directory to CP

2022-01-03 Thread Bogdan-Andrei Iancu


Hi there, and Happy New Year.

Let's clarify on what version of CP you are using - is is the master 
branch? or the 8.3.2 branch ?


Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  https://www.opensips-solutions.com
OpenSIPS eBootcamp 2021
  https://opensips.org/training/OpenSIPS_eBootcamp_2021/

On 12/29/21 1:42 PM, Tomi Hakkarainen wrote:

Hi,


I second Mario.

Its not so simple…. With these instructions provided to this thread.

There is no that kind of config on the file db.inc.php

But I guess if you can connect from cli to the MYSQL with the creds 
you have on that db.inc.php file -> also the connection with php/CP 
should work… or else there is something else preventing the connection.


Tomi


On 29. Dec 2021, at 12.37, Johan De Clercq > wrote:


Do cd /
Locate db.inc.php

Outlook voor iOS downloaden

*Van:*Users > namens mrsanvicente 
mailto:mrsanvice...@gmail.com>>

*Verzonden:*Wednesday, December 29, 2021 2:51:07 AM
*Aan:*Bogdan-Andrei Iancu >
*CC:*OpenSIPS users mailling list >

*Onderwerp:*Re: [OpenSIPS-Users] how to change mysql data directory to CP
Hello Bogdan-Andrei / All,

Sorry for the delay.  I just didn’t find a path or var to modify in 
 db.inc.php.



But later after a reboot, opensips stop working because it could not 
find the new path to the db.


So the source of the problem might be,  how to change path to mysql to 
opensips.

 Thanks
Saludos
Mario San Vicente


El 17 dic 2021, a la(s) 9:16, Bogdan-Andrei Iancu 
mailto:bog...@opensips.org>> escribió:


You need to update the DB settings in this file:

https://github.com/OpenSIPS/opensips-cp/blob/master/config/db.inc.php 



Regards,
Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com  
OpenSIPS eBootcamp 2021
   https://opensips.org/training/OpenSIPS_eBootcamp_2021/  

On 12/16/21 1:52 AM, mrsanvicente wrote:

Yes i did.   And restarted mysqld and httpd.  But still not working.


Thanks

Mario San Vicente


El 15 dic 2021, a la(s) 16:14, Joseph 
Jackson 
escribió:



Did you also change the location of the socket file in the my.cnf?

*From:*Users [mailto:users-boun...@lists.opensips.org 
]*On Behalf Of*Mario San 
Vicente

*Sent:*Wednesday, December 15, 2021 11:27 AM
*To:*OpenSIPS users mailling list
*Subject:*[OpenSIPS-Users] how to change mysql data directory to CP

Hello Everyone,

I have changed my mysql directory and a had limited space on the 
default partition.   I applied the change and opensips is working 
fine.  But the control panel is not working and i can not find 
where to update it.


Getting the following error:

http://x.x.x.x/cp/login.php 

Error!: SQLSTATE[HY000] [2002] Can't connect to local MySQL server 
through socket '/var/lib/mysql/mysql.sock' (2)


Any idea, where to update this?

Saludos!

Mario San Vicente

___
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  




___
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] Facing some issue while running opensips 3.2 latest branch with openssl-1.1.1

2022-01-03 Thread Răzvan Crainea


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 
/usr/local/etc/opensips/opensips_webrtc_reg.cfg:134:13-14: failed to 
load module auth.so

*

* ERROR:core:sr_load_module: could not open module 
: 
/usr/local/lib64/opensips/modules/tls_openssl.so: undefined symbol: 
OPENSSL_sk_num

  ERROR:core:load_module: failed to load module
  Traceback (last included file at the bottom):
  0. /usr/local/etc/opensips/opensips_webrtc_proxy.cfg
  CRITICAL:core:yyerror: parse error in 
/usr/local/etc/opensips/opensips_webrtc_proxy.cfg:77:13-14: failed to 
load module tls_openssl.so*


Can anyone help me how to resolve this please ?

*/Thanks & Regards/*
/Sasmita Panda/
/Senior Network Testing and Software Engineer/
/3CLogic , ph:07827611765/

___
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] B2B logic with forked calls

Re: [OpenSIPS-Users] mid_registrar errors

Re: [OpenSIPS-Users] mid_registrar errors

Re: [OpenSIPS-Users] mid_registrar errors

Re: [OpenSIPS-Users] Compiling for arm v7

Re: [OpenSIPS-Users] Incorrect tls port

Re: [OpenSIPS-Users] how to change mysql data directory to CP

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

8 matches

Site Navigation

Mail list logo

Footer information