[OpenSIPS-Users] Opensips with RTPEngine

[HS]

Hi all.

I just tried to replace RTPProxy with RTPEngine. I did the change as I was
getting one-way audio previously. However, one connection seems
inconsistent (One-way audio) sometimes and the other connection does not
actually even ring a bell. I have tried with both devices on the same Wi-Fi
and one on Wi-Fi and the other on a cellular network. There's no error in
opensips or rtpengine logs, so it seems that the routing is incorrect. I am
using Opensips 3.0. Please let me know what is incorrect or if further
information is needed. Following is my opensips.cfg file:

Thanks for the help in advance.

#
# OpenSIPS residential configuration script
# by OpenSIPS Solutions 
#
# This script was generated via "make menuconfig", from
#   the "Residential" scenario.
# You can enable / disable more features / functionalities by
#   re-generating the scenario with different options.#
#
# Please refer to the Core CookBook at:
#  https://opensips.org/Resources/DocsCookbooks
# for a explanation of possible statements, functions and parameters.
#


### Global Parameters #

log_level=3
log_stderror=no
#log_facility=LOG_LOCAL0
log_facility=LOG_LOCAL7

udp_workers=8

/* uncomment the following lines to enable debugging */
#debug_mode=yes

/* uncomment the next line to enable the auto temporary blacklisting of
   not available destinations (default disabled) */
#disable_dns_blacklist=no

/* uncomment the next line to enable IPv6 lookup after IPv4 dns
   lookup failures (default disabled) */
#dns_try_ipv6=yes

/* comment the next line to enable the auto discovery of local aliases
   based on reverse DNS on IPs */
auto_aliases=no

advertised_address=

listen=  # CUSTOMIZE ME
listen=  # CUSTOMIZE ME

# Set up listeners
#listen=ws:
#listen=wss:
#listen=tls:


### Modules Section 

#set module path
mpath="/usr/lib/x86_64-linux-gnu/opensips/modules/"

 SIGNALING module
loadmodule "signaling.so"

 StateLess module
loadmodule "sl.so"

 Transaction Module
loadmodule "tm.so"
modparam("tm", "fr_timeout", 5)
modparam("tm", "fr_inv_timeout", 30)
modparam("tm", "restart_fr_on_each_reply", 0)
modparam("tm", "onreply_avp_mode", 1)

 Record Route Module
loadmodule "rr.so"
/* do not append from tag to the RR (no need for this script) */
modparam("rr", "append_fromtag", 0)

 MAX ForWarD module
loadmodule "maxfwd.so"

 SIP MSG OPerationS module
loadmodule "sipmsgops.so"

 FIFO Management Interface
loadmodule "mi_fifo.so"
modparam("mi_fifo", "fifo_name", "/tmp/opensips_fifo")
modparam("mi_fifo", "fifo_mode", 0666)

 MYSQL module
loadmodule "db_mysql.so"

 HTTPD module
loadmodule "httpd.so"
modparam("httpd", "port", )

 USeR LOCation module
loadmodule "usrloc.so"
modparam("usrloc", "nat_bflag", "NAT")
modparam("usrloc", "db_mode",   2)
modparam("usrloc", "db_url",
"mysql://opensips:opensipsrw@localhost/opensips") # CUSTOMIZE ME


 REGISTRAR module
loadmodule "registrar.so"
modparam("registrar", "tcp_persistent_flag", "TCP_PERSISTENT")
modparam("registrar", "received_avp", "$avp(received_nh)")/* uncomment the
next line not to allow more than 10 contacts per AOR */
#modparam("registrar", "max_contacts", 10)

 ACCounting module
loadmodule "acc.so"
/* what special events should be accounted ? */
modparam("acc", "early_media", 0)
modparam("acc", "report_cancels", 0)
/* by default we do not adjust the direct of the sequential requests.
   if you enable this parameter, be sure the enable "append_fromtag"
   in "rr" module */
modparam("acc", "detect_direction", 0)
modparam("acc", "db_url",
"mysql://opensips:opensipsrw@localhost/opensips") # CUSTOMIZE ME

 AUTHentication modules
loadmodule "auth.so"
loadmodule "auth_db.so"
modparam("auth_db", "calculate_ha1", 0)
modparam("auth_db", "password_column", "ha1")
modparam("auth_db", "db_url",
"mysql://opensips:opensipsrw@localhost/opensips") # CUSTOMIZE ME
modparam("auth_db", "load_credentials", "")

 ALIAS module
loadmodule "alias_db.so"
modparam("alias_db", "db_url",
"mysql://opensips:opensipsrw@localhost/opensips") # CUSTOMIZE ME

 DOMAIN module
