[PROBLEM] Snomm300 Ton nur in eine Richtung (werde nicht gehört)

[boboflo]

Hallo,

ich habe hier ein SNOM 300 IP-Telefon. Wenn ich irgendwo anrufe werde ich nicht gehört. Ich habe nun ein Portforwarding vorgenommen und auch das hat keine Abhilfe geschaffen. Es muss irgendwas mit der Konfiguration des Telefons zu tun haben.

Details:
Router: Lancom DSL/i 1611 Office

Das Telefon ist über ein Switch mit dem Router verbunden. Als Standardgateway und DNS ist jeweils die IP des Routers angegeben.

Kann mir jemand helfen ich weiss wirklich nicht mehr weiter.

LOG:
Edit Guard-X: Bitte nächstes mal Code-Tags benutzen!

[0]24/12/2001 00:00:13: License verify ok[2]24/12/2001 01:00:13: start_dst(985485600) end_dst(1004238000) offset_dst(3600) offset_utc(3600)
[2]24/12/2001 01:00:13: start DST: 03/25/2001 02:00:00 (985485600)
[2]24/12/2001 01:00:13: end DST: 10/28/2001 03:00:00 (1004238000)
[2]11/7/2007 09:22:48: start_dst(1174788000) end_dst(1193540400) offset_dst(3600) offset_utc(3600)
[2]11/7/2007 09:22:48: start DST: 03/25/2007 02:00:00 (1174788000)
[2]11/7/2007 09:22:48: end DST: 10/28/2007 03:00:00 (1193540400)
[5]11/7/2007 09:22:48: sip::process_auth:Match challenge for user=2029643, realm=sipgate.de
[2]11/7/2007 09:22:49: Registered at registrar as [email][email protected][/email] (Expires: 3600 secs)
[5]11/7/2007 09:24:17: Dialog 2/1 going to trying
[5]11/7/2007 09:24:17: sip::process_auth:Match challenge for user=2029643, realm=sipgate.de
[5]11/7/2007 09:24:17: Dialog 2/1 going to proceeding
[5]11/7/2007 09:24:18: Dialog 2/1 going to early
[5]11/7/2007 09:24:24: Dialog 2/1 going to confirmed
[5]11/7/2007 09:26:00: Received STUN packet that could not be handled
[5]11/7/2007 09:26:01: Received STUN packet that could not be handled
[5]11/7/2007 09:26:02: Received STUN packet that could not be handled
[5]11/7/2007 09:28:17: Received STUN packet that could not be handled
[5]11/7/2007 09:28:18: Received STUN packet that could not be handled
[5]11/7/2007 09:28:19: Received STUN packet that could not be handled
[5]11/7/2007 09:28:19: Received STUN packet that could not be handled
[5]11/7/2007 09:28:19: Received STUN packet that could not be handled
[5]11/7/2007 09:33:38: Received STUN packet that could not be handled
[5]11/7/2007 09:35:36: Received STUN packet that could not be handled
[5]11/7/2007 09:35:37: Received STUN packet that could not be handled
[5]11/7/2007 09:35:38: Received STUN packet that could not be handled
[5]11/7/2007 09:35:40: Received STUN packet that could not be handled
[5]11/7/2007 09:35:41: Received STUN packet that could not be handled
[5]11/7/2007 09:36:48: Received STUN packet that could not be handled
[5]11/7/2007 09:50:18: Dialog 4/3 going to trying
[5]11/7/2007 09:50:18: sip::process_auth:Match challenge for user=2029643, realm=sipgate.de
[5]11/7/2007 09:50:18: Dialog 4/3 going to proceeding
[5]11/7/2007 09:50:22: Dialog 4/3 going to early
[5]11/7/2007 09:50:28: timeout::callback: Registering with timeout of 0 ms
[5]11/7/2007 09:50:28: timeout::callback: Registering with timeout of 0 ms
[5]11/7/2007 09:50:35: Dialog 5/4 going to trying
[5]11/7/2007 09:50:35: sip::process_auth:Match challenge for user=2029643, realm=sipgate.de
[5]11/7/2007 09:50:35: Dialog 5/4 going to proceeding
[5]11/7/2007 09:50:35: Dialog 5/4 going to early
[5]11/7/2007 09:50:39: Dialog 5/4 going to confirmed
[5]11/7/2007 09:52:01: Dialog 10/9 going to trying
[5]11/7/2007 09:52:01: sip::process_auth:Match challenge for user=2029643, realm=sipgate.de
[5]11/7/2007 09:52:01: Dialog 10/9 going to proceeding
[5]11/7/2007 09:52:02: Dialog 10/9 going to early
[5]11/7/2007 09:52:05: Dialog 10/9 going to confirmed
[5]11/7/2007 09:52:49: sip::process_auth:Match challenge for user=2029643, realm=sipgate.de
[2]11/7/2007 09:52:49: Registered at registrar as [email][email protected][/email] (Expires: 3600 secs)
[5]11/7/2007 09:57:08: Dialog 11/10 going to trying
[5]11/7/2007 09:57:08: sip::process_auth:Match challenge for user=2029643, realm=sipgate.de
[5]11/7/2007 09:57:08: Dialog 11/10 going to proceeding
[5]11/7/2007 09:57:09: Dialog 11/10 going to early
[5]11/7/2007 09:57:19: timeout::callback: Registering with timeout of 0 ms
[5]11/7/2007 09:57:19: timeout::callback: Registering with timeout of 0 ms
[5]11/7/2007 09:57:31: Dialog -2/11 going to early
[5]11/7/2007 09:57:34: Dialog -2/11 going to confirmed
[5]11/7/2007 09:57:52: Dialog -2/11 going to terminated
[5]11/7/2007 09:57:53: timeout::callback: Registering with timeout of 0 ms
[8]11/7/2007 10:22:46: No special routing, routing to sip:[email protected];type=user;vendor=snom;product=snom300
[8]11/7/2007 10:22:46: route_pending_packet 1000047: entry=url ? sip:[email protected];type=user;vendor=snom;product=snom300
[8]11/7/2007 10:22:46: DNS cache_lookup: naptr sipgate.de -> 
[8]11/7/2007 10:22:46: route_pending_packet 1000047: entry=srv udp _sip._udp.sipgate.de
[8]11/7/2007 10:22:46: DNS cache_lookup: srv _sip._udp.sipgate.de -> 0 0 sipgate.de 5060

