IP-Touch 40X8 Dead Air

Post Reply
Blackpepper
Member
Posts: 4
Joined: 25 Sep 2017 07:39

IP-Touch 40X8 Dead Air

Post by Blackpepper » 25 Sep 2017 07:54

Hi Boardies,

some 40X8 EE can call a few internal numbers but the other User cant hear them.


PCX Ver.: R11.1-l1.301-30-a-ge-c0s1

Phone:
Firmware version : 4.33.50 on a 100 Mb hardware
Firmware version Data : 4.33.50
Bootloader version : 4.33.50
SIP : 2.01.20

incvisu -T 100:

25/09/17 11:36:39 000010M|000/00/0/000|=4:0426=IPTOUCH terminal reset 13,00:80:9f:b9:23:17,4644
25/09/17 11:36:39 000010M|005/01/0/191|=5:2053=Terminal 191 in service
25/09/17 11:36:41 000010M|000/00/0/000|=4:0426=IPTOUCH terminal reset 13,00:80:9f:df:60:15,4645
25/09/17 11:36:42 000010M|005/01/0/186|=5:2053=Terminal 186 in service
25/09/17 11:36:43 000010M|000/00/0/000|=4:0426=IPTOUCH terminal reset 13,00:80:9f:ba:8d:59,4641
25/09/17 11:36:45 000010M|005/01/0/192|=5:2053=Terminal 192 in service
25/09/17 11:36:46 000010M|000/00/0/000|=4:0426=IPTOUCH terminal reset 13,00:80:9f:b9:23:4f,1547
25/09/17 11:36:47 000010M|005/01/0/043|=5:2053=Terminal 43 in service
25/09/17 11:36:54 000010M|000/00/0/000|=4:0426=IPTOUCH terminal reset 13,00:80:9f:b9:23:91,4649
25/09/17 11:36:54 000010M|005/01/0/134|=5:2053=Terminal 134 in service
25/09/17 11:41:39 000010M|001/07/0/000|=3:1307=MCDU in distri tab entity 100, col Night , line 4 incorrect or missing
25/09/17 11:41:39 000010M|001/07/0/000|=3:1307=MCDU in distri tab entity 100, col Night , line 4 incorrect or missing
25/09/17 11:41:39 000010M|001/07/0/000|=3:1307=MCDU in distri tab entity 0, col Night , line 4 incorrect or missing
25/09/17 11:42:09 000010M|001/07/0/000|=3:1307=MCDU in distri tab entity 0, col Night , line 4 incorrect or missing
25/09/17 11:50:55 000010M|005/01/0/134|=3:0386=Sig. on IP set: No response from de set 00:80:9f:b9:23:91,4649
25/09/17 11:50:55 000010M|005/01/0/191|=3:0386=Sig. on IP set: No response from de set 00:80:9f:b9:23:17,4644
25/09/17 11:50:58 000010M|005/01/0/186|=3:0386=Sig. on IP set: No response from de set 00:80:9f:df:60:15,4645
25/09/17 11:51:01 000010M|005/01/0/192|=3:0386=Sig. on IP set: No response from de set 00:80:9f:ba:8d:59,4641
25/09/17 11:51:03 000010M|005/01/0/043|=3:0386=Sig. on IP set: No response from de set 00:80:9f:b9:23:4f,1547
25/09/17 11:51:48 000010M|000/00/0/000|=4:0426=IPTOUCH terminal reset 13,00:80:9f:b9:23:91,4649
25/09/17 11:51:48 000010M|000/00/0/000|=4:0426=IPTOUCH terminal reset 13,00:80:9f:b9:23:17,4644
25/09/17 11:51:48 000010M|005/01/0/134|=5:2053=Terminal 134 in service
25/09/17 11:51:48 000010M|005/01/0/191|=5:2053=Terminal 191 in service
25/09/17 11:51:54 000010M|000/00/0/000|=4:0426=IPTOUCH terminal reset 13,00:80:9f:df:60:15,4645
25/09/17 11:51:54 000010M|005/01/0/186|=5:2053=Terminal 186 in service
25/09/17 11:51:56 000010M|000/00/0/000|=4:0426=IPTOUCH terminal reset 13,00:80:9f:b9:23:4f,1547
25/09/17 11:51:56 000010M|005/01/0/043|=5:2053=Terminal 43 in service
25/09/17 11:52:02 000010M|000/00/0/000|=4:0426=IPTOUCH terminal reset 13,00:80:9f:ba:8d:59,4641
25/09/17 11:52:02 000010M|005/01/0/192|=5:2053=Terminal 192 in service


