Re: [OpenSIPS-Users] registrant.

[Bogdan-Andrei Iancu]

Hi Johan,

Take a look at 
https://www.opensips.org/Documentation/Install-DBSchema-3-2#AEN9219, it 
will definitely help you here.


Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  https://www.opensips-solutions.com
OpenSIPS Summit 27-30 Sept 2022, Athens
  https://www.opensips.org/events/Summit-2022Athens/

On 8/24/22 7:41 PM, johan wrote:

Is there somebody who has a db extract on how to fill in a record in
registrar ?


wkr,


___
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] registrant.

[johan]

Is there somebody who has a db extract on how to fill in a record in
registrar ?


wkr,


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

Re: [OpenSIPS-Users] Modify the headers after executing a MI function in B2B_LOGIC module

[Li Cai]

Hi Bogdan,

Thanks for the explanation. I mean that the local_route can take effect for the 
forwarded INVITE(from incoming ones) in our proxy, but not after b2b_bridge. 
I'll do more debugging on it since the messages should be visible. Thank you 
very much.


Thanks,
Li

From: Bogdan-Andrei Iancu 
Sent: August 24, 2022 10:33 AM
To: Li Cai ; OpenSIPS users mailling list 

Subject: Re: [OpenSIPS-Users] Modify the headers after executing a MI function 
in B2B_LOGIC module


WARNING: External Email: Exercise Caution

Hi Li,

All SIP requests generated by `b2b_bridge` are to be visible in local_route. 
And on the contrary, the incoming (received) requests DO NOT trigger local 
route.

Regards,


Bogdan-Andrei Iancu



OpenSIPS Founder and Developer

  
https://www.opensips-solutions.com

OpenSIPS Summit 27-30 Sept 2022, Athens

  
https://www.opensips.org/events/Summit-2022Athens/
On 8/24/22 4:34 PM, Li Cai wrote:
Hi Bogdan,

Yes, we have put the changes by calling remove_hf() and append_hf() in the 
'local_route', those functions for new incoming INVITE but not the INVITE sent 
out by 'b2b_bridge'.


Thanks,
Li

From: Bogdan-Andrei Iancu 
Sent: August 24, 2022 7:18 AM
To: OpenSIPS users mailling list 
; Li Cai 

Subject: Re: [OpenSIPS-Users] Modify the headers after executing a MI function 
in B2B_LOGIC module


WARNING: External Email: Exercise Caution


Hi Li,

Have you tried to use the local_route in order to do custom changes on the 
outgoing requests generated by the B2B bridging ?

Best regards,



Bogdan-Andrei Iancu



OpenSIPS Founder and Developer

  
https://www.opensips-solutions.com

OpenSIPS Summit 27-30 Sept 2022, Athens

  
https://www.opensips.org/events/Summit-2022Athens/
On 8/23/22 10:34 PM, Li Cai wrote:
Hi,

I'm working on a change for a B2BUA based on OpenSIPs 2.4, but not sure if the 
function is supported or if it has been supported in the later versions.

We have used the MI command b2b_bridge to bridge existing calls from one entity 
to another and it works, the scenario is the same as expected. While besides 
this, we also need to modify one of the headers of the INVITEs sending to the 
new destination in this scenario,  our scripts in the opensips.cfg can't take 
any effect.


Thanks,
Li
NOTICE TO RECIPIENT: This email, including attachments, may contain information 
which is confidential, proprietary, attorney-client privileged and / or 
controlled under U.S. export laws and regulations and may be restricted from 
disclosure by applicable State and Federal law. Nothing in this email shall 
create any legal binding agreement between the parties unless expressly stated 
herein and provided by an authorized representative of Comtech 
Telecommunications Corp. or its subsidiaries. If you are not the intended 
recipient of this message, be advised that any dissemination, distribution, or 
use of the contents of this message is strictly prohibited. If you received 
this message in error, please notify us immediately by return email and 
permanently delete all copies of the original email and any attached 
documentation from any computer or other media.



___

Users mailing list

Users@lists.opensips.org

Re: [OpenSIPS-Users] Modify the headers after executing a MI function in B2B_LOGIC module

[Bogdan-Andrei Iancu]

Hi Li,

All SIP requests generated by `b2b_bridge` are to be visible in 
local_route. And on the contrary, the incoming (received) requests DO 
NOT trigger local route.


Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  https://www.opensips-solutions.com
OpenSIPS Summit 27-30 Sept 2022, Athens
  https://www.opensips.org/events/Summit-2022Athens/

On 8/24/22 4:34 PM, Li Cai wrote:


Hi Bogdan,

Yes, we have put the changes by calling remove_hf() and append_hf() in 
the ‘local_route’, those functions for new incoming INVITE but not the 
INVITE sent out by ‘b2b_bridge’.


Thanks,

Li

*From:*Bogdan-Andrei Iancu 
*Sent:* August 24, 2022 7:18 AM
*To:* OpenSIPS users mailling list ; Li Cai 

*Subject:* Re: [OpenSIPS-Users] Modify the headers after executing a 
MI function in B2B_LOGIC module


*WARNING: External Email: Exercise Caution*

Hi Li,

Have you tried to use the local_route in order to do custom changes on 
the outgoing requests generated by the B2B bridging ?


Best regards,

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

OpenSIPS Summit 27-30 Sept 2022, Athens
   https://www.opensips.org/events/Summit-2022Athens/  


On 8/23/22 10:34 PM, Li Cai wrote:

Hi,

I’m working on a change for a B2BUA based on OpenSIPs 2.4, but not
sure if the function is supported or if it has been supported in
the later versions.

