[v20] Unable to Edit Trunk Created in v18 – Fails to Register After Modification

[Azerbaijani]

Hi all,

Hoping someone here might have insight into this.

I’ve got a trunk that was originally created back in 3CX v18. After upgrading the system to v20, the trunk continues to work fine until I try to modify any details (e.g., change the number or registration parameters). Once I make a change, it fails to register.
We change the registration settings as we have multiple servers with our upstream carrier so when/if there is an issue with the voice server we are able to just change the details on 3CX to get the voice traffic sent through a backup server.

Since we were using the outbound proxy field on V18, this is the reason why the trunk fails to register when changing the details on V20. 3CX have removed the option to edit this field which has caused this problem.

What I need help with:

I want to edit the existing trunk without having to delete and recreate it — as that would mean redoing all rules, DIDs, mappings, and potentially causing disruption.

Does anyone know where the SIP trunk configs are kept where we can edit them? (I'm not talking about the base templates used to create the SIP Trunks but the configured trunks)

Would really appreciate if anyone’s dealt with this and can share advice or ideas.

Thank you!

 

[K_SAK]

Hi,

The 3 dots at the end of the Trunk line in Voice & Chat have an Export option.

 

[Azerbaijani]

Exporting the trunk wont solve our issue.
We need to be able to edit the registration details including the outbound proxy. As mentioned in the original post, we edit the registration server to be able to send the calls to a different location if/when there is a problem within the upstream providers network.
Rebuilding the SIP trunk each time is not a viable option.
Since 3CX removed the outbound proxy field, we are forced to find another way to edit the outbound proxy, so we are looking for when the SIP trunk config is stored in the backend of the phone system.
We know where the trunk templates are, but thats just for building new trunks.

 

[K_SAK]

Exporting the trunk wont solve our issue.
We need to be able to edit the registration details including the outbound proxy. As mentioned in the original post, we edit the registration server to be able to send the calls to a different location if/when there is a problem within the upstream providers network.
Rebuilding the SIP trunk each time is not a viable option.
Since 3CX removed the outbound proxy field, we are forced to find another way to edit the outbound proxy, so we are looking for when the SIP trunk config is stored in the backend of the phone system.
We know where the trunk templates are, but thats just for building new trunks.

Adding a new trunk with the alternate proxy permanently and route via it selectively with outbound rules? Would your SIP provider have an issue with this?

 

[YiannisH_3CX]

Hi @Azerbaijani

Which SIP trunk provider are you using?

 

[lancerichards]

We have seen this before where the original template is no longer there.
Best to create a new trunk and pop your details in there.

You don't need to migrate your DID's.
As long as they are on a trunk (registered or not) 3CX still does a DID lookup.