Issue with NAPTR registering CompanyFlexCloud

hofmannu

Customer
Joined
Apr 26, 2022
Messages
1
Reaction score
0
Hi,

I'm trying to configure a Telekom CompanyFlex Cloud sip trunk with tel.t-online.de on the 3CX Version 20.0 Update 4 (Build 487 Release), but i cannot resolve the NAPTR

I noticed that the system is can not resolve the registrar and the proxys

I followed this instructions for Telekom Company Flex as well as https://www.3cx.com/docs/sip-trunk-dns-record-resolution/ .

Log:

23.12.2024 17:32:13.542Lc:10001(@telekom Mainburg[<sip:@:0/UDP>])Scheduled DNS resolution in 300 sec.
23.12.2024 17:32:13.542Lc:10001(@telekom Mainburg[<sip:@:0/UDP>])No destination available
23.12.2024 17:32:13.542Lc:10001(@telekom Mainburg[<sip:@:0/UDP>]) has resolved targets to following list:
23.12.2024 17:32:13.498Resolving URI (NAPTR) <sip:@5511xxx.secondary.companyflex.de:0/UDP>
23.12.2024 17:32:13.498Resolving URI (NAPTR) <sip:@55114xxx.primary.companyflex.de:0/UDP>
23.12.2024 17:32:13.470Lc:10001(@telekom Mainburg[<sip:@:0/UDP>]) Resolving targets: primary - sip:5511xxx.primary.companyflex.de, secondary - sip:5511xxx.secondary.companyflex.de over +TLS+IPv4
23.12.2024 17:32:13.470Lc:10001(@telekom Mainburg[<sip:@:0/UDP>]): Registration postponed until target's destination is resolved
23.12.2024 17:32:13.469Registering Line Lc:10001(@telekom Mainburg[<sip:@:0/UDP>])
23.12.2024 17:32:13.469Unregister: ADS for 10001 is not found
23.12.2024 17:32:13.469Unregistering Line 10001


Registrar and Proxys are set to auto-discovery

Should i configure something else outside of the sip trunk?

Any help would be apreciated !!!

Many Thanks
Uwe
 

Latest Posts

Forum statistics

Threads
111,962
Messages
589,993
Members
164,867
Latest member
swegner