We have used the MI command b2b_bridge to bridge existing calls
from one entity to another and it works, the scenario is the same
as expected. While besides this, we also need to modify one of the
headers of the INVITEs sending to the new destination in this
scenario,  our scripts in the opensips.cfg can’t take any effect.

Thanks,

Li

NOTICE TO RECIPIENT: This email, including attachments, may
contain information which is confidential, proprietary,
attorney-client privileged and / or controlled under U.S. export
laws and regulations and may be restricted from disclosure by
applicable State and Federal law. Nothing in this email shall
create any legal binding agreement between the parties unless
expressly stated herein and provided by an authorized
representative of Comtech Telecommunications Corp. or its
subsidiaries. If you are not the intended recipient of this
message, be advised that any dissemination, distribution, or use
of the contents of this message is strictly prohibited. If you
received this message in error, please notify us immediately by
return email and permanently delete all copies of the original
email and any attached documentation from any computer or other
media.

___

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] Need some clarification in opensips cachedb_mongo db configutaion .

[Sasmita Panda]

What exactly do I have?

I have a global cluster of DocumentDB (AWS service ) which is mongodb
compatible .

In the global cluster , the primary cluster is in us-east and the secondary
cluster is in us-west .

I have 2 connection strings for both clusters , primary.xyz.com pointed to
primary cluster , secondary.xyz.com pointed to secondary cluster (secondary
cluster only has read replicas) .

In opensips I have given both the domains like below .

