K
konqi
Guest
Hi @ all,
vorweg: ja ich weiß das Thema is ähnlich zu diesem: http://www.ip-phone-forum.de/showthread.php?t=105547
Doch die dortigen Lösungsansätze helfen kein bisschen und sind wenig Snom spezifisch.
Zum Problem:
Wir setzen hier derzeit im Unternehmen 17 Snom190 und neuerdings 4
Snom320 Telefone ein. Nun haben wir sehr viele notices und warnings in
Asterisk die ich mir nicht weiter erklären kann und leider auch mit
dem Studium der Debugmeldungen nicht weiter komme.
Server ist 172.20.1.254 in einem Class B private Netz
Alle Telefone im selben Netz im Bereich 172.20.20.x
^^
(NAT unnötig)
Anbei daher drei Auszüge aus den Logfiles.
sip_1: zeigt einen Fehler, der neuerdings nur mit den 320ern
auftaucht. Ein setzen der Option canreinvite=no (wie im Obigen Thread) brachte leider auch keine Besserung.
sip_2: zeigt eine Meldung, die ebenfalls nur mit 320ern auftaucht.
diese erscheinen meist sofort nach den Meldungen wie sie in
sip_3 zu sehen sind:
Letztere Meldungen (dass der SUBSCRIBE
fehlschlägt) kommt allerdings auch rel. häufig bei den alten 190ern
Snoms vor. Insbesondere haben wir im Laufe der Zeit ein paar
SIP-Accounts "umgezogen" und scheinbar versuchen sich manche Telefone
weiterhin mit der alten Kennung anzumelden, obwohl diese nachweislich
nicht mehr in der Leitungs-Konfiguration enthalten ist. Bei den
(neuen) Snom320 Geräten ist dies aber absolut unerklärlich, da diese
ganz "frisch" sind und lediglich je einen Account aktiviert haben der
auch als "OK" angezeigt wird.
Ich wäre um Hinweise dankbar diese "Fehler" zu beheben damit in den
Logfiles wirklich nur noch wichtiges erscheint, insbesondere da wir
unsere Infrastruktur mit weiteren Snom320 Geräten verstärken wollen.
Danke und Gruß,
~Marcel
vorweg: ja ich weiß das Thema is ähnlich zu diesem: http://www.ip-phone-forum.de/showthread.php?t=105547
Doch die dortigen Lösungsansätze helfen kein bisschen und sind wenig Snom spezifisch.
Zum Problem:
Wir setzen hier derzeit im Unternehmen 17 Snom190 und neuerdings 4
Snom320 Telefone ein. Nun haben wir sehr viele notices und warnings in
Asterisk die ich mir nicht weiter erklären kann und leider auch mit
dem Studium der Debugmeldungen nicht weiter komme.
Server ist 172.20.1.254 in einem Class B private Netz
Alle Telefone im selben Netz im Bereich 172.20.20.x
^^
(NAT unnötig)
Anbei daher drei Auszüge aus den Logfiles.
sip_1: zeigt einen Fehler, der neuerdings nur mit den 320ern
auftaucht. Ein setzen der Option canreinvite=no (wie im Obigen Thread) brachte leider auch keine Besserung.
Code:
[...]
---
Retransmitting #5 (NAT) to 172.20.20.20:2060:
SIP/2.0 403 Forbidden
Via: SIP/2.0/UDP 172.20.20.20:2060;branch=z9hG4bK-3p1kqw05fp2r;received=172.20.20.20;rport=2060
From: <sip:172.20.20.20:5060>;tag=0koouong9c
To: <sip:[email protected]>;tag=as4176a20e
Call-ID: 3c267009ecd1-062dds3j22ol@snom320-XXXXXXXXXXXX
CSeq: 31 SUBSCRIBE
User-Agent: asterisk_server
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Content-Length: 0
---
Retransmitting #5 (NAT) to 172.20.20.20:2060:
SIP/2.0 403 Forbidden
Via: SIP/2.0/UDP 172.20.20.20:2060;branch=z9hG4bK-2ll0ebuf4ag7;received=172.20.20.20;rport=2060
From: <sip:172.20.20.20:5060>;tag=gm7k2gcv8c
To: <sip:[email protected]>;tag=as0ec71585
Call-ID: 3c267009ecd1-dvjhf5jna8ju@snom320-XXXXXXXXXXXX
CSeq: 31 SUBSCRIBE
User-Agent: asterisk_server
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Content-Length: 0
---
Retransmitting #5 (NAT) to 172.20.20.20:2060:
SIP/2.0 403 Forbidden
Via: SIP/2.0/UDP 172.20.20.20:2060;branch=z9hG4bK-g0jh8zmco7gy;received=172.20.20.20;rport=2060
From: <sip:172.20.20.20:5060>;tag=tyk5t8hs3y
To: <sip:[email protected]>;tag=as51895c92
Call-ID: 3c267009ef42-1wd4jnw215ko@snom320-XXXXXXXXXXXX
CSeq: 31 SUBSCRIBE
User-Agent: asterisk_server
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Content-Length: 0
---
Retransmitting #5 (NAT) to 172.20.20.20:2060:
SIP/2.0 403 Forbidden
Via: SIP/2.0/UDP 172.20.20.20:2060;branch=z9hG4bK-30oi9quccfca;received=172.20.20.20;rport=2060
From: <sip:172.20.20.20:5060>;tag=afk7n3lm6w
To: <sip:[email protected]>;tag=as512a39ef
Call-ID: 3c267009ef42-74tnqusb31h3@snom320-XXXXXXXXXXXX
CSeq: 31 SUBSCRIBE
User-Agent: asterisk_server
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Content-Length: 0
---
Retransmitting #5 (NAT) to 172.20.20.20:2060:
SIP/2.0 403 Forbidden
Via: SIP/2.0/UDP 172.20.20.20:2060;branch=z9hG4bK-aqpy05qgp9xy;received=172.20.20.20;rport=2060
From: <sip:172.20.20.20:5060>;tag=ewf00lwxrx
To: <sip:[email protected]>;tag=as66d9bc86
Call-ID: 3c267009f1b3-6adz5g0njzi3@snom320-XXXXXXXXXXXX
CSeq: 31 SUBSCRIBE
User-Agent: asterisk_server
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Content-Length: 0
---
Retransmitting #5 (NAT) to 172.20.20.20:2060:
SIP/2.0 403 Forbidden
Via: SIP/2.0/UDP 172.20.20.20:2060;branch=z9hG4bK-s4u0bazzunh4;received=172.20.20.20;rport=2060
From: <sip:172.20.20.20:5060>;tag=8kf5x6hicl
To: <sip:[email protected]>;tag=as779cc940
Call-ID: 3c267009f1b3-y2si9chbzs8a@snom320-XXXXXXXXXXXX
CSeq: 31 SUBSCRIBE
User-Agent: asterisk_server
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Content-Length: 0
---
Retransmitting #5 (NAT) to 172.20.20.20:2060:
SIP/2.0 403 Forbidden
Via: SIP/2.0/UDP 172.20.20.20:2060;branch=z9hG4bK-dbgpbcjlm8km;received=172.20.20.20;rport=2060
From: <sip:172.20.20.20:5060>;tag=ism0qz1upn
To: <sip:[email protected]>;tag=as0ebd6d83
Call-ID: 3c267009f1b3-rcitni5fs1ws@snom320-XXXXXXXXXXXX
CSeq: 31 SUBSCRIBE
User-Agent: asterisk_server
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Content-Length: 0
---
Retransmitting #6 (NAT) to 172.20.20.20:2060:
SIP/2.0 403 Forbidden
Via: SIP/2.0/UDP 172.20.20.20:2060;branch=z9hG4bK-xk9bw4320qpj;received=172.20.20.20;rport=2060
From: <sip:172.20.20.20:5060>;tag=6d4hc4t1fv
To: <sip:[email protected]>;tag=as003bed64
Call-ID: 3c267009e7ef-9vzxau8tg151@snom320-XXXXXXXXXXXX
CSeq: 31 SUBSCRIBE
User-Agent: asterisk_server
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Content-Length: 0
---
Retransmitting #6 (NAT) to 172.20.20.20:2060:
SIP/2.0 403 Forbidden
Via: SIP/2.0/UDP 172.20.20.20:2060;branch=z9hG4bK-ov344fpbw0bw;received=172.20.20.20;rport=2060
From: <sip:172.20.20.20:5060>;tag=zphtrc4ml2
To: <sip:[email protected]>;tag=as507e3ca4
Call-ID: 3c267009ea60-qevi7v4ww2p1@snom320-XXXXXXXXXXXX
CSeq: 31 SUBSCRIBE
User-Agent: asterisk_server
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Content-Length: 0
---
Retransmitting #6 (NAT) to 172.20.20.20:2060:
SIP/2.0 403 Forbidden
Via: SIP/2.0/UDP 172.20.20.20:2060;branch=z9hG4bK-fj4dctjuds5u;received=172.20.20.20;rport=2060
From: <sip:172.20.20.20:5060>;tag=t8sdudfkgy
To: <sip:[email protected]>;tag=as4301a1e8
Call-ID: 3c267009ea60-qdtuuqgjr8do@snom320-XXXXXXXXXXXX
CSeq: 31 SUBSCRIBE
User-Agent: asterisk_server
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Content-Length: 0
---
Retransmitting #6 (NAT) to 172.20.20.20:2060:
SIP/2.0 403 Forbidden
Via: SIP/2.0/UDP 172.20.20.20:2060;branch=z9hG4bK-htw135kr1og5;received=172.20.20.20;rport=2060
From: <sip:172.20.20.20:5060>;tag=fg3ugj8u0z
To: <sip:[email protected]>;tag=as3a44c017
Call-ID: 3c267009ecd1-k67l9itmq6ma@snom320-XXXXXXXXXXXX
CSeq: 31 SUBSCRIBE
User-Agent: asterisk_server
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Content-Length: 0
---
Retransmitting #6 (NAT) to 172.20.20.20:2060:
SIP/2.0 403 Forbidden
Via: SIP/2.0/UDP 172.20.20.20:2060;branch=z9hG4bK-3p1kqw05fp2r;received=172.20.20.20;rport=2060
From: <sip:172.20.20.20:5060>;tag=0koouong9c
To: <sip:[email protected]>;tag=as4176a20e
Call-ID: 3c267009ecd1-062dds3j22ol@snom320-XXXXXXXXXXXX
CSeq: 31 SUBSCRIBE
User-Agent: asterisk_server
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Content-Length: 0
---
Retransmitting #6 (NAT) to 172.20.20.20:2060:
SIP/2.0 403 Forbidden
Via: SIP/2.0/UDP 172.20.20.20:2060;branch=z9hG4bK-2ll0ebuf4ag7;received=172.20.20.20;rport=2060
From: <sip:172.20.20.20:5060>;tag=gm7k2gcv8c
To: <sip:[email protected]>;tag=as0ec71585
Call-ID: 3c267009ecd1-dvjhf5jna8ju@snom320-XXXXXXXXXXXX
CSeq: 31 SUBSCRIBE
User-Agent: asterisk_server
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Content-Length: 0
---
Retransmitting #6 (NAT) to 172.20.20.20:2060:
SIP/2.0 403 Forbidden
Via: SIP/2.0/UDP 172.20.20.20:2060;branch=z9hG4bK-g0jh8zmco7gy;received=172.20.20.20;rport=2060
From: <sip:172.20.20.20:5060>;tag=tyk5t8hs3y
To: <sip:[email protected]>;tag=as51895c92
Call-ID: 3c267009ef42-1wd4jnw215ko@snom320-XXXXXXXXXXXX
CSeq: 31 SUBSCRIBE
User-Agent: asterisk_server
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Content-Length: 0
---
Retransmitting #6 (NAT) to 172.20.20.20:2060:
SIP/2.0 403 Forbidden
Via: SIP/2.0/UDP 172.20.20.20:2060;branch=z9hG4bK-30oi9quccfca;received=172.20.20.20;rport=2060
From: <sip:172.20.20.20:5060>;tag=afk7n3lm6w
To: <sip:[email protected]>;tag=as512a39ef
Call-ID: 3c267009ef42-74tnqusb31h3@snom320-XXXXXXXXXXXX
CSeq: 31 SUBSCRIBE
User-Agent: asterisk_server
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Content-Length: 0
---
Retransmitting #6 (NAT) to 172.20.20.20:2060:
SIP/2.0 403 Forbidden
Via: SIP/2.0/UDP 172.20.20.20:2060;branch=z9hG4bK-aqpy05qgp9xy;received=172.20.20.20;rport=2060
From: <sip:172.20.20.20:5060>;tag=ewf00lwxrx
To: <sip:[email protected]>;tag=as66d9bc86
Call-ID: 3c267009f1b3-6adz5g0njzi3@snom320-XXXXXXXXXXXX
CSeq: 31 SUBSCRIBE
User-Agent: asterisk_server
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Content-Length: 0
---
Retransmitting #6 (NAT) to 172.20.20.20:2060:
SIP/2.0 403 Forbidden
Via: SIP/2.0/UDP 172.20.20.20:2060;branch=z9hG4bK-s4u0bazzunh4;received=172.20.20.20;rport=2060
From: <sip:172.20.20.20:5060>;tag=8kf5x6hicl
To: <sip:[email protected]>;tag=as779cc940
Call-ID: 3c267009f1b3-y2si9chbzs8a@snom320-XXXXXXXXXXXX
CSeq: 31 SUBSCRIBE
User-Agent: asterisk_server
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Content-Length: 0
---
Retransmitting #6 (NAT) to 172.20.20.20:2060:
SIP/2.0 403 Forbidden
Via: SIP/2.0/UDP 172.20.20.20:2060;branch=z9hG4bK-dbgpbcjlm8km;received=172.20.20.20;rport=2060
From: <sip:172.20.20.20:5060>;tag=ism0qz1upn
To: <sip:[email protected]>;tag=as0ebd6d83
Call-ID: 3c267009f1b3-rcitni5fs1ws@snom320-XXXXXXXXXXXX
CSeq: 31 SUBSCRIBE
User-Agent: asterisk_server
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Content-Length: 0
---
Destroying call '3c267009d1f6-uumhavm0nqly@snom320-XXXXXXXXXXXX'
Feb 21 11:27:33 WARNING[26846]: chan_sip.c:1227 retrans_pkt: Maximum retries exceeded on transmission 3c267009e7ef-9vzxau8tg151@snom320-XXXXXXXXXXXX for seqno 31 (Critical Response)
Destroying call '3c267009e7ef-9vzxau8tg151@snom320-XXXXXXXXXXXX'
Feb 21 11:27:33 WARNING[26846]: chan_sip.c:1227 retrans_pkt: Maximum retries exceeded on transmission 3c267009ea60-qevi7v4ww2p1@snom320-XXXXXXXXXXXX for seqno 31 (Critical Response)
Destroying call '3c267009ea60-qevi7v4ww2p1@snom320-XXXXXXXXXXXX'
Feb 21 11:27:33 WARNING[26846]: chan_sip.c:1227 retrans_pkt: Maximum retries exceeded on transmission 3c267009ea60-qdtuuqgjr8do@snom320-XXXXXXXXXXXX for seqno 31 (Critical Response)
Feb 21 11:27:33 WARNING[26846]: chan_sip.c:1227 retrans_pkt: Maximum retries exceeded on transmission 3c267009ecd1-k67l9itmq6ma@snom320-XXXXXXXXXXXX for seqno 31 (Critical Response)
Destroying call '3c267009ecd1-k67l9itmq6ma@snom320-XXXXXXXXXXXX'
Destroying call '3c267009ea60-qdtuuqgjr8do@snom320-XXXXXXXXXXXX'
Feb 21 11:27:33 WARNING[26846]: chan_sip.c:1227 retrans_pkt: Maximum retries exceeded on transmission 3c267009ecd1-062dds3j22ol@snom320-XXXXXXXXXXXX for seqno 31 (Critical Response)
Destroying call '3c267009ecd1-062dds3j22ol@snom320-XXXXXXXXXXXX'
Feb 21 11:27:33 WARNING[26846]: chan_sip.c:1227 retrans_pkt: Maximum retries exceeded on transmission 3c267009ecd1-dvjhf5jna8ju@snom320-XXXXXXXXXXXX for seqno 31 (Critical Response)
Destroying call '3c267009ecd1-dvjhf5jna8ju@snom320-XXXXXXXXXXXX'
Feb 21 11:27:33 WARNING[26846]: chan_sip.c:1227 retrans_pkt: Maximum retries exceeded on transmission 3c267009ef42-1wd4jnw215ko@snom320-XXXXXXXXXXXX for seqno 31 (Critical Response)
Destroying call '3c267009ef42-1wd4jnw215ko@snom320-XXXXXXXXXXXX'
Feb 21 11:27:33 WARNING[26846]: chan_sip.c:1227 retrans_pkt: Maximum retries exceeded on transmission 3c267009ef42-74tnqusb31h3@snom320-XXXXXXXXXXXX for seqno 31 (Critical Response)
Feb 21 11:27:33 WARNING[26846]: chan_sip.c:1227 retrans_pkt: Maximum retries exceeded on transmission 3c267009f1b3-6adz5g0njzi3@snom320-XXXXXXXXXXXX for seqno 31 (Critical Response)
Destroying call '3c267009f1b3-6adz5g0njzi3@snom320-XXXXXXXXXXXX'
Destroying call '3c267009ef42-74tnqusb31h3@snom320-XXXXXXXXXXXX'
Feb 21 11:27:33 WARNING[26846]: chan_sip.c:1227 retrans_pkt: Maximum retries exceeded on transmission 3c267009f1b3-y2si9chbzs8a@snom320-XXXXXXXXXXXX for seqno 31 (Critical Response)
Destroying call '3c267009f1b3-y2si9chbzs8a@snom320-XXXXXXXXXXXX'
Feb 21 11:27:33 WARNING[26846]: chan_sip.c:1227 retrans_pkt: Maximum retries exceeded on transmission 3c267009f1b3-rcitni5fs1ws@snom320-XXXXXXXXXXXX for seqno 31 (Critical Response)
Destroying call '3c267009f1b3-rcitni5fs1ws@snom320-XXXXXXXXXXXX'
sip_2: zeigt eine Meldung, die ebenfalls nur mit 320ern auftaucht.
Code:
Feb 21 12:10:19 WARNING[26846]: chan_sip.c:1227 retrans_pkt: Maximum retries exceeded on transmission 3c267009e09c-a3pxnfid9vzx@snom320-XXXXXXXXXXXX for seqno 963 (Critical Response)
Feb 21 12:10:19 WARNING[26846]: chan_sip.c:1227 retrans_pkt: Maximum retries exceeded on transmission 3c267009e30d-6lz8is4hqevi@snom320-XXXXXXXXXXXX for seqno 963 (Critical Response)
Feb 21 12:10:19 WARNING[26846]: chan_sip.c:1227 retrans_pkt: Maximum retries exceeded on transmission 3c267009e30d-khyoi8meqdtu@snom320-XXXXXXXXXXXX for seqno 963 (Critical Response)
Feb 21 12:10:19 WARNING[26846]: chan_sip.c:1227 retrans_pkt: Maximum retries exceeded on transmission 3c267009e57e-spfyn6chk67l@snom320-XXXXXXXXXXXX for seqno 963 (Critical Response)
Feb 21 12:10:19 WARNING[26846]: chan_sip.c:1227 retrans_pkt: Maximum retries exceeded on transmission 3c267009e57e-vsbrtfx0062d@snom320-XXXXXXXXXXXX for seqno 963 (Critical Response)
Feb 21 12:10:19 WARNING[26846]: chan_sip.c:1227 retrans_pkt: Maximum retries exceeded on transmission 3c267009e57e-b5fspgirdvjh@snom320-XXXXXXXXXXXX for seqno 963 (Critical Response)
Feb 21 12:10:20 WARNING[26846]: chan_sip.c:1227 retrans_pkt: Maximum retries exceeded on transmission 3c267009e7ef-jum15kxo1wd4@snom320-XXXXXXXXXXXX for seqno 963 (Critical Response)
Feb 21 12:10:20 WARNING[26846]: chan_sip.c:1227 retrans_pkt: Maximum retries exceeded on transmission 3c267009e7ef-81h592lm74tn@snom320-XXXXXXXXXXXX for seqno 963 (Critical Response)
Feb 21 12:10:20 WARNING[26846]: chan_sip.c:1227 retrans_pkt: Maximum retries exceeded on transmission 3c267009ea60-bj8w5zky6adz@snom320-XXXXXXXXXXXX for seqno 963 (Critical Response)
Feb 21 12:10:20 WARNING[26846]: chan_sip.c:1227 retrans_pkt: Maximum retries exceeded on transmission 3c267009ea60-id82vfwsy2si@snom320-XXXXXXXXXXXX for seqno 963 (Critical Response)
Feb 21 12:10:20 WARNING[26846]: chan_sip.c:1227 retrans_pkt: Maximum retries exceeded on transmission 3c267009ea60-0hbxu9jmrcit@snom320-XXXXXXXXXXXX for seqno 963 (Critical Response)
sip_3 zu sehen sind:
Code:
Feb 21 12:09:59 NOTICE[26846]: chan_sip.c:11007 handle_request_subscribe: Failed to authenticate user <sip:172.20.20.23:5060>;tag=mi0wxwhp6d for SUBSCRIBE
Feb 21 12:09:59 NOTICE[26846]: chan_sip.c:11007 handle_request_subscribe: Failed to authenticate user <sip:172.20.20.23:5060>;tag=3ngks2ddzp for SUBSCRIBE
Feb 21 12:09:59 NOTICE[26846]: chan_sip.c:11007 handle_request_subscribe: Failed to authenticate user <sip:172.20.20.23:5060>;tag=y60bj0hgt8 for SUBSCRIBE
Feb 21 12:09:59 NOTICE[26846]: chan_sip.c:11007 handle_request_subscribe: Failed to authenticate user <sip:172.20.20.23:5060>;tag=1mty226afg for SUBSCRIBE
Feb 21 12:09:59 NOTICE[26846]: chan_sip.c:11007 handle_request_subscribe: Failed to authenticate user <sip:172.20.20.23:5060>;tag=lxb7m64p0k for SUBSCRIBE
Feb 21 12:09:59 NOTICE[26846]: chan_sip.c:11007 handle_request_subscribe: Failed to authenticate user <sip:172.20.20.23:5060>;tag=n9bresr2gm for SUBSCRIBE
Feb 21 12:10:00 NOTICE[26846]: chan_sip.c:11007 handle_request_subscribe: Failed to authenticate user <sip:172.20.20.23:5060>;tag=nfcehtg4ty for SUBSCRIBE
Feb 21 12:10:00 NOTICE[26846]: chan_sip.c:11007 handle_request_subscribe: Failed to authenticate user <sip:172.20.20.23:5060>;tag=6mxnrplbaf for SUBSCRIBE
Feb 21 12:10:00 NOTICE[26846]: chan_sip.c:11007 handle_request_subscribe: Failed to authenticate user <sip:172.20.20.23:5060>;tag=d40fvravew for SUBSCRIBE
Feb 21 12:10:00 NOTICE[26846]: chan_sip.c:11007 handle_request_subscribe: Failed to authenticate user <sip:172.20.20.23:5060>;tag=d4dnfsku8k for SUBSCRIBE
Feb 21 12:10:00 NOTICE[26846]: chan_sip.c:11007 handle_request_subscribe: Failed to authenticate user <sip:172.20.20.23:5060>;tag=bapv4wx0is for SUBSCRIBE
Letztere Meldungen (dass der SUBSCRIBE
fehlschlägt) kommt allerdings auch rel. häufig bei den alten 190ern
Snoms vor. Insbesondere haben wir im Laufe der Zeit ein paar
SIP-Accounts "umgezogen" und scheinbar versuchen sich manche Telefone
weiterhin mit der alten Kennung anzumelden, obwohl diese nachweislich
nicht mehr in der Leitungs-Konfiguration enthalten ist. Bei den
(neuen) Snom320 Geräten ist dies aber absolut unerklärlich, da diese
ganz "frisch" sind und lediglich je einen Account aktiviert haben der
auch als "OK" angezeigt wird.
Ich wäre um Hinweise dankbar diese "Fehler" zu beheben damit in den
Logfiles wirklich nur noch wichtiges erscheint, insbesondere da wir
unsere Infrastruktur mit weiteren Snom320 Geräten verstärken wollen.
Danke und Gruß,
~Marcel