Switchfin firmware on ATCOM IP01 - VoIP 研究室 - 電訊茶室

Rank: 1

31^# 跳轉到 »

發表於 2011-1-2 22:36 | 顯示全部帖子

回復 211# 亞星

試下 power off -> unplug -> re-plug -> power on，最好連LAN線也拔掉，隔五分鐘再試試。我試過Work。

Rowetel 都好似有叫人咁做。

Rank: 1

32^#

發表於 2011-1-13 11:08 | 顯示全部帖子

回復 221# Qnewbie

I'm also glad to learn that Qnewbie has a good start for switching to Switchfin. Agree with ckleea C-Hing that SVN-437 is more stable so far.

Curious to know about the mentioning of "simultaneouly switch-on". What is all about?

Rank: 1

33^#

發表於 2011-1-13 11:12 | 顯示全部帖子

回復 222# 亞星

因為每個人在自己的網絡設備及步署都不盡相同。只要你的IP01本身沒有問題，相信只是卡在某些地方罷了。不用心急，既然現在多了朋友使用Switchfin on IP01，合眾人之力，一定可以解決到的。

BTW，我也是用Draytek 2930N 的Router，一直沒有連接上的問題。

Rank: 1

34^#

發表於 2011-1-13 17:06 | 顯示全部帖子

回復 227# 亞星

建議你把SPA3000先带回家，在同一LAN之內試打，如果通，即表示所有機子都沒有問題。但另一方面，也即表示你在網外，聲音的RTP Packets 出唔到街也入唔到黎，所以無聲。呢D情況我地很多人都試過的，包括我在內。的確是跟Router NAT 設定的事。

Rank: 1

35^#

發表於 2011-1-13 23:17 | 顯示全部帖子

回復 232# 亞星

SPA3000 做了 7 + 1 +2 設定未??

http://www.telecom-cafe.com/foru ... =3232&pid=10201

Rank: 1

36^#

發表於 2011-1-15 17:42 | 顯示全部帖子

Forgot to say. I did that every time before upgrade. I learnt a lesson long time ago. Now, your turn.

Rank: 1

37^#

發表於 2011-1-18 10:02 | 顯示全部帖子

回復 266# 角色

My experiece tell that both SVN432 and SVN437 are very stable.  Just like Draytek router firmware, the manufacturer always advises users not to jump from lower version to higher one every time greater than 0.5.  I think logic can be applied to Switchfin here.  I don't suggest my fellow forum members to jump too fast from SVN373 to SVN456 directly.

The best strategy is to be SVN373 ==>  SVN432 ==> SVN437.  Don't go any further until next more stable release is out.

As you may know well, we won't upgrade Asterisk 1.4 to Asterisk 1.8 directly.  We usually upgrade step by step from Asterisk 1.4 ==> 1.6 ==> 1.8 finally.  Hope you understand what I mean.

Rank: 1

38^#

發表於 2011-1-18 17:49 | 顯示全部帖子

Have you include your Outgoing Dialing Rules in your Dial Plan section?? This is one of the places we always forget to check with.

Rank: 1

39^#

發表於 2011-1-18 22:16 | 顯示全部帖子

For registration with SIP providers far away from your Asterisk Server or the lagged respond time. You might try to give a longer registration time-out allowance.

Admin==>Sip Settings==>TOS under SIP Configuration

Adjust Default Incoming/Outgoing Registration Time as needed.

Rank: 1

40^#

發表於 2011-1-19 21:03 | 顯示全部帖子

In Qnewbie's case, if we apply it in Hong Kong using PCCW, the blocking of port 80 by ISP will be quite useful as we are not allowed to access http thru port 80 here.

We can, then use our desire port as we like.

Rank: 1

41^#

發表於 2011-1-21 10:12 | 顯示全部帖子

回復 303# 亞星

你是否係用 fixed IP，如果係，就一定要加返入去 extern IP 一欄，因為一般大部份人都會是用DDNS 浮動位址，所以是不需要的。之前可能沒有弄清楚所以你一直無法成功。

Rank: 1

42^#

發表於 2011-1-21 15:16 | 顯示全部帖子

本帖最後由 bubblestar 於 2011-1-21 15:17 編輯

回復 311# 亞星

最重要是你能夠做到。
至於externhost 和 externip 的設定，我也是在最初學習時，根據 Asterisk The Future of Telephony 2nd Edition 一書所講做調較的。由於我不是用Fixed IP，所以呢方面沒有太多經驗。

現節錄該書第352頁所講，方便大家參考:

externhost
externhost takes a fully qualified domain name as its argument. If Asterisk is behind
NAT, the SIP header will normally use the private IP address assigned to the server.
If you set this option, Asterisk will perform periodic DNS lookups on the hostname
and replace the private IP address with the IP address returned from the DNS
lookup:

externhost=my.hostname.tld

The use of externhost is not recommended in production systems,
because if the IP address of the server changes, the wrong IP address
will be set in the SIP headers until the next lookup is performed.
The use of externip is recommended instead.

externip
externip takes an IP address as its argument. If Asterisk is behind NAT, the SIP
header will normally use the private IP address assigned to the server. The remote
server will not know how to route back to this address; thus, it must be replaced
with a valid, routeable address:

externip=216.239.39.104

Rank: 1

43^#

發表於 2011-1-21 15:23 | 顯示全部帖子

回復 311# 亞星

ATCOM 的說法，我不知是否全對，但我是用DDNS 會有機會變IP 的，我只需要在externhost 加入自己的DDNS名稱已足夠了，externip 是留空的，一樣可以打出打入。可能呢方面真的是因人而異，或這因為Router 的設定而異吧。

Rank: 1

44^#

發表於 2011-1-24 11:38 | 顯示全部帖子

Speaking of the file in /var/log/messages, I discover that the time shown in this file is 8 hours behind Hong Kong. However, all the time recorded in CDR and in System Status are correct.

Like this morning, my IP01 woke up at about 09:15 but /var/log/messages shown 01:15. I think the culprit is the ntpd that is set to syncronize with inapproprite time server by default as below

Jan 24 01:15:20 IP01 cron.info cron[292]: loading crontab file /etc/config/crontab
Jan 24 01:25:42 IP01 daemon.info ntpd[288]: synchronized to 192.43.244.18, stratum 1

Where should I regulate this time or should I disable the ntp in Service Manager under Admin Tab to fix this problem?

Rank: 1

45^#

發表於 2011-1-24 11:46 | 顯示全部帖子

回復 320# bubblestar

I think the IP 192.43.244.18 is developer's own/personal time server address in Europe.