[8]11/7/2007 10:22:46: route_pending_packet 1000047: entry=a udp sipgate.de 5060
[8]11/7/2007 10:22:46: DNS cache_lookup: a sipgate.de -> 217.10.79.9
[8]11/7/2007 10:22:46: route_pending_packet 1000047: entry=udp 217.10.79.9 5060
[8]11/7/2007 10:22:46: Send Packet SUBSCRIBE
[8]11/7/2007 10:22:48: DNS Cache: Removing naptr sipgate.de
[8]11/7/2007 10:22:48: DNS Cache: Removing srv _sips._tcp.sipgate.de
[7]11/7/2007 10:22:48: NTP: on_ntp_packet() 1: start
[7]11/7/2007 10:22:48: NTP: on_ntp_packet() 2: resend.pending
[7]11/7/2007 10:22:48: NTP: on_ntp_packet() 3: refresh.callback
[2]11/7/2007 10:22:48: start_dst(1174788000) end_dst(1193540400) offset_dst(3600) offset_utc(3600)
[2]11/7/2007 10:22:48: start DST: 03/25/2007 02:00:00 (1174788000)
[2]11/7/2007 10:22:48: end DST: 10/28/2007 03:00:00 (1193540400)
[7]11/7/2007 10:22:48: NTP: on_ntp_packet() 4: leaving
[8]11/7/2007 10:22:48: DNS Cache: Removing srv _sip._tcp.sipgate.de
[8]11/7/2007 10:22:49: No special routing, routing to sip:sipgate.de
[8]11/7/2007 10:22:49: route_pending_packet 1000048: entry=url ? sip:sipgate.de
[8]11/7/2007 10:22:49: No special routing, routing to sip:sipgate.de
[8]11/7/2007 10:22:49: route_pending_packet 1000049: entry=url ? sip:sipgate.de
[8]11/7/2007 10:22:49: DNS Cache: Add naptr sipgate.de =  (ttl=3600)
[8]11/7/2007 10:22:49: route_pending_packet 1000049: entry=url ? sip:sipgate.de
[8]11/7/2007 10:22:49: DNS cache_lookup: naptr sipgate.de -> 
[8]11/7/2007 10:22:49: route_pending_packet 1000049: entry=srv udp _sip._udp.sipgate.de
[8]11/7/2007 10:22:49: DNS cache_lookup: srv _sip._udp.sipgate.de -> 0 0 sipgate.de 5060

[8]11/7/2007 10:22:49: route_pending_packet 1000049: entry=a udp sipgate.de 5060
[8]11/7/2007 10:22:49: DNS cache_lookup: a sipgate.de -> 217.10.79.9
[8]11/7/2007 10:22:49: route_pending_packet 1000049: entry=udp 217.10.79.9 5060
[8]11/7/2007 10:22:49: route_pending_packet 1000049: entry=a udp sipgate.de 5060
[8]11/7/2007 10:22:49: DNS cache_lookup: a sipgate.de -> 217.10.79.9
[8]11/7/2007 10:22:49: route_pending_packet 1000049: entry=udp 217.10.79.9 5060
[7]11/7/2007 10:22:49: Trusted IP Addresses: udp:217.10.79.9
[8]11/7/2007 10:22:49: route_pending_packet 1000048: entry=url ? sip:sipgate.de
[8]11/7/2007 10:22:49: DNS cache_lookup: naptr sipgate.de -> 
[8]11/7/2007 10:22:49: route_pending_packet 1000048: entry=srv udp _sip._udp.sipgate.de
[8]11/7/2007 10:22:49: DNS cache_lookup: srv _sip._udp.sipgate.de -> 0 0 sipgate.de 5060

[8]11/7/2007 10:22:49: route_pending_packet 1000048: entry=a udp sipgate.de 5060
[8]11/7/2007 10:22:49: DNS cache_lookup: a sipgate.de -> 217.10.79.9
[8]11/7/2007 10:22:49: route_pending_packet 1000048: entry=udp 217.10.79.9 5060
[8]11/7/2007 10:22:49: Send Packet REGISTER
[5]11/7/2007 10:22:49: sip::process_auth:Match challenge for user=2029643, realm=sipgate.de
[8]11/7/2007 10:22:49: Routing to explicit plan udp 217.10.79.9 5060
[8]11/7/2007 10:22:49: route_pending_packet 1000050: entry=udp 217.10.79.9 5060
[8]11/7/2007 10:22:49: Send Packet REGISTER
[2]11/7/2007 10:22:49: Registered at registrar as [email][email protected][/email] (Expires: 3600 secs)

 

[der_Gersthofer]

Mit ziemlicher Sicherheit eine Frage der Einstellungen am Router

Bitte mal den WICHTIG Thread lesen, sonst ist das nur ein Rumgerate.

 

[boboflo]

Hallo danke für deine Antwort,

ich habe nun eine Signatur angehängt und habe gerade erfahren, dass das Portforwarding bei unserem Router wieder rausgenommen wurde. Ich werde das nun noch mal ändern lassen und dann nochmal testen ob das Telefon funktioniert.