AkiliSoft

How to find Static IP Address

2009-11-19T18:46:00.000-08:00

1. Get the MAC address from the phone.
2. Put Protocol sniffer (like Wireshark) on hub w/ Phone and PC.
3. On windows PC:

arp -s (unused IP on LAN) (MAC of phone entered like 00-aa-00-62-c6-09)

4. On PC, ping IP:

ping (unused IP selected)

5. Check Protocol sniffer for responses from phone's MAC address.
6. I think that you should see it's real IP in the ARP packets coming from the phone.
7. Set your PC up with an address on the subnet of the phone.
8. Telnet or http into the phone/device.
This is probably assuming that the default password hasn't changed.

Digium PCI Telephony card Stability Issues

2009-09-18T07:34:00.000-07:00

How to solve Digium PCI Telephony card Stability Issues

This guide is mainly related to TE122P stability issues which are being experienced by some users of Asterisk®. Naturally, this also applies to Elastix® and other distribtions that use Asterisk®. This guide can also be applied to any other Digium® products that you might be having issues with and is a guide for good practice in any case. This has been confirmed with both Elastix® and some other ISO based distributions.

In the last month, we had two systems that had similar issues, which was dropping of calls at random times during the day. Its one of those problems that is not easy to diagnose, even down to using PRI Debug, it looks like the carrier equipment has failed for a brief period. So naturally you follow up with the carrier, asking them to look at the line to see if they have any issues.

The reason why I mention two machines, was that they were about 14 months apart in motherboard design (although similar), and it would be beneficial to see if the same correction applied to both would correct the issue, giving us some confidence that this was a step in the right direction. It has also been reported by others that this occurs on both AMD® and Intel® Chipset motherboards

To confirm you have a similar issue, the symptoms/issues that you may come across are:

1) Calls being dropped (Due to Red Alarm)
2) Red Alarms occurring on a regular basis, usually at least 10 per day (as evidenced in the Asterisk Logs)
3) Red Alarms occurring for less than a second
4) When using a Asterisk® Based distribution such as Elastix®, initial format and install is quite slow (15 min format on 120Gb, and 26 min install of ISO as opposed to 3 min format and 6-8 min install of ISO)
5) ZTTool showing an ever increasing increase in the Interrupt misses.
6) The faster the machine, the faster the Interrupt misses increase, and also naturally the more often the call drop outs.

Many of us are aware of the interrupt issue where it is always good practice to make sure that the Digium® cards are on their own interrupt (e.g. not sharing with another device), and this includes many of the Digium® Range, as missed interrupts can cause different issues on different cards. As an example the TDM400P with missed interrupts, can result in crackle on the line, or hissing/popping noises. Many of us have become blaise about this interrupt issue as OS software has improved, drivers have improved, APIC has improved and for many it has not presented any issue.

However, with some of the later motherboards, especially with some of the more "generic" boards, they have been making reasonable changes which include less PCI Slots, changing from IDE to SATA, which also includes support of both hard drive types (including mixing), and many other small changes. These changes are making an impact as we found out recently. It is necessary to move back to confirming that the interrupts are not conflicting with the DIGIUM® Cards. At this point it should be noted that these rules should not only apply to Digium® cards but any other cards used for Telephony.

The same emphasis that you place on good network infrastructure, WAN Quality of Service, traffic prioritisation, should equally apply to the telephony card that you install. Those same "realtime traffic" rules that you steadfastly apply to your Local Area Network and Wide Area Network should apply to your Telephony interface.

To resolve this issue, we used a few "tools" that are available on the system. You don't need to install any additional software. The first one is the simple command

#cat /proc/interrupts

CPU0 CPU1
0: 56986323 0 IO-APIC-edge timer
6: 5 0 IO-APIC-edge floppy
8: 3 0 IO-APIC-edge rtc
9: 0 0 IO-APIC-level acpi
193: 990440 0 IO-APIC-level libata, wcte12x[p]
201: 56975304 0 IO-APIC-level eth0
NMI: 0 0
LOC: 55878552 55878496
ERR: 0
MIS: 0

This straight away tells us that the SATA Interface/Driver and the TE122/Driver are sharing the same interrupt on the system.

Another tool is using ZTTEST which runs a test to confirm whether we had some easy to recognise Interrupt issues

root@elastix ~]# zttest -v
Opened pseudo zap interface, measuring accuracy...

8192 zaptel samples in 8191.664 system clock sample intervals (99.996%)
8192 zaptel samples in 8191.016 system clock sample intervals (99.988%)
8192 zaptel samples in 8191.543 system clock sample intervals (99.994%)
8192 zaptel samples in 8191.520 system clock sample intervals (99.994%)
8192 zaptel samples in 8191.512 system clock sample intervals (99.994%)
8192 zaptel samples in 8191.424 system clock sample intervals (99.993%)
8192 zaptel samples in 56191.512 system clock sample intervals (0.146%) <==== The blip
8192 zaptel samples in 8191.480 system clock sample intervals (99.994%)
8192 zaptel samples in 8191.423 system clock sample intervals (99.993%)
8192 zaptel samples in 8191.456 system clock sample intervals (99.993%)
8192 zaptel samples in 8191.472 system clock sample intervals (99.994%)
8192 zaptel samples in 8191.440 system clock sample intervals (99.993%)
8192 zaptel samples in 8191.496 system clock sample intervals (99.994%)
8192 zaptel samples in 8191.464 system clock sample intervals (99.993%)
8192 zaptel samples in 8191.488 system clock sample intervals (99.994%)
8192 zaptel samples in 8191.432 system clock sample intervals (99.993%)
8192 zaptel samples in 8191.528 system clock sample intervals (99.994%)

We run this test over several hours and noted that in general we were on target (on target is generally a figure of 99.97% or better), except for the occasional blip that you will notice in the listing above. Now generally we take the ZTTEST results with a grain of salt, but in this case, this blip was not something we had seen before, and secondly, the amount of times that it appeared over a two hour period, seemed to roughly correalate to the timing that the system dropped the calls. Secondly, it appeared that the IRQ misses that we saw before, seemed to increase each time this blip appeared.

Last but not least we used the

lspci -vb command

What this provided was very detailed information on how the cards/devices were seen at both the bus level and also at the OS level. The output we saw was as follows

[root@elastix asterisk]# lspci -vb

00:1f.2 IDE interface: Intel Corporation 82801GB/GR/GH (ICH7 Family) SATA IDE Co
ntroller (rev 01) (prog-if 8f [Master SecP SecO PriP PriO])
Subsystem: Giga-byte Technology Unknown device b002
Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 5
I/O ports at d400
I/O ports at d800
I/O ports at dc00
I/O ports at e000
I/O ports at e400
Capabilities: [70] Power Management version 2

00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 01)
Subsystem: Giga-byte Technology Unknown device 5001
Flags: medium devsel, IRQ 5
I/O ports at 0500

02:00.0 Ethernet controller: Digium, Inc. Unknown device 8001 (rev 11)
Subsystem: Digium, Inc. Unknown device 8001
Flags: bus master, medium devsel, latency 64, IRQ 5
I/O ports at a000
Memory at e1000000 (32-bit, non-prefetchable)
Capabilities: [c0] Power Management version 2

02:01.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139
C+ (rev 10)
Subsystem: Realtek Semiconductor Co., Ltd. RT8139
Flags: bus master, medium devsel, latency 64, IRQ 9
I/O ports at a400
Memory at e1001000 (32-bit, non-prefetchable)
Capabilities: [50] Power Management version 2

(*Note - I have only included a few relevant lines.)

Now the normal routine is to relocate the TE122P into a different slot on the motherboard, which in most cases will change the IRQ that the TE122 will use, usually correcting the issue.

So Our interrupts now look like this

cat /proc/interrupts
CPU0 CPU1
0: 56986323 0 IO-APIC-edge timer
6: 5 0 IO-APIC-edge floppy
8: 3 0 IO-APIC-edge rtc
9: 0 0 IO-APIC-level acpi
193: 990440 0 IO-APIC-level libata, eth0
201: 56975304 0 IO-APIC-level wcte12x[p]
NMI: 0 0
LOC: 55878552 55878496
ERR: 0
MIS: 0

If anyone is watching, you will notice that we switched the position of our Ethernet Card and the TE122P card in the PCI Slots. But we now have the desired results that we were looking for which is the TE122P now sitting on an Interrupt of its own.

Normally this would correct things, but what was interesting was our interrupts continued to climb. It appeared that all that we have been taught about interrupts and TE122P was wrong. Suspicions continued....did we have a faulty card? This was discounted straight away as we had two systems doing the same thing, the only thing that was the same was the carrier, although these were two separate locations, so again this was discounted, and we were left with the machine.

After many, many hours, working through all the BIOS options, disabling devices, trying IDE Drives instead of SATA Drives etc etc...we finally made a change which surprised us. Changing the SATA mode in the BIOS from Auto (which is the default on all these motherboards) to SATA Enhanced resulted in the interrupt misses becoming rock solid after boot up. It was the last thing we wanted to change, as we were using a IDE DVDROM drive (which many of the system builders are still supplying).

If the system is using SATA Hard Drive and a IDE CDROM, the system, in Auto mode selects the PATA/SATA mode to support both devices and it appears that this mode is causing a large amount of the issues. Whether it is a combination of the LIBATA Driver and this PATA/SATA compatibility mode, we cannot be sure which is causing the issue. But taking a huge guess, I suspect that this mode is causing clock cycles to be missed or "stolen" resulting in the interrupt misses.

What further backs up that we had found the device that was causing the issue, was the fact that now, upon installing the ISO Distribution again, the installation was back to lightning fast, with 3 mins for the format, and 5 or so minutes for the install.

Naturally, to confirm that we have found the issue, we put everything back to defaults in the BIOS, we moved the cards back to the slots that we had previously, and run the same tests, reinstalled the ISO, which went back to the very long install time, and then checked the interrupts and found them climbing again. This time, we made just the change to the SATA settings in BIOS, and whilst this defintely slowed the interrupt misses, but they were still climbing, but only at a rate of 2 or so every minute, which was a lot better, but not the rock steady position that we had with both corrections.

So to summarise, it appears that the two issues together were causing the Interrupt misses that we had, which were

1) The LIBATA and the WCTE12x[p} driver cannot be on the same interrupt
2) The SATA Driver must be set to ENHANCED MODE (to reduce the possibility that the system selects PATA/SATA mode) which means that you need to be using a SATA (not IDE) CDROM or DVDROM, otherwise it may be disabled

Further evidence has been reviewed on Google, that similar issues are being found on Linux and other Operating Systems with handling of Dual IDE and SATA. What was interesting is that on one motherboard that we applied these changes, we lost access to the IDE Drive, on the other it appeared to still function with and IDE DVD Drive, while in SATA Enhanced mode. It clearly shows that the board manufactures have not got this mode working correctly, and it appears to affect many other boards as well including SuperMicro, ASUS and many others.

Anyhow, we made the changes above to two machines which were defintely suffering from the issue, and we can confirm that they have been in place now for several weeks withour an interrupts miss or any issues (which is what we wanted).

Hope this helps others with similar issues.

Source;
http://www.elastixconnection.com/index.php?option=com_content&task=view&id=60&Itemid=77

Receive and Send Fax with Asterisk 1.4/1.6

2009-09-11T20:52:00.000-07:00

Receiving and sending faxes with asterisk 1.4, NVFaxDetect, iaxmodem and hylafax

UPDATE: Changes to mutex usage in Asterisk 1.4.23 cause NVFax to cease to compile properly, see below for updated files that compile with 1.4.23.1

We have bridged our HylaFax server with our Asterisk server in order to be able to send and receive faxes over VOIP phone lines and to eliminate dedicated PSTN phone lines hooked up directly to modems on our HylaFax server. A lot of documentation floating around on the internet states that VOIP phone lines are not really suited to send/receive faxes. We have found out that it mostly depend on the providers you are using and on your network connectivity quality.

Note: To be able to send/receive faxes over IP, your provider has to support the ulaw codec (alaw in Europe and other areas). gsm, g729 and other compression codecs won't work.
We obtain virtually 100% successful completion for fax transmissions (20 pages per transmission in our tests) with one specific provider while it doesn't work at all with other providers.

Note although that the setup described is this article is also convenient if your faxes come in through PSTN lines (conventional copper wire lines) hooked up to your asterisk server. We used to have dedicated PSTN lines hooked up directly to physical hardware modems on our HylaFax server. We moved those lines to Asterisk and it forwards the call to virtual modems (iaxmodems) running on the HylaFax server residing on the same LAN. Note that there is zero degradation in fax transmission over an iax2 channel on the LAN (Local Area Network).

Iaxmodem documentation states that it should only be used to connect to an Asterisk server over a LAN connection, there is no degradation in fax transmission over an iax2 channel on a LAN. So if you receive fax phone calls over VOIP from the internet, Asterisk will be in charge of dealing with your VOIP provider to insure that the fax is transmitted correctly. If your asterisk server receives fax phone calls over traditional PSTN copper wire lines, you will experience zero fax transmission problems with the setup defined in this article.

Iaxmodem is viewed as an IAX2 extension from Asterisk. It allows you to use any other software at your convenience beside HylaFax to handle the faxes. From linux or hylafax, the virtual iaxmodem is just viewed as a standard hardware fax-modem that could be connected to your system.

What is needed:

At minimum, if you have a dedicated number for your fax machine and you don't need to detect incoming fax tones from a human person you will need:

* Iaxmodem (Click to download)

If you need to detect incoming fax tones in order to be able to share your fax lines with human voice, you will need to recompile asterisk with NVFaxdetect support, simply compile Asterisk after adding the following files into the apps folder in the asterisk sources. The Makefile is just the genuine Makefile with the NVfax apps added into it like this:

APPS+=app_nv_faxdetect.so
APPS+=app_nv_backgrounddetect.so

* Asterisk sources
* apps/app_nv_faxdetect-1.0.6_1.c
* apps/app_nv_backgrounddetect-1.0.6_1.c
* apps/Makefile

UPDATE: For Asterisk 1.4.23.1 and probably for future Asterisk releases, use the following NVFax files instead:

* apps/app_nv_faxdetect-1.0.6_1-foras1.4.23.1.c
* apps/app_nv_backgrounddetect-1.0.6_1-foras1.4.23.1.c

Note: If you downloaded and installed Asterisk from a pre-compiled distribution repository (yum install, trixbox, etc.), you may already have NVFax support built-in to your Asterisk server. Just type the following command to find out, if the modules are there, you already have support for NVFax and you can skip this step.

$ ls /usr/lib/asterisk/modules/app_nv_*

/usr/lib/asterisk/modules/app_nv_backgrounddetect-1.0.6_1.so

/usr/lib/asterisk/modules/app_nv_faxdetect-1.0.6_1.so

Note2: If your fax calls come in exclusively through PSTN lines, you do not need NVFax, just use Zaptel for fax detection. Zaptel fax detection is bundled with every asterisk distribution as far as we can tell. We do not really know because our PSTN lines are hooked to a GXW4104 IP Analog Gateway that forwards PSTN fax calls to our Asterisk server through VOIP. We do not use Zaptel, except ztdummy with high resolution timer kernel support for timing.

You will also need a software to handle faxes coming into or going out from your iaxmodem, we use HylaFax:

* HylaFax (Click to download)

Iaxmodem setup

Download, compile and install iaxmodem. We built iaxmodem statically ( issuing the command "./build static" to build) and we have just copied the generated executable (iaxmodem) to /usr/local/bin

Install the configuration file for your modem in /etc/iaxmodem (mkdir /etc/iaxmodem), we configured 2 faxes to be mapped to 2 extensions defined in asterisk configuration; extension 125 and extension 126:

extension 125 file in /etc/iaxmodem/tty125 :

device /dev/tty125
owner uucp:uucp
mode 660
port 4570
refresh 1800
server 10.10.1.20
peername 125
secret XXXXX
cidname Technologies OC9-ACTS
cidnumber 5555551212
codec ulaw

extension 126 file in /etc/iaxmodem/tty126 :

device /dev/tty126
owner uucp:uucp
mode 660
port 4571
refresh 1800
server 10.10.1.20
peername 126
secret XXXXX
cidname Technologies OC9-ACTS
cidnumber 5555551212
codec ulaw

We arranged so that iaxmodem starts automatically by adding the following to our rc.local file :

/usr/local/bin/iaxmodem

Note: Do not put any other file in /etc/iaxmodem if you use the above command. We left a text file that didn't look at all like an iaxmodem config file but still, iaxmodem read that file and locked up the default iax2 port (4569) on the machine! ;-)

With no option given, iaxmodem just automatically reads all files in /etc/iaxmodem and configures all virtual modems accordingly. We defined extension 125 and 126 with the same passwords in asterisk.On startup iaxmodem registers extension 125 and 126 with the asterisk server. We can see this by running the following command:

asterisk -r -x "iax2 show peers"

126 192.168.11.138 (D) 255.255.255.255 4571 OK (2 ms)
125 192.168.11.138 (D) 255.255.255.255 4570 OK (2 ms)

At this point asterisk is ready to forward calls to the 2 iaxmodems. We have a dedicated fax number, we just mapped that number to extension 125 in FreePBX incoming routes and asterisk forwards all calls to that number to the iaxmodem virtual fax.

Setting up fax tone detection

This step is only required if you want to share your fax lines with human voice. Basically, NVFaxdetect will listen for fax tones when a call comes into asterisk. If it hears fax tones, it will forward the call to extension 126 otherwise, the call is just normally forwarded to our IVR (automated digital receptionist).

To enable Asterisk to use NVFax to detect incoming faxes, we simply need to recompile it after adding the files listed above in the "What is needed" section.

We can now enable fax detection in FreePBX incoming route, specifying to forward the call to extension 126 if fax tones are detected. 5 seconds is the recommanded time to listen for fax tones before passing the call to the IVR or to a human. A human caller will simply hears an additional ring tone during that 5 seconds.

HylaFax configuration

Note that you can use any software to pickup and send faxes from/to the iaxmodems, we just use Hylafax. Here is our HylaFax config file so that it can talk with the iaxmodem on extension 125:

file in /var/spool/hylafax/etc/config.tty125 :

CountryCode: 1
AreaCode: 418
FAXNumber: +1.555.555.1212
LongDistancePrefix: 1
InternationalPrefix: 011
DialStringRules: etc/dialrules
ServerTracing: 1
SessionTracing: 11
RecvFileMode: 0660
LogFileMode: 0600
DeviceMode: 0600
RingsBeforeAnswer: 1
SpeakerVolume: off
GettyArgs: "-h %l dx_%s"
LocalIdentifier: "OC9 Technologies"
TagLineFont: etc/lutRS18.pcf
TagLineFormat: "From %%l|%c|Page %%P of %%T"
MaxRecvPages: 175

