From social at bohboh.info  Fri Mar  1 00:32:30 2024
From: social at bohboh.info (Social Boh)
Date: Thu, 29 Feb 2024 19:32:30 -0500
Subject: [OpenSIPS-Users] Best way to call with prefix and trunks
In-Reply-To: <CAKrJzCw1=K=StqSL3bC_D_OvH2VH2QUU3xD+ZqZ0bN4OvR2OtA@mail.gmail.com>
References: <36ce99b7-67bd-401c-a5e3-668eda1c91e2@bohboh.info>
 <ded675dc-e9eb-4443-b12b-133c341b7f6f@bohboh.info>
 <CAKrJzCw1=K=StqSL3bC_D_OvH2VH2QUU3xD+ZqZ0bN4OvR2OtA@mail.gmail.com>
Message-ID: <9c26f051-75aa-4a02-9138-a9301562e2be@bohboh.info>

My idea for now is using DROYTUNG for all trunks because i have to work 
with prefix and priorities.

Then in failure route use *uac_auth* function for user password trunks

?

---
I'm SoCIaL, MayBe

El 29/02/2024 a las 6:30 p. m., Jehanzaib Younis escribió:
> Hi,
>
> You can use drouting for IP based authentication trunks.
> For username/password based i think you can use digest_auth somethin like
>
> digest_domain("MySIPTrunkRealm", "sip.trunk1.com 
> <http://sip.trunk1.com>", "username1", "password1")
> digest_domain("MySIPTrunkRealm", "sip.trunk2.com 
> <http://sip.trunk2.com>", "username2", "password2")
>
> in the routing you can do something like the following:-
>
> if (is_method("INVITE") && has_totag()) {
>          $var(dest_ip) = $si;
>          if (!digest_auth_check("$var(dest_ip)", "MySIPTrunkRealm", 
> "username", "password")) {
>             xlog("L_ERR", "Failed to authenticate call to 
> $var(dest_ip)\n");
>             sl_send_reply("403", "Forbidden");
>             exit;
>          }
>
>         # Route the call to the trunk
>         route(SOME_OTHER_ROUTE);
> }
>
>
> Regards,
> Jehanzaib
>
>
> On Fri, Mar 1, 2024 at 12:21 PM Social Boh <social at bohboh.info> wrote:
>
>     First reply;
>
>     UAC, UAC AUTH and DROUTING Modules
>
>     ?
>
>     ---
>     I'm SoCIaL, MayBe
>
>     El 29/02/2024 a las 4:05 p. m., Social Boh escribió:
>     > Hello list,
>     >
>     > I have to make calls to PSTN using trunks con IP auth y trunks with
>     > user and password
>     >
>     > I'd like use DROUTING module but I don't know how solve
>     user/password
>     > auth trunk
>     >
>     > Any idea?
>     >
>     > Thank you
>     >
>     > Regards
>     >
>
>     _______________________________________________
>     Users mailing list
>     Users at lists.opensips.org
>     http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240229/23368934/attachment.html>

From venefax at gmail.com  Sat Mar  2 00:57:13 2024
From: venefax at gmail.com (Saint Michael)
Date: Fri, 1 Mar 2024 19:57:13 -0500
Subject: [OpenSIPS-Users] possible big in unixodbc queries
Message-ID: <CAC9cSOAXgV1NuCK38sc4ot6JRRfayM2MDfkotS8+wfdzRRGUKA@mail.gmail.com>

whatever query I call, db_unixodbc_get_columns returns only db_int for
every field.
DBG:avpops:ops_dbquery_avps: query [CALL get_user_details(1)]
 DBG:core:db_new_result: allocate 48 bytes for result set at 0x71c49935ba20
 DBG:db_unixodbc:db_unixodbc_get_columns: 3 columns returned from the query
 DBG:core:db_allocate_columns: allocate 84 bytes for result columns at
0x71c49935ba88
 DBG:db_unixodbc:db_unixodbc_get_columns:
RES_NAMES(0x71c49935baa0)[0]=[username]
 DBG:db_unixodbc:db_unixodbc_get_columns: use DB_INT result type
 DBG:db_unixodbc:db_unixodbc_get_columns: RES_NAMES(0x71c49935bab0)[1]=[email]
 DBG:db_unixodbc:db_unixodbc_get_columns: use DB_INT result type
 DBG:db_unixodbc:db_unixodbc_get_columns: RES_NAMES(0x71c49935bac0)[2]=[phone]
 DBG:db_unixodbc:db_unixodbc_get_columns: use DB_INT result type
 DBG:core:db_allocate_rows: allocate 112 bytes for result rows and
values at 0x71c49935bb18
 DBG:db_unixodbc:db_unixodbc_str2val: converting INT [johndoe]
 ERROR:core:db_str2int: Unexpected characters: [johndoe]
 ERROR:db_unixodbc:db_unixodbc_str2val: converting integer value from
string failed
 ERROR:db_unixodbc:db_unixodbc_convert_row: failed to convert value

opensips -V
version: opensips 3.4.4 (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.
git revision: e50c6736e
main.c compiled on 00:29:53 Mar  2 2024 with gcc 9

dpkg -l | grep unixodbc
ri  unixodbc                         2.3.6-0.1build1
amd64        Basic ODBC tools
ri  unixodbc-dev:amd64               2.3.6-0.1build1
amd64        ODBC libraries for UNIX (development files)

odbc.ini

[opensips]
Description = MySQL ODBC Driver Testing
Driver = maria
Socket = /var/run/mysqld/mysqld.sock
#Server = localhost
User = xxxxx
Password = xxxx
Database = asterisk
Option = 3

odbcinst.ini

[maria]
Description=ODBC for MySQL
Driver=/usr/lib64/mariadb/libmaodbc.so
FileUsage=1
Threading=0

a Unixodbc trace shows that everything is normal,so the issue must be
with opensips
                    Statement = 0x6003034831b0
                        Column Number = 3
                        Target Type = 1 SQL_CHAR
                        Buffer Length = 1024
                        Target Value = 0x77a24e1ff318
                        StrLen Or Ind = 0x7ffc233ad5f0
[ODBC][103886][1709340852.301423][SQLGetData.c][545]
                Exit:[SQL_SUCCESS]
                        Buffer = [123-456-7890]
                        Strlen Or Ind = 0x7ffc233ad5f0 -> 1

as you can see, the target Type is SQL_CHAR

any ideas?


From bogdan at opensips.org  Mon Mar  4 15:44:44 2024
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Mon, 4 Mar 2024 17:44:44 +0200
Subject: [OpenSIPS-Users] [Blog] Launch Darkly integration with OpenSIPS 3.5
Message-ID: <d947b98f-ed89-4dfb-bd1f-7e492938f2b9@opensips.org>

Hi all,

Starting version 3.5 (current devel), OpenSIPS offers integration with 
Launch Darkly service for in-cloud features flag support

https://blog.opensips.org/2024/03/04/launchdarkly-integration-with-opensips-3-5/

Enjoy,

-- 
Bogdan-Andrei Iancu

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



From brett at nemeroff.com  Mon Mar  4 16:12:29 2024
From: brett at nemeroff.com (Brett Nemeroff)
Date: Mon, 4 Mar 2024 10:12:29 -0600
Subject: [OpenSIPS-Users] [Blog] Launch Darkly integration with OpenSIPS
	3.5
In-Reply-To: <d947b98f-ed89-4dfb-bd1f-7e492938f2b9@opensips.org>
References: <d947b98f-ed89-4dfb-bd1f-7e492938f2b9@opensips.org>
Message-ID: <CAPwC5wwSueUc+w27kGmg0yra+BfM-H-DHBpi_WmaaYB6MaDWRw@mail.gmail.com>

Woah, this is super cool. Thanks team for getting this in. I'm really
looking forward to seeing how people use this!!


On Mon, Mar 4, 2024 at 9:46 AM Bogdan-Andrei Iancu <bogdan at opensips.org>
wrote:

> Hi all,
>
> Starting version 3.5 (current devel), OpenSIPS offers integration with
> Launch Darkly service for in-cloud features flag support
>
>
> https://blog.opensips.org/2024/03/04/launchdarkly-integration-with-opensips-3-5/
>
> Enjoy,
>
> --
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>    https://www.opensips-solutions.com
>    https://www.siphub.com
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240304/25da10b2/attachment.html>

From stefan.carlsson at tetab.nu  Mon Mar  4 21:52:58 2024
From: stefan.carlsson at tetab.nu (Stefan Carlsson)
Date: Mon, 4 Mar 2024 21:52:58 +0000
Subject: [OpenSIPS-Users] Reset session timers via re-invite // update
Message-ID: <2370618bd1564cacac7dcc756c7c3ee8@tetab.nu>

Hi !

We have a problem regarding session timers.    One operator runs it via re-invite and the new one via update.

All our PBX's "inside" and UA's runs re-invite and we have the Opensips as a proxy that routes all the traffic to the right UA, Trunks.

So my question is,   is it even possibly to handle both types of session timers methods in Opensips if endpoints only handles re-invite

I've tested to send the update with all headers intact back to the operator but then I receive 481 unknown dialog.

I've tried to read the RFC 3311 but I can't find any examples that is so clear as re-invite ...  (tags)

Do I need to change/add some headervalues such as the did i've got in the 200 message after the invite to build  up
the complete Update response to the operator.

Please bear with me regarding with my "stupid" questions ...  understanding sip is really hard ......

// Regards ...

Stefan


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240304/45221f26/attachment.html>

From wadii at evenmedia.fr  Mon Mar  4 22:38:09 2024
From: wadii at evenmedia.fr (Wadii ELMAJDI | Evenmedia)
Date: Mon, 4 Mar 2024 22:38:09 +0000
Subject: [OpenSIPS-Users] =?windows-1252?q?RE=A0=3A_Reset_session_timers_v?=
	=?windows-1252?q?ia_re-invite_//_update?=
In-Reply-To: <2370618bd1564cacac7dcc756c7c3ee8@tetab.nu>
References: <2370618bd1564cacac7dcc756c7c3ee8@tetab.nu>
Message-ID: <MR1P264MB3585A89BBF57335AFE86DAADCE232@MR1P264MB3585.FRAP264.PROD.OUTLOOK.COM>

hi Stefan

your question is far from stupid

have you tried manipulating the SIP headers to influence the negotiation process between the provider and your PBX ?
you can do that by adjusting the Supported/Require headers in SIP messages within OpenSIPS to indicate that only re-INVITE is supported for session timers
this might prompt your new operator system to fallback to using re-INVITE instead of UPDATE
Additionally check if your PBX can be configured to prefer re-INVITEs

________________________________
De : Users <users-bounces at lists.opensips.org> de la part de Stefan Carlsson <stefan.carlsson at tetab.nu>
Envoyé : Monday, March 4, 2024 10:52:58 PM
À : users at lists.opensips.org <users at lists.opensips.org>
Objet : [OpenSIPS-Users] Reset session timers via re-invite // update


Hi !



We have a problem regarding session timers.    One operator runs it via re-invite and the new one via update.



All our PBX’s “inside” and UA’s runs re-invite and we have the Opensips as a proxy that routes all the traffic to the right UA, Trunks.



So my question is,   is it even possibly to handle both types of session timers methods in Opensips if endpoints only handles re-invite



I’ve tested to send the update with all headers intact back to the operator but then I receive 481 unknown dialog.



I’ve tried to read the RFC 3311 but I can’t find any examples that is so clear as re-invite …  (tags)



Do I need to change/add some headervalues such as the did i’ve got in the 200 message after the invite to build  up

the complete Update response to the operator.



Please bear with me regarding with my “stupid” questions …  understanding sip is really hard ……



// Regards …



Stefan




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240304/50391e73/attachment-0001.html>

From social at bohboh.info  Mon Mar  4 22:56:07 2024
From: social at bohboh.info (Social Boh)
Date: Mon, 4 Mar 2024 17:56:07 -0500
Subject: [OpenSIPS-Users] Reset session timers via re-invite // update
In-Reply-To: <MR1P264MB3585A89BBF57335AFE86DAADCE232@MR1P264MB3585.FRAP264.PROD.OUTLOOK.COM>
References: <2370618bd1564cacac7dcc756c7c3ee8@tetab.nu>
 <MR1P264MB3585A89BBF57335AFE86DAADCE232@MR1P264MB3585.FRAP264.PROD.OUTLOOK.COM>
Message-ID: <372dd808-fb7f-407b-84f5-c84fe64e6b59@bohboh.info>

recently I've had a similar problem with a customer and, if you don't 
need Session Timer, disable it eliminating the timer word in the 
Supported header.

Regards

---
I'm SoCIaL, MayBe

El 4/03/2024 a las 5:38 p. m., Wadii ELMAJDI | Evenmedia escribió:
>
> hi Stefan
>
> your question is far from stupid
>
> have you tried manipulating the SIP headers to influence the 
> negotiation process between the provider and your PBX ?
>
> you can do that by adjusting the Supported/Require headers in SIP 
> messages within OpenSIPS to indicate that only re-INVITE is supported 
> for session timers
>
> this might prompt your new operator system to fallback to using 
> re-INVITE instead of UPDATE
>
> Additionally check if your PBX can be configured to prefer re-INVITEs
>
> ------------------------------------------------------------------------
> *De :* Users <users-bounces at lists.opensips.org> de la part de Stefan 
> Carlsson <stefan.carlsson at tetab.nu>
> *Envoyé :* Monday, March 4, 2024 10:52:58 PM
> *À :* users at lists.opensips.org <users at lists.opensips.org>
> *Objet :* [OpenSIPS-Users] Reset session timers via re-invite // update
>
> Hi !
>
> We have a problem regarding session timers.    One operator runs it 
> via re-invite and the new one via update.
>
> All our PBX’s “inside” and UA’s runs re-invite and we have the 
> Opensips as a proxy that routes all the traffic to the right UA, Trunks.
>
> So my question is,   is it even possibly to handle both types of 
> session timers methods in Opensips if endpoints only handles re-invite
>
> I’ve tested to send the update with all headers intact back to the 
> operator but then I receive 481 unknown dialog.
>
> I’ve tried to read the RFC 3311 but I can’t find any examples that is 
> so clear as re-invite … (tags)
>
> Do I need to change/add some headervalues such as the did i’ve got in 
> the 200 message after the invite to build  up
>
> the complete Update response to the operator.
>
> Please bear with me regarding with my “stupid” questions …  
> understanding sip is really hard ……
>
> // Regards …
>
> Stefan
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240304/2f95b317/attachment.html>

From bogdan at opensips.org  Tue Mar  5 09:14:15 2024
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Tue, 5 Mar 2024 11:14:15 +0200
Subject: [OpenSIPS-Users] possible big in unixodbc queries
In-Reply-To: <CAC9cSOAXgV1NuCK38sc4ot6JRRfayM2MDfkotS8+wfdzRRGUKA@mail.gmail.com>
References: <CAC9cSOAXgV1NuCK38sc4ot6JRRfayM2MDfkotS8+wfdzRRGUKA@mail.gmail.com>
Message-ID: <e661ef8a-d2fa-4517-9ce5-644cc521631d@opensips.org>

The data type of the each column is provided by the unixodbc lib via the 
SQLDescribeCol() function.

I would rather suspect an issue between the unixodbc layer and the 
underlying DB.

Regards,

Bogdan-Andrei Iancu

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

On 02.03.2024 02:57, Saint Michael wrote:
> whatever query I call, db_unixodbc_get_columns returns only db_int for
> every field.
> DBG:avpops:ops_dbquery_avps: query [CALL get_user_details(1)]
>   DBG:core:db_new_result: allocate 48 bytes for result set at 0x71c49935ba20
>   DBG:db_unixodbc:db_unixodbc_get_columns: 3 columns returned from the query
>   DBG:core:db_allocate_columns: allocate 84 bytes for result columns at
> 0x71c49935ba88
>   DBG:db_unixodbc:db_unixodbc_get_columns:
> RES_NAMES(0x71c49935baa0)[0]=[username]
>   DBG:db_unixodbc:db_unixodbc_get_columns: use DB_INT result type
>   DBG:db_unixodbc:db_unixodbc_get_columns: RES_NAMES(0x71c49935bab0)[1]=[email]
>   DBG:db_unixodbc:db_unixodbc_get_columns: use DB_INT result type
>   DBG:db_unixodbc:db_unixodbc_get_columns: RES_NAMES(0x71c49935bac0)[2]=[phone]
>   DBG:db_unixodbc:db_unixodbc_get_columns: use DB_INT result type
>   DBG:core:db_allocate_rows: allocate 112 bytes for result rows and
> values at 0x71c49935bb18
>   DBG:db_unixodbc:db_unixodbc_str2val: converting INT [johndoe]
>   ERROR:core:db_str2int: Unexpected characters: [johndoe]
>   ERROR:db_unixodbc:db_unixodbc_str2val: converting integer value from
> string failed
>   ERROR:db_unixodbc:db_unixodbc_convert_row: failed to convert value
>
> opensips -V
> version: opensips 3.4.4 (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.
> git revision: e50c6736e
> main.c compiled on 00:29:53 Mar  2 2024 with gcc 9
>
> dpkg -l | grep unixodbc
> ri  unixodbc                         2.3.6-0.1build1
> amd64        Basic ODBC tools
> ri  unixodbc-dev:amd64               2.3.6-0.1build1
> amd64        ODBC libraries for UNIX (development files)
>
> odbc.ini
>
> [opensips]
> Description = MySQL ODBC Driver Testing
> Driver = maria
> Socket = /var/run/mysqld/mysqld.sock
> #Server = localhost
> User = xxxxx
> Password = xxxx
> Database = asterisk
> Option = 3
>
> odbcinst.ini
>
> [maria]
> Description=ODBC for MySQL
> Driver=/usr/lib64/mariadb/libmaodbc.so
> FileUsage=1
> Threading=0
>
> a Unixodbc trace shows that everything is normal,so the issue must be
> with opensips
>                      Statement = 0x6003034831b0
>                          Column Number = 3
>                          Target Type = 1 SQL_CHAR
>                          Buffer Length = 1024
>                          Target Value = 0x77a24e1ff318
>                          StrLen Or Ind = 0x7ffc233ad5f0
> [ODBC][103886][1709340852.301423][SQLGetData.c][545]
>                  Exit:[SQL_SUCCESS]
>                          Buffer = [123-456-7890]
>                          Strlen Or Ind = 0x7ffc233ad5f0 -> 1
>
> as you can see, the target Type is SQL_CHAR
>
> any ideas?
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users



From Calin.Dragan at garmin.com  Thu Mar  7 11:39:02 2024
From: Calin.Dragan at garmin.com (Dragan, Calin)
Date: Thu, 7 Mar 2024 11:39:02 +0000
Subject: [OpenSIPS-Users] Missing auth package in docker image
Message-ID: <BN8PR04MB5779EB091C7F5710B0F6BB21F3202@BN8PR04MB5779.namprd04.prod.outlook.com>

Hi,

I'm new to Opensips, so I started with the opensips/opensips docker image, version 3.4. I installed, configured it, the server is running just fine. My problem is that I try to set-up the db authentication, but the auth_db.so cannot be loaded because of the missing auth.so module. This doesn't exist in the docker image. The last image where I found the auth.so module was 3.2, but I tried it and it is not compatible with the 3.4 version. Is there a way to enable db authentication with the 3.4 build?

Thank you
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240307/b341ee63/attachment.html>

From liviu at opensips.org  Thu Mar  7 15:27:40 2024
From: liviu at opensips.org (Liviu Chircu)
Date: Thu, 7 Mar 2024 17:27:40 +0200
Subject: [OpenSIPS-Users] [Blog] Diameter Server Support for IMS Flows in
	OpenSIPS 3.5
Message-ID: <6e3d3834-f0ff-7a98-235b-22d0a6f3d8f6@opensips.org>

Hi all,

The OpenSIPS IMS support is shaping up, with the Diameter Server support 
now being available for alpha testing, on the development (master) branch.

As documentation, we have prepared:

* a wiki tutorial^[1] 
<https://www.opensips.org/Documentation/Tutorials-Diameter-Client-Server> 
on how to use it
* a blog post^[2] <https://blog.opensips.org/?p=9325&preview=true> with 
a more concrete example: processing Push-Profile-Requests (PPR) 
originated by the HSS to our P-CSCF

[1]: https://www.opensips.org/Documentation/Tutorials-Diameter-Client-Server
[2]: 
https://blog.opensips.org/2024/03/07/diameter-server-support-for-ims-flows-in-opensips-3-5/

Enjoy!

-- 
Liviu Chircu
www.twitter.com/liviuchircu  |www.opensips-solutions.com
OpenSIPS Summit 2024 May 14-17 Valencia |www.opensips.org/events
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240307/4978addf/attachment.html>

From razvan at opensips.org  Fri Mar  8 10:15:41 2024
From: razvan at opensips.org (=?UTF-8?Q?R=C4=83zvan_Crainea?=)
Date: Fri, 8 Mar 2024 12:15:41 +0200
Subject: [OpenSIPS-Users] Missing auth package in docker image
In-Reply-To: <BN8PR04MB5779EB091C7F5710B0F6BB21F3202@BN8PR04MB5779.namprd04.prod.outlook.com>
References: <BN8PR04MB5779EB091C7F5710B0F6BB21F3202@BN8PR04MB5779.namprd04.prod.outlook.com>
Message-ID: <2ec77d45-fcc8-41e8-8f57-3da56525c997@opensips.org>

Hi, Calin!

The stock/latest docker image does not come with any extra modules 
installed, it only comes with the opensips package, which should be 
enough for running the default opensips configuration.
  If I understand correctly, you also need the auth_db module, which is 
part of the opensips-auth-modules package, and most likely a database 
module as well.
Luckily, you have multiple choices to get this done:
* Install (i.e. using apt-get install opensips-auth-modules) the 
packages you need in the docker container you already started
* Build your own docker container [2] with the correct setting of the 
`OPENSIPS_EXTRA_MODULES` variable
* Use one of the sipssert images[3], which already includes the desired 
package, along with others[2].

[1] https://github.com/OpenSIPS/docker-opensips
[2] 
https://hub.docker.com/layers/opensips/opensips/sipssert-3.4/images/sha256-be41b1e7cbcd4bb8ce89f8055fc636dd57bd047a9992ff4b42adc75ad4066610?context=explore
[3] 
https://github.com/OpenSIPS/sipssert-opensips-tests/blob/3.4/.opensips.modules

Best regards,

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

On 3/7/24 13:39, Dragan, Calin via Users wrote:
> Hi,
> 
> I'm new to Opensips, so I started with the opensips/opensips docker image, version 3.4. I installed, configured it, the server is running just fine. My problem is that I try to set-up the db authentication, but the auth_db.so cannot be loaded because of the missing auth.so module. This doesn't exist in the docker image. The last image where I found the auth.so module was 3.2, but I tried it and it is not compatible with the 3.4 version. Is there a way to enable db authentication with the 3.4 build?
> 
> Thank you
> 
> 
> Hi,
> 
> I’m new to Opensips, so I started with the opensips/opensips docker 
> image, version 3.4. I installed, configured it, the server is running 
> just fine. My problem is that I try to set-up the db authentication, but 
> the auth_db.so cannot be loaded because of the missing auth.so module. 
> This doesn’t exist in the docker image. The last image where I found the 
> auth.so module was 3.2, but I tried it and it is not compatible with the 
> 3.4 version. Is there a way to enable db authentication with the 3.4 build?
> 
> Thank you
> 
> 
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users


From Calin.Dragan at garmin.com  Fri Mar  8 10:34:19 2024
From: Calin.Dragan at garmin.com (Dragan, Calin)
Date: Fri, 8 Mar 2024 10:34:19 +0000
Subject: [OpenSIPS-Users] Missing auth package in docker image
In-Reply-To: <2ec77d45-fcc8-41e8-8f57-3da56525c997@opensips.org>
References: <BN8PR04MB5779EB091C7F5710B0F6BB21F3202@BN8PR04MB5779.namprd04.prod.outlook.com>
 <2ec77d45-fcc8-41e8-8f57-3da56525c997@opensips.org>
Message-ID: <BN8PR04MB577976F24E2A4D3D4C0E6B42F3272@BN8PR04MB5779.namprd04.prod.outlook.com>

Hi Razvan

Thank you! Installing the missing modules worked like a charm, I just didn’t know where to install them from.

Regards,
Calin

From: Users <users-bounces at lists.opensips.org> On Behalf Of Razvan Crainea
Sent: Friday, March 08, 2024 12:16 PM
To: users at lists.opensips.org
Subject: Re: [OpenSIPS-Users] Missing auth package in docker image

Hi, Calin! The stock/latest docker image does not come with any extra modules installed, it only comes with the opensips package, which should be enough for running the default opensips configuration. If I understand correctly, you also need


Hi, Calin!



The stock/latest docker image does not come with any extra modules

installed, it only comes with the opensips package, which should be

enough for running the default opensips configuration.

  If I understand correctly, you also need the auth_db module, which is

part of the opensips-auth-modules package, and most likely a database

module as well.

Luckily, you have multiple choices to get this done:

* Install (i.e. using apt-get install opensips-auth-modules) the

packages you need in the docker container you already started

* Build your own docker container [2] with the correct setting of the

`OPENSIPS_EXTRA_MODULES` variable

* Use one of the sipssert images[3], which already includes the desired

package, along with others[2].



[1] https://urldefense.com/v3/__https://github.com/OpenSIPS/docker-opensips__;!!EJc4YC3iFmQ!XbjfVzm_t84z0dh8Q9xdosVyOiogt_i7sHVGyQHdHtOIbmWQ5giucNn_NeCOhaB8bBl04p9ZS_hnTW6o4A$<https://urldefense.com/v3/__https:/github.com/OpenSIPS/docker-opensips__;!!EJc4YC3iFmQ!XbjfVzm_t84z0dh8Q9xdosVyOiogt_i7sHVGyQHdHtOIbmWQ5giucNn_NeCOhaB8bBl04p9ZS_hnTW6o4A$>

[2]

https://urldefense.com/v3/__https://hub.docker.com/layers/opensips/opensips/sipssert-3.4/images/sha256-be41b1e7cbcd4bb8ce89f8055fc636dd57bd047a9992ff4b42adc75ad4066610?context=explore__;!!EJc4YC3iFmQ!XbjfVzm_t84z0dh8Q9xdosVyOiogt_i7sHVGyQHdHtOIbmWQ5giucNn_NeCOhaB8bBl04p9ZS_gP1eygJg$<https://urldefense.com/v3/__https:/hub.docker.com/layers/opensips/opensips/sipssert-3.4/images/sha256-be41b1e7cbcd4bb8ce89f8055fc636dd57bd047a9992ff4b42adc75ad4066610?context=explore__;!!EJc4YC3iFmQ!XbjfVzm_t84z0dh8Q9xdosVyOiogt_i7sHVGyQHdHtOIbmWQ5giucNn_NeCOhaB8bBl04p9ZS_gP1eygJg$>

[3]

https://urldefense.com/v3/__https://github.com/OpenSIPS/sipssert-opensips-tests/blob/3.4/.opensips.modules__;!!EJc4YC3iFmQ!XbjfVzm_t84z0dh8Q9xdosVyOiogt_i7sHVGyQHdHtOIbmWQ5giucNn_NeCOhaB8bBl04p9ZS_hjt66IaA$<https://urldefense.com/v3/__https:/github.com/OpenSIPS/sipssert-opensips-tests/blob/3.4/.opensips.modules__;!!EJc4YC3iFmQ!XbjfVzm_t84z0dh8Q9xdosVyOiogt_i7sHVGyQHdHtOIbmWQ5giucNn_NeCOhaB8bBl04p9ZS_hjt66IaA$>



Best regards,



Răzvan Crainea

OpenSIPS Core Developer / SIPhub CTO

https://urldefense.com/v3/__http://www.opensips-solutions.com__;!!EJc4YC3iFmQ!XbjfVzm_t84z0dh8Q9xdosVyOiogt_i7sHVGyQHdHtOIbmWQ5giucNn_NeCOhaB8bBl04p9ZS_heL3gqmw$<https://urldefense.com/v3/__http:/www.opensips-solutions.com__;!!EJc4YC3iFmQ!XbjfVzm_t84z0dh8Q9xdosVyOiogt_i7sHVGyQHdHtOIbmWQ5giucNn_NeCOhaB8bBl04p9ZS_heL3gqmw$> / https://urldefense.com/v3/__https://www.siphub.com__;!!EJc4YC3iFmQ!XbjfVzm_t84z0dh8Q9xdosVyOiogt_i7sHVGyQHdHtOIbmWQ5giucNn_NeCOhaB8bBl04p9ZS_j7Wkuyxw$<https://urldefense.com/v3/__https:/www.siphub.com__;!!EJc4YC3iFmQ!XbjfVzm_t84z0dh8Q9xdosVyOiogt_i7sHVGyQHdHtOIbmWQ5giucNn_NeCOhaB8bBl04p9ZS_j7Wkuyxw$>



On 3/7/24 13:39, Dragan, Calin via Users wrote:

> Hi,

>

> I'm new to Opensips, so I started with the opensips/opensips docker image, version 3.4. I installed, configured it, the server is running just fine. My problem is that I try to set-up the db authentication, but the auth_db.so cannot be loaded because of the missing auth.so module. This doesn't exist in the docker image. The last image where I found the auth.so module was 3.2, but I tried it and it is not compatible with the 3.4 version. Is there a way to enable db authentication with the 3.4 build?

>

> Thank you

>

>

> Hi,

>

> I’m new to Opensips, so I started with the opensips/opensips docker

> image, version 3.4. I installed, configured it, the server is running

> just fine. My problem is that I try to set-up the db authentication, but

> the auth_db.so cannot be loaded because of the missing auth.so module.

> This doesn’t exist in the docker image. The last image where I found the

> auth.so module was 3.2, but I tried it and it is not compatible with the

> 3.4 version. Is there a way to enable db authentication with the 3.4 build?

>

> Thank you

>

>

> _______________________________________________

> Users mailing list

> Users at lists.opensips.org<mailto:Users at lists.opensips.org>

> https://urldefense.com/v3/__http://lists.opensips.org/cgi-bin/mailman/listinfo/users__;!!EJc4YC3iFmQ!XbjfVzm_t84z0dh8Q9xdosVyOiogt_i7sHVGyQHdHtOIbmWQ5giucNn_NeCOhaB8bBl04p9ZS_hkrZARzQ$<https://urldefense.com/v3/__http:/lists.opensips.org/cgi-bin/mailman/listinfo/users__;!!EJc4YC3iFmQ!XbjfVzm_t84z0dh8Q9xdosVyOiogt_i7sHVGyQHdHtOIbmWQ5giucNn_NeCOhaB8bBl04p9ZS_hkrZARzQ$>



_______________________________________________

Users mailing list

Users at lists.opensips.org<mailto:Users at lists.opensips.org>

https://urldefense.com/v3/__http://lists.opensips.org/cgi-bin/mailman/listinfo/users__;!!EJc4YC3iFmQ!XbjfVzm_t84z0dh8Q9xdosVyOiogt_i7sHVGyQHdHtOIbmWQ5giucNn_NeCOhaB8bBl04p9ZS_hkrZARzQ$<https://urldefense.com/v3/__http:/lists.opensips.org/cgi-bin/mailman/listinfo/users__;!!EJc4YC3iFmQ!XbjfVzm_t84z0dh8Q9xdosVyOiogt_i7sHVGyQHdHtOIbmWQ5giucNn_NeCOhaB8bBl04p9ZS_hkrZARzQ$>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240308/72a1cc25/attachment-0001.html>

From razvan at opensips.org  Fri Mar  8 11:21:43 2024
From: razvan at opensips.org (=?UTF-8?Q?R=C4=83zvan_Crainea?=)
Date: Fri, 8 Mar 2024 13:21:43 +0200
Subject: [OpenSIPS-Users] Missing auth package in docker image
In-Reply-To: <BN8PR04MB577976F24E2A4D3D4C0E6B42F3272@BN8PR04MB5779.namprd04.prod.outlook.com>
References: <BN8PR04MB5779EB091C7F5710B0F6BB21F3202@BN8PR04MB5779.namprd04.prod.outlook.com>
 <2ec77d45-fcc8-41e8-8f57-3da56525c997@opensips.org>
 <BN8PR04MB577976F24E2A4D3D4C0E6B42F3272@BN8PR04MB5779.namprd04.prod.outlook.com>
Message-ID: <03708bbd-4368-428f-9109-e05041b01df6@opensips.org>

Hi, Calin!

The apt repository[1] should have already been setup in the docker 
container, so you can access any package from there.

[1] https://apt.opensips.org/

Best regards,

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

On 3/8/24 12:34, Dragan, Calin via Users wrote:
> Hi Razvan
> 
> Thank you! Installing the missing modules worked like a charm, I just didn’t know where to install them from.
> 
> Regards,
> Calin
> 
> From: Users <users-bounces at lists.opensips.org> On Behalf Of Razvan Crainea
> Sent: Friday, March 08, 2024 12:16 PM
> To: users at lists.opensips.org
> Subject: Re: [OpenSIPS-Users] Missing auth package in docker image
> 
> Hi, Calin! The stock/latest docker image does not come with any extra modules installed, it only comes with the opensips package, which should be enough for running the default opensips configuration. If I understand correctly, you also need
> 
> 
> Hi, Calin!
> 
> 
> 
> The stock/latest docker image does not come with any extra modules
> 
> installed, it only comes with the opensips package, which should be
> 
> enough for running the default opensips configuration.
> 
>    If I understand correctly, you also need the auth_db module, which is
> 
> part of the opensips-auth-modules package, and most likely a database
> 
> module as well.
> 
> Luckily, you have multiple choices to get this done:
> 
> * Install (i.e. using apt-get install opensips-auth-modules) the
> 
> packages you need in the docker container you already started
> 
> * Build your own docker container [2] with the correct setting of the
> 
> `OPENSIPS_EXTRA_MODULES` variable
> 
> * Use one of the sipssert images[3], which already includes the desired
> 
> package, along with others[2].
> 
> 
> 
> [1] https://urldefense.com/v3/__https://github.com/OpenSIPS/docker-opensips__;!!EJc4YC3iFmQ!XbjfVzm_t84z0dh8Q9xdosVyOiogt_i7sHVGyQHdHtOIbmWQ5giucNn_NeCOhaB8bBl04p9ZS_hnTW6o4A$<https://urldefense.com/v3/__https:/github.com/OpenSIPS/docker-opensips__;!!EJc4YC3iFmQ!XbjfVzm_t84z0dh8Q9xdosVyOiogt_i7sHVGyQHdHtOIbmWQ5giucNn_NeCOhaB8bBl04p9ZS_hnTW6o4A$>
> 
> [2]
> 
> https://urldefense.com/v3/__https://hub.docker.com/layers/opensips/opensips/sipssert-3.4/images/sha256-be41b1e7cbcd4bb8ce89f8055fc636dd57bd047a9992ff4b42adc75ad4066610?context=explore__;!!EJc4YC3iFmQ!XbjfVzm_t84z0dh8Q9xdosVyOiogt_i7sHVGyQHdHtOIbmWQ5giucNn_NeCOhaB8bBl04p9ZS_gP1eygJg$<https://urldefense.com/v3/__https:/hub.docker.com/layers/opensips/opensips/sipssert-3.4/images/sha256-be41b1e7cbcd4bb8ce89f8055fc636dd57bd047a9992ff4b42adc75ad4066610?context=explore__;!!EJc4YC3iFmQ!XbjfVzm_t84z0dh8Q9xdosVyOiogt_i7sHVGyQHdHtOIbmWQ5giucNn_NeCOhaB8bBl04p9ZS_gP1eygJg$>
> 
> [3]
> 
> https://urldefense.com/v3/__https://github.com/OpenSIPS/sipssert-opensips-tests/blob/3.4/.opensips.modules__;!!EJc4YC3iFmQ!XbjfVzm_t84z0dh8Q9xdosVyOiogt_i7sHVGyQHdHtOIbmWQ5giucNn_NeCOhaB8bBl04p9ZS_hjt66IaA$<https://urldefense.com/v3/__https:/github.com/OpenSIPS/sipssert-opensips-tests/blob/3.4/.opensips.modules__;!!EJc4YC3iFmQ!XbjfVzm_t84z0dh8Q9xdosVyOiogt_i7sHVGyQHdHtOIbmWQ5giucNn_NeCOhaB8bBl04p9ZS_hjt66IaA$>
> 
> 
> 
> Best regards,
> 
> 
> 
> Răzvan Crainea
> 
> OpenSIPS Core Developer / SIPhub CTO
> 
> https://urldefense.com/v3/__http://www.opensips-solutions.com__;!!EJc4YC3iFmQ!XbjfVzm_t84z0dh8Q9xdosVyOiogt_i7sHVGyQHdHtOIbmWQ5giucNn_NeCOhaB8bBl04p9ZS_heL3gqmw$<https://urldefense.com/v3/__http:/www.opensips-solutions.com__;!!EJc4YC3iFmQ!XbjfVzm_t84z0dh8Q9xdosVyOiogt_i7sHVGyQHdHtOIbmWQ5giucNn_NeCOhaB8bBl04p9ZS_heL3gqmw$> / https://urldefense.com/v3/__https://www.siphub.com__;!!EJc4YC3iFmQ!XbjfVzm_t84z0dh8Q9xdosVyOiogt_i7sHVGyQHdHtOIbmWQ5giucNn_NeCOhaB8bBl04p9ZS_j7Wkuyxw$<https://urldefense.com/v3/__https:/www.siphub.com__;!!EJc4YC3iFmQ!XbjfVzm_t84z0dh8Q9xdosVyOiogt_i7sHVGyQHdHtOIbmWQ5giucNn_NeCOhaB8bBl04p9ZS_j7Wkuyxw$>
> 
> 
> 
> On 3/7/24 13:39, Dragan, Calin via Users wrote:
> 
>> Hi,
> 
>>
> 
>> I'm new to Opensips, so I started with the opensips/opensips docker image, version 3.4. I installed, configured it, the server is running just fine. My problem is that I try to set-up the db authentication, but the auth_db.so cannot be loaded because of the missing auth.so module. This doesn't exist in the docker image. The last image where I found the auth.so module was 3.2, but I tried it and it is not compatible with the 3.4 version. Is there a way to enable db authentication with the 3.4 build?
> 
>>
> 
>> Thank you
> 
>>
> 
>>
> 
>> Hi,
> 
>>
> 
>> I’m new to Opensips, so I started with the opensips/opensips docker
> 
>> image, version 3.4. I installed, configured it, the server is running
> 
>> just fine. My problem is that I try to set-up the db authentication, but
> 
>> the auth_db.so cannot be loaded because of the missing auth.so module.
> 
>> This doesn’t exist in the docker image. The last image where I found the
> 
>> auth.so module was 3.2, but I tried it and it is not compatible with the
> 
>> 3.4 version. Is there a way to enable db authentication with the 3.4 build?
> 
>>
> 
>> Thank you
> 
>>
> 
>>
> 
>> _______________________________________________
> 
>> Users mailing list
> 
>> Users at lists.opensips.org<mailto:Users at lists.opensips.org>
> 
>> https://urldefense.com/v3/__http://lists.opensips.org/cgi-bin/mailman/listinfo/users__;!!EJc4YC3iFmQ!XbjfVzm_t84z0dh8Q9xdosVyOiogt_i7sHVGyQHdHtOIbmWQ5giucNn_NeCOhaB8bBl04p9ZS_hkrZARzQ$<https://urldefense.com/v3/__http:/lists.opensips.org/cgi-bin/mailman/listinfo/users__;!!EJc4YC3iFmQ!XbjfVzm_t84z0dh8Q9xdosVyOiogt_i7sHVGyQHdHtOIbmWQ5giucNn_NeCOhaB8bBl04p9ZS_hkrZARzQ$>
> 
> 
> 
> _______________________________________________
> 
> Users mailing list
> 
> Users at lists.opensips.org<mailto:Users at lists.opensips.org>
> 
> https://urldefense.com/v3/__http://lists.opensips.org/cgi-bin/mailman/listinfo/users__;!!EJc4YC3iFmQ!XbjfVzm_t84z0dh8Q9xdosVyOiogt_i7sHVGyQHdHtOIbmWQ5giucNn_NeCOhaB8bBl04p9ZS_hkrZARzQ$<https://urldefense.com/v3/__http:/lists.opensips.org/cgi-bin/mailman/listinfo/users__;!!EJc4YC3iFmQ!XbjfVzm_t84z0dh8Q9xdosVyOiogt_i7sHVGyQHdHtOIbmWQ5giucNn_NeCOhaB8bBl04p9ZS_hkrZARzQ$>
> 
> 
> Hi Razvan
> 
> Thank you! Installing the missing modules worked like a charm, I just 
> didn’t know where to install them from.
> 
> Regards,
> 
> Calin
> 
> *From:*Users <users-bounces at lists.opensips.org> *On Behalf Of *Razvan 
> Crainea
> *Sent:* Friday, March 08, 2024 12:16 PM
> *To:* users at lists.opensips.org
> *Subject:* Re: [OpenSIPS-Users] Missing auth package in docker image
> 
> Hi, Calin! The stock/latest docker image does not come with any extra 
> modules installed, it only comes with the opensips package, which should 
> be enough for running the default opensips configuration. If I 
> understand correctly, you also need
> 
> Hi, Calin!
> 
> The stock/latest docker image does not come with any extra modules
> 
> installed, it only comes with the opensips package, which should be
> 
> enough for running the default opensips configuration.
> 
>    If I understand correctly, you also need the auth_db module, which is
> 
> part of the opensips-auth-modules package, and most likely a database
> 
> module as well.
> 
> Luckily, you have multiple choices to get this done:
> 
> * Install (i.e. using apt-get install opensips-auth-modules) the
> 
> packages you need in the docker container you already started
> 
> * Build your own docker container [2] with the correct setting of the
> 
> `OPENSIPS_EXTRA_MODULES` variable
> 
> * Use one of the sipssert images[3], which already includes the desired
> 
> package, along with others[2].
> 
> [1] 
> https://urldefense.com/v3/__https://github.com/OpenSIPS/docker-opensips__;!!EJc4YC3iFmQ!XbjfVzm_t84z0dh8Q9xdosVyOiogt_i7sHVGyQHdHtOIbmWQ5giucNn_NeCOhaB8bBl04p9ZS_hnTW6o4A$ <https://urldefense.com/v3/__https:/github.com/OpenSIPS/docker-opensips__;!!EJc4YC3iFmQ!XbjfVzm_t84z0dh8Q9xdosVyOiogt_i7sHVGyQHdHtOIbmWQ5giucNn_NeCOhaB8bBl04p9ZS_hnTW6o4A$>
> 
> [2]
> 
> https://urldefense.com/v3/__https://hub.docker.com/layers/opensips/opensips/sipssert-3.4/images/sha256-be41b1e7cbcd4bb8ce89f8055fc636dd57bd047a9992ff4b42adc75ad4066610?context=explore__;!!EJc4YC3iFmQ!XbjfVzm_t84z0dh8Q9xdosVyOiogt_i7sHVGyQHdHtOIbmWQ5giucNn_NeCOhaB8bBl04p9ZS_gP1eygJg$ <https://urldefense.com/v3/__https:/hub.docker.com/layers/opensips/opensips/sipssert-3.4/images/sha256-be41b1e7cbcd4bb8ce89f8055fc636dd57bd047a9992ff4b42adc75ad4066610?context=explore__;!!EJc4YC3iFmQ!XbjfVzm_t84z0dh8Q9xdosVyOiogt_i7sHVGyQHdHtOIbmWQ5giucNn_NeCOhaB8bBl04p9ZS_gP1eygJg$>
> 
> [3]
> 
> https://urldefense.com/v3/__https://github.com/OpenSIPS/sipssert-opensips-tests/blob/3.4/.opensips.modules__;!!EJc4YC3iFmQ!XbjfVzm_t84z0dh8Q9xdosVyOiogt_i7sHVGyQHdHtOIbmWQ5giucNn_NeCOhaB8bBl04p9ZS_hjt66IaA$ <https://urldefense.com/v3/__https:/github.com/OpenSIPS/sipssert-opensips-tests/blob/3.4/.opensips.modules__;!!EJc4YC3iFmQ!XbjfVzm_t84z0dh8Q9xdosVyOiogt_i7sHVGyQHdHtOIbmWQ5giucNn_NeCOhaB8bBl04p9ZS_hjt66IaA$>
> 
> Best regards,
> 
> Răzvan Crainea
> 
> OpenSIPS Core Developer / SIPhub CTO
> 
> https://urldefense.com/v3/__http://www.opensips-solutions.com__;!!EJc4YC3iFmQ!XbjfVzm_t84z0dh8Q9xdosVyOiogt_i7sHVGyQHdHtOIbmWQ5giucNn_NeCOhaB8bBl04p9ZS_heL3gqmw$ <https://urldefense.com/v3/__http:/www.opensips-solutions.com__;!!EJc4YC3iFmQ!XbjfVzm_t84z0dh8Q9xdosVyOiogt_i7sHVGyQHdHtOIbmWQ5giucNn_NeCOhaB8bBl04p9ZS_heL3gqmw$> / https://urldefense.com/v3/__https://www.siphub.com__;!!EJc4YC3iFmQ!XbjfVzm_t84z0dh8Q9xdosVyOiogt_i7sHVGyQHdHtOIbmWQ5giucNn_NeCOhaB8bBl04p9ZS_j7Wkuyxw$ <https://urldefense.com/v3/__https:/www.siphub.com__;!!EJc4YC3iFmQ!XbjfVzm_t84z0dh8Q9xdosVyOiogt_i7sHVGyQHdHtOIbmWQ5giucNn_NeCOhaB8bBl04p9ZS_j7Wkuyxw$>
> 
> On 3/7/24 13:39, Dragan, Calin via Users wrote:
> 
>> Hi,
> 
>> 
> 
>> I'm new to Opensips, so I started with the opensips/opensips docker image, version 3.4. I installed, configured it, the server is running just fine. My problem is that I try to set-up the db authentication, but the auth_db.so cannot be loaded because of the missing auth.so module. This doesn't exist in the docker image. The last image where I found the auth.so module was 3.2, but I tried it and it is not compatible with the 3.4 version. Is there a way to enable db authentication with the 3.4 build?
> 
>> 
> 
>> Thank you
> 
>> 
> 
>> 
> 
>> Hi,
> 
>> 
> 
>> I’m new to Opensips, so I started with the opensips/opensips docker 
> 
>> image, version 3.4. I installed, configured it, the server is running 
> 
>> just fine. My problem is that I try to set-up the db authentication, but 
> 
>> the auth_db.so cannot be loaded because of the missing auth.so module. 
> 
>> This doesn’t exist in the docker image. The last image where I found the 
> 
>> auth.so module was 3.2, but I tried it and it is not compatible with the 
> 
>> 3.4 version. Is there a way to enable db authentication with the 3.4 build?
> 
>> 
> 
>> Thank you
> 
>> 
> 
>> 
> 
>> _______________________________________________
> 
>> Users mailing list
> 
>> Users at lists.opensips.org <mailto:Users at lists.opensips.org>
> 
>> https://urldefense.com/v3/__http://lists.opensips.org/cgi-bin/mailman/listinfo/users__;!!EJc4YC3iFmQ!XbjfVzm_t84z0dh8Q9xdosVyOiogt_i7sHVGyQHdHtOIbmWQ5giucNn_NeCOhaB8bBl04p9ZS_hkrZARzQ$ <https://urldefense.com/v3/__http:/lists.opensips.org/cgi-bin/mailman/listinfo/users__;!!EJc4YC3iFmQ!XbjfVzm_t84z0dh8Q9xdosVyOiogt_i7sHVGyQHdHtOIbmWQ5giucNn_NeCOhaB8bBl04p9ZS_hkrZARzQ$>
> 
> _______________________________________________
> 
> Users mailing list
> 
> Users at lists.opensips.org <mailto:Users at lists.opensips.org>
> 
> https://urldefense.com/v3/__http://lists.opensips.org/cgi-bin/mailman/listinfo/users__;!!EJc4YC3iFmQ!XbjfVzm_t84z0dh8Q9xdosVyOiogt_i7sHVGyQHdHtOIbmWQ5giucNn_NeCOhaB8bBl04p9ZS_hkrZARzQ$ <https://urldefense.com/v3/__http:/lists.opensips.org/cgi-bin/mailman/listinfo/users__;!!EJc4YC3iFmQ!XbjfVzm_t84z0dh8Q9xdosVyOiogt_i7sHVGyQHdHtOIbmWQ5giucNn_NeCOhaB8bBl04p9ZS_hkrZARzQ$>
> 
> 
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users


From rvg at rvgeerligs.nl  Sat Mar  9 13:46:00 2024
From: rvg at rvgeerligs.nl (rvg at rvgeerligs.nl)
Date: Sat, 09 Mar 2024 13:46:00 +0000
Subject: [OpenSIPS-Users] pn still problems
Message-ID: <a8d2f3e21c206d8e1506055671139205a3f189b0@rvgeerligs.nl>

Hi All,

I still have problems with opensips3.4 push notifications:

Somehow INVITEs keep looping and get rejected.

Code:
...
route{

...

if (has_totag()) {

...

if (!is_method("ACK"))
        async (pn_process_purr("location"), resume_route);

...
}

...

# do lookup with method filtering

#--
 lookup("location", "method-filtering");
 $var(rc) = $retcode;
 switch ($var(rc)) {
 case 1:
     # we found at least 1 non-PN contact!
 xlog("L_INFO", "DBG: 1 contacts found non-PN ($var(rc))\n");
     $var(do_relay) = true;
     break;
 case 2:
     # success, but all contacts are PN-enabled, so we're
     # sending PNs / awaiting re-registrations from them
 xlog("L_INFO", "DBG: contacts found send PN? ($var(rc))\n");
     $var(do_relay) = false;
     #$avp(skip_relay) = true;
     break;
 default:
     xlog("L_INFO", "DBG: no contacts found ($var(rc))\n");
     t_reply(404, "Not Found");
     exit;
 }

 if ($var(do_relay) && !t_relay())
    send_reply(500, "Internal Server Error");

...

if($var(do_relay) == true) 
 route(relay);
}

...

from log (looping log, it repeats):

DBG:core:parse_headers: this is the first via
2024-03-09T09:41:13.485706+00:00 xsp2 /usr/local/sbin/opensips[2061136]: DBG:core:_parse_to: end of header reached, state=10
2024-03-09T09:41:13.485748+00:00 xsp2 /usr/local/sbin/opensips[2061136]: DBG:core:_parse_to: display={}, ruri={sip:to at dummy.com}
2024-03-09T09:41:13.485807+00:00 xsp2 /usr/local/sbin/opensips[2061136]: DBG:core:get_hdr_field: <To> [20]; uri=[sip:to at dummy.com] 
2024-03-09T09:41:13.485854+00:00 xsp2 /usr/local/sbin/opensips[2061136]: DBG:core:get_hdr_field: to body [<sip:to at dummy.com>#015#012]
2024-03-09T09:41:13.485915+00:00 xsp2 /usr/local/sbin/opensips[2061136]: DBG:core:get_hdr_field: cseq <CSeq>: <1> 

2024-03-09T09:41:13.485962+00:00 xsp2 /usr/local/sbin/opensips[2061136]: DBG:core:get_hdr_field: found end of header
2024-03-09T09:41:13.486040+00:00 xsp2 /usr/local/sbin/opensips[2061136]: DBG:core:parse_headers: flags=ffffffffffffffff
2024-03-09T09:41:13.486088+00:00 xsp2 /usr/local/sbin/opensips[2061136]: DBG:core:get_dummy_sip_msg: setting as static to 0xffffb1a612c0
2024-03-09T09:41:13.486145+00:00 xsp2 /usr/local/sbin/opensips[2061136]: DBG:core:evi_raise_event_msg: found subscriber E_UL_CONTACT_REFRESH
2024-03-09T09:41:13.486207+00:00 xsp2 /usr/local/sbin/opensips[2061136]: DBG:core:dup_ref_script_route_in_shm: dupping 0xffffaa264f60 [E_UL_CONTACT_REFRESH], idx 1, ver/cnt 1, to new 0xffffaa26d9e0 [E_UL_CONTACT_REFRESH], idx 1, ver/cnt 1
2024-03-09T09:41:13.486283+00:00 xsp2 /usr/local/sbin/opensips[2061136]: DBG:core:release_dummy_sip_msg: cleaning the static sip msg 0xffffb1a612c0
2024-03-09T09:41:13.486352+00:00 xsp2 /usr/local/sbin/opensips[2061136]: DBG:core:destroy_avp_list: destroying list (nil)
2024-03-09T09:41:13.486409+00:00 xsp2 /usr/local/sbin/opensips[2061136]: DBG:core:ipc_handle_job: received job type 0[RPC] from process 6
2024-03-09T09:41:13.486467+00:00 xsp2 /usr/local/sbin/opensips[2061136]: DBG:core:get_dummy_sip_msg: reusing the static sip msg 0xffffb1a612c0
2024-03-09T09:41:13.486533+00:00 xsp2 /usr/local/sbin/opensips[2061136]: DBG:core:parse_params: Parsing params for:[sip:rvg at 82.151.164.77:57775;pn-prid=F1B7F53A99A35254A55CCAE2EDF80C1FAE12F353592BB6ED203ADA0175E34AD9:voip;pn-provider=apns;pn-param=ABCD1234.cllkit.voip;pn-silent=1;pn-timeout=0;transport=udp]
2024-03-09T09:41:13.486571+00:00 xsp2 /usr/local/sbin/opensips[2061136]: ERROR: -- ** --pn_send was called sip:user at dummy.com
2024-03-09T09:41:13.486651+00:00 xsp2 /usr/local/sbin/opensips[2061136]: ERROR:core:route_param_get: route $param variable accepts only integer indexes
2024-03-09T09:41:13.486746+00:00 xsp2 /usr/local/sbin/opensips[2061136]: message repeated 2 times: [ ERROR:core:route_param_get: route $param variable accepts only integer indexes]
2024-03-09T09:41:13.486787+00:00 xsp2 /usr/local/sbin/opensips[2061136]: ERROR:pn params:  <null>,#012                   ,#012                   

2024-03-09T09:41:13.486822+00:00 xsp2 /usr/local/sbin/opensips[2061136]: DBG:core:release_dummy_sip_msg: cleaning the static sip msg 0xffffb1a612c0
2024-03-09T09:41:13.486913+00:00 xsp2 /usr/local/sbin/opensips[2061136]: DBG:core:destroy_avp_list: destroying list (nil)
2024-03-09T09:41:13.697168+00:00 xsp2 /usr/local/sbin/opensips[2061135]: DBG:core:parse_msg: SIP Request:

Any advice appreciated, regards,

Ronald Geerligs
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240309/a98de770/attachment.html>

From rvg at rvgeerligs.nl  Sat Mar  9 14:09:36 2024
From: rvg at rvgeerligs.nl (rvg at rvgeerligs.nl)
Date: Sat, 09 Mar 2024 14:09:36 +0000
Subject: [OpenSIPS-Users] pn still problems part 2
In-Reply-To: <a8d2f3e21c206d8e1506055671139205a3f189b0@rvgeerligs.nl>
References: <a8d2f3e21c206d8e1506055671139205a3f189b0@rvgeerligs.nl>
Message-ID: <8890ae969a777d608af160ce9a460485f85b62bb@rvgeerligs.nl>

Adding:

event_route[E_UL_CONTACT_REFRESH]
{
    route(pm_send, $(param(uri){param.value,pn-provider}),
                   $(param(uri){param.value,pn-prid}),
                   $(param(uri){param.value,pn-param}));
#    $callid;
#    $param(callid);
}


#--
route [pm_send]
{
#    exec(marg.sh)
xlog(" -- ** --pn_send was called $ru\n");
xlog("pn_send: pn params:  $(param(uri){param.value,pn-provider}),
                   $(param(uri){param.value,pn-prid}),
                   $(param(uri){param.value,pn-param})\n");
$var(input) = "input mine three";
#async(exec("/root/marg.sh > effect", "this is my $var(input) for exec\n", , , $avp(env));
# async(exec("/root/marg.sh 5 6 7 > effect", $ru, $ru), resume_route);
 exit;
}

question: Does the route[pm_send] need to return any value? exit does not not return value does it?

does the [pm_send] acually need to send the push for the INVITE to be answered by 200 OK?

Regards, Ronald



March 9, 2024 at 2:46 PM, rvg at rvgeerligs.nl wrote:


> 
> Hi All,
> 
> I still have problems with opensips3.4 push notifications:
> 
> Somehow INVITEs keep looping and get rejected.
> 
> Code:
> ...
> route{
> 
> ...
> 
> if (has_totag()) {
> 
> ...
> 
> if (!is_method("ACK"))
>         async (pn_process_purr("location"), resume_route);
> 
> ...
> }
> 
> ...
> 
> # do lookup with method filtering
> 
> #--
>  lookup("location", "method-filtering");
>  $var(rc) = $retcode;
>  switch ($var(rc)) {
>  case 1:
>      # we found at least 1 non-PN contact!
>  xlog("L_INFO", "DBG: 1 contacts found non-PN ($var(rc))\n");
>      $var(do_relay) = true;
>      break;
>  case 2:
>      # success, but all contacts are PN-enabled, so we're
>      # sending PNs / awaiting re-registrations from them
>  xlog("L_INFO", "DBG: contacts found send PN? ($var(rc))\n");
>      $var(do_relay) = false;
>      #$avp(skip_relay) = true;
>      break;
>  default:
>      xlog("L_INFO", "DBG: no contacts found ($var(rc))\n");
>      t_reply(404, "Not Found");
>      exit;
>  }
> 
>  if ($var(do_relay) && !t_relay())
>     send_reply(500, "Internal Server Error");
> 
> ...
> 
> if($var(do_relay) == true) 
>  route(relay);
> }
> 
> ...
> 
> from log (looping log, it repeats):
> 
> DBG:core:parse_headers: this is the first via
> 2024-03-09T09:41:13.485706+00:00 xsp2 /usr/local/sbin/opensips[2061136]: DBG:core:_parse_to: end of header reached, state=10
> 2024-03-09T09:41:13.485748+00:00 xsp2 /usr/local/sbin/opensips[2061136]: DBG:core:_parse_to: display={}, ruri={sip:to at dummy.com}
> 2024-03-09T09:41:13.485807+00:00 xsp2 /usr/local/sbin/opensips[2061136]: DBG:core:get_hdr_field: <To> [20]; uri=[sip:to at dummy.com] 
> 2024-03-09T09:41:13.485854+00:00 xsp2 /usr/local/sbin/opensips[2061136]: DBG:core:get_hdr_field: to body [<sip:to at dummy.com>#015#012]
> 2024-03-09T09:41:13.485915+00:00 xsp2 /usr/local/sbin/opensips[2061136]: DBG:core:get_hdr_field: cseq <CSeq>: <1> 
> 
> 2024-03-09T09:41:13.485962+00:00 xsp2 /usr/local/sbin/opensips[2061136]: DBG:core:get_hdr_field: found end of header
> 2024-03-09T09:41:13.486040+00:00 xsp2 /usr/local/sbin/opensips[2061136]: DBG:core:parse_headers: flags=ffffffffffffffff
> 2024-03-09T09:41:13.486088+00:00 xsp2 /usr/local/sbin/opensips[2061136]: DBG:core:get_dummy_sip_msg: setting as static to 0xffffb1a612c0
> 2024-03-09T09:41:13.486145+00:00 xsp2 /usr/local/sbin/opensips[2061136]: DBG:core:evi_raise_event_msg: found subscriber E_UL_CONTACT_REFRESH
> 2024-03-09T09:41:13.486207+00:00 xsp2 /usr/local/sbin/opensips[2061136]: DBG:core:dup_ref_script_route_in_shm: dupping 0xffffaa264f60 [E_UL_CONTACT_REFRESH], idx 1, ver/cnt 1, to new 0xffffaa26d9e0 [E_UL_CONTACT_REFRESH], idx 1, ver/cnt 1
> 2024-03-09T09:41:13.486283+00:00 xsp2 /usr/local/sbin/opensips[2061136]: DBG:core:release_dummy_sip_msg: cleaning the static sip msg 0xffffb1a612c0
> 2024-03-09T09:41:13.486352+00:00 xsp2 /usr/local/sbin/opensips[2061136]: DBG:core:destroy_avp_list: destroying list (nil)
> 2024-03-09T09:41:13.486409+00:00 xsp2 /usr/local/sbin/opensips[2061136]: DBG:core:ipc_handle_job: received job type 0[RPC] from process 6
> 2024-03-09T09:41:13.486467+00:00 xsp2 /usr/local/sbin/opensips[2061136]: DBG:core:get_dummy_sip_msg: reusing the static sip msg 0xffffb1a612c0
> 2024-03-09T09:41:13.486533+00:00 xsp2 /usr/local/sbin/opensips[2061136]: DBG:core:parse_params: Parsing params for:[sip:rvg at 82.151.164.77:57775;pn-prid=F1B7F53A99A35254A55CCAE2EDF80C1FAE12F353592BB6ED203ADA0175E34AD9:voip;pn-provider=apns;pn-param=ABCD1234.cllkit.voip;pn-silent=1;pn-timeout=0;transport=udp]
> 2024-03-09T09:41:13.486571+00:00 xsp2 /usr/local/sbin/opensips[2061136]: ERROR: -- ** --pn_send was called sip:user at dummy.com
> 2024-03-09T09:41:13.486651+00:00 xsp2 /usr/local/sbin/opensips[2061136]: ERROR:core:route_param_get: route $param variable accepts only integer indexes
> 2024-03-09T09:41:13.486746+00:00 xsp2 /usr/local/sbin/opensips[2061136]: message repeated 2 times: [ ERROR:core:route_param_get: route $param variable accepts only integer indexes]
> 2024-03-09T09:41:13.486787+00:00 xsp2 /usr/local/sbin/opensips[2061136]: ERROR:pn params:  <null>,#012                   ,#012                   
> 
> 2024-03-09T09:41:13.486822+00:00 xsp2 /usr/local/sbin/opensips[2061136]: DBG:core:release_dummy_sip_msg: cleaning the static sip msg 0xffffb1a612c0
> 2024-03-09T09:41:13.486913+00:00 xsp2 /usr/local/sbin/opensips[2061136]: DBG:core:destroy_avp_list: destroying list (nil)
> 2024-03-09T09:41:13.697168+00:00 xsp2 /usr/local/sbin/opensips[2061135]: DBG:core:parse_msg: SIP Request:
> 
> Any advice appreciated, regards,
> 
> Ronald Geerligs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240309/5236e774/attachment-0001.html>

From spanda at 3clogic.com  Mon Mar 11 06:22:47 2024
From: spanda at 3clogic.com (Sasmita Panda)
Date: Mon, 11 Mar 2024 11:52:47 +0530
Subject: [OpenSIPS-Users] utimer_ticker warning in opensips 3.2
Message-ID: <CALf-Q442AqxhLDxKt6_psUWUzcC1aGfZ9CrHvYXH_BU5GFGL2w@mail.gmail.com>

Hi All ,

Mar 11 05:57:02 ip-192-168-33-171 /usr/local/sbin/opensips[213843]:
INFO:proto_ws:mod_init: initializing WebSocket protocol
Mar 11 05:57:03 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 100
ms ago (now 290 ms), delaying execution
Mar 11 05:57:03 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 200
ms ago (now 390 ms), delaying execution
Mar 11 05:57:03 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 300
ms ago (now 490 ms), delaying execution
Mar 11 05:57:03 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 400
ms ago (now 590 ms), delaying execution
Mar 11 05:57:03 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 500
ms ago (now 690 ms), delaying execution
Mar 11 05:57:03 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 600
ms ago (now 790 ms), delaying execution
Mar 11 05:57:03 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 700
ms ago (now 890 ms), delaying execution
Mar 11 05:57:03 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 800
ms ago (now 990 ms), delaying execution
Mar 11 05:57:03 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 900
ms ago (now 1090 ms), delaying execution
Mar 11 05:57:03 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 1000
ms ago (now 1190 ms), delaying execution
Mar 11 05:57:04 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 1100
ms ago (now 1290 ms), delaying execution
Mar 11 05:57:04 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 1200
ms ago (now 1390 ms), delaying execution
Mar 11 05:57:04 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 1300
ms ago (now 1490 ms), delaying execution
Mar 11 05:57:04 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 1400
ms ago (now 1590 ms), delaying execution
Mar 11 05:57:04 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 1500
ms ago (now 1690 ms), delaying execution
Mar 11 05:57:04 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 1600
ms ago (now 1790 ms), delaying execution
Mar 11 05:57:04 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 1700
ms ago (now 1890 ms), delaying execution
Mar 11 05:57:04 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 1790
ms ago (now 1980 ms), delaying execution
Mar 11 05:57:04 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
WARNING:core:timer_ticker: timer task <tm-timer> already scheduled 990 ms
ago (now 1980 ms), delaying execution

*What is this warning for? Whenever I am starting my openisps service this
warning comes . Although the service seems like it's running but it's not
listening on the socket exposed .  How to resolve this ?*

*/usr/local/sbin/opensips  -V*
version: opensips 3.2.3 (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.
svn revision: 3831:3878
main.c compiled on 07:52:40 Mar 29 2023 with gcc 11

*cat /etc/*release*
Amazon Linux release 2023 (Amazon Linux)
NAME="Amazon Linux"
VERSION="2023"
ID="amzn"
ID_LIKE="fedora"
VERSION_ID="2023"
PLATFORM_ID="platform:al2023"
PRETTY_NAME="Amazon Linux 2023"
ANSI_COLOR="0;33"
CPE_NAME="cpe:2.3:o:amazon:amazon_linux:2023"
HOME_URL="https://aws.amazon.com/linux/"
BUG_REPORT_URL="https://github.com/amazonlinux/amazon-linux-2023"
SUPPORT_END="2028-03-01"
Amazon Linux release 2023 (Amazon Linux)


*Thanks & Regards*
*Sasmita Panda*
*Senior Network Testing and Software Engineer*
*3CLogic , ph:07827611765*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240311/624c27fd/attachment.html>

From spanda at 3clogic.com  Mon Mar 11 06:33:44 2024
From: spanda at 3clogic.com (Sasmita Panda)
Date: Mon, 11 Mar 2024 12:03:44 +0530
Subject: [OpenSIPS-Users] utimer_ticker warning in opensips 3.2
In-Reply-To: <CALf-Q442AqxhLDxKt6_psUWUzcC1aGfZ9CrHvYXH_BU5GFGL2w@mail.gmail.com>
References: <CALf-Q442AqxhLDxKt6_psUWUzcC1aGfZ9CrHvYXH_BU5GFGL2w@mail.gmail.com>
Message-ID: <CALf-Q45dJ=hVdJPxsB7dU1PhER4VYBnHSU+3Jn9RwrvnZ1a=Hg@mail.gmail.com>

With the same server configuration and opensips version I am getting below
error as well .

CRITICAL:core:fm_free: freeing already freed shm pointer (0x7fc110e0b408),
first free: (null): (null)(0) - aborting!

 /usr/local/sbin/opensips[215171]: INFO:core:handle_sigs: child process
215185 exited by a signal 6
 /usr/local/sbin/opensips[215171]: INFO:core:handle_sigs: core was generated
 /usr/local/sbin/opensips[215171]: INFO:core:handle_sigs: terminating due
to SIGCHLD
 /usr/local/sbin/opensips[215172]: Memory status (pkg):
 /usr/local/sbin/opensips[215172]: fm_status (0x7fc2907ff010):
 /usr/local/sbin/opensips[215174]: INFO:core:sig_usr: signal 15 received
 /usr/local/sbin/opensips[215172]: heap size= 33554432
 /usr/local/sbin/opensips[215174]: Memory status (pkg):
 /usr/local/sbin/opensips[215172]: used= 3710048, used+overhead=3801344,
free=29844384
 /usr/local/sbin/opensips[215174]: fm_status (0x7fc2907ff010):
 /usr/local/sbin/opensips[215172]: max used (+overhead)= 3801344
 /usr/local/sbin/opensips[215174]: heap size= 33554432
 /usr/local/sbin/opensips[215172]: dumping free list:
 /usr/local/sbin/opensips[215174]: used= 229752, used+overhead=318936,
free=33324680
 /usr/local/sbin/opensips[215172]: hash =   1 fragments no.:     1, unused:
    0#012#011#011 bucket size:         8 -         8 (first         8)
 /usr/local/sbin/opensips[215174]: max used (+overhead)= 385792
 /usr/local/sbin/opensips[215174]: dumping free list:
 /usr/local/sbin/opensips[215172]: hash =  18 fragments no.:     1, unused:
    0#012#011#011 bucket size:       144 -       144 (first       144)
 /usr/local/sbin/opensips[215174]: hash =   7 fragments no.:   139, unused:
    0#012#011#011 bucket size:        56 -        56 (first        56)
 /usr/local/sbin/opensips[215172]: hash = 2059 fragments no.:     1,
unused:     0#012#011#011 bucket size:  16777216 -  33554432 (first
 29752936)
 /usr/local/sbin/opensips[215174]: hash =  13 fragments no.:    37, unused:
    0#012#011#011 bucket size:       104 -       104 (first       104)
 /usr/local/sbin/opensips[215172]: TOTAL:      3 free fragments = 29753088
free bytes
 /usr/local/sbin/opensips[215172]: TOTAL: 48 overhead
 /usr/local/sbin/opensips[215174]: hash =  16 fragments no.:    61, unused:
    0#012#011#011 bucket size:       128 -       128 (first       128)
 /usr/local/sbin/opensips[215172]: -----------------------------
 /usr/local/sbin/opensips[215174]: hash =  31 fragments no.:   152, unused:
    0#012#011#011 bucket size:       248 -       248 (first       248)
 /usr/local/sbin/opensips[215174]: hash =  68 fragments no.:    16, unused:
    0#012#011#011 bucket size:       544 -       544 (first       544)
 /usr/local/sbin/opensips[215174]: hash = 105 fragments no.:     1, unused:
    0#012#011#011 bucket size:       840 -       840 (first       840)
 /usr/local/sbin/opensips[215174]: hash = 2059 fragments no.:     1,
unused:     0#012#011#011 bucket size:  16777216 -  33554432 (first
 33168816)
 /usr/local/sbin/opensips[215174]: TOTAL:    407 free fragments = 33235496
free bytes
 /usr/local/sbin/opensips[215174]: TOTAL: 48 overhead
 /usr/local/sbin/opensips[215174]: -----------------------------
 /usr/local/sbin/opensips[215176]: Memory status (pkg):
 /usr/local/sbin/opensips[215176]: fm_status (0x7fc2907ff010):
 /usr/local/sbin/opensips[215176]: heap size= 33554432
 /usr/local/sbin/opensips[215176]: used= 3705480, used+overhead=3796584,
free=29848952
 /usr/local/sbin/opensips[215176]: max used (+overhead)= 3798064
 /usr/local/sbin/opensips[215176]: dumping free list:
 /usr/local/sbin/opensips[215176]: hash =   2 fragments no.:     2, unused:
    0#012#011#011 bucket size:        16 -        16 (first        16)
 /usr/local/sbin/opensips[215176]: hash =   3 fragments no.:     1, unused:
    0#012#011#011 bucket size:        24 -        24 (first        24)
 /usr/local/sbin/opensips[215176]: hash =  16 fragments no.:     1, unused:
    0#012#011#011 bucket size:       128 -       128 (first       128)
 /usr/local/sbin/opensips[215175]: Memory status (pkg):
 /usr/local/sbin/opensips[215175]: fm_status (0x7fc2907ff010):
 /usr/local/sbin/opensips[215175]: heap size= 33554432
 /usr/local/sbin/opensips[215176]: hash = 2059 fragments no.:     1,
unused:     0#012#011#011 bucket size:  16777216 -  33554432 (first
 29757664)
 /usr/local/sbin/opensips[215175]: used= 3705480, used+overhead=3796584,
free=29848952
 /usr/local/sbin/opensips[215176]: TOTAL:      5 free fragments = 29757848
free bytes
 /usr/local/sbin/opensips[215175]: max used (+overhead)= 3798064
 /usr/local/sbin/opensips[215176]: TOTAL: 48 overhead
 /usr/local/sbin/opensips[215176]: -----------------------------
 /usr/local/sbin/opensips[215175]: dumping free list:
 /usr/local/sbin/opensips[215175]: hash =   2 fragments no.:     2, unused:
    0#012#011#011 bucket size:        16 -        16 (first        16)
 /usr/local/sbin/opensips[215175]: hash =   3 fragments no.:     1, unused:
    0#012#011#011 bucket size:        24 -        24 (first        24)
 /usr/local/sbin/opensips[215175]: hash =  16 fragments no.:     1, unused:
    0#012#011#011 bucket size:       128 -       128 (first       128)
 /usr/local/sbin/opensips[215175]: hash = 2059 fragments no.:     1,
unused:     0#012#011#011 bucket size:  16777216 -  33554432 (first
 29757664)
 /usr/local/sbin/opensips[215175]: TOTAL:      5 free fragments = 29757848
free bytes
 /usr/local/sbin/opensips[215175]: TOTAL: 48 overhead
 /usr/local/sbin/opensips[215175]: -----------------------------
 /usr/local/sbin/opensips[215171]: INFO:core:shutdown_opensips: process
3(215174) [timer] terminated, still waiting for 13 more
 /usr/local/sbin/opensips[215171]: INFO:core:shutdown_opensips: process
4(215175) [SIP receiver udp:192.168.33.171:5060] terminated, still waiting
for 12 more
 /usr/local/sbin/opensips[215171]: INFO:core:shutdown_opensips: process
5(215176) [SIP receiver udp:192.168.33.171:5060] terminated, still waiting
for 11 more
 /usr/local/sbin/opensips[215171]: INFO:core:shutdown_opensips: process
1(215172) [MI FIFO] terminated, still waiting for 10 more
 /usr/local/sbin/opensips[215173]: INFO:core:sig_usr: signal 15 received
 /usr/local/sbin/opensips[215173]: Memory status (pkg):
 /usr/local/sbin/opensips[215173]: fm_status (0x7fc2907ff010):
 /usr/local/sbin/opensips[215173]: heap size= 33554432
 /usr/local/sbin/opensips[215173]: used= 229752, used+overhead=318936,
free=33324680
 /usr/local/sbin/opensips[215173]: max used (+overhead)= 385792
 /usr/local/sbin/opensips[215173]: dumping free list:
 /usr/local/sbin/opensips[215173]: hash =   7 fragments no.:   139, unused:
    0#012#011#011 bucket size:        56 -        56 (first        56)
 /usr/local/sbin/opensips[215173]: hash =  13 fragments no.:    37, unused:
    0#012#011#011 bucket size:       104 -       104 (first       104)
 /usr/local/sbin/opensips[215173]: hash =  16 fragments no.:    61, unused:
    0#012#011#011 bucket size:       128 -       128 (first       128)
 /usr/local/sbin/opensips[215173]: hash =  31 fragments no.:   152, unused:
    0#012#011#011 bucket size:       248 -       248 (first       248)
 /usr/local/sbin/opensips[215173]: hash =  68 fragments no.:    16, unused:
    0#012#011#011 bucket size:       544 -       544 (first       544)
 /usr/local/sbin/opensips[215173]: hash = 105 fragments no.:     1, unused:
    0#012#011#011 bucket size:       840 -       840 (first       840)
 /usr/local/sbin/opensips[215173]: hash = 2059 fragments no.:     1,
unused:     0#012#011#011 bucket size:  16777216 -  33554432 (first
 33168816)
 /usr/local/sbin/opensips[215173]: TOTAL:    407 free fragments = 33235496
free bytes
 /usr/local/sbin/opensips[215173]: TOTAL: 48 overhead
 /usr/local/sbin/opensips[215173]: -----------------------------
 /usr/local/sbin/opensips[215171]: INFO:core:shutdown_opensips: process
2(215173) [time_keeper] terminated, still waiting for 9 more
 /usr/local/sbin/opensips[215171]: INFO:core:cleanup: cleanup
 /usr/local/sbin/opensips[215171]: CRITICAL:core:sig_alarm_abort: BUG -
shutdown timeout triggered, dying...

*Why is the service crashing ? *

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


On Mon, Mar 11, 2024 at 11:52 AM Sasmita Panda <spanda at 3clogic.com> wrote:

> Hi All ,
>
> Mar 11 05:57:02 ip-192-168-33-171 /usr/local/sbin/opensips[213843]:
> INFO:proto_ws:mod_init: initializing WebSocket protocol
> Mar 11 05:57:03 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
> WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 100
> ms ago (now 290 ms), delaying execution
> Mar 11 05:57:03 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
> WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 200
> ms ago (now 390 ms), delaying execution
> Mar 11 05:57:03 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
> WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 300
> ms ago (now 490 ms), delaying execution
> Mar 11 05:57:03 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
> WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 400
> ms ago (now 590 ms), delaying execution
> Mar 11 05:57:03 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
> WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 500
> ms ago (now 690 ms), delaying execution
> Mar 11 05:57:03 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
> WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 600
> ms ago (now 790 ms), delaying execution
> Mar 11 05:57:03 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
> WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 700
> ms ago (now 890 ms), delaying execution
> Mar 11 05:57:03 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
> WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 800
> ms ago (now 990 ms), delaying execution
> Mar 11 05:57:03 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
> WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 900
> ms ago (now 1090 ms), delaying execution
> Mar 11 05:57:03 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
> WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 1000
> ms ago (now 1190 ms), delaying execution
> Mar 11 05:57:04 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
> WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 1100
> ms ago (now 1290 ms), delaying execution
> Mar 11 05:57:04 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
> WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 1200
> ms ago (now 1390 ms), delaying execution
> Mar 11 05:57:04 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
> WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 1300
> ms ago (now 1490 ms), delaying execution
> Mar 11 05:57:04 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
> WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 1400
> ms ago (now 1590 ms), delaying execution
> Mar 11 05:57:04 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
> WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 1500
> ms ago (now 1690 ms), delaying execution
> Mar 11 05:57:04 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
> WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 1600
> ms ago (now 1790 ms), delaying execution
> Mar 11 05:57:04 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
> WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 1700
> ms ago (now 1890 ms), delaying execution
> Mar 11 05:57:04 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
> WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 1790
> ms ago (now 1980 ms), delaying execution
> Mar 11 05:57:04 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
> WARNING:core:timer_ticker: timer task <tm-timer> already scheduled 990 ms
> ago (now 1980 ms), delaying execution
>
> *What is this warning for? Whenever I am starting my openisps service this
> warning comes . Although the service seems like it's running but it's not
> listening on the socket exposed .  How to resolve this ?*
>
> */usr/local/sbin/opensips  -V*
> version: opensips 3.2.3 (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.
> svn revision: 3831:3878
> main.c compiled on 07:52:40 Mar 29 2023 with gcc 11
>
> *cat /etc/*release*
> Amazon Linux release 2023 (Amazon Linux)
> NAME="Amazon Linux"
> VERSION="2023"
> ID="amzn"
> ID_LIKE="fedora"
> VERSION_ID="2023"
> PLATFORM_ID="platform:al2023"
> PRETTY_NAME="Amazon Linux 2023"
> ANSI_COLOR="0;33"
> CPE_NAME="cpe:2.3:o:amazon:amazon_linux:2023"
> HOME_URL="https://aws.amazon.com/linux/"
> BUG_REPORT_URL="https://github.com/amazonlinux/amazon-linux-2023"
> SUPPORT_END="2028-03-01"
> Amazon Linux release 2023 (Amazon Linux)
>
>
> *Thanks & Regards*
> *Sasmita Panda*
> *Senior Network Testing and Software Engineer*
> *3CLogic , ph:07827611765*
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240311/17773114/attachment-0001.html>

From spanda at 3clogic.com  Mon Mar 11 13:04:14 2024
From: spanda at 3clogic.com (Sasmita Panda)
Date: Mon, 11 Mar 2024 18:34:14 +0530
Subject: [OpenSIPS-Users] utimer_ticker warning in opensips 3.2
In-Reply-To: <CALf-Q45dJ=hVdJPxsB7dU1PhER4VYBnHSU+3Jn9RwrvnZ1a=Hg@mail.gmail.com>
References: <CALf-Q442AqxhLDxKt6_psUWUzcC1aGfZ9CrHvYXH_BU5GFGL2w@mail.gmail.com>
 <CALf-Q45dJ=hVdJPxsB7dU1PhER4VYBnHSU+3Jn9RwrvnZ1a=Hg@mail.gmail.com>
Message-ID: <CALf-Q45xVfjagrctOVtAqEkEhPzeVNWK9Zj7Kfh4_Xow1QjOUQ@mail.gmail.com>

Any update on this ?


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


On Mon, Mar 11, 2024 at 12:03 PM Sasmita Panda <spanda at 3clogic.com> wrote:

> With the same server configuration and opensips version I am getting below
> error as well .
>
> CRITICAL:core:fm_free: freeing already freed shm pointer (0x7fc110e0b408),
> first free: (null): (null)(0) - aborting!
>
>  /usr/local/sbin/opensips[215171]: INFO:core:handle_sigs: child process
> 215185 exited by a signal 6
>  /usr/local/sbin/opensips[215171]: INFO:core:handle_sigs: core was
> generated
>  /usr/local/sbin/opensips[215171]: INFO:core:handle_sigs: terminating due
> to SIGCHLD
>  /usr/local/sbin/opensips[215172]: Memory status (pkg):
>  /usr/local/sbin/opensips[215172]: fm_status (0x7fc2907ff010):
>  /usr/local/sbin/opensips[215174]: INFO:core:sig_usr: signal 15 received
>  /usr/local/sbin/opensips[215172]: heap size= 33554432
>  /usr/local/sbin/opensips[215174]: Memory status (pkg):
>  /usr/local/sbin/opensips[215172]: used= 3710048, used+overhead=3801344,
> free=29844384
>  /usr/local/sbin/opensips[215174]: fm_status (0x7fc2907ff010):
>  /usr/local/sbin/opensips[215172]: max used (+overhead)= 3801344
>  /usr/local/sbin/opensips[215174]: heap size= 33554432
>  /usr/local/sbin/opensips[215172]: dumping free list:
>  /usr/local/sbin/opensips[215174]: used= 229752, used+overhead=318936,
> free=33324680
>  /usr/local/sbin/opensips[215172]: hash =   1 fragments no.:     1,
> unused:     0#012#011#011 bucket size:         8 -         8 (first
> 8)
>  /usr/local/sbin/opensips[215174]: max used (+overhead)= 385792
>  /usr/local/sbin/opensips[215174]: dumping free list:
>  /usr/local/sbin/opensips[215172]: hash =  18 fragments no.:     1,
> unused:     0#012#011#011 bucket size:       144 -       144 (first
> 144)
>  /usr/local/sbin/opensips[215174]: hash =   7 fragments no.:   139,
> unused:     0#012#011#011 bucket size:        56 -        56 (first
>  56)
>  /usr/local/sbin/opensips[215172]: hash = 2059 fragments no.:     1,
> unused:     0#012#011#011 bucket size:  16777216 -  33554432 (first
>  29752936)
>  /usr/local/sbin/opensips[215174]: hash =  13 fragments no.:    37,
> unused:     0#012#011#011 bucket size:       104 -       104 (first
> 104)
>  /usr/local/sbin/opensips[215172]: TOTAL:      3 free fragments = 29753088
> free bytes
>  /usr/local/sbin/opensips[215172]: TOTAL: 48 overhead
>  /usr/local/sbin/opensips[215174]: hash =  16 fragments no.:    61,
> unused:     0#012#011#011 bucket size:       128 -       128 (first
> 128)
>  /usr/local/sbin/opensips[215172]: -----------------------------
>  /usr/local/sbin/opensips[215174]: hash =  31 fragments no.:   152,
> unused:     0#012#011#011 bucket size:       248 -       248 (first
> 248)
>  /usr/local/sbin/opensips[215174]: hash =  68 fragments no.:    16,
> unused:     0#012#011#011 bucket size:       544 -       544 (first
> 544)
>  /usr/local/sbin/opensips[215174]: hash = 105 fragments no.:     1,
> unused:     0#012#011#011 bucket size:       840 -       840 (first
> 840)
>  /usr/local/sbin/opensips[215174]: hash = 2059 fragments no.:     1,
> unused:     0#012#011#011 bucket size:  16777216 -  33554432 (first
>  33168816)
>  /usr/local/sbin/opensips[215174]: TOTAL:    407 free fragments = 33235496
> free bytes
>  /usr/local/sbin/opensips[215174]: TOTAL: 48 overhead
>  /usr/local/sbin/opensips[215174]: -----------------------------
>  /usr/local/sbin/opensips[215176]: Memory status (pkg):
>  /usr/local/sbin/opensips[215176]: fm_status (0x7fc2907ff010):
>  /usr/local/sbin/opensips[215176]: heap size= 33554432
>  /usr/local/sbin/opensips[215176]: used= 3705480, used+overhead=3796584,
> free=29848952
>  /usr/local/sbin/opensips[215176]: max used (+overhead)= 3798064
>  /usr/local/sbin/opensips[215176]: dumping free list:
>  /usr/local/sbin/opensips[215176]: hash =   2 fragments no.:     2,
> unused:     0#012#011#011 bucket size:        16 -        16 (first
>  16)
>  /usr/local/sbin/opensips[215176]: hash =   3 fragments no.:     1,
> unused:     0#012#011#011 bucket size:        24 -        24 (first
>  24)
>  /usr/local/sbin/opensips[215176]: hash =  16 fragments no.:     1,
> unused:     0#012#011#011 bucket size:       128 -       128 (first
> 128)
>  /usr/local/sbin/opensips[215175]: Memory status (pkg):
>  /usr/local/sbin/opensips[215175]: fm_status (0x7fc2907ff010):
>  /usr/local/sbin/opensips[215175]: heap size= 33554432
>  /usr/local/sbin/opensips[215176]: hash = 2059 fragments no.:     1,
> unused:     0#012#011#011 bucket size:  16777216 -  33554432 (first
>  29757664)
>  /usr/local/sbin/opensips[215175]: used= 3705480, used+overhead=3796584,
> free=29848952
>  /usr/local/sbin/opensips[215176]: TOTAL:      5 free fragments = 29757848
> free bytes
>  /usr/local/sbin/opensips[215175]: max used (+overhead)= 3798064
>  /usr/local/sbin/opensips[215176]: TOTAL: 48 overhead
>  /usr/local/sbin/opensips[215176]: -----------------------------
>  /usr/local/sbin/opensips[215175]: dumping free list:
>  /usr/local/sbin/opensips[215175]: hash =   2 fragments no.:     2,
> unused:     0#012#011#011 bucket size:        16 -        16 (first
>  16)
>  /usr/local/sbin/opensips[215175]: hash =   3 fragments no.:     1,
> unused:     0#012#011#011 bucket size:        24 -        24 (first
>  24)
>  /usr/local/sbin/opensips[215175]: hash =  16 fragments no.:     1,
> unused:     0#012#011#011 bucket size:       128 -       128 (first
> 128)
>  /usr/local/sbin/opensips[215175]: hash = 2059 fragments no.:     1,
> unused:     0#012#011#011 bucket size:  16777216 -  33554432 (first
>  29757664)
>  /usr/local/sbin/opensips[215175]: TOTAL:      5 free fragments = 29757848
> free bytes
>  /usr/local/sbin/opensips[215175]: TOTAL: 48 overhead
>  /usr/local/sbin/opensips[215175]: -----------------------------
>  /usr/local/sbin/opensips[215171]: INFO:core:shutdown_opensips: process
> 3(215174) [timer] terminated, still waiting for 13 more
>  /usr/local/sbin/opensips[215171]: INFO:core:shutdown_opensips: process
> 4(215175) [SIP receiver udp:192.168.33.171:5060] terminated, still
> waiting for 12 more
>  /usr/local/sbin/opensips[215171]: INFO:core:shutdown_opensips: process
> 5(215176) [SIP receiver udp:192.168.33.171:5060] terminated, still
> waiting for 11 more
>  /usr/local/sbin/opensips[215171]: INFO:core:shutdown_opensips: process
> 1(215172) [MI FIFO] terminated, still waiting for 10 more
>  /usr/local/sbin/opensips[215173]: INFO:core:sig_usr: signal 15 received
>  /usr/local/sbin/opensips[215173]: Memory status (pkg):
>  /usr/local/sbin/opensips[215173]: fm_status (0x7fc2907ff010):
>  /usr/local/sbin/opensips[215173]: heap size= 33554432
>  /usr/local/sbin/opensips[215173]: used= 229752, used+overhead=318936,
> free=33324680
>  /usr/local/sbin/opensips[215173]: max used (+overhead)= 385792
>  /usr/local/sbin/opensips[215173]: dumping free list:
>  /usr/local/sbin/opensips[215173]: hash =   7 fragments no.:   139,
> unused:     0#012#011#011 bucket size:        56 -        56 (first
>  56)
>  /usr/local/sbin/opensips[215173]: hash =  13 fragments no.:    37,
> unused:     0#012#011#011 bucket size:       104 -       104 (first
> 104)
>  /usr/local/sbin/opensips[215173]: hash =  16 fragments no.:    61,
> unused:     0#012#011#011 bucket size:       128 -       128 (first
> 128)
>  /usr/local/sbin/opensips[215173]: hash =  31 fragments no.:   152,
> unused:     0#012#011#011 bucket size:       248 -       248 (first
> 248)
>  /usr/local/sbin/opensips[215173]: hash =  68 fragments no.:    16,
> unused:     0#012#011#011 bucket size:       544 -       544 (first
> 544)
>  /usr/local/sbin/opensips[215173]: hash = 105 fragments no.:     1,
> unused:     0#012#011#011 bucket size:       840 -       840 (first
> 840)
>  /usr/local/sbin/opensips[215173]: hash = 2059 fragments no.:     1,
> unused:     0#012#011#011 bucket size:  16777216 -  33554432 (first
>  33168816)
>  /usr/local/sbin/opensips[215173]: TOTAL:    407 free fragments = 33235496
> free bytes
>  /usr/local/sbin/opensips[215173]: TOTAL: 48 overhead
>  /usr/local/sbin/opensips[215173]: -----------------------------
>  /usr/local/sbin/opensips[215171]: INFO:core:shutdown_opensips: process
> 2(215173) [time_keeper] terminated, still waiting for 9 more
>  /usr/local/sbin/opensips[215171]: INFO:core:cleanup: cleanup
>  /usr/local/sbin/opensips[215171]: CRITICAL:core:sig_alarm_abort: BUG -
> shutdown timeout triggered, dying...
>
> *Why is the service crashing ? *
>
> *Thanks & Regards*
> *Sasmita Panda*
> *Senior Network Testing and Software Engineer*
> *3CLogic , ph:07827611765*
>
>
> On Mon, Mar 11, 2024 at 11:52 AM Sasmita Panda <spanda at 3clogic.com> wrote:
>
>> Hi All ,
>>
>> Mar 11 05:57:02 ip-192-168-33-171 /usr/local/sbin/opensips[213843]:
>> INFO:proto_ws:mod_init: initializing WebSocket protocol
>> Mar 11 05:57:03 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
>> WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 100
>> ms ago (now 290 ms), delaying execution
>> Mar 11 05:57:03 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
>> WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 200
>> ms ago (now 390 ms), delaying execution
>> Mar 11 05:57:03 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
>> WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 300
>> ms ago (now 490 ms), delaying execution
>> Mar 11 05:57:03 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
>> WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 400
>> ms ago (now 590 ms), delaying execution
>> Mar 11 05:57:03 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
>> WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 500
>> ms ago (now 690 ms), delaying execution
>> Mar 11 05:57:03 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
>> WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 600
>> ms ago (now 790 ms), delaying execution
>> Mar 11 05:57:03 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
>> WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 700
>> ms ago (now 890 ms), delaying execution
>> Mar 11 05:57:03 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
>> WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 800
>> ms ago (now 990 ms), delaying execution
>> Mar 11 05:57:03 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
>> WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 900
>> ms ago (now 1090 ms), delaying execution
>> Mar 11 05:57:03 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
>> WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 1000
>> ms ago (now 1190 ms), delaying execution
>> Mar 11 05:57:04 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
>> WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 1100
>> ms ago (now 1290 ms), delaying execution
>> Mar 11 05:57:04 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
>> WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 1200
>> ms ago (now 1390 ms), delaying execution
>> Mar 11 05:57:04 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
>> WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 1300
>> ms ago (now 1490 ms), delaying execution
>> Mar 11 05:57:04 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
>> WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 1400
>> ms ago (now 1590 ms), delaying execution
>> Mar 11 05:57:04 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
>> WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 1500
>> ms ago (now 1690 ms), delaying execution
>> Mar 11 05:57:04 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
>> WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 1600
>> ms ago (now 1790 ms), delaying execution
>> Mar 11 05:57:04 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
>> WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 1700
>> ms ago (now 1890 ms), delaying execution
>> Mar 11 05:57:04 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
>> WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 1790
>> ms ago (now 1980 ms), delaying execution
>> Mar 11 05:57:04 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
>> WARNING:core:timer_ticker: timer task <tm-timer> already scheduled 990 ms
>> ago (now 1980 ms), delaying execution
>>
>> *What is this warning for? Whenever I am starting my openisps service
>> this warning comes . Although the service seems like it's running but it's
>> not listening on the socket exposed .  How to resolve this ?*
>>
>> */usr/local/sbin/opensips  -V*
>> version: opensips 3.2.3 (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.
>> svn revision: 3831:3878
>> main.c compiled on 07:52:40 Mar 29 2023 with gcc 11
>>
>> *cat /etc/*release*
>> Amazon Linux release 2023 (Amazon Linux)
>> NAME="Amazon Linux"
>> VERSION="2023"
>> ID="amzn"
>> ID_LIKE="fedora"
>> VERSION_ID="2023"
>> PLATFORM_ID="platform:al2023"
>> PRETTY_NAME="Amazon Linux 2023"
>> ANSI_COLOR="0;33"
>> CPE_NAME="cpe:2.3:o:amazon:amazon_linux:2023"
>> HOME_URL="https://aws.amazon.com/linux/"
>> BUG_REPORT_URL="https://github.com/amazonlinux/amazon-linux-2023"
>> SUPPORT_END="2028-03-01"
>> Amazon Linux release 2023 (Amazon Linux)
>>
>>
>> *Thanks & Regards*
>> *Sasmita Panda*
>> *Senior Network Testing and Software Engineer*
>> *3CLogic , ph:07827611765*
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240311/0c3e7337/attachment-0001.html>

From spanda at 3clogic.com  Tue Mar 12 08:57:46 2024
From: spanda at 3clogic.com (Sasmita Panda)
Date: Tue, 12 Mar 2024 14:27:46 +0530
Subject: [OpenSIPS-Users] Need some help on opensips error for wss handshek .
Message-ID: <CALf-Q44nYwthB2z=ignY9uXwrEWhb6tgrXom24v2HwXFDd7UoA@mail.gmail.com>

Hi All ,

1"  :callID 080a9ef8-3911-6c41-689c-fbb5d02e3aae
Mar 12 08:23:11 localhost /usr/sbin/opensips[12987]: ERROR:core:parse_via:
bad char <1> on state 100
Mar 12 08:23:11 localhost /usr/sbin/opensips[12987]: ERROR:core:parse_via:
 <1.1 p1wsa01.rivagecapital.com:80 (Cisco-WSA/12.5.4-011)#015#012#015#012>
Mar 12 08:23:11 localhost /usr/sbin/opensips[12987]: ERROR:core:parse_via:
via parse failed
Mar 12 08:23:11 localhost /usr/sbin/opensips[12987]:
ERROR:core:get_hdr_field: bad via
Mar 12 08:23:11 localhost /usr/sbin/opensips[12987]:
INFO:core:parse_headers: bad header field
Mar 12 08:23:11 localhost /usr/sbin/opensips[12987]:
ERROR:proto_wss:ws_parse_req_handshake: cannot parse headers#012Upgrade:
websocket#015#012Connection: Upgrade#015#012Host:
ir-webrtc2.3ccloud.com#015#012Pragma: no-cache#015#012Cache-Control:
no-cache#015#012User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64)
AppleWebKit/537.36 (KHTML, like Gecko) Chrome/122.0.0.0 Safari/537.36 Edg/
122.0.0.0#015#012Origin:
https://ir-static.3ccloud.com#015#012Sec-WebSocket-Version:
13#015#012Accept-Encoding: gzip, br#015#012Accept-Language:
en-GB,en;q=0.9,en-US;q=0.8#015#012Sec-WebSocket-Key:
I/8XqtXyBCAGorZYjnTYQA==#015#012Sec-WebSocket-Extensions:
permessage-deflate; client_max_window_bits#015#012Sec-WebSocket-Protocol:
sip#015#012X-IMForwards: 20#015#012Via: 1.1 p1wsa01.rivagecapital.com:80
(Cisco-WSA/12.5.4-011)#015#012#015#012


 I am getting this error on my opensips server where I am running webrtc .
What is this error for ?


*Thanks & Regards*
*Sasmita Panda*
*Senior Network Testing and Software Engineer*
*3CLogic , ph:07827611765*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240312/9b388f91/attachment.html>

From alain.bieuzent at free.fr  Tue Mar 12 12:57:49 2024
From: alain.bieuzent at free.fr (Alain Bieuzent)
Date: Tue, 12 Mar 2024 13:57:49 +0100
Subject: [OpenSIPS-Users] OPENSIP 3.4 send_reply and tight matching failed
In-Reply-To: <84BD48FD-8F95-4798-8201-7F87E54DAE4C@free.fr>
References: <84BD48FD-8F95-4798-8201-7F87E54DAE4C@free.fr>
Message-ID: <858EE736-AF3A-46A4-8EBC-8ABF8BC30A8E@free.fr>

Hi all,

 

I am in the process of migrating my proxies from 3.3.9 to 3.4.4.

In 3.4 I find myself with a fault when I try to rewrite a final cause.

 

if (t_check_status("500"))

         {

                          send_reply(503,"Service Unavailable");

                         exit;

          }

 

with 3.3 version, this code works perfectly, since 3.4 I have this error:

 

WARNING:dialog:dlg_onroute: tight matching failed for ACK with callid='67457c401e9ea52e2750100979253a7a at 10.101.180.177:5060'/52, ftag='as5328cea7'/10, ttag='b5a7-2a346bb9d510da893a ee7cda850584cb'/37 and direction=1

WARNING:dialog:dlg_onroute: dialog identification elements are callid='67457c401e9ea52e2750100979253a7a at 10.101.180.177:5060'/52, caller tag='as5328cea7'/10, callee tag='3919223738-770090972'/ 20

 

Has anyone encountered this error before?

 

Complete traces here : https://www.transfernow.net/dl/20240312qvAFfIAL.

 

Regards

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240312/3cdd7ccf/attachment.html>

From johnkiniston at gmail.com  Tue Mar 12 15:41:24 2024
From: johnkiniston at gmail.com (John Kiniston)
Date: Tue, 12 Mar 2024 08:41:24 -0700
Subject: [OpenSIPS-Users] Consultant needed
Message-ID: <34A538EF-7874-4A79-A91C-5347C5A63B69@gmail.com>

Please contact me off list.

I am looking for a consultant to upgrade a legacy opensips script to the current stable release and to add STIR/Shaken to it.

This is a single one time task that is needed, not a regular position.
Sent from my iPhone

From osas at voipembedded.com  Tue Mar 12 15:48:50 2024
From: osas at voipembedded.com (Ovidiu Sas)
Date: Tue, 12 Mar 2024 11:48:50 -0400
Subject: [OpenSIPS-Users] Consultant needed
In-Reply-To: <34A538EF-7874-4A79-A91C-5347C5A63B69@gmail.com>
References: <34A538EF-7874-4A79-A91C-5347C5A63B69@gmail.com>
Message-ID: <CAND0Lkur4MswzZ11uJecFbcD6pOhJxAmqpN03FV0UyrHUSBQMA@mail.gmail.com>

Hello John,

We can have a short talk to see how we can move this forward.
I am reachable at +1-416-454-2289.
I’m located in Toronto, Canada.

Thanks,
Ovidiu

On Tue, Mar 12, 2024 at 11:42 John Kiniston <johnkiniston at gmail.com> wrote:

> Please contact me off list.
>
> I am looking for a consultant to upgrade a legacy opensips script to the
> current stable release and to add STIR/Shaken to it.
>
> This is a single one time task that is needed, not a regular position.
> Sent from my iPhone
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240312/48f62a01/attachment.html>

From stefan.carlsson at tetab.nu  Tue Mar 12 17:18:32 2024
From: stefan.carlsson at tetab.nu (Stefan Carlsson)
Date: Tue, 12 Mar 2024 17:18:32 +0000
Subject: [OpenSIPS-Users] Regex help.
Message-ID: <b70c1bd106d14b65848fbc980cef4c8b@tetab.nu>

Hi !

What is the easiest form to transform this:

o=SYS   1710262255    1710262255    IN    IP4     123.123.123.123

Into

SYS;1710262255;1710262255;IN;IP4;123.123.123.123

for later retrieval via an index function.

[0] = SYS
[1] = 1710262255
[2] = 1710262255
[3] = IN

etc ....



I need to get my hands on the session parameters ...


Thanks in advance ...


//S
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240312/f0f533b6/attachment.html>

From rvg at rvgeerligs.nl  Wed Mar 13 09:27:31 2024
From: rvg at rvgeerligs.nl (rvg at rvgeerligs.nl)
Date: Wed, 13 Mar 2024 09:27:31 +0000
Subject: [OpenSIPS-Users] push notifications opensips 3.4
Message-ID: <efa7092b40dd2bf3ffc9cac6dc1391d7c0e77f15@rvgeerligs.nl>

Hi All,

I still have problems with opensips3.4 push notifications:

Somehow INVITEs keep looping and get rejected.

Code:
...
route{

...

if (has_totag()) {

...

if (!is_method("ACK"))
        async (pn_process_purr("location"), resume_route);

...
}

...

# do lookup with method filtering

#--
lookup("location", "method-filtering");
$var(rc) = $retcode;
switch ($var(rc)) {
case 1:
    # we found at least 1 non-PN contact!
xlog("L_INFO", "DBG: 1 contacts found non-PN ($var(rc))\n");
    $var(do_relay) = true;
    break;
case 2:
    # success, but all contacts are PN-enabled, so we're
    # sending PNs / awaiting re-registrations from them
xlog("L_INFO", "DBG: contacts found send PN? ($var(rc))\n");
    $var(do_relay) = false;
    #$avp(skip_relay) = true;
    break;
default:
    xlog("L_INFO", "DBG: no contacts found ($var(rc))\n");
    t_reply(404, "Not Found");
    exit;
}

if ($var(do_relay) && !t_relay())
    send_reply(500, "Internal Server Error");

...

if($var(do_relay) == true)
route(relay);
}

...

from log (looping log, it repeats untill server REJECT the INVITE or until CANCEL):

DBG:core:parse_headers: this is the first via
2024-03-09T09:41:13.485706+00:00 xsp2 /usr/local/sbin/opensips[2061136]: DBG:core:_parse_to: end of header reached, state=10
2024-03-09T09:41:13.485748+00:00 xsp2 /usr/local/sbin/opensips[2061136]: DBG:core:_parse_to: display={}, ruri={sip:to at dummy.com}
2024-03-09T09:41:13.485807+00:00 xsp2 /usr/local/sbin/opensips[2061136]: DBG:core:get_hdr_field: <To> [20]; uri=[sip:to at dummy.com]
2024-03-09T09:41:13.485854+00:00 xsp2 /usr/local/sbin/opensips[2061136]: DBG:core:get_hdr_field: to body [<sip:to at dummy.com>#015#012]
2024-03-09T09:41:13.485915+00:00 xsp2 /usr/local/sbin/opensips[2061136]: DBG:core:get_hdr_field: cseq <CSeq>: <1>

2024-03-09T09:41:13.485962+00:00 xsp2 /usr/local/sbin/opensips[2061136]: DBG:core:get_hdr_field: found end of header
2024-03-09T09:41:13.486040+00:00 xsp2 /usr/local/sbin/opensips[2061136]: DBG:core:parse_headers: flags=ffffffffffffffff
2024-03-09T09:41:13.486088+00:00 xsp2 /usr/local/sbin/opensips[2061136]: DBG:core:get_dummy_sip_msg: setting as static to 0xffffb1a612c0
2024-03-09T09:41:13.486145+00:00 xsp2 /usr/local/sbin/opensips[2061136]: DBG:core:evi_raise_event_msg: found subscriber E_UL_CONTACT_REFRESH
2024-03-09T09:41:13.486207+00:00 xsp2 /usr/local/sbin/opensips[2061136]: DBG:core:dup_ref_script_route_in_shm: dupping 0xffffaa264f60 [E_UL_CONTACT_REFRESH], idx 1, ver/cnt 1, to new 0xffffaa26d9e0 [E_UL_CONTACT_REFRESH], idx 1, ver/cnt 1
2024-03-09T09:41:13.486283+00:00 xsp2 /usr/local/sbin/opensips[2061136]: DBG:core:release_dummy_sip_msg: cleaning the static sip msg 0xffffb1a612c0
2024-03-09T09:41:13.486352+00:00 xsp2 /usr/local/sbin/opensips[2061136]: DBG:core:destroy_avp_list: destroying list (nil)
2024-03-09T09:41:13.486409+00:00 xsp2 /usr/local/sbin/opensips[2061136]: DBG:core:ipc_handle_job: received job type 0[RPC] from process 6
2024-03-09T09:41:13.486467+00:00 xsp2 /usr/local/sbin/opensips[2061136]: DBG:core:get_dummy_sip_msg: reusing the static sip msg 0xffffb1a612c0
2024-03-09T09:41:13.486533+00:00 xsp2 /usr/local/sbin/opensips[2061136]: DBG:core:parse_params: Parsing params for:[sip:rvg at 82.151.164.77:57775;pn-prid=F1B7F53A99A35254A55CCAE2EDF80C1FAE12F353592BB6ED203ADA0175E34AD9:voip;pn-provider=apns;pn-param=ABCD1234.cllkit.voip;pn-silent=1;pn-timeout=0;transport=udp]
2024-03-09T09:41:13.486571+00:00 xsp2 /usr/local/sbin/opensips[2061136]: ERROR: -- ** --pn_send was called sip:user at dummy.com
2024-03-09T09:41:13.486651+00:00 xsp2 /usr/local/sbin/opensips[2061136]: ERROR:core:route_param_get: route $param variable accepts only integer indexes
2024-03-09T09:41:13.486746+00:00 xsp2 /usr/local/sbin/opensips[2061136]: message repeated 2 times: [ ERROR:core:route_param_get: route $param variable accepts only integer indexes]
2024-03-09T09:41:13.486787+00:00 xsp2 /usr/local/sbin/opensips[2061136]: ERROR:pn params:  <null>,#012                   ,#012                  

2024-03-09T09:41:13.486822+00:00 xsp2 /usr/local/sbin/opensips[2061136]: DBG:core:release_dummy_sip_msg: cleaning the static sip msg 0xffffb1a612c0
2024-03-09T09:41:13.486913+00:00 xsp2 /usr/local/sbin/opensips[2061136]: DBG:core:destroy_avp_list: destroying list (nil)
2024-03-09T09:41:13.697168+00:00 xsp2 /usr/local/sbin/opensips[2061135]: DBG:core:parse_msg: SIP Request:

Any advice appreciated, regards,

Ronald Geerligs
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240313/99c600eb/attachment-0001.html>

From social at bohboh.info  Wed Mar 13 14:15:50 2024
From: social at bohboh.info (Social Boh)
Date: Wed, 13 Mar 2024 09:15:50 -0500
Subject: [OpenSIPS-Users] OpenSIPs generate PRACK
In-Reply-To: <be15bfd5-364b-4c32-8343-05ead701e7e4@opensips.org>
References: <476be849-afbe-4d69-9218-f80bd27022ad@bohboh.info>
 <e880a151-5bca-443e-8216-16b80b4ff067@bohboh.info>
 <CAJTkRNtNYHe2Sid19y0sw8d457j3iCwoJHOjOpjYD4tZU-ekbA@mail.gmail.com>
 <49eb93af-dd10-4fae-82bd-1d19edca403a@opensips.org>
 <fd54ef29-8dfe-4a01-9ac2-ecfef090d47c@bohboh.info>
 <be15bfd5-364b-4c32-8343-05ead701e7e4@opensips.org>
Message-ID: <e44919b5-96c8-4998-bf94-a4cec0c099f2@bohboh.info>

Hello,

two questions about mi_script module:

 1. I don't understand well this sentence: "Moreover, if the running MI
    /command / is configured to run in asynchronous mode (such as
    /t_uac_dlg/ the command blocks in a busy waiting manner until the
    response is received." can I or I can't use t_uac_dlg in
    asynchronous mode?
 2. Can I indicate more than un parameters in the line like:
      * $avp(params) = "method","callid","From:";

  * or is one value for line? Same for $avp(vals)

Thank you

Regards

---
I'm SoCIaL, MayBe

El 26/02/2024 a las 7:43 a. m., Bogdan-Andrei Iancu escribió:
> yes, you can use the b2b_logic (together with b2b_entities) for that, 
> but it may be a too heavy tool for the purpose. Maybe you can try to 
> generate the PRACK from OpenSIPS level by using the t_uac_dlg MI 
> function [1] via the mi_script module [2] - basically to trigger that 
> MI cmd from the onreply_route, when receiving the 180 reply.
>
> [1] https://opensips.org/html/docs/modules/3.4.x/tm.html#mi_t_uac_dlg
> [2] https://opensips.org/html/docs/modules/3.4.x/mi_script.html#afunc_mi
>
> Regards,
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>    https://www.opensips-solutions.com
>    https://www.siphub.com
> On 25.02.2024 14:54, Social Boh wrote:
>>
>> I know the best way is the original caller handle and reply the 183, 
>> but I HAVE to do this at OpenSIPs level.
>>
>> Can I use B2B_Entities and B2B_logic to do this? Is there a scenario 
>> to use tu parse and reply the 183?
>>
>> Thank you
>>
>> ---
>> I'm SoCIaL, MayBe
>> El 16/02/2024 a las 11:31 a. m., Bogdan-Andrei Iancu escribió:
>>> I agree here, the 183 must be relayed back to the original caller 
>>> (which generate the received INVITE) and let it do the PRACK - this 
>>> confirmation must be end-2-end in the dialog.
>>>
>>> Regards,
>>> Bogdan-Andrei Iancu
>>>
>>> OpenSIPS Founder and Developer
>>>    https://www.opensips-solutions.com
>>>    https://www.siphub.com
>>> On 12.02.2024 11:36, Ihor Olkhovskyi wrote:
>>>> You should relay 183 to original source (ione that is sending 
>>>> INVITE) and got PRACK from there.
>>>> That would be the most correct way of handling this
>>>>
>>>> Le lun. 12 févr. 2024 à 02:29, Social Boh <social at bohboh.info> a 
>>>> écrit :
>>>>
>>>>     Maybe someone can help me.
>>>>
>>>>     This is the scenario.
>>>>
>>>>     OpenSIPs receive a INVITE and send it to a server that reply
>>>>     with a 302
>>>>     message (always)
>>>>
>>>>     Then OpenSIPs, in the failure route, take the user part present
>>>>     in the
>>>>     302 contact header, change the destination IP and send with t_relay
>>>>
>>>>     The destination reply with a 183 with Require: 100rel header so
>>>>     OpenSIPs
>>>>     have to reply with a PRACK. This is my problem.
>>>>
>>>>     I don't know which is the best way to handle this (the PRACK)
>>>>
>>>>     Thank you
>>>>
>>>>     Regards
>>>>
>>>>     ---
>>>>     I'm SoCIaL, MayBe
>>>>
>>>>     El 9/02/2024 a las 6:46 a. m., Social Boh escribió:
>>>>     > Hello list,
>>>>     >
>>>>     > can OpenSIPs generate a PRACK message to reply a 180/183 message?
>>>>     >
>>>>     > Thank you
>>>>     >
>>>>     > Regards
>>>>     >
>>>>     > ---
>>>>     > I'm SoCIaL, MayBe
>>>>     >
>>>>     >
>>>>     > _______________________________________________
>>>>     > Users mailing list
>>>>     > Users at lists.opensips.org
>>>>     > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>>
>>>>     _______________________________________________
>>>>     Users mailing list
>>>>     Users at lists.opensips.org
>>>>     http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>>
>>>>
>>>>
>>>> -- 
>>>> Best regards,
>>>> Ihor (Igor)
>>>>
>>>> _______________________________________________
>>>> Users mailing list
>>>> Users at lists.opensips.org
>>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>
>>>
>>> _______________________________________________
>>> Users mailing list
>>> Users at lists.opensips.org
>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240313/4fb59150/attachment.html>

From stefan.carlsson at tetab.nu  Wed Mar 13 15:19:16 2024
From: stefan.carlsson at tetab.nu (Stefan Carlsson)
Date: Wed, 13 Mar 2024 15:19:16 +0000
Subject: [OpenSIPS-Users] How to change the a=sendrecv in SDP
Message-ID: <f1bd56fb725541aa88a2e6e87b6025c0@tetab.nu>

Hi (again ...)

I've found out how to strip out the o= to separate values ...  but now I want to change the a=sendrecv to a=sendonly

The cause is  that our pbx's don't conform to either RFC2543 hold type: null connection IP detected,  nor RFC3264 hold type: inactive or sendonly attributes detected
but use the RFC5359 re-invite indicating call hold via session version incremented by  1.

So now I've trying to make a workaround with the help of OpenSips ..

Can you please help me with that ...

// Regards ...

Stefan Carlsson

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240313/80bf89bc/attachment.html>

From bogdan at opensips.org  Wed Mar 13 16:05:13 2024
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Wed, 13 Mar 2024 18:05:13 +0200
Subject: [OpenSIPS-Users] [Blog] The SQL support, reloaded (in OpenSIPS 3.5)
Message-ID: <d9387c7e-7765-4616-b34b-902f83565069@opensips.org>


Born from the AVPops ashes, the SQLops module is here to provide JSON 
structured SQL querying capabilities, from script level, with prepared 
statements support and many other facilities and boosts 😍. Read all 
about this

     https://blog.opensips.org/2024/03/13/the-sql-support-reloaded/

Enjoy,

-- 
Bogdan-Andrei Iancu

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



From prathibhab.tvm at gmail.com  Thu Mar 14 04:16:19 2024
From: prathibhab.tvm at gmail.com (Prathibha B)
Date: Thu, 14 Mar 2024 09:46:19 +0530
Subject: [OpenSIPS-Users] SDP
Message-ID: <CAJh_-cBOLA_zfLWrfYqX2rb8divky_JBt1ekyNDzSpH9-2_gYg@mail.gmail.com>

How to see the SDP in opensips?

-- 
Regards,
B.Prathibha
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240314/728c5eb3/attachment-0001.html>

From stefan.carlsson at tetab.nu  Thu Mar 14 07:50:54 2024
From: stefan.carlsson at tetab.nu (Stefan Carlsson)
Date: Thu, 14 Mar 2024 07:50:54 +0000
Subject: [OpenSIPS-Users] SDP
In-Reply-To: <CAJh_-cBOLA_zfLWrfYqX2rb8divky_JBt1ekyNDzSpH9-2_gYg@mail.gmail.com>
References: <CAJh_-cBOLA_zfLWrfYqX2rb8divky_JBt1ekyNDzSpH9-2_gYg@mail.gmail.com>
Message-ID: <c8530347bc2844ed9341aa1ab7b6ff0e@tetab.nu>

Hi !

You can use the module sipmsgops to view and change some of the ADP fields such as codecs and streams … but unfortunately you don’t have
complete control of the SDP compared to what it seems could be done on the Kamailio SIP router

I need to change the a=sendrecv field and it seems to be impossible  ☹

Regards …
_________________________________
Stefan Carlsson

From: Users <users-bounces at lists.opensips.org> On Behalf Of Prathibha B
Sent: Thursday, 14 March, 2024 05:16
To: OpenSIPS users mailling list <users at lists.opensips.org>
Subject: [OpenSIPS-Users] SDP

How to see the SDP in opensips?

--
Regards,
B.Prathibha
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240314/2c9acc90/attachment.html>

From social at bohboh.info  Thu Mar 14 17:56:30 2024
From: social at bohboh.info (Social Boh)
Date: Thu, 14 Mar 2024 12:56:30 -0500
Subject: [OpenSIPS-Users] bad uri, state 0 parsed: <$avp> (4) / <$avp(r)> (7)
Message-ID: <ea2ddb3e-d10c-4e26-a150-85d64ccee07c@bohboh.info>

Hello,

any hint with this error:

ERROR:core:parse_uri: bad uri, state 0 parsed: <$avp> (4) / <$avp(r)> (7)

The lines are:

$avp(params) = "ruri";
$avp(vals) = "$avp(r)";:

on onreply route

$avp(r) contain the request uri created on the failure route.

Regards

-- 
---
I'm SoCIaL, MayBe



From rvg at rvgeerligs.nl  Fri Mar 15 10:32:28 2024
From: rvg at rvgeerligs.nl (rvg at rvgeerligs.nl)
Date: Fri, 15 Mar 2024 10:32:28 +0000
Subject: [OpenSIPS-Users] push notifications - and now packages failing
Message-ID: <97c15b957d318b515d97e1c3778bf4f6c32c05b5@rvgeerligs.nl>

Hi all,

Maybe I thought wrong and I tried another system with AMD-INTEL architecture.

Desperate I started to install packages.





The following packages have unmet dependencies:



mediaproxy-common : Depends: python3 (< 3.9) but 3.10.6-1~22.04 is to be installed



E: Unable to correct problems, you have held broken packages.



Any advice is appreciated

Regards,

Ronald
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240315/1d621d6d/attachment.html>

From Calin.Dragan at garmin.com  Fri Mar 15 11:03:48 2024
From: Calin.Dragan at garmin.com (Dragan, Calin)
Date: Fri, 15 Mar 2024 11:03:48 +0000
Subject: [OpenSIPS-Users] Freeswitch integration
Message-ID: <BN8PR04MB5779A7B6308F1D401726ED2EF3282@BN8PR04MB5779.namprd04.prod.outlook.com>

Hi,

I'm trying to use Freeswitch as a media server with Opensips as a load balancer, I need something very basic for a POC. (I configured the load balancer and dispatcher based on old information found here: https://developer.signalwire.com/freeswitch/FreeSWITCH-Explained/Enterprise-Deployment/Enterprise-deployment-OpenSIPS_13173169/#freeswitch-configuration, here: https://developer.signalwire.com/freeswitch/FreeSWITCH-Explained/Auxiliary-Knowledge-and-Utilities/OpenSIPS-configuration-for-2-or-more-FreeSWITCH-installs_13173462/ and here: https://www.opensips.org/Documentation/Tutorials-OpenSIPSFreeSwitchIntegration)

I'm adding the X-Auth-IP header to the requests like this (this is based on the config that ships with the 3.4.x release in the docker image, so I guessed that this is where I should add the header):

route[relay] {
               # for INVITEs enable some additional helper routes
               if (is_method("INVITE")) {
                                remove_hf("X-Auth-IP");
                               append_hf("X-Auth-IP: $si\r\n");
                               append_to_reply("X-Auth-IP: $si\r\n");
                               xlog("L_INFO", "$ci|log|X-Auth-IP: $si\n");
                               xlog("L_INFO", "SIP Message: $mb");

                              t_on_failure("missed_call");
                              t_on_branch("per_branch_ops");
                              t_on_reply("handle_nat");
               }

               if (!t_relay()) {
                              send_reply(500,"Internal Error");
               }
               exit;
}

On the freeswitch side I added the IP set by opensips in the list of allowed addresses.

Now, with or without authentication enabled on the Freeswitch side (i.e. regardless of what I set in the "auth-calls" param, or if I enable the accept-blind-auth), or even whether the Freeswitch is running or not, when I try to place a call from/to some registerd addresses, I get the "407 Proxy authentication required" response.

Could you please give me some hints on what I might be doing wrong, or direct me to a contemporary tutorial?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240315/b3f25f6c/attachment.html>

From rodrigopassos at gmail.com  Fri Mar 15 17:35:34 2024
From: rodrigopassos at gmail.com (Rodrigo R Passos)
Date: Fri, 15 Mar 2024 14:35:34 -0300
Subject: [OpenSIPS-Users] TLS - Private Key fails
Message-ID: <CAF9oA8=paVY5gszDNiBomwUvFY1kJsBUa+i6zaB=je37o_9S=A@mail.gmail.com>

Hi everyone,


I'm trying to start opensips with a certificate generated by opensips-cli,
like a tutorial. I have the following results keys after completing the
command.

INFO: user certificate created in /etc/opensips/tls/user/wss-cert.pem

INFO: user private key created in /etc/opensips/tls/user/wss-privkey.pem

INFO: user CA list (chain of trust) created in
/etc/opensips/tls/user/wss-calist.pem


This is my configuration, in opensips.cfg:

modparam("tls_mgm", "server_domain", "wss")
modparam("tls_mgm", "match_ip_address","[wss]10.0.0.114:5443")
modparam("tls_mgm", "ca_dir", "[wss]/etc/opensips/tls/rootCA/certs")
modparam("tls_mgm", "ca_list", "[wss]/etc/opensips/tls/user/wss-calist.pem")
modparam("tls_mgm",
"certificate","[wss]/etc/opensips/tls/user/wss-cert.pem")
modparam("tls_mgm",
"private_key","[wss]/etc/opensips/tls/user/wss-privkey.pem")
modparam("tls_mgm", "verify_cert", "[wss]0")
modparam("tls_mgm", "require_cert", "[wss]0")
modparam("tls_mgm", "ciphers_list", "[wss]NULL")
modparam("tls_mgm", "tls_method", "[wss]TLSv1")


So, when I start opensips, the log shows information saying the private key
doesn't match with the public key. Follow the log:


Mar 15 14:27:14 esbc01 opensips[80845]: Mar 15 14:27:14 [80845]
ERROR:tls_openssl:load_private_key: unable to load private key file
'/etc/opensips/tls/user/wss-privkey.pem'.

Mar 15 14:27:14 esbc01 opensips[80845]: Retry (2 left) (check password case)

Mar 15 14:27:14 esbc01 opensips[80845]: Mar 15 14:27:14 [80845]
ERROR:tls_openssl:load_private_key: key
'/etc/opensips/tls/user/wss-privkey.pem' does not match the public key of
the certificate

Mar 15 14:27:14 esbc01 opensips[80845]: Mar 15 14:27:14 [80845]
ERROR:tls_mgm:init_tls_domains: Failed to init TLS domain 'wss'

Mar 15 14:27:14 esbc01 opensips[80845]: Mar 15 14:27:14 [80845]
ERROR:core:init_mod: failed to initialize module tls_mgm

Mar 15 14:27:14 esbc01 opensips[80845]: Mar 15 14:27:14 [80845]
ERROR:core:main: error while initializing modules



All procedures to create my own certificate follow the tutorial.


Anyone know what is happening or have any problems like me?


BR


RP
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240315/2e702093/attachment.html>

From stefan.carlsson at tetab.nu  Fri Mar 15 18:27:46 2024
From: stefan.carlsson at tetab.nu (Stefan Carlsson)
Date: Fri, 15 Mar 2024 18:27:46 +0000
Subject: [OpenSIPS-Users] Problems with new installation of 3.4
Message-ID: <9f9c64521006491ab59d3cdb585e8849@tetab.nu>

Hi !

After followed the installation of 3.4 LTS to a fresh ubuntu ver 22 a found some serious problems ...

installing is done via apt.

1) Not all the modules were included in the rep. as it should ref. to spec. vers.  manual

2) After downloading the source , trying to compile the modules missing...  dependencies needed and info is missing in the main doc. or moduledoc.

For example:

make: *** No rule to make target '../../lib/digest_auth/libdigest_auth.a', needed by 'uac_auth.so'.  Stop.

trying to make all from opensips src. root folder ...

Compiling main.c
In file included from main.c:152:
ssl_tweaks.h:2:10: fatal error: openssl/opensslv.h: No such file or directory


Any ideas ...


Mvh // Regards ...
_________________________________
Stefan Carlsson

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240315/85333480/attachment.html>

From social at bohboh.info  Fri Mar 15 22:35:11 2024
From: social at bohboh.info (Social Boh)
Date: Fri, 15 Mar 2024 17:35:11 -0500
Subject: [OpenSIPS-Users] OpenSIPs generate PRACK
In-Reply-To: <be15bfd5-364b-4c32-8343-05ead701e7e4@opensips.org>
References: <476be849-afbe-4d69-9218-f80bd27022ad@bohboh.info>
 <e880a151-5bca-443e-8216-16b80b4ff067@bohboh.info>
 <CAJTkRNtNYHe2Sid19y0sw8d457j3iCwoJHOjOpjYD4tZU-ekbA@mail.gmail.com>
 <49eb93af-dd10-4fae-82bd-1d19edca403a@opensips.org>
 <fd54ef29-8dfe-4a01-9ac2-ecfef090d47c@bohboh.info>
 <be15bfd5-364b-4c32-8343-05ead701e7e4@opensips.org>
Message-ID: <fcfaa1c8-4196-4807-a70e-cc4cf89dd9b3@bohboh.info>

I'm trying using directly opensips-cli via exec module to see if all OK 
and then pass the data tu mi_script module

I think I have a sintaxis problem with the line:

exec("opensips-cli -x mi t_uac_dlg method=INVITE 
ruri="sip:alice at 127.0.0.1:7050" headers="From: 
sip:bobster at 127.0.0.1:1337\r\nTo: sip:alice at 127.0.0.1:7050\r\nContact: 
sip:bobster at 127.0.0.1:1337\r\n"")

I don't know how use " in the line because Headers and ruri need them. 
The result is a error:

ERROR:core:handle_mi_request: Invalid parameters

Any hint, please?

Regards

---
I'm SoCIaL, MayBe

El 26/02/2024 a las 7:43 a. m., Bogdan-Andrei Iancu escribió:
> yes, you can use the b2b_logic (together with b2b_entities) for that, 
> but it may be a too heavy tool for the purpose. Maybe you can try to 
> generate the PRACK from OpenSIPS level by using the t_uac_dlg MI 
> function [1] via the mi_script module [2] - basically to trigger that 
> MI cmd from the onreply_route, when receiving the 180 reply.
>
> [1] https://opensips.org/html/docs/modules/3.4.x/tm.html#mi_t_uac_dlg
> [2] https://opensips.org/html/docs/modules/3.4.x/mi_script.html#afunc_mi
>
> Regards,
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>    https://www.opensips-solutions.com
>    https://www.siphub.com
> On 25.02.2024 14:54, Social Boh wrote:
>>
>> I know the best way is the original caller handle and reply the 183, 
>> but I HAVE to do this at OpenSIPs level.
>>
>> Can I use B2B_Entities and B2B_logic to do this? Is there a scenario 
>> to use tu parse and reply the 183?
>>
>> Thank you
>>
>> ---
>> I'm SoCIaL, MayBe
>> El 16/02/2024 a las 11:31 a. m., Bogdan-Andrei Iancu escribió:
>>> I agree here, the 183 must be relayed back to the original caller 
>>> (which generate the received INVITE) and let it do the PRACK - this 
>>> confirmation must be end-2-end in the dialog.
>>>
>>> Regards,
>>> Bogdan-Andrei Iancu
>>>
>>> OpenSIPS Founder and Developer
>>>    https://www.opensips-solutions.com
>>>    https://www.siphub.com
>>> On 12.02.2024 11:36, Ihor Olkhovskyi wrote:
>>>> You should relay 183 to original source (ione that is sending 
>>>> INVITE) and got PRACK from there.
>>>> That would be the most correct way of handling this
>>>>
>>>> Le lun. 12 févr. 2024 à 02:29, Social Boh <social at bohboh.info> a 
>>>> écrit :
>>>>
>>>>     Maybe someone can help me.
>>>>
>>>>     This is the scenario.
>>>>
>>>>     OpenSIPs receive a INVITE and send it to a server that reply
>>>>     with a 302
>>>>     message (always)
>>>>
>>>>     Then OpenSIPs, in the failure route, take the user part present
>>>>     in the
>>>>     302 contact header, change the destination IP and send with t_relay
>>>>
>>>>     The destination reply with a 183 with Require: 100rel header so
>>>>     OpenSIPs
>>>>     have to reply with a PRACK. This is my problem.
>>>>
>>>>     I don't know which is the best way to handle this (the PRACK)
>>>>
>>>>     Thank you
>>>>
>>>>     Regards
>>>>
>>>>     ---
>>>>     I'm SoCIaL, MayBe
>>>>
>>>>     El 9/02/2024 a las 6:46 a. m., Social Boh escribió:
>>>>     > Hello list,
>>>>     >
>>>>     > can OpenSIPs generate a PRACK message to reply a 180/183 message?
>>>>     >
>>>>     > Thank you
>>>>     >
>>>>     > Regards
>>>>     >
>>>>     > ---
>>>>     > I'm SoCIaL, MayBe
>>>>     >
>>>>     >
>>>>     > _______________________________________________
>>>>     > Users mailing list
>>>>     > Users at lists.opensips.org
>>>>     > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>>
>>>>     _______________________________________________
>>>>     Users mailing list
>>>>     Users at lists.opensips.org
>>>>     http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>>
>>>>
>>>>
>>>> -- 
>>>> Best regards,
>>>> Ihor (Igor)
>>>>
>>>> _______________________________________________
>>>> Users mailing list
>>>> Users at lists.opensips.org
>>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>
>>>
>>> _______________________________________________
>>> Users mailing list
>>> Users at lists.opensips.org
>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240315/9518c3f0/attachment-0001.html>

From prathibhab.tvm at gmail.com  Sun Mar 17 12:52:47 2024
From: prathibhab.tvm at gmail.com (Prathibha B)
Date: Sun, 17 Mar 2024 18:22:47 +0530
Subject: [OpenSIPS-Users] Incoming Call
Message-ID: <CAJh_-cCv9t1Ec6r3ZjEyF5TzP=c_K4Fh4tJ47V+8Xtz1E5tU_w@mail.gmail.com>

Automatically the web page with browser phone url initiates the call
without me loading the webpage.

Attachment: opensips.cfg

-- 
Regards,
B.Prathibha
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240317/c37c050d/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: opensips.cfg
Type: application/octet-stream
Size: 20668 bytes
Desc: not available
URL: <http://lists.opensips.org/pipermail/users/attachments/20240317/c37c050d/attachment-0001.obj>

From prathibhab.tvm at gmail.com  Sun Mar 17 13:01:08 2024
From: prathibhab.tvm at gmail.com (Prathibha B)
Date: Sun, 17 Mar 2024 18:31:08 +0530
Subject: [OpenSIPS-Users] Incoming Call
In-Reply-To: <CAJh_-cCv9t1Ec6r3ZjEyF5TzP=c_K4Fh4tJ47V+8Xtz1E5tU_w@mail.gmail.com>
References: <CAJh_-cCv9t1Ec6r3ZjEyF5TzP=c_K4Fh4tJ47V+8Xtz1E5tU_w@mail.gmail.com>
Message-ID: <CAJh_-cCbyvTEtJk1bBctdvWV_TFPzE2ps9nRLwd1rT=PEA9WVQ@mail.gmail.com>

The call is generate once in a minute.

On Sun, 17 Mar 2024 at 18:22, Prathibha B <prathibhab.tvm at gmail.com> wrote:

> Automatically the web page with browser phone url initiates the call
> without me loading the webpage.
>
> Attachment: opensips.cfg
>
> --
> Regards,
> B.Prathibha
>


-- 
Regards,
B.Prathibha
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240317/94e84360/attachment.html>

From prathibhab.tvm at gmail.com  Sun Mar 17 13:18:28 2024
From: prathibhab.tvm at gmail.com (Prathibha B)
Date: Sun, 17 Mar 2024 18:48:28 +0530
Subject: [OpenSIPS-Users] Incoming Call
In-Reply-To: <CAJh_-cCbyvTEtJk1bBctdvWV_TFPzE2ps9nRLwd1rT=PEA9WVQ@mail.gmail.com>
References: <CAJh_-cCv9t1Ec6r3ZjEyF5TzP=c_K4Fh4tJ47V+8Xtz1E5tU_w@mail.gmail.com>
 <CAJh_-cCbyvTEtJk1bBctdvWV_TFPzE2ps9nRLwd1rT=PEA9WVQ@mail.gmail.com>
Message-ID: <CAJh_-cAD23B1K4BA4L2AKYg_wtZeUgUtHk2Tyj=+OtfEDNBYKA@mail.gmail.com>

This happens once in a minutes. Once a minute, the reregistration happens
and the page reloads itself.

On Sun, 17 Mar 2024 at 18:31, Prathibha B <prathibhab.tvm at gmail.com> wrote:

> The call is generate once in a minute.
>
> On Sun, 17 Mar 2024 at 18:22, Prathibha B <prathibhab.tvm at gmail.com>
> wrote:
>
>> Automatically the web page with browser phone url initiates the call
>> without me loading the webpage.
>>
>> Attachment: opensips.cfg
>>
>> --
>> Regards,
>> B.Prathibha
>>
>
>
> --
> Regards,
> B.Prathibha
>


-- 
Regards,
B.Prathibha
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240317/fd6b6b43/attachment.html>

From david.villasmil.work at gmail.com  Sun Mar 17 16:33:34 2024
From: david.villasmil.work at gmail.com (David Villasmil)
Date: Sun, 17 Mar 2024 17:33:34 +0100
Subject: [OpenSIPS-Users] Incoming Call
In-Reply-To: <CAJh_-cAD23B1K4BA4L2AKYg_wtZeUgUtHk2Tyj=+OtfEDNBYKA@mail.gmail.com>
References: <CAJh_-cCv9t1Ec6r3ZjEyF5TzP=c_K4Fh4tJ47V+8Xtz1E5tU_w@mail.gmail.com>
 <CAJh_-cCbyvTEtJk1bBctdvWV_TFPzE2ps9nRLwd1rT=PEA9WVQ@mail.gmail.com>
 <CAJh_-cAD23B1K4BA4L2AKYg_wtZeUgUtHk2Tyj=+OtfEDNBYKA@mail.gmail.com>
Message-ID: <CAFGRPVr5P1EPdJGyJgxxF0R_H6K66wkT7B_8JTVX4R_dqivagg@mail.gmail.com>

I don’t know, but from what you say, it sounds like a page thing, not
opensips. Check the web page

Regards,

David Villasmil
email: david.villasmil.work at gmail.com
phone: +34669448337


On Sun, 17 Mar 2024 at 14:19, Prathibha B <prathibhab.tvm at gmail.com> wrote:

> This happens once in a minutes. Once a minute, the reregistration happens
> and the page reloads itself.
>
> On Sun, 17 Mar 2024 at 18:31, Prathibha B <prathibhab.tvm at gmail.com>
> wrote:
>
>> The call is generate once in a minute.
>>
>> On Sun, 17 Mar 2024 at 18:22, Prathibha B <prathibhab.tvm at gmail.com>
>> wrote:
>>
>>> Automatically the web page with browser phone url initiates the call
>>> without me loading the webpage.
>>>
>>> Attachment: opensips.cfg
>>>
>>> --
>>> Regards,
>>> B.Prathibha
>>>
>>
>>
>> --
>> Regards,
>> B.Prathibha
>>
>
>
> --
> Regards,
> B.Prathibha
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240317/0855e748/attachment.html>

From social at bohboh.info  Mon Mar 18 20:43:30 2024
From: social at bohboh.info (Social Boh)
Date: Mon, 18 Mar 2024 15:43:30 -0500
Subject: [OpenSIPS-Users] Basic sum question
Message-ID: <757b7bb0-faa3-4099-8fb6-68e1b753091d@bohboh.info>

Hello list

how can I add a 1 to a script variable like:

$var(cs) = $cs{s.int} + 1;

Result:

ERROR:core:eval_elem: invalid string operands
WARNING:core:do_assign: no value in right expression at 
/etc/opensips/opensips.cfg:205

Thank you

Regards

-- 
---
I'm SoCIaL, MayBe



From Ben.Newlin at genesys.com  Mon Mar 18 20:50:48 2024
From: Ben.Newlin at genesys.com (Ben Newlin)
Date: Mon, 18 Mar 2024 20:50:48 +0000
Subject: [OpenSIPS-Users] Basic sum question
In-Reply-To: <757b7bb0-faa3-4099-8fb6-68e1b753091d@bohboh.info>
References: <757b7bb0-faa3-4099-8fb6-68e1b753091d@bohboh.info>
Message-ID: <BN0PR10MB5208C40EB666751D7B7DA651952D2@BN0PR10MB5208.namprd10.prod.outlook.com>

You have to use parentheses in order to use a transformation on a variable.

$var(cs) = $(cs{s.int}) + 1;

Ben Newlin

From: Users <users-bounces at lists.opensips.org> on behalf of Social Boh <social at bohboh.info>
Date: Monday, March 18, 2024 at 4:44 PM
To: users at lists.opensips.org <users at lists.opensips.org>
Subject: [OpenSIPS-Users] Basic sum question
 EXTERNAL EMAIL - Please use caution with links and attachments

Hello list

how can I add a 1 to a script variable like:

$var(cs) = $cs{s.int} + 1;

Result:

ERROR:core:eval_elem: invalid string operands
WARNING:core:do_assign: no value in right expression at
/etc/opensips/opensips.cfg:205

Thank you

Regards

--
---
I'm SoCIaL, MayBe


_______________________________________________
Users mailing list
Users at lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240318/a7223704/attachment.html>

From social at bohboh.info  Mon Mar 18 21:14:54 2024
From: social at bohboh.info (Social Boh)
Date: Mon, 18 Mar 2024 16:14:54 -0500
Subject: [OpenSIPS-Users] Basic sum question [SOLVED]
In-Reply-To: <BN0PR10MB5208C40EB666751D7B7DA651952D2@BN0PR10MB5208.namprd10.prod.outlook.com>
References: <757b7bb0-faa3-4099-8fb6-68e1b753091d@bohboh.info>
 <BN0PR10MB5208C40EB666751D7B7DA651952D2@BN0PR10MB5208.namprd10.prod.outlook.com>
Message-ID: <7537b83a-9b03-4812-871d-6f64a12f3353@bohboh.info>

thank you. Works

Regards

---
I'm SoCIaL, MayBe

El 18/03/2024 a las 3:50 p. m., Ben Newlin escribió:
>
> You have to use parentheses in order to use a transformation on a 
> variable.
>
> $var(cs) = $*(*cs{s.int}*)* + 1;
>
> Ben Newlin
>
> *From: *Users <users-bounces at lists.opensips.org> on behalf of Social 
> Boh <social at bohboh.info>
> *Date: *Monday, March 18, 2024 at 4:44 PM
> *To: *users at lists.opensips.org <users at lists.opensips.org>
> *Subject: *[OpenSIPS-Users] Basic sum question
>
>  EXTERNAL EMAIL - Please use caution with links and attachments
>
> Hello list
>
> how can I add a 1 to a script variable like:
>
> $var(cs) = $cs{s.int} + 1;
>
> Result:
>
> ERROR:core:eval_elem: invalid string operands
> WARNING:core:do_assign: no value in right expression at
> /etc/opensips/opensips.cfg:205
>
> Thank you
>
> Regards
>
> -- 
> ---
> I'm SoCIaL, MayBe
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240318/c2f5d100/attachment.html>

From prathibhab.tvm at gmail.com  Tue Mar 19 05:03:00 2024
From: prathibhab.tvm at gmail.com (Prathibha B)
Date: Tue, 19 Mar 2024 10:33:00 +0530
Subject: [OpenSIPS-Users] call center
Message-ID: <CAJh_-cB_Uw5Enk+4P-so2y-_CjL+V8FAzyMSe-=aOGbabJr5eQ@mail.gmail.com>

How to integrate Opensips with call center application?

-- 
Regards,
B.Prathibha
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240319/0f246ad2/attachment-0001.html>

From prathibhab.tvm at gmail.com  Tue Mar 19 07:30:01 2024
From: prathibhab.tvm at gmail.com (Prathibha B)
Date: Tue, 19 Mar 2024 13:00:01 +0530
Subject: [OpenSIPS-Users] Management Interface
Message-ID: <CAJh_-cCaK4rkXd+R2j-aCGcXacy5LPN2Pa6px=-UxnhTKM6y-Q@mail.gmail.com>

What is the alternative to Asterisk Management Interface in OpenSIPS?

-- 
Regards,
B.Prathibha
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240319/6feec43f/attachment.html>

From spanda at 3clogic.com  Tue Mar 19 11:02:02 2024
From: spanda at 3clogic.com (Sasmita Panda)
Date: Tue, 19 Mar 2024 16:32:02 +0530
Subject: [OpenSIPS-Users] Need some suggestion or help in case of webrtc
 connection with opensips .
Message-ID: <CALf-Q45=rLrQVkStCEFaHpnN6ADvbLw+4f42P-qPRv9Q4Hx7sw@mail.gmail.com>

Hi All ,

I have opensips 3.2 version with webrtc configured . I just got an issue in
production that one browser is trying to establish multiple connections
frequently which overloads my server which has the impact that other
browsers are not able to establish a single connection at some points .

Is this possible? I can limit the number of websocket connections per user
(here the user has a unique username which I used to save as contact in the
location table ) so that the server will reject the connection above that ?

Please do suggest . Your help is appreciated .

*Thanks & Regards*
*Sasmita Panda*
*Senior Network Testing and Software Engineer*
*3CLogic , ph:07827611765*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240319/cec9da5d/attachment.html>

From prathibhab.tvm at gmail.com  Tue Mar 19 12:39:13 2024
From: prathibhab.tvm at gmail.com (Prathibha B)
Date: Tue, 19 Mar 2024 18:09:13 +0530
Subject: [OpenSIPS-Users] CDR
Message-ID: <CAJh_-cAc631keLOKdWfrmORSkgbY3Uq9ajvwnAbaOznMEz0Jmg@mail.gmail.com>

How to get the Call Detail Record in Opensips?
-- 
Regards,
B.Prathibha
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240319/2b8fe648/attachment.html>

From marcin at voipplus.net  Tue Mar 19 13:05:10 2024
From: marcin at voipplus.net (Marcin Groszek)
Date: Tue, 19 Mar 2024 08:05:10 -0500
Subject: [OpenSIPS-Users] CDR
In-Reply-To: <CAJh_-cAc631keLOKdWfrmORSkgbY3Uq9ajvwnAbaOznMEz0Jmg@mail.gmail.com>
References: <CAJh_-cAc631keLOKdWfrmORSkgbY3Uq9ajvwnAbaOznMEz0Jmg@mail.gmail.com>
Message-ID: <a1c0bae3-dc37-fc04-99f3-ad26893c87e9@voipplus.net>

Look in to ACC module.

On 3/19/2024 7:39 AM, Prathibha B wrote:
>
> How to get the Call Detail Record in Opensips?
> -- 
> Regards,
> B.Prathibha
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users

-- 
Best Regards:
Marcin Groszek
Business Phone Service
https://www.voipplus.net

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240319/d438ce88/attachment.html>

From social at bohboh.info  Tue Mar 19 17:53:17 2024
From: social at bohboh.info (Social Boh)
Date: Tue, 19 Mar 2024 12:53:17 -0500
Subject: [OpenSIPS-Users] OpenSIPs generate PRACK
In-Reply-To: <fcfaa1c8-4196-4807-a70e-cc4cf89dd9b3@bohboh.info>
References: <476be849-afbe-4d69-9218-f80bd27022ad@bohboh.info>
 <e880a151-5bca-443e-8216-16b80b4ff067@bohboh.info>
 <CAJTkRNtNYHe2Sid19y0sw8d457j3iCwoJHOjOpjYD4tZU-ekbA@mail.gmail.com>
 <49eb93af-dd10-4fae-82bd-1d19edca403a@opensips.org>
 <fd54ef29-8dfe-4a01-9ac2-ecfef090d47c@bohboh.info>
 <be15bfd5-364b-4c32-8343-05ead701e7e4@opensips.org>
 <fcfaa1c8-4196-4807-a70e-cc4cf89dd9b3@bohboh.info>
Message-ID: <34e1d5c1-deb3-458f-ad0a-401a1d077852@bohboh.info>

Some progress

Now I can reply the first 183 with the PRACK response but when the 
provider send a 180 ringing and I reply with another PPRACK response the 
provider reply with 500 Server Internal Error

Annex PCAP Capture.

Any hint is really appreciate.

Regards

---
I'm SoCIaL, MayBe

El 15/03/2024 a las 5:35 p. m., Social Boh escribió:
>
> I'm trying using directly opensips-cli via exec module to see if all 
> OK and then pass the data tu mi_script module
>
> I think I have a sintaxis problem with the line:
>
> exec("opensips-cli -x mi t_uac_dlg method=INVITE 
> ruri="sip:alice at 127.0.0.1:7050" headers="From: 
> sip:bobster at 127.0.0.1:1337\r\nTo: sip:alice at 127.0.0.1:7050\r\nContact: 
> sip:bobster at 127.0.0.1:1337\r\n"")
>
> I don't know how use " in the line because Headers and ruri need them. 
> The result is a error:
>
> ERROR:core:handle_mi_request: Invalid parameters
>
> Any hint, please?
>
> Regards
>
> ---
> I'm SoCIaL, MayBe
> El 26/02/2024 a las 7:43 a. m., Bogdan-Andrei Iancu escribió:
>> yes, you can use the b2b_logic (together with b2b_entities) for that, 
>> but it may be a too heavy tool for the purpose. Maybe you can try to 
>> generate the PRACK from OpenSIPS level by using the t_uac_dlg MI 
>> function [1] via the mi_script module [2] - basically to trigger that 
>> MI cmd from the onreply_route, when receiving the 180 reply.
>>
>> [1] https://opensips.org/html/docs/modules/3.4.x/tm.html#mi_t_uac_dlg
>> [2] https://opensips.org/html/docs/modules/3.4.x/mi_script.html#afunc_mi
>>
>> Regards,
>> Bogdan-Andrei Iancu
>>
>> OpenSIPS Founder and Developer
>>    https://www.opensips-solutions.com
>>    https://www.siphub.com
>> On 25.02.2024 14:54, Social Boh wrote:
>>>
>>> I know the best way is the original caller handle and reply the 183, 
>>> but I HAVE to do this at OpenSIPs level.
>>>
>>> Can I use B2B_Entities and B2B_logic to do this? Is there a scenario 
>>> to use tu parse and reply the 183?
>>>
>>> Thank you
>>>
>>> ---
>>> I'm SoCIaL, MayBe
>>> El 16/02/2024 a las 11:31 a. m., Bogdan-Andrei Iancu escribió:
>>>> I agree here, the 183 must be relayed back to the original caller 
>>>> (which generate the received INVITE) and let it do the PRACK - this 
>>>> confirmation must be end-2-end in the dialog.
>>>>
>>>> Regards,
>>>> Bogdan-Andrei Iancu
>>>>
>>>> OpenSIPS Founder and Developer
>>>>    https://www.opensips-solutions.com
>>>>    https://www.siphub.com
>>>> On 12.02.2024 11:36, Ihor Olkhovskyi wrote:
>>>>> You should relay 183 to original source (ione that is sending 
>>>>> INVITE) and got PRACK from there.
>>>>> That would be the most correct way of handling this
>>>>>
>>>>> Le lun. 12 févr. 2024 à 02:29, Social Boh <social at bohboh.info> a 
>>>>> écrit :
>>>>>
>>>>>     Maybe someone can help me.
>>>>>
>>>>>     This is the scenario.
>>>>>
>>>>>     OpenSIPs receive a INVITE and send it to a server that reply
>>>>>     with a 302
>>>>>     message (always)
>>>>>
>>>>>     Then OpenSIPs, in the failure route, take the user part
>>>>>     present in the
>>>>>     302 contact header, change the destination IP and send with
>>>>>     t_relay
>>>>>
>>>>>     The destination reply with a 183 with Require: 100rel header
>>>>>     so OpenSIPs
>>>>>     have to reply with a PRACK. This is my problem.
>>>>>
>>>>>     I don't know which is the best way to handle this (the PRACK)
>>>>>
>>>>>     Thank you
>>>>>
>>>>>     Regards
>>>>>
>>>>>     ---
>>>>>     I'm SoCIaL, MayBe
>>>>>
>>>>>     El 9/02/2024 a las 6:46 a. m., Social Boh escribió:
>>>>>     > Hello list,
>>>>>     >
>>>>>     > can OpenSIPs generate a PRACK message to reply a 180/183
>>>>>     message?
>>>>>     >
>>>>>     > Thank you
>>>>>     >
>>>>>     > Regards
>>>>>     >
>>>>>     > ---
>>>>>     > I'm SoCIaL, MayBe
>>>>>     >
>>>>>     >
>>>>>     > _______________________________________________
>>>>>     > Users mailing list
>>>>>     > Users at lists.opensips.org
>>>>>     > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>>>
>>>>>     _______________________________________________
>>>>>     Users mailing list
>>>>>     Users at lists.opensips.org
>>>>>     http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>>>
>>>>>
>>>>>
>>>>> -- 
>>>>> Best regards,
>>>>> Ihor (Igor)
>>>>>
>>>>> _______________________________________________
>>>>> Users mailing list
>>>>> Users at lists.opensips.org
>>>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>>
>>>>
>>>> _______________________________________________
>>>> Users mailing list
>>>> Users at lists.opensips.org
>>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240319/62897911/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PRACK.pcap
Type: application/octet-stream
Size: 16672 bytes
Desc: not available
URL: <http://lists.opensips.org/pipermail/users/attachments/20240319/62897911/attachment-0001.obj>

From igorolhovskiy at gmail.com  Wed Mar 20 09:07:54 2024
From: igorolhovskiy at gmail.com (Ihor Olkhovskyi)
Date: Wed, 20 Mar 2024 10:07:54 +0100
Subject: [OpenSIPS-Users] OpenSIPs generate PRACK
In-Reply-To: <34e1d5c1-deb3-458f-ad0a-401a1d077852@bohboh.info>
References: <476be849-afbe-4d69-9218-f80bd27022ad@bohboh.info>
 <e880a151-5bca-443e-8216-16b80b4ff067@bohboh.info>
 <CAJTkRNtNYHe2Sid19y0sw8d457j3iCwoJHOjOpjYD4tZU-ekbA@mail.gmail.com>
 <49eb93af-dd10-4fae-82bd-1d19edca403a@opensips.org>
 <fd54ef29-8dfe-4a01-9ac2-ecfef090d47c@bohboh.info>
 <be15bfd5-364b-4c32-8343-05ead701e7e4@opensips.org>
 <fcfaa1c8-4196-4807-a70e-cc4cf89dd9b3@bohboh.info>
 <34e1d5c1-deb3-458f-ad0a-401a1d077852@bohboh.info>
Message-ID: <CAJTkRNsv7cmJiFWzDWiDNuMHGw8qp5ENw6pJKBLLsYBJgzX-Tg@mail.gmail.com>

You are not increasing CSeq for subsequent PRACK.

Le mar. 19 mars 2024 à 18:58, Social Boh <social at bohboh.info> a écrit :

> Some progress
>
> Now I can reply the first 183 with the PRACK response but when the
> provider send a 180 ringing and I reply with another PPRACK response the
> provider reply with 500 Server Internal Error
>
> Annex PCAP Capture.
>
> Any hint is really appreciate.
>
> Regards
>
> ---
> I'm SoCIaL, MayBe
>
> El 15/03/2024 a las 5:35 p. m., Social Boh escribió:
>
> I'm trying using directly opensips-cli via exec module to see if all OK
> and then pass the data tu mi_script module
>
> I think I have a sintaxis problem with the line:
>
> exec("opensips-cli -x mi t_uac_dlg method=INVITE ruri=
> "sip:alice at 127.0.0.1:7050" headers="From: sip:bobster at 127.0.0.1:1337\r\nTo:
> sip:alice at 127.0.0.1:7050\r\nContact: sip:bobster at 127.0.0.1:1337\r\n"")
>
> I don't know how use " in the line because Headers and ruri need them. The
> result is a error:
>
> ERROR:core:handle_mi_request: Invalid parameters
>
> Any hint, please?
>
> Regards
>
> ---
> I'm SoCIaL, MayBe
>
> El 26/02/2024 a las 7:43 a. m., Bogdan-Andrei Iancu escribió:
>
> yes, you can use the b2b_logic (together with b2b_entities) for that, but
> it may be a too heavy tool for the purpose. Maybe you can try to generate
> the PRACK from OpenSIPS level by using the t_uac_dlg MI function [1] via
> the mi_script module [2] - basically to trigger that MI cmd from the
> onreply_route, when receiving the 180 reply.
>
> [1] https://opensips.org/html/docs/modules/3.4.x/tm.html#mi_t_uac_dlg
> [2] https://opensips.org/html/docs/modules/3.4.x/mi_script.html#afunc_mi
>
> Regards,
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>   https://www.opensips-solutions.com
>   https://www.siphub.com
>
> On 25.02.2024 14:54, Social Boh wrote:
>
> I know the best way is the original caller handle and reply the 183, but I
> HAVE to do this at OpenSIPs level.
>
> Can I use B2B_Entities and B2B_logic to do this? Is there a scenario to
> use tu parse and reply the 183?
>
> Thank you
>
> ---
> I'm SoCIaL, MayBe
>
> El 16/02/2024 a las 11:31 a. m., Bogdan-Andrei Iancu escribió:
>
> I agree here, the 183 must be relayed back to the original caller (which
> generate the received INVITE) and let it do the PRACK - this confirmation
> must be end-2-end in the dialog.
>
> Regards,
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>   https://www.opensips-solutions.com
>   https://www.siphub.com
>
> On 12.02.2024 11:36, Ihor Olkhovskyi wrote:
>
> You should relay 183 to original source (ione that is sending INVITE) and
> got PRACK from there.
> That would be the most correct way of handling this
>
> Le lun. 12 févr. 2024 à 02:29, Social Boh <social at bohboh.info> a écrit :
>
>> Maybe someone can help me.
>>
>> This is the scenario.
>>
>> OpenSIPs receive a INVITE and send it to a server that reply with a 302
>> message (always)
>>
>> Then OpenSIPs, in the failure route, take the user part present in the
>> 302 contact header, change the destination IP and send with t_relay
>>
>> The destination reply with a 183 with Require: 100rel header so OpenSIPs
>> have to reply with a PRACK. This is my problem.
>>
>> I don't know which is the best way to handle this (the PRACK)
>>
>> Thank you
>>
>> Regards
>>
>> ---
>> I'm SoCIaL, MayBe
>>
>> El 9/02/2024 a las 6:46 a. m., Social Boh escribió:
>> > Hello list,
>> >
>> > can OpenSIPs generate a PRACK message to reply a 180/183 message?
>> >
>> > Thank you
>> >
>> > Regards
>> >
>> > ---
>> > I'm SoCIaL, MayBe
>> >
>> >
>> > _______________________________________________
>> > Users mailing list
>> > Users at lists.opensips.org
>> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>
>
> --
> Best regards,
> Ihor (Igor)
>
> _______________________________________________
> Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
> _______________________________________________
> Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
> _______________________________________________
> Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>


-- 
Best regards,
Ihor (Igor)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240320/321b02f3/attachment.html>

From prathibhab.tvm at gmail.com  Wed Mar 20 10:00:52 2024
From: prathibhab.tvm at gmail.com (Prathibha B)
Date: Wed, 20 Mar 2024 15:30:52 +0530
Subject: [OpenSIPS-Users] external applications
Message-ID: <CAJh_-cCAZ2_0mvb98Csex13oyGvbN18Nt9tLVynXgFED85Ec7g@mail.gmail.com>

How to integrate OpenSIPS with external applications?

-- 
Regards,
B.Prathibha
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240320/ec453fa4/attachment.html>

From marcin at voipplus.net  Wed Mar 20 10:10:10 2024
From: marcin at voipplus.net (Marcin Groszek)
Date: Wed, 20 Mar 2024 05:10:10 -0500
Subject: [OpenSIPS-Users] external applications
In-Reply-To: <CAJh_-cCAZ2_0mvb98Csex13oyGvbN18Nt9tLVynXgFED85Ec7g@mail.gmail.com>
References: <CAJh_-cCAZ2_0mvb98Csex13oyGvbN18Nt9tLVynXgFED85Ec7g@mail.gmail.com>
Message-ID: <5ecfbddd-d737-f2ca-b93d-a93c1886dff6@voipplus.net>

Well, to execute external command from opensips you may want to use EXEC 
module.

this is a manual for v3.2:

https://opensips.org/html/docs/modules/3.2.x/exec.html


On 3/20/2024 5:00 AM, Prathibha B wrote:
> How to integrate OpenSIPS with external applications?
>
> -- 
> Regards,
> B.Prathibha
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users

-- 
Best Regards:
Marcin Groszek
Business Phone Service
https://www.voipplus.net

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240320/6cad8f53/attachment-0001.html>

From prathibhab.tvm at gmail.com  Wed Mar 20 10:16:30 2024
From: prathibhab.tvm at gmail.com (Prathibha B)
Date: Wed, 20 Mar 2024 15:46:30 +0530
Subject: [OpenSIPS-Users] external applications
In-Reply-To: <5ecfbddd-d737-f2ca-b93d-a93c1886dff6@voipplus.net>
References: <CAJh_-cCAZ2_0mvb98Csex13oyGvbN18Nt9tLVynXgFED85Ec7g@mail.gmail.com>
 <5ecfbddd-d737-f2ca-b93d-a93c1886dff6@voipplus.net>
Message-ID: <CAJh_-cBm=yMTTn=E5tTnhqveG867CsCr7G3eOtVij+gtHBXk0w@mail.gmail.com>

No. I want to pass START, CONNECT, END messages from OpenSIPS to external
application.

On Wed, 20 Mar 2024 at 15:42, Marcin Groszek <marcin at voipplus.net> wrote:

> Well, to execute external command from opensips you may want to use EXEC
> module.
>
> this is a manual for v3.2:
>
> https://opensips.org/html/docs/modules/3.2.x/exec.html
>
>
> On 3/20/2024 5:00 AM, Prathibha B wrote:
>
> How to integrate OpenSIPS with external applications?
>
> --
> Regards,
> B.Prathibha
>
> _______________________________________________
> Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
> --
> Best Regards:
> Marcin Groszek
> Business Phone Servicehttps://www.voipplus.net
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>


-- 
Regards,
B.Prathibha
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240320/ac28a3f8/attachment.html>

From marcin at voipplus.net  Wed Mar 20 10:48:30 2024
From: marcin at voipplus.net (Marcin Groszek)
Date: Wed, 20 Mar 2024 05:48:30 -0500
Subject: [OpenSIPS-Users] external applications
In-Reply-To: <CAJh_-cBm=yMTTn=E5tTnhqveG867CsCr7G3eOtVij+gtHBXk0w@mail.gmail.com>
References: <CAJh_-cCAZ2_0mvb98Csex13oyGvbN18Nt9tLVynXgFED85Ec7g@mail.gmail.com>
 <5ecfbddd-d737-f2ca-b93d-a93c1886dff6@voipplus.net>
 <CAJh_-cBm=yMTTn=E5tTnhqveG867CsCr7G3eOtVij+gtHBXk0w@mail.gmail.com>
Message-ID: <68b4c1f2-05b9-a6ff-3e29-7b391bca0a7c@voipplus.net>

You may still do so using EXEC module

to execute async

{
...
async(exec("mycommand.sh start", $ru, $ru), continue);
}

route [continue] {
...
}

or

{
...
async(exec("mycommand.sh end", $ru, $ru), next);
}

route [next] {
...
}

or utilize separate scripts like start.sh, end.sh connect.sh


On 3/20/2024 5:16 AM, Prathibha B wrote:
> No. I want to pass START, CONNECT, END messages from OpenSIPS to 
> external application.
>
> On Wed, 20 Mar 2024 at 15:42, Marcin Groszek <marcin at voipplus.net 
> <mailto:marcin at voipplus.net>> wrote:
>
>     Well, to execute external command from opensips you may want to
>     use EXEC module.
>
>     this is a manual for v3.2:
>
>     https://opensips.org/html/docs/modules/3.2.x/exec.html
>
>
>     On 3/20/2024 5:00 AM, Prathibha B wrote:
>>     How to integrate OpenSIPS with external applications?
>>
>>     -- 
>>     Regards,
>>     B.Prathibha
>>
>>     _______________________________________________
>>     Users mailing list
>>     Users at lists.opensips.org  <mailto:Users at lists.opensips.org>
>>     http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>     -- 
>     Best Regards:
>     Marcin Groszek
>     Business Phone Service
>     https://www.voipplus.net
>
>     _______________________________________________
>     Users mailing list
>     Users at lists.opensips.org <mailto:Users at lists.opensips.org>
>     http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
> -- 
> Regards,
> B.Prathibha
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users

-- 
Best Regards:
Marcin Groszek
Business Phone Service
https://www.voipplus.net

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240320/ee96106b/attachment.html>

From bogdan at opensips.org  Wed Mar 20 11:37:00 2024
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Wed, 20 Mar 2024 13:37:00 +0200
Subject: [OpenSIPS-Users] Problems with new installation of 3.4
In-Reply-To: <9f9c64521006491ab59d3cdb585e8849@tetab.nu>
References: <9f9c64521006491ab59d3cdb585e8849@tetab.nu>
Message-ID: <0a112bcf-f2da-422c-afb8-ac48a7b1aa2a@opensips.org>

Hi,

Some opensips modules are provided via separate debs (due the 
dependencies), so you just have to install more packages, no need to 
compile anything:
https://apt.opensips.org/pool/jammy/3.4-releases/o/opensips/

What you need here is opensips-auth-modules, I guess

Regards,

Bogdan-Andrei Iancu

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

On 15.03.2024 20:27, Stefan Carlsson wrote:
>
> Hi !
>
> After followed the installation of 3.4 LTS to a fresh ubuntu ver 22 a 
> found some serious problems …
>
> installing is done via apt.
>
> 1) Not all the modules were included in the rep. as it should ref. to 
> spec. vers.  manual
>
> 2) After downloading the source , trying to compile the modules 
> missing…  dependencies needed and info is missing in the main doc. or 
> moduledoc.
>
> For example:
>
> make: *** No rule to make target 
> '../../lib/digest_auth/libdigest_auth.a', needed by 'uac_auth.so'.  Stop.
>
> trying to make all from opensips src. root folder …
>
> Compiling main.c
>
> In file included from main.c:152:
>
> ssl_tweaks.h:2:10: fatal error: openssl/opensslv.h: No such file or 
> directory
>
> Any ideas …
>
> Mvh // Regards …
>
> _________________________________
>
> Stefan Carlsson
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240320/d485cd4d/attachment.html>

From igorolhovskiy at gmail.com  Wed Mar 20 12:33:27 2024
From: igorolhovskiy at gmail.com (Ihor Olkhovskyi)
Date: Wed, 20 Mar 2024 13:33:27 +0100
Subject: [OpenSIPS-Users] Need some suggestion or help in case of webrtc
 connection with opensips .
In-Reply-To: <CALf-Q45=rLrQVkStCEFaHpnN6ADvbLw+4f42P-qPRv9Q4Hx7sw@mail.gmail.com>
References: <CALf-Q45=rLrQVkStCEFaHpnN6ADvbLw+4f42P-qPRv9Q4Hx7sw@mail.gmail.com>
Message-ID: <CAJTkRNv_wVTuwpxKS-p4jYQryO59=ApCQ5Tsyao8XCohMmX7tg@mail.gmail.com>

Hi!

You can try to use something like cachedb module (for autoexpiry) with name
of the key like "username_timestamp" and increment it in a case of value
exists. And if value is above some threshold - drop further connections.

Cheers,
Ihor

Le mar. 19 mars 2024 à 12:05, Sasmita Panda <spanda at 3clogic.com> a écrit :

> Hi All ,
>
> I have opensips 3.2 version with webrtc configured . I just got an issue
> in production that one browser is trying to establish multiple connections
> frequently which overloads my server which has the impact that other
> browsers are not able to establish a single connection at some points .
>
> Is this possible? I can limit the number of websocket connections per user
> (here the user has a unique username which I used to save as contact in the
> location table ) so that the server will reject the connection above that ?
>
> Please do suggest . Your help is appreciated .
>
> *Thanks & Regards*
> *Sasmita Panda*
> *Senior Network Testing and Software Engineer*
> *3CLogic , ph:07827611765*
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>


-- 
Best regards,
Ihor (Igor)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240320/973f8db0/attachment.html>

From bogdan at opensips.org  Wed Mar 20 12:37:17 2024
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Wed, 20 Mar 2024 14:37:17 +0200
Subject: [OpenSIPS-Users] pn still problems
In-Reply-To: <a8d2f3e21c206d8e1506055671139205a3f189b0@rvgeerligs.nl>
References: <a8d2f3e21c206d8e1506055671139205a3f189b0@rvgeerligs.nl>
Message-ID: <072ebd55-5090-4ae2-a6a5-3a6c2af46892@opensips.org>

Hi,

In the log snippet, I do not see any of the xlogs you have after the 
lookup() ....

Regards

Bogdan-Andrei Iancu

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

On 09.03.2024 15:46, rvg at rvgeerligs.nl wrote:
> Hi All,
>
> I still have problems with opensips3.4 push notifications:
>
> Somehow INVITEs keep looping and get rejected.
>
> Code:
> ...
> route{
>
> ...
>
> if (has_totag()) {
>
> ...
>
> if (!is_method("ACK"))
>         async (pn_process_purr("location"), resume_route);
>
> ...
> }
>
> ...
>
> # do lookup with method filtering
>
> #--
> lookup("location", "method-filtering");
> $var(rc) = $retcode;
> switch ($var(rc)) {
> case 1:
>     # we found at least 1 non-PN contact!
> xlog("L_INFO", "DBG: 1 contacts found non-PN ($var(rc))\n");
>     $var(do_relay) = true;
>     break;
> case 2:
>     # success, but all contacts are PN-enabled, so we're
>     # sending PNs / awaiting re-registrations from them
> xlog("L_INFO", "DBG: contacts found send PN? ($var(rc))\n");
>     $var(do_relay) = false;
>     #$avp(skip_relay) = true;
>     break;
> default:
>     xlog("L_INFO", "DBG: no contacts found ($var(rc))\n");
>     t_reply(404, "Not Found");
>     exit;
> }
>
> if ($var(do_relay) && !t_relay())
>     send_reply(500, "Internal Server Error");
>
> ...
>
> if($var(do_relay) == true)
> route(relay);
> }
>
> ...
>
> from log (looping log, it repeats):
>
> DBG:core:parse_headers: this is the first via
> 2024-03-09T09:41:13.485706+00:00 xsp2 
> /usr/local/sbin/opensips[2061136]: DBG:core:_parse_to: end of header 
> reached, state=10
> 2024-03-09T09:41:13.485748+00:00 xsp2 
> /usr/local/sbin/opensips[2061136]: DBG:core:_parse_to: display={}, 
> ruri={sip:to at dummy.com}
> 2024-03-09T09:41:13.485807+00:00 xsp2 
> /usr/local/sbin/opensips[2061136]: DBG:core:get_hdr_field: <To> [20]; 
> uri=[sip:to at dummy.com]
> 2024-03-09T09:41:13.485854+00:00 xsp2 
> /usr/local/sbin/opensips[2061136]: DBG:core:get_hdr_field: to body 
> [<sip:to at dummy.com>#015#012]
> 2024-03-09T09:41:13.485915+00:00 xsp2 
> /usr/local/sbin/opensips[2061136]: DBG:core:get_hdr_field: cseq 
> <CSeq>: <1>
> 2024-03-09T09:41:13.485962+00:00 xsp2 
> /usr/local/sbin/opensips[2061136]: DBG:core:get_hdr_field: found end 
> of header
> 2024-03-09T09:41:13.486040+00:00 xsp2 
> /usr/local/sbin/opensips[2061136]: DBG:core:parse_headers: 
> flags=ffffffffffffffff
> 2024-03-09T09:41:13.486088+00:00 xsp2 
> /usr/local/sbin/opensips[2061136]: DBG:core:get_dummy_sip_msg: setting 
> as static to 0xffffb1a612c0
> 2024-03-09T09:41:13.486145+00:00 xsp2 
> /usr/local/sbin/opensips[2061136]: DBG:core:evi_raise_event_msg: found 
> subscriber E_UL_CONTACT_REFRESH
> 2024-03-09T09:41:13.486207+00:00 xsp2 
> /usr/local/sbin/opensips[2061136]: 
> DBG:core:dup_ref_script_route_in_shm: dupping 0xffffaa264f60 
> [E_UL_CONTACT_REFRESH], idx 1, ver/cnt 1, to new 0xffffaa26d9e0 
> [E_UL_CONTACT_REFRESH], idx 1, ver/cnt 1
> 2024-03-09T09:41:13.486283+00:00 xsp2 
> /usr/local/sbin/opensips[2061136]: DBG:core:release_dummy_sip_msg: 
> cleaning the static sip msg 0xffffb1a612c0
> 2024-03-09T09:41:13.486352+00:00 xsp2 
> /usr/local/sbin/opensips[2061136]: DBG:core:destroy_avp_list: 
> destroying list (nil)
> 2024-03-09T09:41:13.486409+00:00 xsp2 
> /usr/local/sbin/opensips[2061136]: DBG:core:ipc_handle_job: received 
> job type 0[RPC] from process 6
> 2024-03-09T09:41:13.486467+00:00 xsp2 
> /usr/local/sbin/opensips[2061136]: DBG:core:get_dummy_sip_msg: reusing 
> the static sip msg 0xffffb1a612c0
> 2024-03-09T09:41:13.486533+00:00 xsp2 
> /usr/local/sbin/opensips[2061136]: DBG:core:parse_params: Parsing 
> params 
> for:[sip:rvg at 82.151.164.77:57775;pn-prid=F1B7F53A99A35254A55CCAE2EDF80C1FAE12F353592BB6ED203ADA0175E34AD9:voip;pn-provider=apns;pn-param=ABCD1234.cllkit.voip;pn-silent=1;pn-timeout=0;transport=udp]
> 2024-03-09T09:41:13.486571+00:00 xsp2 
> /usr/local/sbin/opensips[2061136]: ERROR: -- ** --pn_send was called 
> sip:user at dummy.com
> 2024-03-09T09:41:13.486651+00:00 xsp2 
> /usr/local/sbin/opensips[2061136]: ERROR:core:route_param_get: route 
> $param variable accepts only integer indexes
> 2024-03-09T09:41:13.486746+00:00 xsp2 
> /usr/local/sbin/opensips[2061136]: message repeated 2 times: [ 
> ERROR:core:route_param_get: route $param variable accepts only integer 
> indexes]
> 2024-03-09T09:41:13.486787+00:00 xsp2 
> /usr/local/sbin/opensips[2061136]: ERROR:pn params: 
> <null>,#012                   ,#012
> 2024-03-09T09:41:13.486822+00:00 xsp2 
> /usr/local/sbin/opensips[2061136]: DBG:core:release_dummy_sip_msg: 
> cleaning the static sip msg 0xffffb1a612c0
> 2024-03-09T09:41:13.486913+00:00 xsp2 
> /usr/local/sbin/opensips[2061136]: DBG:core:destroy_avp_list: 
> destroying list (nil)
> 2024-03-09T09:41:13.697168+00:00 xsp2 
> /usr/local/sbin/opensips[2061135]: DBG:core:parse_msg: SIP Request:
>
> Any advice appreciated, regards,
>
> Ronald Geerligs
>
>
>
>
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240320/d69b2783/attachment.html>

From spanda at 3clogic.com  Wed Mar 20 12:47:03 2024
From: spanda at 3clogic.com (Sasmita Panda)
Date: Wed, 20 Mar 2024 18:17:03 +0530
Subject: [OpenSIPS-Users] Need some suggestion or help in case of webrtc
 connection with opensips .
In-Reply-To: <CAJTkRNv_wVTuwpxKS-p4jYQryO59=ApCQ5Tsyao8XCohMmX7tg@mail.gmail.com>
References: <CALf-Q45=rLrQVkStCEFaHpnN6ADvbLw+4f42P-qPRv9Q4Hx7sw@mail.gmail.com>
 <CAJTkRNv_wVTuwpxKS-p4jYQryO59=ApCQ5Tsyao8XCohMmX7tg@mail.gmail.com>
Message-ID: <CALf-Q44Y8LejzD-R6CugDZ4ueZjdvOF0uJw-eWS=+2JSRdijcw@mail.gmail.com>

Hi ,

Thank you for your suggestion . I will try that . just to clarify did you
mean that will drop the wss connection of that user ?


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


On Wed, Mar 20, 2024 at 6:05 PM Ihor Olkhovskyi <igorolhovskiy at gmail.com>
wrote:

> Hi!
>
> You can try to use something like cachedb module (for autoexpiry) with
> name of the key like "username_timestamp" and increment it in a case of
> value exists. And if value is above some threshold - drop further
> connections.
>
> Cheers,
> Ihor
>
> Le mar. 19 mars 2024 à 12:05, Sasmita Panda <spanda at 3clogic.com> a écrit :
>
>> Hi All ,
>>
>> I have opensips 3.2 version with webrtc configured . I just got an issue
>> in production that one browser is trying to establish multiple connections
>> frequently which overloads my server which has the impact that other
>> browsers are not able to establish a single connection at some points .
>>
>> Is this possible? I can limit the number of websocket connections per
>> user (here the user has a unique username which I used to save as contact
>> in the location table ) so that the server will reject the connection above
>> that ?
>>
>> Please do suggest . Your help is appreciated .
>>
>> *Thanks & Regards*
>> *Sasmita Panda*
>> *Senior Network Testing and Software Engineer*
>> *3CLogic , ph:07827611765*
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>
>
> --
> Best regards,
> Ihor (Igor)
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240320/d7e3e554/attachment-0001.html>

From bogdan at opensips.org  Wed Mar 20 13:21:36 2024
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Wed, 20 Mar 2024 15:21:36 +0200
Subject: [OpenSIPS-Users] Need some help on opensips error for wss
 handshek .
In-Reply-To: <CALf-Q44nYwthB2z=ignY9uXwrEWhb6tgrXom24v2HwXFDd7UoA@mail.gmail.com>
References: <CALf-Q44nYwthB2z=ignY9uXwrEWhb6tgrXom24v2HwXFDd7UoA@mail.gmail.com>
Message-ID: <e98e705b-0968-4828-84d7-b101367d2a14@opensips.org>

Hi,

OpenSIPS does not like that 1.1 version in the VIA hdr - it expects 2.0 
(the SIP version).

Regards,

Bogdan-Andrei Iancu

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

On 12.03.2024 10:57, Sasmita Panda wrote:
> Hi All ,
>
> 1"  :callID 080a9ef8-3911-6c41-689c-fbb5d02e3aae
> Mar 12 08:23:11 localhost /usr/sbin/opensips[12987]: 
> ERROR:core:parse_via: bad char <1> on state 100
> Mar 12 08:23:11 localhost /usr/sbin/opensips[12987]: 
> ERROR:core:parse_via:  <1.1 p1wsa01.rivagecapital.com:80 
> <http://p1wsa01.rivagecapital.com:80> 
> (Cisco-WSA/12.5.4-011)#015#012#015#012>
> Mar 12 08:23:11 localhost /usr/sbin/opensips[12987]: 
> ERROR:core:parse_via: via parse failed
> Mar 12 08:23:11 localhost /usr/sbin/opensips[12987]: 
> ERROR:core:get_hdr_field: bad via
> Mar 12 08:23:11 localhost /usr/sbin/opensips[12987]: 
> INFO:core:parse_headers: bad header field
> Mar 12 08:23:11 localhost /usr/sbin/opensips[12987]: 
> ERROR:proto_wss:ws_parse_req_handshake: cannot parse 
> headers#012Upgrade: websocket#015#012Connection: Upgrade#015#012Host: 
> ir-webrtc2.3ccloud.com#015#012Pragma 
> <http://ir-webrtc2.3ccloud.com#015#012Pragma>: 
> no-cache#015#012Cache-Control: no-cache#015#012User-Agent: Mozilla/5.0 
> (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) 
> Chrome/122.0.0.0 <http://122.0.0.0> Safari/537.36 
> Edg/122.0.0.0#015#012Origin <http://122.0.0.0#015#012Origin>: 
> https://ir-static.3ccloud.com#015#012Sec-WebSocket-Version 
> <https://ir-static.3ccloud.com#015#012Sec-WebSocket-Version>: 
> 13#015#012Accept-Encoding: gzip, br#015#012Accept-Language: 
> en-GB,en;q=0.9,en-US;q=0.8#015#012Sec-WebSocket-Key: 
> I/8XqtXyBCAGorZYjnTYQA==#015#012Sec-WebSocket-Extensions: 
> permessage-deflate; 
> client_max_window_bits#015#012Sec-WebSocket-Protocol: 
> sip#015#012X-IMForwards: 20#015#012Via: 1.1 
> p1wsa01.rivagecapital.com:80 <http://p1wsa01.rivagecapital.com:80> 
> (Cisco-WSA/12.5.4-011)#015#012#015#012
>
>
>  I am getting this error on my opensips server where I am running 
> webrtc . What is this error for ?
>
>
> */Thanks & Regards/*
> /Sasmita Panda/
> /Senior Network Testing and Software Engineer/
> /3CLogic , ph:07827611765/
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240320/59c17cb5/attachment.html>

From bogdan at opensips.org  Wed Mar 20 13:29:02 2024
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Wed, 20 Mar 2024 15:29:02 +0200
Subject: [OpenSIPS-Users] OPENSIP 3.4 send_reply and tight matching
	failed
In-Reply-To: <858EE736-AF3A-46A4-8EBC-8ABF8BC30A8E@free.fr>
References: <84BD48FD-8F95-4798-8201-7F87E54DAE4C@free.fr>
 <858EE736-AF3A-46A4-8EBC-8ABF8BC30A8E@free.fr>
Message-ID: <027f24dd-f225-468b-9d05-ce31e3a3ee1c@opensips.org>

Hi,

The script snippet has nothing to do with the matching - it is about a 
200-ok ACK to be matched by the dialog module and the TO-tag does not 
match at all.

The link to the trace expired, if you could repost.

Regards,

Bogdan-Andrei Iancu

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

On 12.03.2024 14:57, Alain Bieuzent wrote:
>
> Hi all,
>
> I am in the process of migrating my proxies from 3.3.9 to 3.4.4.
>
> In 3.4 I find myself with a fault when I try to rewrite a final cause.
>
> if (t_check_status("500"))
>
> {
>
> send_reply(503,"Service Unavailable");
>
> exit;
>
>           }
>
> with 3.3 version, this code works perfectly, since 3.4 I have this error:
>
> WARNING:dialog:dlg_onroute: tight matching failed for ACK with 
> callid='67457c401e9ea52e2750100979253a7a at 10.101.180.177:5060'/52, 
> ftag='as5328cea7'/10, ttag='b5a7-2a346bb9d510da893a ee7cda850584cb'/37 
> and direction=1
>
> WARNING:dialog:dlg_onroute: dialog identification elements are 
> callid='67457c401e9ea52e2750100979253a7a at 10.101.180.177:5060'/52, 
> caller tag='as5328cea7'/10, callee tag='3919223738-770090972'/ 20
>
> Has anyone encountered this error before?
>
> Complete traces here : https://www.transfernow.net/dl/20240312qvAFfIAL.
>
> Regards
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240320/11a67231/attachment.html>

From spanda at 3clogic.com  Wed Mar 20 13:30:09 2024
From: spanda at 3clogic.com (Sasmita Panda)
Date: Wed, 20 Mar 2024 19:00:09 +0530
Subject: [OpenSIPS-Users] Need some help on opensips error for wss
 handshek .
In-Reply-To: <e98e705b-0968-4828-84d7-b101367d2a14@opensips.org>
References: <CALf-Q44nYwthB2z=ignY9uXwrEWhb6tgrXom24v2HwXFDd7UoA@mail.gmail.com>
 <e98e705b-0968-4828-84d7-b101367d2a14@opensips.org>
Message-ID: <CALf-Q44WNwsU8owQ5ZNErnwXkxGuzzKOhKT7fWtcVTNxiy+YLw@mail.gmail.com>

Hi Bogdan,
I appreciate your reply .

How can I suggest modifying this header ? Because I have seen this for some
remote agents who run in the browser . I don't have access to the browser .
The browser which got connected successfully I couldn't see such types of
logs  .

What causes this header version in the wss connection ?


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


On Wed, Mar 20, 2024 at 6:51 PM Bogdan-Andrei Iancu <bogdan at opensips.org>
wrote:

> Hi,
>
> OpenSIPS does not like that 1.1 version in the VIA hdr - it expects 2.0
> (the SIP version).
>
> Regards,
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>   https://www.opensips-solutions.com
>   https://www.siphub.com
>
> On 12.03.2024 10:57, Sasmita Panda wrote:
>
> Hi All ,
>
> 1"  :callID 080a9ef8-3911-6c41-689c-fbb5d02e3aae
> Mar 12 08:23:11 localhost /usr/sbin/opensips[12987]: ERROR:core:parse_via:
> bad char <1> on state 100
> Mar 12 08:23:11 localhost /usr/sbin/opensips[12987]: ERROR:core:parse_via:
>  <1.1 p1wsa01.rivagecapital.com:80 (Cisco-WSA/12.5.4-011)#015#012#015#012>
> Mar 12 08:23:11 localhost /usr/sbin/opensips[12987]: ERROR:core:parse_via:
> via parse failed
> Mar 12 08:23:11 localhost /usr/sbin/opensips[12987]:
> ERROR:core:get_hdr_field: bad via
> Mar 12 08:23:11 localhost /usr/sbin/opensips[12987]:
> INFO:core:parse_headers: bad header field
> Mar 12 08:23:11 localhost /usr/sbin/opensips[12987]: ERROR:proto_
> wss:ws_parse_req_handshake: cannot parse headers#012Upgrade:
> websocket#015#012Connection: Upgrade#015#012Host:
> ir-webrtc2.3ccloud.com#015#012Pragma
> <http://ir-webrtc2.3ccloud.com#015%23012Pragma>:
> no-cache#015#012Cache-Control: no-cache#015#012User-Agent: Mozilla/5.0
> (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/
> 122.0.0.0 Safari/537.36 Edg/122.0.0.0#015#012Origin
> <http://122.0.0.0#015%23012Origin>:
> https://ir-static.3ccloud.com#015#012Sec-WebSocket-Version:
> 13#015#012Accept-Encoding: gzip, br#015#012Accept-Language:
> en-GB,en;q=0.9,en-US;q=0.8#015#012Sec-WebSocket-Key:
> I/8XqtXyBCAGorZYjnTYQA==#015#012Sec-WebSocket-Extensions:
> permessage-deflate; client_max_window_bits#015#012Sec-WebSocket-Protocol:
> sip#015#012X-IMForwards: 20#015#012Via: 1.1 p1wsa01.rivagecapital.com:80
> (Cisco-WSA/12.5.4-011)#015#012#015#012
>
>
>  I am getting this error on my opensips server where I am running webrtc .
> What is this error for ?
>
>
> *Thanks & Regards*
> *Sasmita Panda*
> *Senior Network Testing and Software Engineer*
> *3CLogic , ph:07827611765*
>
> _______________________________________________
> Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240320/9636e877/attachment-0001.html>

From bogdan at opensips.org  Wed Mar 20 13:38:25 2024
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Wed, 20 Mar 2024 15:38:25 +0200
Subject: [OpenSIPS-Users] Regex help.
In-Reply-To: <b70c1bd106d14b65848fbc980cef4c8b@tetab.nu>
References: <b70c1bd106d14b65848fbc980cef4c8b@tetab.nu>
Message-ID: <79c8fcfb-408a-4f72-b747-f7cd59bf3cda@opensips.org>

Hi,

Use the s.subst [1] transformation to replace any continues set of 
spaces with a semi-colon

[1] https://www.opensips.org/Documentation/Script-Tran-3-4#re.subst

Regards,

Bogdan-Andrei Iancu

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

On 12.03.2024 19:18, Stefan Carlsson wrote:
>
> Hi !
>
> What is the easiest form to transform this:
>
> o=SYS   1710262255    1710262255    IN    IP4     123.123.123.123
>
> Into
>
> SYS;1710262255;1710262255;IN;IP4;123.123.123.123
>
> for later retrieval via an index function.
>
> [0] = SYS
>
> [1] = 1710262255
>
> [2] = 1710262255
>
> [3] = IN
>
> etc ….
>
> I need to get my hands on the session parameters …
>
> Thanks in advance …
>
> //S
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240320/0d6fca68/attachment.html>

From bogdan at opensips.org  Wed Mar 20 13:40:46 2024
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Wed, 20 Mar 2024 15:40:46 +0200
Subject: [OpenSIPS-Users] How to change the a=sendrecv in SDP
In-Reply-To: <f1bd56fb725541aa88a2e6e87b6025c0@tetab.nu>
References: <f1bd56fb725541aa88a2e6e87b6025c0@tetab.nu>
Message-ID: <e5803586-b75e-400b-a358-f8c5720221eb@opensips.org>

Hi,

See
https://opensips.org/html/docs/modules/3.4.x/textops.html#func_replace_body_all 

or
https://opensips.org/html/docs/modules/3.4.x/textops.html#func_subst_body

Regards

Bogdan-Andrei Iancu

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

On 13.03.2024 17:19, Stefan Carlsson wrote:
>
> Hi (again …)
>
> I’ve found out how to strip out the o= to separate values …  but now I 
> want to change the a=sendrecv to a=sendonly
>
> The cause is  that our pbx’s don’t conform to either RFC2543 hold 
> type: null connection IP detected,  nor RFC3264 hold type: inactive or 
> sendonly attributes detected
>
> but use the RFC5359 re-invite indicating call hold via session version 
> incremented by  1.
>
> So now I’ve trying to make a workaround with the help of OpenSips ..
>
> Can you please help me with that …
>
> // Regards …
>
> Stefan Carlsson
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240320/10784628/attachment.html>

From bogdan at opensips.org  Wed Mar 20 13:42:32 2024
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Wed, 20 Mar 2024 15:42:32 +0200
Subject: [OpenSIPS-Users] SDP
In-Reply-To: <CAJh_-cBOLA_zfLWrfYqX2rb8divky_JBt1ekyNDzSpH9-2_gYg@mail.gmail.com>
References: <CAJh_-cBOLA_zfLWrfYqX2rb8divky_JBt1ekyNDzSpH9-2_gYg@mail.gmail.com>
Message-ID: <3985dcbd-4ce9-46bd-96b6-a4ae02d074fa@opensips.org>

The online Manual should be your Bible here ;)

https://opensips.org/Documentation/Script-CoreVar-3-4#rb

Regards,

Bogdan-Andrei Iancu

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

On 14.03.2024 06:16, Prathibha B wrote:
> How to see the SDP in opensips?
>
> -- 
> Regards,
> B.Prathibha
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240320/ae00ffa0/attachment.html>

From bogdan at opensips.org  Wed Mar 20 13:43:42 2024
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Wed, 20 Mar 2024 15:43:42 +0200
Subject: [OpenSIPS-Users] SDP
In-Reply-To: <c8530347bc2844ed9341aa1ab7b6ff0e@tetab.nu>
References: <CAJh_-cBOLA_zfLWrfYqX2rb8divky_JBt1ekyNDzSpH9-2_gYg@mail.gmail.com>
 <c8530347bc2844ed9341aa1ab7b6ff0e@tetab.nu>
Message-ID: <a7f44e25-2669-41e5-8269-f2359554a521@opensips.org>

Nothing is impossible as time as you search in the right place (aka the 
Manual). See my reply on your thread.

Regards,

Bogdan-Andrei Iancu

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

On 14.03.2024 09:50, Stefan Carlsson wrote:
>
> Hi !
>
> You can use the module sipmsgops to view and change some of the ADP 
> fields such as codecs and streams … but unfortunately you don’t have
>
> complete control of the SDP compared to what it seems could be done on 
> the Kamailio SIP router
>
> I need to change the a=sendrecv field and it seems to be impossible ☹
>
> Regards …
>
> _________________________________
>
> Stefan Carlsson
>
> *From:* Users <users-bounces at lists.opensips.org> *On Behalf Of 
> *Prathibha B
> *Sent:* Thursday, 14 March, 2024 05:16
> *To:* OpenSIPS users mailling list <users at lists.opensips.org>
> *Subject:* [OpenSIPS-Users] SDP
>
> How to see the SDP in opensips?
>
> -- 
>
> Regards,
>
> B.Prathibha
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240320/beceaf3f/attachment-0001.html>

From babak.yakhchali at gmail.com  Wed Mar 13 11:55:24 2024
From: babak.yakhchali at gmail.com (Babak Yakhchali)
Date: Wed, 13 Mar 2024 15:25:24 +0330
Subject: [OpenSIPS-Users] how to debug many dialogs stuck in state 5?
Message-ID: <CAD3oNZxOXVR+WkKGD6x3OqCSpF=EewO+XJJ5ZOvE8WGBrYrSJA@mail.gmail.com>

Hi
When calling and immediately cancelling, the call is ended but dlg_list
shows the dialog stuck in state 5. Increasing log level to 4 shows these
messages:
Mar 13 15:15:37 : DBG:tm:timer_routine: timer routine:3,tl=0x7f1c861d06e0
next=(nil), timeout=26
Mar 13 15:15:37 : DBG:tm:delete_handler: removing 0x7f1c861d0630
Mar 13 15:15:37 : DBG:tm:delete_cell: delete_cell 0x7f1c861d0630: can't
delete -- still reffed (-1)
Mar 13 15:15:37 : DBG:tm:set_timer: relative timeout is 2
Mar 13 15:15:37 : DBG:tm:insert_timer_unsafe: [3]: 0x7f1c861d06e0 (28)
Mar 13 15:15:37 : DBG:tm:delete_handler: done
Mar 13 15:15:39 : DBG:tm:timer_routine: timer routine:3,tl=0x7f1c861d06e0
next=(nil), timeout=28
Mar 13 15:15:39 : DBG:tm:delete_handler: removing 0x7f1c861d0630
Mar 13 15:15:39 : DBG:tm:delete_cell: delete_cell 0x7f1c861d0630: can't
delete -- still reffed (-1)
Mar 13 15:15:39 : DBG:tm:set_timer: relative timeout is 2
Mar 13 15:15:39 : DBG:tm:insert_timer_unsafe: [3]: 0x7f1c861d06e0 (30)
Mar 13 15:15:39 : DBG:tm:delete_handler: done

How can I debug the issue? What are the possible causes of this?
thanks
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240313/5337eb28/attachment-0001.html>

From bogdan at opensips.org  Wed Mar 20 13:15:21 2024
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Wed, 20 Mar 2024 15:15:21 +0200
Subject: [OpenSIPS-Users] utimer_ticker warning in opensips 3.2
In-Reply-To: <CALf-Q45xVfjagrctOVtAqEkEhPzeVNWK9Zj7Kfh4_Xow1QjOUQ@mail.gmail.com>
References: <CALf-Q442AqxhLDxKt6_psUWUzcC1aGfZ9CrHvYXH_BU5GFGL2w@mail.gmail.com>
 <CALf-Q45dJ=hVdJPxsB7dU1PhER4VYBnHSU+3Jn9RwrvnZ1a=Hg@mail.gmail.com>
 <CALf-Q45xVfjagrctOVtAqEkEhPzeVNWK9Zj7Kfh4_Xow1QjOUQ@mail.gmail.com>
Message-ID: <2e986980-6548-4cd8-b1e5-cbbc65f60fe3@opensips.org>

Hi,

How the two reports fit together here ? there are completely separate 
experiences on different runs?? or if you start opensips first you get 
the warnings and later it crashes ??
For the crash part, I see a core file was generated - could you extract 
the backtrace and post here ? (see 
https://opensips.org/Documentation/TroubleShooting-Crash)

Regards

Bogdan-Andrei Iancu

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

On 11.03.2024 15:04, Sasmita Panda wrote:
> Any update on this ?
>
>
> */Thanks & Regards/*
> /Sasmita Panda/
> /Senior Network Testing and Software Engineer/
> /3CLogic , ph:07827611765/
>
>
> On Mon, Mar 11, 2024 at 12:03 PM Sasmita Panda <spanda at 3clogic.com> wrote:
>
>     With the same server configuration and opensips version I am
>     getting below error as well .
>
>     CRITICAL:core:fm_free: freeing already freed shm pointer
>     (0x7fc110e0b408), first free: (null): (null)(0) - aborting!
>
>      /usr/local/sbin/opensips[215171]: INFO:core:handle_sigs: child
>     process 215185 exited by a signal 6
>      /usr/local/sbin/opensips[215171]: INFO:core:handle_sigs: core was
>     generated
>      /usr/local/sbin/opensips[215171]: INFO:core:handle_sigs:
>     terminating due to SIGCHLD
>      /usr/local/sbin/opensips[215172]: Memory status (pkg):
>      /usr/local/sbin/opensips[215172]: fm_status (0x7fc2907ff010):
>      /usr/local/sbin/opensips[215174]: INFO:core:sig_usr: signal 15
>     received
>      /usr/local/sbin/opensips[215172]: heap size= 33554432
>      /usr/local/sbin/opensips[215174]: Memory status (pkg):
>      /usr/local/sbin/opensips[215172]: used= 3710048,
>     used+overhead=3801344, free=29844384
>      /usr/local/sbin/opensips[215174]: fm_status (0x7fc2907ff010):
>      /usr/local/sbin/opensips[215172]: max used (+overhead)= 3801344
>      /usr/local/sbin/opensips[215174]: heap size= 33554432
>      /usr/local/sbin/opensips[215172]: dumping free list:
>      /usr/local/sbin/opensips[215174]: used= 229752,
>     used+overhead=318936, free=33324680
>      /usr/local/sbin/opensips[215172]: hash =   1 fragments no.:    
>     1, unused:     0#012#011#011 bucket size: 8 -         8 (first    
>         8)
>      /usr/local/sbin/opensips[215174]: max used (+overhead)= 385792
>      /usr/local/sbin/opensips[215174]: dumping free list:
>      /usr/local/sbin/opensips[215172]: hash =  18 fragments no.:    
>     1, unused:     0#012#011#011 bucket size: 144 -       144 (first  
>         144)
>      /usr/local/sbin/opensips[215174]: hash =   7 fragments no.:  
>     139, unused:     0#012#011#011 bucket size:  56 -        56 (first
>            56)
>      /usr/local/sbin/opensips[215172]: hash = 2059 fragments no.:    
>     1, unused:     0#012#011#011 bucket size:  16777216 -  33554432
>     (first  29752936)
>      /usr/local/sbin/opensips[215174]: hash =  13 fragments no.:  
>      37, unused:     0#012#011#011 bucket size: 104 -       104 (first
>           104)
>      /usr/local/sbin/opensips[215172]: TOTAL:      3 free fragments =
>     29753088 free bytes
>      /usr/local/sbin/opensips[215172]: TOTAL: 48 overhead
>      /usr/local/sbin/opensips[215174]: hash =  16 fragments no.:  
>      61, unused:     0#012#011#011 bucket size: 128 -       128 (first
>           128)
>      /usr/local/sbin/opensips[215172]: -----------------------------
>      /usr/local/sbin/opensips[215174]: hash =  31 fragments no.:  
>     152, unused:     0#012#011#011 bucket size: 248 -       248 (first
>           248)
>      /usr/local/sbin/opensips[215174]: hash =  68 fragments no.:  
>      16, unused:     0#012#011#011 bucket size: 544 -       544 (first
>           544)
>      /usr/local/sbin/opensips[215174]: hash = 105 fragments no.:    
>     1, unused:     0#012#011#011 bucket size: 840 -       840 (first  
>         840)
>      /usr/local/sbin/opensips[215174]: hash = 2059 fragments no.:    
>     1, unused:     0#012#011#011 bucket size:  16777216 -  33554432
>     (first  33168816)
>      /usr/local/sbin/opensips[215174]: TOTAL:    407 free fragments =
>     33235496 free bytes
>      /usr/local/sbin/opensips[215174]: TOTAL: 48 overhead
>      /usr/local/sbin/opensips[215174]: -----------------------------
>      /usr/local/sbin/opensips[215176]: Memory status (pkg):
>      /usr/local/sbin/opensips[215176]: fm_status (0x7fc2907ff010):
>      /usr/local/sbin/opensips[215176]: heap size= 33554432
>      /usr/local/sbin/opensips[215176]: used= 3705480,
>     used+overhead=3796584, free=29848952
>      /usr/local/sbin/opensips[215176]: max used (+overhead)= 3798064
>      /usr/local/sbin/opensips[215176]: dumping free list:
>      /usr/local/sbin/opensips[215176]: hash =   2 fragments no.:    
>     2, unused:     0#012#011#011 bucket size:  16 -        16 (first  
>          16)
>      /usr/local/sbin/opensips[215176]: hash =   3 fragments no.:    
>     1, unused:     0#012#011#011 bucket size:  24 -        24 (first  
>          24)
>      /usr/local/sbin/opensips[215176]: hash =  16 fragments no.:    
>     1, unused:     0#012#011#011 bucket size: 128 -       128 (first  
>         128)
>      /usr/local/sbin/opensips[215175]: Memory status (pkg):
>      /usr/local/sbin/opensips[215175]: fm_status (0x7fc2907ff010):
>      /usr/local/sbin/opensips[215175]: heap size= 33554432
>      /usr/local/sbin/opensips[215176]: hash = 2059 fragments no.:    
>     1, unused:     0#012#011#011 bucket size:  16777216 -  33554432
>     (first  29757664)
>      /usr/local/sbin/opensips[215175]: used= 3705480,
>     used+overhead=3796584, free=29848952
>      /usr/local/sbin/opensips[215176]: TOTAL:      5 free fragments =
>     29757848 free bytes
>      /usr/local/sbin/opensips[215175]: max used (+overhead)= 3798064
>      /usr/local/sbin/opensips[215176]: TOTAL: 48 overhead
>      /usr/local/sbin/opensips[215176]: -----------------------------
>      /usr/local/sbin/opensips[215175]: dumping free list:
>      /usr/local/sbin/opensips[215175]: hash =   2 fragments no.:    
>     2, unused:     0#012#011#011 bucket size:  16 -        16 (first  
>          16)
>      /usr/local/sbin/opensips[215175]: hash =   3 fragments no.:    
>     1, unused:     0#012#011#011 bucket size:  24 -        24 (first  
>          24)
>      /usr/local/sbin/opensips[215175]: hash =  16 fragments no.:    
>     1, unused:     0#012#011#011 bucket size: 128 -       128 (first  
>         128)
>      /usr/local/sbin/opensips[215175]: hash = 2059 fragments no.:    
>     1, unused:     0#012#011#011 bucket size:  16777216 -  33554432
>     (first  29757664)
>      /usr/local/sbin/opensips[215175]: TOTAL:      5 free fragments =
>     29757848 free bytes
>      /usr/local/sbin/opensips[215175]: TOTAL: 48 overhead
>      /usr/local/sbin/opensips[215175]: -----------------------------
>      /usr/local/sbin/opensips[215171]: INFO:core:shutdown_opensips:
>     process 3(215174) [timer] terminated, still waiting for 13 more
>      /usr/local/sbin/opensips[215171]: INFO:core:shutdown_opensips:
>     process 4(215175) [SIP receiver udp:192.168.33.171:5060
>     <http://192.168.33.171:5060>] terminated, still waiting for 12 more
>      /usr/local/sbin/opensips[215171]: INFO:core:shutdown_opensips:
>     process 5(215176) [SIP receiver udp:192.168.33.171:5060
>     <http://192.168.33.171:5060>] terminated, still waiting for 11 more
>      /usr/local/sbin/opensips[215171]: INFO:core:shutdown_opensips:
>     process 1(215172) [MI FIFO] terminated, still waiting for 10 more
>      /usr/local/sbin/opensips[215173]: INFO:core:sig_usr: signal 15
>     received
>      /usr/local/sbin/opensips[215173]: Memory status (pkg):
>      /usr/local/sbin/opensips[215173]: fm_status (0x7fc2907ff010):
>      /usr/local/sbin/opensips[215173]: heap size= 33554432
>      /usr/local/sbin/opensips[215173]: used= 229752,
>     used+overhead=318936, free=33324680
>      /usr/local/sbin/opensips[215173]: max used (+overhead)= 385792
>      /usr/local/sbin/opensips[215173]: dumping free list:
>      /usr/local/sbin/opensips[215173]: hash =   7 fragments no.:  
>     139, unused:     0#012#011#011 bucket size:  56 -        56 (first
>            56)
>      /usr/local/sbin/opensips[215173]: hash =  13 fragments no.:  
>      37, unused:     0#012#011#011 bucket size: 104 -       104 (first
>           104)
>      /usr/local/sbin/opensips[215173]: hash =  16 fragments no.:  
>      61, unused:     0#012#011#011 bucket size: 128 -       128 (first
>           128)
>      /usr/local/sbin/opensips[215173]: hash =  31 fragments no.:  
>     152, unused:     0#012#011#011 bucket size: 248 -       248 (first
>           248)
>      /usr/local/sbin/opensips[215173]: hash =  68 fragments no.:  
>      16, unused:     0#012#011#011 bucket size: 544 -       544 (first
>           544)
>      /usr/local/sbin/opensips[215173]: hash = 105 fragments no.:    
>     1, unused:     0#012#011#011 bucket size: 840 -       840 (first  
>         840)
>      /usr/local/sbin/opensips[215173]: hash = 2059 fragments no.:    
>     1, unused:     0#012#011#011 bucket size:  16777216 -  33554432
>     (first  33168816)
>      /usr/local/sbin/opensips[215173]: TOTAL:    407 free fragments =
>     33235496 free bytes
>      /usr/local/sbin/opensips[215173]: TOTAL: 48 overhead
>      /usr/local/sbin/opensips[215173]: -----------------------------
>      /usr/local/sbin/opensips[215171]: INFO:core:shutdown_opensips:
>     process 2(215173) [time_keeper] terminated, still waiting for 9 more
>      /usr/local/sbin/opensips[215171]: INFO:core:cleanup: cleanup
>      /usr/local/sbin/opensips[215171]: CRITICAL:core:sig_alarm_abort:
>     BUG - shutdown timeout triggered, dying...
>     */
>     /*
>     */Why is the service crashing ? /*
>     */
>     /*
>     */Thanks & Regards/*
>     /Sasmita Panda/
>     /Senior Network Testing and Software Engineer/
>     /3CLogic , ph:07827611765/
>
>
>     On Mon, Mar 11, 2024 at 11:52 AM Sasmita Panda
>     <spanda at 3clogic.com> wrote:
>
>         Hi All ,
>
>         Mar 11 05:57:02 ip-192-168-33-171
>         /usr/local/sbin/opensips[213843]: INFO:proto_ws:mod_init:
>         initializing WebSocket protocol
>         Mar 11 05:57:03 ip-192-168-33-171
>         /usr/local/sbin/opensips[213846]: WARNING:core:utimer_ticker:
>         utimer task <tm-utimer> already scheduled 100 ms ago (now 290
>         ms), delaying execution
>         Mar 11 05:57:03 ip-192-168-33-171
>         /usr/local/sbin/opensips[213846]: WARNING:core:utimer_ticker:
>         utimer task <tm-utimer> already scheduled 200 ms ago (now 390
>         ms), delaying execution
>         Mar 11 05:57:03 ip-192-168-33-171
>         /usr/local/sbin/opensips[213846]: WARNING:core:utimer_ticker:
>         utimer task <tm-utimer> already scheduled 300 ms ago (now 490
>         ms), delaying execution
>         Mar 11 05:57:03 ip-192-168-33-171
>         /usr/local/sbin/opensips[213846]: WARNING:core:utimer_ticker:
>         utimer task <tm-utimer> already scheduled 400 ms ago (now 590
>         ms), delaying execution
>         Mar 11 05:57:03 ip-192-168-33-171
>         /usr/local/sbin/opensips[213846]: WARNING:core:utimer_ticker:
>         utimer task <tm-utimer> already scheduled 500 ms ago (now 690
>         ms), delaying execution
>         Mar 11 05:57:03 ip-192-168-33-171
>         /usr/local/sbin/opensips[213846]: WARNING:core:utimer_ticker:
>         utimer task <tm-utimer> already scheduled 600 ms ago (now 790
>         ms), delaying execution
>         Mar 11 05:57:03 ip-192-168-33-171
>         /usr/local/sbin/opensips[213846]: WARNING:core:utimer_ticker:
>         utimer task <tm-utimer> already scheduled 700 ms ago (now 890
>         ms), delaying execution
>         Mar 11 05:57:03 ip-192-168-33-171
>         /usr/local/sbin/opensips[213846]: WARNING:core:utimer_ticker:
>         utimer task <tm-utimer> already scheduled 800 ms ago (now 990
>         ms), delaying execution
>         Mar 11 05:57:03 ip-192-168-33-171
>         /usr/local/sbin/opensips[213846]: WARNING:core:utimer_ticker:
>         utimer task <tm-utimer> already scheduled 900 ms ago (now 1090
>         ms), delaying execution
>         Mar 11 05:57:03 ip-192-168-33-171
>         /usr/local/sbin/opensips[213846]: WARNING:core:utimer_ticker:
>         utimer task <tm-utimer> already scheduled 1000 ms ago (now
>         1190 ms), delaying execution
>         Mar 11 05:57:04 ip-192-168-33-171
>         /usr/local/sbin/opensips[213846]: WARNING:core:utimer_ticker:
>         utimer task <tm-utimer> already scheduled 1100 ms ago (now
>         1290 ms), delaying execution
>         Mar 11 05:57:04 ip-192-168-33-171
>         /usr/local/sbin/opensips[213846]: WARNING:core:utimer_ticker:
>         utimer task <tm-utimer> already scheduled 1200 ms ago (now
>         1390 ms), delaying execution
>         Mar 11 05:57:04 ip-192-168-33-171
>         /usr/local/sbin/opensips[213846]: WARNING:core:utimer_ticker:
>         utimer task <tm-utimer> already scheduled 1300 ms ago (now
>         1490 ms), delaying execution
>         Mar 11 05:57:04 ip-192-168-33-171
>         /usr/local/sbin/opensips[213846]: WARNING:core:utimer_ticker:
>         utimer task <tm-utimer> already scheduled 1400 ms ago (now
>         1590 ms), delaying execution
>         Mar 11 05:57:04 ip-192-168-33-171
>         /usr/local/sbin/opensips[213846]: WARNING:core:utimer_ticker:
>         utimer task <tm-utimer> already scheduled 1500 ms ago (now
>         1690 ms), delaying execution
>         Mar 11 05:57:04 ip-192-168-33-171
>         /usr/local/sbin/opensips[213846]: WARNING:core:utimer_ticker:
>         utimer task <tm-utimer> already scheduled 1600 ms ago (now
>         1790 ms), delaying execution
>         Mar 11 05:57:04 ip-192-168-33-171
>         /usr/local/sbin/opensips[213846]: WARNING:core:utimer_ticker:
>         utimer task <tm-utimer> already scheduled 1700 ms ago (now
>         1890 ms), delaying execution
>         Mar 11 05:57:04 ip-192-168-33-171
>         /usr/local/sbin/opensips[213846]: WARNING:core:utimer_ticker:
>         utimer task <tm-utimer> already scheduled 1790 ms ago (now
>         1980 ms), delaying execution
>         Mar 11 05:57:04 ip-192-168-33-171
>         /usr/local/sbin/opensips[213846]: WARNING:core:timer_ticker:
>         timer task <tm-timer> already scheduled 990 ms ago (now 1980
>         ms), delaying execution
>         */
>         /*
>         */What is this warning for? Whenever I am starting my openisps
>         service this warning comes . Although the service seems like
>         it's running but it's not listening on the socket exposed . 
>         How to resolve this ?/*
>         */
>         /*
>         */usr/local/sbin/opensips  -V*
>         version: opensips 3.2.3 (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.
>         svn revision: 3831:3878
>         main.c compiled on 07:52:40 Mar 29 2023 with gcc 11
>
>         *cat /etc/*release*
>         Amazon Linux release 2023 (Amazon Linux)
>         NAME="Amazon Linux"
>         VERSION="2023"
>         ID="amzn"
>         ID_LIKE="fedora"
>         VERSION_ID="2023"
>         PLATFORM_ID="platform:al2023"
>         PRETTY_NAME="Amazon Linux 2023"
>         ANSI_COLOR="0;33"
>         CPE_NAME="cpe:2.3:o:amazon:amazon_linux:2023"
>         HOME_URL="https://aws.amazon.com/linux/"
>         BUG_REPORT_URL="https://github.com/amazonlinux/amazon-linux-2023"
>         SUPPORT_END="2028-03-01"
>         Amazon Linux release 2023 (Amazon Linux)
>         */
>         /*
>         */
>         /*
>         */Thanks & Regards/*
>         /Sasmita Panda/
>         /Senior Network Testing and Software Engineer/
>         /3CLogic , ph:07827611765/
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240320/7c75e6b8/attachment-0001.html>

From bogdan at opensips.org  Wed Mar 20 13:49:49 2024
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Wed, 20 Mar 2024 15:49:49 +0200
Subject: [OpenSIPS-Users] how to debug many dialogs stuck in state 5?
In-Reply-To: <CAD3oNZxOXVR+WkKGD6x3OqCSpF=EewO+XJJ5ZOvE8WGBrYrSJA@mail.gmail.com>
References: <CAD3oNZxOXVR+WkKGD6x3OqCSpF=EewO+XJJ5ZOvE8WGBrYrSJA@mail.gmail.com>
Message-ID: <eaddf0cc-ce60-4293-a812-deb931a9fb13@opensips.org>

Hi,

What OpenSIPS version are you using? and what module do you use on top 
of the dialog module?

Regards,

Bogdan-Andrei Iancu

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

On 13.03.2024 13:55, Babak Yakhchali wrote:
> Hi
> When calling and immediately cancelling, the call is ended but 
> dlg_list shows the dialog stuck in state 5. Increasing log level to 4 
> shows these messages:
> Mar 13 15:15:37 : DBG:tm:timer_routine: timer 
> routine:3,tl=0x7f1c861d06e0 next=(nil), timeout=26
> Mar 13 15:15:37 : DBG:tm:delete_handler: removing 0x7f1c861d0630
> Mar 13 15:15:37 : DBG:tm:delete_cell: delete_cell 0x7f1c861d0630: 
> can't delete -- still reffed (-1)
> Mar 13 15:15:37 : DBG:tm:set_timer: relative timeout is 2
> Mar 13 15:15:37 : DBG:tm:insert_timer_unsafe: [3]: 0x7f1c861d06e0 (28)
> Mar 13 15:15:37 : DBG:tm:delete_handler: done
> Mar 13 15:15:39 : DBG:tm:timer_routine: timer 
> routine:3,tl=0x7f1c861d06e0 next=(nil), timeout=28
> Mar 13 15:15:39 : DBG:tm:delete_handler: removing 0x7f1c861d0630
> Mar 13 15:15:39 : DBG:tm:delete_cell: delete_cell 0x7f1c861d0630: 
> can't delete -- still reffed (-1)
> Mar 13 15:15:39 : DBG:tm:set_timer: relative timeout is 2
> Mar 13 15:15:39 : DBG:tm:insert_timer_unsafe: [3]: 0x7f1c861d06e0 (30)
> Mar 13 15:15:39 : DBG:tm:delete_handler: done
>
> How can I debug the issue? What are the possible causes of this?
> thanks
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users



From bogdan at opensips.org  Wed Mar 20 13:51:25 2024
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Wed, 20 Mar 2024 15:51:25 +0200
Subject: [OpenSIPS-Users] bad uri,
 state 0 parsed: <$avp> (4) / <$avp(r)> (7)
In-Reply-To: <ea2ddb3e-d10c-4e26-a150-85d64ccee07c@bohboh.info>
References: <ea2ddb3e-d10c-4e26-a150-85d64ccee07c@bohboh.info>
Message-ID: <a2348c08-ae35-42b2-90ee-05a326dd1393@opensips.org>

Hi

drop the quotes in :
     $avp(vals) = "$avp(r)";

as you want to put in $avp(vals) the VALUE of the $avp(r) and not the 
STRING "$avp(r)", I guess

Regards,

Bogdan-Andrei Iancu

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

On 14.03.2024 19:56, Social Boh wrote:
> Hello,
>
> any hint with this error:
>
> ERROR:core:parse_uri: bad uri, state 0 parsed: <$avp> (4) / <$avp(r)> (7)
>
> The lines are:
>
> $avp(params) = "ruri";
> $avp(vals) = "$avp(r)";:
>
> on onreply route
>
> $avp(r) contain the request uri created on the failure route.
>
> Regards
>



From bogdan at opensips.org  Wed Mar 20 13:52:43 2024
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Wed, 20 Mar 2024 15:52:43 +0200
Subject: [OpenSIPS-Users] push notifications - and now packages failing
In-Reply-To: <97c15b957d318b515d97e1c3778bf4f6c32c05b5@rvgeerligs.nl>
References: <97c15b957d318b515d97e1c3778bf4f6c32c05b5@rvgeerligs.nl>
Message-ID: <a6fa593a-1b34-41cf-9aed-f570e30a33ad@opensips.org>

Hi,

Just use rtpproxy or rtpengine instead, if not able to install the 
mediapoxy package.

Regards,

Bogdan-Andrei Iancu

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

On 15.03.2024 12:32, rvg at rvgeerligs.nl wrote:
> Hi all,
>
> Maybe I thought wrong and I tried another system with AMD-INTEL 
> architecture.
>
> Desperate I started to install packages.
>
>
> The following packages have unmet dependencies:
>
> mediaproxy-common : Depends: python3 (< 3.9) but 3.10.6-1~22.04 is to 
> be installed
>
> E: Unable to correct problems, you have held broken packages.
>
>
>
> Any advice is appreciated
>
> Regards,
>
> Ronald
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240320/d9c1dd33/attachment.html>

From bogdan at opensips.org  Wed Mar 20 13:53:58 2024
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Wed, 20 Mar 2024 15:53:58 +0200
Subject: [OpenSIPS-Users] Management Interface
In-Reply-To: <CAJh_-cCaK4rkXd+R2j-aCGcXacy5LPN2Pa6px=-UxnhTKM6y-Q@mail.gmail.com>
References: <CAJh_-cCaK4rkXd+R2j-aCGcXacy5LPN2Pa6px=-UxnhTKM6y-Q@mail.gmail.com>
Message-ID: <9370ffb5-0101-450e-b424-1bb1b64a8236@opensips.org>

OpenSIPS Control Panel
https://controlpanel.opensips.org

Regards

Bogdan-Andrei Iancu

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

On 19.03.2024 09:30, Prathibha B wrote:
> What is the alternative to Asterisk Management Interface in OpenSIPS?
>
> -- 
> Regards,
> B.Prathibha
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240320/c30202dc/attachment.html>

From bogdan at opensips.org  Wed Mar 20 13:56:05 2024
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Wed, 20 Mar 2024 15:56:05 +0200
Subject: [OpenSIPS-Users] Freeswitch integration
In-Reply-To: <BN8PR04MB5779A7B6308F1D401726ED2EF3282@BN8PR04MB5779.namprd04.prod.outlook.com>
References: <BN8PR04MB5779A7B6308F1D401726ED2EF3282@BN8PR04MB5779.namprd04.prod.outlook.com>
Message-ID: <933e2cb1-935b-4e70-afc6-49408c869973@opensips.org>

Hi,

Who's generating the 407 reply? OpenSIPS or FS ?

Regards,

Bogdan-Andrei Iancu

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

On 15.03.2024 13:03, Dragan, Calin via Users wrote:
>
> Hi,
>
> I’m trying to use Freeswitch as a media server with Opensips as a load 
> balancer, I need something very basic for a POC. (I configured the 
> load balancer and dispatcher based on old information found here: 
> https://developer.signalwire.com/freeswitch/FreeSWITCH-Explained/Enterprise-Deployment/Enterprise-deployment-OpenSIPS_13173169/#freeswitch-configuration, 
> here: 
> https://developer.signalwire.com/freeswitch/FreeSWITCH-Explained/Auxiliary-Knowledge-and-Utilities/OpenSIPS-configuration-for-2-or-more-FreeSWITCH-installs_13173462/ 
> and here: 
> https://www.opensips.org/Documentation/Tutorials-OpenSIPSFreeSwitchIntegration)
>
> I’m adding the X-Auth-IP header to the requests like this (this is 
> based on the config that ships with the 3.4.x release in the docker 
> image, so I guessed that this is where I should add the header):
>
> route[relay] {
>
>                # for INVITEs enable some additional helper routes
>
>                if (is_method("INVITE")) {
>
>  remove_hf("X-Auth-IP");
>
> append_hf("X-Auth-IP: $si\r\n");
>
> append_to_reply("X-Auth-IP: $si\r\n");
>
> xlog("L_INFO", "$ci|log|X-Auth-IP: $si\n");
>
> xlog("L_INFO", "SIP Message: $mb");
>
> t_on_failure("missed_call");
>
> t_on_branch("per_branch_ops");
>
> t_on_reply("handle_nat");
>
>                }
>
>                if (!t_relay()) {
>
> send_reply(500,"Internal Error");
>
>                }
>
>                exit;
>
> }
>
> On the freeswitch side I added the IP set by opensips in the list of 
> allowed addresses.
>
> Now, with or without authentication enabled on the Freeswitch side 
> (i.e. regardless of what I set in the “auth-calls” param, or if I 
> enable the accept-blind-auth), or even whether the Freeswitch is 
> running or not, when I try to place a call from/to some registerd 
> addresses, I get the “407 Proxy authentication required” response.
>
> Could you please give me some hints on what I might be doing wrong, or 
> direct me to a contemporary tutorial?
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240320/e292fa28/attachment-0001.html>

From bogdan at opensips.org  Wed Mar 20 14:01:59 2024
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Wed, 20 Mar 2024 16:01:59 +0200
Subject: [OpenSIPS-Users] TLS - Private Key fails
In-Reply-To: <CAF9oA8=paVY5gszDNiBomwUvFY1kJsBUa+i6zaB=je37o_9S=A@mail.gmail.com>
References: <CAF9oA8=paVY5gszDNiBomwUvFY1kJsBUa+i6zaB=je37o_9S=A@mail.gmail.com>
Message-ID: <e5403e2b-8cb8-4829-9926-2eb14dad06bc@opensips.org>

Hi,

I see the root problem is OpenSIPS failing to load the private key file 
- I see some log about password case. So, when you generated the key, 
have you set a password for it?

Regards

Bogdan-Andrei Iancu

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

On 15.03.2024 19:35, Rodrigo R Passos wrote:
>
> Hi everyone,
>
>
> I'm trying to start opensips with a certificate generated by 
> opensips-cli, like a tutorial. I have the following results keys after 
> completing the command.
>
> INFO: user certificate created in /etc/opensips/tls/user/wss-cert.pem
>
> INFO: user private key created in /etc/opensips/tls/user/wss-privkey.pem
>
> INFO: user CA list (chain of trust) created in 
> /etc/opensips/tls/user/wss-calist.pem
>
>
> This is my configuration, in opensips.cfg:
>
> modparam("tls_mgm", "server_domain", "wss")
> modparam("tls_mgm", "match_ip_address","[wss]10.0.0.114:5443 
> <http://10.0.0.114:5443>")
> modparam("tls_mgm", "ca_dir", "[wss]/etc/opensips/tls/rootCA/certs")
> modparam("tls_mgm", "ca_list", 
> "[wss]/etc/opensips/tls/user/wss-calist.pem")
> modparam("tls_mgm", 
> "certificate","[wss]/etc/opensips/tls/user/wss-cert.pem")
> modparam("tls_mgm", 
> "private_key","[wss]/etc/opensips/tls/user/wss-privkey.pem")
> modparam("tls_mgm", "verify_cert", "[wss]0")
> modparam("tls_mgm", "require_cert", "[wss]0")
> modparam("tls_mgm", "ciphers_list", "[wss]NULL")
> modparam("tls_mgm", "tls_method", "[wss]TLSv1")
>
>
> So, when I start opensips, the log shows information saying the 
> private key doesn't match with the public key. Follow the log:
>
>
> Mar 15 14:27:14 esbc01 opensips[80845]: Mar 15 14:27:14 [80845] 
> ERROR:tls_openssl:load_private_key: unable to load private key file 
> '/etc/opensips/tls/user/wss-privkey.pem'.
>
> Mar 15 14:27:14 esbc01 opensips[80845]: Retry (2 left) (check password 
> case)
>
> Mar 15 14:27:14 esbc01 opensips[80845]: Mar 15 14:27:14 [80845] 
> ERROR:tls_openssl:load_private_key: key 
> '/etc/opensips/tls/user/wss-privkey.pem' does not match the public key 
> of the certificate
>
> Mar 15 14:27:14 esbc01 opensips[80845]: Mar 15 14:27:14 [80845] 
> ERROR:tls_mgm:init_tls_domains: Failed to init TLS domain 'wss'
>
> Mar 15 14:27:14 esbc01 opensips[80845]: Mar 15 14:27:14 [80845] 
> ERROR:core:init_mod: failed to initialize module tls_mgm
>
> Mar 15 14:27:14 esbc01 opensips[80845]: Mar 15 14:27:14 [80845] 
> ERROR:core:main: error while initializing modules
>
> All procedures to create my own certificate follow the tutorial.
>
>
> Anyone know what is happening or have any problems like me?
>
>
> BR
>
>
> RP
>
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240320/e0ec9930/attachment.html>

From bogdan at opensips.org  Wed Mar 20 14:05:54 2024
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Wed, 20 Mar 2024 16:05:54 +0200
Subject: [OpenSIPS-Users] external applications
In-Reply-To: <CAJh_-cBm=yMTTn=E5tTnhqveG867CsCr7G3eOtVij+gtHBXk0w@mail.gmail.com>
References: <CAJh_-cCAZ2_0mvb98Csex13oyGvbN18Nt9tLVynXgFED85Ec7g@mail.gmail.com>
 <5ecfbddd-d737-f2ca-b93d-a93c1886dff6@voipplus.net>
 <CAJh_-cBm=yMTTn=E5tTnhqveG867CsCr7G3eOtVij+gtHBXk0w@mail.gmail.com>
Message-ID: <0831297d-6722-4bbc-ae09-b13fa76b649f@opensips.org>

Use the dialog events:
https://opensips.org/html/docs/modules/3.4.x/dialog.html#event_E_DLG_STATE_CHANGED

And you subscribe from outside OpenSIPS for such events:
https://www.opensips.org/Documentation/Interface-Events-3-4

Regards,

Bogdan-Andrei Iancu

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

On 20.03.2024 12:16, Prathibha B wrote:
> No. I want to pass START, CONNECT, END messages from OpenSIPS to 
> external application.
>
> On Wed, 20 Mar 2024 at 15:42, Marcin Groszek <marcin at voipplus.net> wrote:
>
>     Well, to execute external command from opensips you may want to
>     use EXEC module.
>
>     this is a manual for v3.2:
>
>     https://opensips.org/html/docs/modules/3.2.x/exec.html
>
>
>     On 3/20/2024 5:00 AM, Prathibha B wrote:
>>     How to integrate OpenSIPS with external applications?
>>
>>     -- 
>>     Regards,
>>     B.Prathibha
>>
>>     _______________________________________________
>>     Users mailing list
>>     Users at lists.opensips.org
>>     http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>     -- 
>     Best Regards:
>     Marcin Groszek
>     Business Phone Service
>     https://www.voipplus.net
>
>     _______________________________________________
>     Users mailing list
>     Users at lists.opensips.org
>     http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
> -- 
> Regards,
> B.Prathibha
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240320/27f73bfb/attachment-0001.html>

From liviu at opensips.org  Wed Mar 20 14:11:04 2024
From: liviu at opensips.org (Liviu Chircu)
Date: Wed, 20 Mar 2024 16:11:04 +0200
Subject: [OpenSIPS-Users] pn still problems
In-Reply-To: <a8d2f3e21c206d8e1506055671139205a3f189b0@rvgeerligs.nl>
References: <a8d2f3e21c206d8e1506055671139205a3f189b0@rvgeerligs.nl>
Message-ID: <8968ce09-e23b-4ce8-9f7e-a9dac54802d8@opensips.org>

Hello rvg,

Please find some answers below.

On 09.03.2024 15:46, rvg at rvgeerligs.nl wrote:
>
> I still have problems with opensips3.4 push notifications:
>
> Somehow INVITEs keep looping and get rejected.
If the INVITE loops to your server, then you likely have an undesired 
t_relay() operation after a lookup() which only finds "Push 
Notification" contacts, which are not immediately routable.  Here, it 
would be helpful to provide the output of: "opensips-cli -x mi ul_dump", 
corresponding to the AoR you are trying to reach, right before placing 
the call.

Additionally, please post the full opensips.log, so we can see if the 
script logic post-lookup falls under "case 1" or "case 2".  Of course, 
in case of the latter, you should just "exit" the script without any 
further routing, as the INVITE will be put on hold, until a REGISTER 
arrives.

>
> question: Does the route[pm_send] need to return any value? exit does 
> not not return value does it?
Indeed, the return value of that route will be ignored.  FYI, "exit;" 
implicitly returns 1 (success).

>
> does the [pm_send] acually need to send the push for the INVITE to be 
> answered by 200 OK?

Yes, that is the main role of that route ("pn_send", as in: "Push 
Notification Send").

Best regards,

Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com
OpenSIPS Summit 2024 Valencia, May 14-17 | www.opensips.org/events



From Ben.Newlin at genesys.com  Wed Mar 20 14:15:53 2024
From: Ben.Newlin at genesys.com (Ben Newlin)
Date: Wed, 20 Mar 2024 14:15:53 +0000
Subject: [OpenSIPS-Users] external applications
In-Reply-To: <0831297d-6722-4bbc-ae09-b13fa76b649f@opensips.org>
References: <CAJh_-cCAZ2_0mvb98Csex13oyGvbN18Nt9tLVynXgFED85Ec7g@mail.gmail.com>
 <5ecfbddd-d737-f2ca-b93d-a93c1886dff6@voipplus.net>
 <CAJh_-cBm=yMTTn=E5tTnhqveG867CsCr7G3eOtVij+gtHBXk0w@mail.gmail.com>
 <0831297d-6722-4bbc-ae09-b13fa76b649f@opensips.org>
Message-ID: <BN0PR10MB5208016E46D172FF14E384AF95332@BN0PR10MB5208.namprd10.prod.outlook.com>

You can also use the REST client. And there are many other ways, as well.

There is no single correct answer to the vague question of connecting to any generic “external application”. You must understand your systems and decide the best approach depending on the needs and capabilities of both the external application and OpenSIPS.

Ben Newlin

From: Users <users-bounces at lists.opensips.org> on behalf of Bogdan-Andrei Iancu <bogdan at opensips.org>
Date: Wednesday, March 20, 2024 at 10:06 AM
To: OpenSIPS users mailling list <users at lists.opensips.org>, Prathibha B <prathibhab.tvm at gmail.com>
Subject: Re: [OpenSIPS-Users] external applications
 EXTERNAL EMAIL - Please use caution with links and attachments

________________________________
Use the dialog events:
    https://opensips.org/html/docs/modules/3.4.x/dialog.html#event_E_DLG_STATE_CHANGED<https://opensips.org/html/docs/modules/3.4.x/dialog.html#event_E_DLG_STATE_CHANGED>

And you subscribe from outside OpenSIPS for such events:
    https://www.opensips.org/Documentation/Interface-Events-3-4<https://www.opensips.org/Documentation/Interface-Events-3-4>

Regards,


Bogdan-Andrei Iancu



OpenSIPS Founder and Developer

  https://www.opensips-solutions.com<https://www.opensips-solutions.com>

  https://www.siphub.com<https://www.siphub.com>
On 20.03.2024 12:16, Prathibha B wrote:
No. I want to pass START, CONNECT, END messages from OpenSIPS to external application.

On Wed, 20 Mar 2024 at 15:42, Marcin Groszek <marcin at voipplus.net<mailto:marcin at voipplus.net>> wrote:

Well, to execute external command from opensips you may want to use EXEC module.

this is a manual for v3.2:

https://opensips.org/html/docs/modules/3.2.x/exec.html<https://opensips.org/html/docs/modules/3.2.x/exec.html>


On 3/20/2024 5:00 AM, Prathibha B wrote:
How to integrate OpenSIPS with external applications?

--
Regards,
B.Prathibha



_______________________________________________

Users mailing list

Users at lists.opensips.org<mailto:Users at lists.opensips.org>

http://lists.opensips.org/cgi-bin/mailman/listinfo/users<http://lists.opensips.org/cgi-bin/mailman/listinfo/users>

--

Best Regards:

Marcin Groszek

Business Phone Service

https://www.voipplus.net<https://www.voipplus.net>
_______________________________________________
Users mailing list
Users at lists.opensips.org<mailto:Users at lists.opensips.org>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users<http://lists.opensips.org/cgi-bin/mailman/listinfo/users>


--
Regards,
B.Prathibha



_______________________________________________

Users mailing list

Users at lists.opensips.org<mailto:Users at lists.opensips.org>

http://lists.opensips.org/cgi-bin/mailman/listinfo/users<http://lists.opensips.org/cgi-bin/mailman/listinfo/users>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240320/cc4259b5/attachment.html>

From bogdan at opensips.org  Wed Mar 20 14:21:06 2024
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Wed, 20 Mar 2024 16:21:06 +0200
Subject: [OpenSIPS-Users] call center
In-Reply-To: <CAJh_-cB_Uw5Enk+4P-so2y-_CjL+V8FAzyMSe-=aOGbabJr5eQ@mail.gmail.com>
References: <CAJh_-cB_Uw5Enk+4P-so2y-_CjL+V8FAzyMSe-=aOGbabJr5eQ@mail.gmail.com>
Message-ID: <7000ea6d-d188-4664-b915-da3962fafb59@opensips.org>

Could you be more specific on your question, like what OpenSIPS should 
do for the call center application??

Regards,

Bogdan-Andrei Iancu

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

On 19.03.2024 07:03, Prathibha B wrote:
> How to integrate Opensips with call center application?
>
> -- 
> Regards,
> B.Prathibha
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240320/3c0eb0e8/attachment-0001.html>

From bogdan at opensips.org  Wed Mar 20 14:25:01 2024
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Wed, 20 Mar 2024 16:25:01 +0200
Subject: [OpenSIPS-Users] Need some help on opensips error for wss
 handshek .
In-Reply-To: <CALf-Q44WNwsU8owQ5ZNErnwXkxGuzzKOhKT7fWtcVTNxiy+YLw@mail.gmail.com>
References: <CALf-Q44nYwthB2z=ignY9uXwrEWhb6tgrXom24v2HwXFDd7UoA@mail.gmail.com>
 <e98e705b-0968-4828-84d7-b101367d2a14@opensips.org>
 <CALf-Q44WNwsU8owQ5ZNErnwXkxGuzzKOhKT7fWtcVTNxiy+YLw@mail.gmail.com>
Message-ID: <579b76bd-609a-4f44-9b78-a3d7f6823c67@opensips.org>

Hi,

There is a fix (to tolerate different version numbers there) but only in 
OpenSIPS 3.5 [1] (the devel version), not yet backported to stable 3.4 
and 3.2. You can try to do the backport by yourself.

BTW, what WS client & browser are you using ?? It is pretty unusual what 
you report here.

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

Bogdan-Andrei Iancu

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

On 20.03.2024 15:30, Sasmita Panda wrote:
> Hi Bogdan,
> I appreciate your reply .
>
> How can I suggest modifying this header ? Because I have seen this for 
> some remote agents who run in the browser . I don't have access to the 
> browser .
> The browser which got connected successfully I couldn't see such types 
> of logs  .
>
> What causes this header version in the wss connection ?
>
>
> */Thanks & Regards/*
> /Sasmita Panda/
> /Senior Network Testing and Software Engineer/
> /3CLogic , ph:07827611765/
>
>
> On Wed, Mar 20, 2024 at 6:51 PM Bogdan-Andrei Iancu 
> <bogdan at opensips.org> wrote:
>
>     Hi,
>
>     OpenSIPS does not like that 1.1 version in the VIA hdr - it
>     expects 2.0 (the SIP version).
>
>     Regards,
>
>     Bogdan-Andrei Iancu
>
>     OpenSIPS Founder and Developer
>        https://www.opensips-solutions.com
>        https://www.siphub.com
>
>     On 12.03.2024 10:57, Sasmita Panda wrote:
>>     Hi All ,
>>
>>     1"  :callID 080a9ef8-3911-6c41-689c-fbb5d02e3aae
>>     Mar 12 08:23:11 localhost /usr/sbin/opensips[12987]:
>>     ERROR:core:parse_via: bad char <1> on state 100
>>     Mar 12 08:23:11 localhost /usr/sbin/opensips[12987]:
>>     ERROR:core:parse_via:  <1.1 p1wsa01.rivagecapital.com:80
>>     <http://p1wsa01.rivagecapital.com:80>
>>     (Cisco-WSA/12.5.4-011)#015#012#015#012>
>>     Mar 12 08:23:11 localhost /usr/sbin/opensips[12987]:
>>     ERROR:core:parse_via: via parse failed
>>     Mar 12 08:23:11 localhost /usr/sbin/opensips[12987]:
>>     ERROR:core:get_hdr_field: bad via
>>     Mar 12 08:23:11 localhost /usr/sbin/opensips[12987]:
>>     INFO:core:parse_headers: bad header field
>>     Mar 12 08:23:11 localhost /usr/sbin/opensips[12987]:
>>     ERROR:proto_wss:ws_parse_req_handshake: cannot parse
>>     headers#012Upgrade: websocket#015#012Connection:
>>     Upgrade#015#012Host: ir-webrtc2.3ccloud.com#015#012Pragma
>>     <http://ir-webrtc2.3ccloud.com#015%23012Pragma>:
>>     no-cache#015#012Cache-Control: no-cache#015#012User-Agent:
>>     Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
>>     (KHTML, like Gecko) Chrome/122.0.0.0 <http://122.0.0.0>
>>     Safari/537.36 Edg/122.0.0.0#015#012Origin
>>     <http://122.0.0.0#015%23012Origin>:
>>     https://ir-static.3ccloud.com#015#012Sec-WebSocket-Version
>>     <https://ir-static.3ccloud.com#015%23012Sec-WebSocket-Version>:
>>     13#015#012Accept-Encoding: gzip, br#015#012Accept-Language:
>>     en-GB,en;q=0.9,en-US;q=0.8#015#012Sec-WebSocket-Key:
>>     I/8XqtXyBCAGorZYjnTYQA==#015#012Sec-WebSocket-Extensions:
>>     permessage-deflate;
>>     client_max_window_bits#015#012Sec-WebSocket-Protocol:
>>     sip#015#012X-IMForwards: 20#015#012Via: 1.1
>>     p1wsa01.rivagecapital.com:80
>>     <http://p1wsa01.rivagecapital.com:80>
>>     (Cisco-WSA/12.5.4-011)#015#012#015#012
>>
>>
>>      I am getting this error on my opensips server where I am running
>>     webrtc . What is this error for ?
>>
>>
>>     */Thanks & Regards/*
>>     /Sasmita Panda/
>>     /Senior Network Testing and Software Engineer/
>>     /3CLogic , ph:07827611765/
>>
>>     _______________________________________________
>>     Users mailing list
>>     Users at lists.opensips.org
>>     http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240320/dbd2ff31/attachment.html>

From prathibhab.tvm at gmail.com  Wed Mar 20 14:26:14 2024
From: prathibhab.tvm at gmail.com (Prathibha B)
Date: Wed, 20 Mar 2024 14:26:14 +0000
Subject: [OpenSIPS-Users] call center
In-Reply-To: <7000ea6d-d188-4664-b915-da3962fafb59@opensips.org>
References: <CAJh_-cB_Uw5Enk+4P-so2y-_CjL+V8FAzyMSe-=aOGbabJr5eQ@mail.gmail.com>
 <7000ea6d-d188-4664-b915-da3962fafb59@opensips.org>
Message-ID: <TYZPR06MB75254F712426CA5E4C675FE0FC332@TYZPR06MB7525.apcprd06.prod.outlook.com>

Need to pass data from opensips to external call center application like call ID, duration of the call and so on.

Sent from Outlook for Android<https://aka.ms/AAb9ysg>
________________________________
From: Bogdan-Andrei Iancu <bogdan at opensips.org>
Sent: Wednesday, March 20, 2024 7:51:06 PM
To: OpenSIPS users mailling list <users at lists.opensips.org>; Prathibha B <prathibhab.tvm at gmail.com>
Subject: Re: [OpenSIPS-Users] call center

Could you be more specific on your question, like what OpenSIPS should do for the call center application??

Regards,

Bogdan-Andrei Iancu

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

On 19.03.2024 07:03, Prathibha B wrote:
How to integrate Opensips with call center application?

--
Regards,
B.Prathibha



_______________________________________________
Users mailing list
Users at lists.opensips.org<mailto:Users at lists.opensips.org>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240320/67f55b14/attachment.html>

From prathibhab.tvm at gmail.com  Wed Mar 20 14:29:19 2024
From: prathibhab.tvm at gmail.com (Prathibha B)
Date: Wed, 20 Mar 2024 14:29:19 +0000
Subject: [OpenSIPS-Users] call center
In-Reply-To: <TYZPR06MB75254F712426CA5E4C675FE0FC332@TYZPR06MB7525.apcprd06.prod.outlook.com>
References: <CAJh_-cB_Uw5Enk+4P-so2y-_CjL+V8FAzyMSe-=aOGbabJr5eQ@mail.gmail.com>
 <7000ea6d-d188-4664-b915-da3962fafb59@opensips.org>
 <TYZPR06MB75254F712426CA5E4C675FE0FC332@TYZPR06MB7525.apcprd06.prod.outlook.com>
Message-ID: <TYZPR06MB7525014EDE45CA19B15A1C7FFC332@TYZPR06MB7525.apcprd06.prod.outlook.com>

 I want to pass the call START, CONNECT, END messages to the external application

Sent from Outlook for Android<https://aka.ms/AAb9ysg>
________________________________
From: Prathibha B <prathibhab.tvm at gmail.com>
Sent: Wednesday, March 20, 2024 7:56:14 PM
To: Bogdan-Andrei Iancu <bogdan at opensips.org>; OpenSIPS users mailling list <users at lists.opensips.org>
Subject: Re: [OpenSIPS-Users] call center

Need to pass data from opensips to external call center application like call ID, duration of the call and so on.

Sent from Outlook for Android<https://aka.ms/AAb9ysg>
________________________________
From: Bogdan-Andrei Iancu <bogdan at opensips.org>
Sent: Wednesday, March 20, 2024 7:51:06 PM
To: OpenSIPS users mailling list <users at lists.opensips.org>; Prathibha B <prathibhab.tvm at gmail.com>
Subject: Re: [OpenSIPS-Users] call center

Could you be more specific on your question, like what OpenSIPS should do for the call center application??

Regards,

Bogdan-Andrei Iancu

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

On 19.03.2024 07:03, Prathibha B wrote:
How to integrate Opensips with call center application?

--
Regards,
B.Prathibha



_______________________________________________
Users mailing list
Users at lists.opensips.org<mailto:Users at lists.opensips.org>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240320/003d39c6/attachment-0001.html>

From bogdan at opensips.org  Wed Mar 20 15:04:36 2024
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Wed, 20 Mar 2024 17:04:36 +0200
Subject: [OpenSIPS-Users] call center
In-Reply-To: <TYZPR06MB7525014EDE45CA19B15A1C7FFC332@TYZPR06MB7525.apcprd06.prod.outlook.com>
References: <CAJh_-cB_Uw5Enk+4P-so2y-_CjL+V8FAzyMSe-=aOGbabJr5eQ@mail.gmail.com>
 <7000ea6d-d188-4664-b915-da3962fafb59@opensips.org>
 <TYZPR06MB75254F712426CA5E4C675FE0FC332@TYZPR06MB7525.apcprd06.prod.outlook.com>
 <TYZPR06MB7525014EDE45CA19B15A1C7FFC332@TYZPR06MB7525.apcprd06.prod.outlook.com>
Message-ID: <90440aa9-b9ef-4b1a-8642-85ed426de6f3@opensips.org>

Right, see the other thread, with the external app. And for the future 
try to have only one email thread per topic, do not flood with multiple 
emails on the same topic.....

Bogdan-Andrei Iancu

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

On 20.03.2024 16:29, Prathibha B wrote:
>  I want to pass the call START, CONNECT, END messages to the external 
> application
>
> Sent from Outlook for Android <https://aka.ms/AAb9ysg>
> ------------------------------------------------------------------------
> *From:* Prathibha B <prathibhab.tvm at gmail.com>
> *Sent:* Wednesday, March 20, 2024 7:56:14 PM
> *To:* Bogdan-Andrei Iancu <bogdan at opensips.org>; OpenSIPS users 
> mailling list <users at lists.opensips.org>
> *Subject:* Re: [OpenSIPS-Users] call center
> Need to pass data from opensips to external call center application 
> like call ID, duration of the call and so on.
>
> Sent from Outlook for Android <https://aka.ms/AAb9ysg>
> ------------------------------------------------------------------------
> *From:* Bogdan-Andrei Iancu <bogdan at opensips.org>
> *Sent:* Wednesday, March 20, 2024 7:51:06 PM
> *To:* OpenSIPS users mailling list <users at lists.opensips.org>; 
> Prathibha B <prathibhab.tvm at gmail.com>
> *Subject:* Re: [OpenSIPS-Users] call center
> Could you be more specific on your question, like what OpenSIPS should 
> do for the call center application??
>
> Regards,
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>    https://www.opensips-solutions.com  <https://www.opensips-solutions.com>
>    https://www.siphub.com  <https://www.siphub.com>
> On 19.03.2024 07:03, Prathibha B wrote:
>> How to integrate Opensips with call center application?
>>
>> -- 
>> Regards,
>> B.Prathibha
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org  <mailto:Users at lists.opensips.org>
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users  <http://lists.opensips.org/cgi-bin/mailman/listinfo/users>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240320/369cc303/attachment.html>

From alain.bieuzent at free.fr  Wed Mar 20 15:14:04 2024
From: alain.bieuzent at free.fr (Alain Bieuzent)
Date: Wed, 20 Mar 2024 16:14:04 +0100
Subject: [OpenSIPS-Users] OPENSIP 3.4 send_reply and tight matching
	failed
In-Reply-To: <027f24dd-f225-468b-9d05-ce31e3a3ee1c@opensips.org>
References: <84BD48FD-8F95-4798-8201-7F87E54DAE4C@free.fr>
 <858EE736-AF3A-46A4-8EBC-8ABF8BC30A8E@free.fr>
 <027f24dd-f225-468b-9d05-ce31e3a3ee1c@opensips.org>
Message-ID: <14EC8DDF-6F01-4C71-91D5-F0A567CD23C9@free.fr>

Bellow the link to the traces : 

 

https://www.transfernow.net/dl/20240320jzEA98Vz

 

De : Bogdan-Andrei Iancu <bogdan at opensips.org>
Date : mercredi 20 mars 2024 à 14:29
À : OpenSIPS users mailling list <users at lists.opensips.org>, Alain Bieuzent <alain.bieuzent at free.fr>
Objet : Re: [OpenSIPS-Users] OPENSIP 3.4 send_reply and tight matching failed

 

Hi,

The script snippet has nothing to do with the matching - it is about a 200-ok ACK to be matched by the dialog module and the TO-tag does not match at all. 

The link to the trace expired, if you could repost.

Regards,

Bogdan-Andrei Iancu
 
OpenSIPS Founder and Developer
  https://www.opensips-solutions.com
  https://www.siphub.com
On 12.03.2024 14:57, Alain Bieuzent wrote:

Hi all,

 

I am in the process of migrating my proxies from 3.3.9 to 3.4.4.

In 3.4 I find myself with a fault when I try to rewrite a final cause.

 

if (t_check_status("500"))

         {

                          send_reply(503,"Service Unavailable");

                         exit;

          }

 

with 3.3 version, this code works perfectly, since 3.4 I have this error:

 

WARNING:dialog:dlg_onroute: tight matching failed for ACK with callid='67457c401e9ea52e2750100979253a7a at 10.101.180.177:5060'/52, ftag='as5328cea7'/10, ttag='b5a7-2a346bb9d510da893a ee7cda850584cb'/37 and direction=1

WARNING:dialog:dlg_onroute: dialog identification elements are callid='67457c401e9ea52e2750100979253a7a at 10.101.180.177:5060'/52, caller tag='as5328cea7'/10, callee tag='3919223738-770090972'/ 20

 

Has anyone encountered this error before?

 

Complete traces here : https://www.transfernow.net/dl/20240312qvAFfIAL.

 

Regards



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



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240320/37803413/attachment.html>

From bogdan at opensips.org  Wed Mar 20 15:45:36 2024
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Wed, 20 Mar 2024 17:45:36 +0200
Subject: [OpenSIPS-Users] OPENSIP 3.4 send_reply and tight matching
	failed
In-Reply-To: <14EC8DDF-6F01-4C71-91D5-F0A567CD23C9@free.fr>
References: <84BD48FD-8F95-4798-8201-7F87E54DAE4C@free.fr>
 <858EE736-AF3A-46A4-8EBC-8ABF8BC30A8E@free.fr>
 <027f24dd-f225-468b-9d05-ce31e3a3ee1c@opensips.org>
 <14EC8DDF-6F01-4C71-91D5-F0A567CD23C9@free.fr>
Message-ID: <e7cf336c-d2a5-4f2b-86ac-399eca7feb29@opensips.org>

Not the logs, but the trace/ SIP capture - I need to see the sip traffic 
to understand the context of the issue.

Bogdan-Andrei Iancu

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

On 20.03.2024 17:14, Alain Bieuzent wrote:
>
> Bellow the link to the traces :
>
> https://www.transfernow.net/dl/20240320jzEA98Vz
>
> *De : *Bogdan-Andrei Iancu <bogdan at opensips.org>
> *Date : *mercredi 20 mars 2024 à 14:29
> *À : *OpenSIPS users mailling list <users at lists.opensips.org>, Alain 
> Bieuzent <alain.bieuzent at free.fr>
> *Objet : *Re: [OpenSIPS-Users] OPENSIP 3.4 send_reply and tight 
> matching failed
>
> Hi,
>
> The script snippet has nothing to do with the matching - it is about a 
> 200-ok ACK to be matched by the dialog module and the TO-tag does not 
> match at all.
>
> The link to the trace expired, if you could repost.
>
> Regards,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developer
>    https://www.opensips-solutions.com
>    https://www.siphub.com
>
> On 12.03.2024 14:57, Alain Bieuzent wrote:
>
>     Hi all,
>
>     I am in the process of migrating my proxies from 3.3.9 to 3.4.4.
>
>     In 3.4 I find myself with a fault when I try to rewrite a final cause.
>
>     if (t_check_status("500"))
>
>              {
>
>     send_reply(503,"Service Unavailable");
>
>     exit;
>
>     }
>
>     with 3.3 version, this code works perfectly, since 3.4 I have this
>     error:
>
>     WARNING:dialog:dlg_onroute: tight matching failed for ACK with
>     callid='67457c401e9ea52e2750100979253a7a at 10.101.180.177:5060'/52,
>     ftag='as5328cea7'/10, ttag='b5a7-2a346bb9d510da893a
>     ee7cda850584cb'/37 and direction=1
>
>     WARNING:dialog:dlg_onroute: dialog identification elements are
>     callid='67457c401e9ea52e2750100979253a7a at 10.101.180.177:5060'/52,
>     caller tag='as5328cea7'/10, callee tag='3919223738-770090972'/ 20
>
>     Has anyone encountered this error before?
>
>     Complete traces here :
>     https://www.transfernow.net/dl/20240312qvAFfIAL.
>
>     Regards
>
>
>
>     _______________________________________________
>
>     Users mailing list
>
>     Users at lists.opensips.org
>
>     http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240320/3bba6be6/attachment-0001.html>

From social at bohboh.info  Wed Mar 20 21:03:32 2024
From: social at bohboh.info (Social Boh)
Date: Wed, 20 Mar 2024 16:03:32 -0500
Subject: [OpenSIPS-Users] OpenSIPs generate PRACK [SOLVED]
In-Reply-To: <CAJTkRNsv7cmJiFWzDWiDNuMHGw8qp5ENw6pJKBLLsYBJgzX-Tg@mail.gmail.com>
References: <476be849-afbe-4d69-9218-f80bd27022ad@bohboh.info>
 <e880a151-5bca-443e-8216-16b80b4ff067@bohboh.info>
 <CAJTkRNtNYHe2Sid19y0sw8d457j3iCwoJHOjOpjYD4tZU-ekbA@mail.gmail.com>
 <49eb93af-dd10-4fae-82bd-1d19edca403a@opensips.org>
 <fd54ef29-8dfe-4a01-9ac2-ecfef090d47c@bohboh.info>
 <be15bfd5-364b-4c32-8343-05ead701e7e4@opensips.org>
 <fcfaa1c8-4196-4807-a70e-cc4cf89dd9b3@bohboh.info>
 <34e1d5c1-deb3-458f-ad0a-401a1d077852@bohboh.info>
 <CAJTkRNsv7cmJiFWzDWiDNuMHGw8qp5ENw6pJKBLLsYBJgzX-Tg@mail.gmail.com>
Message-ID: <b6995e50-a063-4ed4-a684-16e21c6bf09f@bohboh.info>

Right, solved

Thank you

---
I'm SoCIaL, MayBe

El 20/03/2024 a las 4:07 a. m., Ihor Olkhovskyi escribió:
> You are not increasing CSeq for subsequent PRACK.
>
> Le mar. 19 mars 2024 à 18:58, Social Boh <social at bohboh.info> a écrit :
>
>     Some progress
>
>     Now I can reply the first 183 with the PRACK response but when the
>     provider send a 180 ringing and I reply with another PPRACK
>     response the provider reply with 500 Server Internal Error
>
>     Annex PCAP Capture.
>
>     Any hint is really appreciate.
>
>     Regards
>
>     ---
>     I'm SoCIaL, MayBe
>
>     El 15/03/2024 a las 5:35 p. m., Social Boh escribió:
>>
>>     I'm trying using directly opensips-cli via exec module to see if
>>     all OK and then pass the data tu mi_script module
>>
>>     I think I have a sintaxis problem with the line:
>>
>>     exec("opensips-cli -x mi t_uac_dlg method=INVITE
>>     ruri="sip:alice at 127.0.0.1:7050" headers="From:
>>     sip:bobster at 127.0.0.1:1337\r\nTo:
>>     sip:alice at 127.0.0.1:7050\r\nContact:
>>     sip:bobster at 127.0.0.1:1337\r\n"")
>>
>>     I don't know how use " in the line because Headers and ruri need
>>     them. The result is a error:
>>
>>     ERROR:core:handle_mi_request: Invalid parameters
>>
>>     Any hint, please?
>>
>>     Regards
>>
>>     ---
>>     I'm SoCIaL, MayBe
>>     El 26/02/2024 a las 7:43 a. m., Bogdan-Andrei Iancu escribió:
>>>     yes, you can use the b2b_logic (together with b2b_entities) for
>>>     that, but it may be a too heavy tool for the purpose. Maybe you
>>>     can try to generate the PRACK from OpenSIPS level by using the
>>>     t_uac_dlg MI function [1] via the mi_script module [2] -
>>>     basically to trigger that MI cmd from the onreply_route, when
>>>     receiving the 180 reply.
>>>
>>>     [1]
>>>     https://opensips.org/html/docs/modules/3.4.x/tm.html#mi_t_uac_dlg
>>>     [2]
>>>     https://opensips.org/html/docs/modules/3.4.x/mi_script.html#afunc_mi
>>>
>>>     Regards,
>>>     Bogdan-Andrei Iancu
>>>
>>>     OpenSIPS Founder and Developer
>>>        https://www.opensips-solutions.com
>>>        https://www.siphub.com
>>>     On 25.02.2024 14:54, Social Boh wrote:
>>>>
>>>>     I know the best way is the original caller handle and reply the
>>>>     183, but I HAVE to do this at OpenSIPs level.
>>>>
>>>>     Can I use B2B_Entities and B2B_logic to do this? Is there a
>>>>     scenario to use tu parse and reply the 183?
>>>>
>>>>     Thank you
>>>>
>>>>     ---
>>>>     I'm SoCIaL, MayBe
>>>>     El 16/02/2024 a las 11:31 a. m., Bogdan-Andrei Iancu escribió:
>>>>>     I agree here, the 183 must be relayed back to the original
>>>>>     caller (which generate the received INVITE) and let it do the
>>>>>     PRACK - this confirmation must be end-2-end in the dialog.
>>>>>
>>>>>     Regards,
>>>>>     Bogdan-Andrei Iancu
>>>>>
>>>>>     OpenSIPS Founder and Developer
>>>>>        https://www.opensips-solutions.com
>>>>>        https://www.siphub.com
>>>>>     On 12.02.2024 11:36, Ihor Olkhovskyi wrote:
>>>>>>     You should relay 183 to original source (ione that is sending
>>>>>>     INVITE) and got PRACK from there.
>>>>>>     That would be the most correct way of handling this
>>>>>>
>>>>>>     Le lun. 12 févr. 2024 à 02:29, Social Boh
>>>>>>     <social at bohboh.info> a écrit :
>>>>>>
>>>>>>         Maybe someone can help me.
>>>>>>
>>>>>>         This is the scenario.
>>>>>>
>>>>>>         OpenSIPs receive a INVITE and send it to a server that
>>>>>>         reply with a 302
>>>>>>         message (always)
>>>>>>
>>>>>>         Then OpenSIPs, in the failure route, take the user part
>>>>>>         present in the
>>>>>>         302 contact header, change the destination IP and send
>>>>>>         with t_relay
>>>>>>
>>>>>>         The destination reply with a 183 with Require: 100rel
>>>>>>         header so OpenSIPs
>>>>>>         have to reply with a PRACK. This is my problem.
>>>>>>
>>>>>>         I don't know which is the best way to handle this (the PRACK)
>>>>>>
>>>>>>         Thank you
>>>>>>
>>>>>>         Regards
>>>>>>
>>>>>>         ---
>>>>>>         I'm SoCIaL, MayBe
>>>>>>
>>>>>>         El 9/02/2024 a las 6:46 a. m., Social Boh escribió:
>>>>>>         > Hello list,
>>>>>>         >
>>>>>>         > can OpenSIPs generate a PRACK message to reply a
>>>>>>         180/183 message?
>>>>>>         >
>>>>>>         > Thank you
>>>>>>         >
>>>>>>         > Regards
>>>>>>         >
>>>>>>         > ---
>>>>>>         > I'm SoCIaL, MayBe
>>>>>>         >
>>>>>>         >
>>>>>>         > _______________________________________________
>>>>>>         > Users mailing list
>>>>>>         > Users at lists.opensips.org
>>>>>>         > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>>>>
>>>>>>         _______________________________________________
>>>>>>         Users mailing list
>>>>>>         Users at lists.opensips.org
>>>>>>         http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>>>>
>>>>>>
>>>>>>
>>>>>>     -- 
>>>>>>     Best regards,
>>>>>>     Ihor (Igor)
>>>>>>
>>>>>>     _______________________________________________
>>>>>>     Users mailing list
>>>>>>     Users at lists.opensips.org
>>>>>>     http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>>>
>>>>>
>>>>>     _______________________________________________
>>>>>     Users mailing list
>>>>>     Users at lists.opensips.org
>>>>>     http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>
>>
>>     _______________________________________________
>>     Users mailing list
>>     Users at lists.opensips.org
>>     http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>     _______________________________________________
>     Users mailing list
>     Users at lists.opensips.org
>     http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
> -- 
> Best regards,
> Ihor (Igor)
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240320/fa011520/attachment.html>

From spanda at 3clogic.com  Thu Mar 21 06:37:39 2024
From: spanda at 3clogic.com (Sasmita Panda)
Date: Thu, 21 Mar 2024 12:07:39 +0530
Subject: [OpenSIPS-Users] Need some help on opensips error for wss
 handshek .
In-Reply-To: <579b76bd-609a-4f44-9b78-a3d7f6823c67@opensips.org>
References: <CALf-Q44nYwthB2z=ignY9uXwrEWhb6tgrXom24v2HwXFDd7UoA@mail.gmail.com>
 <e98e705b-0968-4828-84d7-b101367d2a14@opensips.org>
 <CALf-Q44WNwsU8owQ5ZNErnwXkxGuzzKOhKT7fWtcVTNxiy+YLw@mail.gmail.com>
 <579b76bd-609a-4f44-9b78-a3d7f6823c67@opensips.org>
Message-ID: <CALf-Q45hHB93vR+DgZHi29j0JGznOSmfJvRiuuPYuszi4fD90w@mail.gmail.com>

We are using webrtc Client integrated with browsers using sipml5 client
library . I think this is a common library used across the glob .
Every customer that has this same client running with webrtc Server (having
opensips) is common .
But the error I have seen is for one or two agents only .


So the error is for the client or the network ? If it can be the network
then I may suggest the customer to change the network while using webrtc
client .


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


On Wed, Mar 20, 2024 at 7:55 PM Bogdan-Andrei Iancu <bogdan at opensips.org>
wrote:

> Hi,
>
> There is a fix (to tolerate different version numbers there) but only in
> OpenSIPS 3.5 [1] (the devel version), not yet backported to stable 3.4 and
> 3.2. You can try to do the backport by yourself.
>
> BTW, what WS client & browser are you using ?? It is pretty unusual what
> you report here.
>
> [1]
> https://github.com/OpenSIPS/opensips/commit/e30a355397b285a5140ebb25a485bed7134de7ee
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>   https://www.opensips-solutions.com
>   https://www.siphub.com
>
> On 20.03.2024 15:30, Sasmita Panda wrote:
>
> Hi Bogdan,
> I appreciate your reply .
>
> How can I suggest modifying this header ? Because I have seen this for
> some remote agents who run in the browser . I don't have access to the
> browser .
> The browser which got connected successfully I couldn't see such types of
> logs  .
>
> What causes this header version in the wss connection ?
>
>
> *Thanks & Regards*
> *Sasmita Panda*
> *Senior Network Testing and Software Engineer*
> *3CLogic , ph:07827611765*
>
>
> On Wed, Mar 20, 2024 at 6:51 PM Bogdan-Andrei Iancu <bogdan at opensips.org>
> wrote:
>
>> Hi,
>>
>> OpenSIPS does not like that 1.1 version in the VIA hdr - it expects 2.0
>> (the SIP version).
>>
>> Regards,
>>
>> Bogdan-Andrei Iancu
>>
>> OpenSIPS Founder and Developer
>>   https://www.opensips-solutions.com
>>   https://www.siphub.com
>>
>> On 12.03.2024 10:57, Sasmita Panda wrote:
>>
>> Hi All ,
>>
>> 1"  :callID 080a9ef8-3911-6c41-689c-fbb5d02e3aae
>> Mar 12 08:23:11 localhost /usr/sbin/opensips[12987]:
>> ERROR:core:parse_via: bad char <1> on state 100
>> Mar 12 08:23:11 localhost /usr/sbin/opensips[12987]:
>> ERROR:core:parse_via:  <1.1 p1wsa01.rivagecapital.com:80
>> (Cisco-WSA/12.5.4-011)#015#012#015#012>
>> Mar 12 08:23:11 localhost /usr/sbin/opensips[12987]:
>> ERROR:core:parse_via: via parse failed
>> Mar 12 08:23:11 localhost /usr/sbin/opensips[12987]:
>> ERROR:core:get_hdr_field: bad via
>> Mar 12 08:23:11 localhost /usr/sbin/opensips[12987]:
>> INFO:core:parse_headers: bad header field
>> Mar 12 08:23:11 localhost /usr/sbin/opensips[12987]: ERROR:proto_
>> wss:ws_parse_req_handshake: cannot parse headers#012Upgrade:
>> websocket#015#012Connection: Upgrade#015#012Host:
>> ir-webrtc2.3ccloud.com#015#012Pragma
>> <http://ir-webrtc2.3ccloud.com#015%23012Pragma>:
>> no-cache#015#012Cache-Control: no-cache#015#012User-Agent: Mozilla/5.0
>> (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/
>> 122.0.0.0 Safari/537.36 Edg/122.0.0.0#015#012Origin
>> <http://122.0.0.0#015%23012Origin>:
>> https://ir-static.3ccloud.com#015#012Sec-WebSocket-Version:
>> 13#015#012Accept-Encoding: gzip, br#015#012Accept-Language:
>> en-GB,en;q=0.9,en-US;q=0.8#015#012Sec-WebSocket-Key:
>> I/8XqtXyBCAGorZYjnTYQA==#015#012Sec-WebSocket-Extensions:
>> permessage-deflate; client_max_window_bits#015#012Sec-WebSocket-Protocol:
>> sip#015#012X-IMForwards: 20#015#012Via: 1.1 p1wsa01.rivagecapital.com:80
>> (Cisco-WSA/12.5.4-011)#015#012#015#012
>>
>>
>>  I am getting this error on my opensips server where I am running webrtc
>> . What is this error for ?
>>
>>
>> *Thanks & Regards*
>> *Sasmita Panda*
>> *Senior Network Testing and Software Engineer*
>> *3CLogic , ph:07827611765*
>>
>> _______________________________________________
>> Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240321/be78ffd4/attachment-0001.html>

From igorolhovskiy at gmail.com  Thu Mar 21 09:01:05 2024
From: igorolhovskiy at gmail.com (Ihor Olkhovskyi)
Date: Thu, 21 Mar 2024 10:01:05 +0100
Subject: [OpenSIPS-Users] Need some suggestion or help in case of webrtc
 connection with opensips .
In-Reply-To: <CALf-Q44Y8LejzD-R6CugDZ4ueZjdvOF0uJw-eWS=+2JSRdijcw@mail.gmail.com>
References: <CALf-Q45=rLrQVkStCEFaHpnN6ADvbLw+4f42P-qPRv9Q4Hx7sw@mail.gmail.com>
 <CAJTkRNv_wVTuwpxKS-p4jYQryO59=ApCQ5Tsyao8XCohMmX7tg@mail.gmail.com>
 <CALf-Q44Y8LejzD-R6CugDZ4ueZjdvOF0uJw-eWS=+2JSRdijcw@mail.gmail.com>
Message-ID: <CAJTkRNvtfMJEVLDDgVvFLotO-DDS8DYVbAqmsaH6209zOCyNog@mail.gmail.com>

Hi,
Just use drop() function in a case of reaching the limit.

Le mer. 20 mars 2024 à 13:49, Sasmita Panda <spanda at 3clogic.com> a écrit :

> Hi ,
>
> Thank you for your suggestion . I will try that . just to clarify did you
> mean that will drop the wss connection of that user ?
>
>
> *Thanks & Regards*
> *Sasmita Panda*
> *Senior Network Testing and Software Engineer*
> *3CLogic , ph:07827611765*
>
>
> On Wed, Mar 20, 2024 at 6:05 PM Ihor Olkhovskyi <igorolhovskiy at gmail.com>
> wrote:
>
>> Hi!
>>
>> You can try to use something like cachedb module (for autoexpiry) with
>> name of the key like "username_timestamp" and increment it in a case of
>> value exists. And if value is above some threshold - drop further
>> connections.
>>
>> Cheers,
>> Ihor
>>
>> Le mar. 19 mars 2024 à 12:05, Sasmita Panda <spanda at 3clogic.com> a
>> écrit :
>>
>>> Hi All ,
>>>
>>> I have opensips 3.2 version with webrtc configured . I just got an issue
>>> in production that one browser is trying to establish multiple connections
>>> frequently which overloads my server which has the impact that other
>>> browsers are not able to establish a single connection at some points .
>>>
>>> Is this possible? I can limit the number of websocket connections per
>>> user (here the user has a unique username which I used to save as contact
>>> in the location table ) so that the server will reject the connection above
>>> that ?
>>>
>>> Please do suggest . Your help is appreciated .
>>>
>>> *Thanks & Regards*
>>> *Sasmita Panda*
>>> *Senior Network Testing and Software Engineer*
>>> *3CLogic , ph:07827611765*
>>> _______________________________________________
>>> Users mailing list
>>> Users at lists.opensips.org
>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>
>>
>>
>> --
>> Best regards,
>> Ihor (Igor)
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>


-- 
Best regards,
Ihor (Igor)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240321/fbb30c76/attachment.html>

From alain.bieuzent at free.fr  Thu Mar 21 10:29:34 2024
From: alain.bieuzent at free.fr (Alain Bieuzent)
Date: Thu, 21 Mar 2024 11:29:34 +0100
Subject: [OpenSIPS-Users] OPENSIP 3.4 send_reply and tight matching
	failed
In-Reply-To: <e7cf336c-d2a5-4f2b-86ac-399eca7feb29@opensips.org>
References: <84BD48FD-8F95-4798-8201-7F87E54DAE4C@free.fr>
 <858EE736-AF3A-46A4-8EBC-8ABF8BC30A8E@free.fr>
 <027f24dd-f225-468b-9d05-ce31e3a3ee1c@opensips.org>
 <14EC8DDF-6F01-4C71-91D5-F0A567CD23C9@free.fr>
 <e7cf336c-d2a5-4f2b-86ac-399eca7feb29@opensips.org>
Message-ID: <CFD0CD52-7CA7-4D15-A1A9-BC859B139065@free.fr>

Hi bogdan,

 

Find attached the sip traces where we have this error log:

 

Mar 21 11:24:13 lbsip-rtpe-test opensips[3108]: WARNING:dialog:dlg_onroute: tight matching failed for ACK with callid='6a543fbd6eabdc7b797dfd6d56db1568 at 10.101.180.176:5060'/52, ftag='as5625de52'/10, ttag='b5a7-94b8b0d1dd76318f3d174a911be4ece2'/37 and direction=1

Mar 21 11:24:13 lbsip-rtpe-test opensips[3108]: WARNING:dialog:dlg_onroute: dialog identification elements are callid='6a543fbd6eabdc7b797dfd6d56db1568 at 10.101.180.176:5060'/52, caller tag='as5625de52'/10, callee tag='3920005391-2017127892'/21

 

De : Bogdan-Andrei Iancu <bogdan at opensips.org>
Date : mercredi 20 mars 2024 à 16:45
À : Alain Bieuzent <alain.bieuzent at free.fr>, OpenSIPS users mailling list <users at lists.opensips.org>
Objet : Re: [OpenSIPS-Users] OPENSIP 3.4 send_reply and tight matching failed

 

Not the logs, but the trace/ SIP capture - I need to see the sip traffic to understand the context of the issue.


Bogdan-Andrei Iancu
 
OpenSIPS Founder and Developer
  https://www.opensips-solutions.com
  https://www.siphub.com
On 20.03.2024 17:14, Alain Bieuzent wrote:

Bellow the link to the traces : 

 

https://www.transfernow.net/dl/20240320jzEA98Vz

 

De : Bogdan-Andrei Iancu <bogdan at opensips.org>
Date : mercredi 20 mars 2024 à 14:29
À : OpenSIPS users mailling list <users at lists.opensips.org>, Alain Bieuzent <alain.bieuzent at free.fr>
Objet : Re: [OpenSIPS-Users] OPENSIP 3.4 send_reply and tight matching failed

 

Hi,

The script snippet has nothing to do with the matching - it is about a 200-ok ACK to be matched by the dialog module and the TO-tag does not match at all. 

The link to the trace expired, if you could repost.

Regards,


Bogdan-Andrei Iancu
 
OpenSIPS Founder and Developer
  https://www.opensips-solutions.com
  https://www.siphub.com
On 12.03.2024 14:57, Alain Bieuzent wrote:

Hi all,

 

I am in the process of migrating my proxies from 3.3.9 to 3.4.4.

In 3.4 I find myself with a fault when I try to rewrite a final cause.

 

if (t_check_status("500"))

         {

                          send_reply(503,"Service Unavailable");

                         exit;

          }

 

with 3.3 version, this code works perfectly, since 3.4 I have this error:

 

WARNING:dialog:dlg_onroute: tight matching failed for ACK with callid='67457c401e9ea52e2750100979253a7a at 10.101.180.177:5060'/52, ftag='as5328cea7'/10, ttag='b5a7-2a346bb9d510da893a ee7cda850584cb'/37 and direction=1

WARNING:dialog:dlg_onroute: dialog identification elements are callid='67457c401e9ea52e2750100979253a7a at 10.101.180.177:5060'/52, caller tag='as5328cea7'/10, callee tag='3919223738-770090972'/ 20

 

Has anyone encountered this error before?

 

Complete traces here : https://www.transfernow.net/dl/20240312qvAFfIAL.

 

Regards




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







-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240321/8432f0b4/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 6a543fbd6eabdc7b797dfd6d56db1568 at 10.101.180.176 5060.pcap
Type: application/octet-stream
Size: 1732 bytes
Desc: not available
URL: <http://lists.opensips.org/pipermail/users/attachments/20240321/8432f0b4/attachment-0001.obj>

From prathibhab.tvm at gmail.com  Thu Mar 21 12:06:47 2024
From: prathibhab.tvm at gmail.com (Prathibha B)
Date: Thu, 21 Mar 2024 17:36:47 +0530
Subject: [OpenSIPS-Users] fetch username from the URI
Message-ID: <CAJh_-cC4g-VWuyTLxu=fMK2fBjq6xW1L_e6B9MfBGx=foU-TkQ@mail.gmail.com>

I am getting the source and destination URI from $fu and $ru.  How to fetch
the SIP username from the source and destination URI.

What I've tried and not working:
# Extract destination URI from the R-URI (Request-URI)
            $var(destination_uri) = $(ru);

            # Find the position of "@" character in the URI
            $var(at_position) = strstr($(ru), "@");

            # If "@" is found, extract the substring before it as the SIP
username
            if ($var(at_position) != -1) {
                $var(destination_username) = substr($var(destination_uri),
4, $var(at_position) - 5);
            } else {
                $var(destination_username) = "Unknown";
            }

-- 
Regards,
B.Prathibha
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240321/41301cc3/attachment.html>

From razvan at opensips.org  Thu Mar 21 12:14:15 2024
From: razvan at opensips.org (=?UTF-8?Q?R=C4=83zvan_Crainea?=)
Date: Thu, 21 Mar 2024 14:14:15 +0200
Subject: [OpenSIPS-Users] =?utf-8?q?Build_an_IMS_using_OpenSIPS_3=2E5_?=
	=?utf-8?q?=E2=80=93_S-CSCF?=
Message-ID: <c643f26d-215d-4c72-b6eb-4bcc1a43d1be@opensips.org>

Hi, everyone!

Check out our latest blog post to find out about the latest features 
we've developed for OpenSIPS 3.5, and how you can use them to build a 
fully fledged S-CSCF IMS solution:

https://blog.opensips.org/2024/03/21/build-an-ims-using-opensips-3-5-s-cscf-part-1/

Happy hacking!

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


From prathibhab.tvm at gmail.com  Thu Mar 21 13:22:34 2024
From: prathibhab.tvm at gmail.com (Prathibha B)
Date: Thu, 21 Mar 2024 13:22:34 +0000
Subject: [OpenSIPS-Users] fetch username from the URI
In-Reply-To: <CAJh_-cC4g-VWuyTLxu=fMK2fBjq6xW1L_e6B9MfBGx=foU-TkQ@mail.gmail.com>
References: <CAJh_-cC4g-VWuyTLxu=fMK2fBjq6xW1L_e6B9MfBGx=foU-TkQ@mail.gmail.com>
Message-ID: <TYZPR06MB7525525D90CF9B4918C0820CFC322@TYZPR06MB7525.apcprd06.prod.outlook.com>

Issue resolved

Sent from Outlook for Android<https://aka.ms/AAb9ysg>
________________________________
From: Prathibha B <prathibhab.tvm at gmail.com>
Sent: Thursday, March 21, 2024 5:36:47 PM
To: OpenSIPS users mailling list <users at lists.opensips.org>
Subject: fetch username from the URI

I am getting the source and destination URI from $fu and $ru.  How to fetch the SIP username from the source and destination URI.

What I've tried and not working:
# Extract destination URI from the R-URI (Request-URI)
            $var(destination_uri) = $(ru);

            # Find the position of "@" character in the URI
            $var(at_position) = strstr($(ru), "@");

            # If "@" is found, extract the substring before it as the SIP username
            if ($var(at_position) != -1) {
                $var(destination_username) = substr($var(destination_uri), 4, $var(at_position) - 5);
            } else {
                $var(destination_username) = "Unknown";
            }

--
Regards,
B.Prathibha
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240321/bcf35c4c/attachment.html>

From medeanwz at gmail.com  Thu Mar 21 13:23:38 2024
From: medeanwz at gmail.com (M S)
Date: Thu, 21 Mar 2024 14:23:38 +0100
Subject: [OpenSIPS-Users] fetch username from the URI
In-Reply-To: <CAJh_-cC4g-VWuyTLxu=fMK2fBjq6xW1L_e6B9MfBGx=foU-TkQ@mail.gmail.com>
References: <CAJh_-cC4g-VWuyTLxu=fMK2fBjq6xW1L_e6B9MfBGx=foU-TkQ@mail.gmail.com>
Message-ID: <CAEZrhoM7hoKsaDkCi-pntBpqfpQNv51u6wdJXU6zyXjr-oXU-g@mail.gmail.com>

A wise man once said, the online manual should be your bible here :)
openSIPS | Documentation / Core Variables - 3.4
<https://opensips.org/Documentation/Script-CoreVar-3-4#rU>


On Thu, Mar 21, 2024 at 1:09 PM Prathibha B <prathibhab.tvm at gmail.com>
wrote:

> I am getting the source and destination URI from $fu and $ru.  How to
> fetch the SIP username from the source and destination URI.
>
> What I've tried and not working:
> # Extract destination URI from the R-URI (Request-URI)
>             $var(destination_uri) = $(ru);
>
>             # Find the position of "@" character in the URI
>             $var(at_position) = strstr($(ru), "@");
>
>             # If "@" is found, extract the substring before it as the SIP
> username
>             if ($var(at_position) != -1) {
>                 $var(destination_username) = substr($var(destination_uri),
> 4, $var(at_position) - 5);
>             } else {
>                 $var(destination_username) = "Unknown";
>             }
>
> --
> Regards,
> B.Prathibha
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240321/1213f722/attachment.html>

From Li.Cai at comtech.com  Thu Mar 21 13:35:23 2024
From: Li.Cai at comtech.com (Li Cai)
Date: Thu, 21 Mar 2024 13:35:23 +0000
Subject: [OpenSIPS-Users] Can't locate Opensips-cli package's location on
	Ubuntu22.04
Message-ID: <SA1PR09MB80001CB7FE62CDA5F451113A8E322@SA1PR09MB8000.namprd09.prod.outlook.com>

Hi All,

I'm doing migrating from OpenSIPs 2.X to 3.0 on Ubuntu22.04. Here I met a problem to install Opensips-cli on Ubuntu22.
After successfully executing the steps from the installation instruction, like this -
[cid:image001.png at 01DA7B72.F6AECCF0]

The command of 'sudo apt-get install opensip-cli' still can't work, the output is -
[cid:image002.png at 01DA7B72.F6AECCF0]

The command complains that it can't locate the package opensips-cli.

Can anyone help with this issue? Any hint will be highly appreciated.


Thanks,
Li
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240321/51bef1ae/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 19550 bytes
Desc: image001.png
URL: <http://lists.opensips.org/pipermail/users/attachments/20240321/51bef1ae/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 5860 bytes
Desc: image002.png
URL: <http://lists.opensips.org/pipermail/users/attachments/20240321/51bef1ae/attachment-0003.png>

From alain.bieuzent at free.fr  Thu Mar 21 14:11:36 2024
From: alain.bieuzent at free.fr (Alain Bieuzent)
Date: Thu, 21 Mar 2024 15:11:36 +0100
Subject: [OpenSIPS-Users] Can't locate Opensips-cli package's location
 on Ubuntu22.04
Message-ID: <7673C93C-250B-4300-89CE-93050F25FBD9@free.fr>

Did you run an apt update before apt install opensips-cli ?

 

De : Users <users-bounces at lists.opensips.org> au nom de Li Cai <Li.Cai at comtech.com>
Répondre à : OpenSIPS users mailling list <users at lists.opensips.org>
Date : jeudi 21 mars 2024 à 14:37
À : "users at lists.opensips.org" <users at lists.opensips.org>
Objet : [OpenSIPS-Users] Can't locate Opensips-cli package's location on Ubuntu22.04

 

Hi All,

 

I’m doing migrating from OpenSIPs 2.X to 3.0 on Ubuntu22.04. Here I met a problem to install Opensips-cli on Ubuntu22.

After successfully executing the steps from the installation instruction, like this –

 

The command of ‘sudo apt-get install opensip-cli’ still can’t work, the output is –

 

The command complains that it can’t locate the package opensips-cli.

 

Can anyone help with this issue? Any hint will be highly appreciated.

 

 

Thanks,

Li

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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240321/b71cce08/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 19551 bytes
Desc: not available
URL: <http://lists.opensips.org/pipermail/users/attachments/20240321/b71cce08/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 5861 bytes
Desc: not available
URL: <http://lists.opensips.org/pipermail/users/attachments/20240321/b71cce08/attachment-0003.png>

From gmaruzz at gmail.com  Thu Mar 21 14:54:09 2024
From: gmaruzz at gmail.com (Giovanni Maruzzelli)
Date: Thu, 21 Mar 2024 15:54:09 +0100
Subject: [OpenSIPS-Users]
	=?utf-8?q?=5BWG-IMS=5D_Build_an_IMS_using_OpenSI?=
	=?utf-8?b?UFMgMy41IOKAkyBTLUNTQ0Y=?=
In-Reply-To: <c643f26d-215d-4c72-b6eb-4bcc1a43d1be@opensips.org>
References: <c643f26d-215d-4c72-b6eb-4bcc1a43d1be@opensips.org>
Message-ID: <CALXCt0qif9qpL-NoME4GWi0X_Ha6N83DMHmrus9W_OTOsoC6Bg@mail.gmail.com>

On Thu, Mar 21, 2024 at 1:15 PM Răzvan Crainea <razvan at opensips.org> wrote:

>
> Check out our latest blog post to find out about the latest features
> we've developed for OpenSIPS 3.5, and how you can use them to build a
> fully fledged S-CSCF IMS solution:
>
>
> https://blog.opensips.org/2024/03/21/build-an-ims-using-opensips-3-5-s-cscf-part-1/
>
>
a small feat for such a man, a very big achievement for our community!

CONGRATULATIONS RAZVAN !!!

-giovanni

--
Sincerely,

Giovanni Maruzzelli
OpenTelecom.IT
cell: +39 347 266 56 18
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240321/4880d4ec/attachment.html>

From razvan at opensips.org  Thu Mar 21 14:56:05 2024
From: razvan at opensips.org (=?UTF-8?Q?R=C4=83zvan_Crainea?=)
Date: Thu, 21 Mar 2024 16:56:05 +0200
Subject: [OpenSIPS-Users]
 =?utf-8?q?=5BWG-IMS=5D_Build_an_IMS_using_OpenSI?=
 =?utf-8?b?UFMgMy41IOKAkyBTLUNTQ0Y=?=
In-Reply-To: <CALXCt0qif9qpL-NoME4GWi0X_Ha6N83DMHmrus9W_OTOsoC6Bg@mail.gmail.com>
References: <c643f26d-215d-4c72-b6eb-4bcc1a43d1be@opensips.org>
 <CALXCt0qif9qpL-NoME4GWi0X_Ha6N83DMHmrus9W_OTOsoC6Bg@mail.gmail.com>
Message-ID: <834bf60a-b5c8-43ae-911d-9dc00c83bd48@opensips.org>



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

On 3/21/24 16:54, Giovanni Maruzzelli wrote:
> On Thu, Mar 21, 2024 at 1:15 PM Răzvan Crainea <razvan at opensips.org> wrote:
> 
>>
>> Check out our latest blog post to find out about the latest features
>> we've developed for OpenSIPS 3.5, and how you can use them to build a
>> fully fledged S-CSCF IMS solution:
>>
>>
>> https://blog.opensips.org/2024/03/21/build-an-ims-using-opensips-3-5-s-cscf-part-1/
>>
>>
> a small feat for such a man, a very big achievement for our community!
> 
> CONGRATULATIONS RAZVAN !!!
> 
Thanks, Giovanni! But stay tuned, other surprises are on the way :)


From rvg at rvgeerligs.nl  Thu Mar 21 14:57:00 2024
From: rvg at rvgeerligs.nl (rvg at rvgeerligs.nl)
Date: Thu, 21 Mar 2024 14:57:00 +0000
Subject: [OpenSIPS-Users] Can't locate Opensips-cli package's location
 on Ubuntu22.04
In-Reply-To: <7673C93C-250B-4300-89CE-93050F25FBD9@free.fr>
References: <7673C93C-250B-4300-89CE-93050F25FBD9@free.fr>
Message-ID: <d70071f1ba6ea358b19a03c2ab8a6df77b10a15f@rvgeerligs.nl>

check the location of the fifo file in opensips.cfg it should be in /var... as the same in opensips-cli.cfg. 2 cfg file shoud be pointing to the same file



March 21, 2024 at 3:11 PM, "Alain Bieuzent" <alain.bieuzent at free.fr> wrote:


> 
> Did you run an apt update before apt install opensips-cli ?
> 
> **De : **Users <users-bounces at lists.opensips.org> au nom de Li Cai <Li.Cai at comtech.com>
> **Répondre à : **OpenSIPS users mailling list <users at lists.opensips.org>
> **Date : **jeudi 21 mars 2024 à 14:37
> **À : **"users at lists.opensips.org" <users at lists.opensips.org>
> **Objet : **[OpenSIPS-Users] Can't locate Opensips-cli package's location on Ubuntu22.04
> 
> Hi All,
> 
> I’m doing migrating from OpenSIPs 2.X to 3.0 on Ubuntu22.04. Here I met a problem to install Opensips-cli on Ubuntu22.
> 
> After successfully executing the steps from the installation instruction, like this –
> 
> The command of ‘sudo apt-get install opensip-cli’ still can’t work, the output is –
> 
> The command complains that it can’t locate the package opensips-cli.
> 
> Can anyone help with this issue? Any hint will be highly appreciated.
> 
> Thanks,
> 
> Li
> 
> _______________________________________________ Users mailing list Users at lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240321/6237853b/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 19551 bytes
Desc: not available
URL: <http://lists.opensips.org/pipermail/users/attachments/20240321/6237853b/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 5861 bytes
Desc: not available
URL: <http://lists.opensips.org/pipermail/users/attachments/20240321/6237853b/attachment-0003.png>

From bogdan at opensips.org  Thu Mar 21 16:29:51 2024
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Thu, 21 Mar 2024 18:29:51 +0200
Subject: [OpenSIPS-Users] SDP
In-Reply-To: <5b6b65f42c7b497fae7f6d7554f07251@tetab.nu>
References: <CAJh_-cBOLA_zfLWrfYqX2rb8divky_JBt1ekyNDzSpH9-2_gYg@mail.gmail.com>
 <c8530347bc2844ed9341aa1ab7b6ff0e@tetab.nu>
 <a7f44e25-2669-41e5-8269-f2359554a521@opensips.org>
 <5b6b65f42c7b497fae7f6d7554f07251@tetab.nu>
Message-ID: <c7a5b1e7-d75d-43b9-9ab3-4f2019d29ee6@opensips.org>

Hi,

What OpenSIPS version are you using?

Regards,

Bogdan-Andrei Iancu

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

On 21.03.2024 00:09, Stefan Carlsson wrote:
>
> Hi !
>
> I sincerely apologize that I not read thru all the modules before my 
> orginal post , I’ve found that textops module can search and replace
>
> the text in both the header and the body. (which I mailed to the 
> requester)
>
> I’ve tried some of the exported functions but:
>
> orginal snap:  o=root 276479022 276479022 IN IP4 172.24.7.20
>
> $avp(reinv_sess_id) = “12345678”;    # Got this from  
> $avp(reinv_oline) = $(rb{sdp.line,o})   and some regex tweeking and 
>      $(avp(reinv_result){s.select,1,;})
>
> $avp(reinv_sess_ver) = “276479022”;
>
> replace_body("$avp(reinv_sess_ver)","$avp(reinv_sess_id)");
>
> This seemed not to work …
>
> but this did:
>
> Original text snap:        a=sendrecv
>
> replace_body("a=sendrecv", "a=sendonly");       # Indicate call hold 
> according RFC3264
>
> // Regards …
>
> Stefan
>
> *From:* Bogdan-Andrei Iancu <bogdan at opensips.org>
> *Sent:* Wednesday, 20 March, 2024 14:44
> *To:* OpenSIPS users mailling list <users at lists.opensips.org>; Stefan 
> Carlsson <stefan.carlsson at tetab.nu>
> *Subject:* Re: [OpenSIPS-Users] SDP
>
> Nothing is impossible as time as you search in the right place (aka 
> the Manual). See my reply on your thread.
>
> Regards,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developer
>    https://www.opensips-solutions.com
>    https://www.siphub.com
>
> On 14.03.2024 09:50, Stefan Carlsson wrote:
>
>     Hi !
>
>     You can use the module sipmsgops to view and change some of the
>     ADP fields such as codecs and streams … but unfortunately you
>     don’t have
>
>     complete control of the SDP compared to what it seems could be
>     done on the Kamailio SIP router
>
>     I need to change the a=sendrecv field and it seems to be impossible ☹
>
>     Regards …
>
>     _________________________________
>
>     Stefan Carlsson
>
>     *From:* Users <users-bounces at lists.opensips.org>
>     <mailto:users-bounces at lists.opensips.org> *On Behalf Of *Prathibha B
>     *Sent:* Thursday, 14 March, 2024 05:16
>     *To:* OpenSIPS users mailling list <users at lists.opensips.org>
>     <mailto:users at lists.opensips.org>
>     *Subject:* [OpenSIPS-Users] SDP
>
>     How to see the SDP in opensips?
>
>     -- 
>
>     Regards,
>
>     B.Prathibha
>
>
>
>     _______________________________________________
>
>     Users mailing list
>
>     Users at lists.opensips.org
>
>     http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240321/a0cc465c/attachment.html>

From bogdan at opensips.org  Thu Mar 21 16:31:59 2024
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Thu, 21 Mar 2024 18:31:59 +0200
Subject: [OpenSIPS-Users] Need some help on opensips error for wss
 handshek .
In-Reply-To: <CALf-Q45hHB93vR+DgZHi29j0JGznOSmfJvRiuuPYuszi4fD90w@mail.gmail.com>
References: <CALf-Q44nYwthB2z=ignY9uXwrEWhb6tgrXom24v2HwXFDd7UoA@mail.gmail.com>
 <e98e705b-0968-4828-84d7-b101367d2a14@opensips.org>
 <CALf-Q44WNwsU8owQ5ZNErnwXkxGuzzKOhKT7fWtcVTNxiy+YLw@mail.gmail.com>
 <579b76bd-609a-4f44-9b78-a3d7f6823c67@opensips.org>
 <CALf-Q45hHB93vR+DgZHi29j0JGznOSmfJvRiuuPYuszi4fD90w@mail.gmail.com>
Message-ID: <0d6a1cad-7d03-4889-a686-93d0439d7d53@opensips.org>

Just try the pointed patch, to see if it solves your problem..

Regards,

Bogdan-Andrei Iancu

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

On 21.03.2024 08:37, Sasmita Panda wrote:
> We are using webrtc Client integrated with browsers using sipml5 
> client library . I think this is a common library used across the glob .
> Every customer that has this same client running with webrtc Server 
> (having opensips) is common .
> But the error I have seen is for one or two agents only .
>
>
> So the error is for the client or the network ? If it can be the 
> network then I may suggest the customer to change the network while 
> using webrtc client .
>
>
> */Thanks & Regards/*
> /Sasmita Panda/
> /Senior Network Testing and Software Engineer/
> /3CLogic , ph:07827611765/
>
>
> On Wed, Mar 20, 2024 at 7:55 PM Bogdan-Andrei Iancu 
> <bogdan at opensips.org> wrote:
>
>     Hi,
>
>     There is a fix (to tolerate different version numbers there) but
>     only in OpenSIPS 3.5 [1] (the devel version), not yet backported
>     to stable 3.4 and 3.2. You can try to do the backport by yourself.
>
>     BTW, what WS client & browser are you using ?? It is pretty
>     unusual what you report here.
>
>     [1]
>     https://github.com/OpenSIPS/opensips/commit/e30a355397b285a5140ebb25a485bed7134de7ee
>
>     Bogdan-Andrei Iancu
>
>     OpenSIPS Founder and Developer
>        https://www.opensips-solutions.com
>        https://www.siphub.com
>
>     On 20.03.2024 15:30, Sasmita Panda wrote:
>>     Hi Bogdan,
>>     I appreciate your reply .
>>
>>     How can I suggest modifying this header ? Because I have seen
>>     this for some remote agents who run in the browser . I don't have
>>     access to the browser .
>>     The browser which got connected successfully I couldn't see such
>>     types of logs  .
>>
>>     What causes this header version in the wss connection ?
>>
>>
>>     */Thanks & Regards/*
>>     /Sasmita Panda/
>>     /Senior Network Testing and Software Engineer/
>>     /3CLogic , ph:07827611765/
>>
>>
>>     On Wed, Mar 20, 2024 at 6:51 PM Bogdan-Andrei Iancu
>>     <bogdan at opensips.org> wrote:
>>
>>         Hi,
>>
>>         OpenSIPS does not like that 1.1 version in the VIA hdr - it
>>         expects 2.0 (the SIP version).
>>
>>         Regards,
>>
>>         Bogdan-Andrei Iancu
>>
>>         OpenSIPS Founder and Developer
>>            https://www.opensips-solutions.com
>>            https://www.siphub.com
>>
>>         On 12.03.2024 10:57, Sasmita Panda wrote:
>>>         Hi All ,
>>>
>>>         1"  :callID 080a9ef8-3911-6c41-689c-fbb5d02e3aae
>>>         Mar 12 08:23:11 localhost /usr/sbin/opensips[12987]:
>>>         ERROR:core:parse_via: bad char <1> on state 100
>>>         Mar 12 08:23:11 localhost /usr/sbin/opensips[12987]:
>>>         ERROR:core:parse_via:  <1.1 p1wsa01.rivagecapital.com:80
>>>         <http://p1wsa01.rivagecapital.com:80>
>>>         (Cisco-WSA/12.5.4-011)#015#012#015#012>
>>>         Mar 12 08:23:11 localhost /usr/sbin/opensips[12987]:
>>>         ERROR:core:parse_via: via parse failed
>>>         Mar 12 08:23:11 localhost /usr/sbin/opensips[12987]:
>>>         ERROR:core:get_hdr_field: bad via
>>>         Mar 12 08:23:11 localhost /usr/sbin/opensips[12987]:
>>>         INFO:core:parse_headers: bad header field
>>>         Mar 12 08:23:11 localhost /usr/sbin/opensips[12987]:
>>>         ERROR:proto_wss:ws_parse_req_handshake: cannot parse
>>>         headers#012Upgrade: websocket#015#012Connection:
>>>         Upgrade#015#012Host: ir-webrtc2.3ccloud.com#015#012Pragma
>>>         <http://ir-webrtc2.3ccloud.com#015%23012Pragma>:
>>>         no-cache#015#012Cache-Control: no-cache#015#012User-Agent:
>>>         Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
>>>         (KHTML, like Gecko) Chrome/122.0.0.0 <http://122.0.0.0>
>>>         Safari/537.36 Edg/122.0.0.0#015#012Origin
>>>         <http://122.0.0.0#015%23012Origin>:
>>>         https://ir-static.3ccloud.com#015#012Sec-WebSocket-Version
>>>         <https://ir-static.3ccloud.com#015%23012Sec-WebSocket-Version>:
>>>         13#015#012Accept-Encoding: gzip, br#015#012Accept-Language:
>>>         en-GB,en;q=0.9,en-US;q=0.8#015#012Sec-WebSocket-Key:
>>>         I/8XqtXyBCAGorZYjnTYQA==#015#012Sec-WebSocket-Extensions:
>>>         permessage-deflate;
>>>         client_max_window_bits#015#012Sec-WebSocket-Protocol:
>>>         sip#015#012X-IMForwards: 20#015#012Via: 1.1
>>>         p1wsa01.rivagecapital.com:80
>>>         <http://p1wsa01.rivagecapital.com:80>
>>>         (Cisco-WSA/12.5.4-011)#015#012#015#012
>>>
>>>
>>>          I am getting this error on my opensips server where I am
>>>         running webrtc . What is this error for ?
>>>
>>>
>>>         */Thanks & Regards/*
>>>         /Sasmita Panda/
>>>         /Senior Network Testing and Software Engineer/
>>>         /3CLogic , ph:07827611765/
>>>
>>>         _______________________________________________
>>>         Users mailing list
>>>         Users at lists.opensips.org
>>>         http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240321/21eeb682/attachment-0001.html>

From bogdan at opensips.org  Thu Mar 21 17:06:26 2024
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Thu, 21 Mar 2024 19:06:26 +0200
Subject: [OpenSIPS-Users] OPENSIP 3.4 send_reply and tight matching
	failed
In-Reply-To: <CFD0CD52-7CA7-4D15-A1A9-BC859B139065@free.fr>
References: <84BD48FD-8F95-4798-8201-7F87E54DAE4C@free.fr>
 <858EE736-AF3A-46A4-8EBC-8ABF8BC30A8E@free.fr>
 <027f24dd-f225-468b-9d05-ce31e3a3ee1c@opensips.org>
 <14EC8DDF-6F01-4C71-91D5-F0A567CD23C9@free.fr>
 <e7cf336c-d2a5-4f2b-86ac-399eca7feb29@opensips.org>
 <CFD0CD52-7CA7-4D15-A1A9-BC859B139065@free.fr>
Message-ID: <80e7c4bf-a581-4c4e-b899-d37a1cbf3618@opensips.org>

HI Alan,

I suspect a scripting issue, making the received hop-by-hop ACK (for 
negative replies) to be "handled" by the dialog module, which treats it 
as a end-2-end ACK (for 200 OK reply).

I guess your script lacks this block 
https://github.com/OpenSIPS/opensips/blob/master/etc/opensips.cfg#L112 
when comes to sequential requests; this block needs to be before the 
loose_route or any dialog/TH matching.

Regards,

Bogdan-Andrei Iancu

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

On 21.03.2024 12:29, Alain Bieuzent wrote:
>
> Hi bogdan,
>
> Find attached the sip traces where we have this error log:
>
> Mar 21 11:24:13 lbsip-rtpe-test opensips[3108]: 
> WARNING:dialog:dlg_onroute: tight matching failed for ACK with 
> callid='6a543fbd6eabdc7b797dfd6d56db1568 at 10.101.180.176:5060'/52, 
> ftag='as5625de52'/10, ttag='b5a7-94b8b0d1dd76318f3d174a911be4ece2'/37 
> and direction=1
>
> Mar 21 11:24:13 lbsip-rtpe-test opensips[3108]: 
> WARNING:dialog:dlg_onroute: dialog identification elements are 
> callid='6a543fbd6eabdc7b797dfd6d56db1568 at 10.101.180.176:5060'/52, 
> caller tag='as5625de52'/10, callee tag='3920005391-2017127892'/21
>
> *De : *Bogdan-Andrei Iancu <bogdan at opensips.org>
> *Date : *mercredi 20 mars 2024 à 16:45
> *À : *Alain Bieuzent <alain.bieuzent at free.fr>, OpenSIPS users mailling 
> list <users at lists.opensips.org>
> *Objet : *Re: [OpenSIPS-Users] OPENSIP 3.4 send_reply and tight 
> matching failed
>
> Not the logs, but the trace/ SIP capture - I need to see the sip 
> traffic to understand the context of the issue.
>
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developer
>    https://www.opensips-solutions.com
>    https://www.siphub.com
>
> On 20.03.2024 17:14, Alain Bieuzent wrote:
>
>     Bellow the link to the traces :
>
>     https://www.transfernow.net/dl/20240320jzEA98Vz
>
>     *De : *Bogdan-Andrei Iancu <bogdan at opensips.org>
>     <mailto:bogdan at opensips.org>
>     *Date : *mercredi 20 mars 2024 à 14:29
>     *À : *OpenSIPS users mailling list <users at lists.opensips.org>
>     <mailto:users at lists.opensips.org>, Alain Bieuzent
>     <alain.bieuzent at free.fr> <mailto:alain.bieuzent at free.fr>
>     *Objet : *Re: [OpenSIPS-Users] OPENSIP 3.4 send_reply and tight
>     matching failed
>
>     Hi,
>
>     The script snippet has nothing to do with the matching - it is
>     about a 200-ok ACK to be matched by the dialog module and the
>     TO-tag does not match at all.
>
>     The link to the trace expired, if you could repost.
>
>     Regards,
>
>
>     Bogdan-Andrei Iancu
>
>       
>
>     OpenSIPS Founder and Developer
>
>        https://www.opensips-solutions.com
>
>        https://www.siphub.com
>
>     On 12.03.2024 14:57, Alain Bieuzent wrote:
>
>         Hi all,
>
>         I am in the process of migrating my proxies from 3.3.9 to 3.4.4.
>
>         In 3.4 I find myself with a fault when I try to rewrite a
>         final cause.
>
>         if (t_check_status("500"))
>
>                  {
>
>         send_reply(503,"Service Unavailable");
>
>         exit;
>
>         }
>
>         with 3.3 version, this code works perfectly, since 3.4 I have
>         this error:
>
>         WARNING:dialog:dlg_onroute: tight matching failed for ACK with
>         callid='67457c401e9ea52e2750100979253a7a at 10.101.180.177:5060'/52,
>         ftag='as5328cea7'/10, ttag='b5a7-2a346bb9d510da893a
>         ee7cda850584cb'/37 and direction=1
>
>         WARNING:dialog:dlg_onroute: dialog identification elements are
>         callid='67457c401e9ea52e2750100979253a7a at 10.101.180.177:5060'/52,
>         caller tag='as5328cea7'/10, callee tag='3919223738-770090972'/ 20
>
>         Has anyone encountered this error before?
>
>         Complete traces here :
>         https://www.transfernow.net/dl/20240312qvAFfIAL.
>
>         Regards
>
>
>
>
>         _______________________________________________
>
>         Users mailing list
>
>         Users at lists.opensips.org
>
>         http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240321/2cbfb224/attachment.html>

From prathibhab.tvm at gmail.com  Fri Mar 22 00:10:12 2024
From: prathibhab.tvm at gmail.com (Prathibha B)
Date: Fri, 22 Mar 2024 00:10:12 +0000
Subject: [OpenSIPS-Users] SDP
In-Reply-To: <c7a5b1e7-d75d-43b9-9ab3-4f2019d29ee6@opensips.org>
References: <CAJh_-cBOLA_zfLWrfYqX2rb8divky_JBt1ekyNDzSpH9-2_gYg@mail.gmail.com>
 <c8530347bc2844ed9341aa1ab7b6ff0e@tetab.nu>
 <a7f44e25-2669-41e5-8269-f2359554a521@opensips.org>
 <5b6b65f42c7b497fae7f6d7554f07251@tetab.nu>
 <c7a5b1e7-d75d-43b9-9ab3-4f2019d29ee6@opensips.org>
Message-ID: <TYZPR06MB7525A61BA26FA492C464CFB2FC312@TYZPR06MB7525.apcprd06.prod.outlook.com>

3.4

Sent from Outlook for Android<https://aka.ms/AAb9ysg>
________________________________
From: Users <users-bounces at lists.opensips.org> on behalf of Bogdan-Andrei Iancu <bogdan at opensips.org>
Sent: Thursday, March 21, 2024 9:59:51 PM
To: Stefan Carlsson <stefan.carlsson at tetab.nu>; users at lists.opensips.org <users at lists.opensips.org>
Subject: Re: [OpenSIPS-Users] SDP

Hi,

What OpenSIPS version are you using?

Regards,

Bogdan-Andrei Iancu

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

On 21.03.2024 00:09, Stefan Carlsson wrote:

Hi !

I sincerely apologize that I not read thru all the modules before my orginal post , I’ve found that textops module can search and replace

the text in both the header and the body. (which I mailed to the requester)



I’ve tried some of the exported functions but:



orginal snap:  o=root 276479022 276479022 IN IP4 172.24.7.20





$avp(reinv_sess_id) = “12345678”;    # Got this from  $avp(reinv_oline) = $(rb{sdp.line,o})   and some regex tweeking and      $(avp(reinv_result){s.select,1,;})





$avp(reinv_sess_ver) = “276479022”;



replace_body("$avp(reinv_sess_ver)","$avp(reinv_sess_id)");



This seemed not to work …



but this did:



Original text snap:        a=sendrecv



replace_body("a=sendrecv", "a=sendonly");       # Indicate call hold according RFC3264







// Regards …

Stefan





From: Bogdan-Andrei Iancu <bogdan at opensips.org><mailto:bogdan at opensips.org>
Sent: Wednesday, 20 March, 2024 14:44
To: OpenSIPS users mailling list <users at lists.opensips.org><mailto:users at lists.opensips.org>; Stefan Carlsson <stefan.carlsson at tetab.nu><mailto:stefan.carlsson at tetab.nu>
Subject: Re: [OpenSIPS-Users] SDP



Nothing is impossible as time as you search in the right place (aka the Manual). See my reply on your thread.

Regards,


Bogdan-Andrei Iancu



OpenSIPS Founder and Developer

  https://www.opensips-solutions.com

  https://www.siphub.com

On 14.03.2024 09:50, Stefan Carlsson wrote:

Hi !



You can use the module sipmsgops to view and change some of the ADP fields such as codecs and streams … but unfortunately you don’t have

complete control of the SDP compared to what it seems could be done on the Kamailio SIP router



I need to change the a=sendrecv field and it seems to be impossible  ☹



Regards …

_________________________________

Stefan Carlsson



From: Users <users-bounces at lists.opensips.org><mailto:users-bounces at lists.opensips.org> On Behalf Of Prathibha B
Sent: Thursday, 14 March, 2024 05:16
To: OpenSIPS users mailling list <users at lists.opensips.org><mailto:users at lists.opensips.org>
Subject: [OpenSIPS-Users] SDP



How to see the SDP in opensips?



--

Regards,

B.Prathibha



_______________________________________________

Users mailing list

Users at lists.opensips.org<mailto:Users at lists.opensips.org>

http://lists.opensips.org/cgi-bin/mailman/listinfo/users



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240322/7ffc7fa5/attachment-0001.html>

From bogdan at opensips.org  Fri Mar 22 07:53:51 2024
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Fri, 22 Mar 2024 09:53:51 +0200
Subject: [OpenSIPS-Users] SDP
In-Reply-To: <f26617e5-d0b8-43a6-84f8-d577375a0137@tetab.nu>
References: <CAJh_-cBOLA_zfLWrfYqX2rb8divky_JBt1ekyNDzSpH9-2_gYg@mail.gmail.com>
 <c8530347bc2844ed9341aa1ab7b6ff0e@tetab.nu>
 <a7f44e25-2669-41e5-8269-f2359554a521@opensips.org>
 <5b6b65f42c7b497fae7f6d7554f07251@tetab.nu>
 <c7a5b1e7-d75d-43b9-9ab3-4f2019d29ee6@opensips.org>
 <f26617e5-d0b8-43a6-84f8-d577375a0137@tetab.nu>
Message-ID: <117fb6ff-5ee5-4d10-80e7-bc74e1d62c30@opensips.org>

On 2.2 you cannot use variables as parms for any script functions, some 
of them do not support variables. And replace_body() is one of them.

In 3.4 all script functions can take vars as params, so you should be fine.

Regards,

Bogdan-Andrei Iancu

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

On 22.03.2024 08:37, Stefan Carlsson wrote:
> Still on 2.2 but are planning to migrste later in the spring to Ubuntu 
> and 3.4   ..
>
> Can you please in some quick notes tell me what must change in the 
> script if required....
> Regards …
>
> Stefan
>
> ------------------------------------------------------------------------
> *From:* Bogdan-Andrei Iancu <bogdan at opensips.org>
> *Sent:* Thursday, 21 March 2024 17:30
> *To:* Stefan Carlsson; users at lists.opensips.org
> *Subject:* Re: [OpenSIPS-Users] SDP
>
> Hi,
>
> What OpenSIPS version are you using?
>
> Regards,
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>    https://www.opensips-solutions.com
>    https://www.siphub.com
> On 21.03.2024 00:09, Stefan Carlsson wrote:
>>
>> Hi !
>>
>> I sincerely apologize that I not read thru all the modules before my 
>> orginal post , I’ve found that textops module can search and replace
>>
>> the text in both the header and the body. (which I mailed to the 
>> requester)
>>
>> I’ve tried some of the exported functions but:
>>
>> orginal snap:  o=root 276479022 276479022 IN IP4 172.24.7.20
>>
>> $avp(reinv_sess_id) = “12345678”;    # Got this from  
>> $avp(reinv_oline) = $(rb{sdp.line,o})   and some regex tweeking and 
>>      $(avp(reinv_result){s.select,1,;})
>>
>> $avp(reinv_sess_ver) = “276479022”;
>>
>> replace_body("$avp(reinv_sess_ver)","$avp(reinv_sess_id)");
>>
>> This seemed not to work …
>>
>> but this did:
>>
>> Original text snap:        a=sendrecv
>>
>> replace_body("a=sendrecv", "a=sendonly");       # Indicate call hold 
>> according RFC3264
>>
>> // Regards …
>>
>> Stefan
>>
>> *From:* Bogdan-Andrei Iancu <bogdan at opensips.org>
>> *Sent:* Wednesday, 20 March, 2024 14:44
>> *To:* OpenSIPS users mailling list <users at lists.opensips.org>; Stefan 
>> Carlsson <stefan.carlsson at tetab.nu>
>> *Subject:* Re: [OpenSIPS-Users] SDP
>>
>> Nothing is impossible as time as you search in the right place (aka 
>> the Manual). See my reply on your thread.
>>
>> Regards,
>>
>> Bogdan-Andrei Iancu
>>   
>> OpenSIPS Founder and Developer
>>    https://www.opensips-solutions.com
>>    https://www.siphub.com
>>
>> On 14.03.2024 09:50, Stefan Carlsson wrote:
>>
>>     Hi !
>>
>>     You can use the module sipmsgops to view and change some of the
>>     ADP fields such as codecs and streams … but unfortunately you
>>     don’t have
>>
>>     complete control of the SDP compared to what it seems could be
>>     done on the Kamailio SIP router
>>
>>     I need to change the a=sendrecv field and it seems to be impossible ☹
>>
>>     Regards …
>>
>>     _________________________________
>>
>>     Stefan Carlsson
>>
>>     *From:* Users <users-bounces at lists.opensips.org>
>>     <mailto:users-bounces at lists.opensips.org> *On Behalf Of *Prathibha B
>>     *Sent:* Thursday, 14 March, 2024 05:16
>>     *To:* OpenSIPS users mailling list <users at lists.opensips.org>
>>     <mailto:users at lists.opensips.org>
>>     *Subject:* [OpenSIPS-Users] SDP
>>
>>     How to see the SDP in opensips?
>>
>>     -- 
>>
>>     Regards,
>>
>>     B.Prathibha
>>
>>
>>
>>     _______________________________________________
>>
>>     Users mailing list
>>
>>     Users at lists.opensips.org
>>
>>     http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240322/fedfb993/attachment.html>

From guillaume.desgeorge at orange.com  Fri Mar 22 08:57:46 2024
From: guillaume.desgeorge at orange.com (guillaume.desgeorge at orange.com)
Date: Fri, 22 Mar 2024 08:57:46 +0000
Subject: [OpenSIPS-Users] How to access to a column of a location database
Message-ID: <PAVPR02MB92075A75244B3E49E6AF42A883312@PAVPR02MB9207.eurprd02.prod.outlook.com>

Hi everybody,
In my routing logic of my "opensips.cfg" file, I'm trying to access the "socket" field of the location table of registered contacts.
I have the registering informations correctly written in MySQL location table but can't find a function to access it.
I'd like to have a function which I give the registered username and can give me back the associated socket.
Is the lookup () function the good one ? I didn't understand how to use it that way.
Thanks for your help,

   Guillaume
Orange Restricted



Orange Restricted
____________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240322/2467c283/attachment-0001.html>

From spanda at 3clogic.com  Thu Mar 21 06:24:12 2024
From: spanda at 3clogic.com (Sasmita Panda)
Date: Thu, 21 Mar 2024 11:54:12 +0530
Subject: [OpenSIPS-Users] utimer_ticker warning in opensips 3.2
In-Reply-To: <2e986980-6548-4cd8-b1e5-cbbc65f60fe3@opensips.org>
References: <CALf-Q442AqxhLDxKt6_psUWUzcC1aGfZ9CrHvYXH_BU5GFGL2w@mail.gmail.com>
 <CALf-Q45dJ=hVdJPxsB7dU1PhER4VYBnHSU+3Jn9RwrvnZ1a=Hg@mail.gmail.com>
 <CALf-Q45xVfjagrctOVtAqEkEhPzeVNWK9Zj7Kfh4_Xow1QjOUQ@mail.gmail.com>
 <2e986980-6548-4cd8-b1e5-cbbc65f60fe3@opensips.org>
Message-ID: <CALf-Q46ceCOvwVf8gNKcdbkAaD99+k-rESkdGAoSrCno+jMf2w@mail.gmail.com>

Sometimes it crashes and sometimes while starting I get the warings of the
timer .  Same config  shows different issues .



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


On Wed, Mar 20, 2024 at 6:45 PM Bogdan-Andrei Iancu <bogdan at opensips.org>
wrote:

> Hi,
>
> How the two reports fit together here ? there are completely separate
> experiences on different runs?? or if you start opensips first you get the
> warnings and later it crashes ??
> For the crash part, I see a core file was generated - could you extract
> the backtrace and post here ? (see
> https://opensips.org/Documentation/TroubleShooting-Crash)
>
> Regards
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>   https://www.opensips-solutions.com
>   https://www.siphub.com
>
> On 11.03.2024 15:04, Sasmita Panda wrote:
>
> Any update on this ?
>
>
> *Thanks & Regards*
> *Sasmita Panda*
> *Senior Network Testing and Software Engineer*
> *3CLogic , ph:07827611765*
>
>
> On Mon, Mar 11, 2024 at 12:03 PM Sasmita Panda <spanda at 3clogic.com> wrote:
>
>> With the same server configuration and opensips version I am getting
>> below error as well .
>>
>> CRITICAL:core:fm_free: freeing already freed shm pointer
>> (0x7fc110e0b408), first free: (null): (null)(0) - aborting!
>>
>>  /usr/local/sbin/opensips[215171]: INFO:core:handle_sigs: child process
>> 215185 exited by a signal 6
>>  /usr/local/sbin/opensips[215171]: INFO:core:handle_sigs: core was
>> generated
>>  /usr/local/sbin/opensips[215171]: INFO:core:handle_sigs: terminating
>> due to SIGCHLD
>>  /usr/local/sbin/opensips[215172]: Memory status (pkg):
>>  /usr/local/sbin/opensips[215172]: fm_status (0x7fc2907ff010):
>>  /usr/local/sbin/opensips[215174]: INFO:core:sig_usr: signal 15 received
>>  /usr/local/sbin/opensips[215172]: heap size= 33554432
>>  /usr/local/sbin/opensips[215174]: Memory status (pkg):
>>  /usr/local/sbin/opensips[215172]: used= 3710048, used+overhead=3801344,
>> free=29844384
>>  /usr/local/sbin/opensips[215174]: fm_status (0x7fc2907ff010):
>>  /usr/local/sbin/opensips[215172]: max used (+overhead)= 3801344
>>  /usr/local/sbin/opensips[215174]: heap size= 33554432
>>  /usr/local/sbin/opensips[215172]: dumping free list:
>>  /usr/local/sbin/opensips[215174]: used= 229752, used+overhead=318936,
>> free=33324680
>>  /usr/local/sbin/opensips[215172]: hash =   1 fragments no.:     1,
>> unused:     0#012#011#011 bucket size:         8 -         8 (first
>> 8)
>>  /usr/local/sbin/opensips[215174]: max used (+overhead)= 385792
>>  /usr/local/sbin/opensips[215174]: dumping free list:
>>  /usr/local/sbin/opensips[215172]: hash =  18 fragments no.:     1,
>> unused:     0#012#011#011 bucket size:       144 -       144 (first
>> 144)
>>  /usr/local/sbin/opensips[215174]: hash =   7 fragments no.:   139,
>> unused:     0#012#011#011 bucket size:        56 -        56 (first
>>  56)
>>  /usr/local/sbin/opensips[215172]: hash = 2059 fragments no.:     1,
>> unused:     0#012#011#011 bucket size:  16777216 -  33554432 (first
>>  29752936)
>>  /usr/local/sbin/opensips[215174]: hash =  13 fragments no.:    37,
>> unused:     0#012#011#011 bucket size:       104 -       104 (first
>> 104)
>>  /usr/local/sbin/opensips[215172]: TOTAL:      3 free fragments =
>> 29753088 free bytes
>>  /usr/local/sbin/opensips[215172]: TOTAL: 48 overhead
>>  /usr/local/sbin/opensips[215174]: hash =  16 fragments no.:    61,
>> unused:     0#012#011#011 bucket size:       128 -       128 (first
>> 128)
>>  /usr/local/sbin/opensips[215172]: -----------------------------
>>  /usr/local/sbin/opensips[215174]: hash =  31 fragments no.:   152,
>> unused:     0#012#011#011 bucket size:       248 -       248 (first
>> 248)
>>  /usr/local/sbin/opensips[215174]: hash =  68 fragments no.:    16,
>> unused:     0#012#011#011 bucket size:       544 -       544 (first
>> 544)
>>  /usr/local/sbin/opensips[215174]: hash = 105 fragments no.:     1,
>> unused:     0#012#011#011 bucket size:       840 -       840 (first
>> 840)
>>  /usr/local/sbin/opensips[215174]: hash = 2059 fragments no.:     1,
>> unused:     0#012#011#011 bucket size:  16777216 -  33554432 (first
>>  33168816)
>>  /usr/local/sbin/opensips[215174]: TOTAL:    407 free fragments =
>> 33235496 free bytes
>>  /usr/local/sbin/opensips[215174]: TOTAL: 48 overhead
>>  /usr/local/sbin/opensips[215174]: -----------------------------
>>  /usr/local/sbin/opensips[215176]: Memory status (pkg):
>>  /usr/local/sbin/opensips[215176]: fm_status (0x7fc2907ff010):
>>  /usr/local/sbin/opensips[215176]: heap size= 33554432
>>  /usr/local/sbin/opensips[215176]: used= 3705480, used+overhead=3796584,
>> free=29848952
>>  /usr/local/sbin/opensips[215176]: max used (+overhead)= 3798064
>>  /usr/local/sbin/opensips[215176]: dumping free list:
>>  /usr/local/sbin/opensips[215176]: hash =   2 fragments no.:     2,
>> unused:     0#012#011#011 bucket size:        16 -        16 (first
>>  16)
>>  /usr/local/sbin/opensips[215176]: hash =   3 fragments no.:     1,
>> unused:     0#012#011#011 bucket size:        24 -        24 (first
>>  24)
>>  /usr/local/sbin/opensips[215176]: hash =  16 fragments no.:     1,
>> unused:     0#012#011#011 bucket size:       128 -       128 (first
>> 128)
>>  /usr/local/sbin/opensips[215175]: Memory status (pkg):
>>  /usr/local/sbin/opensips[215175]: fm_status (0x7fc2907ff010):
>>  /usr/local/sbin/opensips[215175]: heap size= 33554432
>>  /usr/local/sbin/opensips[215176]: hash = 2059 fragments no.:     1,
>> unused:     0#012#011#011 bucket size:  16777216 -  33554432 (first
>>  29757664)
>>  /usr/local/sbin/opensips[215175]: used= 3705480, used+overhead=3796584,
>> free=29848952
>>  /usr/local/sbin/opensips[215176]: TOTAL:      5 free fragments =
>> 29757848 free bytes
>>  /usr/local/sbin/opensips[215175]: max used (+overhead)= 3798064
>>  /usr/local/sbin/opensips[215176]: TOTAL: 48 overhead
>>  /usr/local/sbin/opensips[215176]: -----------------------------
>>  /usr/local/sbin/opensips[215175]: dumping free list:
>>  /usr/local/sbin/opensips[215175]: hash =   2 fragments no.:     2,
>> unused:     0#012#011#011 bucket size:        16 -        16 (first
>>  16)
>>  /usr/local/sbin/opensips[215175]: hash =   3 fragments no.:     1,
>> unused:     0#012#011#011 bucket size:        24 -        24 (first
>>  24)
>>  /usr/local/sbin/opensips[215175]: hash =  16 fragments no.:     1,
>> unused:     0#012#011#011 bucket size:       128 -       128 (first
>> 128)
>>  /usr/local/sbin/opensips[215175]: hash = 2059 fragments no.:     1,
>> unused:     0#012#011#011 bucket size:  16777216 -  33554432 (first
>>  29757664)
>>  /usr/local/sbin/opensips[215175]: TOTAL:      5 free fragments =
>> 29757848 free bytes
>>  /usr/local/sbin/opensips[215175]: TOTAL: 48 overhead
>>  /usr/local/sbin/opensips[215175]: -----------------------------
>>  /usr/local/sbin/opensips[215171]: INFO:core:shutdown_opensips: process
>> 3(215174) [timer] terminated, still waiting for 13 more
>>  /usr/local/sbin/opensips[215171]: INFO:core:shutdown_opensips: process
>> 4(215175) [SIP receiver udp:192.168.33.171:5060] terminated, still
>> waiting for 12 more
>>  /usr/local/sbin/opensips[215171]: INFO:core:shutdown_opensips: process
>> 5(215176) [SIP receiver udp:192.168.33.171:5060] terminated, still
>> waiting for 11 more
>>  /usr/local/sbin/opensips[215171]: INFO:core:shutdown_opensips: process
>> 1(215172) [MI FIFO] terminated, still waiting for 10 more
>>  /usr/local/sbin/opensips[215173]: INFO:core:sig_usr: signal 15 received
>>  /usr/local/sbin/opensips[215173]: Memory status (pkg):
>>  /usr/local/sbin/opensips[215173]: fm_status (0x7fc2907ff010):
>>  /usr/local/sbin/opensips[215173]: heap size= 33554432
>>  /usr/local/sbin/opensips[215173]: used= 229752, used+overhead=318936,
>> free=33324680
>>  /usr/local/sbin/opensips[215173]: max used (+overhead)= 385792
>>  /usr/local/sbin/opensips[215173]: dumping free list:
>>  /usr/local/sbin/opensips[215173]: hash =   7 fragments no.:   139,
>> unused:     0#012#011#011 bucket size:        56 -        56 (first
>>  56)
>>  /usr/local/sbin/opensips[215173]: hash =  13 fragments no.:    37,
>> unused:     0#012#011#011 bucket size:       104 -       104 (first
>> 104)
>>  /usr/local/sbin/opensips[215173]: hash =  16 fragments no.:    61,
>> unused:     0#012#011#011 bucket size:       128 -       128 (first
>> 128)
>>  /usr/local/sbin/opensips[215173]: hash =  31 fragments no.:   152,
>> unused:     0#012#011#011 bucket size:       248 -       248 (first
>> 248)
>>  /usr/local/sbin/opensips[215173]: hash =  68 fragments no.:    16,
>> unused:     0#012#011#011 bucket size:       544 -       544 (first
>> 544)
>>  /usr/local/sbin/opensips[215173]: hash = 105 fragments no.:     1,
>> unused:     0#012#011#011 bucket size:       840 -       840 (first
>> 840)
>>  /usr/local/sbin/opensips[215173]: hash = 2059 fragments no.:     1,
>> unused:     0#012#011#011 bucket size:  16777216 -  33554432 (first
>>  33168816)
>>  /usr/local/sbin/opensips[215173]: TOTAL:    407 free fragments =
>> 33235496 free bytes
>>  /usr/local/sbin/opensips[215173]: TOTAL: 48 overhead
>>  /usr/local/sbin/opensips[215173]: -----------------------------
>>  /usr/local/sbin/opensips[215171]: INFO:core:shutdown_opensips: process
>> 2(215173) [time_keeper] terminated, still waiting for 9 more
>>  /usr/local/sbin/opensips[215171]: INFO:core:cleanup: cleanup
>>  /usr/local/sbin/opensips[215171]: CRITICAL:core:sig_alarm_abort: BUG -
>> shutdown timeout triggered, dying...
>>
>> *Why is the service crashing ? *
>>
>> *Thanks & Regards*
>> *Sasmita Panda*
>> *Senior Network Testing and Software Engineer*
>> *3CLogic , ph:07827611765*
>>
>>
>> On Mon, Mar 11, 2024 at 11:52 AM Sasmita Panda <spanda at 3clogic.com>
>> wrote:
>>
>>> Hi All ,
>>>
>>> Mar 11 05:57:02 ip-192-168-33-171 /usr/local/sbin/opensips[213843]:
>>> INFO:proto_ws:mod_init: initializing WebSocket protocol
>>> Mar 11 05:57:03 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
>>> WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 100
>>> ms ago (now 290 ms), delaying execution
>>> Mar 11 05:57:03 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
>>> WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 200
>>> ms ago (now 390 ms), delaying execution
>>> Mar 11 05:57:03 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
>>> WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 300
>>> ms ago (now 490 ms), delaying execution
>>> Mar 11 05:57:03 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
>>> WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 400
>>> ms ago (now 590 ms), delaying execution
>>> Mar 11 05:57:03 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
>>> WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 500
>>> ms ago (now 690 ms), delaying execution
>>> Mar 11 05:57:03 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
>>> WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 600
>>> ms ago (now 790 ms), delaying execution
>>> Mar 11 05:57:03 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
>>> WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 700
>>> ms ago (now 890 ms), delaying execution
>>> Mar 11 05:57:03 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
>>> WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 800
>>> ms ago (now 990 ms), delaying execution
>>> Mar 11 05:57:03 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
>>> WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 900
>>> ms ago (now 1090 ms), delaying execution
>>> Mar 11 05:57:03 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
>>> WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 1000
>>> ms ago (now 1190 ms), delaying execution
>>> Mar 11 05:57:04 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
>>> WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 1100
>>> ms ago (now 1290 ms), delaying execution
>>> Mar 11 05:57:04 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
>>> WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 1200
>>> ms ago (now 1390 ms), delaying execution
>>> Mar 11 05:57:04 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
>>> WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 1300
>>> ms ago (now 1490 ms), delaying execution
>>> Mar 11 05:57:04 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
>>> WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 1400
>>> ms ago (now 1590 ms), delaying execution
>>> Mar 11 05:57:04 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
>>> WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 1500
>>> ms ago (now 1690 ms), delaying execution
>>> Mar 11 05:57:04 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
>>> WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 1600
>>> ms ago (now 1790 ms), delaying execution
>>> Mar 11 05:57:04 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
>>> WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 1700
>>> ms ago (now 1890 ms), delaying execution
>>> Mar 11 05:57:04 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
>>> WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled 1790
>>> ms ago (now 1980 ms), delaying execution
>>> Mar 11 05:57:04 ip-192-168-33-171 /usr/local/sbin/opensips[213846]:
>>> WARNING:core:timer_ticker: timer task <tm-timer> already scheduled 990 ms
>>> ago (now 1980 ms), delaying execution
>>>
>>> *What is this warning for? Whenever I am starting my openisps service
>>> this warning comes . Although the service seems like it's running but it's
>>> not listening on the socket exposed .  How to resolve this ?*
>>>
>>> */usr/local/sbin/opensips  -V*
>>> version: opensips 3.2.3 (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.
>>> svn revision: 3831:3878
>>> main.c compiled on 07:52:40 Mar 29 2023 with gcc 11
>>>
>>> *cat /etc/*release*
>>> Amazon Linux release 2023 (Amazon Linux)
>>> NAME="Amazon Linux"
>>> VERSION="2023"
>>> ID="amzn"
>>> ID_LIKE="fedora"
>>> VERSION_ID="2023"
>>> PLATFORM_ID="platform:al2023"
>>> PRETTY_NAME="Amazon Linux 2023"
>>> ANSI_COLOR="0;33"
>>> CPE_NAME="cpe:2.3:o:amazon:amazon_linux:2023"
>>> HOME_URL="https://aws.amazon.com/linux/"
>>> BUG_REPORT_URL="https://github.com/amazonlinux/amazon-linux-2023"
>>> SUPPORT_END="2028-03-01"
>>> Amazon Linux release 2023 (Amazon Linux)
>>>
>>>
>>> *Thanks & Regards*
>>> *Sasmita Panda*
>>> *Senior Network Testing and Software Engineer*
>>> *3CLogic , ph:07827611765*
>>>
>>
> _______________________________________________
> Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240321/7d869966/attachment-0001.html>

From bogdan at opensips.org  Thu Mar 21 16:31:24 2024
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Thu, 21 Mar 2024 18:31:24 +0200
Subject: [OpenSIPS-Users] utimer_ticker warning in opensips 3.2
In-Reply-To: <CALf-Q46ceCOvwVf8gNKcdbkAaD99+k-rESkdGAoSrCno+jMf2w@mail.gmail.com>
References: <CALf-Q442AqxhLDxKt6_psUWUzcC1aGfZ9CrHvYXH_BU5GFGL2w@mail.gmail.com>
 <CALf-Q45dJ=hVdJPxsB7dU1PhER4VYBnHSU+3Jn9RwrvnZ1a=Hg@mail.gmail.com>
 <CALf-Q45xVfjagrctOVtAqEkEhPzeVNWK9Zj7Kfh4_Xow1QjOUQ@mail.gmail.com>
 <2e986980-6548-4cd8-b1e5-cbbc65f60fe3@opensips.org>
 <CALf-Q46ceCOvwVf8gNKcdbkAaD99+k-rESkdGAoSrCno+jMf2w@mail.gmail.com>
Message-ID: <d3ed4465-f669-4517-a4c0-32347ea696da@opensips.org>

IF

(a) it crashes, try to get a backtrace

(b) it block on starting, try to do a "trap" via opensips-cli

Regards,

Bogdan-Andrei Iancu

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

On 21.03.2024 08:24, Sasmita Panda wrote:
> Sometimes it crashes and sometimes while starting I get the warings of 
> the timer .  Same config  shows different issues .
>
>
>
> */Thanks & Regards/*
> /Sasmita Panda/
> /Senior Network Testing and Software Engineer/
> /3CLogic , ph:07827611765/
>
>
> On Wed, Mar 20, 2024 at 6:45 PM Bogdan-Andrei Iancu 
> <bogdan at opensips.org> wrote:
>
>     Hi,
>
>     How the two reports fit together here ? there are completely
>     separate experiences on different runs?? or if you start opensips
>     first you get the warnings and later it crashes ??
>     For the crash part, I see a core file was generated - could you
>     extract the backtrace and post here ? (see
>     https://opensips.org/Documentation/TroubleShooting-Crash)
>
>     Regards
>
>     Bogdan-Andrei Iancu
>
>     OpenSIPS Founder and Developer
>        https://www.opensips-solutions.com
>        https://www.siphub.com
>
>     On 11.03.2024 15:04, Sasmita Panda wrote:
>>     Any update on this ?
>>
>>
>>     */Thanks & Regards/*
>>     /Sasmita Panda/
>>     /Senior Network Testing and Software Engineer/
>>     /3CLogic , ph:07827611765/
>>
>>
>>     On Mon, Mar 11, 2024 at 12:03 PM Sasmita Panda
>>     <spanda at 3clogic.com> wrote:
>>
>>         With the same server configuration and opensips version I am
>>         getting below error as well .
>>
>>         CRITICAL:core:fm_free: freeing already freed shm pointer
>>         (0x7fc110e0b408), first free: (null): (null)(0) - aborting!
>>
>>          /usr/local/sbin/opensips[215171]: INFO:core:handle_sigs:
>>         child process 215185 exited by a signal 6
>>          /usr/local/sbin/opensips[215171]: INFO:core:handle_sigs:
>>         core was generated
>>          /usr/local/sbin/opensips[215171]: INFO:core:handle_sigs:
>>         terminating due to SIGCHLD
>>          /usr/local/sbin/opensips[215172]: Memory status (pkg):
>>          /usr/local/sbin/opensips[215172]: fm_status (0x7fc2907ff010):
>>          /usr/local/sbin/opensips[215174]: INFO:core:sig_usr: signal
>>         15 received
>>          /usr/local/sbin/opensips[215172]: heap size= 33554432
>>          /usr/local/sbin/opensips[215174]: Memory status (pkg):
>>          /usr/local/sbin/opensips[215172]: used= 3710048,
>>         used+overhead=3801344, free=29844384
>>          /usr/local/sbin/opensips[215174]: fm_status (0x7fc2907ff010):
>>          /usr/local/sbin/opensips[215172]: max used (+overhead)= 3801344
>>          /usr/local/sbin/opensips[215174]: heap size= 33554432
>>          /usr/local/sbin/opensips[215172]: dumping free list:
>>          /usr/local/sbin/opensips[215174]: used= 229752,
>>         used+overhead=318936, free=33324680
>>          /usr/local/sbin/opensips[215172]: hash =   1 fragments no.:
>>             1, unused:     0#012#011#011 bucket size:         8 -    
>>             8 (first 8)
>>          /usr/local/sbin/opensips[215174]: max used (+overhead)= 385792
>>          /usr/local/sbin/opensips[215174]: dumping free list:
>>          /usr/local/sbin/opensips[215172]: hash =  18 fragments no.:
>>             1, unused:     0#012#011#011 bucket size:       144 -    
>>           144 (first 144)
>>          /usr/local/sbin/opensips[215174]: hash =   7 fragments no.:
>>           139, unused:     0#012#011#011 bucket size:        56 -    
>>            56 (first  56)
>>          /usr/local/sbin/opensips[215172]: hash = 2059 fragments no.:
>>             1, unused:     0#012#011#011 bucket size:  16777216 -
>>          33554432 (first  29752936)
>>          /usr/local/sbin/opensips[215174]: hash =  13 fragments no.:
>>            37, unused:     0#012#011#011 bucket size:       104 -    
>>           104 (first 104)
>>          /usr/local/sbin/opensips[215172]: TOTAL:      3 free
>>         fragments = 29753088 free bytes
>>          /usr/local/sbin/opensips[215172]: TOTAL: 48 overhead
>>          /usr/local/sbin/opensips[215174]: hash =  16 fragments no.:
>>            61, unused:     0#012#011#011 bucket size:       128 -    
>>           128 (first 128)
>>          /usr/local/sbin/opensips[215172]: -----------------------------
>>          /usr/local/sbin/opensips[215174]: hash =  31 fragments no.:
>>           152, unused:     0#012#011#011 bucket size:       248 -    
>>           248 (first 248)
>>          /usr/local/sbin/opensips[215174]: hash =  68 fragments no.:
>>            16, unused:     0#012#011#011 bucket size:       544 -    
>>           544 (first 544)
>>          /usr/local/sbin/opensips[215174]: hash = 105 fragments no.:
>>             1, unused:     0#012#011#011 bucket size:       840 -    
>>           840 (first 840)
>>          /usr/local/sbin/opensips[215174]: hash = 2059 fragments no.:
>>             1, unused:     0#012#011#011 bucket size:  16777216 -
>>          33554432 (first  33168816)
>>          /usr/local/sbin/opensips[215174]: TOTAL:    407 free
>>         fragments = 33235496 free bytes
>>          /usr/local/sbin/opensips[215174]: TOTAL: 48 overhead
>>          /usr/local/sbin/opensips[215174]: -----------------------------
>>          /usr/local/sbin/opensips[215176]: Memory status (pkg):
>>          /usr/local/sbin/opensips[215176]: fm_status (0x7fc2907ff010):
>>          /usr/local/sbin/opensips[215176]: heap size= 33554432
>>          /usr/local/sbin/opensips[215176]: used= 3705480,
>>         used+overhead=3796584, free=29848952
>>          /usr/local/sbin/opensips[215176]: max used (+overhead)= 3798064
>>          /usr/local/sbin/opensips[215176]: dumping free list:
>>          /usr/local/sbin/opensips[215176]: hash =   2 fragments no.:
>>             2, unused:     0#012#011#011 bucket size:        16 -    
>>            16 (first  16)
>>          /usr/local/sbin/opensips[215176]: hash =   3 fragments no.:
>>             1, unused:     0#012#011#011 bucket size:        24 -    
>>            24 (first  24)
>>          /usr/local/sbin/opensips[215176]: hash =  16 fragments no.:
>>             1, unused:     0#012#011#011 bucket size:       128 -    
>>           128 (first 128)
>>          /usr/local/sbin/opensips[215175]: Memory status (pkg):
>>          /usr/local/sbin/opensips[215175]: fm_status (0x7fc2907ff010):
>>          /usr/local/sbin/opensips[215175]: heap size= 33554432
>>          /usr/local/sbin/opensips[215176]: hash = 2059 fragments no.:
>>             1, unused:     0#012#011#011 bucket size:  16777216 -
>>          33554432 (first  29757664)
>>          /usr/local/sbin/opensips[215175]: used= 3705480,
>>         used+overhead=3796584, free=29848952
>>          /usr/local/sbin/opensips[215176]: TOTAL:      5 free
>>         fragments = 29757848 free bytes
>>          /usr/local/sbin/opensips[215175]: max used (+overhead)= 3798064
>>          /usr/local/sbin/opensips[215176]: TOTAL: 48 overhead
>>          /usr/local/sbin/opensips[215176]: -----------------------------
>>          /usr/local/sbin/opensips[215175]: dumping free list:
>>          /usr/local/sbin/opensips[215175]: hash =   2 fragments no.:
>>             2, unused:     0#012#011#011 bucket size:        16 -    
>>            16 (first  16)
>>          /usr/local/sbin/opensips[215175]: hash =   3 fragments no.:
>>             1, unused:     0#012#011#011 bucket size:        24 -    
>>            24 (first  24)
>>          /usr/local/sbin/opensips[215175]: hash =  16 fragments no.:
>>             1, unused:     0#012#011#011 bucket size:       128 -    
>>           128 (first 128)
>>          /usr/local/sbin/opensips[215175]: hash = 2059 fragments no.:
>>             1, unused:     0#012#011#011 bucket size:  16777216 -
>>          33554432 (first  29757664)
>>          /usr/local/sbin/opensips[215175]: TOTAL:      5 free
>>         fragments = 29757848 free bytes
>>          /usr/local/sbin/opensips[215175]: TOTAL: 48 overhead
>>          /usr/local/sbin/opensips[215175]: -----------------------------
>>          /usr/local/sbin/opensips[215171]:
>>         INFO:core:shutdown_opensips: process 3(215174) [timer]
>>         terminated, still waiting for 13 more
>>          /usr/local/sbin/opensips[215171]:
>>         INFO:core:shutdown_opensips: process 4(215175) [SIP receiver
>>         udp:192.168.33.171:5060 <http://192.168.33.171:5060>]
>>         terminated, still waiting for 12 more
>>          /usr/local/sbin/opensips[215171]:
>>         INFO:core:shutdown_opensips: process 5(215176) [SIP receiver
>>         udp:192.168.33.171:5060 <http://192.168.33.171:5060>]
>>         terminated, still waiting for 11 more
>>          /usr/local/sbin/opensips[215171]:
>>         INFO:core:shutdown_opensips: process 1(215172) [MI FIFO]
>>         terminated, still waiting for 10 more
>>          /usr/local/sbin/opensips[215173]: INFO:core:sig_usr: signal
>>         15 received
>>          /usr/local/sbin/opensips[215173]: Memory status (pkg):
>>          /usr/local/sbin/opensips[215173]: fm_status (0x7fc2907ff010):
>>          /usr/local/sbin/opensips[215173]: heap size= 33554432
>>          /usr/local/sbin/opensips[215173]: used= 229752,
>>         used+overhead=318936, free=33324680
>>          /usr/local/sbin/opensips[215173]: max used (+overhead)= 385792
>>          /usr/local/sbin/opensips[215173]: dumping free list:
>>          /usr/local/sbin/opensips[215173]: hash =   7 fragments no.:
>>           139, unused:     0#012#011#011 bucket size:        56 -    
>>            56 (first  56)
>>          /usr/local/sbin/opensips[215173]: hash =  13 fragments no.:
>>            37, unused:     0#012#011#011 bucket size:       104 -    
>>           104 (first 104)
>>          /usr/local/sbin/opensips[215173]: hash =  16 fragments no.:
>>            61, unused:     0#012#011#011 bucket size:       128 -    
>>           128 (first 128)
>>          /usr/local/sbin/opensips[215173]: hash =  31 fragments no.:
>>           152, unused:     0#012#011#011 bucket size:       248 -    
>>           248 (first 248)
>>          /usr/local/sbin/opensips[215173]: hash =  68 fragments no.:
>>            16, unused:     0#012#011#011 bucket size:       544 -    
>>           544 (first 544)
>>          /usr/local/sbin/opensips[215173]: hash = 105 fragments no.:
>>             1, unused:     0#012#011#011 bucket size:       840 -    
>>           840 (first 840)
>>          /usr/local/sbin/opensips[215173]: hash = 2059 fragments no.:
>>             1, unused:     0#012#011#011 bucket size:  16777216 -
>>          33554432 (first  33168816)
>>          /usr/local/sbin/opensips[215173]: TOTAL:    407 free
>>         fragments = 33235496 free bytes
>>          /usr/local/sbin/opensips[215173]: TOTAL: 48 overhead
>>          /usr/local/sbin/opensips[215173]: -----------------------------
>>          /usr/local/sbin/opensips[215171]:
>>         INFO:core:shutdown_opensips: process 2(215173) [time_keeper]
>>         terminated, still waiting for 9 more
>>          /usr/local/sbin/opensips[215171]: INFO:core:cleanup: cleanup
>>          /usr/local/sbin/opensips[215171]:
>>         CRITICAL:core:sig_alarm_abort: BUG - shutdown timeout
>>         triggered, dying...
>>         */
>>         /*
>>         */Why is the service crashing ? /*
>>         */
>>         /*
>>         */Thanks & Regards/*
>>         /Sasmita Panda/
>>         /Senior Network Testing and Software Engineer/
>>         /3CLogic , ph:07827611765/
>>
>>
>>         On Mon, Mar 11, 2024 at 11:52 AM Sasmita Panda
>>         <spanda at 3clogic.com> wrote:
>>
>>             Hi All ,
>>
>>             Mar 11 05:57:02 ip-192-168-33-171
>>             /usr/local/sbin/opensips[213843]: INFO:proto_ws:mod_init:
>>             initializing WebSocket protocol
>>             Mar 11 05:57:03 ip-192-168-33-171
>>             /usr/local/sbin/opensips[213846]:
>>             WARNING:core:utimer_ticker: utimer task <tm-utimer>
>>             already scheduled 100 ms ago (now 290 ms), delaying execution
>>             Mar 11 05:57:03 ip-192-168-33-171
>>             /usr/local/sbin/opensips[213846]:
>>             WARNING:core:utimer_ticker: utimer task <tm-utimer>
>>             already scheduled 200 ms ago (now 390 ms), delaying execution
>>             Mar 11 05:57:03 ip-192-168-33-171
>>             /usr/local/sbin/opensips[213846]:
>>             WARNING:core:utimer_ticker: utimer task <tm-utimer>
>>             already scheduled 300 ms ago (now 490 ms), delaying execution
>>             Mar 11 05:57:03 ip-192-168-33-171
>>             /usr/local/sbin/opensips[213846]:
>>             WARNING:core:utimer_ticker: utimer task <tm-utimer>
>>             already scheduled 400 ms ago (now 590 ms), delaying execution
>>             Mar 11 05:57:03 ip-192-168-33-171
>>             /usr/local/sbin/opensips[213846]:
>>             WARNING:core:utimer_ticker: utimer task <tm-utimer>
>>             already scheduled 500 ms ago (now 690 ms), delaying execution
>>             Mar 11 05:57:03 ip-192-168-33-171
>>             /usr/local/sbin/opensips[213846]:
>>             WARNING:core:utimer_ticker: utimer task <tm-utimer>
>>             already scheduled 600 ms ago (now 790 ms), delaying execution
>>             Mar 11 05:57:03 ip-192-168-33-171
>>             /usr/local/sbin/opensips[213846]:
>>             WARNING:core:utimer_ticker: utimer task <tm-utimer>
>>             already scheduled 700 ms ago (now 890 ms), delaying execution
>>             Mar 11 05:57:03 ip-192-168-33-171
>>             /usr/local/sbin/opensips[213846]:
>>             WARNING:core:utimer_ticker: utimer task <tm-utimer>
>>             already scheduled 800 ms ago (now 990 ms), delaying execution
>>             Mar 11 05:57:03 ip-192-168-33-171
>>             /usr/local/sbin/opensips[213846]:
>>             WARNING:core:utimer_ticker: utimer task <tm-utimer>
>>             already scheduled 900 ms ago (now 1090 ms), delaying
>>             execution
>>             Mar 11 05:57:03 ip-192-168-33-171
>>             /usr/local/sbin/opensips[213846]:
>>             WARNING:core:utimer_ticker: utimer task <tm-utimer>
>>             already scheduled 1000 ms ago (now 1190 ms), delaying
>>             execution
>>             Mar 11 05:57:04 ip-192-168-33-171
>>             /usr/local/sbin/opensips[213846]:
>>             WARNING:core:utimer_ticker: utimer task <tm-utimer>
>>             already scheduled 1100 ms ago (now 1290 ms), delaying
>>             execution
>>             Mar 11 05:57:04 ip-192-168-33-171
>>             /usr/local/sbin/opensips[213846]:
>>             WARNING:core:utimer_ticker: utimer task <tm-utimer>
>>             already scheduled 1200 ms ago (now 1390 ms), delaying
>>             execution
>>             Mar 11 05:57:04 ip-192-168-33-171
>>             /usr/local/sbin/opensips[213846]:
>>             WARNING:core:utimer_ticker: utimer task <tm-utimer>
>>             already scheduled 1300 ms ago (now 1490 ms), delaying
>>             execution
>>             Mar 11 05:57:04 ip-192-168-33-171
>>             /usr/local/sbin/opensips[213846]:
>>             WARNING:core:utimer_ticker: utimer task <tm-utimer>
>>             already scheduled 1400 ms ago (now 1590 ms), delaying
>>             execution
>>             Mar 11 05:57:04 ip-192-168-33-171
>>             /usr/local/sbin/opensips[213846]:
>>             WARNING:core:utimer_ticker: utimer task <tm-utimer>
>>             already scheduled 1500 ms ago (now 1690 ms), delaying
>>             execution
>>             Mar 11 05:57:04 ip-192-168-33-171
>>             /usr/local/sbin/opensips[213846]:
>>             WARNING:core:utimer_ticker: utimer task <tm-utimer>
>>             already scheduled 1600 ms ago (now 1790 ms), delaying
>>             execution
>>             Mar 11 05:57:04 ip-192-168-33-171
>>             /usr/local/sbin/opensips[213846]:
>>             WARNING:core:utimer_ticker: utimer task <tm-utimer>
>>             already scheduled 1700 ms ago (now 1890 ms), delaying
>>             execution
>>             Mar 11 05:57:04 ip-192-168-33-171
>>             /usr/local/sbin/opensips[213846]:
>>             WARNING:core:utimer_ticker: utimer task <tm-utimer>
>>             already scheduled 1790 ms ago (now 1980 ms), delaying
>>             execution
>>             Mar 11 05:57:04 ip-192-168-33-171
>>             /usr/local/sbin/opensips[213846]:
>>             WARNING:core:timer_ticker: timer task <tm-timer> already
>>             scheduled 990 ms ago (now 1980 ms), delaying execution
>>             */
>>             /*
>>             */What is this warning for? Whenever I am starting my
>>             openisps service this warning comes . Although the
>>             service seems like it's running but it's not listening on
>>             the socket exposed .  How to resolve this ?/*
>>             */
>>             /*
>>             */usr/local/sbin/opensips  -V*
>>             version: opensips 3.2.3 (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.
>>             svn revision: 3831:3878
>>             main.c compiled on 07:52:40 Mar 29 2023 with gcc 11
>>
>>             *cat /etc/*release*
>>             Amazon Linux release 2023 (Amazon Linux)
>>             NAME="Amazon Linux"
>>             VERSION="2023"
>>             ID="amzn"
>>             ID_LIKE="fedora"
>>             VERSION_ID="2023"
>>             PLATFORM_ID="platform:al2023"
>>             PRETTY_NAME="Amazon Linux 2023"
>>             ANSI_COLOR="0;33"
>>             CPE_NAME="cpe:2.3:o:amazon:amazon_linux:2023"
>>             HOME_URL="https://aws.amazon.com/linux/"
>>             BUG_REPORT_URL="https://github.com/amazonlinux/amazon-linux-2023"
>>             SUPPORT_END="2028-03-01"
>>             Amazon Linux release 2023 (Amazon Linux)
>>             */
>>             /*
>>             */
>>             /*
>>             */Thanks & Regards/*
>>             /Sasmita Panda/
>>             /Senior Network Testing and Software Engineer/
>>             /3CLogic , ph:07827611765/
>>
>>
>>     _______________________________________________
>>     Users mailing list
>>     Users at lists.opensips.org
>>     http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240321/c174f065/attachment-0001.html>

From prathibhab.tvm at gmail.com  Sat Mar 23 10:09:11 2024
From: prathibhab.tvm at gmail.com (Prathibha B)
Date: Sat, 23 Mar 2024 15:39:11 +0530
Subject: [OpenSIPS-Users] variables not working as expected
Message-ID: <CAJh_-cAw8+x6CtQ0583Nt1=+R-JY__2pJnbSAtYta8D-=m1Y3Q@mail.gmail.com>

 if ( !create_dialog("B") ) {
            send_reply(500,"Internal Server Error");
            exit;
        }
        else
            dlg_on_answer("dlg_answered");


route[dlg_answered] {
        $var(payload) = "{'type':'ANSWERED', 'from':" + $fU +", 'to':" +
$tU+ "}";
}
*Result:*
{'type':'ANSWERED', 'from':*from*, 'to'*:to*}

$fU - from URI
$tU - to URI

-- 
Regards,
B.Prathibha
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240323/83f4b5df/attachment.html>

From prathibhab.tvm at gmail.com  Sat Mar 23 10:50:07 2024
From: prathibhab.tvm at gmail.com (Prathibha B)
Date: Sat, 23 Mar 2024 16:20:07 +0530
Subject: [OpenSIPS-Users] variables not working as expected
In-Reply-To: <CAJh_-cAw8+x6CtQ0583Nt1=+R-JY__2pJnbSAtYta8D-=m1Y3Q@mail.gmail.com>
References: <CAJh_-cAw8+x6CtQ0583Nt1=+R-JY__2pJnbSAtYta8D-=m1Y3Q@mail.gmail.com>
Message-ID: <CAJh_-cDXscuX6U2B6Ac5LZJh+MCQzNiRTk_CqUSZmT4Ah9+Qmg@mail.gmail.com>

unable to access the script variable in the route block

On Sat, 23 Mar 2024 at 15:39, Prathibha B <prathibhab.tvm at gmail.com> wrote:

>  if ( !create_dialog("B") ) {
>             send_reply(500,"Internal Server Error");
>             exit;
>         }
>         else
>             dlg_on_answer("dlg_answered");
>
>
> route[dlg_answered] {
>         $var(payload) = "{'type':'ANSWERED', 'from':" + $fU +", 'to':" +
> $tU+ "}";
> }
> *Result:*
> {'type':'ANSWERED', 'from':*from*, 'to'*:to*}
>
> $fU - from URI
> $tU - to URI
>
> --
> Regards,
> B.Prathibha
>


-- 
Regards,
B.Prathibha
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240323/da40f1b1/attachment.html>

From stefan.carlsson at tetab.nu  Sat Mar 23 11:36:40 2024
From: stefan.carlsson at tetab.nu (Stefan Carlsson)
Date: Sat, 23 Mar 2024 11:36:40 +0000
Subject: [OpenSIPS-Users] variables not working as expected
In-Reply-To: <CAJh_-cDXscuX6U2B6Ac5LZJh+MCQzNiRTk_CqUSZmT4Ah9+Qmg@mail.gmail.com>
References: <CAJh_-cAw8+x6CtQ0583Nt1=+R-JY__2pJnbSAtYta8D-=m1Y3Q@mail.gmail.com>,
 <CAJh_-cDXscuX6U2B6Ac5LZJh+MCQzNiRTk_CqUSZmT4Ah9+Qmg@mail.gmail.com>
Message-ID: <85d67460-e028-4040-968e-c8e7b1ccbf0a@tetab.nu>


Tip,

If you want to use vars in the dialog, use $dlg_var()

Those are valid from create_dlg()  to the last BYE
but dont forget to use loose_route() or match_dialog()
before refering to them again...

(Note: They are vslud  in all the in-dialog messages such as re-invite )

Tip 2 ... Buy the book

https://www.oreilly.com/library/view/building-telephony-systems/9781785280610/

Excellent

 Regards_
Stefan


________________________________
From: Prathibha B <prathibhab.tvm at gmail.com>
Sent: Saturday, 23 March 2024 12:26
To: OpenSIPS users mailling list
Subject: Re: [OpenSIPS-Users] variables not working as expected

unable to access the script variable in the route block

On Sat, 23 Mar 2024 at 15:39, Prathibha B <prathibhab.tvm at gmail.com<mailto:prathibhab.tvm at gmail.com>> wrote:
 if ( !create_dialog("B") ) {
            send_reply(500,"Internal Server Error");
            exit;
        }
        else
            dlg_on_answer("dlg_answered");


route[dlg_answered] {
        $var(payload) = "{'type':'ANSWERED', 'from':" + $fU +", 'to':" + $tU+ "}";
}
Result:
{'type':'ANSWERED', 'from':from, 'to':to}

$fU - from URI
$tU - to URI

--
Regards,
B.Prathibha


--
Regards,
B.Prathibha
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240323/c0d09b59/attachment.html>

From prathibhab.tvm at gmail.com  Sun Mar 24 09:43:43 2024
From: prathibhab.tvm at gmail.com (Prathibha B)
Date: Sun, 24 Mar 2024 15:13:43 +0530
Subject: [OpenSIPS-Users] Reg media server
Message-ID: <CAJh_-cCSabYxerZwVL7B8RxSnYEZxM6LELOv1yLXa54BQWS1uA@mail.gmail.com>

Is it madatorily required to use a media server such as rtpengine. I'm
using coturn server as the TURN server for media relay. I'm getting the
media through coturn server. Still rtpengine is required?


-- 
Regards,
B.Prathibha
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240324/a594d55a/attachment.html>

From abalashov at evaristesys.com  Sun Mar 24 16:38:24 2024
From: abalashov at evaristesys.com (Alex Balashov)
Date: Sun, 24 Mar 2024 12:38:24 -0400
Subject: [OpenSIPS-Users] Reg media server
In-Reply-To: <CAJh_-cCSabYxerZwVL7B8RxSnYEZxM6LELOv1yLXa54BQWS1uA@mail.gmail.com>
References: <CAJh_-cCSabYxerZwVL7B8RxSnYEZxM6LELOv1yLXa54BQWS1uA@mail.gmail.com>
Message-ID: <9AE0EF24-A76F-4FAF-82A9-23D41FB85884@evaristesys.com>

I wouldn't say that.

> On Mar 24, 2024, at 5:43 AM, Prathibha B <prathibhab.tvm at gmail.com> wrote:
> 
> Is it madatorily required to use a media server such as rtpengine. I'm using coturn server as the TURN server for media relay. I'm getting the media through coturn server. Still rtpengine is required?
> 
> 
> -- 
> Regards,
> B.Prathibha
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users

-- 
Alex Balashov
Principal Consultant
Evariste Systems LLC
Web: https://evaristesys.com
Tel: +1-706-510-6800



From liviu at opensips.org  Mon Mar 25 09:36:03 2024
From: liviu at opensips.org (Liviu Chircu)
Date: Mon, 25 Mar 2024 11:36:03 +0200
Subject: [OpenSIPS-Users] pn still problems
In-Reply-To: <a8d2f3e21c206d8e1506055671139205a3f189b0@rvgeerligs.nl>
References: <a8d2f3e21c206d8e1506055671139205a3f189b0@rvgeerligs.nl>
Message-ID: <c787fbd7-f044-4e0c-9a1f-f56bf974283f@opensips.org>

Hi rvg,

I took a look at the logs you provided and, indeed, your "rvg" AoR has 
exactly 1 contact registered, with flags value of "4" in the MI ul_dump, 
confirming that it is RFC 8599 PN enabled.  Now, regarding the INVITE 
looping, if you still have this issue, make sure to avoid t_relay() 
after the lookup, as discussed earlier.

Finally, if the call does not connect... that's because, logically 
speaking, there is *always* a need to generate a Push Notification on 
*every* call attempt.  While I do agree this might be a bit of overkill, 
it is the only way to cover all timing-related corner-cases (imagine 
this race condition: the phone registered 1.5 minutes ago or earlier, 
but the NAT pinhole only lasts for 1 minute, so by the time you call, it 
is unreachable).  So please make sure to get your *PN_SEND* route to 
actually do the work -- send the PN, wake up the app and get it to 
Re-REGISTER, which will cause OpenSIPS to /inject/ an INVITE over to it.

Alternatively, if you just want to play with the Push Notification 
support /without sending Push Notifications/... try to bump the 
registrar's pn_skip_pn_interval 
<https://opensips.org/docs/modules/3.5.x/registrar.html#param_pn_skip_pn_interval> 
setting to some ridiculous value like *600* seconds, causing the module 
to refrain from mandating any Push Notification to be sent in the first 
10 minutes following the app's REGISTER, as it delivers calls 
straight-through to the app.

Best regards,

Liviu Chircu
www.twitter.com/liviuchircu  |www.opensips-solutions.com
OpenSIPS Summit 2024 Valencia, May 14-17 |www.opensips.org/events

On 09.03.2024 15:46, rvg at rvgeerligs.nl wrote:
> I still have problems with opensips3.4 push notifications:
>
> Somehow INVITEs keep looping and get rejected.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240325/7b7fb6f5/attachment.html>

From bogdan at opensips.org  Tue Mar 26 15:49:25 2024
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Tue, 26 Mar 2024 17:49:25 +0200
Subject: [OpenSIPS-Users] If it's May, it's OpenSIPS Summit
Message-ID: <3b9d75b7-7e9f-4709-98b5-abe733f6e64b@opensips.org>


Spring is here and May is getting closer and closer - and we celebrate 
this OpenSIPS Summit vibe with the *summit-24-flash-sale* 50% discount 
code for all registrations between 28th 00:00 and 31th 23:59 GMT - we 
love March 🙂. This special offer is limited to 20 seats, so hurry up 😉!

https://www.opensips.org/events/Summit-2024Valencia/#pricing

See you in Valencia!

-- 
Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
   https://www.siphub.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240326/bf5158be/attachment.html>

From schu at schu.net  Tue Mar 26 21:17:01 2024
From: schu at schu.net (Matthew Schumacher)
Date: Tue, 26 Mar 2024 14:17:01 -0700
Subject: [OpenSIPS-Users] Getting the $rb or media port for egress message.
Message-ID: <fdff23b8-26d6-4f03-b560-654f840c6304@schu.net>

Hello,

I'm trying to log the media port for another system and using this code 
to grab the m line out of an SDP header:

   if (has_body("application/sdp")){
     rtpengine_offer();
     $var(mline) = $(rb{sdp.line,m,0});
     xlog("TEST $var(mline)\n");
   }

The problem is that it only sees the ports for ingress SDP messages and 
not egress SDP messages.  What can I do to grab the SDP messages leaving 
opensips?

I want to take this data and inject a firewall rule that allows the 
media and remove it later because NAT helpers don't work on TLS traffic, 
my system already knows what port to expect, and I don't like having a 
huge pile of UDP ports allowed through.

Honestly, I'm not sure why the kernel mode forwarding in rtpengine 
doesn't also allow traffic based on ports we are expecting to see 
traffic from.... that's what I thought it did at first until I realized 
that it's only forwarding the RTP packet through the kernel faster 
without needing userspace.

Thanks,
Matt


From eremina.net at gmail.com  Wed Mar 27 06:56:03 2024
From: eremina.net at gmail.com (Pavel Eremin)
Date: Wed, 27 Mar 2024 11:56:03 +0500
Subject: [OpenSIPS-Users] Getting the $rb or media port for egress
	message.
In-Reply-To: <fdff23b8-26d6-4f03-b560-654f840c6304@schu.net>
References: <fdff23b8-26d6-4f03-b560-654f840c6304@schu.net>
Message-ID: <CAF3UBt2+xiW=sP-nxyNTPwdwmzmsJvZZbLJg3YuJi=hB7Y5ygg@mail.gmail.com>

Hi, if I understand correctly, you have to get $rb from onreply_route.

ср, 27 мар. 2024 г. в 02:19, Matthew Schumacher <schu at schu.net>:
>
> Hello,
>
> I'm trying to log the media port for another system and using this code
> to grab the m line out of an SDP header:
>
>    if (has_body("application/sdp")){
>      rtpengine_offer();
>      $var(mline) = $(rb{sdp.line,m,0});
>      xlog("TEST $var(mline)\n");
>    }
>
> The problem is that it only sees the ports for ingress SDP messages and
> not egress SDP messages.  What can I do to grab the SDP messages leaving
> opensips?
>
> I want to take this data and inject a firewall rule that allows the
> media and remove it later because NAT helpers don't work on TLS traffic,
> my system already knows what port to expect, and I don't like having a
> huge pile of UDP ports allowed through.
>
> Honestly, I'm not sure why the kernel mode forwarding in rtpengine
> doesn't also allow traffic based on ports we are expecting to see
> traffic from.... that's what I thought it did at first until I realized
> that it's only forwarding the RTP packet through the kernel faster
> without needing userspace.
>
> Thanks,
> Matt
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users


From prathibhab.tvm at gmail.com  Wed Mar 27 11:40:15 2024
From: prathibhab.tvm at gmail.com (Prathibha B)
Date: Wed, 27 Mar 2024 17:10:15 +0530
Subject: [OpenSIPS-Users] $DLG_dir
Message-ID: <CAJh_-cCkEDKPxhJ7vyhZ=O2BXNkVigx9NOidnO9QNEyTkc7wsw@mail.gmail.com>

$DLG_dir returns null, when used in is_method("INVITE")


-- 
Regards,
B.Prathibha
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240327/577cf149/attachment.html>

From medeanwz at gmail.com  Wed Mar 27 11:53:24 2024
From: medeanwz at gmail.com (M S)
Date: Wed, 27 Mar 2024 12:53:24 +0100
Subject: [OpenSIPS-Users] $DLG_dir
In-Reply-To: <CAJh_-cCkEDKPxhJ7vyhZ=O2BXNkVigx9NOidnO9QNEyTkc7wsw@mail.gmail.com>
References: <CAJh_-cCkEDKPxhJ7vyhZ=O2BXNkVigx9NOidnO9QNEyTkc7wsw@mail.gmail.com>
Message-ID: <CAEZrhoPnMqAD6AdYsU9+RUaL1qgb41jM9ahUvonfztY0Y19Bog@mail.gmail.com>

1.10.5. $DLG_dir

Returns the direction of the request in dialog (as "upstream" string if the
request is generated by callee or "downstream" string if the request is
generated by caller) - to be used for sequential request. This PV will be
available only for sequential requests (not for replies), after doing
loose_route().

NULL will be returned if there is no dialog for the request.

On Wed, Mar 27, 2024 at 12:44 PM Prathibha B <prathibhab.tvm at gmail.com>
wrote:

> $DLG_dir returns null, when used in is_method("INVITE")
>
>
> --
> Regards,
> B.Prathibha
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240327/18a87397/attachment.html>

From liviu at opensips.org  Wed Mar 27 13:22:35 2024
From: liviu at opensips.org (Liviu Chircu)
Date: Wed, 27 Mar 2024 15:22:35 +0200
Subject: [OpenSIPS-Users] [Blog] HTTP/2 Server Support for Next-Generation
 Services in OpenSIPS 3.5
Message-ID: <0409ecbc-ce53-4f73-a5fa-c61a74c188f1@opensips.org>

Hi all,

OpenSIPS "master" branch got better just a few hours ago as we merged 
the new "http2d" module, offering HTTP/2 server-side support.  Read all 
about it in this blog post:

https://blog.opensips.org/2024/03/27/http-2-server-support-for-next-generation-services-in-opensips-3-5/

Enjoy!

-- 
Liviu Chircu
www.twitter.com/liviuchircu  |www.opensips-solutions.com
OpenSIPS Summit 2024 Valencia, May 14-17 |www.opensips.org/events
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240327/71863917/attachment.html>

From gmaruzz at gmail.com  Wed Mar 27 14:06:41 2024
From: gmaruzz at gmail.com (Giovanni Maruzzelli)
Date: Wed, 27 Mar 2024 15:06:41 +0100
Subject: [OpenSIPS-Users] [Blog] HTTP/2 Server Support for
 Next-Generation Services in OpenSIPS 3.5
In-Reply-To: <0409ecbc-ce53-4f73-a5fa-c61a74c188f1@opensips.org>
References: <0409ecbc-ce53-4f73-a5fa-c61a74c188f1@opensips.org>
Message-ID: <CALXCt0rVB8V-4z2ByH4GsUR_vLeHnMpEtot9reOk28F_dCAh3A@mail.gmail.com>

On Wed, Mar 27, 2024 at 2:25 PM Liviu Chircu <liviu at opensips.org> wrote:

> Hi all,
>
> OpenSIPS "master" branch got better just a few hours ago as we merged the
> new "http2d" module, offering HTTP/2 server-side support.  Read all about
> it in this blog post:
>
>
> https://blog.opensips.org/2024/03/27/http-2-server-support-for-next-generation-services-in-opensips-3-5/
>

G L O R I O U S

-giovanni

-- 
Sincerely,

Giovanni Maruzzelli
OpenTelecom.IT
cell: +39 347 266 56 18
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240327/990600aa/attachment.html>

From noc at voipaustralia.com.au  Wed Mar 27 22:30:51 2024
From: noc at voipaustralia.com.au (VoIP Australia NOC)
Date: Wed, 27 Mar 2024 22:30:51 +0000
Subject: [OpenSIPS-Users] [Blog] HTTP/2 Server Support for
 Next-Generation Services in OpenSIPS 3.5
In-Reply-To: <0409ecbc-ce53-4f73-a5fa-c61a74c188f1@opensips.org>
References: <0409ecbc-ce53-4f73-a5fa-c61a74c188f1@opensips.org>
Message-ID: <ME2PR01MB576373482A85076D75D07525F4342@ME2PR01MB5763.ausprd01.prod.outlook.com>

I have tried more than 3 times to be removed from this mailing list and my emails are still bombarded, can someone whom runs this please remove me from it?

From: Users <users-bounces at lists.opensips.org> On Behalf Of Liviu Chircu
Sent: Wednesday, March 27, 2024 9:23 PM
To: OpenSIPS devel mailling list <devel at lists.opensips.org>; OpenSIPS users mailling list <users at lists.opensips.org>
Subject: [OpenSIPS-Users] [Blog] HTTP/2 Server Support for Next-Generation Services in OpenSIPS 3.5


Hi all,

OpenSIPS "master" branch got better just a few hours ago as we merged the new "http2d" module, offering HTTP/2 server-side support.  Read all about it in this blog post:

https://blog.opensips.org/2024/03/27/http-2-server-support-for-next-generation-services-in-opensips-3-5/

Enjoy!

--

Liviu Chircu

www.twitter.com/liviuchircu<http://www.twitter.com/liviuchircu> | www.opensips-solutions.com<http://www.opensips-solutions.com>

OpenSIPS Summit 2024 Valencia, May 14-17 | www.opensips.org/events<http://www.opensips.org/events>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240327/4ccaf48d/attachment.html>

From prathibhab.tvm at gmail.com  Thu Mar 28 06:56:45 2024
From: prathibhab.tvm at gmail.com (Prathibha B)
Date: Thu, 28 Mar 2024 12:26:45 +0530
Subject: [OpenSIPS-Users] Send failed(477/TM)
Message-ID: <CAJh_-cDHYvGgnnNuLKy-pLX1U4-XPP6BXtUUznRaC69kSQ1W-w@mail.gmail.com>

You tried t make a video call. send failed(477/TM). I am getting this error
frequently.
-- 
Regards,
B.Prathibha
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240328/6738a265/attachment-0001.html>

From Johan at democon.be  Thu Mar 28 08:29:40 2024
From: Johan at democon.be (Johan De Clercq)
Date: Thu, 28 Mar 2024 09:29:40 +0100
Subject: [OpenSIPS-Users]
	https://datatracker.ietf.org/doc/html/rfc3261#section-13.3.1.1
Message-ID: <CAEVWGm_Mbp2JU5hT54iYPCrgs25uMEvAZ2XsGctP_rhR7YDz-w@mail.gmail.com>

Question,

I always believed that fr_inv_timer should trigger when an invite is not
finished in due time.
This seems however to contradict the link in the title

 If the UAS is not able to answer the invitation immediately, it can
   choose to indicate some kind of progress to the UAC (for example, an
   indication that a phone is ringing).  This is accomplished with a
   provisional response between 101 and 199.  These provisional
   responses establish early dialogs and therefore follow the procedures
   of Section 12.1.1
<https://datatracker.ietf.org/doc/html/rfc3261#section-12.1.1> in
addition to those of Section 8.2.6
<https://datatracker.ietf.org/doc/html/rfc3261#section-8.2.6>.  A UAS
MAY
   send as many provisional responses as it likes.  Each of these MUST
   indicate the same dialog ID.  However, these will not be delivered
   reliably.

   If the UAS desires an extended period of time to answer the INVITE,
   it will need to ask for an "extension" in order to prevent proxies
   from canceling the transaction.  A proxy has the option of canceling
   a transaction when there is a gap of 3 minutes between responses in a
   transaction.  To prevent cancellation, the UAS MUST send a non-100
   provisional response at every minute, to handle the possibility of
   lost provisional responses.

      An INVITE transaction can go on for extended durations when the
      user is placed on hold, or when interworking with PSTN systems
      which allow communications to take place without answering the
      call.  The latter is common in Interactive Voice Response (IVR)
      systems.


Can somebody please comment on this ?

BR, Johan.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240328/77c68739/attachment.html>

From liviu at opensips.org  Thu Mar 28 09:22:56 2024
From: liviu at opensips.org (Liviu Chircu)
Date: Thu, 28 Mar 2024 11:22:56 +0200
Subject: [OpenSIPS-Users] [Blog] HTTP/2 Server Support for
 Next-Generation Services in OpenSIPS 3.5
In-Reply-To: <ME2PR01MB576373482A85076D75D07525F4342@ME2PR01MB5763.ausprd01.prod.outlook.com>
References: <0409ecbc-ce53-4f73-a5fa-c61a74c188f1@opensips.org>
 <ME2PR01MB576373482A85076D75D07525F4342@ME2PR01MB5763.ausprd01.prod.outlook.com>
Message-ID: <ee115311-190c-c81a-3ccf-e0643d3fc7f1@opensips.org>

On 28.03.2024 00:30, VoIP Australia NOC wrote:
> I have tried more than 3 times to be removed from this mailing list 
> and my emails are still bombarded, can someone whom runs this please 
> remove me from it?

Unsubscribing from a GNU Mailman public mailing list is a standard 
procedure, there are no mysteries or hidden "gotchas" around it:

1. go to http://lists.opensips.org
<http://lists.opensips.org>2. pick your Mailman list to unsubscribe from 
(e.g. Users)
3. scroll down, fill in your email and click the "*Unsubscribe or edit 
options*" button
4. have a Snickers
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240328/262f9f05/attachment.html>

From bogdan at opensips.org  Thu Mar 28 10:15:20 2024
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Thu, 28 Mar 2024 12:15:20 +0200
Subject: [OpenSIPS-Users] How to access to a column of a location
	database
In-Reply-To: <PAVPR02MB92075A75244B3E49E6AF42A883312@PAVPR02MB9207.eurprd02.prod.outlook.com>
References: <PAVPR02MB92075A75244B3E49E6AF42A883312@PAVPR02MB9207.eurprd02.prod.outlook.com>
Message-ID: <89d962bc-0e78-43ef-a5e9-092c11e02b5b@opensips.org>

Hi Guillaume,

The registered contact (and the additional info) is fetched via the 
lookup("location") function. It also sets the registered socket for the 
routing the current request.

Regards,

Bogdan-Andrei Iancu

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

On 22.03.2024 10:57, guillaume.desgeorge at orange.com wrote:
>
> Hi everybody,
>
> In my routing logic of my “opensips.cfg” file, I’m trying to access 
> the “socket” field of the location table of registered contacts.
>
> I have the registering informations correctly written in MySQL 
> location table but can’t find a function to access it.
>
> I’d like to have a function which I give the registered username and 
> can give me back the associated socket.
>
> Is the lookup () function the good one ? I didn’t understand how to 
> use it that way.
>
> Thanks for your help,
>
>    Guillaume
>
> Orange Restricted
>
>
> Orange Restricted
>
> ____________________________________________________________________________________________________________
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
>
> This message and its attachments may contain confidential or privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
> Thank you.
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240328/c3dd4abe/attachment.html>

From bogdan at opensips.org  Thu Mar 28 10:32:06 2024
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Thu, 28 Mar 2024 12:32:06 +0200
Subject: [OpenSIPS-Users] Getting the $rb or media port for egress
 message.
In-Reply-To: <fdff23b8-26d6-4f03-b560-654f840c6304@schu.net>
References: <fdff23b8-26d6-4f03-b560-654f840c6304@schu.net>
Message-ID: <cd08490f-bcd5-4ec0-8b6a-276f1e4fb5a3@opensips.org>

Hi Matthew,

For efficiency reasons, the changes over the SIP messages are not 
applied (so vizible) on the spot, but only at the end, when the SIP 
message is sent out. So, shortly, you cannot see the changes done by 
your script, you all the time "see" the initial received message.

Options you have here:

1) force applying the changes, see the get_updated_body_part() [1]
   if (has_body("application/sdp")){
     rtpengine_offer();
     get_updated_body_part( "application/sdp", $var(new_sdp));
     $var(mline) = $(var(new_sdp){sdp.line,m,0});
     xlog("TEST $var(mline)\n");
   }

2) instruct rtpengine not to change the SDP in the message, but to do 
the changes over an SDP stored in a variable. And you will push the new 
SDP manually in the message.
   if (has_body("application/sdp")){
$var(new_sdp)= $rb;
     rtpengine_offer(,,,,,$var(new_sdp));
     $var(mline) = $(var(new_sdp){sdp.line,m,0});
     remove_body_part("application/sdp");
     add_body_part($var(new_sdp),"application/sdp");
     xlog("TEST $var(mline)\n");
   }


[1] 
https://opensips.org/html/docs/modules/3.4.x/sipmsgops.html#func_get_updated_body_part

Regards,

Bogdan-Andrei Iancu

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

On 26.03.2024 23:17, Matthew Schumacher wrote:
> Hello,
>
> I'm trying to log the media port for another system and using this 
> code to grab the m line out of an SDP header:
>
>   if (has_body("application/sdp")){
>     rtpengine_offer();
>     $var(mline) = $(rb{sdp.line,m,0});
>     xlog("TEST $var(mline)\n");
>   }
>
> The problem is that it only sees the ports for ingress SDP messages 
> and not egress SDP messages.  What can I do to grab the SDP messages 
> leaving opensips?
>
> I want to take this data and inject a firewall rule that allows the 
> media and remove it later because NAT helpers don't work on TLS 
> traffic, my system already knows what port to expect, and I don't like 
> having a huge pile of UDP ports allowed through.
>
> Honestly, I'm not sure why the kernel mode forwarding in rtpengine 
> doesn't also allow traffic based on ports we are expecting to see 
> traffic from.... that's what I thought it did at first until I 
> realized that it's only forwarding the RTP packet through the kernel 
> faster without needing userspace.
>
> Thanks,
> Matt
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users



From bogdan at opensips.org  Thu Mar 28 10:35:19 2024
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Thu, 28 Mar 2024 12:35:19 +0200
Subject: [OpenSIPS-Users]
 https://datatracker.ietf.org/doc/html/rfc3261#section-13.3.1.1
In-Reply-To: <CAEVWGm_Mbp2JU5hT54iYPCrgs25uMEvAZ2XsGctP_rhR7YDz-w@mail.gmail.com>
References: <CAEVWGm_Mbp2JU5hT54iYPCrgs25uMEvAZ2XsGctP_rhR7YDz-w@mail.gmail.com>
Message-ID: <80c77a9a-ae00-4f16-8e4f-3c1f3a1c640a@opensips.org>

Hi Johan,

In OpenSIPS, the fr_inv_timer kicks in (for INVITEs) when a first reply 
(typically a 100) is received from UAS. And it will wait for the final 
reply. So, it is how long to wait from the first reply up to the final one.

Regards,

Bogdan-Andrei Iancu

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

On 28.03.2024 10:29, Johan De Clercq wrote:
> Question,
>
> I always believed that fr_inv_timer should trigger when an invite is 
> not finished in due time.
> This seems however to contradict the link in the title
>
>   If the UAS is not able to answer the invitation immediately, it can
>     choose to indicate some kind of progress to the UAC (for example, an
>     indication that a phone is ringing).  This is accomplished with a
>     provisional response between 101 and 199.  These provisional
>     responses establish early dialogs and therefore follow the procedures
>     ofSection 12.1.1  <https://datatracker.ietf.org/doc/html/rfc3261#section-12.1.1>  in addition to those ofSection 8.2.6  <https://datatracker.ietf.org/doc/html/rfc3261#section-8.2.6>.  A UAS MAY
>     send as many provisional responses as it likes.  Each of these MUST
>     indicate the same dialog ID.  However, these will not be delivered
>     reliably.
>
>     If the UAS desires an extended period of time to answer the INVITE,
>     it will need to ask for an "extension" in order to prevent proxies
>     from canceling the transaction.  A proxy has the option of canceling
>     a transaction when there is a gap of 3 minutes between responses in a
>     transaction.  To prevent cancellation, the UAS MUST send a non-100
>     provisional response at every minute, to handle the possibility of
>     lost provisional responses.
>
>        An INVITE transaction can go on for extended durations when the
>        user is placed on hold, or when interworking with PSTN systems
>        which allow communications to take place without answering the
>        call.  The latter is common in Interactive Voice Response (IVR)
>        systems.
>
> Can somebody please comment on this ?
>
> BR, Johan.
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240328/73474880/attachment-0001.html>

From bogdan at opensips.org  Thu Mar 28 10:58:13 2024
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Thu, 28 Mar 2024 12:58:13 +0200
Subject: [OpenSIPS-Users]
 https://datatracker.ietf.org/doc/html/rfc3261#section-13.3.1.1
In-Reply-To: <CAEVWGm91fL9REZx+qHrmY04CAk2RDR5TCFO8Xm1J2LbBg9PTWQ@mail.gmail.com>
References: <CAEVWGm_Mbp2JU5hT54iYPCrgs25uMEvAZ2XsGctP_rhR7YDz-w@mail.gmail.com>
 <80c77a9a-ae00-4f16-8e4f-3c1f3a1c640a@opensips.org>
 <CAEVWGm91fL9REZx+qHrmY04CAk2RDR5TCFO8Xm1J2LbBg9PTWQ@mail.gmail.com>
Message-ID: <8d1c78e1-3e15-4c59-ad51-fb7531dfa015@opensips.org>

For any reply, see here the condition:

https://github.com/OpenSIPS/opensips/blob/4b23a80bd14dcf509ebe8de22f26906d34e0b079/modules/tm/t_reply.c#L1697

Keep in mind that the restart_fr_on_each_reply is by default on (set to 1).


Regards,

Bogdan-Andrei Iancu

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

On 28.03.2024 12:37, Johan De Clercq wrote:
> Thanks for the swift reply Bogdan.
> but shouldn't this timer be reset when receiving f.e. 180 or 183 ?
>
>
> Op do 28 mrt 2024 om 11:35 schreef Bogdan-Andrei Iancu 
> <bogdan at opensips.org>:
>
>     Hi Johan,
>
>     In OpenSIPS, the fr_inv_timer kicks in (for INVITEs) when a first
>     reply (typically a 100) is received from UAS. And it will wait for
>     the final reply. So, it is how long to wait from the first reply
>     up to the final one.
>
>     Regards,
>
>     Bogdan-Andrei Iancu
>
>     OpenSIPS Founder and Developer
>        https://www.opensips-solutions.com
>        https://www.siphub.com
>
>     On 28.03.2024 10:29, Johan De Clercq wrote:
>>     Question,
>>
>>     I always believed that fr_inv_timer should trigger when an invite
>>     is not finished in due time.
>>     This seems however to contradict the link in the title
>>
>>       If the UAS is not able to answer the invitation immediately, it can
>>         choose to indicate some kind of progress to the UAC (for example, an
>>         indication that a phone is ringing).  This is accomplished with a
>>         provisional response between 101 and 199.  These provisional
>>         responses establish early dialogs and therefore follow the procedures
>>         ofSection 12.1.1  <https://datatracker.ietf.org/doc/html/rfc3261#section-12.1.1>  in addition to those ofSection 8.2.6  <https://datatracker.ietf.org/doc/html/rfc3261#section-8.2.6>.  A UAS MAY
>>         send as many provisional responses as it likes.  Each of these MUST
>>         indicate the same dialog ID.  However, these will not be delivered
>>         reliably.
>>
>>         If the UAS desires an extended period of time to answer the INVITE,
>>         it will need to ask for an "extension" in order to prevent proxies
>>         from canceling the transaction.  A proxy has the option of canceling
>>         a transaction when there is a gap of 3 minutes between responses in a
>>         transaction.  To prevent cancellation, the UAS MUST send a non-100
>>         provisional response at every minute, to handle the possibility of
>>         lost provisional responses.
>>
>>            An INVITE transaction can go on for extended durations when the
>>            user is placed on hold, or when interworking with PSTN systems
>>            which allow communications to take place without answering the
>>            call.  The latter is common in Interactive Voice Response (IVR)
>>            systems.
>>
>>     Can somebody please comment on this ?
>>
>>     BR, Johan.
>>
>>
>>     _______________________________________________
>>     Users mailing list
>>     Users at lists.opensips.org
>>     http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240328/c6e274d8/attachment.html>

From ulus_egemen at hotmail.com  Thu Mar 28 14:35:26 2024
From: ulus_egemen at hotmail.com (egemen ulus)
Date: Thu, 28 Mar 2024 14:35:26 +0000
Subject: [OpenSIPS-Users] Callee details not visible in dialog detail
Message-ID: <GV1P193MB21192D582CE43E043DAEF4428E3B2@GV1P193MB2119.EURP193.PROD.OUTLOOK.COM>

Hi,
I am wondering why callee info is not visible in dialog details:
Here is the case:

client-1 > kamailio > two asterisks > kamailio > client-2
registration is on asterisk.

dialog module is enabled and I want to see the asterisk IP that is determined by dispatcher module.
I have tried to put dlg_manage function even after dispatch function, but did not help.

Any way to have asterisk IP in dialog details?

It shows only this:

{
 h_entry: 483
 h_id: 8644
 ref: 1
 call-id: v489LdfOFD5mnlHupQHOvw..
 from_uri: sip:1515 at 12.12.12.12;transport=UDP
 to_uri: sip:2222 at 12.12.12.12
 state: 5
 start_ts: 0
 init_ts: xxxx
 end_ts: xxxx
 duration: xxxx
 timeout: 0
 lifetime: 3600
 dflags: 512
 sflags: 0
 iflags: 0
 caller: {
  tag: d0283007
  contact: sip:1515 at 1.1.1.1:64966;transport=UDP
  cseq: 1
  route_set:
  socket: udp:172.22.10.10:5060
 }
 callee: {
  tag: <null string>
  contact: <null string>
  cseq: <null string>
  route_set: <null string>
  socket: <null string>
 }
 profiles: {
 }
 variables: {
 }
}


Regards

Get Outlook for Android<https://aka.ms/AAb9ysg>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240328/7323533b/attachment.html>

From bogdan at opensips.org  Thu Mar 28 20:34:41 2024
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Thu, 28 Mar 2024 22:34:41 +0200
Subject: [OpenSIPS-Users] Callee details not visible in dialog detail
In-Reply-To: <GV1P193MB21192D582CE43E043DAEF4428E3B2@GV1P193MB2119.EURP193.PROD.OUTLOOK.COM>
References: <GV1P193MB21192D582CE43E043DAEF4428E3B2@GV1P193MB2119.EURP193.PROD.OUTLOOK.COM>
Message-ID: <feb0e850-a0ce-40b3-96ef-d78e12467b80@opensips.org>

Hi,

If using Kamailio, you should ask this on the kamilio mailing list, 
right ? This mailing list is for OpenSIPS.

Regards

Bogdan-Andrei Iancu

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

On 28.03.2024 16:35, egemen ulus wrote:
> Hi,
> I am wondering why callee info is not visible in dialog details:
> Here is the case:
>
> client-1 > kamailio > two asterisks > kamailio > client-2
> registration is on asterisk.
>
> dialog module is enabled and I want to see the asterisk IP that is 
> determined by dispatcher module.
> I have tried to put dlg_manage function even after dispatch function, 
> but did not help.
>
> Any way to have asterisk IP in dialog details?
>
> It shows only this:
>
> {
>  h_entry: 483
>  h_id: 8644
>  ref: 1
>  call-id: v489LdfOFD5mnlHupQHOvw..
>  from_uri: sip:1515 at 12.12.12.12;transport=UDP
>  to_uri: sip:2222 at 12.12.12.12
>  state: 5
>  start_ts: 0
>  init_ts: xxxx
>  end_ts: xxxx
>  duration: xxxx
>  timeout: 0
>  lifetime: 3600
>  dflags: 512
>  sflags: 0
>  iflags: 0
>  caller: {
>   tag: d0283007
>   contact: sip:1515 at 1.1.1.1:64966;transport=UDP
>   cseq: 1
>   route_set:
>   socket: udp:172.22.10.10:5060
>  }
>  callee: {
>   tag: <null string>
>   contact: <null string>
>   cseq: <null string>
>   route_set: <null string>
>   socket: <null string>
>  }
>  profiles: {
>  }
>  variables: {
>  }
> }
>
>
> Regards
>
> Get Outlook for Android <https://aka.ms/AAb9ysg>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240328/cd30f6b4/attachment.html>

From Calin.Dragan at garmin.com  Fri Mar 29 10:25:15 2024
From: Calin.Dragan at garmin.com (Dragan, Calin)
Date: Fri, 29 Mar 2024 10:25:15 +0000
Subject: [OpenSIPS-Users] Freeswitch integration
In-Reply-To: <BN8PR04MB5779A7B6308F1D401726ED2EF3282@BN8PR04MB5779.namprd04.prod.outlook.com>
References: <BN8PR04MB5779A7B6308F1D401726ED2EF3282@BN8PR04MB5779.namprd04.prod.outlook.com>
Message-ID: <BN8PR04MB57793C56BEBFDAEE18CA3235F33A2@BN8PR04MB5779.namprd04.prod.outlook.com>

Hi Bogdan,

Sorry, I missed your other reply. Meanwhile I advanced with my integration POC, and I’m able to exchange messages between OpenSIPS as a load balancer and Freeswitch as media service.

Where I’m stuck now is establishing a call between parties. The first invite is sent to the Freeswitch, Freeswitch picks it, tryes to establish a bridge, responds with a 100 Trying, that 100 message reach back the OpenSIPS, and nothing else happens, I cannot see it generating a new invite for the second participant and the ringing message.

Not sure which information about my setup would be useful to help you help me 😊.

Thank you,
Calin



From: Dragan, Calin
Sent: Friday, March 15, 2024 1:04 PM
To: users at lists.opensips.org
Subject: Freeswitch integration

Hi,

I’m trying to use Freeswitch as a media server with Opensips as a load balancer, I need something very basic for a POC. (I configured the load balancer and dispatcher based on old information found here: https://developer.signalwire.com/freeswitch/FreeSWITCH-Explained/Enterprise-Deployment/Enterprise-deployment-OpenSIPS_13173169/#freeswitch-configuration, here: https://developer.signalwire.com/freeswitch/FreeSWITCH-Explained/Auxiliary-Knowledge-and-Utilities/OpenSIPS-configuration-for-2-or-more-FreeSWITCH-installs_13173462/ and here: https://www.opensips.org/Documentation/Tutorials-OpenSIPSFreeSwitchIntegration)

I’m adding the X-Auth-IP header to the requests like this (this is based on the config that ships with the 3.4.x release in the docker image, so I guessed that this is where I should add the header):

route[relay] {
               # for INVITEs enable some additional helper routes
               if (is_method("INVITE")) {
                                remove_hf("X-Auth-IP");
                               append_hf("X-Auth-IP: $si\r\n");
                               append_to_reply("X-Auth-IP: $si\r\n");
                               xlog("L_INFO", "$ci|log|X-Auth-IP: $si\n");
                               xlog("L_INFO", "SIP Message: $mb");

                              t_on_failure("missed_call");
                              t_on_branch("per_branch_ops");
                              t_on_reply("handle_nat");
               }

               if (!t_relay()) {
                              send_reply(500,"Internal Error");
               }
               exit;
}

On the freeswitch side I added the IP set by opensips in the list of allowed addresses.

Now, with or without authentication enabled on the Freeswitch side (i.e. regardless of what I set in the “auth-calls” param, or if I enable the accept-blind-auth), or even whether the Freeswitch is running or not, when I try to place a call from/to some registerd addresses, I get the “407 Proxy authentication required” response.

Could you please give me some hints on what I might be doing wrong, or direct me to a contemporary tutorial?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240329/34d216a9/attachment-0001.html>

From spanda at 3clogic.com  Fri Mar 29 12:07:01 2024
From: spanda at 3clogic.com (Sasmita Panda)
Date: Fri, 29 Mar 2024 17:37:01 +0530
Subject: [OpenSIPS-Users] Opensips 3.2 with TCP connintion and DB operation
 on a single instance .
Message-ID: <CALf-Q47WaFYFzE23Wx2hqws_dB5qza2hZHOAMfKd21Sar03bxw@mail.gmail.com>

Hi All ,

Earlier in the very early stage of using opensips I had faced some issues
while using TCP with DB operation . Opensips has evolved a lot in the past
few years with so many additional features .

Now , can I use TCP globally with opensips 3.2 . My config will do DB
lookup as well .

https://www.opensips.org/Documentation/Script-Async-3-2#toc10
Is this relevant to my scenario or what issue is mentioned  here  ?

*Thanks & Regards*
*Sasmita Panda*
*Senior Network Testing and Software Engineer*
*3CLogic , ph:07827611765*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240329/0ffe8f3a/attachment.html>

From guillaume.desgeorge at orange.com  Fri Mar 29 13:08:56 2024
From: guillaume.desgeorge at orange.com (guillaume.desgeorge at orange.com)
Date: Fri, 29 Mar 2024 13:08:56 +0000
Subject: [OpenSIPS-Users] How to access to a column of a location
	database
In-Reply-To: <89d962bc-0e78-43ef-a5e9-092c11e02b5b@opensips.org>
References: <PAVPR02MB92075A75244B3E49E6AF42A883312@PAVPR02MB9207.eurprd02.prod.outlook.com>
 <89d962bc-0e78-43ef-a5e9-092c11e02b5b@opensips.org>
Message-ID: <PAVPR02MB9207FBAC5310A1EF8FD4C3A1833A2@PAVPR02MB9207.eurprd02.prod.outlook.com>

Hi Bogdan,
Thank you for your answer.
And is it possible to use that lookup("location") function to put the "registered socket" field in a variable in order to use it for my script ?
Regards,

  Guillaume

De : Bogdan-Andrei Iancu <bogdan at opensips.org>
Envoyé : jeudi 28 mars 2024 11:15
À : OpenSIPS users mailling list <users at lists.opensips.org>; DESGEORGE Guillaume INNOV/IT-S <guillaume.desgeorge at orange.com>
Objet : Re: [OpenSIPS-Users] How to access to a column of a location database

CAUTION : This email originated outside the company. Do not click on any links or open attachments unless you are expecting them from the sender.
ATTENTION : Cet e-mail provient de l'extérieur de l'entreprise. Ne cliquez pas sur les liens ou n'ouvrez pas les pièces jointes à moins de connaitre l'expéditeur.


Hi Guillaume,

The registered contact (and the additional info) is fetched via the lookup("location") function. It also sets the registered socket for the routing the current request.

Regards,


Bogdan-Andrei Iancu



OpenSIPS Founder and Developer

  https://www.opensips-solutions.com<https://www.opensips-solutions.com/>

  https://www.siphub.com<https://www.siphub.com/>
On 22.03.2024 10:57, guillaume.desgeorge at orange.com<mailto:guillaume.desgeorge at orange.com> wrote:
Hi everybody,
In my routing logic of my "opensips.cfg" file, I'm trying to access the "socket" field of the location table of registered contacts.
I have the registering informations correctly written in MySQL location table but can't find a function to access it.
I'd like to have a function which I give the registered username and can give me back the associated socket.
Is the lookup () function the good one ? I didn't understand how to use it that way.
Thanks for your help,

   Guillaume
Orange Restricted



Orange Restricted

____________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.



This message and its attachments may contain confidential or privileged information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.

Thank you.



_______________________________________________

Users mailing list

Users at lists.opensips.org<mailto:Users at lists.opensips.org>

http://lists.opensips.org/cgi-bin/mailman/listinfo/users

____________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240329/ff85b826/attachment-0001.html>

From vladpaiu at opensips.org  Fri Mar 29 14:01:25 2024
From: vladpaiu at opensips.org (Vlad Paiu)
Date: Fri, 29 Mar 2024 16:01:25 +0200
Subject: [OpenSIPS-Users] How to access to a column of a location
	database
In-Reply-To: <PAVPR02MB9207FBAC5310A1EF8FD4C3A1833A2@PAVPR02MB9207.eurprd02.prod.outlook.com>
References: <PAVPR02MB92075A75244B3E49E6AF42A883312@PAVPR02MB9207.eurprd02.prod.outlook.com>
 <89d962bc-0e78-43ef-a5e9-092c11e02b5b@opensips.org>
 <PAVPR02MB9207FBAC5310A1EF8FD4C3A1833A2@PAVPR02MB9207.eurprd02.prod.outlook.com>
Message-ID: <0ce77a75-bd01-4b73-85fc-614bf7ce4e3c@opensips.org>

Hello,

You can use 
https://opensips.org/html/docs/modules/3.3.x/registrar.html#param_attr_avp 
in order to populate any custom info at save() time and the info will 
automatically be populated for you at lookup() time.


Regards,
Vlad


On 29.03.2024 15:08, guillaume.desgeorge at orange.com wrote:
>
> Hi Bogdan,
>
> Thank you for your answer.
>
> And is it possible to use that lookup("location") function to put the 
> “registered socket” field in a variable in order to use it for my script ?
>
> Regards,
>
>   Guillaume
>
> *De :*Bogdan-Andrei Iancu <bogdan at opensips.org>
> *Envoyé :* jeudi 28 mars 2024 11:15
> *À :* OpenSIPS users mailling list <users at lists.opensips.org>; 
> DESGEORGE Guillaume INNOV/IT-S <guillaume.desgeorge at orange.com>
> *Objet :* Re: [OpenSIPS-Users] How to access to a column of a location 
> database
>
> *CAUTION*: This email originated outside the company. Do not click on 
> any links or open attachments unless you are expecting them from the 
> sender.
>
> *ATTENTION*: Cet e-mail provient de l'extérieur de l'entreprise. Ne 
> cliquez pas sur les liens ou n'ouvrez pas les pièces jointes à moins 
> de connaitre l'expéditeur.
>
>
>
> Hi Guillaume,
>
> The registered contact (and the additional info) is fetched via the 
> lookup("location") function. It also sets the registered socket for 
> the routing the current request.
>
> Regards,
>
> Bogdan-Andrei Iancu
>   
> OpenSIPS Founder and Developer
>    https://www.opensips-solutions.com
>    https://www.siphub.com
>
> On 22.03.2024 10:57, guillaume.desgeorge at orange.com wrote:
>
>     Hi everybody,
>
>     In my routing logic of my “opensips.cfg” file, I’m trying to
>     access the “socket” field of the location table of registered
>     contacts.
>
>     I have the registering informations correctly written in MySQL
>     location table but can’t find a function to access it.
>
>     I’d like to have a function which I give the registered username
>     and can give me back the associated socket.
>
>     Is the lookup () function the good one ? I didn’t understand how
>     to use it that way.
>
>     Thanks for your help,
>
>        Guillaume
>
>     Orange Restricted
>
>     Orange Restricted
>
>     ____________________________________________________________________________________________________________
>
>     Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
>
>     pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
>
>     a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
>
>     Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
>
>       
>
>     This message and its attachments may contain confidential or privileged information that may be protected by law;
>
>     they should not be distributed, used or copied without authorisation.
>
>     If you have received this email in error, please notify the sender and delete this message and its attachments.
>
>     As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
>
>     Thank you.
>
>
>
>     _______________________________________________
>
>     Users mailing list
>
>     Users at lists.opensips.org
>
>     http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
> ____________________________________________________________________________________________________________
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
>
> This message and its attachments may contain confidential or privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
> Thank you.
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240329/6890d9f7/attachment.html>

From brett at nemeroff.com  Fri Mar 29 15:16:02 2024
From: brett at nemeroff.com (Brett Nemeroff)
Date: Fri, 29 Mar 2024 10:16:02 -0500
Subject: [OpenSIPS-Users] Callee details not visible in dialog detail
In-Reply-To: <feb0e850-a0ce-40b3-96ef-d78e12467b80@opensips.org>
References: <GV1P193MB21192D582CE43E043DAEF4428E3B2@GV1P193MB2119.EURP193.PROD.OUTLOOK.COM>
 <feb0e850-a0ce-40b3-96ef-d78e12467b80@opensips.org>
Message-ID: <CAPwC5wxYNp1bb5xn75f7Dd4boDKNAjWEOQBUAcp34WqDi65yaA@mail.gmail.com>

While I agree with Bogdan about asking on the right list this particular
one is likely to be resolved the same way. You gotta be careful because
there are enough differences where that isn’t always the case. I believe
dlg_manage is Kamailio so you are definitely in the wrong spot!


Dialog variables can be used to store just about anything into the dialog
works similarly on both.

Best of luck!


https://www.kamailio.org/docs/modules/devel/modules/dialog.html#idm1681


https://opensips.org/html/docs/modules/2.2.x/dialog.html#idp6006096


On Thu, Mar 28, 2024 at 3:36 PM Bogdan-Andrei Iancu <bogdan at opensips.org>
wrote:

> Hi,
>
> If using Kamailio, you should ask this on the kamilio mailing list, right
> ? This mailing list is for OpenSIPS.
>
> Regards
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>   https://www.opensips-solutions.com
>   https://www.siphub.com
>
> On 28.03.2024 16:35, egemen ulus wrote:
>
> Hi,
> I am wondering why callee info is not visible in dialog details:
> Here is the case:
>
> client-1 > kamailio > two asterisks > kamailio > client-2
> registration is on asterisk.
>
> dialog module is enabled and I want to see the asterisk IP that is
> determined by dispatcher module.
> I have tried to put dlg_manage function even after dispatch function, but
> did not help.
>
> Any way to have asterisk IP in dialog details?
>
> It shows only this:
>
> {
>  h_entry: 483
>  h_id: 8644
>  ref: 1
>  call-id: v489LdfOFD5mnlHupQHOvw..
>  from_uri: sip:1515 at 12.12.12.12;transport=UDP
>  to_uri: sip:2222 at 12.12.12.12
>  state: 5
>  start_ts: 0
>  init_ts: xxxx
>  end_ts: xxxx
>  duration: xxxx
>  timeout: 0
>  lifetime: 3600
>  dflags: 512
>  sflags: 0
>  iflags: 0
>  caller: {
>   tag: d0283007
>   contact: sip:1515 at 1.1.1.1:64966;transport=UDP
>   cseq: 1
>   route_set:
>   socket: udp:172.22.10.10:5060
>  }
>  callee: {
>   tag: <null string>
>   contact: <null string>
>   cseq: <null string>
>   route_set: <null string>
>   socket: <null string>
>  }
>  profiles: {
>  }
>  variables: {
>  }
> }
>
>
> Regards
>
> Get Outlook for Android <https://aka.ms/AAb9ysg>
>
> _______________________________________________
> Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240329/da026270/attachment-0001.html>

From schu at schu.net  Fri Mar 29 16:08:09 2024
From: schu at schu.net (Matthew Schumacher)
Date: Fri, 29 Mar 2024 09:08:09 -0700
Subject: [OpenSIPS-Users] Why does tracer uri=file show in/out sip messages
 and uri=sip only shows in?
Message-ID: <312a3ea1-c25d-45a0-aea2-10bd0cecc090@schu.net>

Hello All,

I have this config:

modparam("tracer","trace_id","[siptrace]uri=sip:127.0.0.1:9999")
modparam("tracer","trace_id","[siptrace]uri=file:/var/log/siptrace.log")

route {
     trace("siptrace","d","sip");

...

When I look at the messages that show up on UDP:9999 I only see egress 
sip messages, but when I look at /var/log/siptrace.log I see both sides 
of the conversation.  Is this by design?  Is there a way to send all 
messages to a port, or a socket, or perhaps define a pipe to another 
process?  I'm trying to setup a second daemon that monitors all of the 
sip dialog between opensips and other hosts.

Thanks!
Matt


From schu at schu.net  Fri Mar 29 17:57:49 2024
From: schu at schu.net (Matthew Schumacher)
Date: Fri, 29 Mar 2024 10:57:49 -0700
Subject: [OpenSIPS-Users] Why does tracer uri=file show in/out sip
 messages and uri=sip only shows in?
In-Reply-To: <312a3ea1-c25d-45a0-aea2-10bd0cecc090@schu.net>
References: <312a3ea1-c25d-45a0-aea2-10bd0cecc090@schu.net>
Message-ID: <7fb4ccf1-b808-4a24-b403-3f9e52c8c63a@schu.net>

On 3/29/24 9:08 AM, Matthew Schumacher wrote:
> Hello All,
>
> I have this config:
>
> modparam("tracer","trace_id","[siptrace]uri=sip:127.0.0.1:9999")
> modparam("tracer","trace_id","[siptrace]uri=file:/var/log/siptrace.log")
>
> route {
>     trace("siptrace","d","sip");
>
> ...
>
> When I look at the messages that show up on UDP:9999 I only see egress 
> sip messages, but when I look at /var/log/siptrace.log I see both 
> sides of the conversation.  Is this by design?  Is there a way to send 
> all messages to a port, or a socket, or perhaps define a pipe to 
> another process?  I'm trying to setup a second daemon that monitors 
> all of the sip dialog between opensips and other hosts.
>
> Thanks!
> Matt
>


Correction, I only see ingress SIP messages, not egress when using the 
sip: uri in the tracer module.  If I use file: or hep: I see both sides.




From engineer.naveed68 at gmail.com  Sat Mar 30 19:56:25 2024
From: engineer.naveed68 at gmail.com (Naveed Ur Rehman)
Date: Sun, 31 Mar 2024 00:56:25 +0500
Subject: [OpenSIPS-Users] B2BUA Broken ACKs
Message-ID: <CAPzMEBP5jcX+ZVa3=fkDabzyuJ+fVC+v0qK+KtmSEDmT0pU6HA@mail.gmail.com>

[image: image.png]
Hi All
I have a strange issue, where ACKs are not reaching the called party. Even
BYE messages reach back to called party fine, but ACKs are stucked within
opensips,. opensips not even trying to send the ACKs to callee. What could
be the problem?

Regards

Naveed
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240331/b3699650/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 484408 bytes
Desc: not available
URL: <http://lists.opensips.org/pipermail/users/attachments/20240331/b3699650/attachment-0001.png>