Trunks in 3CX v20 Dashboard

[yevpro]

We have several sip-trunks. After migration to v20, interface has changed and now in dashboard we see an error because some VOIP providers are not supported by 3cx.



Is there any way to make a provider "trusted/verified" so that we see that error in dashboard only in case the sip-trunk is down?

 

[fxbastler]

Basically yes, it depends on the answers to the following questions:

1. What kind of trunk was originally used as a template?
2. Can you still access the trunk in the administration to change anything?
3. What kind of 3CX license are you using?
4. Is it a Windows or Linux 3CX?
5. Do you have access to the 3CX system (any kind of a shell)?

 

[TheodorosG_3CX]

This is an indication for the generic provider template that is in use, under the Voice&Chat section you also see the reason:

 

[yevpro]

This is an indication for the generic provider template that is in use, under the Voice&Chat section you also see the reason:

View attachment 46899

Yes, thats our case. We are using generic voip provider. But the trunk in active. So its confusing to see in dasboard an error.

I am ok to see the warning on the Voice&Chat page, but not on the dasboard page.

 

[yevpro]

Basically yes, it depends on the answers to the following questions:

1. What kind of trunk was originally used as a template?
2. Can you still access the trunk in the administration to change anything?
3. What kind of 3CX license are you using?
4. Is it a Windows or Linux 3CX?
5. Do you have access to the 3CX system (any kind of a shell)?

1) Generic VOIP Provider
2) Yes, I can
3) PRO4SC
4) Linux VM from 3cx Azur template
5) Yes, I have full control.

 

[fxbastler]

Not supported: replace the template file name in the database.
Per example:

1. list all gateways and their template name
   select idgateway, name, model from public.gateway;
2. change #2 to the dts template (file must exist in the template directory, customize idgateway as needed):
   update public.gateway set model='dts.pv.xml' where idgateway=2;
commit;
3. reboot 3cx

This way you keep the complete setup: DID, names, assignment, outgoing rules, etc..