loadmodule "domain.so"
modparam("domain", "db_url",
"mysql://opensips:opensipsrw@localhost/opensips") # CUSTOMIZE ME
modparam("domain", "db_mode", 0)   # Use caching
modparam("auth_db|usrloc", "use_domain", 1)

 PRESENCE modules
loadmodule "xcap.so"
loadmodule "presence.so"
loadmodule "presence_xml.so"
modparam("xcap|presence", "db_url",
"mysql://opensips:opensipsrw@localhost/opensips") # CUSTOMIZE ME
modparam("presence_xml", "force_active", 1)
modparam("presence", "fallback2db", 0)

 DIALOG module
loadmodule "dialog.so"
modparam("dialog", "dlg_match_mode", 1)
modparam("dialog", "default_timeout", 21600)  # 6 hours timeout
modparam("dialog", "db_mode", 2)
modparam("dialog", "db_url",
"mysql://opensips:opensipsrw@localhost/opensips") # CUSTOMIZE ME

  NAT modules
loadmodule "nathelper.so"
modparam("registrar|nathelper", "received_avp", "$avp(rcv)")
modparam("

[OpenSIPS-Users] Opensips-3.0.4 compile tcp fails

[Robert Dyck]

net/tcp_common.c will not compile. Too many errors to list 
here.

It seems to be a new file as compared to my 3.0.2.

Rob


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

[OpenSIPS-Users] topology hiding bug?

[M S]

Dear OpenSIPS development team,
I have come across a strange case that sometime when I use
topology_hiding("UD"), it makes a mistake in changing Contact field.
Scenario is:

A: (Contact: ) sends Invite to private IP of
opensips, opensips changes Contact field to: (Contact:
) and sends Invite from public IP
to B.
Then B sends 200 OK back to Opensips public IP, with correct Contact:
(Contact: ). so far so good.
Now Opensips sends 200 OK back to A from its private IP, and changes
Contact to:
Contact: 

As you see, did part is repeated twice.. and that means when A replies with:
ACK sip:90006969.did.29c.2ed202e.did.29c.2ed202e@172.24.8.37 SIP/2.0

Opensips throws an error: ERROR:dialog:dlg_onroute: malformed route param
[29c.2ed202e.did.29c.2ed202e]

Is this a bug? I am using Opensips 3.1.0.

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

Re: [OpenSIPS-Users] [RELEASE] OpenSIPS 2.4.9 and 3.0.4 and 3.1.1 minor releases

[ryan embgrets]

So, I just upgraded my opensips to 3.1 and it looks like cache_raw_query
function is broken.

On opensips 3.0 it was ok with 2 parameters but now expecting 3 on opensips
3.1

parse error in /etc/opensips/opensips.cfg:265:24-25: too few parameters for
command #012

This below is what i have on line 265

cache_raw_query("redis:group1","EXPIRE $ci 3600");

Was the syntax changed for this cache_raw_query? Because I could not seem
to find it inside docs.

Ryan.


On Tue, 17 Nov 2020 at 22:51, mrsanvicente  wrote:

> Great news, Bravo!!
>
>
>
> Mario
>
> > El 17 nov 2020, a la(s) 8:53, Răzvan Crainea 
> escribió:
> >
> > Hi, Everyone!
> >
> > As promissed, we are happy to announce OpenSIPS latest minor releases:
> 2.4.9[1], 3.0.4[2] and 3.1.1[3]. All stable versions are now released with
> all the available fixes.
> > In order to migrate from previous minor versions, simply upgrade the
> packages - there's no need to make any DB or script changes. If you want to
> migrate from a previous version, make sure you're following the correct
> migration manual[4].
> >
> > [1] https://opensips.org/pub/opensips/2.4.9/ChangeLog
> > [2] https://opensips.org/pub/opensips/3.0.4/ChangeLog
> > [3] https://opensips.org/pub/opensips/3.1.1/ChangeLog
> > [4] https://www.opensips.org/Documentation/Migration
> >
> > Enjoy the new releases!
> >
> > Răzvan Crainea
> > OpenSIPS Core Developer
> > http://www.opensips-solutions.com
> >
> >> On 11/6/20 12:54 PM, Răzvan Crainea wrote:
> >> Hello, everyone!
> >> I am happy to announce you that on Tuesday, 17th of November 2020, we
> will be releasing three new minor versions, one for each of our supported
> branches - 2.4, 3.0 and 3.1.
> >> All these releases will only contain bug fixes gathered from their
> previous releases, so no script changes, or migration procedures are
> required to use them. A simple upgrade will suffice.
> >> We will let you know when the releases are completed, so you can start
> using them.
> >> Until then, happy hacking!
> >
> > ___
> > Users mailing list
> > Users@lists.opensips.org
> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] [RELEASE] OpenSIPS 2.4.9 and 3.0.4 and 3.1.1 minor releases

