[Gelöst] Asterisk und Telekom: Registrierung rejected

[Tenere]

Guten Morgen zusammen.

Ich habe nun einen Telekom All-IP Anschluss erhalten und versuche nun meinen Asterisk 13 mit der Telekom ans Laufen zu bekommen.

Die Registrierung erfolgt (manchmal) auch, nur wird leider immer wieder als "rejected" gemeldet:

[Feb 3 07:29:34] WARNING[10070]: res_pjsip_outbound_registration.c:763 schedule_retry: No response received from 'sip:tel.t-online.de' on registration attempt to 'sip:[email protected]', retrying in '60'

Ich habe mich an dieser Anleitung orientiert und die pjsip.conf dementsprechend konfiguriert.

Ich bin für jeden Hinweis dankbar...

MfG,

Tenere

global]
type=global
user_agent=LasRamblas
endpoint_identifier_order=ip,username
default_from_user=12345

[transport-udp]
type=transport
protocol=udp
bind=0.0.0.0
local_net=192.168.178.0/24
local_net=10.10.10.0/27

[transport-tcp]
type=transport
protocol=tcp
bind=0.0.0.0
local_net=192.168.178.0/24
local_net=10.10.10.0/27


;----------------------------------------------------------------

[03_Telekom]
type=registration
transport=transport-udp
outbound_auth=03_Telekom_auth
server_uri=sip:tel.t-online.de
client_uri=sip:[email protected]
contact_user=1234567890
retry_interval=60
forbidden_retry_interval=300
expiration=480
auth_rejection_permanent=false

[03_Telekom_auth]
type=auth
auth_type=userpass
[email protected]
username=1234567890
realm=tel.t-online.de

[03_Telekom_out]
type=endpoint
transport=transport-udp
context=unspecified
disallow=all
allow=g722
allow=alaw
outbound_auth=03_Telekom_auth
aors=03_Telekom_out_aor
callerid=1234567890
from_user=1234567890
from_domain=tel.t-online.de
timers=no
rtp_symmetric=yes

[03_Telekom_out_aor]
type=aor
contact=sip:[email protected]

[03_Telekom_in_01]
type=endpoint
transport=transport-udp
context=03_Telekom_in
disallow=all
allow=g722
allow=alaw
outbound_auth=03_Telekom_auth

[03_Telekom_in]
type=identify
endpoint=telekom_in
match=217.0.0.0/13

 

[rentier-s]

Du wirst wahrscheinlich noch eine external_signaling_address brauchen.

 

[Tenere]

Da ich eine dynamische IP habe, wie kann ich in der pjsip.conf dies abbilden? In dem Link ist nur eine statische IP erwähnt.

Allerdings funktioniert mein sipgate Account problemlos...

Nachtrag:
In der pjsip.conf [transport-udp] modifiziert:

[transport-udp]
type=transport
protocol=udp
bind=0.0.0.0
local_net=192.168.178.0/24
local_net=10.10.10.0/27
external_media_address=phone.123.de
external_signaling_address=phone.123.de

Allerdings ohne Erfolg...

[Feb  3 12:11:37] WARNING[11391] res_pjsip_outbound_registration.c: No response received from 'sip:tel.t-online.de' on registration attempt to 'sip:[email protected]', retrying in '60'
[Feb  3 12:12:37] WARNING[11391] res_pjsip_outbound_registration.c: No response received from 'sip:tel.t-online.de' on registration attempt to 'sip:[email protected]', retrying in '60'
[Feb  3 12:13:37] WARNING[11391] res_pjsip_outbound_registration.c: No response received from 'sip:tel.t-online.de' on registration attempt to 'sip:[email protected]', retrying in '60'
[Feb  3 12:14:37] WARNING[11391] res_pjsip_outbound_registration.c: No response received from 'sip:tel.t-online.de' on registration attempt to 'sip:[email protected]', retrying in '60'
[Feb  3 12:15:37] WARNING[11391] res_pjsip_outbound_registration.c: No response received from 'sip:tel.t-online.de' on registration attempt to 'sip:[email protected]', retrying in '60'
[Feb  3 12:16:37] WARNING[11391] res_pjsip_outbound_registration.c: No response received from 'sip:tel.t-online.de' on registration attempt to 'sip:[email protected]', retrying in '60'
[Feb  3 12:17:37] WARNING[11391] res_pjsip_outbound_registration.c: No response received from 'sip:tel.t-online.de' on registration attempt to 'sip:[email protected]', retrying in '60'
[Feb  3 12:18:37] WARNING[11391] res_pjsip_outbound_registration.c: No response received from 'sip:tel.t-online.de' on registration attempt to 'sip:[email protected]', retrying in '60'

 

[Tenere]

Guten Abend zusammen,

gibt es niemanden, dem dieses Problem bekannt ist?

Gruss aus EU,

Jörg

- - - Aktualisiert - - -

Es ist offensichtlich ein Bug in der 13er Asterisk Version.
Mit der 14er läuft es einwandfrei.