By , September 3, 2014 12:21 PM


to connect to the serial port use putty

select the COM port and settings can be

When the port is selected click Ok, to get to the Port configuration form

On this form specify the port settings.

The most common port speeds for GSM phones and modems are 9600, 19200, 57600 and 115200.

The Data bits should be set to 8. The Parity to none the Stop bits to 1 and the flow control should be hardware.

Set the appropriate serial port (usually COM1)
Baud rate (speed) = 9600
Data bits = 8
Stop bits = 1
Parity = N



Will give you a response OK if you are connected

I can check in PuTTY GSM modem information using commands:
Manufacturer: AT+CGMI -> “WAYECOM MODULE”
Model: AT+CGMM -> “MULTIBAND G850/900E/1800/1900MHz”
Revision: AT+CGMR -> “652B09gg.Q2406B 1961548 103107 17:50”

VMware Vcenter corruption

By , March 3, 2014 4:27 PM

mount -n -o remount,rw /

e2fsck -f /dev/sda3


By , February 10, 2014 1:50 PM

0 VMN A0
1 VMN A1
6 VMN B0
7 VMN B1

Duplicate Outlook 2013 Calendars and how to remove them

By , January 30, 2014 6:23 PM

Can you restore the .pst? It needs unloading from outlook before just deleting it.

If not:

You can solve the errors rather easily – just remove the data links in ‘Control Panel’/’Mail’/[Data Files]. Don’t do this yet.

See if you have options to remove the calendars there (probably not – now would be a good time to backup/export the working PST+calendar) and do so.

If you can still expand the contents of the deleted .pst in the Navigation pane then goto the folder view and right click and delete the offending calendar. More than likely you won’t have this option so just remove the data files from the Account window (as mentioned above).

If the calendars are still showing, do you have the option of unselecting them from the Calendar window?

Kanel and Moxa

By , January 19, 2014 10:26 AM


I use terminal servers since over 5 years with no problems.

As Cezary said, you should use rawtcp or telnet mode to conect to the
modems connected to your moxa device. Therefore no need to install any
driver nor kernel module. That is only needed if you want your OS to
show ethernet port as a virtual local serial port and then have kannel
connected to the local virtual serial port.

You should define each of your modems with its IP and port so kannel
will connect directly to it via TCP/IP:

group = smsc
smsc = at
smsc-id = modem1
log-level = 0
modemtype = auto
speed = 115200
log-file = “/var/log/kannel/modem1.log”
allowed-smsc-id = modem1;modem3
sim-buffering = true
keepalive = 60
max-error-count = 8
device = rawtcp <<<<<<<<< THIS SETUP WILL ALLOW YOU TO host = <<<<<<<<< CONECT DIRECTLY TO YOUR MODEM port = 2100 <<<<<<<<<< ON THE MOXA DEVICE Hope helps Regards Alvaro On 6/1/12, Cezary Siwek wrote:
> Hi,
> Long time ago I’ve been playing with a regular serial modems + terminal
> server.
> The terminal server exposes each modem on a different tcp port. In the
> kannel you use either ‘rawtcp’ or ‘telnet’ smsc type.
> It worked fine for a several years.
> Regards,
> Cezary
> On 01/06/2012 10:57, Peter Valdemar Mørch wrote:
>> Hi,
>> We’ve been using Falcom and Tango modems in the past, but they’ve been
>> difficult to buy lately. Instead we’re considering buying “Moxa
>> OnCell” or “Siemens MC35i” (which appears to be identical to
>> “Cinterion MC35i”).
>> Now that we’re looking to test and buy new modems anyway, we’d love
>> some that work better in VMware ESX environments where access to
>> serial ports isn’t possible. All the above modems except the “Moxa
>> OnCell” are accessed via a serial port.
>> E.g. something that holds a SIM card, has an IP address and provides
>> an SMPP interface would be perfect, but I realise I’m a novice in this
>> field.
>> So far in VMware, we’ve been setting up Moxa Serial Device Servers (
>> http://www.moxa.com/product/Serial_Device_Servers.htm ) that via a
>> kernel module in the ESXi virtual host provide access to a
>> pseudo-serial port. That is flaky at best. The “Moxa OnCell” also
>> needs a kernel module, and we haven’t yet had success with it.
>> I’ve read http://kannel.org/compatibility.shtml but I haven’t been
>> able to find a vendor for any of the “Phones that works as SMSC’s with
>> Kannel”. At least two of the three are no longer being produced, but I
>> think they all used serial port access, and so don’t work so well
>> under VMware.
>> So in short, I’m looking equipment/solutions recommendations that
>> allow us to send SMSes from both real hardware and VMware ESX guests
>> using our own SIM card (not a remote hosted solution), using hardware
>> that is still current and in production and without kernel
>> modules/patches.
>> Does such equipment exist? What do you recommend?
>> Thank you for reading this far.
>> Peter

Thomas Challenger Thomas Challenger