#
#
# Modem-related stuff: should reflect modem command interface
# and hardware connection/cabling (e.g. flow control).
#
ModemType: Class1 # use this to supply a hint

#
# Enabling this will use the hfaxd-protocol to set Caller*ID
#
#ModemSetOriginCmd: AT+VSID="%s","%d"

#
# If "glare" during initialization becomes a problem then take
# the modem off-hook during initialization, and then place it
# back on-hook when done.
#
#ModemResetCmds: "ATH1\nAT+VCID=1" # enables CallID display
#ModemReadyCmds: ATH0

Class1AdaptRecvCmd: AT+FAR=1
Class1TMConnectDelay: 400 # counteract quick CONNECT response

#
# If you have trouble with V.17 receiving or sending,
# you may want to enable one of these, respectively.
#
Class1RMQueryCmd: "!24,48,72,96" # enable this to disable V.17 receiving
Class1TMQueryCmd: "!24,48,72,96" # enable this to disable V.17 sending

#
# You'll likely want Caller*ID display (also displays DID) enabled.
#
ModemResetCmds: AT+VCID=1 # enables CallID display

#
# The pty does not support changing parity.
#
PagerTTYParity: none

#
# If you are "missing" Caller*ID data on some calls (but not all)
# and if you do not have adequate glare protection you may want to
# not answer based on RINGs, but rather enable the CallIDAnswerLength
# for NDID, disable AT+VCID=1 and do this:
#
#RingsBeforeAnswer: 0
#ModemRingResponse: AT+VRID=1

# Uncomment DATE and TIME if you really want them, but you probably don't.
#CallIDPattern: "DATE="
#CallIDPattern: "TIME="
CallIDPattern: "NMBR="
CallIDPattern: "NAME="
CallIDPattern: "ANID="
#CallIDPattern: "USER=" # username provided by call
#CallIDPattern: "PASS=" # password provided by call
#CallIDPattern: "CDID=" # DID context in call
CallIDPattern: "NDID="
#CallIDAnswerLength: 4

We now need to fork the usual Hylafax faxgetty to listen for incoming fax :

in rc.local :

/usr/local/sbin/faxgetty tty125 &

/usr/local/sbin/faxgetty tty126 &

as well as the usal daemons, see HylaFax documentation if you are interested in using it.

in rc.local :

/usr/local/sbin/hfaxd
/usr/local/sbin/faxq

Add-on

View this free package: AvantFax. It allows you to let your users access fax functionality from a web browser. Some have used this package along with what is described in this article to set up pools of over 2000 iaxmodems and they have got so to speak in the fax sending/receiving outsourcing business.

Commentaires / Comments (23)
forward call to 125 extension
1 vendredi, 07 décembre 2007 05:14
spooky
How can I perform fax detection and forward to extension 125 in asterisk 1,4 ? (No FreePBX)
Re: forward call to 125 extension
2 jeudi, 13 décembre 2007 23:37
ls
Hi,

Note that 125 is just a random extension number we picked up for our examples, it can be any extension number.

You can do the same in Asterisk 1.4 without FreePBX by manually editing your extension.conf file. Just follow the instructions in the article and edit your extension.conf manually instead of editing the extension settings in FreePBX.

Here are the lines required to detect a FAX or send to an IVR in the incoming section of extention.conf :
...
...
exten => s,n,Set(FAX_RX=125)
exten => s,n,Answer
exten => s,n,Playtones(ring)
exten => s,n,NVFaxDetect(5)
exten => s,n,Goto(ivr-2,s,1)
...

Just replace the lines in your configuration file that sends to the IVR with the above lines in order to first detect fax tones and reload Asterisk so it re-read its config files.
tiff isues
3 jeudi, 31 janvier 2008 10:21
spooky
I have managed to install hylafax.When a fax comes my asterisk forward the call to iaxmodem.Iaxmodem to hylafax . But when I try to see the fax,which is in tiff format,through webmin then I receive an error , That the file format is not supported or Image something is not installed on my machine . What may be the problem ?
Re: tiff issue
4 vendredi, 01 février 2008 00:34
oc9
Hi,

If you got so far, it means you have successfully configured asterisk, iaxmodem and hylafax. Congratulations! ;-)

As you may already understand, the tiff issue is not related to the fax setup.

To be able to view faxes from webmin you should.

1) Make sure the tiff mime type is defined in your apache configuration, in your apache folder, in conf/mime.types, you should have a line with :

image/tiff tiff tif

2) You will need a program that supports displaying multi-page tiff images.

Do a search for "linux fax viewer" to find a program that displays multi-page tiff files correctly.

On my linux desktop, I use :

kfax (KDE fax viewer)

To have mozilla open the tiff file automatically when you click on it, you will need to define you fax viewer program (i.e. kfax) to handle tiff files in mozilla or in your system settings.

Alternatively, you can download the file to your local drive and use the tiff2ps or tiff2pdf utilities (to transform it either to a .ps or .pdf file.

Same principle applies on windows, on windows, my XP install came with a utility named "Windows image and faxes preview" and that's what I use to read/print faxes (e.g. tiff files).
Asterisk & Fax over SIP Channels
5 jeudi, 14 février 2008 15:49
Amit
Hi
i read your post on Asterisk list. last 3 months i am trying to set Asterisk Fax to email
on SIP, but i have no success when i try with Spandsp..
so do you have any idea how we can make this if we are using SIP-VOIP with
Asterisk.Otherwise help me to do this with any other software taht u check it.only need is that that work
with SIP-VOIP Asterisk.(SIP Channel).
plz provide me link or config deatils if you have so i can try this with my Asterisk
Asterisk version 1.4.9
on dell server with RHEL OS
using SIP Channel type.

i am waiting for ur reply

Regards
Amit
RE: Asterisk & Fax over SIP Channels
6 jeudi, 14 février 2008 15:51
Alain Côté
1) We try that too but we couldn't get it to work well. That's why we recommend using iaxmodem. Iaxmodem comes with its own spandsp libraries.

2) So asterisk knows nothing about spandsp, asterisk just forwards the call to iaxmodem which takes care of decoding the fax. We leave asterisk alone and handle the faxes with iaxmodem. Don't use spandsp within asterisk.

3) Since you tell asterisk to forward the call to iaxmodem in inbound routes, (or in extensions if you wish) it does not matter if the call comes in through a SIP trunk or an IAX trunk. We have calls coming in through SIP and IAX trunks and faxes are forwarded to the iaxmodem.

4) Hylafax is a very stable and powerful fax handling software, it does fax to email since at least 15 years ;-)

SIP trunk --> asterisk --> iaxmodem --> hylafax --> email So the instructions in the article will work with a SIP trunk too ;-)

Cheers,
creating fax dialplan in asterisk
7 jeudi, 06 mars 2008 12:25
Iqbal
Thanks for your tutorial. But i don't know how to create dial plan for my fax machine.So my asterisk know to send fax to the fax machine

Here my configuration

Hylafax+iaxmodem+trixbox2.4.xCisco router ios 13(FXO)Switching Center(PSTN Central)My fax machine(fax number 6211)
Could you give me example help to create dialplan in extension.conf for fax number in this case 6211 base on the configuration above.Thanks sorry for my English...
Re: creating fax dialplan in asterisk
8 dimanche, 16 mars 2008 23:36
oc9
Here are the lines required to detect a FAX or send to an IVR in the incoming section of extention.conf :
...
...
exten => s,n,Set(FAX_RX=125)
exten => s,n,Answer
exten => s,n,Playtones(ring)
exten => s,n,NVFaxDetect(5)
exten => s,n,Goto(ivr-2,s,1)
...

Just replace the lines in your configuration file that sends to the IVR with the above lines in order to first detect fax tones and reload Asterisk so it re-read its config files.

If you share voice and fax, you need to use NVFaxDetect which catch the fax call at the IVR level and automagically forwards it to the fax extension. If you have a dedicated number for your fax, just forward all calls to the fax extension like you would normally do for a phone extension with a dedicated number.

If you use FreePBX just configure the fax handling in your Inbound Routes :
Fax Extension: 6211
Fax Email: (leave blank)
Fax Detection Type: NVFax
Pause After Answer: 5
Faxing
9 vendredi, 11 avril 2008 11:22
Keith
Great read on your article, but there is a lot of misinformation on the subject.

1. Faxing over VoIP is not dependant on the carrier. Network jitter is what causes a fax to fail when sending/receiving faxes over SIP. The only reason you may get better results with one provider is because your connection to them, at this moment, may be good. However, this will eventually change at some point and your faxing will decrease to 50%-70% success rate.

2. IAX modem is slow (14.4k), but really only achieves 9.6k. This is something that will never change. Traditional lines are 33.6k. Hence, your 20 page document will take 5 times as long to send/receive.

3. Why are you trying to have Asterisk send the email? HylaFAX should be in charge of all fax functions including sending the pdf to email.

Guys, you will never be able to "beat" the system for faxing. If you want reliable faxing, stick with the PSTN.
Re: Faxing
10 dimanche, 13 avril 2008 03:06
Alain Côté
Great read on your article, but there is a lot of misinformation on the subject.

---> Thanks !

1. Faxing over VoIP is not dependant on the carrier. Network jitter is what causes a fax to fail when sending/receiving faxes over SIP. The only reason you may get better results with one provider is because your connection to them, at this moment, may be good. However, this will eventually change at some point and your faxing will decrease to 50%-70% success rate.

----> I agree, but this is the same as your "good" carrier becoming a bad "carrier" or your "good" internet connectivity becoming "bad". It is therefore dependent on your carrier and your internet connectivity, which is pretty much what we have said in the article ;-)

2. IAX modem is slow (14.4k), but really only achieves 9.6k. This is something that will never change. Traditional lines are 33.6k. Hence, your 20 page document will take 5 times as long to send/receive.

----> Very good point ! This should definitely have been noted in the article !

3. Why are you trying to have Asterisk send the email? HylaFAX should be in charge of all fax functions including sending the pdf to email.

-----> I don't know where this is from, we recommend delegating everything to Hylafax just as you do.

Guys, you will never be able to "beat" the system for faxing. If you want reliable faxing, stick with the PSTN.

------> Agreed, if you run a mission critical fax operation that needs maximum reliability. But this is changing slowly as networks get better. Who would have thought that VOIP could be possible in the early ages of Internet (say in 1980, when I got my first access to it)?. Also, do not forget that Internet2 (Also called The Grid) is coming ;-)

-------> Also, note that the article states that the suggested setup is also valid if you use PSTN lines ONLY with Asterisk as your PBX, it lets you share your fax lines with voice, all handled by Asterisk, with only PSTN lines and VOIP used internally only.

asterisk pstn faxing
11 dimanche, 11 mai 2008 05:10
dave
hi there i have a tdm24xxp(fxo) port is it possible to route faxes to hylafax from asterisk + do you need to route your incoming calls to the iaxmodem, or can you route the calls strait from fxo to hylafax using asterisk?

any help welcome
Re: asterisk pstn faxing
12 lundi, 19 mai 2008 20:03
oc9
Yes shou;ld be able to do that as long as you use ulaw between your asterisk and the tdm24xxp(fxo) and that it supports fax passtrough. You will also need to use a hardware modem on the hylafax server. This type of config is very similar to having hylafax hooked to a hardware modem that is turn hooked to a PSTN line. So asterisk routing prior to the fax call hitting the hardware modem on the hylafax server will be transparent.

Also, you wouldn't be limited by the relatively slow speed of iaxmodem, as a another user has rightly noted 2 messages ago.
Sending fax
13 mercredi, 16 juillet 2008 23:42
Juvs
Hi, nice tutorial, but I didn't see an example to send an fax using hylafax and asterisk, we have some PSTN lines connected to asterisk and we want to sent faxes using this lines.
Need to setup this only for outgoing faxes...
14 jeudi, 31 juillet 2008 13:02
Capt Nemo
Hi there,

great article, I wana setup this for only outgoing faxes, i-e, I only need to send faxes. Is it possible. Do I still need any extra hardware for this?

thanks for your help in advance!!!

cheers!
Nemo.
Re: Sending fax
15 lundi, 04 août 2008 20:29
oc9
Just follow standard hylafax procedure to send a fax. Remember that hylafax sees your IAXmodem as any other modem. The fact that you use iax modem/asterisk is completely transparent to hylafax. Hylafax doesn't know anything about asterisk and iaxmodem, hylafax doesn't even know they exist!

That's the reason why we like this approach despite the limitations of iaxmodem, everything is nicely layered in indepandant layers.

To send a fax, we just use the following command triggered from our custom web interface, just have a look at AvantFax (link in the article) if you want to install a turn key solution :

command to send fax with hylafax:

/usr/local/bin/sendfax -x "Destination company" -r "Subject of the fax" -c "Comment for recipient" -D -h localhost:9008 -d "Recipient Name"@1555555121 2 file.pdf
Re: Need to setup this only for outgoing faxes...
16 lundi, 04 août 2008 20:36
oc9
The setup described in this article works equally well to send faxes, please have a look at above reply (Re: Sending fax) which pretty much answer your question.

Additionally, remember that this setup works with totally independent layers so any solution that works with hylafax to send faxes will work with this setup.

Hylafax exists since more than 15 years so many very mature solutions to send faxes with hylafax are available. Again, that's why we choose that solution, to completely abstract asterisk and VOIP out of the picture.
Which provider you have tested is suited best?
17 samedi, 07 mars 2009 17:49
ingo
We also have tested two dozen providers. So far gafachi stands out. What is your best choice?
I can't receive fax
18 lundi, 09 mars 2009 06:49
faty
Hi:
How can I see the communication between hylafax and iaxmodem and the console of them?I only can see the console of asterisk.It shows: 'IAX2/iaxmodem-2 is ringing' when I dial the fax number.
and nothing else.I can't receive fax.
I installed asterisk 1.4.18 and iaxmodem-1.2.0 and
hylafax-5.2.9-1.fc9.i386.rpm and these are my main configurations:
extensions.conf:
[from-pstn]
exten => 9711315,1,Answer
exten => 9711315,2,Dial(IAX2/iaxmodem)
iax.conf:
[iaxmodem]
type=friend
secret=password
port=4570
host=dynamic
context=from-pstn
disallow=all
allow=alaw

/etc/iaxmodem/ttyIAX0
device /dev/ttyIAX0
owner uucp:uucp
mode 660
port 4570
refresh 50
server 127.0.0.1
peername iaxmodem
secret password
codec alaw
and this is my modem type in /var/spool/hylafax/etc/config.tty
ModemType: Class1
/etc/inittab:
id:5:initdefault:
IA00:23:respawn:/usr/bin/iaxmodem
ttyIAX0
IA00:23:respawn:/usr/bin/iaxmodem
ttyIAX0
mo00:23:respawn:/usr/sbin/faxgetty ttyIAX0

I started hylafax and run iaxmodem.
I see below lines when I run faxstat:
HylaFAX scheduler on localhost.localdomain: Running
Modem ttyIAX0 (9711315): Waiting for modem to come ready

I'd appreciate any help,idea.
~
Re: Which provider you have tested is suited best?
19 lundi, 09 mars 2009 22:45
oc9
Hello,

Well there is no big secret, we use a local provider a few hops away from us that is directly hooked to the Telco via T1 links. The provider is 15ms away from us.

International providers where the call is routed to (or received from) out of the country networks have less chances to succeed in a steady way. There is more spots on the network where weakness may cause the call to fail and you often do not know how the call is routed once it gets to the provider.

To get maximum reliability, we use a local provider and we know how our call is routed once it gets to that provider. Straight to the Telco with T1 links ;-)

We do not use any of our other 4 providers for faxes for the reasons stated above. We use g729 on those trunks anyway which is not best suited for faxes.
Re: I can't receive fax
20 lundi, 09 mars 2009 22:52
oc9
Hi,

It looks like you do have faxgetty running, to test that hylafax communicates with the modem, use the following command:

$ ps axw | grep faxgetty
14871 pts/9 S 0:00 /sbin/faxgetty -q /var/spool/hylafax-2 tty882991110992
14872 pts/9 S 0:00 /sbin/faxgetty ttyIAX
14873 pts/9 S 0:00 /sbin/faxgetty acts1

faxgetty does the communication between hylafax and iaxmodem
Re:I can't receive fax
21 mardi, 10 mars 2009 07:45
faty
Hi:
thank you for reply.
after running : ps axw | grep faxgetty
I saw :
7687 pts/9 S+ 0:00 grep faxgetty
Is it problem?
Re: I can't receive fax
22 mardi, 10 mars 2009 07:47
faty
Hi:
thank you for reply.
after running : ps axw | grep faxgetty
I saw :
7687 pts/9 S+ 0:00 grep faxgetty
Is it problem?
Re: I can't receive fax
23 mardi, 10 mars 2009 17:42
oc9
Yes it is a problem, ps returned you the pid of the grep command you were currently running (pid=7687) ( pid= process ID ) this is the pid of the grep process created by the command you just typed.

But ps show that you DO NOT have faxgetty running hence hylafax can't receive faxes. To see that you have a faxgetty process running, you must have a faxgetty process showing up when you issue the command ps axw | grep faxgetty.

The process name will start with the name faxgetty as the examples show in previous posts. The name of the process will be faxgetty, not grep:

$ ps axw | grep faxgetty
14872 pts/9 S 0:00 /sbin/faxgetty ttyIAX

You may also use pidof faxgetty which will only return pids of faxgetty processes :

/sbin/pidof faxgetty
14872

See how we start faxgetty in our article, we just put the following command in /etc/rc.d/rc.local, you may also test it from the command line and it should just work :

/usr/local/sbin/faxgetty tty125 &

You can also use the following command to list all processes on your computer:

$top -b -n 1

source:
http://blogtech.oc9.com/index.php?option=com_content&view=article&catid=4:asterisk&id=77:20071121ast&Itemid=6

Build an In-Car PC

2009-08-20T12:07:00.000-07:00

peripherals.

On the flip side, here are a few limitations on the technology which you should consider before implementing a mini-ITX solution:

* Not Upgradeable: To reduce the cost of manufacture, CPUs are permanently installed on the mainboard. The ZIF (Zero Insertion Force) socket on most modern motherboards makes up a significant part of the manufacture cost. In VIA's EPIA (Embedded Platform Innovative Architecture) architecture, the company integrated the mainboard and CPU and removed the socket to streamline production and reduce costs.
* Limited Expandability: Typical cases have limited real estate—that's the cost of going "small." Power supplies can be as small as 60 watts, limiting the addition of peripherals. Also, these boards have minimal PCI slots available.
* Higher Cost: The cost for an integrated mini-ITX mainboard is likely to be higher than a comparable ATX motherboard/CPU bundle.

