"The best business telephones in the world."

Hallo zusammen,

ich habe heute mein Snom an den Speedport von der Telekom angeschlossen.

Ich bekomme eine IP Adresse und kann auch auf die Weboberfläche zugreifen. Jedoch kann das Telefon sich nicht registrieren.

In den Screenshots sind meine Einstellungen.

Freue mich über jede Hilfe.

Viele Grüße,

Philipp

Guten Tag,

vielen Dank für die Antwort. Das Problem ist jedoch immer noch vorhanden.

Hier mal was im Log steht:

Oct 12 17:01:48.925 [NOTICE] PHN: DST start 29.03.2020 02:00:00 end 25.10.2020 03:00:00 offset 3600

Oct 12 17:01:50.017 [NOTICE] PHN: ProvUtils::UcLookUpFirmwareUpdateViaDNS: domain: >speedport.ip<

Oct 12 17:01:50.017 [NOTICE] PHN: ProvUtils::UcSendFirmwareUpdateAvailableRequest: enabled: 1; url: >https://ucupdates-r2.speedport.ip/RequestHandler/ucdevice.upx<; id: ><

Oct 12 17:01:50.017 [NOTICE] PHN: ProvUtils::UcSendFirmwareUpdateAvailableRequest: request: ><Request><DeviceType>3PIP</DeviceType><MacAddress>00-04-13-92-83-74</MacAddress><SerialNumber>NA</SerialNumber><IP>192.168.2.154</IP><UserID></UserID><NumOfFiles>1</NumOfFiles><LocaleID>ENU</LocaleID><Vendor>Snom</Vendor><Model>snomD785</Model><Revision>AB</Revision><CurrentTime>2011-10-14T08:07:30</CurrentTime><CurrentModule><FileName>cpe.nbt</FileName><FileVersion><Major>10</Major><Minor>1</Minor><Build>22</Build><QFE>0</QFE><TimeStamp>2009-12-10T11:31:30</TimeStamp></FileVersion></CurrentModule></Request><

Oct 12 17:01:50.247 [ERROR ] PHN: TPL: Socket Error: 21/37/connected, Tls error, closing

Oct 12 17:01:50.248 [ERROR ] TLS: BIO_new_bio_pair code 336151570, error:14094412:SSL routines:ssl3_read_bytes:sslv3 alert bad certificate

Oct 12 17:01:50.248 [ERROR ] TLS: BIO_new_bio_pair code 336150757, error:140940E5:SSL routines:ssl3_read_bytes:ssl handshake failure

Oct 12 17:01:48.001 [NOTICE] PHN: DST start 29.03.2020 02:00:00 end 25.10.2020 03:00:00 offset 3600

Oct 12 17:01:48.042 [NOTICE] PHN: Fetching FW URL: https://secure-provisioning.snom.com:443/snomD785/snomD785-firmware.htm

Oct 12 17:01:48.042 [NOTICE] PHN: Fetching URL: https://secure-provisioning.snom.com:443/snomD785/snomD785-firmware.htm

Oct 12 17:01:48.348 [NOTICE] PHN: Std-Settings stored

Oct 12 17:01:52.763 [WARN ] SIP: cannot get ip address of stunserver stun.t-online:3478, will try again with next registration attempt (see setting retry_after_failed_register)

Oct 12 17:01:55.912 [WARN ] PHN: Could not resolve host >ucupdates-r2.speedport.ip<

Oct 12 17:01:55.912 [WARN ] WEBCLIENT: Could not resolve host ucupdates-r2.speedport.ip

Oct 12 17:01:55.913 [NOTICE] PHN: ProvUtils::UcFirmwareUpdateAvailableResponseReceived code: 400

Oct 12 17:06:40.450 [NOTICE] PHN: testNetworkPolicyIsSet

Oct 12 17:10:37.569 [NOTICE] PHN: TPL: Socket 28 idle/connect timeout

Oct 12 17:10:37.570 [NOTICE] PHN: TPL: Socket 29 idle/connect timeout

Oct 12 17:10:37.571 [NOTICE] PHN: TPL: Socket 30 idle/connect timeout