modparam("usrloc",
"cachedb_url","mongodb//docdb:cccl0g1c@*primary.xyz.com:27017
*,*secondary.xyz.com:27017
*
/opensipsDB.userlocation?&readPreference=secondaryPreferred&retryWrites=false")

whenever my primary cluster goes down and secondary is promoted to
primary , opensips throws an error of connection loss . Opensips at that
point also trying to connect to the *primary.xyz.com
 *although that is down* .  *

*At this point , my expectation was , opensips must have automatically
detect the the older primary cluster was down and secondary was became
primary and work properly . *

*But its not happening . Once I restart the service its works fine . *






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


On Wed, Aug 24, 2022 at 3:30 PM Liviu Chircu  wrote:

> On 24.08.2022 11:56, Sasmita Panda wrote:
>
>
> Now my primary cluster goes down so my secondary cluster becomes primary .
> I have updated the connection string against the domain in route53 . Now
> *primary-cluster.xzy.com * is pointed to
> the new primary custer connection string .
>
> While creating a connection from the console through the mongo shell it's
> getting connected . But opensips is not able to switch the connecting
> string somehow . still it's trying to connect to the previous primary
> connection string .
>
> It seems like opensips has cached the connection string and is trying to
> connect to the same even after I have updated the string from the backend .
>
> libmongo will try each node in your CSV of nodes, there is no going around
> this.  Now, while your usage of two completely different clusters in the
> same connection string seems to be *non-conventional* (I don't recall any
> documentation advising this, all Mongo docs talk about connecting to either
> a *replica set*, or to a *list of* *mongos* servers), I still think it
> could work.  Maybe just configure the "connectionTimeousMS" parameters (or
> others??) and see if you can get libmongoc to time out faster on your 1st
> cluster, when it goes down.
>
> Best regards,
>
> --
> Liviu Chircuwww.twitter.com/liviuchircu | www.opensips-solutions.com
> OpenSIPS Summit 2022 Athens, Sep 27-30 | www.opensips.org/events
>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Modify the headers after executing a MI function in B2B_LOGIC module

[Li Cai]

Hi Bogdan,

Yes, we have put the changes by calling remove_hf() and append_hf() in the 
'local_route', those functions for new incoming INVITE but not the INVITE sent 
out by 'b2b_bridge'.


Thanks,
Li

From: Bogdan-Andrei Iancu 
Sent: August 24, 2022 7:18 AM
To: OpenSIPS users mailling list ; Li Cai 

Subject: Re: [OpenSIPS-Users] Modify the headers after executing a MI function 
in B2B_LOGIC module


WARNING: External Email: Exercise Caution

Hi Li,

Have you tried to use the local_route in order to do custom changes on the 
outgoing requests generated by the B2B bridging ?

Best regards,


Bogdan-Andrei Iancu



OpenSIPS Founder and Developer

  
https://www.opensips-solutions.com

OpenSIPS Summit 27-30 Sept 2022, Athens

  
https://www.opensips.org/events/Summit-2022Athens/
On 8/23/22 10:34 PM, Li Cai wrote:
Hi,

I'm working on a change for a B2BUA based on OpenSIPs 2.4, but not sure if the 
function is supported or if it has been supported in the later versions.

We have used the MI command b2b_bridge to bridge existing calls from one entity 
to another and it works, the scenario is the same as expected. While besides 
this, we also need to modify one of the headers of the INVITEs sending to the 
new destination in this scenario,  our scripts in the opensips.cfg can't take 
any effect.


Thanks,
Li
NOTICE TO RECIPIENT: This email, including attachments, may contain information 
which is confidential, proprietary, attorney-client privileged and / or 
controlled under U.S. export laws and regulations and may be restricted from 
disclosure by applicable State and Federal law. Nothing in this email shall 
create any legal binding agreement between the parties unless expressly stated 
herein and provided by an authorized representative of Comtech 
Telecommunications Corp. or its subsidiaries. If you are not the intended 
recipient of this message, be advised that any dissemination, distribution, or 
use of the contents of this message is strictly prohibited. If you received 
this message in error, please notify us immediately by return email and 
permanently delete all copies of the original email and any attached 
documentation from any computer or other media.


___

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-cli debian 11

[johan]

that worked, thank you razvan.

On 24/08/2022 13:17, Răzvan Crainea wrote:
> Hi, Johan!
>
> Are you trying to install on Debian 11 or on Ubuntu 22?
> Because I see that the sources list is jammy, but then you are
> fetching bullseye.
>
> Best regards,
>
> Răzvan Crainea
> OpenSIPS Core Developer
> http://www.opensips-solutions.com
>
> On 8/24/22 13:42, johan wrote:
>> the old repo gives errors on bullseye.
>>
>> root@sipp:/etc/apt/sources.list.d# apt install opensips-cli
>> Reading package lists... Done
>> Building dependency tree... Done
>> Reading state information... Done
>> The following additional packages will be installed:
>>    libpq5 python-babel-localedata python3-anyjson python3-arrow
>> python3-babel
>>    python3-cffi python3-cffi-backend python3-cryptography
>> python3-dateutil
>>    python3-infinity python3-mysqldb python3-openssl python3-ply
>>    python3-psycopg2cffi python3-pycparser python3-pymysql
>> python3-sqlalchemy
>>    python3-sqlalchemy-ext python3-sqlalchemy-utils python3-tz
>> Suggested packages:
>>    python-arrow-doc python-cryptography-doc python3-cryptography-vectors
>>    python3-mysqldb-dbg python-openssl-doc python3-openssl-dbg
>> python-ply-doc
>>    python-pymysql-doc python-sqlalchemy-doc python3-fdb python3-pymssql
>>    python3-psycopg2 python-sqlalchemy-utils-doc
>> The following NEW packages will be installed:
>>    libpq5 opensips-cli python-babel-localedata python3-anyjson
>> python3-arrow
>>    python3-babel python3-cffi python3-cffi-backend python3-cryptography
>>    python3-dateutil python3-infinity python3-mysqldb python3-openssl
>>    python3-ply python3-psycopg2cffi python3-pycparser python3-pymysql
>>    python3-sqlalchemy python3-sqlalchemy-ext python3-sqlalchemy-utils
>>    python3-tz
>> 0 upgraded, 21 newly installed, 0 to remove and 0 not upgraded.
>> Need to get 7,133 kB of archives.
>> After this operation, 38.5 MB of additional disk space will be used.
>> Do you want to continue? [Y/n] y
>> Get:1 http://deb.debian.org/debian bullseye/main amd64 libpq5 amd64
>> 13.7-0+deb11u1 [180 kB]
>> Get:2 http://deb.debian.org/debian bullseye/main amd64
>> python3-sqlalchemy all 1.3.22+ds1-1 [795 kB]
>> Get:3 https://apt.opensips.org jammy/cli-nightly amd64 opensips-cli all
>> 0.1~20220822~a480e53-1 [41.3 kB]
>> Get:4 http://deb.debian.org/debian bullseye/main amd64 python3-anyjson
>> all 0.3.3-2 [8,196 B]
>> Get:5 http://deb.debian.org/debian bullseye/main amd64 python3-dateutil
>> all 2.8.1-6 [79.2 kB]
>> Get:6 http://deb.debian.org/debian bullseye/main amd64 python3-arrow all
>> 0.17.0-1 [50.7 kB]
>> Get:7 http://deb.debian.org/debian bullseye/main amd64
>> python-babel-localedata all 2.8.0+dfsg.1-7 [4,997 kB]
>> Get:8 http://deb.debian.org/debian bullseye/main amd64 python3-tz all
>> 2021.1-1 [34.8 kB]
>> Get:9 http://deb.debian.org/debian bullseye/main amd64 python3-babel all
>> 2.8.0+dfsg.1-7 [100 kB]
>> Get:10 http://deb.debian.org/debian bullseye/main amd64 python3-infinity
>> all 1.5-2 [4,364 B]
>> Get:11 http://deb.debian.org/debian bullseye/main amd64
>> python3-cffi-backend amd64 1.14.5-1 [85.8 kB]
>> Get:12 http://deb.debian.org/debian bullseye/main amd64 python3-ply all
>> 3.11-4 [65.5 kB]
>> Get:13 http://deb.debian.org/debian bullseye/main amd64
>> python3-pycparser all 2.20-3 [74.5 kB]
>> Get:14 http://deb.debian.org/debian bullseye/main amd64 python3-cffi all
>> 1.14.5-1 [87.9 kB]
>> Get:15 http://deb.debian.org/debian bullseye/main amd64
>> python3-psycopg2cffi amd64 2.8.1-2 [64.1 kB]
>> Get:16 http://deb.debian.org/debian bullseye/main amd64
>> python3-sqlalchemy-utils all 0.36.8-4 [66.6 kB]
>> Get:17 http://deb.debian.org/debian bullseye/main amd64
>> python3-cryptography amd64 3.3.2-1 [223 kB]
>> Get:18 http://deb.debian.org/debian bullseye/main amd64 python3-openssl
>> all 20.0.1-1 [53.7 kB]
>> Get:19 http://deb.debian.org/debian bullseye/main amd64 python3-mysqldb
>> amd64 1.4.4-2+b3 [57.0 kB]
>> Get:20 http://deb.debian.org/debian bullseye/main amd64 python3-pymysql
>> all 0.9.3-2 [43.4 kB]
>> Get:21 http://deb.debian.org/debian bullseye/main amd64
>> python3-sqlalchemy-ext amd64 1.3.22+ds1-1 [19.9 kB]
>> Fetched 7,133 kB in 14s (519
>> kB/s)
>> Selecting previously unselected package libpq5:amd64.
>> (Reading database ... 163371 files and directories currently installed.)
>> Preparing to unpack .../00-libpq5_13.7-0+deb11u1_amd64.deb ...
>> Unpacking libpq5:amd64 (13.7-0+deb11u1) ...
>> Selecting previously unselected package python3-sqlalchemy.
>> Preparing to unpack .../01-python3-sqlalchemy_1.3.22+ds1-1_all.deb ...
>> Unpacking python3-sqlalchemy (1.3.22+ds1-1) ...
>> Selecting previously unselected package python3-anyjson.
>> Preparing to unpack .../02-python3-anyjson_0.3.3-2_all.deb ...
>> Unpacking python3-anyjson (0.3.3-2) ...
>> Selecting previously unselected package python3-dateutil.
>> Preparing to unpack .../03-python3-dateutil_2.8.1-6_all.deb ...
>> Unpacking python3-dateutil (2.8.1-6) ...
>> Selecting previously unselected

Re: [OpenSIPS-Users] opensips-cli debian 11

[Johan De Clercq]

Debian 11

Outlook voor iOS downloaden

Van: Users  namens Răzvan Crainea 

Verzonden: Wednesday, August 24, 2022 1:17:00 PM
Aan: users@lists.opensips.org 
Onderwerp: Re: [OpenSIPS-Users] opensips-cli debian 11

Hi, Johan!

Are you trying to install on Debian 11 or on Ubuntu 22?
Because I see that the sources list is jammy, but then you are fetching
bullseye.

Best regards,

Răzvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com

On 8/24/22 13:42, johan wrote:
> the old repo gives errors on bullseye.
>
> root@sipp:/etc/apt/sources.list.d# apt install opensips-cli
> Reading package lists... Done
> Building dependency tree... Done
> Reading state information... Done
> The following additional packages will be installed:
>libpq5 python-babel-localedata python3-anyjson python3-arrow python3-babel
>python3-cffi python3-cffi-backend python3-cryptography python3-dateutil
>python3-infinity python3-mysqldb python3-openssl python3-ply
>python3-psycopg2cffi python3-pycparser python3-pymysql python3-sqlalchemy
>python3-sqlalchemy-ext python3-sqlalchemy-utils python3-tz
> Suggested packages:
>python-arrow-doc python-cryptography-doc python3-cryptography-vectors
>python3-mysqldb-dbg python-openssl-doc python3-openssl-dbg python-ply-doc
>python-pymysql-doc python-sqlalchemy-doc python3-fdb python3-pymssql
>python3-psycopg2 python-sqlalchemy-utils-doc
> The following NEW packages will be installed:
>libpq5 opensips-cli python-babel-localedata python3-anyjson python3-arrow
>python3-babel python3-cffi python3-cffi-backend python3-cryptography
>python3-dateutil python3-infinity python3-mysqldb python3-openssl
>python3-ply python3-psycopg2cffi python3-pycparser python3-pymysql
>python3-sqlalchemy python3-sqlalchemy-ext python3-sqlalchemy-utils
>python3-tz
> 0 upgraded, 21 newly installed, 0 to remove and 0 not upgraded.
> Need to get 7,133 kB of archives.
> After this operation, 38.5 MB of additional disk space will be used.
> Do you want to continue? [Y/n] y
> Get:1 http://deb.debian.org/debian bullseye/main amd64 libpq5 amd64
> 13.7-0+deb11u1 [180 kB]
> Get:2 http://deb.debian.org/debian bullseye/main amd64
> python3-sqlalchemy all 1.3.22+ds1-1 [795 kB]
> Get:3 https://apt.opensips.org jammy/cli-nightly amd64 opensips-cli all
> 0.1~20220822~a480e53-1 [41.3 kB]
> Get:4 http://deb.debian.org/debian bullseye/main amd64 python3-anyjson
> all 0.3.3-2 [8,196 B]
> Get:5 http://deb.debian.org/debian bullseye/main amd64 python3-dateutil
> all 2.8.1-6 [79.2 kB]
> Get:6 http://deb.debian.org/debian bullseye/main amd64 python3-arrow all
> 0.17.0-1 [50.7 kB]
> Get:7 http://deb.debian.org/debian bullseye/main amd64
> python-babel-localedata all 2.8.0+dfsg.1-7 [4,997 kB]
> Get:8 http://deb.debian.org/debian bullseye/main amd64 python3-tz all
> 2021.1-1 [34.8 kB]
> Get:9 http://deb.debian.org/debian bullseye/main amd64 python3-babel all
> 2.8.0+dfsg.1-7 [100 kB]
> Get:10 http://deb.debian.org/debian bullseye/main amd64 python3-infinity
> all 1.5-2 [4,364 B]
> Get:11 http://deb.debian.org/debian bullseye/main amd64
> python3-cffi-backend amd64 1.14.5-1 [85.8 kB]
> Get:12 http://deb.debian.org/debian bullseye/main amd64 python3-ply all
> 3.11-4 [65.5 kB]
> Get:13 http://deb.debian.org/debian bullseye/main amd64
> python3-pycparser all 2.20-3 [74.5 kB]
> Get:14 http://deb.debian.org/debian bullseye/main amd64 python3-cffi all
> 1.14.5-1 [87.9 kB]
> Get:15 http://deb.debian.org/debian bullseye/main amd64
> python3-psycopg2cffi amd64 2.8.1-2 [64.1 kB]
> Get:16 http://deb.debian.org/debian bullseye/main amd64
> python3-sqlalchemy-utils all 0.36.8-4 [66.6 kB]
> Get:17 http://deb.debian.org/debian bullseye/main amd64
> python3-cryptography amd64 3.3.2-1 [223 kB]
> Get:18 http://deb.debian.org/debian bullseye/main amd64 python3-openssl
> all 20.0.1-1 [53.7 kB]
> Get:19 http://deb.debian.org/debian bullseye/main amd64 python3-mysqldb
> amd64 1.4.4-2+b3 [57.0 kB]
> Get:20 http://deb.debian.org/debian bullseye/main amd64 python3-pymysql
> all 0.9.3-2 [43.4 kB]
> Get:21 http://deb.debian.org/debian bullseye/main amd64
> python3-sqlalchemy-ext amd64 1.3.22+ds1-1 [19.9 kB]
> Fetched 7,133 kB in 14s (519
> kB/s)
> Selecting previously unselected package libpq5:amd64.
> (Reading database ... 163371 files and directories currently installed.)
> Preparing to unpack .../00-libpq5_13.7-0+deb11u1_amd64.deb ...
> Unpacking libpq5:amd64 (13.7-0+deb11u1) ...
> Selecting previously unselected package python3-sqlalchemy.
> Preparing to unpack .../01-python3-sqlalchemy_1.3.22+ds1-1_all.deb ...
> Unpacking python3-sqlalchemy (1.3.22+ds1-1) ...
> Selecting previously unselected package python3-anyjson.
> Preparing to unpack .../02-python3-anyjson_0.3.3-2_all.deb ...
> Unpacking python3-anyjson (0.3.3-2) ...
> Selecting previously unselected package python3-dateutil.
> Preparing to unpack .../03-python3-dateutil_2.8.1-6_all.deb ...
> Unpac

Re: [OpenSIPS-Users] Dispatcher within a K8s environment

[Bogdan-Andrei Iancu]

Hi Jonathan,

I guess this will be a good topic (DS and K8S) for the OpenSIPS Summit 
in Athens - I think this is the 3rd time in the last week coming across 
it :)


