On 7/7/19 11:55 AM, Michael Maier wrote:
> On 06.07.19 at 22:16 hwilmer wrote:
>> Is there an advantage to using pjsip? What's needed for easybell with pjsip?
>
> For easybell, I don't know of any advantage. But that's not very reliable,
> because I'm using easybell for dedicated requirements
On Sun, Jul 7, 2019, at 11:17 AM, hw wrote:
>
> Thanks, setting 'tlscafile=/etc/pki/tls/certs/ca-bundle.crt' seems to do
> the trick. However:
>
> First I set 'tlsdontverifyserver=no' and issued a 'sip reload'. There
> was no error message. I found that suspicious and restarted asterisk,
On 7/6/19 7:23 PM, Michael Maier wrote:
On 06.07.19 at 12:16 hwilmer wrote:
On 7/6/19 10:40 AM, Michael Maier wrote:
On 05.07.19 at 22:02 hw wrote:
openssl verify -CAfile ca.pem asterisk.pem
asterisk.pem: OK
When I set tlsdontverifyserver=yes, it works (i. e. asterisk registers
to the SIP
On 06.07.19 at 22:16 hwilmer wrote:
Is there an advantage to using pjsip? What's needed for easybell with pjsip?
For easybell, I don't know of any advantage. But that's not very reliable, because I'm using easybell for dedicated requirements only. I'm
considering chan_sip legacy. I wouldn't
On 06.07.19 at 12:16 hwilmer wrote:
> On 7/6/19 10:40 AM, Michael Maier wrote:
>> On 05.07.19 at 22:02 hw wrote:
>>>
>>> openssl verify -CAfile ca.pem asterisk.pem
>>> asterisk.pem: OK
>>>
>>>
>>> When I set tlsdontverifyserver=yes, it works (i. e. asterisk registers
>>> to the SIP provider and
On 7/6/19 10:40 AM, Michael Maier wrote:
> On 05.07.19 at 22:02 hw wrote:
>>
>> openssl verify -CAfile ca.pem asterisk.pem
>> asterisk.pem: OK
>>
>>
>> When I set tlsdontverifyserver=yes, it works (i. e. asterisk registers
>> to the SIP provider and there is no error message). Otherwise I'm
>>
On 05.07.19 at 22:02 hw wrote:
>
> openssl verify -CAfile ca.pem asterisk.pem
> asterisk.pem: OK
>
>
> When I set tlsdontverifyserver=yes, it works (i. e. asterisk registers
> to the SIP provider and there is no error message). Otherwise I'm
> getting the error message and asterisk does not
On 7/5/19 9:32 PM, John Runyon wrote:
On Fri, 5 Jul 2019 at 14:28, hw mailto:h...@gc-24.de>> wrote:
I thought about that and checked the configuration I've been using to
create the certificate, and I can't see anywhere that it would expire
earlier than after 3650 days. Is there
On 7/5/19 9:32 PM, John Runyon wrote:
On Fri, 5 Jul 2019 at 14:28, hw mailto:h...@gc-24.de>> wrote:
I thought about that and checked the configuration I've been using to
create the certificate, and I can't see anywhere that it would expire
earlier than after 3650 days. Is there
On Fri, 5 Jul 2019 at 14:28, hw wrote:
> I thought about that and checked the configuration I've been using to
> create the certificate, and I can't see anywhere that it would expire
> earlier than after 3650 days. Is there another way to check this?
>
openssl verify -CAfile ca.crt server.crt
On 7/5/19 9:22 PM, Steve Murphy wrote:
hw--
I see this kind of behavior when the certificate expires... you've
probably checked this, but sometimes we
miss little details like that.
I thought about that and checked the configuration I've been using to
create the certificate, and I can't see
hw--
I see this kind of behavior when the certificate expires... you've probably
checked this, but sometimes we
miss little details like that.
murf
On Fri, Jul 5, 2019 at 1:14 PM hw wrote:
> On 7/5/19 10:50 AM, Doug Lytle wrote:
> > On 7/4/19 6:40 PM, hw wrote:
> >> This has again, and for no
On 7/5/19 10:50 AM, Doug Lytle wrote:
On 7/4/19 6:40 PM, hw wrote:
This has again, and for no reason, ceased to work again after
restarting asterisk. No matter what I try, I can't create a
certificate asterisk
would verify.
Have you considered using LetsEncrypt for a valid certificate?
On 7/4/19 6:40 PM, hw wrote:
This has again, and for no reason, ceased to work again after
restarting asterisk. No matter what I try, I can't create a
certificate asterisk
would verify.
Have you considered using LetsEncrypt for a valid certificate?
Doug
--
14 matches
Mail list logo
