McFone Posted September 5, 2013 Report Share Posted September 5, 2013 Hi, we have a lot of CRITIC errors for your snom 720 the fone is working! We use PNP with TLS and a Voice VLAN with LLDP Any idea why the log has a lot of error messages? thanks 5/9/2013 14:33:38 [NOTICE] PHN: TLS: received alert 0, level 15/9/2013 14:33:38 [NOTICE] PHN: TLS: received alert 0, level 15/9/2013 14:33:38 [ERROR ] PHN: TPL: Socket Error: 45/24/connected, read -> No such file or directory (2)5/9/2013 14:33:38 [ERROR ] PHN: TPL: Socket Error: 44/23/connected, read -> No such file or directory (2)5/9/2013 14:33:53 [NOTICE] PHN: TPL: Socket 43 idle/connect timeout5/9/2013 14:33:57 [CRITIC] PHN: SIP: packet 1001789 dest invalid tls:xx.xx.xx.xx:5061 for Request DISCOVER/-5/9/2013 14:33:57 [CRITIC] PHN: SIP: Registered at registrar as 38@pbx.xx.de (Expires: 58 secs)5/9/2013 14:34:17 [NOTICE] PHN: TPL: Socket 46 idle/connect timeout5/9/2013 14:34:26 [CRITIC] PHN: SIP: packet 1001793 dest invalid tls:xx.xx.xx.xx:5061 for Request DISCOVER/-5/9/2013 14:34:26 [CRITIC] PHN: SIP: Registered at registrar as 38@pbx.xx.de (Expires: 59 secs)5/9/2013 14:34:39 [NOTICE] PHN: TPL: Socket 47 idle/connect timeout5/9/2013 14:34:56 [CRITIC] PHN: SIP: packet 1001795 dest invalid tls:xx.xx.xx.xx:5061 for Request DISCOVER/-5/9/2013 14:34:56 [CRITIC] PHN: SIP: Registered at registrar as 38@pbx.xx.de (Expires: 62 secs)5/9/2013 14:35:12 [NOTICE] PHN: TPL: Socket 48 idle/connect timeout5/9/2013 14:35:27 [CRITIC] PHN: SIP: packet 1001799 dest invalid tls:xx.xx.xx.xx:5061 for Request DISCOVER/-5/9/2013 14:35:27 [CRITIC] PHN: SIP: Registered at registrar as 38@pbx.xx.de (Expires: 60 secs)5/9/2013 14:35:57 [CRITIC] PHN: SIP: packet 1001802 dest invalid tls:xx.xx.xx.xx:5061 for Request DISCOVER/-5/9/2013 14:35:57 [CRITIC] PHN: SIP: Registered at registrar as 38@pbx.xx.de (Expires: 60 secs)5/9/2013 14:36:27 [CRITIC] PHN: SIP: packet 1001806 dest invalid tls:xx.xx.xx.xx:5061 for Request DISCOVER/-5/9/2013 14:36:27 [CRITIC] PHN: SIP: Registered at registrar as 38@pbx.xx.de (Expires: 61 secs)5/9/2013 14:36:58 [CRITIC] PHN: SIP: packet 1001810 dest invalid tls:xx.xx.xx.xx:5061 for Request DISCOVER/-5/9/2013 14:36:58 [CRITIC] PHN: SIP: Registered at registrar as 38@pbx.xx.de (Expires: 60 secs)5/9/2013 14:37:28 [CRITIC] PHN: SIP: packet 1001813 dest invalid tls:xx.xx.xx.xx:5061 for Request DISCOVER/-5/9/2013 14:37:28 [CRITIC] PHN: SIP: Registered at registrar as 38@pbx.xx.de (Expires: 59 secs)5/9/2013 14:37:57 [CRITIC] PHN: SIP: packet 1001817 dest invalid tls:xx.xx.xx.xx:5061 for Request DISCOVER/-5/9/2013 14:37:57 [CRITIC] PHN: SIP: Registered at registrar as 38@pbx.xx.de (Expires: 61 secs)5/9/2013 14:38:28 [CRITIC] PHN: SIP: packet 1001821 dest invalid tls:xx.xx.xx.xx:5061 for Request DISCOVER/-5/9/2013 14:38:28 [CRITIC] PHN: SIP: Registered at registrar as 38@pbx.xx.de (Expires: 58 secs)5/9/2013 14:38:57 [CRITIC] PHN: SIP: packet 1001824 dest invalid tls:xx.xx.xx.xx:5061 for Request DISCOVER/-5/9/2013 14:38:57 [CRITIC] PHN: SIP: Registered at registrar as 38@pbx.xx.de (Expires: 58 secs)5/9/2013 14:39:26 [CRITIC] PHN: SIP: packet 1001827 dest invalid tls:xx.xx.xx.xx:5061 for Request DISCOVER/-5/9/2013 14:39:26 [CRITIC] PHN: SIP: Registered at registrar as 38@pbx.xx.de (Expires: 62 secs)5/9/2013 14:39:57 [CRITIC] PHN: SIP: packet 1001831 dest invalid tls:xx.xx.xx.xx:5061 for Request DISCOVER/-5/9/2013 14:39:57 [CRITIC] PHN: SIP: Registered at registrar as 38@pbx.xx.de (Expires: 60 secs)5/9/2013 14:40:27 [CRITIC] PHN: SIP: packet 1001835 dest invalid tls:xx.xx.xx.xx:5061 for Request DISCOVER/-5/9/2013 14:40:27 [CRITIC] PHN: SIP: Registered at registrar as 38@pbx.xx.de (Expires: 60 secs)5/9/2013 14:40:45 [NOTICE] PHN: TPL: Socket 49 idle/connect timeout5/9/2013 14:40:57 [CRITIC] PHN: SIP: packet 1001838 dest invalid tls:xx.xx.xx.xx:5061 for Request DISCOVER/-5/9/2013 14:40:57 [CRITIC] PHN: SIP: Registered at registrar as 38@pbx.xx.de (Expires: 61 secs)5/9/2013 14:41:27 [CRITIC] PHN: SIP: packet 1001842 dest invalid tls:xx.xx.xx.xx:5061 for Request DISCOVER/-5/9/2013 14:41:27 [CRITIC] PHN: SIP: Registered at registrar as 38@pbx.xx.de (Expires: 58 secs) Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted September 5, 2013 Report Share Posted September 5, 2013 Not sure if routing DISCOVER packets should be considered "critical". Also the fact that the phone is registered is not critical IMHO. OTOH the "notice" that the socket timed out would be critical. I would suggest that the log levels in the phone should be reviewed... Quote Link to comment Share on other sites More sharing options...
McFone Posted September 5, 2013 Author Report Share Posted September 5, 2013 we set the log level higher any idea to solve this messages thanks 5/9/2013 19:34:42 [NOTICE] PHN: TPL: Socket 108 idle/connect timeout5/9/2013 19:34:42 [DEBUG2] PHN: WEB: HTTP 108/443 disconnecting5/9/2013 19:34:42 [DEBUG2] PHN: WEB: HTTP 108/443 disconnected5/9/2013 19:34:42 [DEBUG2] PHN: WEB: HTTP 108/443 deleted5/9/2013 19:34:34 [NOTICE] PHN: TLS: received alert 0, level 15/9/2013 19:34:34 [ERROR ] PHN: TPL: Socket Error: 110/24/connected, read -> No such file or directory (2)5/9/2013 19:34:34 [DEBUG2] PHN: WEB: HTTP 110/443 disconnected5/9/2013 19:34:34 [DEBUG2] PHN: WEB: HTTP 110/443 deleted5/9/2013 19:34:34 [NOTICE] PHN: TLS: received alert 0, level 15/9/2013 19:34:34 [ERROR ] PHN: TPL: Socket Error: 109/23/connected, read -> No such file or directory (2)5/9/2013 19:34:34 [DEBUG2] PHN: WEB: HTTP 109/443 disconnected5/9/2013 19:34:34 [DEBUG2] PHN: WEB: HTTP 109/443 deleted5/9/2013 19:34:39 [iNFO ] PHN: SIP: Identity 1 reregister in 292000 ms.5/9/2013 19:34:39 [DEBUG1] PHN: SIP: Routing to outbound proxy: sip:xx.xx.xx.xx:5061;transport=tls5/9/2013 19:34:39 [DEBUG1] PHN: SIP: route pending packet 1003995: entry=url ? sip:xx.xx.xx.xx:5061;transport=tls all 85/9/2013 19:34:39 [DEBUG1] PHN: SIP: route pending packet 1003995: entry=tls xx.xx.xx.xx 5061 all 85/9/2013 19:34:39 [CRITIC] PHN: SIP: packet 1003995 dest invalid tls:xx.xx.xx.xx:5061 for Request DISCOVER/- Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted September 5, 2013 Report Share Posted September 5, 2013 If the phone behind a firewall or in the LAN? It looks to me like the TCP connection is not stable. You might have to make the intervals shorter. Quote Link to comment Share on other sites More sharing options...
McFone Posted September 6, 2013 Author Report Share Posted September 6, 2013 the snomONE is in the datacenter WAN and the phone is in the LAN and we use ACL for the network. To make the intervals shorter for the TCP connections we change in the PBX a value or in the network ? thanks Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted September 6, 2013 Report Share Posted September 6, 2013 Well if you can change it in the network it would be the best solution. If that's not possible, make it shorter in the PBX admin settings (admin/general/system/performance TCP/TLS NAT Refresh). Quote Link to comment Share on other sites More sharing options...
Recommended Posts
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.