V20 Upgrade Unable To Edit SIP Trunks

[kent3]

Hey everyone

Wondering if anyone can shed any light on an issue that we have seen on 3 separate upgrades from v18 to v20

We use Generic SIP trunks always by the way, out of the 20 or so systems we have updated already, 3 of them would not allow us to access the SIP trunk settings, no error code to give you, just does nothing when you click on the trunk.

We have had to delete the trunks and re-add them. Not ideal when we have some very large clients to upgrade with 100 DDI +, I don't want to be re-adding them after the update. Im thinking maybe its a setting in the trunk that the upgrade doesn't like? Also worth noting is, when we added the trunks pre v20, we didn't use templates.

Wonder if anyone else has had this issue happen to them?

Any help would be appreciated!

 

[bitn2]

This happens if the pbx dont have the template of the trunk. You can add it manually by windscp or something else. The other way is to delete and make a new trunk with generic template.

 

[kent3]

Thanks for the advise, just had a PM from another user that confirmed it, with link from Reddit post

Weird how it does not affect all systems as I mentioned on 3 of 20 have done this and they were all setup without templates initially, I wonder if its the backup file, some may not have custom templates/firmware selected

 

[logic-call]

Hi
After the transition to version 20 of 3cx, I could not edit the trunks, and i had toe make 20 new trunks Now it appears that the Trunks signaling no longer works. There are no more lines coming in on a number of trunks (15). When I contacted the supplier of the exchange and also the supplier of the lines, it turned out (perhaps the provider has a tool) that the trunks were not registered with the provider, while for me they were all green. At v18 I could also see the last registration of the trunks and now I can't. This is very difficult, now I just have to randomly click on refresh registration and hope that helps. This is very unpleasant and I cannot manage it this way. Is there another way to see that the trunks are registered?. How do I get more control over this? Provider is Dstny and accepted on 3cx.

 

[bitn2]

Hi
After the transition to version 20 of 3cx, I could not edit the trunks, and i had toe make 20 new trunks Now it appears that the Trunks signaling no longer works. There are no more lines coming in on a number of trunks (15). When I contacted the supplier of the exchange and also the supplier of the lines, it turned out (perhaps the provider has a tool) that the trunks were not registered with the provider, while for me they were all green. At v18 I could also see the last registration of the trunks and now I can't. This is very difficult, now I just have to randomly click on refresh registration and hope that helps. This is very unpleasant and I cannot manage it this way. Is there another way to see that the trunks are registered?. How do I get more control over this? Provider is Dstny and accepted on 3cx.

You dont need to make all trunks new. Just copy the template by winscp to the pbx and everything is fine. Trunks that are ip based are allways green, only trunks that have a authentication with user and password are green when connected and red if not.

 

[logic-call]

In ver 18 trunks worked fine and red when they were not registered, after a refresh registration they got green when registered, i also could see when last time registered fine. Registration is with Authentication ID (SIP User ID) and Authentication password