defence 99 on local set :

-026 000-00:00:02.180 code: 4.33.50 data: 4.33.50 sysdate:
-025 000-00:00:35.880 code: 4.33.50 data: 4.33.50 sysdate: 25/09/2017-07:01:08
-024 000-00:07:26.330 reset__: [13] uaudp_lost_connect (1947 ua_udp_protocol.c)
-023 000-00:00:02.180 code: 4.33.50 data: 4.33.50 sysdate:
-022 000-00:00:35.190 code: 4.33.50 data: 4.33.50 sysdate: 25/09/2017-07:08:41
-021 000-00:01:23.220 reset__: [13] uaudp_lost_connect (1947 ua_udp_protocol.c)
-020 000-00:00:02.180 code: 4.33.50 data: 4.33.50 sysdate:
-019 000-00:00:35.980 code: 4.33.50 data: 4.33.50 sysdate: 25/09/2017-07:10:22
-018 000-00:53:29.600 reset__: [13] uaudp_lost_connect (1947 ua_udp_protocol.c)
-017 000-00:00:02.180 code: 4.33.50 data: 4.33.50 sysdate:
-016 000-00:00:35.900 code: 4.33.50 data: 4.33.50 sysdate: 25/09/2017-08:04:09
-015 000-00:42:40.340 reset__: [13] uaudp_lost_connect (1947 ua_udp_protocol.c)
-014 000-00:00:02.180 code: 4.33.50 data: 4.33.50 sysdate:
-013 000-00:00:35.790 code: 4.33.50 data: 4.33.50 sysdate: 25/09/2017-08:46:56
-012 000-00:15:57.530 reset__: [13] uaudp_lost_connect (1947 ua_udp_protocol.c)
-011 000-00:00:02.180 code: 4.33.50 data: 4.33.50 sysdate:
-010 000-00:00:35.600 code: 4.33.50 data: 4.33.50 sysdate: 25/09/2017-09:03:01
-009 000-01:18:22.240 telnet from 192.168.241.2 accepted
-008 000-02:33:34.220 reset__: [13] uaudp_lost_connect (1947 ua_udp_protocol.c)
-007 000-00:00:02.180 code: 4.33.50 data: 4.33.50 sysdate:
-006 000-00:00:38.260 code: 4.33.50 data: 4.33.50 sysdate: 25/09/2017-11:36:45
-005 000-00:15:01.640 reset__: [13] uaudp_lost_connect (1947 ua_udp_protocol.c)
-004 000-00:00:02.170 code: 4.33.50 data: 4.33.50 sysdate:
-003 000-00:00:35.980 code: 4.33.50 data: 4.33.50 sysdate: 25/09/2017-11:52:02

First try Network Problems, but udp_stats has no error at all.
The bootup look clear, dhcp, tftp.
Switch reboot, same as before.

Has anybody some hints?

thx, cu.

Blackpepper
Member
Posts: 4
Joined: 25 Sep 2017 07:39

Re: IP-Touch 40X8 Dead Air

Post by Blackpepper » 10 Oct 2017 05:49

Bump!

alexeik
Member
Posts: 259
Joined: 26 Apr 2007 10:47
Location: Bad Oeynhausen, germany

Re: IP-Touch 40X8 Dead Air

Post by alexeik » 11 Oct 2017 07:11

i would have a look in the ip tickets, if there is a problem with packets...

mgsox
Member
Posts: 186
Joined: 31 Aug 2007 05:14

Re: IP-Touch 40X8 Dead Air

Post by mgsox » 18 Oct 2017 05:32

hi
check if the configuration of the lanpbxbuild is correct.
try to user g729 as global algorithm.
using ippstat check if the sets are updated (ippstat > 14 >10)
finaly on mgr>users>Tsc IP User>Reset For Update Authorized + YES make it a NO.

Post Reply

Return to “ipTouch (40x8) issues and tricks”