Unfortunately there is no way to skip at the moment that DNS failure 
when loading the destinations :(even more, there some code that 
relies on the fact that there is an "IP" attached to any 
destination.And I just checked, a local error in sending the ping 
(like the DNS err) does not results in marking the destination as failed 
or so. so it is not so straight as ignoring the DNS error.


Best regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  https://www.opensips-solutions.com
OpenSIPS Summit 27-30 Sept 2022, Athens
  https://www.opensips.org/events/Summit-2022Athens/

On 8/24/22 12:24 AM, Jonathan Hunter wrote:


Hi All,

I have a query around dispatcher behaviour, I am running 3.2 in a k8s 
environment.


I have 2 freeswitch instances defined in a destination set, both of 
which are pods.


As people may be aware its fun implementing in k8s as pods can restart 
and disappear at times so I ideally want this reflected in the cache 
and output of opensips-cli -x mi ds_list where I was hoping the 
freeswitch entries would be defined but with a state of probing or 
inactive.


With my current setup, when restarting opensips for example, I have 
the dispatcher table populated in postgres db , and if opensips cant 
resolve the URI it wont load it into cache, like wise if opensips is 
running and freeswitch pod drops, I see this in the logs;


Aug 23 21:22:01 [55] ERROR:dispatcher:add_dest2list: could not resolve 
freeswitch-opensips-deployment-1.freeswitch-opensips, skipping it


Aug 23 21:22:01 [55] WARNING:dispatcher:ds_load_data: failed to add 
destination 
 
in group 10


I therefore don’t see it listed in cache when I run ds_list.

Does anyone know if its possible to tweak dispatcher to always load 
the database entries into cache at startup, and also set their status 
to probing/inactive if not reachable due to a resolving issue as above?


My dispatcher settings are;

 Dynamic routing

loadmodule "dispatcher.so"

modparam("dispatcher", "db_url", "postgres://x.x.x.x/opensips")

modparam("dispatcher", "ds_probing_mode", 1)

modparam("dispatcher", "ds_probing_threshhold", 1)

modparam("dispatcher", "persistent_state", 0)

modparam("dispatcher", "ds_ping_interval", 5)

modparam("dispatcher", "table_name", "dispatcher")

modparam("dispatcher", "cluster_id", 1)

Hope that makes sense!

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] Modify the headers after executing a MI function in B2B_LOGIC module