[mrsanvicente]

Great news, Bravo!!



Mario

> El 17 nov 2020, a la(s) 8:53, Răzvan Crainea  escribió:
> 
> Hi, Everyone!
> 
> As promissed, we are happy to announce OpenSIPS latest minor releases: 
> 2.4.9[1], 3.0.4[2] and 3.1.1[3]. All stable versions are now released with 
> all the available fixes.
> In order to migrate from previous minor versions, simply upgrade the packages 
> - there's no need to make any DB or script changes. If you want to migrate 
> from a previous version, make sure you're following the correct migration 
> manual[4].
> 
> [1] https://opensips.org/pub/opensips/2.4.9/ChangeLog
> [2] https://opensips.org/pub/opensips/3.0.4/ChangeLog
> [3] https://opensips.org/pub/opensips/3.1.1/ChangeLog
> [4] https://www.opensips.org/Documentation/Migration
> 
> Enjoy the new releases!
> 
> Răzvan Crainea
> OpenSIPS Core Developer
> http://www.opensips-solutions.com
> 
>> On 11/6/20 12:54 PM, Răzvan Crainea wrote:
>> Hello, everyone!
>> I am happy to announce you that on Tuesday, 17th of November 2020, we will 
>> be releasing three new minor versions, one for each of our supported 
>> branches - 2.4, 3.0 and 3.1.
>> All these releases will only contain bug fixes gathered from their previous 
>> releases, so no script changes, or migration procedures are required to use 
>> them. A simple upgrade will suffice.
>> We will let you know when the releases are completed, so you can start using 
>> them.
>> Until then, happy hacking!
> 
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users

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

Re: [OpenSIPS-Users] Teams TLS Error

[Vlad Patrascu]

I guess this error, which is indeed not worded very well, threw you off:

ERROR:tls_mgm:tlsp_set_certificate: TLS domain [my.domain.com 
] not defined in '[my.domain.com 
]/usr/local/etc/opensips/tls/my_domain_com.pem'


