XL Studio v 3.4
SMS Plug-in for Microsoft Excel®.

“Time saved is money earned”.

If you have Microsoft Excel®, send direct bulk SMS with it. If you too believe, that saving time by utilizing it to the maximum will enhance your working; then this offer is best suited to you. No matter what profession you are into, reaching out to a wide base of people is a part of it. And if you want to do this in a matter of a few seconds - XL Studio 3.4 is what we have to offer. It is easy to use software that will help you to reach out to a number of people directly.

Mass SMS service:
Operator puts a message in the database -> this triggers a trigger which determines who to send to and calls the gateway with the proper parameters ->the gateway parses the message that comes from the database byte by byte and replaces each Arabic character with the proper ascii replacement -> the gateway now determines which operator(s) to send to -> the messages are sent to the operator Short Message Central or SMC which in turn transmits them to each cell phone.

Service request SMS service:
User sends a request to your service number with some kind of message -> the gateway parses the message and replaces each designated ascii character with the proper Arabic character -> the message is stored in the database -> a trigger gets triggered by this and alerts:

1.) Another software that can deduce from the contents of the message what to answer and stores the answer in some table which in turn triggers another trigger so the reply gets sent back to the user. Examples are weather and stock quotes.

2.) Instead of another software it is a human that sees the message and sends an appropriate message back. Examples are super premium services like personal horoscopes or why not booking a table at a restaurant.

Mass SMS service:
Operator puts a message in the database -> this triggers a trigger which determines who to send to and calls the gateway with the proper parameters ->the gateway parses the message that comes from the database byte by byte and replaces each Arabic character with the proper ascii replacement -> the gateway now determines which operator(s) to send to -> the messages are sent to the operator Short Message Central or SMC which in turn transmits them to each cell phone.

Service request SMS service:
User sends a request to your service number with some kind of message -> the gateway parses the message and replaces each designated ascii character with the proper Arabic character -> the message is stored in the database -> a trigger gets triggered by this and alerts:

1.) Another software that can deduce from the contents of the message what to answer and stores the answer in some table which in turn triggers another trigger so the reply gets sent back to the user. Examples are weather and stock quotes.

2.) Instead of another software it is a human that sees the message and sends an appropriate message back. Examples are super premium services like personal horoscopes or why not booking a table at a restaurant.

Also clarification on the above: When I said it won’t make sense in the ascii range I meant the first byte in each Arabic character.

Jean: You have to check the spec for the version of smpp/emi(upc) that you will be using and how the operator you will be working with encodes arabic. I had this problem with special German characters.

The solution is that you have to map them by replacing normal ascii characters, if the versions you will be working with won’t allow for double byte character encodings. I had to work with GSM7 when I mapped special German characters. After you have your mapping tables finished you will probably have to store your arabic characters as double bytes in the PostgreSQL database.

Be very careful now because PostgreSQL stores the characters in a mixed single and double byte sequence. Arabic will probably be mapped to values that won’t make sense in the ascii range, that is how you can get to them. Your code has to realize that aha this is not an ascii character, but what character is it then? Look up in the Arabic to for instance GSM7 table, aha that arabic character will replace for instance “{”, so we put an “{” in the SMS message instead and everything should be fine.

I hope I made sense?