Jump to content

Deutsche Telekom


HighCtenor
 Share

Recommended Posts

  • Replies 60
  • Created
  • Last Reply

Top Posters In This Topic

  • 2 years later...

Hi,

I'm back again with a new issue since today at 02:38 am.

TRUNKs setup completely unchanged, but no REGISTRATION since tonight:

TRUN:	Registration on trunk 4 (03********) failed with code 408. Retry in 60 seconds

It's seems there is no DNS resolving for "tel.t-online.de" in the "Proxy Address" to "sip:tel.t-online.de"  since my pcap shows not a single packet for Telekom SIP or destination IP 217.0.128.132 or .133 !

Vodia is running in ver. 59.0 (FreeBSD) and here is the DNS answer from host system itself:

dig tel.t-online.de

; <<>> DiG 9.11.2-P1 <<>> tel.t-online.de
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10901
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;tel.t-online.de.		IN	A

;; ANSWER SECTION:
tel.t-online.de.	3600	IN	A	217.0.128.132

;; Query time: 119 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Tue Jul 10 20:47:17 CEST 2018
;; MSG SIZE  rcvd: 60

Once more: It helps to set the "Proxy address" to "sip:217.0.128.132" for the trunk, but isn't really nice.

Flow Sequence in this case:

sip.jpg

Any ideas or hints for me?

Link to comment
Share on other sites

Try using host instead of dig, there you can also specify the type (e.g. host -t SRV). There were several outages last week on our VoIP phone in Germany (PBX not involved) where the phone would not register. Maybe this is just because too many people are on vacation in Deutsche Telekom right now... Hopefully nothing has changed in the setup on their side!

Link to comment
Share on other sites

Yes... the time is typical for Deutsche Telekom to load new running_config in network devices.

$ dig -t NAPTR tel.t-online.de

; <<>> DiG 9.11.2-P1 <<>> -t NAPTR tel.t-online.de
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61953
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;tel.t-online.de.		IN	NAPTR

;; ANSWER SECTION:
tel.t-online.de.	4425	IN	NAPTR	20 0 "s" "SIP+D2U" "" _sip._udp.tel.t-online.de.
tel.t-online.de.	4425	IN	NAPTR	10 0 "s" "SIPS+D2T" "" _sips._tcp.tel.t-online.de.
tel.t-online.de.	4425	IN	NAPTR	30 0 "s" "SIP+D2T" "" _sip._tcp.tel.t-online.de.

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Wed Jul 11 16:19:24 CEST 2018
;; MSG SIZE  rcvd: 208

I'm currently on my investigation in wireshark, any special request?

Link to comment
Share on other sites

 

On 7/11/2018 at 4:00 PM, Vodia PBX said:

Try using host instead of dig, there you can also specify the type (e.g. host -t SRV). There were several outages last week on our VoIP phone in Germany (PBX not involved) where the phone would not register. Maybe this is just because too many people are on vacation in Deutsche Telekom right now... Hopefully nothing has changed in the setup on their side!

It seems Vodia in vacation mode too... ;-) Come on, lets debug again!

Service Ticket created at DTAG additionally.

Link to comment
Share on other sites

No just watching the soccer world sup LoL... The question is if this is always not working now or on/off. If it is permanent it would be interesting to see what is in the DNS cache of the PBX (web interface) and if this makes any sense. If this is on/off there must be something else, maybe even a unstable Ethernet connector or something like that. 

Link to comment
Share on other sites

It is permanent since 4 days.

DNS Cache:

Type 	Address 	Content 	TTL
A	d-eps-608.edns.t-ipnet.de	217.0.3.228	55:28
A	h2-eps-608.edns.t-ipnet.de	217.0.3.244	55:28
A	proxy.dus.net	83.125.8.71	01:28
A	proxy.live.sipgate.de	217.10.68.147	21:08:48
A	s-eps-608.edns.t-ipnet.de	217.0.20.212	55:28
A	sip.iptel.org	212.79.111.155	55:28
A	sipgate.de	217.10.79.9	02:55:28
AAAA	d-eps-608.edns.t-ipnet.de		25:28
AAAA	h2-eps-608.edns.t-ipnet.de		25:28
AAAA	proxy.dus.net		55:28
AAAA	proxy.live.sipgate.de	[2001:ab7::2]	21:08:48
AAAA	s-eps-608.edns.t-ipnet.de		25:28
AAAA	sip.iptel.org		02:46:08
AAAA	sipgate.de	[2001:ab7::4]	02:55:28
NAPTR	proxy.dus.net	0 50 s SIP+D2U - _sip._udp.proxy.dus.net 	01:28
NAPTR	sip.iptel.org		02:46:08
NAPTR	tel.t-online.de	30 0 s SIP+D2T - _sip._tcp.tel.t-online.de 20 0 s SIP+D2U - _sip._udp.tel.t-online.de 10 0 s SIPS+D2T - _sips._tcp.tel.t-online.de 	01:55:28
SRV	_sip._tcp.sip.iptel.org		02:46:08
SRV	_sip._tls.sip.iptel.org		02:46:08
SRV	_sip._udp.proxy.dus.net	0 0 proxy.dus.net 5060 	01:28
SRV	_sip._udp.sip.iptel.org		02:46:08
SRV	_sips._tcp.sip.iptel.org		02:46:08
SRV	_sips._tcp.tel.t-online.de	30 0 h2-eps-608.edns.t-ipnet.de 5061 20 0 d-eps-608.edns.t-ipnet.de 5061 10 0 s-eps-608.edns.t-ipnet.de 5061 	55:28

 

Link to comment
Share on other sites

Here we have the Log Entries for one of my DTAG Number with normal (currently failed Registration) "Proxy address": "tel.t-online.de"

[8] 18:23:52.446	TRUN:	Trunk 5: Preparing for re-registration
[8] 18:23:52.446	TRUN:	Trunk 5: sending discover message for tel.t-online.de
[8] 18:23:52.449	TRUN:	Trunk 5 (03????????) is associated with the following addresses: tls:217.0.20.212:5061 tls:217.0.3.228:5061 tls:217.0.3.244:5061
[8] 18:23:52.450	TRUN:	Trunk 03????????): Sending registration to sip:tel.t-online.de
...
[5] 18:24:24.451	TRUN:	Registration on trunk 5 (03????????) failed with code 408. Retry in 60 seconds

May be we don't have to use TLS here?

Link to comment
Share on other sites

On 7/10/2018 at 9:36 PM, Bronko said:

 


dig tel.t-online.de

; <<>> DiG 9.11.2-P1 <<>> tel.t-online.de
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10901
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;tel.t-online.de.		IN	A

;; ANSWER SECTION:
tel.t-online.de.	3600	IN	A	217.0.128.132

;; Query time: 119 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Tue Jul 10 20:47:17 CEST 2018
;; MSG SIZE  rcvd: 60

 

 

What do you mean?

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share




×
×
  • Create New...