[Bogdan-Andrei Iancu]

Hi Li,

Have you tried to use the local_route in order to do custom changes on 
the outgoing requests generated by the B2B bridging ?


Best regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  https://www.opensips-solutions.com
OpenSIPS Summit 27-30 Sept 2022, Athens
  https://www.opensips.org/events/Summit-2022Athens/

On 8/23/22 10:34 PM, Li Cai wrote:


Hi,

I’m working on a change for a B2BUA based on OpenSIPs 2.4, but not 
sure if the function is supported or if it has been supported in the 
later versions.


We have used the MI command b2b_bridge to bridge existing calls from 
one entity to another and it works, the scenario is the same as 
expected. While besides this, we also need to modify one of the 
headers of the INVITEs sending to the new destination in this 
scenario,  our scripts in the opensips.cfg can’t take any effect.


Thanks,

Li

NOTICE TO RECIPIENT: This email, including attachments, may contain 
information which is confidential, proprietary, attorney-client 
privileged and / or controlled under U.S. export laws and regulations 
and may be restricted from disclosure by applicable State and Federal 
law. Nothing in this email shall create any legal binding agreement 
between the parties unless expressly stated herein and provided by an 
authorized representative of Comtech Telecommunications Corp. or its 
subsidiaries. If you are not the intended recipient of this message, 
be advised that any dissemination, distribution, or use of the 
contents of this message is strictly prohibited. If you received this 
message in error, please notify us immediately by return email and 
permanently delete all copies of the original email and any attached 
documentation from any computer or other media.


___
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-cli debian 11

[Răzvan Crainea]

Hi, Johan!

Are you trying to install on Debian 11 or on Ubuntu 22?
Because I see that the sources list is jammy, but then you are fetching 
bullseye.


