Mobiboo wishes to provide the ability to it’s customers to send SMS and ideally MMS text messages to each other (on net) initially with the correct interface to talk to the existing API’s already in existence for sending/ receiving text messages to and from GSM networks.
In basic terms a user will create a 160 character SMS text message or take a photograph perhaps and create an MMS message and we need to get this to another users’ handset. All Mobiboo mobiles have a real phone number of 079112XXXXX attached to them which is a UK issued mobile number range. The mobiboo phones authenticate on our SIP registry allowing users to use them wherever they have WiFi signal. The protocol being used is SIP.
I am not sure that anyone has developed any SMSC before for SIP. If they have then we would wish to comply with any sensibly existing standard otherwise create a new standard called SIP-SMPP
The deliverables will be in two stages:
A fully working SMSC which allows short messages (as defined in the GSM specifications - SMS & MMS) to be sent between mobiboo phones via SIP with ability to send to other SIP (non GSM) phones by creating additional API's.
I am not sure what the SIP SMS messaging standards are at the moment, or if in fact there are any. GSM uses SMPP (Short Message peer-to-peer Protocol).
The **short message peer-to-peer protocol (SMPP)** is a telecommunications industry protocol for exchanging SMS messages between SMS peer entities such as short message service centres. It is often used to allow third parties (e.g. value-added service providers like news organisations) to submit messages, often in bulk.
SMPP was originally designed by Aldiscon, a small Irish company that was later bought by Logica. In 1999, SMPP was formally handed over to the SMPP Developers Forum, later renamed as The SMS Forum.
The protocol is based on pairs of request/response PDUs (protocol data units, or packets) exchanged over OSI layer 4 ([TCP]/[IP] session or [url removed, login to view] SVC3) connections. PDUs are binary encoded for efficiency.
The most commonly used versions of SMPP are v3.3, the most widely supported standard, and v3.4, which adds transceiver support (single connections that can send and receive messages). Data exchange may be synchronous, where each peer must wait for a response for each PDU being sent, and asynchronous, where receiving and transmitting go in independent threads with the use of buffers and timers. The latest version of SMPP is v5.0.
This is an example of a 60-octet *submit_sm* PDU...
00 00 00 3C 00 00 00 04 00 00 00 00 00 00 00 05 00 02 08 35 35 35 00 01 01
35 35 35 35 35 35 35 35 35 00 00 00 00 00 00 00 00 00 00 0F 48 65 6C 6C 6F
20 77 69 6B 69 70 65 64 69 61
'command_length', (60) ... 00 00 00 3C
'command_id', (4) ... 00 00 00 04
'command_status', (0) ... 00 00 00 00
'sequence_number', (5) ... 00 00 00 05
'service_type', () ... 00
'source_addr_ton', (2) ... 02
'source_addr_[npi]', (8) ... 08
'source_addr', (555) ... 35 35 35 00
'dest_addr_ton', (1) ... 01
'dest_addr_[npi]', (1) ... 01
'dest_addr', (555555555) ... 35 35 35 35 35 35 35 35 35 00
'esm_class', (0) ... 00
'protocol_id', (0) ... 00
'priority_flag', (0) ... 00
'schedule_delivery_time', () ... 00
'validity_period', () ... 00
'registered_delivery', (0) ... 00
'replace_if_present_flag', (0) ... 00
'data_coding', (0) ... 00
'sm_default_msg_id', (0) ... 00
'sm_length', (15) ... 0F
'short_message', (Hello wikipedia) ... 48 65 6C 6C 6F 20 77 69 6B 69 70 65 64 69 61'
* the details regarding SMPP are available at [[url removed, login to view]]
* an [open source]implementation of an SMPP gateway is available at [[url removed, login to view]]
* [SMS/MMS Resources]
_**Additions to the SMSC to allow send/ receive to/ from GSM networks, using exisitng industry interfaces such as MBLOX and MXTelecom.
* 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done.
2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables):
a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment.
b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request.
3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement).
This will need to operate on a linux Platform.