Thank you everyone for your help and comments with this.
I can't explain this but it has now started working. I had no luck with
tlsv1 or tlsv1_2 but using sslv23 does work.
The strange thing is, I tried that before and it DIDN'T work. I'm not
sure why.
Apologies for my delay in responding to th
> "JC" == Joshua C Colp writes:
JC> To be specific, this is in PJSIP land. There was no insisting or anything
JC> and it wasn't a decision we originally made. It's the way that Teluu
JC> implemented the TLS transport in PJSIP and since we use PJSIP then it
JC> applies to us.
my recall is mor
On Thu, Dec 2, 2021 at 12:50 PM Dan Jenkins wrote:
> As far as I'm aware Josh, it doesnt stop a call from happening - I've had
> the same "errors" pop up when using Twilio and Simwood but calls continue
> just fine.
>
>From the reading of the code[1] it would fail verification, so it depends
on
As far as I'm aware Josh, it doesnt stop a call from happening - I've had
the same "errors" pop up when using Twilio and Simwood but calls continue
just fine.
On Thu, Dec 2, 2021 at 2:30 PM Joshua C. Colp wrote:
> On Thu, Dec 2, 2021 at 10:18 AM James Cloos wrote:
>
>> > "KT" == Kingsley Ta
On Thu, Dec 2, 2021 at 10:18 AM James Cloos wrote:
> > "KT" == Kingsley Tart writes:
>
> KT> I can't get Asterisk to send a SIP call to Twilio over TLS
> KT> because it complains about Twilio's wildcard certificate.
>
> the sip rfc claims that wildcard certs should be invalid for sip.
>
> di
> "KT" == Kingsley Tart writes:
KT> I can't get Asterisk to send a SIP call to Twilio over TLS
KT> because it complains about Twilio's wildcard certificate.
the sip rfc claims that wildcard certs should be invalid for sip.
digium insisted on following that advise as set in stone, and so
ast
It shouldnt stop the call from happening. It will be something else... up
your debugging level and see what else you get
Lots of providers go against this part of the spec but I've run Asterisk 18
with twilio over sip over tls and everything worked, it just spat out the
error line
On Thu, Dec 2,
On 02.12.21 01:21, Kingsley Tart wrote:
No I haven't, but if I did I suspect they would take no notice. Twilio
is a big provider who do what they do because they can.
And I can see why they do this, because customers can set up their own
SIP trunks on their system with their unique hostname, so
On Wed, 2021-12-01 at 22:54 +0100, Antony Stone wrote:
> So, https://datatracker.ietf.org/doc/html/rfc5922#section-7.2 does seem
> pretty
> clear about this. "Implementations MUST NOT match any form of wildcard"
>
> Have you contacted the provider who is using a wildcard certificate in this
>
That particular error does not prevent it from connecting (at least it doesn't
in the 18.x I'm using with my own wildcard certs). The problem may be
somewhere else -- for example Twilio might require TLS 1.2 or later -- so try
adding in
method=tlsv1_2
to you transport configuration. If that
On Wednesday 01 December 2021 at 22:43:47, Kingsley Tart wrote:
> On Wed, 2021-12-01 at 21:49 +0100, Antony Stone wrote:
> >
> > What is the exact "complaint"?
> [Nov 29 16:44:08] ERROR[25803] pjproject: tlsc0x7f1c74246778 RFC
> 5922 (section 7.2) does not allow TLS wildcard certificat
On Wed, 2021-12-01 at 21:49 +0100, Antony Stone wrote:
> On Wednesday 01 December 2021 at 21:39:52, Kingsley Tart wrote:
>
> > Hi,
> >
> > I can't get Asterisk to send a SIP call to Twilio over TLS because
> > it
> > complains about Twilio's wildcard certificate.
>
> What is the exact "complaint
On Wednesday 01 December 2021 at 21:39:52, Kingsley Tart wrote:
> Hi,
>
> I can't get Asterisk to send a SIP call to Twilio over TLS because it
> complains about Twilio's wildcard certificate.
What is the exact "complaint"?
> Is there a way round this?
Maybe, once we know what the error messag
Hi,
I can't get Asterisk to send a SIP call to Twilio over TLS because it
complains about Twilio's wildcard certificate.
This is with Asterisk 18.8.0 and PJSIP 2.10
pjsip show transport shows me this:
allow_reload : false
async_operations : 1
bind
14 matches
Mail list logo
