is "Force Invites to be send to IP of Registrar " option removed from generic sip trunk template in v16.0.3.676

[PanagiotisK]

Self explanatory title.
We upgraded the 3cx of a customer to v16.0.3.676 and the generic sip trunk that they are using is unregistered once or twice a day for 5-10 minutes
We are checking the settings one by one with a working SIP Trunk of the same provider from a different customer with v16.0.2.910 and we noticed that this option (which is checked in the working customer) is missing on the new version.
Is this on purpose?

 

[JohnS_3CX]

Hi Panagiotis

There are further optimizations coming in V16-Update-4 for Generic trunks.

As for "Force Invites to be sent to IP of Registrar" this was specifically for providers with SRV records (meaning they might have two IPs for registration) and it restricted the invites to go to the IP that was resolved first from the record. If you provider does not have such a thing, the option does absolutely nothing. Anyway, in update 3 it is always on by default so thats why it was removed as an option.

What you can do however that may help, is to change the "transport" under the options menu. Instead of "any" change it to UDP

 

[ahcomputers]

We have been having similar issue since 16.0.3.676. We are not seeing the trunk unregister, but we are at times having outbound calls failing while inbound calls still come in. Reviewing captures, we can see that 3cx registered to one IP of sip provider, but invites from 3cx were sent to a different ip in the SRV record for the provider. If this option is always on by default, it appears to be broken.

 

[JohnS_3CX]

@ahcomputers if you have such a specific case as you described and need a solution, please open a ticket with support directly.

 

[ahcomputers]

@ahcomputers if you have such a specific case as you described and need a solution, please open a ticket with support directly.

Thanks. I did open a ticket two days ago. Came here hoping to get another set of eyes on it and quicker resolution as this is disrupting service significantly.
I'll continue to work through the ticket process.