'/etc/init.d/dahdi [status,start,stop,restart]' works under a systemd
system, as stated in /etc/init.d/README:
Note that traditional init scripts continue to function on a systemd
system. An init script /etc/rc.d/init.d/foobar is implicitly mapped
into a service unit foobar.service during
with the Cisco 7940/7960 phones that
populate most of our offices.
Thanks,
--Ruisheng
On Fri, Feb 12, 2021 at 3:13 PM Ruisheng Peng wrote:
> Thanks Joshua for the tip re using hostname rather than IP address when
> configuring the phone. It worked nicely on the linphone on my macbookp
in office.
Thanks,
--Ruisheng
On Fri, Feb 12, 2021 at 4:48 AM Joshua C. Colp wrote:
> On Thu, Feb 11, 2021 at 9:01 PM Ruisheng Peng
> wrote:
>
>> Sorry, my bad. I failed to change the transport to tls on the provision
>> for the hardphone, nor did change the transport
wrote:
> On Mon, Feb 8, 2021 at 6:14 PM Ruisheng Peng wrote:
>
>> Thanks Jashua for the suggestion. To find out if the issue was only
>> limited to the softphone that was using tls transport (SOFTPHONE_B on ext
>> 103, a linphone running off my MBP), I also turned one of t
nsion (sets, 100, 3) exited non-zero on
'PJSIP/f30B0B02-0016'
<--- Transmitting SIP request (499 bytes) to UDP:128.171.77.48:5060 --->
BYE sip:f30B0B02@128.171.77.48:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 128.171.77.23:5060
;rport;branch=z9hG4bKPje24627f6-0b3b-4b65-ab88-93
Hi all,
I managed to get tls transport going with asterisk 16.14.0, and set one
handset (SOFTPHONE_B) to use the transport. I have set up a few other
handsets (both soft and hard) to use udp and tcp transports:
voip1*CLI> pjsip show endpoints
Endpoint:
I/OAuth:
Aor:
wrote:
> Hi,
>
> On 1/26/2021 3:12 PM, Ruisheng Peng wrote:
>
> Transport: transport-tls: cert_file /home/asterisk/certs/asterisk.crt is
> either missing or not readable
>
>
> This error means that the file either does not exist or that Asterisk is
> not able to ope
established.
On Fri, Jan 29, 2021 at 9:42 PM Michael Maier wrote:
>
> On 29.01.21 at 22:33 Ruisheng Peng wrote:
> > Thanks for the detailed explanation Michael.
> >
> > I stop the current asterisk process (started by systemd), and restart it
> as
> > asterisk:
/keys/privkey.pem
method = tlsv1_2
allow_reload = true
Not sure what was the nature of the problem. Maybe Selinux? There was no
complaint from that department though.
Thanks for the help and suggestions,
--Ruisheng
On Fri, Jan 29, 2021 at 11:33 AM Ruisheng Peng wrote:
> Tha
tls transport is not established in the end. Only the two hard phones
using udp transport and a softphone using tcp transport are registered.
Thanks,
--Ruisheng
On Thu, Jan 28, 2021 at 7:42 PM Michael Maier wrote:
>
> On 27.01.21 at 22:57 Ruisheng Peng wrote:
> > Thanks Michael
Tichy wrote:
> On Tue, Jan 26, 2021 at 10:12:22AM -1000, Ruisheng Peng wrote:
>
> > The self-sign asterisk.crt:
>
> I saved that file in "x.crt".
>
> openssl x509 -in x.crt -noout -text
>
>
>RSA Public-Key: (1024 bit)
>
>
>
&
y
allow_reload = true
In the end the tls transport was still not installed for SOFTPHONE_B:
Endpoint: f30A0A01 Not in
use0 of inf
InAuth: f30A0A01/f30A0A01
Aor: f30A0A01 1
Contact:
Hi,
I'm experimenting with Asterisk-16.14.0 on a CentOS7 box, and run into
problems loading the SSL certificate to establish transport-tls. Tried
self-signed certificate generated with ast_tls_cert under contrib/scripts
and the one issued by Letsencrypt, both would bomb out with a parsing
Hi,
I'm experimenting with Asterisk-16.14.0 on a CentOS7 box, and run into
problems loading the SSL certificate to establish transport-tls. Tried
self-signed certificate generated with ast_tls_cert under contrib/scripts
and the one issued by Letsencrypt, both would bomb out with a parsing
14 matches
Mail list logo
