Name Modified Size Downloads / Week Status
v3.10 2014-10-02 0
v3.0 2014-10-01 0
v2.0 2013-01-02 0
2nVoivceBlueSMS_3.10.tar.gz 2014-10-03 42.0 kB 0
README 2014-10-02 6.5 kB 0
INSTALL 2014-10-02 2.0 kB 0
CHANGELOG 2014-10-02 576 Bytes 0
2nVoivceBlueSMS_3.00.tar.gz 2014-10-01 40.9 kB 0
2nVoivceBlueSMS_2.03.tar.gz 2013-01-11 39.7 kB 0
Totals: 9 Items   131.7 kB
Full featured HTTP SMS service for 2n VoiceBlue (Next) GSM VoIP adapters with sending and receivig capabilities. Telnet or serial communications are available. GitHUB project: https://github.com/ttobi/2n-sms-server The service periodically checks the incoming SMS-es on the VoiceBlue adapter then stores in a local SQLite database. It can communicate via telnet, you can switch telnet off with USE_TELNET = False/True. If USE_TELNET = False, it will try to connect ONLY on serial (ttyUSB) ports (older VoiceBlue devices, but telnet preferred). The HTTP REST service listens on a defined HTTP port (default 8080) and controllable via simple POST/GET calls. (In case of GET call the message should be URL encoded.) The HTTP responses from the service are simple XMLs for easy to use and parse. For details, control functions, output XML templates, please read the README document. There is a basic Apache+PHP WEB frontend available to control the service. VoiceBlue AT commands reference: https://wiki.2n.cz/display/VBN30EN/4.2+AT+Interface DEPENDENCIES: - Python > 2.7.x - Python-Messaging https://github.com/pmarti/python-messaging PREFERRED way to install Python-messaging module: cd ~ git clone https://github.com/pmarti/python-messaging.git cd python-messaging sudo python setup.py install OPTIONAL: For serial communication: - Python-serial 2.5 > http://sourceforge.net/projects/pyserial/files/pyserial/2.5/pyserial-2.5.tar.gz/download BASIC USAGE EXAMPLE: 0.) edit config variables below: # CONFIG START section 1.) start HTTP server on port: ./[program name] [server port] (default:8080) (root user requitred ONLY for serial communictaions) 2.) sending SMS: use a HTTP browser to call the server via GET method: http://[host address:port]/?rcpt=[full tel. number of recipient]&msg=urlencode([155 character sms])&smsc=[our telco's sms center full number (with + and country code, eg: +36...)] 3.) receiving SMS messages: http://[host address:port]/?action=listall Licensed under GPL v2: http://www.gnu.org/licenses/gpl-2.0.html ------------------------------------------ DETAILED CONFIG ------------------------------------------ For configuration, please edit the 2nVoiceBlueSMSServer.py file "CONFIG section." SIMCARDSINUSE: how many SIM card installed on yout device. (0,1,2,3) SQLITE_PATH: the local SQLite database path, the server will creates it if not exist. The sent and received SMS-es stored here. IMPORTANT: the server deletes the SMS messages from the SIM cards after it fetched and stored in teh SQLite database. LOGFILE: the detailed log output of the server LOG_TO_LOGFILE: if you need ONLY print to CLI, use False here SERPORT: basic serial USB path root, without number! of the device, at startup, the server try to connect from ttyUSB[0] to ttyUSB[10] SERBAUD: baud rate for 2n device, fixed : 921600, do not change it! PORT: the HTTP server default port to listen on SMSC: default telco's SMSC number. It can be pass via HTTP GET also, but you can set it up. Can be fetched from the SMS, Message settings, or from the Internet. SIMPOLLINTERVAL: the server periodically polls the SIM cards in the device, fetches the SMS messages then stores in the local db, the poll interval in seconds #telnet settings USE_TELNET: True: use telnet to connect VB device, it is the default, False: try serial ports TELNET_HOST: telnet hostname or IP of VoiceBlue modem TELNET_PORT: telnet port TELNET_USER: Voice Blue modem user TELNET_PASSWORD VoiceBlue modem password TELNET_TIMEOUT: the telnet command timeout USE_GSM_MODEM: True/False, workaround for CMS: 500 internal error, use GSM modem directly, workaround for Voice Blue Next devices, keep it True ------------------------------------------ HTTP COMMUNICATION, GET/POST CALLS AND RESPONSES ------------------------------------------ -------------------------- SMS SENDING via POST/GET: -------------------------- example: rcpt: recipient phone number msg: SMS message body, max 155 chars, accents removed. To avoid encoding problems, it should be urlencoded in case of GET. smsc: SIM's telco's SMS center number, not required if given at the config above. Response XML: ------------- <response type="send"> <status>[OK|ERROR]</status> <date>[datetime]</date> <-- datetime format: YYYY-MM-DD hh:mm:ss --> <id>[individual SMS ID]</id> </response> -------------------------- SMS FETCH via POST/GET: -------------------------- example: action: listall (list all plus deleted SMS messages stored locally) list (list only not deleted SMS messages) listdel (list deleted SMS) listrec (default / list only received - incoming - SMS messages) listrecdel (list deleted received messages) listsent (list sent - outgoing - messages) listsentdel (list received deleted messages) listqueue (list queued messages for sending - not sent yet) listerr (list of messages with sending errors occured) Response XML: ------------- <response type="receive"> <sms> <id>[SHA1 hash id of SMS]</id> <smsdate>[sent/received datetime]</smsdate> <lastdate>[datetime of message modification - queued -> sent, error]</lastdate> <cardnum>"[SIM card number: 0|1|2|3]</cardnum> <fromnum>[sender number - only incoming messages | None]</fromnum> <tonum>[recipient's number - only sent messages | None]</tonum> <status>[queued | sent | senderror | received]</status> <deleted>[yes | no]</deleted> <msg><![CDATA[ - message body - ]]></msg> </sms> </response> -------------------------- SMS DELETE via POST/GET: -------------------------- example:[SMS id - hash] action: delete id: SHA1 hash (40 chars long ID) Response XML: ------------- <response type="delete"> <status>[OK|ERROR]</status> <date>[datetime]</date> <-- datetime format: YYYY-MM-DD hh:mm:ss --> <id>[individual SMS ID]</id> </response> -------------------------- TRUNCATE DELETED SMS FROM DB via POST/GET: -------------------------- example: action: truncate Response XML: ------------- <response type="truncate"> <status>[OK|ERROR]</status> <date>[datetime]</date> <-- datetime format: YYYY-MM-DD hh:mm:ss --> <pcs>[number of truncated messages]</pcs> </response> -------------------------- INSUFFICIENT RESPONSE: -------------------------- <response type="error"> <error>insufficient request</error> </response> For install instructions please check INSTALL file.
Source: README, updated 2014-10-02

Thanks for helping keep SourceForge clean.

Screenshot instructions:
Red Hat Linux   Ubuntu

Click URL instructions:
Right-click on ad, choose "Copy Link", then paste here →
(This may not be possible with some types of ads)

More information about our ad policies

Briefly describe the problem (required):

Upload screenshot of ad (required):
Select a file, or drag & drop file here.

Please provide the ad click URL, if possible:

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.

No, thanks