First of all Thank you all al lot for thoughts an pointers. Will try to work them through.
It is the current stable OPNsense 26.7.4 released, will upgrade to 26.7.5 this weekend. But didn't migrate to Source NAT till now, will take a look at this this weekend as well.
New installation, before my Provider was Vodafone via TV/Cable network, rest of setup, HT802v2 and opnSense is the same, the Vodafone box was operation in bridge mode, so all the login and stuff was managed by opnSense, same as with Telekom now.
Thnx for this pointer, there was an error in my post, I used the correct tel.t-online.de server, the page was also given form the Telekom support.
opnSenese uses the DNS it will receive during PPPoE login, and the ATA use the opnSense as DNS, this should be fine.
Apart from the normalization and static port in the Out-NAT there are no further rules for the ATA.
If I set the register expire below 7 Minutes, it looks like I run in a rate limit at the Telekom Server. Than it happens that I get a 403 response from telekom for about 20 min in the ATA SIP logs.
Yes in OpnSense, I create a normalization rule for the LAN and WAN Network, this was given Tip form the AI, apparently Telekom is strict about the lifetime of SIP packages, can*t really verify if it will help or not.
I will now try to let a paket capture running for a whole session "Working - Failure - Working" to get an inside what the ATA doing or what answers it get or not.
The main problem is that I have to call my own phone periodically to find out if the Problem is currently occurring.
Quote from: muchacha_grande on October 01, 2026, 10:49:56 PM@Xaver, if you are using an updated OPNSense version, you can migrate Outbound NAT to Source NAT. Once migrated there is a new option in the Source NAT rule called "endpoint independent". You can try enabling that. Is the "full cone nat"
It seems to me that this option is not present in the old Outbound NAT rule menu but if it is, you don't need to migrate to the new system.
It is the current stable OPNsense 26.7.4 released, will upgrade to 26.7.5 this weekend. But didn't migrate to Source NAT till now, will take a look at this this weekend as well.
Quote from: lmoore on October 01, 2026, 11:11:15 PMIs this a new installation or has it worked in the past?
New installation, before my Provider was Vodafone via TV/Cable network, rest of setup, HT802v2 and opnSense is the same, the Vodafone box was operation in bridge mode, so all the login and stuff was managed by opnSense, same as with Telekom now.
Quote from: lmoore on October 01, 2026, 11:11:15 PMI'm unable to resolve any SRV records for tel.telekom.de, but this may be because I am elsewhere in the world.
Searching the net it appears the SIP server to use is tel.t-online.de and SRV records can be resolved for this address.
Perhaps this page will help: https://www.telekom.de/hilfe/internet-telefonie/telefonie/voice-over-ip-sip-client
Thnx for this pointer, there was an error in my post, I used the correct tel.t-online.de server, the page was also given form the Telekom support.
Code Select
# nslookup -query=naptr tel.t-online.de
Server: --SNIP--
Address: --SNIP--
Non-authoritative answer:
tel.t-online.de naptr = 30 0 "s" "SIP+D2T" "" _sip._tcp.tel.t-online.de.
tel.t-online.de naptr = 10 0 "s" "SIPS+D2T" "" _sips._tcp.tel.t-online.de.
tel.t-online.de naptr = 20 0 "s" "SIP+D2U" "" _sip._udp.tel.t-online.de.
# nslookup -query=SRV _sips._tcp.tel.t-online.de.
Server: --SNIP--
Address: --SNIP--
Non-authoritative answer:
_sips._tcp.tel.t-online.de service = 10 0 5061 mue000-l01-mav-pc-rb-001.edns.t-ipnet.de.
_sips._tcp.tel.t-online.de service = 30 0 5061 nes008-f01-mav-pc-ra-001.edns.t-ipnet.de.
_sips._tcp.tel.t-online.de service = 20 0 5061 hno002-f01-mav-pc-ra-001.edns.t-ipnet.de.
Quote from: lmoore on October 01, 2026, 11:11:15 PMAnother tidbit I came across is you need to be querying the DNS servers offered by Telekom to ensure it works: https://support.yeastar.com/hc/en-us/articles/360014536894-Recommended-SIP-Configuration-for-Deutsche-Telekom
Which DNS servers are used by the ATA?
If you find you can receive a call as soon as the ATA has registered, but you can't receive an incoming call after a couple of minutes, or until the next registration, you could drop the Keep-Alive interval to 25 seconds. If you use TCP for the SIP connection the state timeout should be the default of 86400 seconds when it is established.
I recently moved some numbers to another ITSP and I'm using TLS and SRTP. I've set the registration interval for this service to 5 minutes.
Have you created specific firewall rules for your VoIP service?
opnSenese uses the DNS it will receive during PPPoE login, and the ATA use the opnSense as DNS, this should be fine.
Apart from the normalization and static port in the Out-NAT there are no further rules for the ATA.
If I set the register expire below 7 Minutes, it looks like I run in a rate limit at the Telekom Server. Than it happens that I get a 403 response from telekom for about 20 min in the ATA SIP logs.
Quote from: lmoore on October 01, 2026, 11:11:15 PMYou mentioned you disabled 'Normalization', are you referring to OPNsense?
Does the QoS from Telekom use DSCP and do you know what values these should be?
Yes in OpnSense, I create a normalization rule for the LAN and WAN Network, this was given Tip form the AI, apparently Telekom is strict about the lifetime of SIP packages, can*t really verify if it will help or not.
I will now try to let a paket capture running for a whole session "Working - Failure - Working" to get an inside what the ATA doing or what answers it get or not.
The main problem is that I have to call my own phone periodically to find out if the Problem is currently occurring.
"