Make cell phones send calls to trixbox asterisk voicemail

We have people travelling internationally who are using different SIM cards for different countries on unlocked iphones. Different people use the SIMS so we don't want them to setup voicemail on each SIM each time they travel somewhere or hand off the phone.

So what I am doing is forwarding voicemail to my asterisk (trixbox) pbx. This can be done with RDNIS if your system supports it. The way I accomplished this though was through forwarding calls destined for voicemail to a specific DID I have on my asterisk system and setup the incoming route for the DID to go directly to the users office voicemail. They then get emailed the voicemail message.

Using the following call forwarding codes, I have the user forward voicemail calls to the DID I setup in asterisk.

Here is how I forward the calls on the cell phone (on the iphone, push and hold down 0 to get a + symbol):

No Answer Forward: **61*+ 1 DIDNUMBER # [SEND]
Unreachable Forward:**62*+ 1 DIDNUMBER # [SEND]
Busy Forward* * 67 * + 1 DIDNUMBER # [SEND]

This worked for me on AT&T.

CHROOT to remote fedora 16 install on SAN via iscsiadm

The goal of this post is to help you gain access to a CHROOT environment of a F16 install which was installed to a SAN via iscsi.

While working on installing fedora to a diskless system using iscsi root and boot, my system would not boot. I needed a way to access the system in chroot so I could reinstall grub with the proper iscsi boot config. Everything discussed here is Fedora 16 64bit. I am using an EMC VNXe 3100 SAN. For this demonstration, I do not have chap enabled so it is not discussed here.

Boot the Fedora 16 Live CD USB

• Boot Fedora 16 Live USB. I had some problems getting mine to boot so see blog entry http://ispman.blogspot.com/2012/02/boot-fedora-16-64-bit-live-boot-from.html
• Open a terminal window and su
  

Connect to the SAN via iSCSI using iscsiadm

• Edit /etc/iscsi/initiatorname.iscsi and put in the iqn your machine is going to initiate iscsi as. In my case: InitiatorName=iqn.1986-03.com.ibm:06LEJE8.linux Note: The initiator name also needs programmed in your SAN to allow connections from the IQN.
• Reload iscsi:

#/etc/init.d/iscsi restart

• Setup your ethernet card to have an IP on the SAN network:

# ifconfig eth0 172.16.10.100/24

• Add the network card you are going to use for iscsi to the iscsi database:

# iscsiadm -m iface -I eth0 -o new
New interface eth0 added

• Add the iscsi target to your isci database using iscsiadm: iscsiadm -m node -T -p -o new

# iscsiadm -m node -T iqn.1992-05.com.emc:apm001140005820000-10-vnxe -p 172.16.10.18 -o new

Starting iscsid:
New iSCSI node [tcp:[hw=,ip=,net_if=,iscsi_if=default] 172.16.10.18,3260,-1 iqn.1992-05.com.emc:ap001140005820000-10-vnxe] added

• Now log into the iscsi target: iscsiadm -m node -T -p -l

# iscsiadm -m node -T iqn.1992-05.com.emc:ap001140005820000-10-vnxe -p 172.16.10.18 -l

Logging in to [iface: default, target: iqn.1992-05.com.emc:apm00114005820000-10-vnxe, portal: {172.16.10.18,3260]

Login to [iface: default, target: iqn.1992-05.com.emc:apm00114005820000-10-vnxe, portal: {172.16.10.18,3260] successful

• Ensure the session is up and running

# iscsiadm -m session -P 3

• Using dmesg, find what device your iscsi drive was attached to. In my case it was sdb
• I used LVM when I installed to the iscsi target before so I have to bring up the lv's

#fdisk -l /dev/sdb

• Use lvs to find the VG name
  

#lvs

• Make the lv active

#vgchange -a y VolGroup

• Make your temporary mountpoint

#mkdir /mnt/sysimage

• Mount the root partition to sysimage. For me, lvs told me the name was lv_root, then mount the rest
  

#mount /dev/VolGroup/lv_root /mnt/sysimage

#mount -t tmpfs none /mnt/sysimage/tmp

#mount -t tmpfs none /mnt/sysimage/var/lock

#mount -t tmpfs none /mnt/sysimage/var/lib/iscsi

#mount --bind /dev /mnt/sysimage/dev

#mount -t proc none /mnt/sysimage/proc

• Mount the boot partition of the drive which for me was sdb2
  

#mount /dev/sdb2 /mnt/sysimage/boot

• Begin the chroot

#chroot /mnt/sysimage

#source /etc/profile

Boot Fedora 16 64 bit live boot from usb ibm hs22

I was not able to boot to a Fedora 64bit live usb stick. I downloaded the 64bit live iso and used the windows version of Fedora Live USB Created. The boot would drop out saying no root device.


From: http://www.fedoraforum.org/forum/showthread.php?p=1476942

nk1eto Offline Registered User

Join Date: May 2011 Posts: 1

Re: Lenovo S205 won't boot any Live USB Fedora distro

---

I was having this same exact problem on a Lenovo x120e Thinkpad, Fedora liveUSB created with unetbootin. Solved it by:

1. Find your USB disk label. When in the debug shell, run

Code:

ls /dev/disk/by-label/ UDISK

My label was UDISK. The fedora installer by default expects the label to be Fedora-15-x86_64-Live-Desktop (or similar)
2. Reboot and edit the GRUB boot command.

Code:

hit ENTER to view GRUB menu. hit 'e' to edit commands before booting. hit 'e' to edit top entry. change LABEL=Fedora-15-x86_64-Live-Desktop to LABEL= (also remove 'quiet rhgb' for verbosity) hit ENTER to accept and 'b' to boot.

that should do it.

---

Last edited by nk1eto; 28th May 2011 at 03:23 PM.

Specify different network policies for different ssid's on a single cisco ap

From looking at the log file for NPS (to find your log file go to server manager, roles, network policy and access services, NPS, Accounting) I was able to see that when I connect to different ssids (single cisco access point, multiple ssids and vlans), the log shows me the mac address of the virtual ap I connect to. I tried to find this mac address on my cisco ap but couldnt so I connected to the different ssid's, looked at the log to get them.

For example:
"VMDC01","IAS",01/10/2012,10:00:41,1,"seegrid\bfisk","SEEGRID\bfisk","0023.050c.e751","0811.9688.ffb0",,,"pghap2","192.168.10.25",51105,9,"192.168.10.25","pghap02",,,19,,,1,11,"SGA Wireless",0,"311 1 192.168.10.4 01/10/2012 13:30:09 192",,,,"Microsoft: Secured password (EAP-MSCHAP v2)",,,,,,,,,,,,,,,,,,,,,,,,,,,,,,"SGA",1,,,,

After my username bfisk, you will see the mac for the vap and for my client computer connecting to the wifi. Looking at the logs I found one ssid = e751 and the other was e750.

I then created network policies, one for each ssid/vlan and used the condition Called Station ID = e751$ for the one ssid, e750$ for the other ssid. Added the different domain group conditions for each and presto, working like a champ.

Downfall to this is if you have multple ap's you will need to do the same for each ap to get all the mac addresses. I couldnt find the vap mac using show int.