Best regards,

Răzvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com

On 8/24/22 13:42, johan wrote:

the old repo gives errors on bullseye.

root@sipp:/etc/apt/sources.list.d# apt install opensips-cli
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
   libpq5 python-babel-localedata python3-anyjson python3-arrow python3-babel
   python3-cffi python3-cffi-backend python3-cryptography python3-dateutil
   python3-infinity python3-mysqldb python3-openssl python3-ply
   python3-psycopg2cffi python3-pycparser python3-pymysql python3-sqlalchemy
   python3-sqlalchemy-ext python3-sqlalchemy-utils python3-tz
Suggested packages:
   python-arrow-doc python-cryptography-doc python3-cryptography-vectors
   python3-mysqldb-dbg python-openssl-doc python3-openssl-dbg python-ply-doc
   python-pymysql-doc python-sqlalchemy-doc python3-fdb python3-pymssql
   python3-psycopg2 python-sqlalchemy-utils-doc
The following NEW packages will be installed:
   libpq5 opensips-cli python-babel-localedata python3-anyjson python3-arrow
   python3-babel python3-cffi python3-cffi-backend python3-cryptography
   python3-dateutil python3-infinity python3-mysqldb python3-openssl
   python3-ply python3-psycopg2cffi python3-pycparser python3-pymysql
   python3-sqlalchemy python3-sqlalchemy-ext python3-sqlalchemy-utils
   python3-tz
0 upgraded, 21 newly installed, 0 to remove and 0 not upgraded.
Need to get 7,133 kB of archives.
After this operation, 38.5 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://deb.debian.org/debian bullseye/main amd64 libpq5 amd64
13.7-0+deb11u1 [180 kB]
Get:2 http://deb.debian.org/debian bullseye/main amd64
python3-sqlalchemy all 1.3.22+ds1-1 [795 kB]
Get:3 https://apt.opensips.org jammy/cli-nightly amd64 opensips-cli all
0.1~20220822~a480e53-1 [41.3 kB]
Get:4 http://deb.debian.org/debian bullseye/main amd64 python3-anyjson
all 0.3.3-2 [8,196 B]
Get:5 http://deb.debian.org/debian bullseye/main amd64 python3-dateutil
all 2.8.1-6 [79.2 kB]
Get:6 http://deb.debian.org/debian bullseye/main amd64 python3-arrow all
0.17.0-1 [50.7 kB]
Get:7 http://deb.debian.org/debian bullseye/main amd64
python-babel-localedata all 2.8.0+dfsg.1-7 [4,997 kB]
Get:8 http://deb.debian.org/debian bullseye/main amd64 python3-tz all
2021.1-1 [34.8 kB]
Get:9 http://deb.debian.org/debian bullseye/main amd64 python3-babel all
2.8.0+dfsg.1-7 [100 kB]
Get:10 http://deb.debian.org/debian bullseye/main amd64 python3-infinity
all 1.5-2 [4,364 B]
Get:11 http://deb.debian.org/debian bullseye/main amd64
python3-cffi-backend amd64 1.14.5-1 [85.8 kB]
Get:12 http://deb.debian.org/debian bullseye/main amd64 python3-ply all
3.11-4 [65.5 kB]
Get:13 http://deb.debian.org/debian bullseye/main amd64
python3-pycparser all 2.20-3 [74.5 kB]
Get:14 http://deb.debian.org/debian bullseye/main amd64 python3-cffi all
1.14.5-1 [87.9 kB]
Get:15 http://deb.debian.org/debian bullseye/main amd64
python3-psycopg2cffi amd64 2.8.1-2 [64.1 kB]
Get:16 http://deb.debian.org/debian bullseye/main amd64
python3-sqlalchemy-utils all 0.36.8-4 [66.6 kB]
Get:17 http://deb.debian.org/debian bullseye/main amd64
python3-cryptography amd64 3.3.2-1 [223 kB]
Get:18 http://deb.debian.org/debian bullseye/main amd64 python3-openssl
all 20.0.1-1 [53.7 kB]
Get:19 http://deb.debian.org/debian bullseye/main amd64 python3-mysqldb
amd64 1.4.4-2+b3 [57.0 kB]
Get:20 http://deb.debian.org/debian bullseye/main amd64 python3-pymysql
all 0.9.3-2 [43.4 kB]
Get:21 http://deb.debian.org/debian bullseye/main amd64
python3-sqlalchemy-ext amd64 1.3.22+ds1-1 [19.9 kB]
Fetched 7,133 kB in 14s (519
kB/s)
Selecting previously unselected package libpq5:amd64.
(Reading database ... 163371 files and directories currently installed.)
Preparing to unpack .../00-libpq5_13.7-0+deb11u1_amd64.deb ...
Unpacking libpq5:amd64 (13.7-0+deb11u1) ...
Selecting previously unselected package python3-sqlalchemy.
Preparing to unpack .../01-python3-sqlalchemy_1.3.22+ds1-1_all.deb ...
Unpacking python3-sqlalchemy (1.3.22+ds1-1) ...
Selecting previously unselected package python3-anyjson.
Preparing to unpack .../02-python3-anyjson_0.3.3-2_all.deb ...
Unpacking python3-anyjson (0.3.3-2) ...
Selecting previously unselected package python3-dateutil.
Preparing to unpack .../03-python3-dateutil_2.8.1-6_all.deb ...
Unpacking python3-dateutil (2.8.1-6) ...
Selecting previously unselected package python3-arrow.
Preparing to unpack .../04-python3-arrow_0.17.0-1_all.deb ...
Unpacking python3-arrow (0.17.0-1) ...
Selecting previously unselected package python-babel-localedata.
Preparing to unpack
.../05-python-babel-localedata_2.8.0+dfsg.1-7_all.deb ...
Unpacking python-babel-localedata (2.8.0+dfsg.1-7) ...
Selecting previously unselected package py

