Future Support for IP-Based Authentication in 3CX SMB Edition?

[Shragi]

Are there any plans to support IP-based authentication for call trunks in the SMB edition of 3CX in the near future?

 

[N_G]

No...

 

[bitn2]

Technically not possible. You are not allone on an SMB machine.

 

[Shragi]

IP register + user authentication...

 

[bitn2]

IP register + user authentication...

Thats what you have already.. User authentication. There are no trunks with both.

 

[NicholasP_3CX]

IP based trunks essentially mean there is no authentication done, and the provider will blindly accept any request from your IP Address.

As it is a shared instance, we do not allow this type of provider on the SMB platform.

 

[Shragi]

I’ve been giving this more thought and wondering if Twilio BYOC + Twilio Elastic Trunk could help overcome this limitation and allow me to connect to a 3CX trunk.

My main motivation is to take advantage of favourable rates with DIDww to a destination country we frequently call, which I haven’t been able to match with other SIP providers.

I’ve successfully connected the DIDww outbound trunk to 3CX, but I’m unable to get the inbound trunk working.

Would this setup be a viable workaround?