|
|
| SMS Server Tools 3 Community |
| Welcome, Guest. The forum is currently read-only, but will open soon. |
Fri Mar 14, 2025 10:44 |
Page: 1
| Keywords: Mode: All keywords (AND) |
|
Fri Jul 29, 2011 10:41
|
gaio: Probably i've missed something... sorry, i'm not used to forums, i prefer using BTS and lists.
Now i've seen there's a ''private block'' but really i don't know how to use it.
But... in the meantime, for other reasons, i've exchanged my 2n VoiceBlue lite with an 2n OfficeRoute, that have a SMS2mail internal gateway, so i'm using that for now.
Surely i was not known that keke build me a ''custom'' version. sorry.
Worster, i'm going to holidays, for 4 weeks, so... is someone (eg, dieug) in the meantime can do some tests...
|
|
Mon Nov 01, 2010 15:05
|
gaio:
"Simple poll" surely has been working with your perl script, there is no doubt about it. SMSTools3 could also use "simple polling", but it is not enough because there are more than one processes which need to handle the same interface. This cannot be done simultaneously, which means that there should be some kind of "scheduling" for usage of the interface, or multiplexer.
Sure, muxing is needed, but consider that every reply from the GSMBox report contain the SIM or group that generate the event, and there's also a sort of ''index'' number, so if you expect a reply you can correlate.
On the other hand, as you already have the script, why not to continue with it in the future too?
Sure, for now i will do that, probably with a simple (ok, stupid ;) perl daemon that receive PDU and send them.
Again, thanks,
|
|
Thu Oct 28, 2010 07:57
|
gaio:
The "simplified interface" is also "very limited" interface, which allows only single modem to be used at a time. Missing features, like signal quality, registration status, phonecalls etc.. likely are not a problem. What SMSTools3 will need, is a MUX device (like a modem process) which talks with the Gateway and places incoming messages to the shared memory of appropriate modem process, and gets outgoing messages and sends them using the correct modem. Basically it's not very complicated to code, but many other things should be handled too. For example, if there are four processes sending messages, and 2N can handle only one modem at a time, there will be long delays and timeouts should be changed. And if smsd is stopping when a message is not yet sent, it should be handled properly. And so on...
I've not understood (really: never tried to... ;-) how SMSTools3 works, but in my experience a simple poll (connect, send PDU data, wait for error or ok) do the job. For MUXing, consider also that you can define a group in the GSMBox and send messages to the group: it is the box itself that muxes messages between the SIM...
I have to think what to do with this 2N Gateway, but right now I do not promise anything. If I add 2N specific features to the SMSTools3, those features should be supported in the future too. It may be slightly difficult, because I do not even have this kind of a 2N Gateway...
As just stated in private email, if you need i can provide support for this...
|
|
Mon Oct 25, 2010 13:33
|
gaio: I've just post http://smstools3.kekekasvi.com/topic.php?id=454, also i own a 2n devices (a VoiceBlue Lite) and for me the solution is using the ''simplified PDU mode''.
That probably need specific coding in SMSServer3... ;-(((
|
|
Mon Oct 25, 2010 13:30
|
gaio: I've buyed a 2n (http://www.2n.cz/en/) GSM gateways, exactly the VoiceBlue Lite (4 port, http://www.2n.cz/en/products/gsm-gateways/voip/voiceblue-lite/) mainly as a ''GSMBox'' use, but i've tried to experiment in sending SMS.
For now i'm experimenting using a bit of perl and expect perl module, butwill be cool to use SMSServer3!
Reading the manual (http://www.2n.cz/download/2/0/3/vbl-manual-2.6.pdf) and poking around seems that my gateway was simply a ''wrapper'' built around four Siemens/Cinterion MC55i modules (http://www.m2mportal.ru/lib/mc55i_atc_v01201.pdf).
The box have ethernet, usb and rs-232 connectivity, AFA the manual say, all export the same AT-command interface.
Reading the manual i've also understood that there's substantially two modes of sending SMS.
1) using an AT ''prefix'' command that send the AT command directly to the specific GSM interface, eg:
AT&G0=ATI
send the command ''ATI'' to the first MC55i module; i've successfully send some message using this, but was proven to be very unreilable, or i was really ignorant about SMS AT commands...
2) using a simplified interfaces provided by the box itself; the interface works entering in ''SMS mode'' with AT!G=A6, then working with SMS with only 5 commands (list, read, delete, send to module or to group of modules) that accept only PDU data. Then you have to exit from SMS mode with AT!G=55.
This mode works flawlessy (again, with my AT command and perl knowledge...).
Seems to me that SMSTools3 can be use mode 1) with little or no modification, but probably require major sessions of debugging and trial and error to made reilable.
I think that mode 2) will work, but require the writing of specific code (even if simpler and not complex one, AFAIK).
Reading other forum seems to me that all 2n devices behave similary, so probably implemementing ''simplified PDU mode'' would support all 2n devices, or at least most.
Unfortunately my GSM, SMS and C language knowledge are very poor...
|
Page: 1
Time in this board is UTC.
|
|
|
 |
|
|
 |
|