What it actually means is that the TLS domain "my.domain.com" (the 
tls_mgm module's record/structure, ) is not defined. Refer to this [1] 
section in docs for a better explanation on the the concept of "TLS 
domains" in tls_mgm. The term "TLS domain" might be a little loose and 
generate confusion sometimes.


So what you should do is add this in your config:

modparam("tls_mgm", "server_domain", "my.domain.com")

By the way, you can use any arbitrary identifier for the domain part in 
the tls_mgm parameters, eg. :


modparam("tls_mgm", "server_domain", "mydom")

modparam("tls_mgm","certificate", 
"[mydom]/usr/local/etc/opensips/tls/myCert.pem")


...

[1] https://opensips.org/docs/modules/3.1.x/tls_mgm.html#idp2972192

Regards,

--
Vlad Patrascu
OpenSIPS Developer
http://www.opensips-solutions.com

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

Re: [OpenSIPS-Users] Teams TLS Error

[Mark Farmer]

Hi Vlad/all

Sure (sanitized)

Nov 13 15:35:04 [175814] DBG:core:load_module: loading module
/usr/local/lib64/opensips/modules/tls_mgm.so
Nov 13 15:35:04 [175814] INFO:tls_mgm:mod_load: openssl version: OpenSSL
1.1.1f  31 Mar 2020
Nov 13 15:35:04 [175814] DBG:core:register_module: register_pv: tls_mgm
Nov 13 15:35:04 [175814] DBG:core:set_mod_param_regex: tls_mgm matches
module tls_mgm
Nov 13 15:35:04 [175814] DBG:core:set_mod_param_regex: found 
in module tls_mgm [/usr/local/lib64/opensips/modules/]
Nov 13 15:35:04 [175814] ERROR:tls_mgm:tlsp_set_certificate: TLS domain [
my.domain.com] not defined in '[my.domain.com
]/usr/local/etc/opensips/tls/my_domain_com.pem'
Nov 13 15:35:04 [175814] Traceback (last included file at the bottom):
Nov 13 15:35:04 [175814]  0. /usr/local//etc/opensips/opensips.cfg
Nov 13 15:35:04 [175814] CRITICAL:core:yyerror: parse error in
/usr/local//etc/opensips/opensips.cfg:191:19-20: Parameter 
not found in module  - can't set
Nov 13 15:35:04 [175814] #modparam("tls_mgm", "require_cert", "[dom4]1")
Nov 13 15:35:04 [175814]
Nov 13 15:35:04 [175814] modparam("tls_mgm","certificate", "[my.domain.com
]/usr/local/etc/opensips/tls/my_domain_com.pem")
Nov 13 15:35:04 [175814] ^~
Nov 13 15:35:04 [175814] modparam("tls_mgm","private_key", "[my.domain.com
]/usr/local/etc/opensips/tls/my_domain_com.key")
Nov 13 15:35:04 [175814] modparam("tls_mgm","ca_dir", "/etc/ssl/certs")
Nov 13 15:35:04 [175814] DBG:core:set_mod_param_regex: tls_mgm matches
module tls_mgm
Nov 13 15:35:04 [175814] DBG:core:set_mod_param_regex: found 
in module tls_mgm [/usr/local/lib64/opensips/modules/]
Nov 13 15:35:04 [175814] ERROR:tls_mgm:tlsp_set_pk: TLS domain [
my.domain.com] not defined in '[my.domain.com
]/usr/local/etc/opensips/tls/my_domain_com.key'
Nov 13 15:35:04 [175814] CRITICAL:core:yyerror: parse error in
/usr/local//etc/opensips/opensips.cfg:192:19-20: Parameter 
not found in module  - can't set
Nov 13 15:35:04 [175814] DBG:core:set_mod_param_regex: tls_mgm matches
module tls_mgm
Nov 13 15:35:04 [175814] DBG:core:set_mod_param_regex: found  in
module tls_mgm [/usr/local/lib64/opensips/modules/]
Nov 13 15:35:04 [175814] ERROR:tls_mgm:split_param_val: No TLS domain name
Nov 13 15:35:04 [175814] CRITICAL:core:yyerror: parse error in
/usr/local//etc/opensips/opensips.cfg:193:19-20: Parameter  not
found in module  - can't set
Nov 13 15:35:04 [175814] DBG:core:set_mod_param_regex: tls_mgm matches
module tls_mgm
Nov 13 15:35:04 [175814] DBG:core:set_mod_param_regex: found 
in module tls_mgm [/usr/local/lib64/opensips/modules/]
Nov 13 15:35:04 [175814] ERROR:tls_mgm:tlsp_set_verify: TLS domain [
my.domain.com] not defined in '[my.domain.com]1'
Nov 13 15:35:04 [175814] CRITICAL:core:yyerror: parse error in
/usr/local//etc/opensips/opensips.cfg:194:19-20: Parameter 
not found in module  - can't set
Nov 13 15:35:04 [175814] DBG:core:set_mod_param_regex: tls_mgm matches
module tls_mgm
Nov 13 15:35:04 [175814] DBG:core:set_mod_param_regex: found 
in module tls_mgm [/usr/local/lib64/opensips/modules/]
Nov 13 15:35:04 [175814] ERROR:tls_mgm:tlsp_set_require: TLS domain [
my.domain.com] not defined in '[my.domain.com]1'
Nov 13 15:35:04 [175814] CRITICAL:core:yyerror: parse error in
/usr/local//etc/opensips/opensips.cfg:195:19-20: Parameter 
not found in module  - can't set
Nov 13 15:35:04 [175814] DBG:core:set_mod_param_regex: tls_mgm matches
module tls_mgm
Nov 13 15:35:04 [175814] DBG:core:set_mod_param_regex: found 
in module tls_mgm [/usr/local/lib64/opensips/modules/]
Nov 13 15:35:04 [175814] ERROR:tls_mgm:tlsp_set_method: TLS domain [
my.domain.com] not defined in '[my.domain.com]TLSv1_2'
Nov 13 15:35:04 [175814] CRITICAL:core:yyerror: parse error in
/usr/local//etc/opensips/opensips.cfg:196:19-20: Parameter  not
found in module  - can't set
Nov 13 15:35:04 [175814] DBG:core:set_mod_param_regex: tls_mgm matches
module tls_mgm
Nov 13 15:35:04 [175814] DBG:core:set_mod_param_regex: found
 in module tls_mgm [/usr/local/lib64/opensips/modules/]
Nov 13 15:35:04 [175814] ERROR:tls_mgm:split_param_val: No TLS domain name
Nov 13 15:35:04 [175814] CRITICAL:core:yyerror: parse error in
/usr/local//etc/opensips/opensips.cfg:198:20-21: Parameter
 not found in module  - can't set



