As Obihai announced on its blog page, Google Sets the Date for the End of XMPP with Google Voice (GV) to be 5/14/2014.
http://blog.obihai.com/2013/10/important-message-about-google-voice.html
After I read it, I decided to port my number out of GV to ANVEO (http://www.anveo.com/) since they are running a porting promotion at the moment (porting request must be submited before December 31st 2013). I can enjoy one year of unlimited incoming calls at ANVEO for $24. The terms for the free porting is copied below from their website:
* Free Porting Specific Terms: When the FREE porting is complete the phone number will be pre-paid for 12 months and account will be charged a non-refundable $24 (12 x $2/month) for Personal Unlimited rate plan
Otherwise porting a US number needs $15 porting fee without the promotion. Another option to keep the old GV number working is to order a new phone number at ANVEO and forward the GV number to the ANVEO number. There is no setup fee for a new ANVEO phone number when it is ordered on 'Personal Unlimited' rate plan ($2/month). However, I'm not convinced that free GV forwarding will last long therefore I chose to port the GV number out.
I first went to the following web page to unlock my GV number. It was unlocked immediately after I paid $3 to Google for porting it out.
https://www.google.com/voice/unlock
I need to submit a copy of the GV confirmation page for unlocking the number to ANVEO together with the porting request. The ANVEO porting request form can be downloaded from here. I submitted the porting request on night of 10/31 and added $30 into my ANVEO account with google checkout. I received an email from ANVEO on 11/5 saying that "the phone number porting is almost complete and it will be switched to our carrier within 48-72 hours. The phone number is now in your account."
I tried to use the ANVEO number in Asterisk and it worked. Before I can used it on a SIP device, I needed to activate SIP service at ANVEO website under Account Options->SIP Device
Registration. An SIP password is generated after the activation and Asterisk needs this SIP password to register for SIP. The username for a SIP device is the ANVEO account number.
The following are the context for ANVEO in users.conf for Asterisk
[general]
hassip = yes
hasiax = no
registeriax = no
callwaiting = yes
threewaycalling = yes
callwaitingcallerid = yes
transfer = yes
canpark = yes
cancallforward = yes
callreturn = yes
call-limit = 100
qualify = yes
disallow = all
allow = ulaw,alaw
type = friend
[anveo]
host=sip.anveo.com
port=5010
username= {account number}
secret= {SIP password}
insecure=port,invite
group = null
hasexten = yes
canreinvite = yes
callcounter = yes
disallow=all
allow=ulaw
context=anveo-in
registersip = yes
And the following is the context in extensions.conf for ANVEO incoming calls(6666 is the extension number of my home)
[anveo-in]
exten => s,1,NoOp(From Anveo ${EXTEN})
exten => s,n,Dial(SIP/6666)
I prefer Nonoh for outgoing calls, which currently offers free calling to countries such as US, Canada and China for 120 days after a credit (10 Euro minimum) is bought. And I found it a good idea to set the caller ID for outgoing calls to the ANVEO number at the Nonoh account settings.
The following are the context for Nonoh in users.conf for Asterisk
[nonoh]
host = sip.nonoh.net
username = {nonoh username}
secret = {nonoh password}
group = null
registersip = yes
canreinvite = yes
insecure = port,invite
hasexten = no
And the following is the context in extensions.conf for Nonoh (assuming the numbers dialed start with 00 then country code)
[DLPN_6666]
include = CallingRule_Out
include = default
include = parkedcalls
include = conferences
include = ringgroups
include = voicemenus
include = queues
include = voicemailgroups
include = directory
include = pagegroups
include = page_an_extension
[CallingRule_Out]
exten => _00[1-9]X.,1,Dial(SIP/nonoh/${EXTEN:0})
It is also possible to use ANVEO for outgoing calls, which costs 1 cent/minute in the US. The SIP device settings for outgoing calls can be found at
https://www.anveo.com/faq.asp?code=faq_sip_config
ANVEO also provides E911 service for $0.8/month per address and a bunch of add-ons for additional services.
Thursday, November 7, 2013
Monday, July 22, 2013
Apache Hadoop with single Fedora node
Today when I tried to start Jobtracker for Apache Hadoop 1.2.1, I kept getting the following ENOENT error
I realized the most important error is the bold one, which is related to logging as specified in mapred-site.xml
After the the correct folder permissions are set, it should look like following
FATAL org.apache.hadoop.mapred.JobTracker: ENOENT: No such file or directory
at org.apache.hadoop.io.nativeio.NativeIO.chmod(Native Method)
at org.apache.hadoop.fs.FileUtil.execSetPermission(FileUtil.java:699)
at org.apache.hadoop.fs.FileUtil.setPermission(FileUtil.java:654)
at org.apache.hadoop.fs.RawLocalFileSystem.setPermission(RawLocalFileSystem.java:509)
at org.apache.hadoop.fs.RawLocalFileSystem.mkdirs(RawLocalFileSystem.java:344)
at org.apache.hadoop.fs.FilterFileSystem.mkdirs(FilterFileSystem.java:189)
at org.apache.hadoop.mapred.CompletedJobStatusStore.(CompletedJobStatusStore.java:81)
at org.apache.hadoop.mapred.JobTracker.initialize(JobTracker.java:2051)
at org.apache.hadoop.mapred.JobTracker.offerService(JobTracker.java:2328)
at org.apache.hadoop.mapred.JobTracker.main(JobTracker.java:4792)
I realized the most important error is the bold one, which is related to logging as specified in mapred-site.xml
mapred.job.tracker.persist.jobstatus.dir file:////var/log/hadoop/mr/jobstatus
After the the correct folder permissions are set, it should look like following
$ ll /var/log/hadoop/
drwxr-xr-x. 2 hdfs hadoop 4096 Jul 22 22:45 hdfs
drwxr-xr-x. 4 mapred hadoop 4096 Jul 22 23:10 mapred
drwxr-xr-x. 2 mapred hadoop 4096 Jul 22 20:14 mr
After all the services are running, I can list them by#jps
22896 DataNode
26189 TaskTracker
22225 NameNode
26502 Jps
26042 JobTracker
And I can list the listening ports of the services by# lsof -i -P | egrep -v "ESTABLISHED" | grep java
java 22225 hdfs 66u IPv4 573305 0t0 TCP localhost:8020 (LISTEN)
java 22225 hdfs 79u IPv4 573311 0t0 TCP localhost:50070 (LISTEN)
java 22896 hdfs 63u IPv4 575844 0t0 TCP *:50010 (LISTEN)
java 22896 hdfs 65u IPv4 576654 0t0 TCP *:50075 (LISTEN)
java 22896 hdfs 73u IPv4 575856 0t0 TCP *:50020 (LISTEN)
java 26042 mapred 64u IPv4 589571 0t0 TCP localhost:9000 (LISTEN)
java 26042 mapred 75u IPv4 589575 0t0 TCP localhost:50030 (LISTEN)
java 26189 mapred 61u IPv4 590005 0t0 TCP localhost:40660 (LISTEN)
java 26189 mapred 79u IPv4 590177 0t0 TCP *:50060 (LISTEN)
Monday, July 15, 2013
Fedora dracut in chroot environment
The following is the procedure to create new initframfs when the root filesystem has structural changes such as between LVM, MD or plain.
- Chroot to the desired folder (.e.g. /mnt/temp)
chroot /mnt/temp
- mount the system partitions /proc, /run, /dev, /sys
mount -t proc proc /proc
mount -t tmpfs tmpfs /run
mount -t devtmpfs devtmpfs /dev
mount -t sysfs sysfs /sys - mount the /boot and / partition
mount -t ext4 /dev/sdb1 /boot
mount -t ext4 /dev/md0 / - Create the udev/data folder to emulate the udev database
cd /run
mkdir udev/data - To include mdadm in Fedora dracut: add module mdraid found in /usr/lib/dracut/modules.d/
dracut -v -f -a mdraid --mdadmconf /boot/initramfs-$(uname -r).img $(uname -r)
Saturday, July 13, 2013
How to make Samba 4 shares writable with Fedora 19 and Selinux
Today I found I couldn't create new folders in my samba 4 share under Fedora 19. And this was due to the settings of Selinux since there wasn't any problem without enabling Selinux.
The status of the Selinux boolean values that are relevant to Samba can be queried via the following command:
Since we need to allow samba to modify shared files, the files/directories must be labeled public_content_rw_t and we must turn on the smbd_anon_write boolean.
Note: File context can be temporarily modified with the chcon command. However, that won't survive a relabeling. We need to permanently change the file context by using the semanage fcontext command. This will modify the SELinux labeling database. It is necessary to use restorecon to apply the labels.
The status of the Selinux boolean values that are relevant to Samba can be queried via the following command:
#getsebool -a | grep samba
#getsebool -a | grep smbd
Since we need to allow samba to modify shared files, the files/directories must be labeled public_content_rw_t and we must turn on the smbd_anon_write boolean.
- Labeling all files under the share folder (e.g. /mnt/media) to public_content_rw_t so that they can be modified by multiple domains (Apache, FTP, rsync, Samba).
#semanage fcontext -a -t public_content_rw_t "/mnt/media(/.*)?"
#restorecon -F -R /mnt/media
Note: File context can be temporarily modified with the chcon command. However, that won't survive a relabeling. We need to permanently change the file context by using the semanage fcontext command. This will modify the SELinux labeling database. It is necessary to use restorecon to apply the labels.
- Turn on the smbd_anon_write boolean:
#setsebool -P smbd_anon_write 1
- It's NOT necessary to turn on samba_export_all_rw if the shared files/directories are properly labeled and the smbd_anon_write boolean is turned on.
- The security context of the files can be verified via
# ls -Z /mnt/media
drwxrwxr-x. video media system_u:object_r:public_content_rw_t:s0 video
Tuesday, March 5, 2013
Running power calculator in windows 7
The following are important for the power calculator power toy to run successfully in windows 7:
- The file pcalc.exe needs to run in compatibility mode for windows XP. This can be set by right clicking the file pcalc.exe in windows explorer and click "Properties" of the context menu. Then click on the button near the bottom "Change settings for all userse" and check the compatility mode as shown below. Click OK to save the changes.
- The file pcalc.exe can not reside in windows\system32 folder. I found windows folder or other folders should work.
Sunday, March 3, 2013
Use search in windows 7 to clean up the mess from BOX sync
Today I found that the BOX sync I installed for BOX.net caused a big problem in my data folder. It created multiple copies of the same file for each file in my local and remote data folder and some of the files were cloned for up to 20 times.
After I did a quick look at many of the cloned local copies created by BOX sync, I found there are some patterns on their file name and last modification date:
After I did a quick look at many of the cloned local copies created by BOX sync, I found there are some patterns on their file name and last modification date:
- They have a file name appendix (n) before the file extension, where n is a number ranging from 1 to 20
- They were last modified on the same day: Feb. 26, 2013
- They are all files. No sub folders were cloned
I could use search in windows 7 to locate all the files satisfying the above patterns with the following search syntax:
filename: "(" kind: NOT folders datemodified:2/26/2013
More than 3000 items were found matching the search criteria. After I verified that they were actually excessive files, I selected all of them and deleted them to clean up the mess.
Subscribe to:
Posts (Atom)