› VitalPBX Community Support › General Discussion › Some questions about pbx and gui.
- This topic has 14 replies, 3 voices, and was last updated 10 months, 2 weeks ago by
jrosetto.
- Post
-
- March 27, 2018 at 2:05 am
1) that product have irc channel?
2)In vps script maybe need add:
yum -y install NetworkManager
systemctl enable NetworkManager
systemctl start NetworkManager
3) i have a trouble, i want use pbx in vps with chan-sip only (no pjsip) + tls only on 5061 port + srtp. how to do it? i try config via gui but have no idea how to do it.
0
- Replies
-
- March 27, 2018 at 6:27 am
So, i found a bug!
when i use letsencrypt certificate it works well with webgui but not work when i use chan-sip tls.
tcp 0 0 127.0.0.1:5063 0.0.0.0:* LISTEN 1369/asterisk
tcp 0 0 127.0.0.1:5062 0.0.0.0:* LISTEN 1369/asterisk
udp 0 0 0.0.0.0:5060 0.0.0.0:* 1369/asterisk
udp 0 0 127.0.0.1:5062 0.0.0.0:* 1369/asteriskbut if i use self-signed certificate it works well.
tcp 0 0 127.0.0.1:5063 0.0.0.0:* LISTEN 1369/asterisk
tcp 0 0 0.0.0.0:5061 0.0.0.0:* LISTEN 1369/asterisk
tcp 0 0 127.0.0.1:5062 0.0.0.0:* LISTEN 1369/asterisk
udp 4864 0 0.0.0.0:5060 0.0.0.0:* 1369/asterisk
udp 0 0 127.0.0.1:5062 0.0.0.0:* 1369/asterisk0- March 27, 2018 at 8:40 am
not working config:
tlscertfile=/usr/share/ombutel/certificates/pbx2.raven.kz/bundle.pem
tlscafile=/usr/share/ombutel/certificates/pbx2.raven.kz/chain.pemworking config(self-signed) :
tlscertfile=/usr/share/ombutel/certificates/pbx.raven.kz.pem
tlscafile=/usr/share/ombutel/certificates/ca.crt0- April 1, 2018 at 9:51 pm
- March 6, 2020 at 3:56 pm
DId you ever get anywhere with this. I would like to use TLS with letsencrypt but after generating the cert the PBX isn’t listening on 5063 anymore for PJSIP TLS. 5062 is unaffected.
0- March 6, 2020 at 4:01 pm
- March 6, 2020 at 4:12 pm
Created the profile PJSIP and enabled TLS but running ‘lsof -i -P -n | grep 5063’ still comes up blank. Anything else I need to do?
0- March 6, 2020 at 4:23 pm
- March 6, 2020 at 4:38 pm
Getting closer… Here are the errors
[2020-03-06 11:35:39] ERROR[9044]: config_options.c:798 aco_process_var: Error parsing method=tlsv3 at line 49 of /etc/asterisk/ombutel/pjsip__20-transport.conf
[2020-03-06 11:35:39] ERROR[9044]: res_sorcery_config.c:407 sorcery_config_internal_load: Could not create an object of type ‘transport’ with id ‘transport-tls’ from configuration file ‘pjsip.conf’
[2020-03-06 11:35:39] NOTICE[9044]: res_sorcery_config.c:418 sorcery_config_internal_load: Retaining existing configuration for object of type ‘transport’ with id ‘transport-tls’That line in the config is going to
[transport-wss]
It is listening at this point but I am unable to register over TLS.
0- March 6, 2020 at 4:50 pm
- March 6, 2020 at 4:52 pm
- March 6, 2020 at 4:53 pm
- March 6, 2020 at 5:05 pm
That stopped the errors and I can register on the phone side. But on the asterisk side the extension shows as unavailable.
0- March 6, 2020 at 5:08 pm
- March 6, 2020 at 5:12 pm
Ah I got it. I had to change the profile to the new one I created on the extension. Everything seems to be working as intended. Thanks for your help. I owe you one.
0
- You must be logged in to reply to this topic.