Hi brothers,
Every days around nine o´clock, some IPTouch reinit. In defence command view "uaudp_release _message". I have change the parameters Quality of service without results.
Can someone helpme?
Thanks in advance.
UAUDP RELEASE MESSAGE
Re: UAUDP RELEASE MESSAGE
Take a look on phone facilities category. It contains allowed time for binaries update, change to for ex.: from 2AM till 5AM.
Phone tries to update binaries but something wrong . Next morning again tries.
Another case maybe somebody overload network each morning.
Phone tries to update binaries but something wrong . Next morning again tries.
Another case maybe somebody overload network each morning.
Re: UAUDP RELEASE MESSAGE
Looks quite reasonable.OXE_4400 wrote:Another case maybe somebody overload network each morning.
It would be more interesting to know from where "uaudp_release _message" originated - from IPTouch or CS?dryhouse wrote: In defence command view "uaudp_release _message".
If it looks like a duck, swims like a duck, and quacks like a duck, then it probably is a duck.
-
dryhouse
Re: UAUDP RELEASE MESSAGE
I don´t know where it is from. I have this defence....
023 000-00:00:03.000 code: 3.91.40 data: 3.91.40 sysdate:
-022 000-00:01:21.620 code: 3.91.40 data: 3.91.40 sysdate: 21/04/2011-21:12:57
-021 000-08:34:13.180 reset__: [14] uaudp_release_message (1506 manager.c)
-020 000-00:00:02.980 code: 3.91.40 data: 3.91.40 sysdate:
-019 000-00:01:21.460 code: 3.91.40 data: 3.91.40 sysdate: 22/04/2011-05:47:16
-018 000-15:25:23.960 reset__: [14] uaudp_release_message (1506 manager.c)
-017 000-00:00:03.080 code: 3.91.40 data: 3.91.40 sysdate:
-016 000-00:01:21.720 code: 3.91.40 data: 3.91.40 sysdate: 22/04/2011-21:12:45
-015 001-23:59:27.030 reset__: [14] uaudp_release_message (1506 manager.c)
-014 000-00:00:03.000 code: 3.91.40 data: 3.91.40 sysdate:
-013 000-00:01:21.400 code: 3.91.40 data: 3.91.40 sysdate: 24/04/2011-21:12:11
-012 000-01:52:52.680 reset__: [14] uaudp_release_message (1506 manager.c)
-011 000-00:00:02.890 code: 3.91.40 data: 3.91.40 sysdate:
-010 000-00:01:31.120 code: 3.91.40 data: 3.91.40 sysdate: 24/04/2011-23:05:20
-009 000-00:06:32.440 reset__: [14] uaudp_release_message (1506 manager.c)
-008 000-00:00:02.870 code: 3.91.40 data: 3.91.40 sysdate:
-007 000-00:01:21.300 code: 3.91.40 data: 3.91.40 sysdate: 24/04/2011-23:11:51
-006 000-00:07:02.420 reset__: [14] uaudp_release_message (1506 manager.c)
-005 000-00:00:02.980 code: 3.91.40 data: 3.91.40 sysdate:
-004 000-00:01:21.660 code: 3.91.40 data: 3.91.40 sysdate: 24/04/2011-23:19:01
-003 000-00:07:22.420 reset__: [14] uaudp_release_message (1506 manager.c)
-002 000-00:00:02.810 code: 3.91.40 data: 3.91.40 sysdate:
-001 000-00:01:21.300 code: 3.91.40 data: 3.91.40 sysdate: 24/04/2011-23:26:31
>000 000-12:41:32.950 telnet from 172.26.83.10 accepted
defence OK
Thanks.
023 000-00:00:03.000 code: 3.91.40 data: 3.91.40 sysdate:
-022 000-00:01:21.620 code: 3.91.40 data: 3.91.40 sysdate: 21/04/2011-21:12:57
-021 000-08:34:13.180 reset__: [14] uaudp_release_message (1506 manager.c)
-020 000-00:00:02.980 code: 3.91.40 data: 3.91.40 sysdate:
-019 000-00:01:21.460 code: 3.91.40 data: 3.91.40 sysdate: 22/04/2011-05:47:16
-018 000-15:25:23.960 reset__: [14] uaudp_release_message (1506 manager.c)
-017 000-00:00:03.080 code: 3.91.40 data: 3.91.40 sysdate:
-016 000-00:01:21.720 code: 3.91.40 data: 3.91.40 sysdate: 22/04/2011-21:12:45
-015 001-23:59:27.030 reset__: [14] uaudp_release_message (1506 manager.c)
-014 000-00:00:03.000 code: 3.91.40 data: 3.91.40 sysdate:
-013 000-00:01:21.400 code: 3.91.40 data: 3.91.40 sysdate: 24/04/2011-21:12:11
-012 000-01:52:52.680 reset__: [14] uaudp_release_message (1506 manager.c)
-011 000-00:00:02.890 code: 3.91.40 data: 3.91.40 sysdate:
-010 000-00:01:31.120 code: 3.91.40 data: 3.91.40 sysdate: 24/04/2011-23:05:20
-009 000-00:06:32.440 reset__: [14] uaudp_release_message (1506 manager.c)
-008 000-00:00:02.870 code: 3.91.40 data: 3.91.40 sysdate:
-007 000-00:01:21.300 code: 3.91.40 data: 3.91.40 sysdate: 24/04/2011-23:11:51
-006 000-00:07:02.420 reset__: [14] uaudp_release_message (1506 manager.c)
-005 000-00:00:02.980 code: 3.91.40 data: 3.91.40 sysdate:
-004 000-00:01:21.660 code: 3.91.40 data: 3.91.40 sysdate: 24/04/2011-23:19:01
-003 000-00:07:22.420 reset__: [14] uaudp_release_message (1506 manager.c)
-002 000-00:00:02.810 code: 3.91.40 data: 3.91.40 sysdate:
-001 000-00:01:21.300 code: 3.91.40 data: 3.91.40 sysdate: 24/04/2011-23:26:31
>000 000-12:41:32.950 telnet from 172.26.83.10 accepted
defence OK
Thanks.
Re: UAUDP RELEASE MESSAGE
Any errors on OXE? Looks like UA/UDP connection lost/released but it is not clear for which reason.dryhouse wrote:I don´t know where it is from. I have this defence....
-021 000-08:34:13.180 reset__: [14] uaudp_release_message (1506 manager.c)
-018 000-15:25:23.960 reset__: [14] uaudp_release_message (1506 manager.c)
-015 001-23:59:27.030 reset__: [14] uaudp_release_message (1506 manager.c)
-012 000-01:52:52.680 reset__: [14] uaudp_release_message (1506 manager.c)
-009 000-00:06:32.440 reset__: [14] uaudp_release_message (1506 manager.c)
-006 000-00:07:02.420 reset__: [14] uaudp_release_message (1506 manager.c)
-003 000-00:07:22.420 reset__: [14] uaudp_release_message (1506 manager.c)
If it looks like a duck, swims like a duck, and quacks like a duck, then it probably is a duck.
-
dryhouse
Re: UAUDP RELEASE MESSAGE
24/04/11 21:12:03 000030M|001/00/0/020|=5:2053=Terminal 20 in service
24/04/11 23:05:03 000030M|001/00/0/020|=5:2053=Terminal 20 in service
24/04/11 23:11:43 000030M|001/00/0/020|=5:2053=Terminal 20 in service
24/04/11 23:18:53 000030M|001/00/0/020|=5:2053=Terminal 20 in service
24/04/11 23:26:23 000030M|001/00/0/020|=5:2053=Terminal 20 in service
No more errors in OXE
24/04/11 23:05:03 000030M|001/00/0/020|=5:2053=Terminal 20 in service
24/04/11 23:11:43 000030M|001/00/0/020|=5:2053=Terminal 20 in service
24/04/11 23:18:53 000030M|001/00/0/020|=5:2053=Terminal 20 in service
24/04/11 23:26:23 000030M|001/00/0/020|=5:2053=Terminal 20 in service
No more errors in OXE
Re: UAUDP RELEASE MESSAGE
Weird...
Try to get some info running "syslog" traces.
Try to get some info running "syslog" traces.
If it looks like a duck, swims like a duck, and quacks like a duck, then it probably is a duck.
