Problem moving Trunk from v15 to v16

[Dalibor]

Hi All,

I am trying to move a working trunk from version 15 to version 16 3CX server.

Since my provider is not on the list, and the v16 does not allow to add SIP directly, I have exported provider from v15 server, and removed the trunk from v15.
After importing the profile, and assigning user name / pw on the v16 server, this trunk does not even attempts to register.
To make sure I've made no mistake, I've imported the trunk back into v15, added credentials, and it connected right away.

There no attempts in the log, and there are no attempt times in the SIP trunks list.

This is how registration looks on v16:


and this is how it looks on v15:


I have attached the xml provider file.

Any help is appreciated !

 

[cobaltit]

So I would check the registration to make sure you have it set to register. But you absolutely can add a generic sip trunk/voip provider in 3CX and just copy over the settings without export/import

 

[Dalibor]

Thank you for pointing that you can still add generic provider.
There used to be a "generic" SIP provider type that is gone now. However I see a can just pick any offered provider and change the server to match mine.

However, the problem is still there - no attempts to register.
It is set to register:


again, identical setup works fine on version 15

 

[cobaltit]

Generic SIP trunk provider still seems to be there for me:



You might want to check the auto discovery boxes (turn them off). But otherwise, this is what supported providers are for.

 

[Dalibor]

Thank you for the reply. I tried that as well. In addition to this I've added another one with a different provider, and it did not tried to connect as well.
I guess something is wrong with the server itself.

I'm about to wipe out the server and set it up again.

Thank you all !

 

[Dalibor]

Update:

After fresh installation and the restore of the backup, everything works out of the box !

 

[AWS2P]

how did you proceed first time to v16 ?
Did you restore your v15 backup during install?
PBX is windows on premise?

 

[Dalibor]

This particular server is installed from the v15.5 debian iso, running on the vmware ESXi.
It was running fine for quite some time.
Around 9 months ago, I've issued "apt update / apt upgrade" sequence, and the server booted up as a v16, and in the process changed the perpetual license it was running on, to a yearly.

This server does not do much, as it's only purpose is to run a single SIP trunk, because it is restricted by the provider to geographical IP range - does not work out of the country.
It is in the bridge with my other server and forwards all incoming calls over the bridge.

The inconvenience I had was at highway speeds, the VoIP calls can get choppy and illegal to use while driving (hard to do hands-free).
So with some extra time from isolation, I've decided to move one of my normal sip trunks over to this server, use regular cellular line to call it , and then have digital receptionist to select an extension that is not logged in - to forward the call out trough the resident trunk.
Very simple solution, right?

Hence my surprise when it refused to work.

Solution was to export all settings to a file, download it. Next, take the server offline, spin up new vm from the latest ISO. At the point where it asked for a license or a backup file, I've uploaded the backup file.

Process finished, and everything worked without any change.

I hope this helps.