I apologize if this is a duplicate post - ran into some errors while
posting the first time.
Thanks Razvan. Installing cryptography fixed that issue. I was able to run
-x tls rootCA and userCERT, and create the certificates.
However, when running Opensips I get this error now:
Hi,
I’m currently attempting to take an INVITE from an Asterisk server that is
requesting an extension number, perform dbalias lookups to have extensions
turned into sip users (x1000 -> test_hardphone) and then do location lookups on
those sip users. There can be multiple sip users for each
Hi,
I'm trying to set up two tls domains for two sets of clients. First one
requires TLSv1 (higher not supported), and the other one requires TLSv1_2
or higher.
Right now the domain with tlsv1 is active on 5061 and has no issues. I'm
trying to add the second domain.
As far as I understand (do not
Thanks Razvan. Installing the cryptography module fixed it - I was able to
run both -x tls rootCA and userCERT, and create the certificates.
However, when I start Opensips, I get the following error:
ERROR:tls_wolfssl:load_private_key: key
'/usr/local/etc/opensips/tls/server/privkey.pem' does not
Can you double check whether you have the python-openssl or
python-cryptography libraries?
Best regards,
Răzvan Crainea
OpenSIPS Core Developer / SIPhub CTO
http://www.opensips-solutions.com / https://www.siphub.com
On 9/26/23 16:38, L S wrote:
I'm trying to create certificates using
I'm trying to create certificates using opensips-cli:
opensips-cli - f /usr/local/etc/opensips-cli.cfg -d -x tls rootCA
DEBUG: Skipping module 'tls' - excluded on purpose
ERROR: No module 'tls' loaded
Trying to find out why I am getting this message now - it used to work
fine. All other modules
Hi,
Following the abundance of emails and GH tickets from B.Prathibha, I
want to point out some important aspects of the code of conduct here:
1) BEFORE considering the community help, be sure you checked the
available documentation and did any online research on the matter
2) BEFORE
opensips version: 3.3
Error:
I am using websocket. I am using the letsencrypt certifcate. When I
connected from web to web and when verify_cert is 1 and require_cert is 1,
get the following errors:
ERROR:tls_openssl:openssl_tls_accept: New TLS connection from
14.139.183.221:53946 failed to
Thanks @Michel,
hep socket is indeed the local host.
step I missed, installing heplify agent on the opensips system.
Forward the received packets towards Homer :)
case closed.
Vincent
Op di 26 sep 2023 om 08:21 schreef Michel crans :
> If you're not seeing any packets received on the Homer
When user2 accepts the call, the above error occurs.
On Tue, 26 Sept 2023 at 14:08, Prathibha B wrote:
> I'm getting this error in log:
>
> New TLS connection from 45.33.68.226:42316 failed to accept
> ERROR:tls_openssl:tls_print_errstack: TLS errstack: error:0AEA:SSL
> routines::callback
I'm getting this error in log:
New TLS connection from 45.33.68.226:42316 failed to accept
ERROR:tls_openssl:tls_print_errstack: TLS errstack: error:0AEA:SSL
routines::callback failed
ERROR:proto_wss:wss_read_req: cannot fix read connection
On Tue, 26 Sept 2023 at 13:41, Prathibha B wrote:
Hi Ray,
The "tcp_accept_aliases" should be harmless if there is no "alias" param
received in the incoming requests. If no such parameter is pushed by the
end-devices, there is 0 impact.
And indeed, this has a really ugly side effect for the (CG)NAT'd
devices. But let's give it a try,
I've created two users and they are registered to opensips. When I try to
connect, user 1 to user 2, I get temporarily unavailable. Config file is
attached with this email.
--
Regards,
B.Prathibha
#
# OpenSIPS residential configuration script
# by OpenSIPS Solutions
#
# Please refer to the
I am using websocket. I am trying web to web call.
On Tue, 26 Sept 2023 at 13:40, Prathibha B wrote:
> I've created two users and they are registered to opensips. When I try to
> connect, user 1 to user 2, I get temporarily unavailable. Config file is
> attached with this email.
>
> --
>
If you're not seeing any packets received on the Homer server, there could
be several reasons for this issue. Let's go through some troubleshooting
steps:
1.
Check Network Connectivity:
- Ensure that there is network connectivity between your OpenSIPS server
and the Homer server.
15 matches
Mail list logo