无奈

当人与人之间的相处有一段时间后, 可能因了解而产生的误会也就会随之而来.
近期内的争执变多了...相信你我都能感受得到.
或许我真的有时在别人分享心情前, 就把自己的看法说出来是不对.
但, 我也是因为在乎, 才希望能开解对方.

对我而言, 帮助人需要某些程度上的基本限度.
要认为这些帮助是否需要.
如果一个人完全没为自己的未来策划, 而一直期待别人的帮忙, 这些人帮得下吗?
并不是别人有这种能力我们就应该要求他人的帮助.
我们须想想, 我们要求的帮助是必须的吗?
所以我一直以来都提倡一个观念, 没那么大的头, 别带那么大的帽子.

但这一切, 我都没权利管, 也不想要管.
希望不会因一次的帮忙而引来未来无限的需求吧?

人生, 就是永远那么无奈.

梦想的起飞 - 台湾环岛14天 (序)

梦想的起飞

人生因梦想而变得有意义,
因有目标而变得更加努力.

回想为何会对宝岛台湾有兴趣...
应该是在fridatan与我的朋友去台北以后开始的.
或许我有更大的理想, 那就是环岛.
研究下去, 才发现原来台湾有那么多特别的民风, 景色.

以下是我得到资料的一些网站::
1) 背包客棧自助旅行論壇
2) 旅遊人生
3) Mobile01
4) http://taiwan.wcn.com.tw/b5/
5) http://trip.wts.com.tw
6) http://www.taiwanfun.com
7) http://travel.network.com.tw/main/travel/default.asp
8) http://www.nightfair.com.tw/index/default.asp
9) http://youthtravel.tw/index1.php

以下是一些筹备时的台湾书籍::



从决定要去台湾到真正去台湾, 大约是相隔半年的时间.
还记得, 那时我很兴奋告诉朋友自己将会去台湾,
但到最后眼见朋友一个一个的都去了回来, 自己还在等着旅游展的到来.....
当然, 在着急等待中, 时间已渐渐的流失,
旅游展也随着到来.

或许太多选择, 因此到真正决定要买机票时,
evaair, 华航等比较便宜的航空公司的票已被一扫而空.
迫不得已下, 只好买了比较贵的国泰航空的机票.
12月22日傍晚出发, 1月5日从台北回来.
决定以十四天环岛游台湾.

票已买了...那就只有更努力的做研究, 以便篇排更完美的行程表.
幸得网友热情的解答, 行程表终于出来了.
大约11月尾, 我们便开始预订所有的住宿.
由于我们去的时间是旅游的旺季,所以我们对住宿的预留不敢掉以轻心.
谁都不想在台湾睡街头嘛.

一切都准备好后, 就开始倒数, 等待日子的到来了.

虽然台湾岛并不太大, 但是要在14天内环绕台湾岛一圈, 并不是件太容易的事.
虽然行程表有些许赶, 但很庆幸的, 还是完成它了:P
以下是我的行程地图(红线)::

台北 -> 日月潭 -> 台中 -> 阿里山 -> 台南 -> 高雄 -> 花莲 -> 台北

台湾14天游记

花了差不多一年的时间, 终于把台湾游记写完了..
真的很慢也需要很多的耐心.

如有兴趣可到
http://chinese.cari.com.my/myforum/viewthread.php?tid=750545&extra=page%3D1

Setting Up Websphere MQ Server

1) Create a queue manager

crtmqm -q queue.manager.1

-q is make the queue manager become default queue manager

2) Start queue manager

strmqm

3) Start MQSC

runmqsc

- doesn't provide a prompt, but will show Starting MQSC for queue manager queue.manager.1.

4) Create a local queue called queue 1

define qlocal(QUEUE1)

5) At MQSC Windows

a) define a server connection channel
define channel(channel1) chltype(svrconn) trptype(tcp) mcauser(' ')

b) By default will listening to port 1414, to change:
alter listener(system.default.listener.tcp) trptype(tcp) port(2001)

c) to check busy port
netstat -an

d) Start default Websphere MQ Listener
start listener(system.default.listener.tcp)

e) Verify the listener has been started by
display lsstatus(*)


f) Stop MQSC by
end

With this...following object has been created
1) default queue manager queue.manager.1
2) local queue called QUEUE1
3) Server connection channel called CHANNEL1

C++ Copy File Function

CopyFile Function

This function is used to copy a file from a path to another file location/path.

The structure of the function as follow::

BOOL WINAPI CopyFile(
IN LPCSTR lpExistingFileName,
IN LPCSTR lpNewFileName,
IN BOOL bFailIfExists
);

Where::
lpExistingFileName is the source file location
lpNewFileName is the location where the file copy to
bFailIfExists is to set to replace or not.

bFailIfExists == true
The file won't be replaced.
bFailIfExists == false
The file will be replaced.

How to use RPM

In its simplest form, RPM can be used to install packages:

rpm -i foobar-1.0-1.i386.rpm

The next simplest command is to uninstall a package:

rpm -e foobar

One of the more complex but highly useful commands allows you to install packages via FTP. If you are connected to the net and want to install a new package, all you need to do is specify the file with a valid URL, like so:

rpm -i ftp://ftp.redhat.com/pub/redhat/rh-2.0-beta/RPMS/foobar-1.0-1.i386.rpm