While there are certainly some cons to going with mini-ITX, I believe the technology is sound. That's why I recommend it as the virtual heart of this build.

Car PC Benefits

The public's attitude about what belongs in a car, coupled with technological advances that have made components like displays more compact and robust, have transformed cars and SUVs into rolling infotainment centers. Not long ago, a video display in a car would turn heads; today, it's commonplace. Global positioning systems (GPS) that were once deployed exclusively by the military now listen for bleeps from space from consumer dashboards. DVD players, surround sound, and video displays have all become popular selling features for auto makers. Add to that the high-end options: satellite radio, Bluetooth connectivity, rear-view cameras, vehicle diagnostics and sensor monitoring, Wi-Fi, smart alarm systems, and more. As a result, consumers seek new possibilities for their mobile computing needs.

Car dealers and makers of satellite radio, GPS and media players are targeting a growing consumer market with individual infotainment products. But a well-built car PC can run all of these and more. It can also help consumers with route planning, Web browsing, personal scheduling, gaming, and general computing.

System builders should consider consumers to be just part of whom you should pitch for offering a road PC. There are also hardcore mobile computing applications you could offer, such as digital video recording for police vehicles with broadband connectivity. Also, consider inventory and transportation tracking systems for trucking and delivery companies that provide businesses the advantage of being able to pinpoint where their products and materials anytime anywhere.

Let's take a look at some approaches to getting a PC on the road and choosing the right components. Then I'll show you how to put it all together.

Why Not Go With a Notebook?

In-car PC components are similar to those for notebook and desktop systems—power supplies, CPU, hard disk, etc.—but they need to meet much more rugged specifications. The operating environment in a car is vastly different from an office desktop. Notebooks, while closer in size and ruggedness, are still best for home or office use.

Can you simply mount a notebook or desktop and use it in a car? Sure, and many installers have done just that. But there are serious drawbacks. Desperate installers have mounted flimsy desktop cases in the trunk; used inefficient power inverters to supply power; and even have built elaborate trays for input devices. But size, cable runs and cooling requirements make the desktop approach cumbersome to install and unappealing to operate.

Where standard desktop boxes are awkward for the road, notebooks are a better fit. But their power supplies are not specifically built to handle the special demands of the starts and stops of an average vehicle. As a result, an unmodified notebook cannot be counted on for reliable in-car service.

In addition, both traditional desktops and notebooks are plagued with overheating problems and unexpected reboot issues. Inopportune reboots can occur as power fluctuates in a system designed more to provide power for a car's lights, wiper motors and fans than the smooth, constant voltage required for typical computing.
Car PC's Require Special Components

A reliable in-car PC needs to use small yet rugged components whose size and shape allow proper placement, whether on a crowded dashboard, in or under a dashboard, or under the car's seats. The PC needs to be out of the way of the car's critical instruments.

A car PC must also be designed to be a real workhorse. It will need to handle heat and cold, exposure to sunlight, rapid changes in temperature and humidity, along with shocks and vibrations from the road. The system must also survive as an add-on to a power system that is frequently switched off, often for long periods, and that is prone to deep cycle discharging.

Automotive electrical systems—unlike the clean, steady household current from a wall receptacle—operate off a DC (direct current) storage system that is constantly changing. First, it discharges to deliver power to 'turn-over' a cold car engine. Then it charges the battery back to capacity as the car is driven. Car PCs must operate from power fully conditioned to remove the risk of low voltage during cranking and carefully regulated to prevent damage to PC components during charging.

In summary, an in-car PC must work consistently and meet the challenges of in-vehicle operability. It must be able to take a beating, have short boot times, offer power-saving features, and run its applications easily and safely accessible. The system must be mountable where it is easily visible but doesn't block the driver's line of vision or the path of airbags. The system also must be fastened securely so it won't come lose in a minor accident.

To meet all these challenging requirements, you'll need to choose the right components. In the next section, we'll look at your best choices for parts and how to source them.

Getting the Right Parts for a Car PC

Finding the right parts for your car PC is all about heat, power, vibration/shock, and operability. Let's take these in order:

Heat: Large power requirements and heat dissipation don't mix well with the confined space of a car. As a result, traditional desktops are difficult to keep cool in a car. Notebooks require less cooling, but mini-ITX boxes are even better. They're also easier to tuck into tight spaces. At just 17 cm. x 17 cm., a mini-ITX can fit into or below a dashboard, or even in a glove compartment. Special enclosures, like the VoomPC case, allow for optimal cooling and shock resistance while keeping a compact footprint; I'll discuss this at greater length later in the Recipe.

Power: This is the most challenging obstacle to computing on the road. Specifically, how do you supply clean power as needed? And how do you not drain a car system's battery when the car is unattended for long periods? Inefficient power inverters can covert the 12-volt DC typically used in car electronics into the 120-volt AC (alternating current) source required for a standard PC power supply. But there are a number of drawbacks. Most notably, inverters don't "know" when the car ignition is being turned off, so PCs won't shut down properly and will constantly be restarting on short trips. While notebooks use less power and can operate without an inverter (since they operate from battery power already), they can drain car batteries if left on or in 'hibernation mode' over long periods.

An excellent solution is a new breed of power supply that can make decisions about how to supply power and even signal a PC to 'hibernate' or 'shut-down' when warranted. It's called a DC-to-DC converter, and it can covert a car's 12-volt source into the 3.3-volt, 5-volt, and 1-volt outputs that computers can use. I especially like the M2-ATX. It allows for a user-selectable timer that lets the PC to remain on for a certain amount of time after the car is shut off before issuing a command to the computer to go to 'sleep.' Then, after a prolonged period of sleep, the power supply protects the car's battery by issuing a full shutdown command to the PC.

Vibration and shock: Components in a car PC are subject to all the same jarring, bumping and G-forces as passengers are. If all users drove luxury cars on traffic-free, freshly paved highways, then vibration and shock would be a non-issue. But in the real world, potholes, debris, curbs, and sudden stops and starts can all cause serious trouble for an in-car PC. As a result, hardware mounting, cable stress and wear, and choice of hard disk need to address the situation.

The PC's hard disk is the only constantly moving part, making it the one most sensitive to road shock and vibration. Fortunately, most of today's 2.5-inch notebook drives are designed to take a reasonable amount of abuse from motion, and most are suitable for all but the most rugged applications. I recommend the Seagate Momentus 7200.1, which has been rigorously tested for use in many mobile and notebook applications. For situations where you know your car PC will be heavily stressed, Seagate's EE-25 series drives are hardened specifically for automotive applications; they should hold up better in challenging applications.

Operability: Car PC users need to get to their applications fast and with a minimum of interaction. So keyboards and mice, while handy for occasional work in the car, are of limited use in a car. Instead, car PCs should rely on touch screens and software interfaces with "skins" that let users access their apps quickly and safely.

In car lingo, a touch screen works like a "head unit," providing access to music selection or a GPS. A major goal of a car PC is to replace the vehicle's head unit with a touch screen that will act as GPS, CD player, radio and the like.

Skins used with voice-recognition software can also provide safe and a mostly hands-free method of working with applications. Applications like RoadRunner and SKINbedder work with NaviVoice voice recognition to provide quick access to applications with a minimum of driver involvement. In the screenshot below, you can see how NaviVoice helps to integrate voice activated GPS with media playing and other applications, making GPS functions available quickly and safely with a one-word command:

With applications like Mobile Media Center, users can develop their own "skins" to access media and other car applications by touch. Here's an example:

Ingredients

Here are the components you'll need to create a car PC:

CarPC Parts List

Power Supply:

M2-AXT(160-watt)

- ATX, 6-24V wide input range

- Intelligent shutdown controller

- ON/OFF motherboard control

- Survives vehicle engine cranks

- Battery deep discharge prevention

- High efficiency, 160-watts output

- "Anti-thump" amplifier remote control

- 15A automotive fuse (mini-blade)

- VIA, P4 and AMD (NYSE:AMD) CPU support

$90.
Enclosure: VoomPC

- Rugged enclosure, easy to handle and mount

- 5.5mm aluminum extrusion

- Compatible with any mini-ITX board

- 210mm (W) x 254mm (L) x 56mm (H)

- Up to three fans for moist/heat removal
$80
Mainboard VIA SP130000

- VIA C3 EBGA processor

- 1 DDR266/333/400 DIMM socket

- UniChromePro AGP graphics/MPEG-2 decoder/MPEG-4 Accelerator

- 1 PCI

- 2 X UltraDMA 133/100 connector

- VIA VT6103 10/100 Base-T Ethernet PHY

- VIA VT1617A 6-channel AC' 97 codec

- VIA VT1623 TV encoder

- VIA VT6307S IEEE 1394 Firewire
$200.
Touchscreen Monitor (Two options)
Motorized VMI70 7-inch TFT-LCD monitor with touch panel

7-inch fully motorized in-dash TFT-LCD monitor touch screen VGA and TV

- 16:9 TFT-LCD car PC monitor

- Resolution: 800 x 480

- VGA support: 640 x 480 to 1280 x 768

- Video Input: AV1/AV2

- Audio output: Single audio output

- Standard PAL/NTSC TV signal reception

- Double-channel video input

- Includes remote control

- Chromatic system: PAL/NTSC (auto switch)

- Input: Double-channel AV/TV input, 1 VGA input

- One year warranty
$400
Non-Motorized VM7000 7-inch TFT LCD touchscreen for car PC

- Mount type: Dashboard or Headrest

- PAL/NTSC

- Resolution 720 x 400 to 1280 x 1024

- 16:9 aspect ratio

- Video input: XGA/VGA input (15 pin D-SUB), USB or RS232 interface

- Two RCA video inputs, one audio input

- Built-in speaker

- Display brightness (with touchscreen): 280cd/ m²

- Power consumption: < 9W

- Includes: Remote control, USB cable, VGA cable, AV cable, dashboard mounting bracket, headrest mounting bracket and screws, stylus, CD with touch screen drivers, operation manual

- One-year warranty
$215.
Hard Disk (Two options)
7200 RPM Seagate Momentus 7200 ST910021A

-Reliable 100 GB ATA

-Fast-booting with average seek-time of 10.5 msec.

-Low-power consumption for maximum battery life

-Whisper-quiet load/unload acoustics

-Operating shock of 250Gs (to withstand rugged environments)
$220.
5400 RPM Mobile Seagate EE25 5400RPM

-60GB designed for automotive entertainment and GPS systems

- Hardened for mobile computing and other extreme environments

- Tested for 24x7 operation at elevated temperatures

- In use for mission-critical military field applications
$145.
Memory Kingston KVR400X64C3A/512 (512-MB, 400-MHz DDR DIMM). This is reliable, affordable memory. $54.

The following photo is a shot of the main components: VoomPC case, Seagate hard drive, and M2-ATX power supply board for our Car PC. It also shows a Star monitor I used to check the mainboard before permanent installation of a touch screen:

Vertical mounting of the hard drives, rather than horizontal mounting, can minimize trouble from hard impacts and minimize "head crash" situations. If you know a drive will be getting serious abuse, choose a location for the enclosures that provide sufficient air flow and keep the disks perpendicular to the road.

Assembling the Car PC

Before assembly, and before making final decisions on parts, make sure you have a solid plan and a proper place to work. Finding the right place to work on your car PC will make for a cleaner installation and speed your project along. Look for a protected location with good lighting. You'll also want to use a droplight to help you with interior fitting and for working under the hood. Don't forget Internet access for downloading applications, updates, etc. While garages with a high-speed hook-up might be hard to come by, you'll only need network access for a short period. So be prepared to string a long cable, or use a USB wireless-network adaptor.

No special tools are needed to build and install a Car PC. You can go with the favorite tools of professional installers, such as good wire strippers with spring action and wire-gauge sensing; a heavy-duty crimping tool; a thread-locker compound such as LocTite, which can prevent screws from coming loose from repeated vibration; and a collection of faston and other wire-splicing parts. Wire connectors are available in various assortments or in bubble packs from auto-supply stores, and they are highly recommended for a safe and professional-looking installation.

Here are the 14 steps for the Car PC assembly:

CarPC Assembly Steps

1

Install memory and configure VIA mainboard ___
2 Install the motherboard on the base plate of enclosure using four screws.

See illustration of parts layout above.

