電訊茶室 - Powered by Discuz! Board

標題: ATCOM IP01，我的IP-01突然经常死机，可能在reboot中 [打印本頁]

作者: 角色 時間: 2010-8-2 06:54 標題: ATCOM IP01，我的IP-01突然经常死机，可能在reboot中

本帖最後由角色於 2010-8-25 08:01 編輯

因为ATCOM 经常死机，这个帖子是用来记录最长的run-time是多少？如果你天天关机，当然你的记录就没有意思了。

Members们，把你们的最长的runtime，上载，看看那一台IP-01能够走的最远。

角色

作者: 角色 時間: 2010-8-2 06:55

本帖最後由角色於 2010-8-15 15:09 編輯

最长记录：
23:45:24 up 13 days, 2:33, (86#) 由bubblestar做出
01:57:10 up 12 days, 4:45, （84#）由bubblestar做出
21:45:29 up 11 days, 33 min, （83#）由bubblestar做出
21:54:41 up 10 days, 43 min (69#) 由bubblestar做出
23:07:05 up 9 days （61#）由bubblestar做出
21:12:57 up 8 days, 4 min （55#）由bubblestar做出
13:09:30 up 5 days, 14:40 有电脑超人做出（之后自己关了电源）
06:33:37 up 4 days, 9:57 由ckleea做出 (34#) （之后系统自己reset，restart Asterisk）
08:55:28 up 3 days, 10:26, load average: 0.00, 0.00, 0.00 由电脑超人做出
22:14:56 up 3 days, 1:38, load average: 0.00, 0.00, 0.01 由ckleea做出
21:46:09 up 2 days, 34 min, Load Average: 0.00, 0.00, 0.00 由bubblestar做出

电脑超人
Uptime : 08:55:28 up 3 days, 10:26, load average: 0.00, 0.00, 0.00
Uptime : 13:09:30 up 5 days, 14:40, load average: 0.24, 0.09, 0.06 （41#）
关了电源

角色
Uptime : 06:48:46 up 1 day, 23:39, load average: 0.13, 0.07, 0.02
Uptime : 08:18:59 up 6:41, load average: 0.17, 0.08, 0.06 （昨天停电，所以重来）
Uptime : 07:37:16 up 1 day, 5:59, load average: 0.17, 0.07, 0.04
Uptime : 08:06:17 up 2 days, 6:28, load average: 0.00, 0.11, 0.07
Uptime : 13:40:35 up 4 days, 12:03, load average: 0.60, 0.48, 0.45 （42#）
Uptime : 08:11:37 up 5 days, 6:34, load average: 0.00, 0.03, 0.05 （47#）

bubblestar
Uptime: 20:10:56 up 22:59, Load Average: 0.22, 0.08, 0.06
Uptime: 21:46:09 up 2 days, 34 min, Load Average: 0.00, 0.00, 0.00
Uptime: 00:56:25 up 3:44, Load Average: 0.02, 0.01, 0.00
Uptime: 21:12:28 up 3 days, 0 min, Load Average: 0.01, 0.03, 0.04
Uptime: 21:12:57 up 8 days, 4 min （55#）
Uptime: 23:07:05 up 9 days, 1:55, （61#）
Uptime:21:54:41 up 10 days, 43 min (69#)
Uptime: 21:45:29 up 11 days, 33 min, （83#）
Uptime: 01:57:10 up 12 days, 4:45, （84#）
23:45:24 up 13 days, 2:33, (86#)

ckleea
Uptime : 07:28:32 up 10:52, load average: 0.00, 0.00, 0.00
Uptime : 12:05:58 up 1 day, 15:29, load average: 0.00, 0.11, 0.07
Uptime : 22:14:56 up 3 days, 1:38, load average: 0.00, 0.00, 0.01
Uptime : 06:33:37 up 4 days, 9:57, load average: 0.00, 0.00, 0.00 (34#)
自己reset，那么可能大约是5天左右，asterisk就不能工作了。

lttliang:
Uptime : 12:01:31 up 4 days, 17 min, load average: 0.76, 0.32, 0.11 (40#)

作者: 角色 時間: 2010-8-2 06:55

System Status
Uptime : 06:48:46 up 1 day, 23:39, load average: 0.13, 0.07, 0.02

角色

作者: ckleea 時間: 2010-8-2 07:29

System Status
Uptime : 07:28:32 up 10:52, load average: 0.00, 0.00, 0.00

Reboot yesterday to move to different room

作者: ckleea 時間: 2010-8-2 08:55

有冇遇過以下 errors. 我的 IP01 是從新 factory reset，用DHCP 連接 router，用 standard ports. Firmware 0.3.8

[Aug  1 22:19:09] WARNING[11761] channel.c: Hard hangup called by thread 3111961 on Local/executecommand@asterisk_guitools-6de5,2, while fd is blocked by thread 67608 in procedure ast_waitfor_nandfds!  Expect a failure
[Aug  1 22:19:09] WARNING[11769] channel.c: Hard hangup called by thread 3117083 on Local/executecommand@asterisk_guitools-ab94,2, while fd is blocked by thread 67608 in procedure ast_waitfor_nandfds!  Expect a failure
[Aug  1 22:19:09] WARNING[11767] channel.c: Hard hangup called by thread 3116058 on Local/executecommand@asterisk_guitools-b7d8,2, while fd is blocked by thread 67608 in procedure ast_waitfor_nandfds!  Expect a failure
[Aug  1 22:19:16] WARNING[11810] channel.c: Hard hangup called by thread 3153945 on Local/executecommand@asterisk_guitools-f19f,2, while fd is blocked by thread 67608 in procedure ast_waitfor_nandfds!  Expect a failure
[Aug  1 22:19:44] WARNING[11846] channel.c: Hard hangup called by thread 3188759 on Local/executecommand@asterisk_guitools-8204,2, while fd is blocked by thread 67608 in procedure ast_waitfor_nandfds!  Expect a failure

作者: 角色 時間: 2010-8-2 09:14

有，但是之前是否有就没有留意过。

角色

作者: ckleea 時間: 2010-8-2 09:27

我估software 都係唔係好好！

作者: bubblestar 時間: 2010-8-2 12:55

我的IP01是連上Netgear Swtich，再駁Router，Asterisk Logs 出現以下情況。原因不明。

[Aug  2 00:46:10] WARNING[13388] channel.c: Hard hangup called by thread 58392 on Local/executecommand@asterisk_guitools-838b,2, while fd is blocked by thread 59417 in procedure ast_waitfor_nandfds!  Expect a failure
[Aug  2 00:46:11] WARNING[13397] channel.c: Hard hangup called by thread 64539 on Local/executecommand@asterisk_guitools-c590,2, while fd is blocked by thread 59417 in procedure ast_waitfor_nandfds!  Expect a failure
[Aug  2 00:46:11] WARNING[13394] channel.c: Hard hangup called by thread 62488 on Local/executecommand@asterisk_guitools-ff8d,2, while fd is blocked by thread 59417 in procedure ast_waitfor_nandfds!  Expect a failure
[Aug  2 00:46:16] WARNING[13464] channel.c: Hard hangup called by thread 128024 on Local/executecommand@asterisk_guitools-e269,2, while fd is blocked by thread 59417 in procedure ast_waitfor_nandfds!  Expect a failure
[Aug  2 00:46:26] WARNING[13490] channel.c: Hard hangup called by thread 147479 on Local/executecommand@asterisk_guitools-36d6,2, while fd is blocked by thread 59417 in procedure ast_waitfor_nandfds!  Expect a failure
[Aug  2 00:46:41] WARNING[13516] channel.c: Hard hangup called by thread 163864 on Local/executecommand@asterisk_guitools-03e7,2, while fd is blocked by thread 59417 in procedure ast_waitfor_nandfds!  Expect a failure
[Aug  2 00:46:42] WARNING[13520] channel.c: Hard hangup called by thread 165912 on Local/executecommand@asterisk_guitools-3dff,2, while fd is blocked by thread 59417 in procedure ast_waitfor_nandfds!  Expect a failure
[Aug  2 00:46:42] WARNING[13525] channel.c: Hard hangup called by thread 168984 on Local/executecommand@asterisk_guitools-916c,2, while fd is blocked by thread 59417 in procedure ast_waitfor_nandfds!  Expect a failure
[Aug  2 00:47:00] WARNING[13537] channel.c: Hard hangup called by thread 179224 on Local/executecommand@asterisk_guitools-384c,2, while fd is blocked by thread 59417 in procedure ast_waitfor_nandfds!  Expect a failure
[Aug  2 00:51:23] WARNING[13666] channel.c: Hard hangup called by thread 238616 on Local/executecommand@asterisk_guitools-73e1,2, while fd is blocked by thread 59417 in procedure ast_waitfor_nandfds!  Expect a failure
[Aug  2 00:51:28] WARNING[13677] channel.c: Hard hangup called by thread 242712 on Local/executecommand@asterisk_guitools-6b48,2, while fd is blocked by thread 59417 in procedure ast_waitfor_nandfds!  Expect a failure
[Aug  2 00:51:29] WARNING[13682] channel.c: Hard hangup called by thread 245784 on Local/executecommand@asterisk_guitools-4c4a,2, while fd is blocked by thread 59417 in procedure ast_waitfor_nandfds!  Expect a failure
[Aug  2 00:51:42] WARNING[13689] channel.c: Hard hangup called by thread 250904 on Local/executecommand@asterisk_guitools-db98,2, while fd is blocked by thread 59417 in procedure ast_waitfor_nandfds!  Expect a failure
[Aug  2 00:51:43] WARNING[13695] channel.c: Hard hangup called by thread 255000 on Local/executecommand@asterisk_guitools-5c84,2, while fd is blocked by thread 59417 in procedure ast_waitfor_nandfds!  Expect a failure
[Aug  2 00:51:50] WARNING[13701] channel.c: Hard hangup called by thread 259096 on Local/executecommand@asterisk_guitools-a7cd,2, while fd is blocked by thread 59417 in procedure ast_waitfor_nandfds!  Expect a failure
[Aug  2 00:51:52] WARNING[13706] channel.c: Hard hangup called by thread 262168 on Local/executecommand@asterisk_guitools-1036,2, while fd is blocked by thread 59417 in procedure ast_waitfor_nandfds!  Expect a failure
[Aug  2 00:51:57] WARNING[13712] channel.c: Hard hangup called by thread 266264 on Local/executecommand@asterisk_guitools-5f99,2, while fd is blocked by thread 59417 in procedure ast_waitfor_nandfds!  Expect a failure
[Aug  2 00:51:59] WARNING[13718] channel.c: Hard hangup called by thread 270360 on Local/executecommand@asterisk_guitools-4625,2, while fd is blocked by thread 59417 in procedure ast_waitfor_nandfds!  Expect a failure
[Aug  2 00:52:07] WARNING[13727] channel.c: Hard hangup called by thread 274456 on Local/executecommand@asterisk_guitools-73ef,2, while fd is blocked by thread 59417 in procedure ast_waitfor_nandfds!  Expect a failure
[Aug  2 00:52:09] WARNING[13733] channel.c: Hard hangup called by thread 278552 on Local/executecommand@asterisk_guitools-48b7,2, while fd is blocked by thread 59417 in procedure ast_waitfor_nandfds!  Expect a failure
[Aug  2 00:52:17] WARNING[13739] channel.c: Hard hangup called by thread 282648 on Local/executecommand@asterisk_guitools-3013,2, while fd is blocked by thread 59417 in procedure ast_waitfor_nandfds!  Expect a failure

作者: bubblestar 時間: 2010-8-2 12:57

本帖最後由 bubblestar 於 2010-8-2 12:58 編輯

System Status

Uptime: 00:56:25 up 3:44,
Load Average: 0.02, 0.01, 0.00

作者: 角色 時間: 2010-8-2 13:06

真的不知道！是否新的firmware是遮这样，还是旧的firmware也有同样的问题呢？

角色

作者: ckleea 時間: 2010-8-2 13:43

回復 8# bubblestar

和我的差唔多，我都用 Netgear.

作者: bubblestar 時間: 2010-8-3 08:17

接近了一天，IP01仍在運作。

Uptime: 20:10:56 up 22:59,
Load Average: 0.22, 0.08, 0.06

而記憶體已用及未用的數值亦非常穩定，沒有多大變化。

Memory Usage:
total used free shared buffers
Mem: 45704 37072 8632 0 768

作者: 角色 時間: 2010-8-3 08:21

我的memory usage：

Memory Usage:

total used free shared buffers
Mem: 45704 39532 6172 0 760

角色

作者: ckleea 時間: 2010-8-3 12:06

System Status
Uptime : 12:05:58 up 1 day, 15:29, load average: 0.00, 0.11, 0.07

Memory Usage:

total used free shared buffers
Mem: 45704 33372 12332 0 712

作者: lttliang 時間: 2010-8-3 14:35

Memory Usage:
total used free shared buffers
Mem: 45704 37360 8344 0 756

內存使用量好高有冇咩辦法解決?

作者: ckleea 時間: 2010-8-3 14:38

我發覺我的 free memory 比你地多，是否我最近 flash 完剛剛裝有關？

作者: 角色 時間: 2010-8-3 15:37

不知道为什么？可能我的backup比较多。

角色

作者: 角色 時間: 2010-8-4 07:38

本帖最後由角色於 2010-8-4 07:43 編輯

Uptime : 07:37:16 up 1 day, 5:59, load average: 0.17, 0.07, 0.04

Memory Usage:
total used free shared buffers
Mem: 45704 41236 4468 0 784

複製代碼

After removing the /perisistent/var/log/asterisk/messages, the memory usage:

Memory Usage:
total used free shared buffers
Mem: 45704 40180 5524 0 784

複製代碼

作者: ckleea 時間: 2010-8-4 08:39

你說得對

作者: bubblestar 時間: 2010-8-4 09:46

角色兄的IP01又再死機? 點解你的記錄仲係得一天多少少呢?

作者: bubblestar 時間: 2010-8-4 09:47

本帖最後由 bubblestar 於 2010-8-4 09:48 編輯

Uptime:
21:46:09 up 2 days, 34 min,
Load Average: 0.00, 0.00, 0.00

複製代碼

Memory Usage:
total used free shared buffers
Mem: 45704 37128 8576 0 776

複製代碼

作者: 321 時間: 2010-8-4 22:14

最長才兩天?呢個結果好得人驚.
唔通要有人24小時準備幫佢reboot?

作者: ckleea 時間: 2010-8-4 22:15

Not really. 3 days already

System Status
Uptime : 22:14:56 up 3 days, 1:38, load average: 0.00, 0.00, 0.01

作者: ckleea 時間: 2010-8-4 22:43

This is taken from another asterisk (dd-wrt router with asterisk plugin)

System Status
Uptime : 22:42:46 up 9 days, 15:50, 0 users, load average: 0.19, 0.05, 0.01

作者: 角色 時間: 2010-8-5 08:06

Mine is only 2 days +

Uptime : 08:06:17 up 2 days, 6:28, load average: 0.00, 0.11, 0.07

作者: 電腦超人 時間: 2010-8-5 08:56

現在行了3 days+...
Uptime : 08:55:28 up 3 days, 10:26, load average: 0.00, 0.00, 0.00

作者: bubblestar 時間: 2010-8-5 09:13

我也行了 3 days+

Uptime: 21:12:28 up 3 days, 0 min,
Load Average: 0.01, 0.03, 0.04

Memory Usage:
total used free shared buffers
Mem: 45704 37164 8540 0 776

作者: 角色 時間: 2010-8-5 09:20

看来大家的IP-01都能度过三天，看看谁的IP-01能活的最久。

角色

作者: bubblestar 時間: 2010-8-5 09:43

回復 24# ckleea

Router per se is designed for 24x7 usage purpose. I think it won't die easily unless external power failure or its own lifespan ends.

作者: lttliang 時間: 2010-8-5 11:18

試過一次4日,後來ip01的時間唔準 ,改左就重啟過依家好似未超過

作者: 角色 時間: 2010-8-5 17:47

回復 30# lttliang

那么你的IP-01最长能走多远呢？

角色

作者: bubblestar 時間: 2010-8-5 18:35

IP01仍然運作，但跟角色兄的SERVER連不上，Unreachable。

作者: 電腦超人 時間: 2010-8-6 00:19

4天了~

Uptime : 00:19:30 up 4 days, 1:50, load average: 0.00, 0.00, 0.00

作者: ckleea 時間: 2010-8-6 06:34

Same 4 days, no attack.

System Status
Uptime : 06:33:37 up 4 days, 9:57, load average: 0.00, 0.00, 0.00

作者: bubblestar 時間: 2010-8-6 10:19

四天以上了

Uptime: 22:17:28 up 4 days, 1:05,
Load Average: 0.00, 0.00, 0.00

作者: ckleea 時間: 2010-8-6 12:18

我的IP01 must be died, can't access

作者: ckleea 時間: 2010-8-6 14:17

Only web access temporarily not accessible. still working

System Status
Uptime : 14:16:23 up 4 days, 17:40, load average: 0.02, 0.01, 0.01

作者: 角色 時間: 2010-8-6 14:55

Are you remotely (via Internet) access your ip-01?

YH

作者: ckleea 時間: 2010-8-6 15:15

Yes, normally it should be ok. Other asterisks work except the IP01 when I felt it was dead

作者: lttliang 時間: 2010-8-7 12:02

Uptime : 12:01:31 up 4 days, 17 min, load average: 0.76, 0.32, 0.11

作者: 電腦超人 時間: 2010-8-7 13:12

5天半了~

Uptime : 13:09:30 up 5 days, 14:40, load average: 0.24, 0.09, 0.06

作者: 角色 時間: 2010-8-7 13:41

我的是

Uptime : 13:40:35 up 4 days, 12:03, load average: 0.60, 0.48, 0.45

角色

作者: ckleea 時間: 2010-8-7 20:08

I have a reset for unknown reason

System Status
Uptime : 20:07:55 up 2:49, load average: 0.00, 0.07, 0.06

作者: 電腦超人 時間: 2010-8-7 22:16

殘念啊~(日語"可惜")
剛剛因為要關電制弄一些東東...所以過不了6天...

大概"差不多"6天吧...

作者: bubblestar 時間: 2010-8-8 01:04

自己關機, 並不算是死機吧.

作者: 角色 時間: 2010-8-8 08:12

如果自己关机，当然不能算在IP-01 firmware本身。

我的也能走5天了。
Uptime : 08:11:37 up 5 days, 6:34, load average: 0.00, 0.03, 0.05

角色

作者: bubblestar 時間: 2010-8-8 13:46

本帖最後由 bubblestar 於 2010-8-8 13:48 編輯

我的已是第六天零四個半鐘了，看看能否打破角色所說不能超過七天的記錄了。明天就有結果。

Uptime: 01:43:34 up 6 days, 4:31,
Load Average: 0.29, 0.11, 0.03

作者: 角色 時間: 2010-8-8 13:49

虽然系统没有死，但是我的ET263 Trunk就会死掉，我要做一次sip reload才能把问题解决好。

所以每天reset一次最好。

角色

作者: bubblestar 時間: 2010-8-8 14:40

其實會不會是Provider本身的問題而不是IP01的問題呢? 正如 IPTEL 早前經常死掉一樣，那源頭並不是自己SERVER的問題啊。最主要是知道根源而作結論較好一些吧!

我本身沒有使用ET263，所以不便下評論，但我有註冊 Sipgate，Gizmo5 和 IPKall 等等都沒有斷過Trunk的連繋。

如果想天天都能很Robust 地運作下去，那麼角色兄的一天一次RESET 動作也不失為一個好辦法，當然自動化操作是少不了的。

作者: 角色 時間: 2010-8-8 14:51

你说起这个问题，我也证实过，在香港的ET263完全没有问题。所以我在深圳的IP-01做了一次sip reload，然后就可以马上能打出大陆电话。我香港的NAS的Asterisk Server，开了很久，差不多一年多，除了计划停电维修外，其他什么问题也没有，而且稳定性是非常高。

而IP-01，都没有说过它可以行一个月，每次都是大约1周后就出现各种问题。

等我IP-01死掉后我会加入每一个晚上reboot系统一次，那么每一次它都可以活的超过几天，那么天天reboot后，理论它死亡的机率就非常低。

角色

作者: 角色 時間: 2010-8-8 22:03

我的IP-01，因为某些原因需要reboot，所以我的IP-01也要重来。

角色

作者: 電腦超人 時間: 2010-8-9 02:06

我的IP01...行了不夠一天...
Call Detail Records好像有點問題...不能顯示...

Viewing 1-9 of 9
(most recent first)
Account Code
1 </body></html>
2 <address>Asterisk Server</address>
3 <hr />
4 <p>Internal Server Error</p>
5 <h1>Internal Error</h1>
6 </head><body>
7 <title>500 Internal Error</title>
8 <html><head>
9 <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
Manager CDR Files

複製代碼

打算reboot一次...

作者: lttliang 時間: 2010-8-10 08:59

Uptime : 08:58:55 up 6 days, 21:15, load average: 0.24, 0.04, 0.01

作者: lttliang 時間: 2010-8-10 09:01

行走6日不知是否有一日在CLI 里做左sip reload的原因,如果是的話,是否以後要佢每一分鐘sip reload一次就不會死呢?

作者: bubblestar 時間: 2010-8-10 09:20

本帖最後由 bubblestar 於 2010-8-10 09:25 編輯

行咗 8 天，仍非常之壯健。

不過發現Memory used 由 Day 1 的 37072 開始緩升至現在的 38392，稍後看看會不會自動回落。

Uptime: 21:12:57 up 8 days, 4 min,
Load Average: 0.06, 0.07, 0.07

Memory Usage:
total used free shared buffers
Mem: 45704 38392 7312 0 804

作者: bubblestar 時間: 2010-8-10 09:24

都係做一個Screen Capture，以免被說是吹水，留一記錄也好

圖片附件: 2010-08-10_092244.png (2010-8-10 09:24, 14.79 KB) / 下載次數 941
http://telecom-cafe.com/forum/attachment.php?aid=139&k=d8f4d6a69d4f7d488871b858932179d6&t=1739733326&sid=Eq0I7Q

作者: 角色 時間: 2010-8-10 09:55

厉害！劲！

角色

作者: 電腦超人 時間: 2010-8-10 22:59

我的IP01最近一次好像連2天也撐不到...

剛剛角色兄跟我說未能login...我在SSH一看之下連基本的service也沒了...

所以reboot了一次...

作者: 角色 時間: 2010-8-10 23:19

看来你的IP01，如果有问题，不是restart Asterisk，而是reboot。还有每个晚上都reboot一次。

角色

作者: ckleea 時間: 2010-8-10 23:30

Now about 3 days

System Status
Uptime : 23:12:29 up 3 days, 5:54, load average: 0.00, 0.02, 0.03

作者: bubblestar 時間: 2010-8-11 11:13

九天了。

Uptime: 23:07:05 up 9 days, 1:55,
Load Average: 0.00, 0.08, 0.06

不過memory used 的讀數，真的會按日增加，大概今早比昨天早上多了1272。 Free Memory只剩下若6000左右，看看會不會捱到多 6 天便死掉，如果係的話， 15天便是極限了。

Memory Usage:
total used free shared buffers
Mem: 45704 39664 6040 0 824

作者: 角色 時間: 2010-8-11 11:26

劲！

角色

作者: lttliang 時間: 2010-8-11 18:01

回復 61# bubblestar

如果是這樣 ,是否可以做到唔記錄log,从而唔比它用多内存?

作者: 角色 時間: 2010-8-11 18:02

现在我都不加log的。

角色

作者: bubblestar 時間: 2010-8-11 18:12

在哪裡取消呢?

作者: 角色 時間: 2010-8-11 22:15

As suggested by alang, you may modify the /etc/asterisk/logger.conf.

YH

作者: lttliang 時間: 2010-8-11 23:28

回復 66# 角色

可否列出來一下,修改的方法?

作者: ckleea 時間: 2010-8-12 06:30

My device has more problems than usual. Somehow, I can't connect by certain sip accounts. Under investigation.

作者: bubblestar 時間: 2010-8-12 09:57

本帖最後由 bubblestar 於 2010-8-12 10:01 編輯

踏入第10天了，

Uptime: 21:54:41 up 10 days, 43 min,
Load Average: 0.00, 0.00, 0.00

Memory Usage:
total used free shared buffers
Mem: 45704 39684 6020 0 824

在/etc/asterisk/logger/conf disabled 咗少少之後，memory用量沒有最上升了。看多幾日情況會否可以維持下去。又或這等死機後，重新看看用了logger disable 之後可否長時間把MEMORY維持低水平。

作者: 角色 時間: 2010-8-12 10:07

不知道是否我们的IP-01接了很多trunks，和大约10个 users的关系，所以有的时候导致系统不稳定。

角色

作者: bubblestar 時間: 2010-8-12 10:07

Knowing that you have 4 fixed IP from your ISP, have you clearly separated all sip and rtp ports among all your devices? Although it will not be a big problem for independent IP, I still doubt the ISP would really offer such 咁荀的 serivce to you without extra charges. ha ha ha.

作者: ckleea 時間: 2010-8-12 10:37

MY router has rules to deal with individual ports WAN and LAN. I have configured to allow in and out for different services based on different IPs (of course use Cname for simplificity)

However, it would be nicer to have Draytek and some other Taiwan brand routers that allow open port functions for a group of port and address.

The IP01 and Centos server work. My existing problems are
1. some user extensions are logged in and works but not other in IP01,
2. as said, I have problems now with HKBN 2B dial in. Look like the SIP communications are ok but somehow it drops. 角色 has helped me to figure out the dial out problem.

作者: bubblestar 時間: 2010-8-12 10:50

回復 70# 角色

可能你說的也有道理。現在我經常接著5條TRUNKS (有時會8條) 及 7 個 USERS。

沒有你地咁多吧

作者: bubblestar 時間: 2010-8-12 10:53

回復 72# ckleea

Yes, you've got the right person. YHFung has become the Master in the area of VoIP now.

作者: lttliang 時間: 2010-8-12 12:57

我的ip01又死左，我系router里面睇唔到ip01的IP地址，平時如果ip01如果冇死的話，IP地址會顯示在router的靜態IP地址個列

作者: lttliang 時間: 2010-8-12 13:00

唔可能吧 5個trunk 3個user都成日死

作者: ckleea 時間: 2010-8-12 15:33

補充，IPs are ok to use. I pay off at a higher price than the present HK$99 per months. The subscription itself has included wireless ethernet modem which can turn on.
For different asterisks and IP01s, I try to dial out without any problem. At present the usage is low. IP01 if ok, will be move to other country for the purpose of "IDD"

角色兄 has been very helpful and more importantly, it is very difficult to have a person like him that is willing to share his experience.
I just try to share my experience as well.

We keep learning. We are somewhat 發燒友

作者: 角色 時間: 2010-8-12 18:05

We may mutually study and ed benefited each other. Since I learned VoIP technology from other members in HKEPC, now this is my turn to convery my VoIP knowledage to other junior members.

May be we are VoIP-aholic.

YH

作者: ckleea 時間: 2010-8-12 23:33

We learn and share to keep VOIP running well under our limited resources. Best of them are free software, inexpensive hardware, relative inexpensive VOIP service. Outcome is that we connect one another to make our network powerful.

作者: bubblestar 時間: 2010-8-13 00:15

Just as the concept of Internet. It links all small networks around the world to form an enormous network with knowledges that benefits mankinid . The same idea may apply to VoIP.

作者: 角色 時間: 2010-8-13 08:54

For ordinary text or image messages exchange, it should be okay. However for VoIP messages, it requires the time from the sender to the receiver to be small, otherwise it is meaningless to do so. Also VoIP messages may be blocked by some means in some countries. As a result, we may have to rely on the VPN technology, for instance VoIP over (IPSec) VPN tunnel.

YH

作者: ckleea 時間: 2010-8-13 08:58

How about the creation of VPN among members for co-operation? I understand there may be a lot of issues to resolve but sound interesting if we are able to have several asterisks in different countries.

BTW, we are slightly out of topic from this thread.

作者: bubblestar 時間: 2010-8-13 09:48

踏入了第11天。

Uptime: 21:45:29 up 11 days, 33 min,
Load Average: 0.00, 0.00, 0.00

作者: bubblestar 時間: 2010-8-14 14:02

十二天了，看能否可以去到兩星期吧。應該可以啩，因為自從disabled 了 /etc/asterisk/logger.conf 之後，memory used 明顯地穩定了下來，一直三天都維持在39700水平。

Uptime: 01:57:10 up 12 days, 4:45,
Load Average: 0.00, 0.00, 0.00

作者: lttliang 時間: 2010-8-14 19:37

我改左/etc/asterisk/logger.conf 之後  一直差不多這樣  使用量冇升太多，睇一下可以堅持幾耐先
Memory Usage:
            total       used       free    shared    buffers
  Mem:       45704       32876       12828          0       148

作者: bubblestar 時間: 2010-8-15 11:48

13 天

Uptime: 23:45:24 up 13 days, 2:33,
Load Average: 0.00, 0.00, 0.00

作者: bubblestar 時間: 2010-8-15 13:25

本帖最後由 bubblestar 於 2010-8-15 13:27 編輯

意外新發現

什麼也沒有做，但剛才只在PUTTY進入了

root :~> asterisk -grcvvvvvvvvvvv

IP01*CLI>

跟著EXIT 返出去，幾分鐘後，再到GUI 看一看，發覺MEMORY USED 大幅減少，FREE MEMORY 則大幅回升。

Memory Usage: (因為樓下數字跟SCREEN CAPTURE有時間先後，所以數字有小小出入)
total used free shared buffers
Mem: 45704 29284 16420 0 116

最近三、四天， free momory原本得返6000都唔夠。有無人知道原因呢??

圖片附件: 2010-08-15_132356.png (2010-8-15 13:24, 87.38 KB) / 下載次數 1201
http://telecom-cafe.com/forum/attachment.php?aid=150&k=339442399a180fc61021110908e15ff8&t=1739733326&sid=Eq0I7Q

作者: bubblestar 時間: 2010-8-15 13:42

另外，有沒有人知道

root :~> asterisk -grcvvvvvvvvvvv

root :~> asterisk -grvvvvvvvvvvv

兩句有什麼分別，第一句多了一個 c 宇，我也不求甚解，因為IP01 MANUAL曾說過可用此句，所以照跟，也忘了它是什麼意思了。

作者: 角色 時間: 2010-8-15 14:22

You may got the answer from the manual of asterisk as follows:

http://www.voip-info.org/wiki/view/Asterisk+man+page

where c denotes for console mode.

YH

作者: bubblestar 時間: 2010-8-16 11:02

本帖最後由 bubblestar 於 2010-8-16 11:08 編輯

超越兩星期 (14天)!!

終於達到 2 星期了，今早發現它爽了很多

。Free Momory 再由昨天的16000水平，增加至今早超過18000多的數值。而Memory used 則進一步下降至27576 (昨天是29300)。

初步結論，Memory used 跌至6000之下左右，會自動回升。或這要再看多一個ROUND 才可以下總結。

System Uptime

Memory Usage

圖片附件: 2010-08-16_105325.png (2010-8-16 11:01, 17.34 KB) / 下載次數 1124
http://telecom-cafe.com/forum/attachment.php?aid=151&k=04fc8b285c3537ead34dcf53d56bc40a&t=1739733326&sid=Eq0I7Q

圖片附件: 2010-08-16_105243.png (2010-8-16 11:03, 27.04 KB) / 下載次數 1170
http://telecom-cafe.com/forum/attachment.php?aid=152&k=54955c163a665f1078e66d8020bb6dbe&t=1739733326&sid=Eq0I7Q

作者: 角色 時間: 2010-8-16 11:32

你那么高，可能与你的TTS有关。

角色

作者: 角色 時間: 2010-8-16 11:35

应该这样看，如果一直没有error messages出来，理应系统可以走的很就，但是遇到一些连接不通，那么log messages就出现很多，那么导致系统去写那些error message如log file，慢慢file越来越大，导致系统出现问题。所以要经常留意error messages，能解决就要解决，不能就把它删掉。

角色

作者: bubblestar 時間: 2010-8-16 12:50

本帖最後由 bubblestar 於 2010-8-16 12:54 編輯

造出14天記錄後約兩小時，因為在GUI 版面需要修改一個接駁選項，當選好後要在右上角按 Apply Changes 的時候，便無法再進入 GUI 版面了，它彈出了一句 HTTP 404 的錯誤碼，表示WEB PAGE不能進入或WEB PAGE 位置可能被更改位置了。情況好像跟早前 ckleea 兄所遇到的一樣。

從 putty / WinSCP 進入均沒有問題，而且 IP01 Server 仍然運作良好的。只是進不了GUI 版面罷了。

這種情況算真死定假死呢?? 當時我是使用Windows 7 的。有沒有 Win XP 用家有類似問題呢? 不知是 WIN OS 問題定係 IP01 問題，但總的來說它仍能運作，等於腦幹/心臟仍工作，我認為不能宣告它死亡的，只介面溝通出了岔子。馬上拔喉的話，好似早咗D。。。。。。

作者: 角色 時間: 2010-8-16 14:04

可能再等一会，GUI有可以上来用。

角色

作者: yiucsw 時間: 2010-8-19 15:17

懒人的笨方法。
我的IP01几乎每三天当机一次。
现在加上用外置的Timer，每天晚上重启一次。将Logger的notice删掉。系统好像反应快多了，也没有当机。有没有人用同一样的方法解决不稳定问题？因我想改更长时间再重启两/三天一次？

作者: 角色 時間: 2010-8-19 19:21

现在我都不等ATCOM新的firmware，也不寄望他们能做什么。因为每次一reboot都可以活几天，那么天天自动reboot就可以。现在我每天凌晨4点就reboot一次，还有在当天，如果系统发现asterisk process不见，系统又会reboot。这两个tasks，我估计系统失灵的机会会减到很低。

角色

作者: ckleea 時間: 2010-8-19 19:36

If you go to the original ATCOM firmware company VOIPtel.no, you can see the version is just 3.4. ATCOM has upgraded to 3.8

作者: ckleea 時間: 2010-8-20 15:05

My IP01 after using switchfin firmware has loading always at around 3.0 when idle
Uptime : 13:14:51 up 2 days, 15:44, load average: 3.30, 3.15, 3.04

作者: 角色 時間: 2010-8-20 15:13

If so, it seems that there are some intensive processes running in the background. Is there any processes required higher computing time?

YH

作者: ckleea 時間: 2010-8-20 17:27

WHat is your percentage of CPU usage? I am at 50%

歡迎光臨電訊茶室 (http://telecom-cafe.com/forum/)