Solved 3CX doesn't attempt to resolve NAPTR/SRV

[leon.p]

Hi,

I'm trying to configure a generic sip trunk with FQDN on the 3CX system(16.0.9), but i cannot reach the first peer.

This is a ip based trunk, during the troubleshooting i started capturing the traffic and noticed that the system is not even trying to resolve the FQDN.

I followed this instructions https://www.3cx.com/docs/sip-trunk-dns-record-resolution/ .

Should i allow/configure something else outside of the sip trunk?

 

[YiannisH_3CX]

Hi @leon.p

You should make sure that the Auto Discovery option is enabled next to your registrar and that your transport is set to ANY in the options page. That will enable the PBX to query for NAPTR / SRV records.

 

[leon.p]

Hi @YiannisH_3CX

Thanks for the fast respond.

Yes both of them are enabled, but still no attempt to resolve the FQDN

 

[YiannisH_3CX]

Do you have a registrar and a proxy? Btw the PBX will only to resolve DNS during a service restart or if it runs out of targets and tries to do another query to find new targets.

 

[leon.p]

Hi @YiannisH_3CX

Thanks man that worked after rebooting the server, query was performed and successfully established the call.

Can i do this process only by restarting one service not the whole server?

And what do you mean "if it runs out of targets" e.g if the registration fails or call fails?

 

[YiannisH_3CX]

Can i do this process only by restarting one service not the whole server?

Sure you can access the "Services" menu found on the Dashboard and restart only the SIP server service.

And what do you mean "if it runs out of targets" e.g if the registration fails or call fails?

When you add a trunk the PBX will perform a full DNS query (depending on your settings) and will get a list of IPs it can try to connect to and will start trying to connect when registration based or will send the call there if IP based. If the PBX fails to register to all targets or tries to send the call to all targets and fail it will perform a new DNS query to try to resolve new targets after the timeout expires.

Glad to see you were able to resolve the issue.