TLS SIP Trunk ( SignalWire)

[ahmedgc01]

Hi,
I don't know that whether I'm in right place to post my question regarding TLS SIP Trunk ( SignalWire) registration in 3CX .I spent hours and hours tried to configure trunk but in vain . Can anyone guide me in regards, I'll really appreciate you . thanks .

 

[eddv123]

Yes this is the right forum for this question. Since this is an unsupported provider (to my knowledge) then you need to provide more information.

For example is the provider registration or IP authentication based, where have you got to with your setup and have you used a generic provider template.

The more information you can provider the better the chance of solving the issue we have.

 

[ahmedgc01]

Thanks eddv123 for prompt reply.
I have encountered this error " myaccount.sip.signalwire.com:5061] from L:4.1[Extn:002] failed, cause: Cause: 408 Request Timeout/INVITE from local " . When I tried to call on USA cell via this server on TLS. SignalWire SIP trunk woks at TLS layer on port 5061 for encrypted traffic. I remember on fusionpbx server it is working with the help of certificate which we got from letsencrypt . It's authentication error , i think tunnel and TLS both can not work at the same time . Is there any way to use TLS instead of tunnel in that case .

 

[eddv123]

Well your correct if you are referring to 3CX Tunnel it uses its own encryption but is not relevant when it comes to SIP trunking (clients and SBC only).

I would say to generate a Wireshark capture however you cant see the packets due to it being encrypted.
Have you asked the provider for their opinion.

 

[ahmedgc01]

signalwire sip trunk is domain based and user authentication (username and password ) are required. I used Generic and Generic sip trunk as ours sip trunk is not listed in provided list of sip trunk. I don't have any idea about template.

 

[JohnS_3CX]

Hi @ahmedgc01

This will not work currently because it uses TLS for the trunk SIP transport as you described.

Currently you can only enable SRTP (just the audio portion) via 3CX trunk settings.

Unless the provider allows you to send SIP without TLS, it will not work.



Note: Tunnel is only for the 3CX SBC and clients - not for the trunks, hence it does not apply here at all.

 

[ahmedgc01]

provider says that sip trunk(signalwire SIP trunk) works with all IP PBX systems.

 

[JohnS_3CX]

provider says that sip trunk(signalwire SIP trunk) works with all IP PBX systems.

That's a generic response, they will have to give you their requirements or at least some basic form of setup guide (i.e credentials, authentication method)

 

[ahmedgc01]

thanks JohnS_3CX
here is information (credential they have given me) .
Trunk Number/Account: PBXXXXX
Password:abcdef
Provider URL: account.sip.signalwire.com
DID: 61xxxxxx
Trunk Name: SignalWire works on TLS .

 

[ahmedgc01]

thanks JohnS_3CX
here is information (credential they have given me) .
Trunk Number/Account: PBXXXXX
Password:abcdef
Provider URL: account.sip.signalwire.com
DID: 61xxxxxx
Trunk Name: SignalWire works on TLS .

 

[JohnS_3CX]

Ok then since TLS is a requirement, it will not work with the current version of the PBX.

3CX Trunk authentication does not support TLS mode.

 

[ahmedgc01]

Not clear on this link https://docs.signalwire.com.I hope 3CX will provide TLS based sip trunk registration in future. thanks anyway

 

[Evolute IT]

Ok then since TLS is a requirement, it will not work with the current version of the PBX.

3CX Trunk authentication does not support TLS mode.

Is TLS auth on the radar of possible implementations? It'd be great honestly, a lot of providers support TLS so it would encrypt from end-to-end.

 

[JohnS_3CX]

We are making some back end changes that will give more flexibility in the way the system interacts with VoIP providers, and SIP TLS is also being considered.