返回列表 發帖
回復 300# ckleea


   明白,我可以將備份直接copy落去asterisk folder裡面,理論上應可正常運行,對嗎?應該唔需要重新再設定一次

TOP

回復 301# orangelau


    理論上是對。

TOP

回復 302# ckleea

試左新版有幾個BUG:
(1) 係OPTION>REBOOT後不能再進入GUI介面,但運作正常,試過重裝,不做任何修改,結果仍是一樣
(2) 啟動FOLLOW ME功能的EXT. 完全不能再接通, 直至關閉FOLLOW ME功能, EXT.方可再接通
(3) 啟動VOICEMAIL功能的EXT. 完全不能再接通, 直至關閉VOICEMAIL功能, EXT.方可再接通
(4) 所有FEATURE CODE(轉線等功能)都不能使用

TOP

回復 303# orangelau


我沒有使用這些功能,等有空試下。

chan_dongle ok?

TOP

回復 304# ckleea

個chan-dongle仍是一樣,一時得一時唔得,還發現到一個新問題:在我用ext通話時,若個chan-dongle收到來電,ext會斷線,不能打出,直至chan-dongle斷線後,才能再運作。

TOP

你是經常有多人使用?

你的情況似CPU 應付不來

TOP

回復 306# ckleea
明白

TOP

本帖最後由 ckleea 於 2014-5-31 08:31 編輯

為你的Raspberrypi Image 加入 Google Cloud Printing,原先已有 Air Print
用root ssh login 後
1. ,輸入下指令
  1. sudo apt-get install build-essential python-dev libcups2-dev python-pip
  2. pip install cloudprint pycups
複製代碼
2. 然後建立
sudo nano /etc/init.d/gcloudprint
  1. #! /bin/bash
  2. # /etc/init.d/gcloudprint

  3. ### BEGIN INIT INFO
  4. # Provides:        cloudprint
  5. # Required-Start:    $remote_fs $syslog
  6. # Required-Stop:    $remote_fs $syslog
  7. # Default-Start:    2 3 4 5
  8. # Default-Stop:        0 1 6
  9. # Short-Description:    System service to run cloud print connector
  10. # Description:        System service to run cloud print connector
  11. ### END INIT INFO

  12. # Carry out start/stop/restart actions
  13. case "$1" in
  14.     start)
  15.         echo "Starting cloud print connector"
  16.         cloudprint >> /var/log/cloudprint.log &
  17.         ;;
  18.     stop)
  19.         echo "Stopping cloud print connector"
  20.         killall cloudprint
  21.         ;;
  22.     restart)
  23.         echo "Restart connector"
  24.         echo "Stopping cloud print connector"
  25.         killall cloudprint
  26.         echo "Starting cloud print connector"
  27.         cloudprint >> /var/log/cloudprint.log &
  28.         ;;
  29.     *)
  30.         echo "Usage: /etc/init.d/gcloudprint {start|stop|restart}"
  31.         exit 1
  32.         ;;
  33. esac

  34. exit 0
複製代碼
3. 設定 gcloudprint 在boot 機後可自行起動
sudo chmod +x /etc/init.d/gcloudprint
sudo update-rc.d gcloudprint defaults

4. 最後在 command line,輸入 cloudprint想動
然後輸入 google username 和 password,連上你的 google account

5. 如果重設 google account, 在 /root directory 內, delete 這兩個檔案
rm .cloudorintauth
rm .cloudprintauth.sasl

https://www.google.com/cloudprint/#printers

screenshot.31-05-2014 08.18.54.png

Ref: http://dev.shyd.de/2012/01/remot ... google-cloud-print/

Enjoy cloud printing.

TOP

Another site showing similar service

http://atinkerersblog.wordpress. ... -on-a-raspberry-pi/

TOP

回復 309# ckleea


    Sounds good

TOP

回復 288# orangelau


    I got the same problem as you do. I can resolve it by flashing another version of firmware. You can try different version of firmware of your dongle and it must be able to resolve the "dialing" status problem.

TOP

回復 311# h20555


    Good news to me

TOP

本帖最後由 ckleea 於 2015-1-8 22:01 編輯

更新版即將發佈

內容如下
Version 1.8
Last updated on
Raspberry Pi firmware update "version 5abd572e2ed1811283443387af09377b95501c50 Dec 19 2014"
Debian Wheezy OS update to "Linux raspberrypi 3.12.35+ #730 PREEMPT Fri Dec 19 18:31:24 GMT 2014 armv6l GNU/Linux"

Webmin update to 1.730
Softether VPN update to (Ver 4.12, Build 9514, beta) 2014/11/17

Remove Yate and Minisipserver
Add Kamailio 4.01 Sip proxy (optional). Use defaut UDP 5060 port; not configure

Asterisk update to latest SVN r403917
1. Add CDR logging to mySQL (cdr_odbc.conf)
2. Add Realtime SIP/IAX users for Asterisk (res_odbc.conf, extconfig.conf, modules.conf)
3. Add cron job to check CMPhone drop registration (/opt/scripts/asterisk.sh)
4. Update chan_dongle to match asterisk update
5. Change default asterisk sip accounts from 1000 and 1001 to 2000 and 2001
6. Use UDP 65060 as sip port. Change to other port in sip.conf

TOP

本帖最後由 ckleea 於 2015-1-11 16:52 編輯

Beta version 其實已經可以下載

Be careful to test out asterisk by replacing your own config files

My suggestion is to create a new set of config files by APL or GUI

Remember the default port is 65060.

SIP Port 5060 is not using at the moment

TOP

期待中

TOP

返回列表