Re: [OpenSIPS-Users] Cli and DB path

[Ali Alawi]

Dear Răzvan,

Thanks for your response, the cli are all set successfully using
database_schema_path.

Regards,
Ali

On Tue, May 17, 2022 at 10:52 AM Răzvan Crainea  wrote:

> Hi, Ali!
>
> Setting the database_schema_path should do the trick. Can you set it
> again and provide the logs?
>
> Best regards,
>
> Răzvan Crainea
> OpenSIPS Core Developer
> http://www.opensips-solutions.com
>
> On 5/14/22 02:30, Ali Alawi wrote:
> > Dear all,
> >
> > When I install opensips3.2 using APT packages, the cli point correctly
> > to mysql (mariadb) through /usr/share/opensips (Everything work fine)
> >
> > However, when  installation done using git clone --recursive, the cli
> > point to /usr/share/opensips  but in this time the cli doesn't find
> > mysql when i try to:
> > opensips-cli -x database create
> > ERROR: path '/usr/share/opensips' to OpenSIPS DB scripts does not exist!
> >
> > I notice that mysql is resides inside '/usr/local/share/opensips'
> > instead of '/usr/share/opensips'
> > I try to include the corrected path in the default.cfg and also try
> > |opensips-cli -o database_schema_path=|
> > |But I come up with no success|
> > |Any suggestions please? |
> >
> > Regards,
> > Ali
> >
> > ___
> > 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

[OpenSIPS-Users] SQL Cacher+Galera Cluster

[Mehdi Shirazi]

Hi
I plan to use SQL Cacher with Galera Cluster. After a record changes I want
to update the cache. Using standard triggers in mariadb is not possible to
run opensips-cli commands.
Please tell me your suggestions for the best approach.

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

[OpenSIPS-Users] [Release] OpenSIPS 3.3.0 major release, beta version

[Bogdan-Andrei Iancu]

Hi there !!

It is that time of the year to do our iteration - one more year, one 
more ambitious roadmap 
, one more 
OpenSIPS major release.


So, we are all happy to announce the beta release of *OpenSIPS 3.3.0 
major version* - and this 3.3 version is all about Messaging with MSRP, 
about Unified Communications with Contact Centers, about IMS with RCS 
and Diameter. But here is the shortest possible description 
 of this release; 
and be aware that it's actually not so short as nothing is short about 3.3 !


Please keep in mind that 3.3.0 is still a beta release, targeting mid 
July to become fully stable. So, we still have some testing ahead of us :).


Many thanks to our awesome community for contributing with ideas, code, 
patches, tests and reports!


Looking for downloading it? See the tarball 
or the GIT repo 
. Packages (rpms 
 and debs ) are 
also already available!


Enjoy it,

--
Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  https://www.opensips-solutions.com
OpenSIPS eBootcamp 23rd May - 3rd June 2022
  https://opensips.org/training/OpenSIPS_eBootcamp_2022/

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

Re: [OpenSIPS-Users] no TLS client domain found error

[Ovidiu Sas]

Please upgrade to the latest version and see if the error persists. If yes,
please run the server in debug mode and save the logs so this issue can be
investigated properly.

Thanks,
Ovidiu

On Wed, May 18, 2022 at 09:02 Jehanzaib Younis 
wrote:

> Thank you Bogdan,
> That helped a lot. As you mentioned I need to start only with
> server_domain or client_domain.
> Now I changed my config a bit as shown below:
>  (WebRTC) Client
> modparam("tls_mgm", "server_domain", "sip.mywebphone.xx")
> modparam("tls_mgm", "certificate",
> "[sip.mywebphone.xx]/etc/letsencrypt/live/sip.mywebphone.xx/cert.pem")
> modparam("tls_mgm", "private_key",
> "[sip.mywebphone.xx]/etc/letsencrypt/live/sip.mywebphone.xx/privkey.pem")
> modparam("tls_mgm", "ca_list",
> "[sip.mywebphone.xx]/etc/letsencrypt/live/sip.mywebphone.xx/fullchain.pem")
> modparam("tls_mgm", "ca_dir",
> "[sip.mywebphone.xx]/etc/letsencrypt/live/sip.mywebphone.xx")
> modparam("tls_mgm", "tls_method", "[sip.mywebphone.xx]SSLv23")
> modparam("tls_mgm", "verify_cert", "[sip.mywebphone.xx]1")
> modparam("tls_mgm", "require_cert", "[sip.mywebphone.xx]1")
>
> ### This is for MS-Teams direct route
> modparam("tls_mgm", "client_domain", "dom1.formsteams.com")
> modparam("tls_mgm", "certificate", "[dom1.formsteams.com
> ]/etc/letsencrypt/live/dom1.formsteams.com/cert.pem")
> modparam("tls_mgm", "private_key", "[dom1.formsteams.com
> ]/etc/letsencrypt/live/dom1.formsteams.com/privkey.pem")
> modparam("tls_mgm", "ca_list", "[dom1.formsteams.com
> ]/etc/letsencrypt/live/dom1.formsteams.com/fullchain.pem")
> modparam("tls_mgm", "ca_dir", "[dom1.formsteams.com]/etc/letsencrypt/live/
> dom1.formsteams.com")
> modparam("tls_mgm", "tls_method", "[dom1.formsteams.com]SSLv23")
> modparam("tls_mgm", "verify_cert", "[dom1.formsteams.com]1")
> modparam("tls_mgm", "require_cert", "[dom1.formsteams.com]1")
> modparam("tls_mgm", "client_sip_domain_avp", "tls_sip_dom")
>
> Looks like the initial handshake is fine when my server sends OPTIONS to
> MSTeams. There is a bug in the code according to the logs as shown below:
>
> opensips[10659]: CRITICAL:core:io_watch_add: #012>>> used fd map fd=142 is
> not present in fd_array
> (fd=142,type=19,flags=8003,data=0x7f825805ceb8)#012#012It seems you
> have hit a programming bug.#012Please help us make OpenSIPS better by
> reporting it at https://github.com/OpenSIPS/opensips/issues
> opensips[10659]: CRITICAL:core:io_watch_add: [TCP_main] check failed after
> successful fd add (fd=141,type=19,data=0x7f825804fd98,flags=1) already=0
> opensips[23993]: NOTICE:tls_wolfssl:verify_callback: depth = 1, verify
> success
> opensips[23993]: NOTICE:tls_wolfssl:verify_callback: depth = 0, verify
> success
> opensips[23993]: INFO:tls_wolfssl:_wolfssl_tls_async_connect: new TLS
> connection to 52.114.16.74:5061 established
> opensips[23993]: NOTICE:tls_wolfssl:verify_callback: depth = 1, verify
> success
> opensips[23993]: NOTICE:tls_wolfssl:verify_callback: depth = 0, verify
> success
> opensips[23995]: INFO:tls_wolfssl:_wolfssl_tls_async_connect: new TLS
> connection to 52.114.76.76:5061 established
>
>
> Regards,
> Jehanzaib
>
>
> On Wed, May 18, 2022 at 6:15 PM Bogdan-Andrei Iancu 
> wrote:
>
>> Hi Jehanzaib,
>>
>> The sequence for the MST TLS domains is wrong.
>>
>> For each TLS domain block, you need to start only with a server_domain
>> or client_domain - of course, different names. And for each domain you need
>> you set the matching conditions. See
>> https://opensips.org/html/docs/modules/3.2.x/tls_mgm.html#domains-param
>>
>> Basically something like:
>>
>> modparam("tls_mgm", "server_domain", "formsteams_server")
>> modparam("tls_mgm", "match_ip_address", "[formsteams_server]")
>> modparam("tls_mgm", "match_sip_domain", "[formsteams_server]")
>> modparam("tls_mgm", "certificate", "[formsteams_server].)
>> 
>>
>>
>> modparam("tls_mgm", "client_domain", "formsteams_client")
>> modparam("tls_mgm", "match_ip_address", "[formsteams_client]")
>> modparam("tls_mgm", "match_sip_domain", "[formsteams_client]")
>> modparam("tls_mgm", "certificate", "[formsteams_client].)
>> 
>>
>>
>> Best regards,
>>
>> Bogdan-Andrei Iancu
>>
>> OpenSIPS Founder and Developer
>>   https://www.opensips-solutions.com
>> OpenSIPS eBootcamp 23rd May - 3rd June 2022
>>   https://opensips.org/training/OpenSIPS_eBootcamp_2022/
>>
>> On 5/18/22 2:38 AM, Jehanzaib Younis wrote:
>>
>> Hi Bogdan,
>> That's the problem, when I try to add the client_domain I get an error.
>> Actually, I have a working config for webrtc but now I am adding a new
>> domain for MS teams direct route. In fact, any other domain gives an error.
>> If I disable MS Teams domain, the opensips do not give an error message and
>> my webrtc client can connect without any issue.
>>
>> loadmodule "tls_mgm.so"
>> modparam("tls_mgm", "tls_library", "wolfssl")
>>
>>  (WebRTC) Client
>> modparam("tls_mgm", "server_domain", "sip.mywebphone.xx")
>> modparam("tls_mgm", 

Re: [OpenSIPS-Users] JSON log format

[Răzvan Crainea]

Hi, Denis!

No plans yet, but feel free to open a feature request[1]. This way we 
can easily keep track of all requests.


[1] https://github.com/OpenSIPS/opensips/issues

Best regards,

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

On 3/21/22 14:26, Denis Alekseytsev wrote:

Hi,

Are there any plans to introduce JSON log format and systemd-journal 
integration?


Thanks,
Xaled

___
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] no TLS client domain found error

[Jehanzaib Younis]

Thank you Bogdan,
That helped a lot. As you mentioned I need to start only with server_domain
or client_domain.
Now I changed my config a bit as shown below:
 (WebRTC) Client
modparam("tls_mgm", "server_domain", "sip.mywebphone.xx")
modparam("tls_mgm", "certificate",
"[sip.mywebphone.xx]/etc/letsencrypt/live/sip.mywebphone.xx/cert.pem")
modparam("tls_mgm", "private_key",
"[sip.mywebphone.xx]/etc/letsencrypt/live/sip.mywebphone.xx/privkey.pem")
modparam("tls_mgm", "ca_list",
"[sip.mywebphone.xx]/etc/letsencrypt/live/sip.mywebphone.xx/fullchain.pem")
modparam("tls_mgm", "ca_dir",
"[sip.mywebphone.xx]/etc/letsencrypt/live/sip.mywebphone.xx")
modparam("tls_mgm", "tls_method", "[sip.mywebphone.xx]SSLv23")
modparam("tls_mgm", "verify_cert", "[sip.mywebphone.xx]1")
modparam("tls_mgm", "require_cert", "[sip.mywebphone.xx]1")

### This is for MS-Teams direct route
modparam("tls_mgm", "client_domain", "dom1.formsteams.com")
modparam("tls_mgm", "certificate", "[dom1.formsteams.com
]/etc/letsencrypt/live/dom1.formsteams.com/cert.pem")
modparam("tls_mgm", "private_key", "[dom1.formsteams.com
]/etc/letsencrypt/live/dom1.formsteams.com/privkey.pem")
modparam("tls_mgm", "ca_list", "[dom1.formsteams.com]/etc/letsencrypt/live/
dom1.formsteams.com/fullchain.pem")
modparam("tls_mgm", "ca_dir", "[dom1.formsteams.com]/etc/letsencrypt/live/
dom1.formsteams.com")
modparam("tls_mgm", "tls_method", "[dom1.formsteams.com]SSLv23")
modparam("tls_mgm", "verify_cert", "[dom1.formsteams.com]1")
modparam("tls_mgm", "require_cert", "[dom1.formsteams.com]1")
modparam("tls_mgm", "client_sip_domain_avp", "tls_sip_dom")

Looks like the initial handshake is fine when my server sends OPTIONS to
MSTeams. There is a bug in the code according to the logs as shown below:

opensips[10659]: CRITICAL:core:io_watch_add: #012>>> used fd map fd=142 is
not present in fd_array
(fd=142,type=19,flags=8003,data=0x7f825805ceb8)#012#012It seems you
have hit a programming bug.#012Please help us make OpenSIPS better by
reporting it at https://github.com/OpenSIPS/opensips/issues
opensips[10659]: CRITICAL:core:io_watch_add: [TCP_main] check failed after
successful fd add (fd=141,type=19,data=0x7f825804fd98,flags=1) already=0
opensips[23993]: NOTICE:tls_wolfssl:verify_callback: depth = 1, verify
success
opensips[23993]: NOTICE:tls_wolfssl:verify_callback: depth = 0, verify
success
opensips[23993]: INFO:tls_wolfssl:_wolfssl_tls_async_connect: new TLS
connection to 52.114.16.74:5061 established
opensips[23993]: NOTICE:tls_wolfssl:verify_callback: depth = 1, verify
success
opensips[23993]: NOTICE:tls_wolfssl:verify_callback: depth = 0, verify
success
opensips[23995]: INFO:tls_wolfssl:_wolfssl_tls_async_connect: new TLS
connection to 52.114.76.76:5061 established


Regards,
Jehanzaib


On Wed, May 18, 2022 at 6:15 PM Bogdan-Andrei Iancu 
wrote:

> Hi Jehanzaib,
>
> The sequence for the MST TLS domains is wrong.
>
> For each TLS domain block, you need to start only with a server_domain or
> client_domain - of course, different names. And for each domain you need
> you set the matching conditions. See
> https://opensips.org/html/docs/modules/3.2.x/tls_mgm.html#domains-param
>
> Basically something like:
>
> modparam("tls_mgm", "server_domain", "formsteams_server")
> modparam("tls_mgm", "match_ip_address", "[formsteams_server]")
> modparam("tls_mgm", "match_sip_domain", "[formsteams_server]")
> modparam("tls_mgm", "certificate", "[formsteams_server].)
> 
>
>
> modparam("tls_mgm", "client_domain", "formsteams_client")
> modparam("tls_mgm", "match_ip_address", "[formsteams_client]")
> modparam("tls_mgm", "match_sip_domain", "[formsteams_client]")
> modparam("tls_mgm", "certificate", "[formsteams_client].)
> 
>
>
> Best regards,
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>   https://www.opensips-solutions.com
> OpenSIPS eBootcamp 23rd May - 3rd June 2022
>   https://opensips.org/training/OpenSIPS_eBootcamp_2022/
>
> On 5/18/22 2:38 AM, Jehanzaib Younis wrote:
>
> Hi Bogdan,
> That's the problem, when I try to add the client_domain I get an error.
> Actually, I have a working config for webrtc but now I am adding a new
> domain for MS teams direct route. In fact, any other domain gives an error.
> If I disable MS Teams domain, the opensips do not give an error message and
> my webrtc client can connect without any issue.
>
> loadmodule "tls_mgm.so"
> modparam("tls_mgm", "tls_library", "wolfssl")
>
>  (WebRTC) Client
> modparam("tls_mgm", "server_domain", "sip.mywebphone.xx")
> modparam("tls_mgm", "certificate",
> "[sip.mywebphone.xx]/etc/letsencrypt/live/sip.mywebphone.xx/cert.pem")
> modparam("tls_mgm", "private_key",
> "[sip.mywebphone.xx]/etc/letsencrypt/live/sip.mywebphone.xx/privkey.pem")
> modparam("tls_mgm", "ca_list",
> "[sip.mywebphone.xx]/etc/letsencrypt/live/sip.mywebphone.xx/fullchain.pem")
> modparam("tls_mgm", "ca_dir",
> "[sip.mywebphone.xx]/etc/letsencrypt/live/sip.mywebphone.xx")
> modparam("tls_mgm", 

Re: [OpenSIPS-Users] no TLS client domain found error

[Ahmed Rehan]

1. certificates must be in any subdir of /etc/opensips/tls/

2. it should be a real files, not symlinks.


Check these settings




On Wed, May 18, 2022 at 11:15 AM Bogdan-Andrei Iancu 
wrote:

> Hi Jehanzaib,
>
> The sequence for the MST TLS domains is wrong.
>
> For each TLS domain block, you need to start only with a server_domain or
> client_domain - of course, different names. And for each domain you need
> you set the matching conditions. See
> https://opensips.org/html/docs/modules/3.2.x/tls_mgm.html#domains-param
>
> Basically something like:
>
> modparam("tls_mgm", "server_domain", "formsteams_server")
> modparam("tls_mgm", "match_ip_address", "[formsteams_server]")
> modparam("tls_mgm", "match_sip_domain", "[formsteams_server]")
> modparam("tls_mgm", "certificate", "[formsteams_server].)
> 
>
>
> modparam("tls_mgm", "client_domain", "formsteams_client")
> modparam("tls_mgm", "match_ip_address", "[formsteams_client]")
> modparam("tls_mgm", "match_sip_domain", "[formsteams_client]")
> modparam("tls_mgm", "certificate", "[formsteams_client].)
> 
>
>
> Best regards,
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>   https://www.opensips-solutions.com
> OpenSIPS eBootcamp 23rd May - 3rd June 2022
>   https://opensips.org/training/OpenSIPS_eBootcamp_2022/
>
> On 5/18/22 2:38 AM, Jehanzaib Younis wrote:
>
> Hi Bogdan,
> That's the problem, when I try to add the client_domain I get an error.
> Actually, I have a working config for webrtc but now I am adding a new
> domain for MS teams direct route. In fact, any other domain gives an error.
> If I disable MS Teams domain, the opensips do not give an error message and
> my webrtc client can connect without any issue.
>
> loadmodule "tls_mgm.so"
> modparam("tls_mgm", "tls_library", "wolfssl")
>
>  (WebRTC) Client
> modparam("tls_mgm", "server_domain", "sip.mywebphone.xx")
> modparam("tls_mgm", "certificate",
> "[sip.mywebphone.xx]/etc/letsencrypt/live/sip.mywebphone.xx/cert.pem")
> modparam("tls_mgm", "private_key",
> "[sip.mywebphone.xx]/etc/letsencrypt/live/sip.mywebphone.xx/privkey.pem")
> modparam("tls_mgm", "ca_list",
> "[sip.mywebphone.xx]/etc/letsencrypt/live/sip.mywebphone.xx/fullchain.pem")
> modparam("tls_mgm", "ca_dir",
> "[sip.mywebphone.xx]/etc/letsencrypt/live/sip.mywebphone.xx")
> modparam("tls_mgm", "tls_method", "[sip.mywebphone.xx]SSLv23")
> modparam("tls_mgm", "verify_cert", "[sip.mywebphone.xx]1")
> modparam("tls_mgm", "require_cert", "[sip.mywebphone.xx]1")
>
> ### This is for MS-Teams direct route
> modparam("tls_mgm", "server_domain", "dom1.formsteams.com")
> modparam("tls_mgm", "client_domain", "dom1.formsteams.com")
> modparam("tls_mgm", "certificate", "[dom1.formsteams.com
> ]/etc/letsencrypt/live/dom1.formsteams.com/cert.pem")
> modparam("tls_mgm", "private_key", "[dom1.formsteams.com
> ]/etc/letsencrypt/live/dom1.formsteams.com/privkey.pem")
> modparam("tls_mgm", "ca_list", "[dom1.formsteams.com
> ]/etc/letsencrypt/live/dom1.formsteams.com/fullchain.pem")
> modparam("tls_mgm", "ca_dir", "[dom1.formsteams.com]/etc/letsencrypt/live/
> dom1.formsteams.com")
> modparam("tls_mgm", "tls_method", "[dom1.formsteams.com]SSLv23")
> modparam("tls_mgm", "verify_cert", "[dom1.formsteams.com]1")
> modparam("tls_mgm", "require_cert", "[dom1.formsteams.com]1")
> modparam("tls_mgm", "client_sip_domain_avp", "tls_sip_dom")
>
> When i enable the MS-Teams direct route domain i get the below error:
> no certificate for tls domain ' dom1.formsteams.com ' defined
>
>
> Regards,
> Jehanzaib
>
>
> On Wed, May 18, 2022 at 3:04 AM Bogdan-Andrei Iancu 
> wrote:
>
>> Hi Jehanzaib,
>>
>> What are the TLS client domains you have defined in your tls_mgm module ?
>>
>> Regards,
>>
>> Bogdan-Andrei Iancu
>>
>> OpenSIPS Founder and Developer
>>   https://www.opensips-solutions.com
>> OpenSIPS eBootcamp 23rd May - 3rd June 2022
>>   https://opensips.org/training/OpenSIPS_eBootcamp_2022/
>>
>> On 5/17/22 4:32 PM, Jehanzaib Younis wrote:
>>
>> Hi,
>>
>> I am having trouble to send/receive OPTIONS to ms teams.
>> Using the dispatcher module. The socket is defined as tls:*mysbcip*:5061
>> Looks like when my opensips (3.2.x) tries to send OPTIONS. it is giving
>> me the following error
>>
>> ERROR:proto_tls:proto_tls_conn_init: no TLS client domain found
>> ERROR:core:tcp_conn_create: failed to do proto 3 specific init for conn
>> 0x7f00ef2a85a0
>> ERROR:core:tcp_async_connect: tcp_conn_create failed
>> ERROR:proto_tls:proto_tls_send: async TCP connect failed
>> ERROR:tm:msg_send: send() to 52.114.76.76:5061 for proto tls/3 failed
>> ERROR:tm:t_uac: attempt to send to '
>> sip:sip3.pstnhub.microsoft.com:5061;transport:tls' failed
>>
>> I am setting the Contact as 
>>
>> Looks like the client domain is used for outgoing TLS connection but no
>> idea which domain i need to add here. The socket is my opensips ip address.
>>
>> Has anyone seen a similar kind of behaviour?
>>
>> Thank you.
>>
>> Regards,
>> Jehanzaib
>>
>> 

Re: [OpenSIPS-Users] How to use old "opensipsctl avp add" with opensips-cli?

[Johan De Clercq]

Create  your own table in the db.
Then specify that as DB table in the module parameters (will avoid hassle
when you have to migrate)

Op wo 18 mei 2022 om 08:22 schreef Bela H :

> Hello,
>
> I want to set up a call forwarding and followed the instructions from the
> "Building telephony systems with OpenSIPS". However, this is a little bit
> outdated, the old opensipsctl was replaced by opensips-cli. How can I add
> an avp data into a usr_preferences table from opensips-cli?
> This was the old format: *opensipsctl avp add A_number callfwd 0 C_number*
>
> Cheers,
> Bela
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] How to use old "opensipsctl avp add" with opensips-cli?

[Jehanzaib Younis]

Hi Bela,
I think you can use (opensips-cli): database add avp command


Regards,
Jehanzaib


On Wed, May 18, 2022 at 6:20 PM Bela H  wrote:

> Hello,
>
> I want to set up a call forwarding and followed the instructions from the
> "Building telephony systems with OpenSIPS". However, this is a little bit
> outdated, the old opensipsctl was replaced by opensips-cli. How can I add
> an avp data into a usr_preferences table from opensips-cli?
> This was the old format: *opensipsctl avp add A_number callfwd 0 C_number*
>
> Cheers,
> Bela
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] OpenSIPS CP upgrade to 9.3.2

[Bogdan-Andrei Iancu]

Hi Bela,

OK, be sure the user you are using to log into CP has the "admin" 
permission on the cdrviewer tool . Check this via the Admin tools -> Access.


Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  https://www.opensips-solutions.com
OpenSIPS eBootcamp 23rd May - 3rd June 2022
  https://opensips.org/training/OpenSIPS_eBootcamp_2022/

On 5/18/22 12:25 AM, Bela H wrote:


Hi Bogdan,

I have re-installed the CP 9.3.2 but the results are same. Still 
missing CDR fields in the CDR Viewer and no gear icon anywhere only 
Users/Alias Management and System/Monit.


However, in the CDR details I can see the additional fields:

What did I wrong?

Cheers,

Bela

*From: *Bogdan-Andrei Iancu 
*Sent: *Wednesday, 18 May 2022 03:01
*To: *OpenSIPS users mailling list ; 
Bela H 

*Subject: *Re: [OpenSIPS-Users] OpenSIPS CP upgrade to 9.3.2

Hi Bela,

Does you CDRviewer look like this ?



See the gear box in the right upper corner.

And be sure that the 9.3.2 version is indeed displayed in the left 
upper corner.


Regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
   https://www.opensips-solutions.com  
OpenSIPS eBootcamp 23rd May - 3rd June 2022
   https://opensips.org/training/OpenSIPS_eBootcamp_2022/  


On 5/17/22 10:55 AM, Bela H wrote:

Hello,

What is the best method to upgrade the control panel from 8.3.2 to
9.3.2?

I had some extra fields e.g. in CDR viewer and disappeared after
9.3.2. It is in the file
/var/www/html/opensips-cp/config/tools/system/cdrviewer/local.inc.php
but not visible in the CDR viewer panel only in the detailed view
for each call.

Also I don’t see this gear icon Bogdan mentioned in the blog: Each
tool has its own Settings panel “accessible via the gear-icon in
the right side of the tool header”.

Cheers,

Bela



___

Users mailing list

Users@lists.opensips.org  

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




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

Re: [OpenSIPS-Users] OpenSIPS CP upgrade to 9.3.2

[Bela H]

Hi Bogdan,

I have re-installed the CP 9.3.2 but the results are same. Still missing CDR 
fields in the CDR Viewer and no gear icon anywhere only Users/Alias Management 
and System/Monit.

[cid:image002.png@01D86A99.33EE85C0]

However, in the CDR details I can see the additional fields:
[cid:image005.png@01D86A99.33EE85C0]

What did I wrong?

Cheers,
Bela

From: Bogdan-Andrei Iancu
Sent: Wednesday, 18 May 2022 03:01
To: OpenSIPS users mailling list; Bela 
H
Subject: Re: [OpenSIPS-Users] OpenSIPS CP upgrade to 9.3.2

Hi Bela,

Does you CDRviewer look like this ?

[cid:part1.1E9CE55B.28BF7076@opensips.org]

See the gear box in the right upper corner.

And be sure that the 9.3.2 version is indeed displayed in the left upper corner.

Regards,


Bogdan-Andrei Iancu



OpenSIPS Founder and Developer

  https://www.opensips-solutions.com

OpenSIPS eBootcamp 23rd May - 3rd June 2022

  https://opensips.org/training/OpenSIPS_eBootcamp_2022/
On 5/17/22 10:55 AM, Bela H wrote:

Hello,

What is the best method to upgrade the control panel from 8.3.2 to 9.3.2?
I had some extra fields e.g. in CDR viewer and disappeared after 9.3.2. It is 
in the file 
/var/www/html/opensips-cp/config/tools/system/cdrviewer/local.inc.php but not 
visible in the CDR viewer panel only in the detailed view for each call.

Also I don’t see this gear icon Bogdan mentioned in the blog: Each tool has its 
own Settings panel “accessible via the gear-icon in the right side of the tool 
header”.

Cheers,
Bela



___

Users mailing list

Users@lists.opensips.org

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


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

Re: [OpenSIPS-Users] OpenSIPS 3.2 + MySQL - do_accounting()

[Eugen Prieb via Users]

Hello,

his is attached SIP-Trace fpr examle call. This is permanent error by 
MySQL use.


--
Mit freundlichen Grüßen,
Best regards

Eugen Prieb

Am 01.03.2022 um 15:28 schrieb Bogdan-Andrei Iancu:

Hi Eugen,

What is the capture of the call that produced that CDR ? Can you 
reproduce it ?


Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  https://www.opensips-solutions.com
OpenSIPS eBootcamp
  https://www.opensips.org/Training/Bootcamp

On 2/23/22 11:21 PM, Eugen Prieb via Users wrote:

Hello,

I will collect all CDRs, also failled, in DB.

I see in log follow message:
Feb 23 21:58:33 opensips-32 /sbin/opensips[2623292]: 
CRITICAL:db_mysql:wrapper_single_mysql_stmt_execute: driver error 
(1048): Column 'to_tag' cannot be null


As MySQL is MariaDB 10.5.12 installed. Have you any idee?


U 2022/03/02 23:11:52.987389 + 176.199.99.57:61172 -> 95.111.248.176:5060

INVITE sip:+49301203@95.111.248.176 SIP/2.0
Via: SIP/2.0/UDP 
192.168.178.23:5060;branch=z9hG4bK006c3cd0eb98ec11b76f277d269fdfd3;rport
From: "PhonerLite" ;tag=2078659750
To: 
Call-ID: 006C3CD0-EB98-EC11-B76E-277D269FDFD3@192.168.178.23
CSeq: 5 INVITE
Contact: 
Content-Type: application/sdp
Allow: INVITE, OPTIONS, ACK, BYE, CANCEL, INFO, NOTIFY, MESSAGE, UPDATE
Max-Forwards: 69
Supported: 100rel, replaces, from-change
User-Agent: SIPPER for PhonerLite
P-Preferred-Identity: 
Content-Length:   417

v=0
o=- 615152551 1 IN IP4 192.168.178.23
s=SIPPER for PhonerLite
c=IN IP4 192.168.178.23
t=0 0
m=audio 5062 RTP/AVP 8 0 2 3 97 110 111 9 101
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:2 G726-32/8000
a=rtpmap:3 GSM/8000
a=rtpmap:97 iLBC/8000
a=rtpmap:110 speex/8000
a=rtpmap:111 speex/16000
a=rtpmap:9 G722/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ssrc:3874030355
a=sendrecv

U 2022/03/02 23:11:52.987526 + 95.111.248.176:5060 -> 176.199.99.57:61172

SIP/2.0 100 Trying
Via: SIP/2.0/UDP 
192.168.178.23:5060;received=176.199.99.57;branch=z9hG4bK006c3cd0eb98ec11b76f277d269fdfd3;rport=61172
To: 
From: "PhonerLite" ;tag=2078659750
Call-ID: 006C3CD0-EB98-EC11-B76E-277D269FDFD3@192.168.178.23
CSeq: 5 INVITE
Server:Class5 OpenSIPS
Content-Length: 0


U 2022/03/02 23:11:52.994924 + 95.111.248.176:5060 -> 176.199.99.57:61172

SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP 
192.168.178.23:5060;received=176.199.99.57;branch=z9hG4bK006c3cd0eb98ec11b76f277d269fdfd3;rport=61172
To: ;tag=28de.97201e0cc1f84b5f4058acdfba4ae5bf
From: "PhonerLite" ;tag=2078659750
Call-ID: 006C3CD0-EB98-EC11-B76E-277D269FDFD3@192.168.178.23
CSeq: 5 INVITE
Proxy-Authenticate: Digest realm="95.111.248.176", 
nonce="Adg2o5qqx5zG1rXomjs4ijFivSdNo2tetQO2qu9/LRYA"
Server:Class5 OpenSIPS
Content-Length: 0


U 2022/03/02 23:11:53.531998 + 176.199.99.57:61172 -> 95.111.248.176:5060

INVITE sip:+49301203@95.111.248.176 SIP/2.0
Via: SIP/2.0/UDP 
192.168.178.23:5060;branch=z9hG4bK006c3cd0eb98ec11b770277d269fdfd3;rport
From: "PhonerLite" ;tag=2078659750
To: 
Call-ID: 006C3CD0-EB98-EC11-B76E-277D269FDFD3@192.168.178.23
CSeq: 6 INVITE
Contact: 
Proxy-Authorization: Digest username="4901179322878", realm="95.111.248.176", 
nonce="Adg2o5qqx5zG1rXomjs4ijFivSdNo2tetQO2qu9/LRYA", 
uri="sip:+49301203@95.111.248.176", 
response="f8bbe4488f0bf527d6c21038c021e434", algorithm=MD5
Content-Type: application/sdp
Allow: INVITE, OPTIONS, ACK, BYE, CANCEL, INFO, NOTIFY, MESSAGE, UPDATE
Max-Forwards: 69
Supported: 100rel, replaces, from-change
User-Agent: SIPPER for PhonerLite
P-Preferred-Identity: 
Content-Length:   417

v=0
o=- 615152551 1 IN IP4 192.168.178.23
s=SIPPER for PhonerLite
c=IN IP4 192.168.178.23
t=0 0
m=audio 5062 RTP/AVP 8 0 2 3 97 110 111 9 101
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:2 G726-32/8000
a=rtpmap:3 GSM/8000
a=rtpmap:97 iLBC/8000
a=rtpmap:110 speex/8000
a=rtpmap:111 speex/16000
a=rtpmap:9 G722/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ssrc:3874030355
a=sendrecv

U 2022/03/02 23:11:53.532054 + 95.111.248.176:5060 -> 176.199.99.57:61172

SIP/2.0 100 Trying
Via: SIP/2.0/UDP 
192.168.178.23:5060;received=176.199.99.57;branch=z9hG4bK006c3cd0eb98ec11b770277d269fdfd3;rport=61172
To: 
From: "PhonerLite" ;tag=2078659750
Call-ID: 006C3CD0-EB98-EC11-B76E-277D269FDFD3@192.168.178.23
CSeq: 6 INVITE
Server:Class5 OpenSIPS
Content-Length: 0


U 2022/03/02 23:11:53.882219 + 95.111.248.176:5060 -> 176.199.99.57:61172

SIP/2.0 100 Giving it a try
Via: SIP/2.0/UDP 
192.168.178.23:5060;received=176.199.99.57;branch=z9hG4bK006c3cd0eb98ec11b770277d269fdfd3;rport=61172
To: 
From: "PhonerLite" ;tag=2078659750
Call-ID: 006C3CD0-EB98-EC11-B76E-277D269FDFD3@192.168.178.23
CSeq: 6 INVITE
Server:Class5 OpenSIPS
Content-Length: 0


U 2022/03/02 23:11:53.884734 + 95.111.248.176:5060 -> 127.0.0.1:5080

INVITE sip:49301203@127.0.0.1:5080 SIP/2.0
Record-Route: 
Via: SIP/2.0/UDP 95.111.248.176:5060;branch=z9hG4bK30f3.7d39fdf6.0
Via: SIP/2.0/UDP 

[OpenSIPS-Users] pjsip patch supporting sip 3xx embedded headers

[Di-Shi Sun via Users]

All,

I committed a pjsip patch pull request in pjsip project to support SIP 3xx 
embedded header. It inserts stand-alone SIP headers based on SIP 3xx Contact 
header URI header parameters into the redirect SIP INVITE messages. It is a 
common feature supported by any SIP implementations, such as Metaswitch, Oracle 
SBC, Ribbon, etc. It should solve the issue that it is difficult to pass useful 
information using SIP 3xx in Asterisk. If anybody wants to try, the patch link 
is attached.

https://github.com/pjsip/pjproject/pull/3085/commits/b065eef9913df15757808b352c2ce9054809

To use this patch, please follow the steps

  1.  Download Asterisk 18 source code
  2.  Run “./configure --with-pjproject-bundled --with-jansson-bundled”.
  3.  Apply the patch to 
./third-party/pjproject/source/pjsip/src/pjsip-ua/sip_inv.c
  4.  Build/install/run Asterisk
  5.  In pjsip.conf, the redirect server endpoint should be configured with 
“redirect_method=uri_pjsip”
  6.  When the redirect server returns a SIP 3xx with Contact header, say 
“Contact: ;q=0.99”, the redirected SIP 
INVITE message should contain “Test: test” header.

Please me know if you have any questions.

Sincerely,

Di-Shi Sun.




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

[OpenSIPS-Users] How to use old "opensipsctl avp add" with opensips-cli?

[Bela H]

Hello,

I want to set up a call forwarding and followed the instructions from the 
"Building telephony systems with OpenSIPS". However, this is a little bit 
outdated, the old opensipsctl was replaced by opensips-cli. How can I add an 
avp data into a usr_preferences table from opensips-cli?
This was the old format: opensipsctl avp add A_number callfwd 0 C_number

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

[OpenSIPS-Users] JSON log format

[Denis Alekseytsev]

Hi,

Are there any plans to introduce JSON log format and systemd-journal 
integration?

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

Re: [OpenSIPS-Users] no TLS client domain found error

[Bogdan-Andrei Iancu]

Hi Jehanzaib,

The sequence for the MST TLS domains is wrong.

For each TLS domain block, you need to start only with a server_domain 
or client_domain - of course, different names. And for each domain you 
need you set the matching conditions. See 
https://opensips.org/html/docs/modules/3.2.x/tls_mgm.html#domains-param


Basically something like:

modparam("tls_mgm", "server_domain", "formsteams_server")
modparam("tls_mgm", "match_ip_address", "[formsteams_server]")
modparam("tls_mgm", "match_sip_domain", "[formsteams_server]")
modparam("tls_mgm", "certificate", "[formsteams_server].)



modparam("tls_mgm", "client_domain", "formsteams_client")
modparam("tls_mgm", "match_ip_address", "[formsteams_client]")
modparam("tls_mgm", "match_sip_domain", "[formsteams_client]")
modparam("tls_mgm", "certificate", "[formsteams_client].)



Best regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  https://www.opensips-solutions.com
OpenSIPS eBootcamp 23rd May - 3rd June 2022
  https://opensips.org/training/OpenSIPS_eBootcamp_2022/

On 5/18/22 2:38 AM, Jehanzaib Younis wrote:

Hi Bogdan,
That's the problem, when I try to add the client_domain I get an 
error. Actually, I have a working config for webrtc but now I am 
adding a new domain for MS teams direct route. In fact, any other 
domain gives an error. If I disable MS Teams domain, the opensips do 
not give an error message and my webrtc client can connect without any 
issue.


loadmodule "tls_mgm.so"
modparam("tls_mgm", "tls_library", "wolfssl")

 (WebRTC) Client
modparam("tls_mgm", "server_domain", "sip.mywebphone.xx")
modparam("tls_mgm", "certificate", 
"[sip.mywebphone.xx]/etc/letsencrypt/live/sip.mywebphone.xx/cert.pem")
modparam("tls_mgm", "private_key", 
"[sip.mywebphone.xx]/etc/letsencrypt/live/sip.mywebphone.xx/privkey.pem")
modparam("tls_mgm", "ca_list", 
"[sip.mywebphone.xx]/etc/letsencrypt/live/sip.mywebphone.xx/fullchain.pem")
modparam("tls_mgm", "ca_dir", 
"[sip.mywebphone.xx]/etc/letsencrypt/live/sip.mywebphone.xx")

modparam("tls_mgm", "tls_method", "[sip.mywebphone.xx]SSLv23")
modparam("tls_mgm", "verify_cert", "[sip.mywebphone.xx]1")
modparam("tls_mgm", "require_cert", "[sip.mywebphone.xx]1")

### This is for MS-Teams direct route
modparam("tls_mgm", "server_domain", "dom1.formsteams.com 
")
modparam("tls_mgm", "client_domain", "dom1.formsteams.com 
")
modparam("tls_mgm", "certificate", "[dom1.formsteams.com 
]/etc/letsencrypt/live/dom1.formsteams.com/cert.pem 
")
modparam("tls_mgm", "private_key", "[dom1.formsteams.com 
]/etc/letsencrypt/live/dom1.formsteams.com/privkey.pem 
")
modparam("tls_mgm", "ca_list", "[dom1.formsteams.com 
]/etc/letsencrypt/live/dom1.formsteams.com/fullchain.pem 
")
modparam("tls_mgm", "ca_dir", "[dom1.formsteams.com 
]/etc/letsencrypt/live/dom1.formsteams.com 
")
modparam("tls_mgm", "tls_method", "[dom1.formsteams.com 
]SSLv23")
modparam("tls_mgm", "verify_cert", "[dom1.formsteams.com 
]1")
modparam("tls_mgm", "require_cert", "[dom1.formsteams.com 
]1")

modparam("tls_mgm", "client_sip_domain_avp", "tls_sip_dom")

When i enable the MS-Teams direct route domain i get the below error:
no certificate for tls domain ' dom1.formsteams.com 
 ' defined



Regards,
Jehanzaib


On Wed, May 18, 2022 at 3:04 AM Bogdan-Andrei Iancu 
mailto:bog...@opensips.org>> wrote:


Hi Jehanzaib,

What are the TLS client domains you have defined in your tls_mgm
module ?

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com  
OpenSIPS eBootcamp 23rd May - 3rd June 2022
   https://opensips.org/training/OpenSIPS_eBootcamp_2022/  


On 5/17/22 4:32 PM, Jehanzaib Younis wrote:

Hi,

I am having trouble to send/receive OPTIONS to ms teams.
Using the dispatcher module. The socket is defined
as tls:*mysbcip*:5061
Looks like when my opensips (3.2.x) tries to send OPTIONS. it is
giving me the following error
*
*
ERROR:proto_tls:proto_tls_conn_init: no TLS client domain found
ERROR:core:tcp_conn_create: failed to do proto 3 specific init
for conn 0x7f00ef2a85a0
ERROR:core:tcp_async_connect: tcp_conn_create failed
ERROR:proto_tls:proto_tls_send: async TCP connect failed
ERROR:tm:msg_send: send() to 52.114.76.76:5061
 for proto tls/3 failed
ERROR:tm:t_uac: attempt to send to