Re: [OpenSIPS-Users] opensips-cli debian 11

[johan]

the old repo gives errors on bullseye.

root@sipp:/etc/apt/sources.list.d# apt install opensips-cli
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
  libpq5 python-babel-localedata python3-anyjson python3-arrow python3-babel
  python3-cffi python3-cffi-backend python3-cryptography python3-dateutil
  python3-infinity python3-mysqldb python3-openssl python3-ply
  python3-psycopg2cffi python3-pycparser python3-pymysql python3-sqlalchemy
  python3-sqlalchemy-ext python3-sqlalchemy-utils python3-tz
Suggested packages:
  python-arrow-doc python-cryptography-doc python3-cryptography-vectors
  python3-mysqldb-dbg python-openssl-doc python3-openssl-dbg python-ply-doc
  python-pymysql-doc python-sqlalchemy-doc python3-fdb python3-pymssql
  python3-psycopg2 python-sqlalchemy-utils-doc
The following NEW packages will be installed:
  libpq5 opensips-cli python-babel-localedata python3-anyjson python3-arrow
  python3-babel python3-cffi python3-cffi-backend python3-cryptography
  python3-dateutil python3-infinity python3-mysqldb python3-openssl
  python3-ply python3-psycopg2cffi python3-pycparser python3-pymysql
  python3-sqlalchemy python3-sqlalchemy-ext python3-sqlalchemy-utils
  python3-tz
0 upgraded, 21 newly installed, 0 to remove and 0 not upgraded.
Need to get 7,133 kB of archives.
After this operation, 38.5 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://deb.debian.org/debian bullseye/main amd64 libpq5 amd64
13.7-0+deb11u1 [180 kB]
Get:2 http://deb.debian.org/debian bullseye/main amd64
python3-sqlalchemy all 1.3.22+ds1-1 [795 kB]
Get:3 https://apt.opensips.org jammy/cli-nightly amd64 opensips-cli all
0.1~20220822~a480e53-1 [41.3 kB]
Get:4 http://deb.debian.org/debian bullseye/main amd64 python3-anyjson
all 0.3.3-2 [8,196 B]
Get:5 http://deb.debian.org/debian bullseye/main amd64 python3-dateutil
all 2.8.1-6 [79.2 kB]
Get:6 http://deb.debian.org/debian bullseye/main amd64 python3-arrow all
0.17.0-1 [50.7 kB]
Get:7 http://deb.debian.org/debian bullseye/main amd64
python-babel-localedata all 2.8.0+dfsg.1-7 [4,997 kB]
Get:8 http://deb.debian.org/debian bullseye/main amd64 python3-tz all
2021.1-1 [34.8 kB]
Get:9 http://deb.debian.org/debian bullseye/main amd64 python3-babel all
2.8.0+dfsg.1-7 [100 kB]
Get:10 http://deb.debian.org/debian bullseye/main amd64 python3-infinity
all 1.5-2 [4,364 B]
Get:11 http://deb.debian.org/debian bullseye/main amd64
python3-cffi-backend amd64 1.14.5-1 [85.8 kB]
Get:12 http://deb.debian.org/debian bullseye/main amd64 python3-ply all
3.11-4 [65.5 kB]
Get:13 http://deb.debian.org/debian bullseye/main amd64
python3-pycparser all 2.20-3 [74.5 kB]
Get:14 http://deb.debian.org/debian bullseye/main amd64 python3-cffi all
1.14.5-1 [87.9 kB]
Get:15 http://deb.debian.org/debian bullseye/main amd64
python3-psycopg2cffi amd64 2.8.1-2 [64.1 kB]
Get:16 http://deb.debian.org/debian bullseye/main amd64
python3-sqlalchemy-utils all 0.36.8-4 [66.6 kB]
Get:17 http://deb.debian.org/debian bullseye/main amd64
python3-cryptography amd64 3.3.2-1 [223 kB]
Get:18 http://deb.debian.org/debian bullseye/main amd64 python3-openssl
all 20.0.1-1 [53.7 kB]
Get:19 http://deb.debian.org/debian bullseye/main amd64 python3-mysqldb
amd64 1.4.4-2+b3 [57.0 kB]
Get:20 http://deb.debian.org/debian bullseye/main amd64 python3-pymysql
all 0.9.3-2 [43.4 kB]
Get:21 http://deb.debian.org/debian bullseye/main amd64
python3-sqlalchemy-ext amd64 1.3.22+ds1-1 [19.9 kB]
Fetched 7,133 kB in 14s (519
kB/s)     
Selecting previously unselected package libpq5:amd64.
(Reading database ... 163371 files and directories currently installed.)
Preparing to unpack .../00-libpq5_13.7-0+deb11u1_amd64.deb ...
Unpacking libpq5:amd64 (13.7-0+deb11u1) ...
Selecting previously unselected package python3-sqlalchemy.
Preparing to unpack .../01-python3-sqlalchemy_1.3.22+ds1-1_all.deb ...
Unpacking python3-sqlalchemy (1.3.22+ds1-1) ...
Selecting previously unselected package python3-anyjson.
Preparing to unpack .../02-python3-anyjson_0.3.3-2_all.deb ...
Unpacking python3-anyjson (0.3.3-2) ...
Selecting previously unselected package python3-dateutil.
Preparing to unpack .../03-python3-dateutil_2.8.1-6_all.deb ...
Unpacking python3-dateutil (2.8.1-6) ...
Selecting previously unselected package python3-arrow.
Preparing to unpack .../04-python3-arrow_0.17.0-1_all.deb ...
Unpacking python3-arrow (0.17.0-1) ...
Selecting previously unselected package python-babel-localedata.
Preparing to unpack
.../05-python-babel-localedata_2.8.0+dfsg.1-7_all.deb ...
Unpacking python-babel-localedata (2.8.0+dfsg.1-7) ...
Selecting previously unselected package python3-tz.
Preparing to unpack .../06-python3-tz_2021.1-1_all.deb ...
Unpacking python3-tz (2021.1-1) ...
Selecting previously unselected package python3-babel.
Preparing to unpack .../07-python3-babel_2.8.0+dfsg.1-7_all.deb ...
Unpacking python3