Oct 12 17:10:40.039 [NOTICE] PHN: TPL: Socket 27 idle/connect timeout

Oct 12 17:10:40.049 [NOTICE] PHN: TPL: Socket 25 idle/connect timeout

Oct 12 17:10:40.050 [NOTICE] PHN: TPL: Socket 26 idle/connect timeout

Oct 12 17:11:55.160 [CRITIC] PHN: Warning: Ignore invalid parameter: save_identity_photo

Oct 12 17:11:57.223 [NOTICE] PHN: Std-Settings stored

Oct 12 17:11:58.362 [WARN ] SIP: cannot get ip address of stunserver stun.t-online:3478, will try again with next registration attempt (see setting retry_after_failed_register)

Oct 12 17:12:00.149 [NOTICE] PHN: TPL: Socket 31 idle/connect timeout

Oct 12 17:12:01.309 [NOTICE] PHN: TPL: Socket 32 idle/connect timeout

Oct 12 17:12:18.089 [NOTICE] PHN: TPL: Socket 33 idle/connect timeout

Oct 12 17:12:20.000 [NOTICE] PHN: TPL: Socket 34 idle/connect timeout

Oct 12 17:12:50.390 [CRITIC] PHN: Warning: Ignore invalid parameter: save_identity_photo

Oct 12 17:12:50.391 [WARN ] SIP: cannot get ip address of stunserver stun.t-online:3478, will try again with next registration attempt (see setting retry_after_failed_register)

Oct 12 17:12:52.309 [NOTICE] PHN: Std-Settings stored

Oct 12 17:12:53.563 [CRITIC] PHN: Warning: Ignore invalid parameter: save_identity_photo

Oct 12 17:12:53.563 [CRITIC] PHN: Warning: Ignore invalid parameter: REREGISTER:1

Oct 12 17:12:53.563 [CRITIC] PHN: Warning: Ignore invalid parameter: REREGISTER

Oct 12 17:12:53.565 [WARN ] SIP: cannot get ip address of stunserver stun.t-online:3478, will try again with next registration attempt (see setting retry_after_failed_register)

Oct 12 17:12:55.369 [NOTICE] PHN: TPL: Socket 36 idle/connect timeout

Oct 12 17:12:56.687 [NOTICE] PHN: TPL: Socket 35 idle/connect timeout

Oct 12 17:13:02.519 [NOTICE] PHN: TPL: Socket 37 idle/connect timeout

Oct 12 17:13:04.459 [NOTICE] PHN: TPL: Socket 38 idle/connect timeout

Oct 12 17:13:08.919 [NOTICE] PHN: TPL: Socket 39 idle/connect timeout

Oct 12 17:13:10.867 [NOTICE] PHN: TPL: Socket 40 idle/connect timeout

Oct 12 17:14:51.593 [CRITIC] PHN: Warning: Ignore invalid parameter: save_identity_photo

Oct 12 17:14:51.593 [CRITIC] PHN: Warning: Ignore invalid parameter: REREGISTER:1

Oct 12 17:14:51.593 [CRITIC] PHN: Warning: Ignore invalid parameter: REREGISTER

Oct 12 17:14:54.689 [NOTICE] PHN: TPL: Socket 41 idle/connect timeout

Oct 12 17:14:54.792 [WARN ] SIP: cannot get ip address of stunserver stun.t-online:3478, will try again with next registration attempt (see setting retry_after_failed_register)

Oct 12 17:14:56.579 [NOTICE] PHN: TPL: Socket 42 idle/connect timeout

Oct 12 17:15:10.839 [NOTICE] PHN: TPL: Socket 44 idle/connect timeout

Oct 12 17:15:11.659 [NOTICE] PHN: TPL: Socket 43 idle/connect timeout

Also ehrlich gesagt bin ich etwas enttäuscht von dem Support hier.

Nach kurzem Verweis auf einen Link. Gibt es keine Antwort mehr... Schade, da bleibt mir nichts anderes übrig als zu einem anderen Hersteller zu gehen.

Ich denke, es ist nur eine Werbung hier. Sie haben keine weitere Unterstützung, wie sie sagen. wie enttäuschend!friv