On Mon, 16 Nov 2020 at 20:44, Vlad Patrascu  wrote:

> Hi Mark,
>
> Can you post the actual errors that you get in the OpenSIPS logs, if that
> is the case?
>
> Regards,
>
> --
> Vlad Patrascu
> OpenSIPS Developerhttp://www.opensips-solutions.com
>
> On 16.11.2020 11:04, Mark Farmer wrote:
>
> Good morning all
>
> Can anyone clarify whether the TLS domain in SAN is supported or not
> please?
>
> Many thanks
> Mark.
>
>
> On Fri, 13 Nov 2020 at 15:59, Kevin Vines  wrote:
>
>> You got me there... the doc states
>>
>> OpenSIPS offers SIP service for multiple  219domains, e.g. atlanta.com 
>> and biloxi.com. Altough both domains  220will be hosted on a single SIP 
>> proxy, the SIP proxy needs 2  221certificates: One for atlanta.com and 
>>

Re: [OpenSIPS-Users] [RELEASE] OpenSIPS 2.4.9 and 3.0.4 and 3.1.1 minor releases

[Răzvan Crainea]

Hi, Everyone!

As promissed, we are happy to announce OpenSIPS latest minor releases: 
2.4.9[1], 3.0.4[2] and 3.1.1[3]. All stable versions are now released 
with all the available fixes.
In order to migrate from previous minor versions, simply upgrade the 
packages - there's no need to make any DB or script changes. If you want 
to migrate from a previous version, make sure you're following the 
correct migration manual[4].


[1] https://opensips.org/pub/opensips/2.4.9/ChangeLog
[2] https://opensips.org/pub/opensips/3.0.4/ChangeLog
[3] https://opensips.org/pub/opensips/3.1.1/ChangeLog
[4] https://www.opensips.org/Documentation/Migration

Enjoy the new releases!

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

On 11/6/20 12:54 PM, Răzvan Crainea wrote:

Hello, everyone!

I am happy to announce you that on Tuesday, 17th of November 2020, we 
will be releasing three new minor versions, one for each of our 
supported branches - 2.4, 3.0 and 3.1.
All these releases will only contain bug fixes gathered from their 
previous releases, so no script changes, or migration procedures are 
required to use them. A simple upgrade will suffice.
We will let you know when the releases are completed, so you can start 
using them.


Until then, happy hacking!


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

[OpenSIPS-Users] Force rtpmap:101

[Mark Farmer]

Hi everyone

I am getting some INVITE's that are requesting a=rtpmap:100
telephone-event/8000 and some other codecs too which is breaking DTMF.

What I really need to do is to force a=rtpmap:101 telephone-event/8000 in
the replies.
Can anyone tell me how to do this please? I've been looking at the docs but
I'm struggling with this one.

I am using RTPEngine and OpenSIPS 3.0

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

Re: [OpenSIPS-Users] Separating call branches via topology_hiding

[Denys Pozniak]

I will add diagrams to make it clearer.

*Now:*
FreeSWITCH --> Forking Proxy --> SEMS --> Edge Proxy

*Want to build:*
FreeSWITCH --> Forking Proxy --> OpenSIPS (topology_hiding) --> Edge Proxy

According to our specifics, the Edge Proxy should receive calls with
separate SIP CallIDs


пн, 16 нояб. 2020 г. в 20:25, Denys Pozniak :

> Hello!
>
> We use the following logic:
> When the user dials the internal extension, FreeSWITCH adds SIP AoRs of
> destination devices in X-headers.
> After that, the downstream Proxy forks this call according to these AoRs
> (e.g. 1 incoming call spawns 5 outgoing branches).
> In order to turn these branches into separate calls, we use a sems sbc,
> but due to certain limitations we are forced to replace it.
>
> I tested  *topology_hiding* module and determined that it does not split
> such branches into separate calls (all outgoing calls have the same SIP
> CallID).
>
> Is there any way to solve this problem?
>
> --
>
> BR,
> Denys Pozniak
>
>
>

-- 

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

[OpenSIPS-Users] Segfault in OpenSIPs 2.4.8

[Schneur Rosenberg]

Hi I just upgraded from 2.4.4 to 2.4.8 and my system crashed, first I
got a couple of these messages in my log over a span of a few hours.

CRITICAL:db_mysql:wrapper_single_mysql_stmt_execute: driver error
(1213): Deadlock found when trying to get lock; try restarting
transaction


And then this happened

 CRITICAL:core:sig_usr: segfault in process pid: 2440, id: 88

CRITICAL:core:handle_worker: dead child 88 (EOF received), pid 2440

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