[OpenSIPS-Users] opensips-cli debian 11

[johan]

Liviu,

is there already a repo for opensips-cli on debian 11 ?


Secondly, if the old repo would work on debian 11, can  you please put a
pub key ?

Get:4 https://apt.opensips.org jammy InRelease [21.9 kB]
Err:4 https://apt.opensips.org jammy InRelease
  The following signatures couldn't be verified because the public key
is not available: NO_PUBKEY 81CE21E7049AD65B
Reading package lists... Done
W: GPG error: https://apt.opensips.org jammy InRelease: The following
signatures couldn't be verified because the public key is not available:
NO_PUBKEY 81CE21E7049AD65B
E: The repository 'https://apt.opensips.org jammy InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is
therefore disabled by default.

wkr,

wkr,


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

Re: [OpenSIPS-Users] Need some clarification in opensips cachedb_mongo db configutaion .

[Liviu Chircu]

On 24.08.2022 11:56, Sasmita Panda wrote:


Now my primary cluster goes down so my secondary cluster becomes 
primary . I have updated the connection string against the domain in 
route53 . Now
*primary-cluster.xzy.com * is pointed 
to the new primary custer connection string .


While creating a connection from the console through the mongo shell 
it's getting connected . But opensips is not able to switch the 
connecting string somehow . still it's trying to connect to the 
previous primary connection string .


It seems like opensips has cached the connection string and is trying 
to connect to the same even after I have updated the string from the 
backend .


libmongo will try each node in your CSV of nodes, there is no going 
around this.  Now, while your usage of two completely different clusters 
in the same connection string seems to be *non-conventional* (I don't 
recall any documentation advising this, all Mongo docs talk about 
connecting to either a *replica set*, or to a *list of* *mongos* 
servers), I still think it could work.  Maybe just configure the 
"connectionTimeousMS" parameters (or others??) and see if you can get 
libmongoc to time out faster on your 1st cluster, when it goes down.


Best regards,

--
Liviu Chircu
www.twitter.com/liviuchircu  |www.opensips-solutions.com
OpenSIPS Summit 2022 Athens, Sep 27-30 |www.opensips.org/events
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Need some clarification in opensips cachedb_mongo db configutaion .

[Sasmita Panda]

Hi Liviu ,

I have mapped a domain in AWS route53 primary-clsuter.xyz.com to mongodb
primary cluster connection string  .

Now my primary cluster goes down so my secondary cluster becomes primary .
I have updated the connection string against the domain in route53 . Now
*primary-cluster.xzy.com * is pointed to
the new primary custer connection string .

While creating a connection from the console through the mongo shell it's
getting connected . But opensips is not able to switch the connecting
string somehow . still it's trying to connect to the previous primary
connection string .

It seems like opensips has cached the connection string and is trying to
connect to the same even after I have updated the string from the backend .

Once I restart the opensips service everything starts working and the
connection string was updated to the latest primary cluster connection
string .


How will I manage this ?


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


On Tue, Aug 23, 2022 at 3:31 PM Liviu Chircu  wrote:

> On 22.08.2022 08:44, Sasmita Panda wrote:
> >
> > When I am configuring 2 connectionstrings here , that means
> > 1. Opensips will always honor the 1st one as primary and 2nd one as
> > secondary ?
> >
> > 2. If the 1st one will get down and 2nd one becomes primary , what
> > will happen to opensips ? Will that keep the 2nd one as primary
> > automatically or I have to switch the domain in the config ?
> >
> > 3. How does opensips decide which one is primary and which is secondary ?
> >
> > Please help me out . I am stuck in the middle of something here .
>
> Hi Sasmita,
>
> This has more to do with the libmongoc library behavior, rather than
> OpenSIPS.  First, the multi-host replica set syntax is part of the
> MongoDB connection string syntax[1], so everything that you can read on
> the Mongo website also applies to the "cachedb_mongodb" module.
>
> 1. This means that once you include the "replicaSet=rs0" component, the
> library will automatically establish who is the PRIMARY node on each
> query.  If the PRIMARY should ever change (either due to system failure,
> manual switch, etc.), the library will be able to switch to the new
> PRIMARY, whichever that may become (imagine you have a 5-node replica set).
>
> 2. no need to change the config string. The library will always know
> which is the PRIMARY (writer) node.
>
> 3. I cannot say... I image the library will connect to each node and run
> an "isMaster()"[2] command?  I suggest you do an ngrep or even a PCAP
> capture - that should give you more info on libmongoc behavior.
>
> [1]: https://www.mongodb.com/docs/v5.2/reference/connection-string/
> [2]: https://www.mongodb.com/docs/v4.2/reference/command/isMaster/
>
> Best regards,
>
> --
> Liviu Chircu
> www.twitter.com/liviuchircu | www.opensips-solutions.com
> OpenSIPS Summit 2022 Athens, Sep 27-30 | www.opensips.org/events
>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users