___
3 Install the 2.5-inch hard drive using the four silicone rubber shock absorbent pads over the hard drive mounting holes. Fasten the hard drive using four undercut M3 screws attached from the bottom. (See illustration of parts layout, above). Shock pads for mounting the hard drive are included with the VoomPC enclosure ___
4 Attach a 44-40 pin IDE cable to the hard drive and motherboard. ___
5 Attach the M2 ATX power supply over the hard drive, using the remaining standoffs. See illustration of parts layout above. ___
6 Connect the ATX cable harness (provided with power supply) to the motherboard. Use small tie-wraps to manage the ATX cable harness. This is important, not only to prevent rattle and cable wear, but to improve air-flow critical for proper cooling. Note: If you are using a different VIA mainboard, you may be able to eliminate the ATX cable harness entirely, by a custom ATX power extender bus made for use with some EPIA MII mainboards (available from http://www.mini-box.com ) ___
7 Connect the Red / Black / White (terminated in faston quick-splice connectors) to the power supply. Red is un-switched battery, white is switched battery (ignition) and Black is GND. When looking for a power connection in, remember that the switched battery (ignition) is usually present on your cigarette lighter or most of your 12-volt power wires. Un-switched battery (harder to find) is present on your alarm system or other 'always-on' electronics. Use a volt-meter to detect switched versus un-switched wires. If hard to find, connect directly to the battery. ___
8 Connect the LED wire to the LED output if you're the M2-ATX for LED pins. ___
9 Connect the ON/OFF wire harness (provided in the PSU package) to the M2-ATX ON/OFF controller and to the ON/OFF mainboard switch. ___
10 (Optional) Attach your audio amp See details in VoomPC enclosure manual to connect the Amp Enable wire harness to your amp. Please pay special attention to the polarity of the wires. Note: Your amplifier remote control unit actually needs only one wire (RMT), GND is optional. ___
11 Hook up display, keyboard, etc, and perform a quick test of your system by turning ignition ON ___
12 Attach temporary CD-ROM drive to load operating system and application software. ___
13 Secure the enclosure in the vehicle using the four front/back mounting screws. If you don't want to drill holes into your car chassis, large velcro pads work well when attached to the bottom plate of the enclosure. Use the "hook" side of the velcro pad on the PC to attach to your car's carpet. This works very well in most interiors. ___
14 Locate and mount touch screen. For many applications, this can represent a bulk of the work and require patience. Work slowly and carefully knowing that a slip of the Exacto knife or spilling adhesive will mean a trip to scrap yard or a costly trip to the dealer's parts department to fix. ___

Here's a photograph showing how the components are placed for assembly onto the bottom plate of a VoomPC case. Note the overlapping strata of parts to retain our small footprint:

A Word about Car PC and Safety

Using a PC on the road requires a tremendous amount of responsibility. The purpose of having a car PC—in addition to being really cool, of course—is to add to the enjoyment and safety of the driving experience. Unfortunately, having something as wonderful and complex as a computer within sight and reach of a driver can present a serious distraction.

In other words, don't make your in-car PC a driving hazard for yourself or your clients. Instead, follow these important steps as part of your installation:

* Consult your local laws. In the U.S., for example, many states restrict the use of an in-car video monitor that's in the view of the driver.
* Take extra care to provide a safe installation. Design application access to be as easy and hands-free as possible.
* Consider having a serious talk with your clients about the safe use of the car PC. Since everyone will have questions and want to talk about their car PC, suggest an explanation before the trip gets underway. Or suggest offering to pull over to give a complete tour of the hardware and applications curbside, rather than while in motion.

Once the Car PC is built and installed, you'll be ready to load the applications your client desires. But be prepared for questions, lots of them. Car PCs get loads of attention from both potential clients and passers-by. Don't forget to mention to your potential clients that having a Car PC consolidates all their miscellaneous hardware and wires into one box with a large, easy-to-use touch screen. It also lets them run their favorite PC applications in their car. PC gamers will love it for the novelty. Salespeople will love the GPS and the integrated phone and PC applications. And all your on-the-road clients will enjoy the superior media ability of motoring in style with their car PC.

SIDEBAR: Additional Resources for Building Car PCs

Online Vendors: You'll want to source your parts from people who are familiar with the mini-ITX and know the car PC business. I found these three online vendors to be among the best:

* Mini-Box
* MP3Car
* Digital Worldwide

Discussion Forums: Check out the many car-PC sites forums for tips and tricks. Here are three I like:

* Car PC Specialist
* MP3Car.Com
* CarTFT

Books: I recommend two helpful books devoted to car PCs. These two books can be especially helpful if you don't have a lot of experience with 12-volt DC systems, are unfamiliar with "faston" connectors for splicing wire quickly, or are uncomfortable cutting into ignition wiring:

* Geek My Ride by Auri Rahimzadeh (Wiley, 2005)
* Car PC Hacks by Damien Stolarz (O'Reilly, 2005)

Additional ideas: Have a look at some pre-built car PCs. Streetdeck is one that has attracted a lot of attention.

General information on mini-ITX systems: Check out the EPIACenter.

ANDY MCDONOUGH is a professional musician, composer, voice actor, engineer, and educator happily freelancing in New Jersey.

Vyatta Wireless 3G USB card setup

2009-08-09T16:20:00.000-07:00

Wireless 3G USB card setup

The 3G USB wireless modem implementation has been verified against a Sierra Wireless USB Connect 881 modem on the ATT network and a UT Starcom (Pantech) 3G modem on the Verizon network, Tmobile.

config tree:
Code:

interfaces {
wirelessmodem {
backup;
device ;
mtu <1-1500>;
network ;
no-dns;
}
}

Wirelessmodem devices are numbered ppp0-ppp999. The device will not show up in show interfaces until it is configured. The 3g drivers don't create a network interface until pppd is running.

backup: If this node is set, a default route to the upstream provider will be installed in the routing table as a backup default route (metric 10). In this use case, the modem will only be used if the primary route fails.

device: specify the system device for the modem. The default is ttyUSB0. 3g modems for the most part use either ttyUSBx or ttyACMx. Example configs are provided below for reference.

mtu: set the maximum transmission unit for this link

network: this parameter is used to define the chat script for a given network. This chat script is the sequence of AT commands sent to the modem. Chat scripts are provided for att and verizon. Those scripts may work on other networks. The verizon one may work for sprint for example. If a user has a network that doesn't work with one of the pre-existing chat scripts, they can add a custom one by putting the script in a file in /opt/vyatta/share/ppp/network/. The cli will automatically recognize it as a valid configuration option.

no-dns: do not add the provider's DNS hosts to the local name resolution path.

New operational mode commands:
show interfaces wirelessmodem (ppp0): show the layer 3 stats for wirelessmodem interface ppp0
show interfaces wirelessmodem (ppp0) stats: show the ppp stats for wirelessmodem interface ppp0
show interfaces wirelessmodem (ppp0) debug: show the debug startup log wirelessmodem interface ppp0
clear interfaces wirelessmodem (ppp0) session: reset the ppp session

Configuration samples:
ATT Sierra Wireless:

set interfaces wirelessmodem ppp0
commit

Verizon UT Starcom:

set interfaces wirelessmodem ppp0 network verizon
set interfaces wirelessmodem ppp0 device ttyACM0
commit

The usb id for the card I have is 1199:6880, which doesn't work out of the box.

Code:

sat1-wf:~# show system usb
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 005: ID 10d5:55a4 Uni Class Technology Co., Ltd
Bus 003 Device 004: ID 413c:3010 Dell Computer Corp. Optical Wheel Mouse
Bus 003 Device 003: ID 413c:2105 Dell Computer Corp. Model L100 Keyboard
Bus 003 Device 002: ID 058f:9254 Alcor Micro Corp. Hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 1199:6880 Sierra Wireless, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Notice that the Sierra Wireless chip is found, but a quick check of the logs shows this
Code:

May 18 14:53:29 sat1-wf pppd[4145]: In file /etc/ppp/peers/wlm0: unrecognized option '/dev/ttyUSB0'

looking in /dev, sure enough there is no ttyUSB0. The problem is that the usb_serial module doesn't recognize the usb id of this card, but that's an easy fix.

First unload the sierra module, then the usb_serial module. Then load the usb_serial module and tell it to recognize the sierra card. Reload the sierra module and you're done. For those of you who are not clear on exactly how to do that:

Code:

modprobe -r usb_serial
modprobe -r sierra
modprobe usb_serial vendor=0x1199 product=0x6880
modprobe sierra

Now to make it persistent across reboots, edit /etc/modules and add:
usb_serial vendor=0x1199 product=0x6880

Now there is just one more problem. After all of that, a quick check of the /dev directory shows 4 ttyUSBX devices. Vyatta uses ttyUSB0 by default, but the one we want is ttyUSB4. So change your config to something like this:

Code:

wlm0 {
device ttyUSB4
network att
}

or

All you have to do is create the file /etc/modprobe.d/options and put this line in it:

options usbserial vendor=0x1199 product=0x6880

That will make it survive reboots.

create the file /etc/modprobe.d/options and put this line in it:

options usbserial vendor=0x1199 product=0x6880

This will enumerate 7 usb devices ttyUSB0 - 6

use device ttyUSB3

Also for those that use tmobile usa

copy /opt/vyatta/share/ppp/network/att to /opt/vyatta/share/ppp/network/tmobile

edit /opt/vyatta/share/ppp/network/tmobile

modify line 4 from
OK 'AT+CGDCONT=1,"IP","ISP.CINGULAR"'
to
OK 'AT+CGDCONT=1,"IP","WAP.VOICESTREAM.COM"'

If your interface is wlm0 then

set interfaces wirelessmodem wlm0 network tmobile

Rollback yum updates

2009-07-20T13:21:00.000-07:00

Anyone who has been around here a while knows yum updates can be a nightmare. It seems other distros are not immune to this either. On the Elastix beta list the following info came through and it may not be a bad idea to add this as a default behaviour in the various distros

--------------------------------------------email from Elastix Beta list ------------------------------------------------
Something to look at if packages break
#

To configure yum to save rollback information, add the line
tsflags=repackage to /etc/yum.conf.

#

To configure command-line rpm to do the same thing, add the line
%_repackage_all_erasures 1 to /etc/rpm/macros.

#

Install, erase, and update packages to your heart's content, using pup,
pirut, yumex, yum, rpm, and the yum automatic update service.

#

If/when you want to rollback to a previous state, perform an rpm update with
the --rollback option followed by a date/time specifier. Some examples: rpm
-Uhv --rollback '9:00 am', rpm -Uhv --rollback '4 hours ago', rpm -Uhv
--rollback 'december 25'.

source:
http://www.trixbox.org/forums/trixbox-forums/open-discussion/rollback-yum-updates

Building a module in Trixbox

2009-07-19T14:36:00.000-07:00

Building a module in Trixbox

cd /var/www/html/maint/modules/support/
cp -R /var/www/html/maint/modules/support /var/www/html/maint/modules/test

-Modify the module.xml file and the page.support.php file ( rename this according to your file option in module.xml).

Today I am going to break down the anatomy of a Trixbox CE module. Note that I am talking about a module in Trixbox CE's dashboard, and not a module in FreePBX, though there are many similarities.

I have created a skeleton module, keeping things as simple as possible. Lets look at the files, starting with module.xml. This file is required by the dashboard menu code as it is scanned every time the dashboard is shown. It tells it where to place the entry in the menus, and what happens when that menu is selected. Lets look at the tags:
module.xml

System

The primary menu to be placed under, or if hidden tab (see below) is 0, the name of the primary menu.

Skeleton Admin

The menu item name

Administer Skeleton

Tooltip text for menu item

Skeleton Admin

Is used in the module's HTML in the footer

skeleton

The folder the module resides in (/maint/modules/skeleton)

2.6.1

Is used in the module's HTML in the footer

1

A 1 makes this module an item in a menu, a 0 makes it a new menu

?skeleton

The actual link url. In this example, its just an argument to the dashboard's index.php, which causes it to load the template below. It could be a full URL to anything, but then you wouldnt get the dashboard headers and menu.

The required smarty template, described below.

config.php

Config variables mostly for smarty.

skeleton
0

A 1 here causes a new window to be opened, a 0 does not.

11

Where to place the menu/item. The number is relative to the numbers in other modules, so this one would be placed after another module at 10 but before one placed at 20.
module.tpl

This is a smarty template file. Here's whats in module.tpl:

This places your module's HTML inside of an iframe. If you like using smarty templates you can just put your html here and not use an iframe. Personally, I despise smarty. But that's what the dashboard is currently using. Because of this, you have the code below. the {literal} tag tells smarty not to mess with anything inside of it. This bit of javascript code is called from within the iframe by the module, so it can tell the iframe how tall it needs to be.

The advantage of doing it this way, is that you can embed whatever you want. You can even wrap an entire separate web application inside a module using the iframes (this is how FreePBX is put into the Trixbox dashboard). Notice the url in the iframe tag.

{literal}

{/literal}
config.php

Finally, you need this config file. This at minimum needs the following:

$smarty->assign("inner","skeleton");
?>

This just tells the smarty engine in the dashboard to insert our template into the dashboard's template.

Now, this is really all you need to know to start making a module. But there's some more interesting stuff there to take advantage of. Most of the newer modules have been written using two frameworks. One is a backend PHP Framework called Kohana (http://kohanaphp.com/), and the other is a frontend Javascript framework called Appcelerator (http://www.appcelerator.com/). You can use either or both or neither of them, your choice. Kohana I highly recomend because it takes care of many security issues for you, makes database access easy, and has lots of nice libraries built into it. Its also very efficient and flexible. Appcelerator is an interesting beast and can be hard to wrap your head around because it uses a message based mechanism and its own kind of syntax to add functionality to HTML tags. It can be very powerful and it has many handy complex GUI widgets included. Unfortunately the newest versions are incompatible with whats being used in Trixbox, so I can't anymore really recommend it. Instead I think I would go with just jQuery and the jQuery UI and maybe some of the controls from the ext framework.

Kohana uses an MVC style design, so you will see a controllers folder, and in there a skeleton.php file. I recommend reading the Kohana documentation, its really quite excellent. Reading this file should give you the general idea of how it works, though.

Source:
http://sporkbox.org/node/3
http://www.trixbox.org/forums/trixbox-forums/trixbox-projects/trixbox-development-where-start

SMESever Windows Integration

2009-07-06T06:40:00.000-07:00

Microsoft Windows integration with SMEserver
Goal

Provide hints and tips to make life a bit easier in mixed environments.

As suggested in this forum thread: http://forums.contribs.org/index.php?topic=39396.0
Login to shared recources

If you have exactly the same usernames and passwords in both clients and server, users only have to log in once (to Windows) to have direct access to shared recources on the server.
Domain Admins group

By default, SME Server allocates the "admin" user as the sole Domain Administrator. However, in larger environments it is often useful to have a group of users who can administer Windows workstations.

To make a group of users Domain Administrators, simply name the group as normal and write "Domain Admin" as the description. When users who are members of this group next log in to a Windows workstation that is joined to the SME Server domain, they will have Local Administrator rights automatically.

How to change PDC from Windows 2003 to SME Server.

From http://forums.contribs.org/index.php?topic=40228.new;topicseen Q: Is there any way in which i can do this without having to backup all the XP PC's and re-adding the PC's to the new Domain and then restoring all the files ?

A: The Microsoft "Active Directory Migration Tool" is supposed to do all of this automatically -- but always looks like it will take 30 - 40 hours of effort to setup, debug, and test prior to hitting the "go" button...

I move PC's from one domain to another as follows:

* Setup identical usernames on the new domain controller
* Add the computer to the new domain
* Login to the new domain NOT as the user who uses this computer (but with local administrative rights on the workstation).

It is important to NOT login as the intended user until after the following step, or you will create a new profile directory named for the new domain, and you'll have to use the "variation" listed below. Sometimes (if the old profile included auto-start programs that don't close on logout), you may need to reboot the computer, making sure that the first login after reboot is to a user account that is NOT the intended user for the computer in order to be able to rename the intended user's profile.

* Rename the user's profile c:\documents and settings\username ==> c:\documents and settings\username.old
* logout
* login as the intended user (re-creating "c:\documents and settings\username")
* logout
* login as another user with local admin rights (the same user used above, for example)
* rename the new userprofile c:\documents and settings\username ==> c:\documents and settings\username.new
* rename the old user profile c:\documents and settings\username.old ==> c:\documents and settings\username
* Change the ownership of the old profile to be the new user (or give the new user local administrative rights on the workstation)
* logout
* login as the new user - s/he should now have the exact same environment s/he had on the Windows server.

Variation - can't use the old username, or old profile name is incorrect, or you've already created a new profile name for the intended user If the old profile name is "username.domainname", or if you're trying to change the username but keep the settings from the old system:

* download and install the Windows 2003 Resource Kit
* follow the above procedure, ending up with the old profile named correctly for the new login credentials
* use "linkd.exe" (from the W2k3 resource kit) to create a "link" to the new profile with the exact name of the old profile, in case any of the registry settings include a hard-coded path to the old profile directory name.

(note: you don't need to install the entire resource kit on each workstation, you only need to put "linkd.exe" somewhere where you can get to it from each system - either in c:\windows on each system, or in a network share, for example)

Howto upgrade realtek network drivers on SMEServer

2009-07-06T06:33:00.000-07:00

# yum install kernel-devel gcc

Download the source from the realtek website

http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=5&PFid=5&Level=5&Conn=4&DownTypeID=3

remove the module causing the problem

# lsmod | grep r8169
# rmmod r8169

Download and extract the realtek driver

# cd /usr/src
# tar xjvf realtek-driver.tar.bz
# cd realtek-driver
# make clean
# make clean modules
# make install

Rename the old drive

# mv /lib/modules/`uname -r`/kernel/drivers/net/r8169.ko /lib/modules/`uname -r`/kernel/drivers/net/r8169.ko.bak

Unload the old driver

# rmmod r8169

Load the new module

# depmod -a
# modprobe r8168

Check the /etc/modprobe.conf file for a line entry like: alias eth0 r8169 and edit the line.
You might want to comment out the existing alias line and create a new line entry, example;
#alias eth0 r8169
alias eth0 r8168
# yum remove kernel-devel gcc
# signal-event post-upgrade; signal-event reboot

The module should be visible from the console mode when you reconfigure the server

trixbox 2.8 Xen fix/install

2009-07-01T09:14:00.000-07:00

For this to work, you need to have the install media for CentOS, I use the CentOS 5.3 i386 DVD. You should also have a read the trixbox-xen.pdf on this site.

CentOS specific stuff we need to do.
mount -oloop CentOS-5.3-i386-bin-DVD.iso /var/www/html/centos

make sure this is browsable in a web browser. You will need to be able to serve the installer these files.

We need to copy off the vmliuz and initrd.img from the images/xen folder for our use during the install. I like to serve all of my xen specific stuff from a nfs mount so that I can access these files from different xen servers without issues. How you do it is up to you. These files MUST be accessible by the computer that is going to boot the Xen DomU for trixbox28. For ease of following this doc, I will user /srv/xen/trixbox28 as my directory for these files.
mkdir /srv/xen/trixbox28
cd /var/www/html/centos/images/xen
cp initrd.img vmlinuz /srv/xen/trixbox28/

Trixbox Specific Repo Setup.
mkdir /var/www/html/trixbox

We have to create a trixbox folder to serve the rpms from for the installer.
mkdir /mnt/iso
mount -oloop trixbox-2.8.0.iso /mnt/iso

We need to mount the trixbox-2.8.0 iso so we can get the rpms and the comps.xml file off.
cd /mnt/iso/trixbox
cp *.rpm /var/www/html/trixbox/

Now we need to grab the comps.xml file for making the trixbox repo on our web server.
cd /mnt/iso/repodata
cp comps.xml /var/www/html/trixbox/
cd /var/www/html/trixbox/

We need to add a couple of rpms to our new trixbox repo for xen. This will ensure the xen kernel and dahdi kmod files will work right out of the box. Make sure you are in /var/www/html/trixbox when doing the wget. Please also make sure to use your closest mirror by going to http://www.centos.org/modules/tinycontent/index.php?id=30
wget http://mirror.nic.uoregon.edu/centos/5.3/updates/i386/RPMS/kernel-xen-2.6.18-128.1.10.el5.i686.rpm

We also need the kmod-dahdi from the trixbox repo.
wget http://yum.trixbox.org/trixbox/2.8/test/kmod-dahdi-linux-xen-2.2.0-4_trixbox.2.6.18_128.1.10.el5.i686.rpm

Now lets create our repo for our installer.
createrepo -g ./comps.xml ./

if the createrepo is not found, install it with yum and try again.
yum -y createrepo

Now we create our install file. I call mine trixbox28.install, the contents are listed below. Yours may differ. Of particular note is the kernel, ramdisk, and ks=http://192.168.1.216/trixbox.ks lines. The file trixbox.ks is our kickstart file, which we will have to make changes to from my original one in my xen guide.

kernel = “/srv/xen/trixbox28/vmlinuz”
ramdisk = “/srv/xen/trixbox28/initrd.img”
extra = “text ks=http://192.168.1.216/trixbox.ks”
name = “trixbox”
memory = “512″
disk = [ 'tap:aio:/srv/xen/trixbox.img,xvda,w', ]
vif = [ 'bridge=xenbr0', ]
vcpus=1
on_reboot = ‘destroy’
on_crash = ‘destroy’

Save this file in /etc/xen/

Now we need to edit the trixbox.ks file or ks.cfg from my trixbox-xen guide. We need to change the first line for the url to now point to our centos install media.
url –url http://192.168.1.216/centos
please make sure to use the ip address for your web server that is serving the centos install media.

We also need to add one additional repo (trixbox) to the trixbox.ks file. This is done with the repo line. Add this just before the %packages statement in the trixbox.ks file. Be sure to change the IP address and path to reflect the trixbox repo we created from above. We also need to add the kmod-dahdi-linux-xen so it gets installed and not install the kmod-dahdi-linux package.

#Add the repo information
repo –name=trixbox –baseurl=http://192.168.1.216/trixbox/
%packages
@Core
@Trixboxcore
kernel
kernel-xen
#add kmod-dahdi-linux-xen
kmod-dahdi-linux-xen
#remove the one for the other kernel so they don’t conflict possibly
-kmod-dahdi-linux
postfix
-sendmail

Now save your trixbox.ks or ks.cfg file with these changes.

Now start the install process for trixbox28.
xm create -c trixbox28.install

Your installer should start and ask you for your local as well as a password for root.

You may, more than likely, see a few error messages fly by when the installer starts going. These are ok to ignore.

Once the install has finished it will shutdown and you will need to start it with your actual trixbox28 xen config. Mine is listed below, again yours might differ.

name = “trixbox28″
memory = “512″
disk = [ 'tap:aio:/srv/xen/trixbox.img,xvda,w', ]
vif = [ 'bridge=xenbr0', ]
bootloader=”/usr/bin/pygrub”
vcpus=1
on_reboot = ‘restart’
on_crash = ‘restart’

You should see no errors with dhadi,
Starting dahdi: Loading DAHDI hardware modules:
wct4xxp: [ OK ]
wcte12xp: [ OK ]
wct1xxp: [ OK ]
wcte11xp: [ OK ]
wctdm24xxp: [ OK ]
opvxa1200: [ OK ]
wcfxo: [ OK ]
wctdm: [ OK ]
wcb4xxp: [ OK ]
wctc4xxp: [ OK ]
xpp_usb: [ OK ]

No hardware timing source found in /proc/dahdi, loading dahdi_dummy
Running dahdi_cfg: [ OK ]
Firstboot scripts will run and you should be good to go.
Source:
http://engineertim.com/?p=98

Installing freePBX on Debian Lenny

2009-06-30T21:48:00.000-07:00

Installing freePBX on Debian Lenny

Install Intrepid/lenny server as usual. Mark LAMP when installing the services. This will add Apache, MySQL and PHP5. Log in the server and access the super user account by issuing

sudo su

If you want to be sure about MySQL and PHP do this

apt-get install php5-mysql libapache2-mod-php5 mysql-server

You may need to set up apache appropriately, at the least be sure php5 is enabled. In Intrepid Ibex this is not needed:

a2enmod php5

For the localization to work properly you may have to edit /etc/php5/apache2/php.ini and modify as follow (leny/sid):

; PHP's built-in default is text/html
default_mimetype = "text/html"
;default_charset = "ISO-8859-1"
default_charset = "utf8"

Adding the last line forces the default charset for php pages (override apache charset) to be utf8.

From http://www.freepbx.org/trac/wiki/UbuntuServer

I had the problem with others i18n php websites too and this modification works fine for all of them

other Php.ini settings you should change to make FreePBX happy.

; Magic quotes for incoming GET/POST/Cookie data.
magic_quotes_gpc = Off

;max_input_nesting_level = 64 ; Maximum input variable nesting level
memory_limit = 100M ; Maximum amount of memory a script may consume (16MB)

Install Asterisk ¶

apt-get install asterisk asterisk-mysql asterisk-mp3 php-db php5-gd php-pear sox curl

There is no reason to install zaptel if you are using kernel 2.6 or above as it will provide the timing device unless of course you are using zaptel hardware. Ztdummy is no longer necessary.

I am installing these also, sounds and prompts in spanish

apt-get install asterisk-prompt-es asterisk-sounds-extra

There are two approaches to solve the permissions problem, one is to add the asterisk group to the user www-data default in apache.

1. Keep Apache running as www-data

adduser www-data asterisk

With this approach, FreePBX gives an error copying /usr/share/asterisk/bin/agi-bin. Change the owner doing this

chown www-data.asterisk -R /usr/share/asterisk

After installing FreePBX you will need to change the user in amportal.conf. This is explained in the section "Installing FreePBX".

Skip step 2 and jump to step 3 in this section.

2. Change Apache to run as asterisk

The other one is to edit the /etc/apache2/envvars file and change apache's user to asterisk. I tested this one and it works.

#export APACHE_RUN_USER=www-data
#export APACHE_RUN_GROUP=www-data
export APACHE_RUN_USER=asterisk
export APACHE_RUN_GROUP=asterisk

If you switched from approach 1 to approach 2, you should delete the session files in /var/lib/php5 or change ownership to asterisk.

3. Reload apache

apache2ctl graceful

To make the FOP server start, I changed the default shell for the user asterisk that was set to false:

usermod -s /bin/bash asterisk

In /usr/sbin/safe_asterisk I changed the variable BACKGROUND which is in 0 to 1
Installing FreePBX ¶

Download freepbx from http://www.freepbx.org

cd /tmp
wget http://mirror.freepbx.org/freepbx-2.5.1.tar.gz
cd /usr/src
tar xvfz /tmp/freepbx-2.5.1.tar.gz
cd freepbx-2.5.1

Prepare database. (If you have set up a root password for mysql, as it prompts you to when installing, then you will have to include the '-p' switch in all the following commands beginning with mysql. For example, the first will be "mysqladmin create asterisk -p". Enter your mysql root password when prompted):

mysqladmin create asterisk
mysqladmin create asteriskcdrdb
mysql asterisk < SQL/newinstall.sql
mysql asteriskcdrdb < SQL/cdr_mysql_table.sql

mysql

GRANT ALL PRIVILEGES ON asterisk.* TO asteriskuser@localhost IDENTIFIED BY 'amp109';
GRANT ALL PRIVILEGES ON asteriskcdrdb.* TO asteriskuser@localhost IDENTIFIED BY 'amp109';
flush privileges;
quit

VERY IMPORTANT BEFORE INSTALLING FREEPBX Make a copy of /etc/asterisk/modules.conf. FreePBX rewrites the file and trashes Asterisk installation. If you restart Asterisk after installing FreePBX Asterisk dies with no message.

cp /etc/asterisk/modules.conf ~/asterisk-modules.conf

Start installation of freepbx:

./install_amp

Things to write on, the other things may be left to the default values

AMPWEBROOT=/var/www/freepbx

Warning: If you have put FreePBX on a subdirectory, the panel will not work under the admin pages.

There are two approaches to make it work

1. Fix the error

Change the file /var/www/freepbx/admin/views/panel.php

// where it reads
// ''.
// you should erase one step back in the uri, as it shows here
''.

Go to step 3.

2. Create a virtual server and access your freepbx as http://freepbx

If you have access to the dns you can add a virtual server in Apache and avoid this last . Edit the file /etc/apache2/sites-available/freepbx and put this.

################# Named VirtualHosts

ServerName freepbx
ServerAlias freepbx

ServerAdmin yourname@yourdomain.com
ErrorLog /var/log/apache2/freepbx.error.log
CustomLog /var/log/apache2/freepbx.access.log combined

DocumentRoot /var/www/freepbx

Options Indexes FollowSymLinks MultiViews
Order allow,deny
AllowOverride All
Allow from all

AuthType Basic
AuthName "Restricted Area"
AuthUserFile freepbx-passwd
Require user admin

##################################################################

Make a symlink to make it available

ln -s /etc/apache2/sites-available/freepbx /etc/apache2/sites-enabled/099-freepbx

And add a password file with the password you want.

htpasswd -c /etc/apache2/freepbx-passwd admin

3. Restart Apache

/etc/init.d/apache2 restart

Restore the backup you've made of your modules.conf

cp ~/asterisk-modules.conf /etc/asterisk/modules.conf

If you have forgoten to make that backup, disable two libraries that are stopping asterisk to work. To disable a library you can add lines in /etc/asterisk/modules.conf. The autoload directive will load anything in the lib directory (/usr/lib/asterisk/modules) unless you put the line noload in the configuration file, before the global directive.

noload =>app_directory.so
noload =>res_adsi.so

In Ubuntu Hardy Heron, you should disable also

noload => app_voicemail_imap.so
noload => app_voicemail_odbc.so

From http://www.voip-info.org/wiki/view/Asterisk+modules

app_directory.so => (Extension Directory)
res_adsi.so: Resource for ADSI applications. See http://www.voip-info.org/wiki/view/ADSI

If you kept Apache running as www-data add this lines at the end of /etc/amportal.conf

AMPASTERISKUSER=www-data
AMPASTERISKGROUP=asterisk

To make it start at the end of everything, edit the /etc/rc.local file before the line exit 0.

/usr/local/sbin/amportal start
exit 0

(Optional) Asterisk will start on its own after package installation. If you want to run it under safe_asterisk and managed by amportal, remove asterisk from starting on its own

update-rc.d -f asterisk remove

Add a symlink and change permissions to make your System Recordings available to IVRs.

ln -s /var/lib/asterisk/sounds/custom /usr/local/share/asterisk/sounds/
chown -R asterisk:asterisk /usr/local/share/asterisk/
chmod -R 755 /usr/local/share/asterisk/

/usr/share/asterisk and its sub-directories must be owned by user and group asterisk or you will get an error in FreePBX about agi-bin and permissions. You can check your permissions

$ ls -l /usr/share | grep asterisk
drwxr-xr-x 8 asterisk asterisk 4096 2009-02-11 22:59 asterisk

If it does not look as above (i.e., ownership is root root instead of asterisk asterisk), then fix it

$ sudo chown -R asterisk:asterisk /usr/share/asterisk

If you're using Ubuntu 9.04 (Jaunty Jackalope) you may need to add the following line to /etc/apache2/httpd.conf:

DocumentRoot /var/www

and restart apache

apache2ctl restart

Find your new FreePBX web interface at http://server-ip/freepbx.

source:
http://www.freepbx.org/trac/wiki/UbuntuServerIntrepid

Asterisk, DAHDI and the Kernel drivers

2009-06-26T20:11:00.000-07:00

I yum upgraded my system and SAIL has stopped working".
This has to do with the fact that the Digium card drivers need to be loaded as part of the kernel (using insmod or modprobe) and the drivers themselves are actually stored in the kernel directory structure (usually in /lib/modules/kernel-release/extra or /lib/modules/kernel-release/update/extra). When the kernel changes (as it often does after a yum upgrade), Asterisk cannot find its drivers anymore (because they are in the directory structure of the old kernel, but not in the new one). ATrpms try to minimise the work they have to do by separating Zaptel/DAHDI rpms into two parts; the core release (1.4.xx) and a kmdl release which just contains the kmods for a particular kernel.

Now, it is by no means guaranteed that ATrpms will have a kmdl release available for your particular kernel whenever you do a yum upgrade. So, before you run a yum update, use yum to check whether it will update the kernel by issuing the following console command...

[root@sam SPECS]# yum check-update | grep -i kernel
kernel.i686 2.6.9-78.0.13.EL smeupdates
kernel-smp.i686 2.6.9-78.0.13.EL smeupdates

You can now check ATrpms to see if the is a zaptel/DAHDI kmdl for the new kernel release before you do the yum update.

If you didn't do the check and you are now in trouble, the easiest thing to do is simply start your SME Server on the old kernel. When yum installs a new kernel it doesn't throw the old one away and you can usually just start SME on the old (previous) kernel by pressing the space bar when the penguin/SME server splash screen appears at boot time. This will show you a list of all of the available kernels and you can choose which one you wish to start.

If on the other hand you absolutely must run the new kernel for some reason (perhaps it fixes a big security hole) then you can usually get away with copying the contents of the /extra/ directory from the old kernel tree to the new one (at least until you can get hold of the correct kmdl rpm)...

cp -a /lib/modules/_old-kernel_/extra/* /lib/modules/`uname -r`/extra

This won't work if you have moved from an EL kernel to an ELsmp kernel, or vice versa, but for most other changes, you should get away with it. We don't recommend this practice and we certainly don't guarantee that it will work. You are on your own. If it breaks your SME install then you get to keep all of the pieces. However, suffice to say that it has thus far worked for us.

source;
http://sarkpbx.com/twiki/bin/view/Main/AsteriskDahdi

How to Run VMWare ESXi on PowerEdge T105

2009-06-18T12:03:00.000-07:00

How to Run VMWare ESXi on PowerEdge T105

How to Run VMWare ESXi 4.0 on PowerEdge T105, you ask? Simple Answer. Flash Drive. The process goes thusly.

* Get your ESXi Image ready to go. You can download it from the VMWare website.
* Get your trusty 1GB+ Empty Flash Drive and stick it into one of the USB Ports on the Server
* Next, Burn the ISO to a disk and stick it in your drive.
* Press F11 at the BIOS to select your Boot device.
* Boot from the DVD-ROM Drive.
* When prompted where to install VMWare ESXi choose the Flash Drive that should show up in the list.
* When prompted to reboot, remove the installation media. On reboot enter the BIOS.
* Switch the Hard Drive Boot Priority to put the USB drive to the top.
* Boot VMWare ESXi as normal.

Voilà! You’re ready to rock. The PowerEdge T105 is not on the HCL so you’re unfortunately unable to run it natively because of the onboard SATA controller. You could also find a compatible SATA controller and put the drives on that, but realistically the USB Drive is not that big of a hassel for most small environments. It also means you can boot VMWare even in the event of a HDD Failure. I’ve heard that many people will actually put the flash drive inside the case that so it is not at risk of being knocked around

source
http://www.greenwireit.com/blog/2009/06/how-to-run-vmware-esxi-on-poweredge-t105/

FreePBX DialPatterns

2009-04-19T21:03:00.000-07:00

Outbound Routing and Trunks

There are two sections where numbers can be manipulated before passing them out to the outside world. The trunk and the outbound route.

The Trunk

The first thing to note is there is no point whatsoever of putting any anything in the trunk dial rules unless it changes the dial string.
The dial rules are there for manipulating the number before sending it onto the carrier.

For instance, many VoIP carriers require calls to be sent to them in what is known as IETF format.
For instance, someone in the USA would dial: -

011 44 1179 1179 33 to speak to me in the UK
however, your ITSP will only require:- 44 1179 1179 33 In the UK and much of the rest of the world, we simply prefix with a 00, so to call me normally, the user dials 00 44 1179 1179 33, however the carrier requires 441179117933

USA numbering system called the NANP – the North American Numbering Plan.
Three sections of the plan: NPA-NXX-XXXX

NPA – the area code [2-9][0-8][0-9]
NXX – The exchange Code [2-9][0-9][0-9]
XXXX-Station Code – [0-9][0-9][0-9][0-9]

All numbers in the USA CANADA AND ISLANDS follow the above convention.
However, the USA international code is 1,
therefore your ISP may require you to actually send 1 followed by the remaining 10 digits.

The Outbound Route

The outbound route selects which trunk to use depending on the number dialed by the customer.
It goes in strict order from the top, trying to match the number actually dialed with the pattern in the outbound route. When it matches with a pattern, then it will select the first available trunk connected to that route.

Generally speaking, we try and get all the numbers into the same sort of order before delivering them onto the the trunk. e.g.
In the USA, we would be trying to get them into 10 digit NANP format.
For the rest of the world, we would be delivering the numbers with the international dialing code,
so that if the call goes out via a standard land line, it will simply be delivered as is,
whereas if you are going out via a provider, you can add and remove digits to suit the carrier.

The Tools

In both outbound routes and trunks, there are a number of codes that are used to filter or select numbers as well as to do manipulation.

Selection

X – Matches any digit from 0 to 9 Z – Matches any digit from 1 to 9
N – Matches any digit from 2 to 9
[123] – Matches only the numbers in the brackets, e.g. 123
[1-3] – Matches a range of digits in the brackets, again 123
[1236-9] – Matches a range of digits as above, 123 678 and 9 .
wildcard and matches everything.
Asterisk warn against just putting in a . to match with everything – it is better practice to put X. to match everything.

So in the North American numbering plan mentioned previously,
we had:-

NPA – the area code [2-9][0-8][0-9]
NXX -the exchange Code [2-9][0-9][0-9]
XXXX - Station Code – [0-9][0-9][0-9][0-9]

Which translates to N[0-8]XNXXXXXX
However, for simplicity, it is just written as NXXNXXXXXX

Another example is a UK Cellphone.

The number always starts with a 447, and next digit is a number between 4 and 9, and always with another 9 digits after the 7 – so this number would be selected as 447[4-9]XXXXXXXXX, being lazy, you could just select the number as 447. but there is a danger that people could dial numbers beginning 4470 which are over a dollar a minute, and provide a revenue share for the owner of the number.

Manipulation

Numbers can be manipulated with the following operands.

“+” - Adds a number onto the dialed digits. “|” _ Subtracts a number from the dialed digits.

So in the USA, to add a 1 onto the front of the NANP dial it is as simple as putting in 1+NXXNXXXXXX before delivering the number to your VoIP carrier. Do this in the trunk dial rule.

In the UK, things are slightly more tricky. When we dial say my number in the UK, we would dial 01179117933, so to get this into IETF format, we have to remove the leading 0 and replace with a 44. This can be achieved by putting in a manipulation rule in the trunk dial rules. 44+0|ZXXXXXXXXX This rule would strip the leading 0 off and add a 44 onto the front where the number was 11 digits long, started with a 0, and the next number was not a 0.

Also in the UK, we can dial locally for instance, 01788 is the Rugby code, and then there are 6 digits, where the first digit is not a 0. So to pass this over a VoIP trunk in IETF format, we need to add 441788 onto the front of the number – this is easily done with 441788+ZXXXXX. However, there is one small problem – directory inquiries in the UK begin with 118 followed by 3 digits, so we would have to put a precise rule in for that as well 118XXX and make sure it went out via a suitable trunk.

The | can be used to help people move from an old PBX, where you do 9 for an outside line, and you still want people to dial with or without a 9. Simply put 9| NXXNXXXXXX and NXXNXXXXXX in the dial patterns box in the outbound route.

This will therefore match any 10 digit NANP number, and any 10 digit NANP number prefixed with 9.

Practicalities

The first job is to create all the trunks, with dial rules to put them into IETF format where necessary, so that the number is delivered as the carrier expects to see it.

Then we can move onto Outbound routes.

The first job is to ensure that the emergency services can be called. In the USA, this is 911, or if you are in a panic, it may be 9911 (9 for an outside line) In the UK, it is 999 and in much of Europe 112.

Taking the USA as an example, it is usually preferable to send emergency calls out over the local PSTN so that the caller ID is correct, and the emergency services know where to find you. There are E911 services, but keeping it simple, we assume all Emergency calls are going out over the local PSTN lines.

Operator Services and local calls.

So Create an outbound route, select the first PSTN trunk, and all the others (just in case) and put in:- 911 ; Will call emergency services 9|911 ; Will call emergency services even if they did 9 for an outside line.

Additionally, we can put some other patterns in here for any other numbers which have to go out over the PSTN. IN the UK, we have operator services, which are all 3 or 4 digits long, and never more than 5, so a simple: ZXXXX ; 5 Digit numbers not starting with a 0 ZXXX ; 4 Digit numbers not starting with a 0 ZXX ; 3 Digit numbers not starting with a 0

In my experience, operator services and numbers that have to be dialed via the PSTN are never more than 5 digits and always start with a 1 to 9.

Then we want to do the same for people who still want to dial 9 for an outside line – as per the legacy system 9|ZXXXX ; 5 Digit numbers not starting with a 0 and prefixed with a 9 for an outside line 9|ZXXX ; 4 Digit numbers not starting with a 0 and prefixed with a 9 for an outside line 9|ZXX ; 3 Digit numbers not starting with a 0 and prefixed with a 9 for an outside line

You may also want to put in something 777|. So you can test your analogue trunks are working correctly, to force a call over the PSTN by prefixing your call with a 777.

National

The next Outbound route entry will be say for your USA, or national numbers, e.g.

NXXNXXXXXX ; NANP numbers 9| NXXNXXXXXX ; NANP numbers, where the user has prefixed with a 9

The leading 1, or whatever has to be added on the front will be added on by the trunk dial rule. If you are using VoIP, you may want a hidden dial string to force calls over the VoIP trunks, so maybe add 888|. to force calls over VoIP. International Calls

The final entry, maybe for your international calls.

The length of the dialed digits can vary depending on where you are calling, so this will be the last outbound route.

So in the USA, the international prefix is 011 and the next number will be a number between 1 and 9, so an entry for international routes will be

011Z. Which will match any international number For the rest of the world that uses 00 as the international prefix, 00Z. Will achieve the same ends.

Again, the 00 or the 011 will be stripped off by the dial rule in the trunk.

Again, we would want to make provision for people dialing 9 for an outside line

9|011Z. Or 9|00Z. As appropriate for your country.

Clearly these rules can be moved around to suit your own particular requirements.
Inbound Routes

It is not well documented, but it is possible to pattern match on inbound routes in the caller ID, this is done by prefixing the Caller ID to be matched with an underscore. So to match all calls that come from Germany, which has a dialcode of 49, simply type _49. in the inbound route caller ID field. This will match all calls which begin with a 49, with anything after it. You can use all of the selection digits to pattern match that you use in the outbound routes.

DAHDI CFG

2009-04-19T19:13:00.000-07:00

DAHDI conf files settings.

#cat dahdi-channels.conf

; Autogenerated by /usr/sbin/dahdi_genconf on Fri Apr 3 22:28:00 2009 -- do not hand edit
; Dahdi Channels Configurations (chan_dahdi.conf)
;
; This is not intended to be a complete chan_dahdi.conf. Rather, it is intended
; to be #include-d by /etc/asterisk/chan_dahdi.conf that will include the global settings
;
; Span 1: WCFXO/0 "Wildcard X100P Board 1" (MASTER)
;;; line="1 WCFXO/0/0 FXSKS (EC: MG2)"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 1
callerid=
group=
context=default

#cat system.conf

# Autogenerated by /usr/sbin/dahdi_genconf on Fri Apr 3 22:28:00 2009 -- do not hand edit
# Dahdi Configuration File
#
# This file is parsed by the Dahdi Configurator, dahdi_cfg
#
# Span 1: WCFXO/0 "Wildcard X100P Board 1" (MASTER)
fxsks=1
echocanceller=mg2,1

# Global data

loadzone = us
defaultzone = us

Here are the Dahdi command responses:

#setup-pstn

--------------------------------------------------------------
Detecting PSTN cards
--------------------------------------------------------------

dahdi-linux-2.1.0.4-1_centos5

STOPPING ASTERISK
Unable to connect to remote asterisk (does /var/run/asterisk/asterisk.ctl exist?)
Asterisk Stopped

STOPPING FOP SERVER
FOP Server Stopped
Unloading DAHDI hardware modules: doneLoading DAHDI hardware modules:
wct4xxp: [ OK ]
wcte12xp: [ OK ]
wct1xxp: [ OK ]
wcte11xp: [ OK ]
wctdm24xxp: [ OK ]
wcfxo: [ OK ]
wctdm: [ OK ]
wcb4xxp: [ OK ]
wctc4xxp: [ OK ]
xpp_usb: [ OK ]

Running dahdi_cfg: [ OK ]

Checking for dahdi-auto.conf
No need to create symlink

SETTING FILE PERMISSIONS
Permissions OK

STARTING ASTERISK
Asterisk Started

STARTING FOP SERVER
FOP Server Started
Channel Location State Application(Data)
0 active channels
0 active calls
0 calls processed

#dahdi_cfg -vvv

DAHDI Tools Version - 2.1.0.2

DAHDI Version: 2.1.0.4
Echo Canceller(s): MG2
Configuration
======================

Channel map:

Channel 01: FXS Kewlstart (Default) (Echo Canceler: mg2) (Slaves: 01)

1 channels to configure.

Setting echocan for channel 1 to mg2

#dahdi_tool

DAHDI Tool (C)2002-2008 Digium, Inc.

¤ DAHDI Telephony Interfaces
â Alarms Span â
â OK Wildcard X100P Board 1

CLI> dahdi show status

Description Alarms IRQ bpviol CRC4 Fra Codi Options LBO
Wildcard X100P Board 1 OK 0 0 0 CAS Unk YEL 0 db (CSU)/0-133 feet (DSX-1)

CLI> dahdi show channels

Chan Extension Context Language MOH Interpret Blocked State

CLI>

CLI> dahdi restart

Destroying channels and reloading DAHDI configuration.
== Parsing '/etc/asterisk/chan_dahdi.conf': == Found
== Parsing '/etc/asterisk/dahdi-channels.conf': == Found

CLI> dahdi show status

Description Alarms IRQ bpviol CRC4 Fra Codi Options LBO
Wildcard X100P Board 1 OK 0 0 0 CAS Unk YEL 0 db (CSU)/0-133 feet (DSX-1)

CLI> dahdi show channels

Chan Extension Context Language MOH Interpret Blocked State

Upgrade SMEServer-8.0beta3 to PHP-5.2.3

2009-04-18T20:10:00.000-07:00

db yum_repositories set c5-testing repository
db yum_repositories setprop c5-testing GPGKey http://dev.centos.org/centos/RPM-GPG-KEY-CentOS-testing
db yum_repositories setprop c5-testing BaseURL "http://dev.centos.org/centos/\$releasever/testing/\$basearch/"
db yum_repositories setprop c5-testing Name "CentOS-5 Testing" enabled 0 GPGCheck yes
signal-event yum-modify
yum --enablerepo=c5-testing update php
php --version
signal-event post-upgrade; signal-event reboot

OpenSBC on Vyatta Firewall

2009-03-05T20:08:00.000-08:00

OpenSBC on Vyatta Firewall How-To
This solution builds a firewall that allows for Inbound SIP calling, Outbound SIP calling and far-end NAT traversal for remote users.

Introduction
The following instructions will help you create a fully functional SIP Session Border Controller. Utilizing
the Open Source SBC known as OpenSBC (www.opensourcesip.org) and the Open Source and high
performance firewall known as Vyatta (www.vyatta.org) you will be able to create a single server
solution. This solution was designed to work with the Open Source PBX sipX Enterprise Communications
Server (sipXecs) but should function for most pure SIP solutions with minor adjustments.
A Session Border Controller is a device used in VoIP networks to provide control over the signaling and
sometimes also the media streams involved in setting up, conducting, and tearing down calls. The battle
with SIP traffic is usually in dealing with Network Address Translation (NAT) issues. Whether on the PBX
side or on the far end for a teleworker. The SBC helps solve those problems.
The Session Border Controller also allows administrators to not have to expose their PBX equipment
directly to the Internet. The SBC acts as a buffer between the two worlds and may have some security
measures implemented.
Additionally it is desirable to be able to prioritize outbound Internet traffic through a single interface to
the Internet. If a Session Border Controller is placed in parallel with a corporate firewall they will both
contend for the same bandwidth. With the SBC and firewall in line the voice traffic can be prioritized
properly over the data traffic.
OpenSBC can do much more than manage SIP traffic in and out of a network. Another great feature of
the product is the ability to setup trunks to Internet Telephony Service Providers (ITSP’s). This
document however is concerned with SIP and NAT Traversal issues, so let’s get on with it.
Install Vyatta
This work was done with Vyatta 5 Beta.
Download the Vyatta LiveCD ISO from http://www.vyatta.org/downloads
Burn the ISO to a CD (imgburn (www.imgburn.com) works great)
1. Boot from Vyatta LiveCD ISO. Press ENTER.
2. At login, username 'root', password 'vyatta'.
3. Enter 'install-system'
4. Configure as needed... (see example configuration at the end of this document)
Download/Install Items Needed for OpenSBC Compliation
This is kind of a kitchen sink approach as there are probably more packaged listed than needed.
1. Login to Firewall as user 'vyatta'
2. cd /etc/apt
3. su
4. Password: (enter root password)
5. nano -w sources.list
6. Add line: "deb ftp://ftp.us.debian.org/debian/ lenny main contrib non-free"
7. Ctrl-X and Y to overwrite
8. apt-get update
9. apt-get install -y mc autoconf automake cvs flex expat libexpat1-dev libtool build-essential
libxml2 libxml2-dev libtiff4 libtiff4-dev php5 php5-cli php5-mysql php5 php5-cli php5-mysql
php5-gd mysql-server libmysqlclient15-dev php-pear php-db curl sox apache2 libssl-dev
libncurses5-dev bison libaudiofile-dev subversion libnewt-dev libcurl3-dev libnet-ssleay-perl
openssl ssl-cert libauthen-pam-perl libio-pty-perl libmd5-perl libpg-perl libdbd-pg-perl php5-
pgsql sqlite3 libsqlite3-dev openssl ssl-cert libapache2-mod-php5 php5-cli php5-common
phpMyAdmin php5-mcrypt mcrypt phppgadmin apache2 libmcrypt-dev
Get OpenSipStack and OpenSBC from CVS:
This will download the most current OpenSIPStack and OpenSBC code from the development area.
1. cd /usr/src
2. cvs -d:pserver:anonymous@opensipstack.cvs.sourceforge.net:/cvsroot/opensipstack login
3. cvs -z3 -d:pserver:anonymous@opensipstack.cvs.sourceforge.net:/cvsroot/opensipstack co -P
opensipstack
4. cvs -z3 -d:pserver:anonymous@opensipstack.cvs.sourceforge.net:/cvsroot/opensipstack co -P
opensbc
Compile / Make OpenSipStack and OpebSBC:
The following will compile OpenSIPStack and OpenSBC
1. cd /usr/src/opensipstack
2. chmod +x ./configure
3. ./configure
4. make bothnoshared
5. cd ../opensbc
6. chmod +x ./configure
7. ./configure
8. make bothnoshared
9. make distrib
Relocate Executables
Copy the executables to a more acceptable location on the server.
1. cp /usr/src/opensbc/distrib/* /usr/local/bin
Fix Shell Scripts
The following will modify the startup and shutdown shell scripts.
1. Edit /usr/local/bin/startup.sh (i use 'nano -w /usr/local/bin/startup.sh')
2. Modify the startup command to: ./opensbc -d -p /var/run/opensbc.pid -H 65536 -C 1024000
3. Modify the shutdown command to: ./opensbc -k -p /var/run/opensbc.pid
Make OpenSBC run at Startup
The following will make OpenSBC run when the Linux machine starts up.
1. copy startup.sh to /etc/init.d (cp /usr/local/bin/startup.sh /etc/init.d/opensbc.sh
2. Modify opensbc.sh to make sure it runs as root and so it can find the application.
a. nano -w /etc/init.d/opensbc.sh
b. Make the line read: /usr/local/bin/opensbc -u root -d -p /var/run/opensbc.pid -H 65536
-C 1024000
Note: In Debian the startup programs run from the rc2.d directory, begin with cap S and the order
number it should start in. Create a symbolic link in that directory to the opensbc.sh script file.
3. ln -fs /etc/init.d/opensbc.sh /etc/rc2.d/S92opebsbc
Miscellaneous Information
Log / Ini Files
The ini file is in: /root/OpenSIPStack/OpenSBC_data
The log files are in /root/OpebSIPStack/OpebSBC_data/logs
To watch a log file use tail -f
tail -f /root/OpenSIPStack/OpebSBC_data/logs/b2bua-....
To get to OpenSBC Administration Console
http://inside.ip.addr.vyatta:9999
OpenSBC.ini file:
See the important settings in RED.
[Solegy]
RTTS-Client-Address=(gets populated automatically with outside IP, this is of no use)
[OpenSBC-General-Parameters]
SIP-Log-Level=1
PTRACE-Log-Level=1
Log-File-Prefix=b2bua
SBC-Application-Mode=B2BUpperReg Mode
Interface-Address Array Size=0
Enable-Backdoor-Port=True
Enable-Trunk-Port=True
Enable-Calea-Port=True
RTP-Min-Port=10000
RTP-Max-Port=20000
Enable-Local-Refer=False
Max-Forwards=70
Encryption-Mode=XOR
Encryption-Key=GS
Transaction-Thread-Count=10
Session-Thread-Count=10
Alerting-Timeout=30000
Seize-Timeout=60000
SIP-Timer-B=Default
SIP-Timer-H=Default
Session-Keep-Alive=1800
Session-Max-Life-Span=10800
Max-Concurrent-Session=100
Max-Call-Rate-Per-Second=10
[Upper-Registration]
Enable-Stateful-Reg=False
Rewrite-TO-Domain=True
Rewrite-FROM-Domain=True
Route-List Array Size=1
Route-List 1=[sip:*@externalsip.domain] sip:internalsip.domain;domain=internalsip.domain
[Internal-DNS-Mapping]
Internal-DNS-Map Array Size=2
Internal-DNS-Map 1=[sip:internalsip.domain] sip:internal.ip.of.sipxpbx:5060
Internal-DNS-Map 2=[sip:internal.fqdn.ofsipxpbx] sip:internal.ip.of.sipxpbx:5060
[Proxy-Relay-Routes]
Drop-Routes-On-Ping-Timeout=False
Proxy-Resolve-To-URI=True
Route-List Array Size=0
[B2BUA-Routes]
Enable-Route-Scripting=False
Route-Script=b2bua-route.cscript
Route-List Array Size=1
Route-List 1= [sip:*@externalsip.domain] sip:internalsip.domain
Insert-Route-Header=True
Rewrite-TO-URI=True
Prepend-ISUP-OLI=False
Route-By-Request-URI=True
Route-By-To-URI=False
Drop-Routes-On-Ping-Timeout=False
Use-External-XML=False
External-XML-File=b2bua-route.xml
[Media-Server]
Enable-Media-Server=False
Media-Server-Number=5000
Codec-List Array Size=0
No-RTP-Proxy-On-All-Transfers=False
Enable-Announcement-Service=False
4xx-Error-Map=prompts/basic/cant_complete.wav
5xx-Error-Map=prompts/basic/cant_complete.wav
6xx-Error-Map=prompts/basic/cant_complete.wav
Announcement-Error-Map Array Size=0
[Outbound-Proxies]
Outbound-Proxies Array Size=0
[Local-Domain-Accounts]
Accept-All-Registration=True
Account-List Array Size=0
A Simple Vyatta Configuration
firewall {
broadcast-ping disable
name ALLOW_ESTABLISHED {
rule 10 {
action accept
state {
established enable
}
}
}
name INBOUND {
rule 20 {
action accept
destination {
}
log disable
state {
established enable
related enable
}
}
rule 999 {
action drop
destination {
address 0.0.0.0/0
}
log enable
source {
address 0.0.0.0/0
}
}
}
:
name OUTBOUND {
rule 999 {
action accept
destination {
address 0.0.0.0/0
}
log disable
source {
address 0.0.0.0/0
}
}
}
name TO-ROUTER {
rule 10 {
action accept
log disable
state {
established enable
related enable
}
}
rule 30 {
action accept
icmp {
type 3
}
log disable
protocol icmp
}
rule 32 {
action accept
icmp {
:
type 8
}
log disable
protocol icmp
}
rule 34 {
action accept
icmp {
type 11
}
log disable
protocol icmp
}
rule 40 { (Allow SIP Signalling Traffic In)
action accept
destination {
port 5060
}
log enable
protocol udp
}
rule 41 { (Allow RTP (voice) traffic in)
action accept
destination {
port 10000-20000
}
log enable
protocol udp
}
rule 999 {
action drop
destination {
address 0.0.0.0/0
}
log enable
source {
address 0.0.0.0/0
}
}
}
}
interfaces {
ethernet eth0 {
address 172.16.1.254/24
description inside
firewall {
in {
name OUTBOUND
}
}
hw-id {auto populated with inside MAC addr}
mtu 1500
}
ethernet eth1 {
address dhcp (I’m getting my IP DHCP from cable modem)
firewall {
in {
name INBOUND
:
}
local {
name TO-ROUTER
}
}
hw-id {auto populated with outside MAC addr}
}
loopback lo {
}
}
service {
dhcp-server {
disabled false
shared-network-name ETH0_POOL {
authoritative disable
subnet 172.16.1.0/24 { (Inside Network IP Range)
default-router 172.16.1.254 (Inside IP Address of Vyatta)
dns-server 172.16.1.2 (IP Address of PBX or internal DNS Server)
dns-server 208.67.222.222 (Extra DNS Servers…)
dns-server 208.67.220.220
domain-name xyzcompany.com (Internal SIP domain)
ntp-server 172.16.1.2 (To Get Time from PBX)
start 172.16.1.100 {
stop 172.16.1.200
}
tftp-server-name 172.16.1.2 (To Download Phone Config Files from PBX)
}
}
}
dns { (If you are using dynamic DNS for Outside Interface)
dynamic {
interface eth1 {
service dyndns {
host-name sipxecs.dyndns.info
login LoginID
password password
}
}
}
}
nat {
rule 1 {
outbound-interface eth1
type masquerade
}
}
ssh {
allow-root true
}
webproxy {
cache-size 500
listen-address 172.16.1.254 {
}
}
:
}
system {
domain-name xyzcompany.com
host-name fw1
login {
user root {
authentication {
encrypted-password $1$0/Nwe.bk$rM/D4fTAHbvjaLarha/xK/
}
}
user vyatta {
authentication {
encrypted-password $1$6xFKV1OQ$ifrekBjneuSx1kacuaJm8/
}
}
}
ntp-server 69.59.150.135
package {
auto-sync 1
repository community {
components main
distribution stable
url http://packages.vyatta.com/vyatta
}
}
syslog {
console {
facility all {
level err
}
}
host 172.16.1.129 {
facility all {
level err
}
facility kern {
level debug
}
facility local0 {
level debug
}
}
}
}

Thanks Michael W. Picher for a great howto
http://sipxecs.blogspot.com/2009/01/opensbc-on-vyatta-firewall-how-to.html

FreeSwith on Vyatta

2009-03-05T20:04:00.000-08:00

Vyatta (ver 5 beta) with FreeSwitch Installation

Install Vyatta

Boot from ISO. Press ENTER.

At login, username 'root', password 'vyatta'.

Enter 'install-system'

Configure as needed...

Get items required for building Freeswitch

Login to Firewall as user 'vyatta'

vyatta@FW1:~$ cd /etc/apt
vyatta@FW1:/etc/apt$ su
Password: (enter root password)
vyatta@FW1:/etc/apt$ nano -w sources.list

Add line: "deb ftp://ftp.us.debian.org/debian/ lenny main contrib non-free"

Ctrl-X and Y to overwrite

FW1:/etc/apt# apt-get update

FW1:/etc/apt# apt-get install -y mc autoconf automake libtool build-essential libxml2 libxml2-dev libtiff4 libtiff4-dev php5 php5-cli php5-mysql php5 php5-cli php5-mysql php5-gd mysql-server libmysqlclient15-dev php-pear php-db curl sox apache2 libssl-dev libncurses5-dev bison libaudiofile-dev subversion libnewt-dev libcurl3-dev libnet-ssleay-perl openssl ssl-cert libauthen-pam-perl libio-pty-perl libmd5-perl libpg-perl libdbd-pg-perl php5-pgsql sqlite3 libsqlite3-dev openssl ssl-cert libapache2-mod-php5 php5-cli php5-common phpMyAdmin php5-mcrypt mcrypt phppgadmin apache2 libmcrypt-dev

Get the Freeswitch Code

cd /usr/src/

svn checkout http://svn.freeswitch.org/svn/freeswitch/trunk freeswitch

Build Freeswitch...

cd freeswitch

./bootstrap.sh

./configure –prefix=/usr/local/freeswitch

make

make install

make sounds-install

make moh-install

make samples

Run Freeswitch...

cd /usr/local/freeswitch/bin

./freeswitch

original post
http://sipxecs.blogspot.com/

Change SQL in Trixbox 2.6.1 Passwords Step by Step

2009-02-24T14:14:00.000-08:00

http://trixbox.org/forums/trixbox-forums/open-discussion/change-default-sql-password-freepbx-version-2-6

How to Change MySQL passwords: Follow each step in order !

Step 1) mysql -u root –p [ENTER]
Step 2) Enter password: passw0rd [ENTER]

Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 3743 to server version: 5.0.22

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

Step 3) mysql> use mysql; [ENTER]
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Database changed
Step 4) mysql> update user set password = PASSWORD('NEW_PASSWORD') where User = 'asteriskuser'; [ENTER]`
Query OK, 1 row affected (0.00 sec)
Rows matched: 1 Changed: 1 Warnings: 0

Step 5) mysql> grant all privileges on *.* to root@localhost identified by ''NEW_PASSWORD ' with grant option; [ENTER]
Query OK, 0 rows affected (0.00 sec)

Step 6) mysql> show databases; [ENTER]
+------------------------+
| Database |
+------------------------+
| information_schema |
| asterisk |
| asteriskcdrdb |
| asteriskrealtime |
| endpoints |
| meetme |
| mysql |
| sugarcrm |
| test |
+------------------------+
9 rows in set (0.00 sec)

Step 7) mysql> grant all privileges on meetme.* to asteriskuser@localhost; [ENTER]
Query OK, 0 rows affected (0.00 sec)

Step 7) mysql> grant all privileges on endpoints.* to asteriskuser@localhost; [ENTER]
Query OK, 0 rows affected (0.00 sec)

Step 8) mysql> grant all privileges on asteriskrealtime.* to asteriskuser@localhost; [ENTER]
Query OK, 0 rows affected (0.00 sec)

Step 9) mysql> grant all privileges on asteriskcdrdb.* to asteriskuser@localhost; [ENTER]
Query OK, 0 rows affected (0.00 sec)

Step 10) mysql> grant all privileges on asterisk.* to asteriskuser@localhost; [ENTER]
Query OK, 0 rows affected (0.00 sec)

Step 11) mysql> flush privileges; [ENTER]
Query OK, 0 rows affected (0.00 sec)

mysql> exit [ENTER]
Bye

OK THIS PART IS FINISHED!

Next…..

Change default passwords:

To change the FreePBX manager pass, you need to edit two separate files and put in the new password.

Step 12) nano /etc/asterisk/manager.conf [ENTER]

Find 'secret = amp111' under the [admin] section. Change 'amp11' to your new desired password. CTRL+X followed by 'Y' to save and exit.

Now, we need to edit the /etc/amportal.conf to use our new password.

Step 13) nano /etc/amportal.conf [ENTER]

Find the line that says 'AMPMGRPASS=amp111' and change the 'amp11' to the new password you just set. CTRL+X followed by 'Y' to save and exit.

Now we need to edit the /etc/cbmysql.conf

Step 14) nano /etc/asterisk/cbmysql.conf [ENTER]

Find the line that says password=passw0rd' and change the ' passw0rd' to the new password you just set. CTRL+X followed by 'Y' to save and exit.

Now we need to edit the /var/www/html/web-meetme/lib/database.php
Step 15) nano /var/www/html/web-meetme/lib/database.php [ENTER]
Find the line that says $password = 'passw0rd';' and change the 'passw0rd' to the new password you just set. CTRL+X followed by 'Y' to save and exit.

You will also need to update the password in the /etc/asterisk/cdr_mysql.conf file for call detail records (cdr) and in /etc/asterisk/res_mysql

Step 16) nano /etc/asterisk/cdr_mysql.conf [ENTER]

Find the line that says 'password=amp109' and change the 'amp109' to the new password you just set. CTRL+X followed by 'Y' to save and exit.

Step 17) nano /etc/asterisk/res_mysql.conf [ENTER]

Find the line that says 'dbpass=amp109' and change the 'amp109' to the new password you just set. CTRL+X followed by 'Y' to save and exit.

Step 18) service mysqld restart [ENTER]

Step 19) amportal restart [ENTER]

Ready to Rock ‘n’ Roll!

*** NOTE: FreePBX/MySQL does not like having an exclamation point (!) in the password. There may be other special characters that it doesn't like also.

Document prepared by: Scott J. Arnold 09/11/2008 Contact: Scott@TheVOIPWiz.com
IAX2 Hardware at http://www.thevoipwiz.com

web-meetme

2009-02-24T14:02:00.001-08:00

Log into the mysql db and look at the user table in the meetme db. I found that the password update feature sets the passwds to NULL. Not sure why, but setting a plaintext!! password for the user fixes it (update user set password="NEWPASS" where id=x;). meetme v3 is still having other issues, like not allowing viewing of the conferences in progress (says auth timeout after 90 seconds in some phpagi-asmanager file) and the emailer feature is mailing the notice, but its content is duplicated. To fix the email not working problem, I changed the MAILER option to SERVER, and to fix meetme from saying "invalid conference number" updated the username/password for the DB in several files and changed "localhost" to its ip equiv "127.0.0.1". There seems to be alot of places where username, password and dbhost are still defined statically in the files, which is a headache to track down and change:

/var/www/html/web-meetme/lib/database.php
/var/www/html/web-meetme/lib/defines.php
/var/www/html/admin/functions.inc.php
/var/www/html/include/ccsframework/common.php
/var/www/html/xmlservices/include/xmlservices_libs.php

Still looking for something else that needs changing, I think its bad programming in there somewhere thats assuming the db user/pass is the same as for asterisk and webmeetme or something...

edit: Found my issues, the other config file is /etc/asterisk/phpagi.conf, it has the default asterisk admin user/pass in it.... add that to the list of hardcoded usernames/passes that needs to be #included somewhere. meetme and webmeetme work good now... still tracking down why the email has the body contents duped, and why bringing up a conference to edit its props doesnt pull in the name or other details.

* Login or register to post comments

tlum
Posts: 39
Member Since:
2008-08-10
Code error in user_add_sqldb.php
Sun, 11/23/2008 - 7:50pm

Problems in /var/www/html/web-meetme/user_add_sqldb.php

Around line 90:

Change:

if($userPass)
{
// $userPass = md5($userPass);
$userPass = "password='$userPass'";
}
if (intval($conflict) == 1){
$data = array($userEmail,$userAdmin,$fname,$lname,$phone,$userPassr);

To:

// if($userPass)
// {
// $userPass = md5($userPass);
// $userPass = "password='$userPass'";
// }
if (intval($conflict) == 1){
$data = array($userEmail,$userAdmin,$fname,$lname,$phone,$userPass);

Missspelling $userPassr passes NULL to the database... correct variable misspelling by removing 'r'. Comment (or remove) $userPass = "password='$userPass'"; to correct syntax. $userPass should simply be the actual password. Looks like someone was toying with an MD5 hash in the database... never quite got it working, but never quite reverted back to working non-MD5 either.

-Ted-

* Login or register to post comments

kinglyr
Posts: 26
Member Since:
2007-05-06
WEB-MEETME PROBLEMS SOLVED!!! (STEP-BY-STEP)
Wed, 01/14/2009 - 10:41am

After a lot of reading and testing here is the solutions of the Web-Meetme problems, that i can confirm that all EXIST on TrixBox v2.6.2.1 (STABLE)

There is a typo in one of the .php files for Web Meetme. Go to the Linux CLI and type this in:
nano -w /var/www/html/web-meetme/user_add_sqldb.php
Press CTRL+W to search and type in 'userPassr' and press Enter. If you get taken to a result, change 'userPassr' to 'userPass' (removing the 'r' on the end). Also there is another error in Line 93 comment out $userPass = "password='$userPass'"; and insert instead $userPass = "$userPass";

ALSO A USEFUL TIP:
If you did something wrong and you have been locked out from Web-Meetme then do the following to see the meetme users and change their password and admin priviledges:
mysql -u root -p (enter your SQL root password, default is: passw0rd)
show databases;
use meetme;
show tables;
show columns from user;
select * from user;
select * from user where password is null;
update user set password=PASSWORD("newpass") where email='user_email_you_want_change_pass';

EndPoint Device Setup

2009-02-24T08:25:00.000-08:00

Atftp server

Description

This contribution adds a tftp server (atftp-server) to your smeserver (primarily used by workstations that are using the pxeboot protocol to retrieve boot images and parameters from the server).

It was produced to support my smeserver-thinclient contrib, but can be used independently.

I also have a sister contrib that uses tftp-server, if you prefer that server. It works the same as this one and is interchangeable.

Requires

smeserver >= 7.0

wget http://distro.ibiblio.org/pub/linux/distributions/smeserver/releases/7/smecontribs/SRPMS/smeserver-tftp-server-1.0-2.el4.sme.src.rpm
wget http://distro.ibiblio.org/pub/linux/distributions/smeserver/releases/7/smecontribs/SRPMS/smeserver-xinetd-0.1-1.el4.sme.src.rpm
http://yum.trixbox.org/centos/5/SRPMS/tb-tftpboot-2.6.0-1.src.rpm
http://yum.trixbox.org/centos/5/SRPMS/tbm-endpointcfg-2.6.1-7.src.rpm
http://yum.trixbox.org/centos/5/SRPMS/aastra-ipphone-2.4.1-1.src.rpm
http://yum.trixbox.org/centos/5/SRPMS/aastra-ipphone-2.4.1-1.src.rpm

atftp-server >= 0.7-3

wget http://apt.sw.be/redhat/el5/en/i386/dag/RPMS/atftp-server-0.7-6.el5.rf.i386.rpm

Installation

This contrib is currently held in the smedev repository (I will try to move it into smeextras or smeaddons), so the following commands will install on your smeserver. atftp-server is currently available in the dag repository.

yum --enablerepo=smedev --enablerepo=dag install smeserver-atftp-server

Officially you should then need to activate the database changes etc., but this is not required for this package.

signal-event post-upgrade

signal-event reboot

The tftpd status is controlled via the Thin Clients server-manager panel if you have installed my smeserver-thinclient contrib.

If you haven't, you'll need to enable the atftp server and expand all the templates etc.

config setprop tftpd status enabled

signal-event tftpd-conf

If for any reason the atftp server isn't running, try:

/etc/init.d/supervise/tftpd restart

Defaults

You shouldn't need to play with any parameters (except status). The defaults and allowed values are listed below.

	default	allowed Values	description
status	disabled	enabled/disabled
access	private	private/public/localhost	private = internal interface ONLY public = all interfaces localhost = localhost ONLY disabled = none
user	root	root/nobody	should default to nobody, but this doesn't work
timeout	default	default/300	default = 900 seconds (15 minutes)
UDPPort	69	any port
directory	/tftpboot	any directory

These settings can be set/changed via

#! exec 2>&1

exec /usr/sbin/in.tftpd --user nobody.nofiles --daemon --no-fork \

--tftpd-timeout 30 --retry-timeout 5 --no-tsize --no-blksize \

--no-multicast  --verbose=7 /tftpboot

##Add asterisk www to sudoers
##!/bin/bash

cp /etc/sudoers /etc/e-smith/templates-custom/etc/

sed -i 's/^Defaults requiretty/# Defaults requiretty/g' /etc/e-smith/templates-custom/etc/sudoers
for sudocmd in /usr/bin/nmap ; do
if ! grep "asterisk ALL = NOPASSWD: $sudocmd" /etc/e-smith/templates-custom/etc/sudoers >/dev/null 2>&1; then
echo "asterisk ALL = NOPASSWD: $sudocmd" >> /etc/e-smith/templates-custom/etc/sudoers
echo "asterisk ALL = NOPASSWD: $sudocmd added to /etc/e-smith/templates-custom/etc/sudoers"
fi
done

## We want to create/update the trixbox version

mkdir -p /etc/trixbox
echo %{version} > /etc/trixbox/trixbox-version.

echo "-------------------------------------------"
echo "Configuring MySQL"
echo "-------------------------------------------"

#create SQL table for storing CDRs
/usr/bin/mysqladmin create asteriskcdrdb
/usr/bin/mysql GRANT ALL PRIVILEGES ON asteriskcdrdb.* TO asteriskuser@localhost IDENTIFIED BY 'amp109';
/usr/bin/mysql < /opt/asterisk/sql/asteriskcdr.sql

#create SQL table Asterisk RealTime
/usr/bin/mysqladmin create asteriskrealtime
/usr/bin/mysql < /opt/asterisk/sql/asteriskrealtime.sql

#create SQL table web-meetme
/usr/bin/mysqladmin create meetme
/usr/bin/mysql meetme < /opt/asterisk/sql/meetme.sql

#create SQL table for phone config
/usr/bin/mysqladmin create endpoints
/usr/bin/mysql < /opt/asterisk/sql/endpoints.sql

echo "-------------------------------------------"
echo "installing ATFTP Server"
echo "-------------------------------------------"

##touch /etc/e-smith/templates/etc/dhcpd.conf/11Option-150
option option-150 code 150 = $localip;\n;

##touch /etc/e-smith/templates/etc/dhcpd.conf/25TFTPServerName
{
package esmith;

use strict;
use Errno;
use esmith::config;
use esmith::util;
use esmith::db;

my %config;
tie %config, 'esmith::config', '/home/e-smith/db/configuration';

my $systemname = db_get_type(\%config, 'SystemName') || '';
my $domainname = db_get_type(\%config, 'DomainName') || '';
my $localip = db_get_type(\%config, 'LocalIP') || '';

$OUT .= " option tftp-server-name \"$systemname.$domainname\";\n";
$OUT .= " option option-150 $localip;\n";
}

touch /var/log/atftpd.log
chown nobody:nobody /var/log/atftpd.log
cp -f $LOAD_LOC/tftp /etc/xinetd.d
chkconfig tftp on

SMEServer IM

2009-02-24T08:14:00.000-08:00

SMEServer MailServer

2009-02-24T07:57:00.000-08:00

Zarafa

Open Source Collaboration, providing:

Integration with your existing Linux mailserver
Native mobile phone support
Outlook "Look & Feel" webaccess
Stable Outlook sharing (100% MAPI) - MS Exchange replacement

The Community version http://forums.zarafa.com/viewtopic.php?f=7&t=990

Installation

Download & install ...

Zarafa rpms

http://www.zarafa.com/download-community

Distribution = Rhel 4

3 Outlook license version (or possibly just disable licensed service for the GPL version, check please)

tar -zxvf zarafa-6.20-rhel4-i386.tar.gz
yum localinstall libvmime*.rpm libical*.rpm zarafa-6*.rpm zarafa-webaccess-6*.rpm zarafa-licensed-6*.rpm

smeserver-zarafa

Note:

This is a beta release. Possibly for production servers after testing with per user settings first.

You select 'per user' or 'globally' where you want mail delivered via db entries. Default leaves mail going to users ~/Maildir.

A minimal amount of disruption can be achieved by enabling per user, that user just enables another IMAP connection in their email client on port 8143, they could then just drag and drop mail between SME to Zarafa mail stores.

Install a fresh SME 7.4 test server and perform the following:

yum install smeserver-zarafa --enablerepo=smetest

After rpm install execute the following:

/etc/e-smith/events/actions/zarafa-install
signal-event post-upgrade; signal-event reboot

Note:

You will be prompted to select the user plugin you wish to test. Note the ldap plugin is currently not supported in the rpm. The unix plugin reads existing SME user details but also includes groups and machine names (messy). The db plugin is pristine however you need to enter all the user details. In both cases the user must exist in SME first as a standard user. A decision on which plugin we will choose for final deployment is still to be determined.

Enable mail delivery to zarafa for users:

for all users

config setprop zarafa-server GlobalForward enabled

or for individual users

db accounts setprop $USERNAME zarafa enabled

apply

/etc/e-smith/events/actions/qmail-update-user

If you chose the db plugin, run:

/etc/e-smith/events/actions/zarafa-create-user

Usage

Webmail

Access with a browser,

https://server/zarafa
https://server/webaccess
https://server/webmail (with Horde disabled 'config setprop imp status disabled')

Outlook

To use MS Outlook install the zarafaclient-*.msi add-on contained in the win32 directory of zarafa-*.tar.gz

Outlook 2007 client generates Error 0x80070057 on send and receive if the Zarafa

server is added to an existing profile. Creating a new clean profile solved the problem.

IMAP

The default ports for Zarafa are 8000 + default values

so imap = 8143, imaps 8993

SME and Zarafa use different folder naming.

drafts > Drafts          [client specific ?, Drafts is default Thunderbird-2.0]
sent-mail > Sent Items
trash > Deleted Items
junkmail > Junk E-mail

Thunderbird

The Thunderbird client uses its own Trash folder, not the Zarafa "Deleted Items" folder,

Change in the config editor

Preferences > advance > config editor, find mail.server.number and add new string as below

user_pref("mail.server.server5.port", "8143");
user_pref("mail.server.server5.name", "zac@232.net");
user_pref("mail.server.server5.numHdrsToKeep", 30);
user_pref("mail.server.server5.timeout", 29);

right click > new
preference name > mail.server.server5.trash_folder_name
value > Deleted Items

+user_pref("mail.server.server5.trash_folder_name", "Deleted Items");

Drafts and Sent Items can be changed in : Account Settings > user > Copies and Folders

If junkmail exists just delete it.

Calendar

To access the calendar functions with an iCal client eg, Thunderbird and Lighting

in Thunderbird/Lightning > New Calendar > on network > ical > http://:8088/ical//calendar/

8089 for SSL

Note, there were problems with reading events created with /webaccess, seems better with RC1

It's a know problem. Zarafa 6.30 will use CalDEV instead of iCal

Mobile synchronisation

To enable synchronization of your mobile phone through ActiveSync with Zarafa, Z-push needs to be installed.

You can find the original Z-push installation documentation here: http://download.zarafa.com/zarafa/release/docs/z-push_installation_manual.en.pdf

Download the latest Z-push version (see: http://z-push.sourceforge.net).

wget http://download2.berlios.de/z-push/z-push-1.2.1.tar.gz

Extract the files:

tar -zxvf z-push-1.2.1.tar.gz -C /var/www/html

'State'-dir needs to be writable for apache:

chmod 755 /var/www/html/z-push/state
chown www:www /var/www/html/z-push/state

Expand and restart

expand-template /etc/httpd/conf/httpd.conf
sv restart httpd-e-smith

SSL Synchronization with Windows Mobile devices

Synchronisation over a secured connection is possible if you can add your site as a trusted one with corresponding certificate on your mobile.

This is the case for Windows mobile 6 (WM6) devices. Problems should occurs on several WM5 devices, because of a bug that limits addition of certificates with that OS.

Here are the steps to add your server as a trusted platform on your WM6 mobile :

1. to convert your server's certificate into a (Binary coded DER X.509) .cer file you can either run the following command and skip to step 4 or just start at the next step.

 openssl x509 -in /home/e-smith/ssl.pem/.pem -inform PEM -out /root/.cer -outform DER

2. copy your server's certificates located in /home/e-smith/ssl.crt/ on a Windows XP/Vista computer

3. we need to transform those .crt certificates to .cer certificate ( same type of certificate but .crt are text-encoded ). To do so :

in microsoft windows open a certificate by double clicking on it
in "Detail" Tab pane choose "Copy to file"
Choose Binary coded DER X.509 (.cer) format
save resulting .cer certificates on local machine

4. transfer .cer certificates on your mobile using windows explorer

5. When done, on your WM6 mobile use file explorer to open those certificates. When opening one, the certificate is automatically added to trusted sites.

6. You can then change your Exchange server parameters to use SSL. It will be asked to reenter your password.

Know working hardware

Tested and working with WinMobile 6.1 on a HTC TyTN II over a SSL connection / mail-push is working.

Tested and working with WinMobile 6.1 on an upgraded QTEK9100 over SSL connection. Push mail not tested.

Mail Sorting

Maildrop as configured with smeserver-mailsorting will deliver to ~/Maildir rather than zarafa

For now either disable sorting or bypass for zarafa users.

Procmail will sort to zarafa from smeserver-mailsorting-1.2-29

Extras

Command line admin

man zarafa for details

List users:

/usr/bin/zarafa-admin -l

Update a user to admin status:

/usr/bin/zarafa-admin -u  -a 1

Migrating users and data to Zarafa

http://wiki.contribs.org/Imapsync

Customizing the Calendar

The labels and categories in the calendar can be altered to suit user requirements.

 The labels are defined in /var/www/html/webaccess/client/layout/dialogs/standard/appointment.php beginning at line 225

 The categories are in /var/www/html/webaccess/client/layout/dialogs/modal/categories.php beginning at line 51.

Zarafa Bayesian learning

This howto enables SpamAssasin Bayesian learning for Zarafa

Bugs

Check your logs when troubleshooting or reporting bugs

tail -f /var/log/zarafa/*
tail  /var/log/slapd
tail  /var/log/messages

Please raise bugs under the SME-Contribs section in bugzilla and select the smeserver-zarafa component or use this link .

Search open bugs for smeserver-zarafa at bugs.contribs.org

Zarafa: use their forum for zarafa specific bug reporting, http://forums.zarafa.com/

Origingal contribution

http://wiki.contribs.org/Zarafa

Thanks:

Darrell May

Stephen Noble http://dungog.net/wiki

MySQL Database on SMEServer

2009-02-24T07:14:00.000-08:00

SME Server runs MySQL as a database server. A lot of applications require a MySQL database, among them is the Horde webmail interface which is supplied by SME Server by default.

MySQL website: http://www.mysql.com
MySQL 4.1 manual: http://dev.mysql.com/doc/refman/4.1/en/

General

The SME Server is based on CentOS, the development team will take their stock RPM's from the CentOS releases. The current version of MySQL installed on SME Server is version 4.1.20.

You can upgrade MySQL to a higher version but you are advised not to do so, as this might break your SME Server configuration. The Horde webmail interface relies on MySQL. Upgrading to version 5.x is known to break stuff like webmail. If you insist on upgrading MySQL you may be able to find instructions in the forum, but be advised that no support can be expected from the developers and all bugs reported in the bugtracker will not be taken into account.

MySQL on SME Server runs on a socket instead of on a port which you might be accustomed to. This is done to improve security as in the view of the development team only the server itself (localhost) needs to have access to the MySQL server. However you can configure MySQL to be accessible from the local network (see below).

MySQL root password

There appears to be no password set for the MySQL root password, but this is not true. If you are logged in to the SME Server shell a special mechanism is in place to log you in with MySQL root privileges without prompting you for the password.

The MySQL root password for SME Server is a 72 character random string generated during installation of SME Server. You should never change the MySQL root password as this will break your SME Server configuration. How to login as MySQL root user? describes how to access MySQL with root privileges on SME Server.

Login as MySQL root user

To login as MySQL root user, simply type 'mysql' at the SME Server shell, this will log you in with root privileges.

Resetting the MySQL root password

To reset the password for the MySQL root account. The MySQL root user on SME Server has a random generated password which is generated during installation. You do not need to know this password to login to MySQL with root privileges on SME Server. If you might have changed the MySQL root password you can reset it like this after getting command line access as root user.

For SME Server 7.3 and more recent versions do the following:

cd /var/service/mysqld
sv d .
expand-template /root/.my.cnf
expand-template /var/service/mysqld/set.password
/usr/libexec/mysqld --bootstrap --user=mysql --skip-grant-tables < ./set.password
sv u .

For SME Server 7.2 and earlier releases do the following (they use the runsvctrl command instead of the sv command):

cd /var/service/mysqld
runsvctrl d .
expand-template /root/.my.cnf
expand-template /var/service/mysqld/set.password
/usr/libexec/mysqld --bootstrap --user=mysql --skip-grant-tables < ./set.password
runsvctrl u .

Restoring accidently deleted MySQL root user

Note: The following is only applicable on SME 7.3 and MySQL 4.1

cd /var/service/mysqld
sv d .
echo 'use mysql;'>set.rootuser
echo -n 'INSERT INTO user VALUES("localhost","root","",'>>set.rootuser
echo '"Y","Y","Y","Y","Y","Y","Y","Y","Y","Y","Y","Y","Y","Y","Y","Y","Y","Y","Y","Y","Y","","","","",0,0,0);'>>set.rootuser
expand-template /root/.my.cnf
expand-template /var/service/mysqld/set.password
/usr/libexec/mysqld --bootstrap --user=mysql --skip-grant-tables < set.rootuser
/usr/libexec/mysqld --bootstrap --user=mysql --skip-grant-tables < set.password
sv u .

Access MySQL from the local network

MySQL on SME Server is run on a socket instead of on a port. MySQL on SME Server is by default configured to allow only localhost connections to improve security, this means that it is only accessible from the server itself and not from the local network nor from the internet. If you wish to enable local network access, execute the following commands on a SME Server shell as root:

config setprop mysqld LocalNetworkingOnly no
expand-template /etc/my.cnf
sv t /service/mysqld

Access MySQL from a remote network

If you wish to enable access to MySQL databases from remote networks, then in addition to the LocalNetworkingOnly db setting mentioned above, you will need to execute the following commands:

config set mysqld service access public status enabled TCPPort 3306
signal-event remoteaccess-update
signal-event reboot

Keep in mind this enables access to your MySQL database for ANYONE, so make sure you have strong passwords on ALL your MySQL databases. Alternatively it would be a more secure approach to require external (remote) users to establish a VPN connection and effectively become part of the local network. In that case do not change the mysql access to public status using the above command.

Enable InnoDB engine

For enable InnoDB engine, run the following commands:

db configuration setprop mysqld InnoDB enabled
expand-template /etc/my.cnf
sv t /service/mysqld

Administration

Information about user managament can be found in the MySQL User Account Management section of the MySQL manual, which holds a lot of useful information, a small section is listed here for convenience.

Create a new database

See the developers guide if you wish to automate the creation of a database within an rpm

Get access to the SME Server shell and issue the following commands:

mysqladmin create 'dbname' --default-character-set=utf8

This will create an empty database called dbname.

	Warning:
	The 'root' user should not be permitted to access the database except from localhost. Each application should have its own database and its own user to access that database.

Creating MySQL user(s)

Decide which permissions you will have to give to the user on what database. Details about this can be found in the MySQL Manual found at the MySQL site. Get access to the SME Server shell and issue the following commands to login to the MySQL server:

mysql

Suppose we want to create a user which has read-only access on all tables in the database called 'test':

GRANT SELECT ON test.* TO 'user'@'host' IDENTIFIED BY 'password';

In the above line you will have to fill in the user and the host and/or domain from which you will allow the user access to the SME Server MySQL server (don't forget the single quotes). More information can be found in the MySQL Server Manual at the MySQL website linked here.

Listing available databases

To view a list of available databases on the system you can issue the following command while logged in in MySQL:

show databases;

Remove a database

Get access to the SME Server shell and MySQL and issue the following command:

drop database databasename;

Replace databasename with the name of the database.

Remove a user

Get access to the SME Server shell and MySQL and issue the following command:

USE mysql;
DELETE FROM user WHERE user = 'username';
FLUSH PRIVILEGES;

Replace username with the username you wish to delete.

	Tip:
	mysql_setpermission is a command line menu driven utility that can assist in MySQL administration.

MySQL Database on SMEServer 7.4/8.0

2009-02-24T07:09:00.000-08:00

SME Server runs MySQL as a database server. A lot of applications require a MySQL database, among them is the Horde webmail interface which is supplied by SME Server by default.

MySQL website: http://www.mysql.com
MySQL 4.1 manual: http://dev.mysql.com/doc/refman/4.1/en/

General

The SME Server is based on CentOS, the development team will take their stock RPM's from the CentOS releases. The current version of MySQL installed on SME Server is version 4.1.20.

MySQL root password

Login as MySQL root user

To login as MySQL root user, simply type 'mysql' at the SME Server shell, this will log you in with root privileges.

Resetting the MySQL root password

For SME Server 7.3 and more recent versions do the following:

cd /var/service/mysqld
sv d .
expand-template /root/.my.cnf
expand-template /var/service/mysqld/set.password
/usr/libexec/mysqld --bootstrap --user=mysql --skip-grant-tables < ./set.password
sv u .

For SME Server 7.2 and earlier releases do the following (they use the runsvctrl command instead of the sv command):

cd /var/service/mysqld
runsvctrl d .
expand-template /root/.my.cnf
expand-template /var/service/mysqld/set.password
/usr/libexec/mysqld --bootstrap --user=mysql --skip-grant-tables < ./set.password
runsvctrl u .

Restoring accidently deleted MySQL root user

Note: The following is only applicable on SME 7.3 and MySQL 4.1

cd /var/service/mysqld
sv d .
echo 'use mysql;'>set.rootuser
echo -n 'INSERT INTO user VALUES("localhost","root","",'>>set.rootuser
echo '"Y","Y","Y","Y","Y","Y","Y","Y","Y","Y","Y","Y","Y","Y","Y","Y","Y","Y","Y","Y","Y","","","","",0,0,0);'>>set.rootuser
expand-template /root/.my.cnf
expand-template /var/service/mysqld/set.password
/usr/libexec/mysqld --bootstrap --user=mysql --skip-grant-tables < set.rootuser
/usr/libexec/mysqld --bootstrap --user=mysql --skip-grant-tables < set.password
sv u .

Access MySQL from the local network

config setprop mysqld LocalNetworkingOnly no
expand-template /etc/my.cnf
sv t /service/mysqld

Access MySQL from a remote network

If you wish to enable access to MySQL databases from remote networks, then in addition to the LocalNetworkingOnly db setting mentioned above, you will need to execute the following commands:

config set mysqld service access public status enabled TCPPort 3306
signal-event remoteaccess-update
signal-event reboot

Enable InnoDB engine

For enable InnoDB engine, run the following commands:

db configuration setprop mysqld InnoDB enabled
expand-template /etc/my.cnf
sv t /service/mysqld

Administration

Create a new database

See the developers guide if you wish to automate the creation of a database within an rpm

Get access to the SME Server shell and issue the following commands:

mysqladmin create 'dbname' --default-character-set=utf8

This will create an empty database called dbname.

	Warning:
	The 'root' user should not be permitted to access the database except from localhost. Each application should have its own database and its own user to access that database.

Creating MySQL user(s)

mysql

Suppose we want to create a user which has read-only access on all tables in the database called 'test':

GRANT SELECT ON test.* TO 'user'@'host' IDENTIFIED BY 'password';

Listing available databases

To view a list of available databases on the system you can issue the following command while logged in in MySQL:

show databases;

Remove a database

Get access to the SME Server shell and MySQL and issue the following command:

drop database databasename;

Replace databasename with the name of the database.

Remove a user

Get access to the SME Server shell and MySQL and issue the following command:

USE mysql;
DELETE FROM user WHERE user = 'username';
FLUSH PRIVILEGES;

Replace username with the username you wish to delete.

	Tip:
	mysql_setpermission is a command line menu driven utility that can assist in MySQL administration.

Later versions of applications

Why does SME Server still not have PHP 5, MySql4, Apach2, xxx

SME Server 7.x is based on Centos 4.x which in term is based on RedHat Enterprise Linux 4.x. Since the development team is limited in person and time, all work is done in spare time, we do not have the time to implement such big changes and cope with the maintenance of such work.

Is xxx on SME Server still safe to run?

Yes, because security fixes and bug fixes are backported to the 4.x releases and they are propagated to the users as updates, for more information have a look at http://www.redhat.com/security/updates/backporting.

Can I install a later version of xxx

Yes, but you are then responsible for updates and possible conflicts with updates

For example see this page for PHP#PHP_5 PHP updates and warnings

Known Problems

	Note:
	This section is to be used to document problems that cannot or will not be fixed through development of SME Server 7. Please refer to the KnownProblems page

Simple Hotel Style Wake-Up Calls

2009-02-21T19:04:00.000-08:00

Simple Hotel Style Wake-Up Calls – THE MODULE

The Hotel Style Wake Up call function has proven to be of interest to many of us. Simpler than Ward’s Voice Reminders, the system emulates the wake-up calls you might get when staying at a hotel.

So far – in the previous thread about this topic – we learned several ways of manually deploying the existing scripts. From all feedback – those methods are working well for most folks. But, from the stand point of being easy to install and configure – well, some folks had issues.

When it comes right down to it – I just don’t prefer to make the PBX administrator drop into a command line or text file to make simple configuration changes. And I have always wanted to try my hand at making an actual FreePBX module……

I am pleased to release to general use today the Hotel Style Wake Up Calls Module for FreePBX. The module uses essentially the same scripts used in the manually installed version – but with some significant changes.

Ok - On with the Show.

Prerequisites – Pay Attention

- If you currently run any version of the Wake-Up scripts (from agi-bin), such as those discussed in this article, the module version will not co-reside. You should REMOVE the wakeup scripts from previous versions from your platform before installing the module. Failure to do so will cause unanticipated behaviors (Read: The old scripts wont work, may be replaced, and the new module won’t work either. Not good).

- If you currently run the Outside The Box Wakeup Calls – The module will do the same work, but be aware you still have to manually configure one aspect of it. (http://pbxinaflash.com/forum/showpos...64&postcount=9)

Note: The module DOES support the ability for the operator to send wakeup calls to any telephone number – including PTSN numbers; just not dialing in from outside the system – since Authentication is not yet supported.

- This module uses the mySql database to store and read its configuration values. If you are running your pbx under a database other than MySQL, this module will fail.

- If you have changed the asterisk user password to the MySQL asterisk database, this module will fail. (It can be edited to work under these circumstances, but that is outside the scope of this article)

Under the Hood
For those interested in the details, the typical version of the Wake-Up scripts use variables (set in the include script) to establish various details, such as Operator Mode config, and other similar configuration settings. Also, the two scripts used different methods and locations for storing their configuration variables – leaving the installer to configure things in three separate places.

In the module version, both of the work-horse scripts have been modified to gather their configurations from the same .inc script. The .inc script itself has been modified to gather most configuration details from the database, instead of fixed values found in the scripts. To round it all out, the module has a user interface that allows the most common configuration settings to be changed (and stored in the database) – without ever opening a text editor.

Installation and Configuration – Wake-Up Calls: THE MODULE
Works exactly like installing any other third party module.

Download the module. You can get it from HERE.
In FreePBX, Module Admin, Upload the Module to your PBX.
In FreePBX, Module Admin, under Third Party Addon, Locate Wake Up Calls, and INSTALL.
In FreePBX, Under tools, Third Party Addon, Select Wake Up Calls.

You should be greeted by the Wake Up Calls user interface screen, shown below.

The module installer installs default values.

Operator Mode
When enabled, the operator mode allows those extensions listed as Operator Extensions to request a Wake Up Call for any telephone number, up to the length specified in the Extension length drop down box.
If you do not wish to support WakeUp calls to outside numbers, select the extension length which matches the extension length used on your PBX.
If you do plan on supporting outside telephone numbers, select 10 or 11 as the extension length – dependant upon how your PBX dialing is set up (to require a leading ‘1’ or not.)
If you enter a destination number that is less than your maximum extension length - you must end your input with the # key, or it wont process your input. (Thanks for pointing this out, HAT!)

General Conifguration
Ring Time determines how long the Wake Up Call will ring the destination number before giving up for that attempt.
Retry time is the wait period between retries.
Max Retries is the maximum number of times the system will attempt the wake up call, or snooze call back.
WakeUp Caller ID allows you to customize the Caller ID info displayed by the wake up service. By default, the phone number shows the default feature code assigned when you install the module. If you change the feature code – make sure to come here and change the caller id to reflect the new value.

Changing the Dail String (Feaure Code)
In keeping with the goal of not having to edit config files, the Wake-Up Module sets the feature code (or dial string) using the FreePBX Feature Codes Page. (In FreePBX, under Setup, Select Feature Codes).

In the WakeUp Calls section, find the Wake Up Calls item. All controls work as expected here. You may change the feature code to suit your needs, and even disable the Wake Up calls service.

Future Module Updates
The FreePBX module update process works as expected for this module. Should an update be released, simply upload it to your PBX in the same way as the original. The Module Admin will then recognize a pending upgrade, and offer you that choice. Upon Upgrade, your previously established configuration items are not disturbed.

This module is not in the FreePBX third party modules repository, and as of this writing, there is no help page for it available from the More Information link in the FreePBX Module Admin. This may be accomplished in future releases.

Roadmap to Future Module Updates
In the future, I hope to add support for authenticating outside callers, in order to restore all the functionality in the Outside the Box version previously mentioned,

Credits/Thanks
I would never have been able to start this module without Jeremy Coulter, who provided me with actual working copies of the scripts to begin with, and lots of encouragement. I have naturally left any and all credit/author lines in the original scripts that were present when I got them.

Also – my ego would have taken a lethal beating from all the failures along the way were it not for Joe Roper – who provided encouragement, advice, and shared his immense knowledge of the FreePBX environment freely along the way.

Last – certainly not least, Jerry Swordsteel in far away Sweden jumped in and spent a good 4-5 hours coding the PHP for the Module’s user interface screen, and data/string manipulation needs. Jeremy, Joe, Jerry – thanks for helping make this module possible!

As always – share your results – and let us know how the Wake Up Module works for you.

Until next time –