TLS trunk to an unsupported provider

[nicedoggie]

I have tried to enable tls under "options" and uploaded the letsencrypt .pem file. The provider is saying that they are not getting a tls connection request from my 3cx.
I see this in my event log:
Call or Registration to BMU_BlueSharkDigital_TG1 has failed. sip:[email protected]:5060;transport=TLS replied: 404 Not found; from IP:64.147.93.179:5060

Does this indicate that TLS is trying to connect?

Thanks!

 

[nicedoggie]

I received a .pem file from the tls trunk provider and when I try to upload it, the certificate always shows root_cert_10000.pem as the certificate in use under the trunk/options screen, not the .pem file that I "uploaded". It doesn't seem to actually upload the file. I tried deleting the trunk and doing it over and that didn't change anything.

 

[Evolute IT]

I received a .pem file from the tls trunk provider and when I try to upload it, the certificate always shows root_cert_10000.pem as the certificate in use under the trunk/options screen, not the .pem file that I "uploaded". It doesn't seem to actually upload the file. I tried deleting the trunk and doing it over and that didn't change anything.

It renames the file internally, that's normal. It is the same file. You can confirm by checking the expiration date.

 

[Guillaume Bourgeois]

Typically providers work with port 5061 for TLS
Change the destination port for 5061 and try again.

 

[nicedoggie]

Thanks, y'all for the information. I tried again using port 5061 although the provider had said to use 5060. Here are a few log entries.

09/24/2023 12:20:49 PM - [CM504005]: Registration failed for: Lc:10000(@BMU_BlueSharkDigital_TG1[<sip:[email protected]:5061/TLS>]); Cause: Cause: 503 Transport failure: no transports left to try/REGISTER from local
09/24/2023 12:20:04 PM - [CM504005]: Registration failed for: Lc:10000(@BMU_BlueSharkDigital_TG1[<sip:[email protected]:5061/TLS>]); Cause: Cause: 503 Transport failure: no transports left to try/REGISTER from local
09/24/2023 12:17:55 PM - [CM504005]: Registration failed for: Lc:10000(@BMU_BlueSharkDigital_TG1[<sip:[email protected]:5060/TLS>]); Cause: Cause: 404 Not found/REGISTER from 64.147.93.179:5060

 

[Guillaume Bourgeois]

It’s up to the SIP provider to support you. Send them the logs and ask them to assist you

or

change for a trunk that has passed the interop test at 3CX (Supported).
Probably the username is wrong ..

So if it looks in their history by looking for the username.. and it is not good, it is possible that it concludes that it is not receiving your attempts..
Anyway, ask them to help you or come back to us using a supported trunk..


https://www.3cx.com/partners/sip-trunks/

 

[nicedoggie]

I have worked with the provider but they are not very responsive. This is termination in Bermuda and I tried the International 3cx approved companies and none have termination in Bermuda.

 

[Guillaume Bourgeois]

You can send me your PCAP file on DM .
I suggest privately because I wouldn't want to leak information that you wouldn't want shared publicly.
Send me privately and I'll reply to you here

 

[nicedoggie]

I would have but my client gave up due to the time it took working with the provider. Thanks for the offer.

 

[drsam.theme]

I received a .pem file from the tls trunk provider and when I try to upload it, the certificate always shows root_cert_10000.pem as the certificate in use under the trunk/options screen, not the .pem file that I "uploaded". It doesn't seem to actually upload the file. I tried deleting the trunk and doing it over and that didn't change anything.

Where are you trying to upload it? I received a certificate from the operator, I don’t understand where to upload it in the trunk settings. PBX v20

 

[Guillaume Bourgeois]

Where are you trying to upload it? I received a certificate from the operator, I don’t understand where to upload it in the trunk settings. PBX v20

This is not yet available in version v20.

In cases where the certificate was added in version 18 and subsequently updated to v20, it will continue to function, but it is not currently possible to upload a certificate on v20.

 

[drsam.theme]

This is not yet available in version v20.

In cases where the certificate was added in version 18 and subsequently updated to v20, it will continue to function, but it is not currently possible to upload a certificate on v20.

What then to do if the Operator only works TLS, how to add a certificate?(

 

[Guillaume Bourgeois]

Revert to v18

What if you upgraded and need to go back? Whether you lost access because of passwords, or any other issue, you should immediately go back to v18! Kill your v20 machine, spin up a v18 one (Marketplace images and ISO are still v18) and restore your latest v18 backup. NOTICE: You will need to contact 3CX Support to get your license key downgraded back down to v18, as it won't work in v18 once you upgraded to v20.

credit : @ConceptsWeb ​

 

[drsam.theme]

Revert to v18

credit : @ConceptsWeb ​

Thank you! That's what I did. The certificate has been added, the SIP trunk is working.