[asterisk-users] Change by Deutsche Telekom end of februar. Can someone help me?

Michael Maier m1278468 at mailbox.org
Tue Feb 16 15:32:02 CST 2021

On 16.02.21 at 20:33 Luca Bertoncello wrote:
> Am 16.02.2021 um 19:56 schrieb Michael Maier:
> Hi Michael,
>>> Do I use pjsip?
>> pjsip show registrations
> gw*CLI> pjsip show registrations
> No objects found.
> So I don't use pjsip... :(


> Maybe could you send me an abstract of your configuration?

Take a look here [1]

>>> You mean, I have to create a "fake" Zone tel.t-online.de in my Bind with
>>> these settings? Looks like dangerous, if they changes something...
>> If you do that statically -> yes, you're right. You have to do it
>> dynamically. I attached a script, which can be used to dynamically build
>> a rpz each 15 minutes e.g. It directly asks the telekom nameserver for
>> naptr and srv entries. It looks like this:
>> server
>> zone rpz-tonline
>> update delete tel.t-online.de.rpz-tonline.
>> update delete _sips._tcp.tel.t-online.de.rpz-tonline.
>> update delete _sip._tcp.tel.t-online.de.rpz-tonline.
>> update add tel.t-online.de.rpz-tonline. 60      NAPTR   10 0 "s"
>> "SIPS+D2T" "" _sips._tcp.tel.t-online.de.
>> update add tel.t-online.de.rpz-tonline. 60      NAPTR   30 0 "s"
>> "SIP+D2T" "" _sip._tcp.tel.t-online.de.
>> update add _sips._tcp.tel.t-online.de.rpz-tonline.      60 SRV  10 0
>> 5061 s-eps-110.edns.t-ipnet.de.
>> update add _sip._tcp.tel.t-online.de.rpz-tonline.       60 SRV  10 0
>> 5060 s-epp-110.edns.t-ipnet.de.
>> send
> So if I undestand what you mean, you check the NAPTR and SRV für
> _sips._tcp.tel.t-online.de and save the record in a "virtual domain"
> rpz-tonline, is it correct?
> Then I suppose you use this domain instead of tel.t-online.de in the SIP
> configuratione as "host", "outboundproxy" and "fromdomain", is it correct?

No - you have to use the correct domain name in asterisk.  Only bind knows about 
the fake domain. You have to configure bind correctly.

You have to create the fake domain in the bind config like this:
options {
         response-policy {
             zone "rpz-tonline";


zone "rpz-tonline" {
         type master;
         file "/var/named/rpz-tonline-override";
         allow-query { any; };
         allow-transfer { any; };
         allow-update { any; };

All other things: take a look at the script! It's not that complicated.

>> The script unregisters and registers the telekom trunks, if a change is
>> detected. This is done as long as there is no call active. This works
>> for me - but may not wort for others - feel free to change the code.
> OK, I'll check it...
>> Independently you have to add your own trunk names to get it working
>> (telekomPJSIP-a, ...).
> Could you explain me that? I'm not an expert of Asterisk... :(

Well, if you want to use it, you really should engage yourself a bit more to get 
it solved. It's not that easy. Or you may forget about the DNS fake and live with 
the problem, that asterisk could partly switch sometimes to another server - 
breaking the telephony. I don't think it would happen that often, because Telekom 
usually is extremely stable. Try at first to get a running pjsip configuration. 
The DNS theme could be done later on.



More information about the asterisk-users mailing list