Please note, that RPM will now query and/or install via FTP.

While these are simple commands, rpm can be used in a multitude of ways. To see which options are available in your version of RPM, type:

rpm --help

You can find more details on what those options do in the RPM man page, found by typing:

man rpm



  

GDB - Code Debugger in Linux Enviroment

GDB is a tool for developer to debug the software when in Linux enviroment.

Run your application in debug mode
------------------------------------
1) gdb [application_name]
2) to set a break point
a) b [function_name]
b) b [document_name]:[line_number]
3) Start the application
run
4) Next line when in debug mode
n
5) Continue running when debug mode
c
6) Exit Debug Mode
q

Debugging Core Dump File
---------------------------
1) gdb [application_name] [core_dump_filename]
2) Debug the dump segment
b
3) Look into the dump segment
frame [segment_number]
4) Exit the debug mode
q

TCAP Erro Message

ERRORS {
-- systemFailure -- localValue 34,
-- dataMissing -- localValue 35,
-- unexpectedDataValue -- localValue 36,
-- facilityNotSupported -- localValue 21,
-- unknownSubscriber -- localValue 1,
-- teleserviceNotProvisioned -- localValue 11,
-- absentSubscriber -- localValue 27,
-- callBarred -- localValue 13}

TCAP SRI_SM Response Messge Decode

SRI_SM TCAP Message Decode
==========================

Dialogue Request
----------------
Original Message
I00 M tc783 iffff f2d d14 s00 p0400

******Decode Parameter Field******
END Dialogue Ind
04
Msg End Ind
00


Component Request
-----------------
Original Message
I00 M tc781 iffff f2d d14 s00
p09011EA21C020100301702012D301204031032F4A00B810913079188966310406000

******Decode Parameter Field******
Result Successful
09
Component Portion
01
1E
A21C020100301702012D301204031032F4A00B8109130791889663104060
Msg End Ind
00

******Decode Component Portion******
Return Result Last Ind
A2
Component Portion length
1C

Invoke ID Portion
Invoke ID Ind = 02
Invoke ID Length = 01
Invoke ID Value = 00

Result Portion
Result Ind = 30
Result Length = 17
Result Value = 02012D301204031032F4A00B8109130791889663104060

******Decode comp Portion******
Operation Code Portion
02
01
2D
Result Portion
30
12
04031032F4A00B8109130791889663104060

******Decode Result Portion******
IMSI Portion
04
03
1032F4
Network Number Portion
A0
0B
8109130791889663104060

Alert Subscriber (ALERT_NOTIFICATION)

Alert Subscriber
-------------------

Alert subscriber message usually was sent when the user didn't switch on the mobile phone. It was received by SMSC and will store to the database and wait for send retry.

MOBILE USER(off) ---- (ALERT_NOTIFICATION) ----> MAPSMS ----> MTSL ---->Database

There will be another mechanism to query out the retry table sms and send it out trough mapsms.

Database -----------> Message Dispatcher --------> Mapsms -------> Mobile User

* There no response message needed for the alert notification message.

Global Title Translation

Global Title Translation

A Global Title (GT) is an address used in the SCCP protocol for routing signaling messages on telecommunications networks. In theory, a global title is a unique address which refers to only one destination, though in practice destinations can change over time.

GTES
- will change according to the length of the GT Address.
- If the length == odd number, then set GTES to 1
- If the length == even number, then set GTES to 2

for MO_SM
- will be using remote service centre address(RSC_SCCP_ADDR) as the GT Address value.

for MT_SM
- will be using msc address as the GT Address value

for SRISM
- will be using the HLR SCCP Adreess as tyhe GT Address value.

TCAP : Long SMS Handling

TCAP Layer Long SMS Handling

Long sms handling for tcap layer would be like follow

-> DLG_BEGIN + EMPTY_COMP
<- DLG_CONTINUE + EMPTY_COMP
-> DLG_CONTINUE + INVOKE_COMP
<- DLG_END + ResultLast_COMP

- Whenever a long sms is send, it will send by a dialogue begin and a empty component.
- The receiver will need to response by sending a continue dialogue and a empty component.
- After the continue dialogue is sent, the sender will start sending the message content by sending continue dialogue and a invoke component.
- After receiver received, it will response a end dialogue and the resultlast component.

MO_SM and MT_SM : Address Defination

MO_SM
-----------
-When mobile user submit_sm to mapsms, so it msisdn would be the originating address(sm_rp_oa).
- The message will send to SMSC, so the service centre address would be the destination address(sm_rp_da).
- The destination address would pack to the sm_rp_ui.

Service Centre Address
- Own mapsms address
- pack to sm_rp_da

MSISDN
- Message Source Address
- pack to sm_rp_oa

sm_rp_ui
- pack in message destination address

- MO_SM message will not need to send SRISM to the message service center.


MT_SM
----------
- Whenever mapsms wish to send an deliver_sm, the originating address would be the service center address.
- The destination address would be retrieve from the srism process to get the destination imsi.
- the sm_rp_ui user information would pack in the msisdn(source addresss).

Service Centre Address
- would be the mapsms own address also.
- will be pack to the sm_rp_oa

MSISDN
- would be the message source address
- will be pack to the sm_rp_ui

sm_rp_da
- will be using the destination imsi.
- the destination imsi was get from the srism request.

- MTSM would need to send SRISM to get the route information.