Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I assume that by IN you mean <a href="http://en.wikipedia.org/wiki/Intelligent_network" rel="nofollow noreferrer">Intelligent Network</a>? Usually IN is not relevant for sending/receiving SMS messages - you need to connect to the <a href="http://en.wikipedia.org/wiki/Short_message_service_center" rel="nofollow noreferrer">Short Message Service Center</a> (SMSC) (or some proxy/gateway) in order to do that.</p> <p>As also pointed out by Bombe, there are several protocols that you can use to connect to the mobile operators SMSC, it is all quite vendor-specific, due to historic reasons. Common protocols are:</p> <ul> <li><a href="http://en.wikipedia.org/wiki/SMPP" rel="nofollow noreferrer">SMPP</a> (most popular, becoming the de-facto standard). There are two SMPP java libraries: <ul> <li><a href="http://sourceforge.net/projects/smppapi" rel="nofollow noreferrer">SMPP API at SourceForge</a> - very stable and mature library, I have personally used it in several projects and can recommend it. </li> <li><a href="http://opensmpp.logica.com/" rel="nofollow noreferrer">Logica OpenSMPP</a> - library from the company that developed the SMPP specification. I have never used this, so I cannot comment on its maturity or stability.</li> </ul></li> <li><a href="http://en.wikipedia.org/wiki/Universal_Computer_Protocol" rel="nofollow noreferrer">UCP</a> (<a href="http://www.nowsms.com/discus/messages/1/EMI%5FUCP%5FSpecification%5F40-8156.pdf" rel="nofollow noreferrer">specification</a>) - quite old standard. I'm not aware of any open java libraries for this protocol. However, as it is all ASCII-based, it is fairly easy to implement yourself (as long as you like messing with bytes :-)).</li> <li><a href="http://en.wikipedia.org/wiki/CIMD" rel="nofollow noreferrer">CIMD2</a> - specification for communicating with Nokia SMSCs. It is becoming legacy, as I have heard that newer Nokia SMSC releases also support SMPP. No known open java libraries for this either.</li> <li>and finally, there are gazillions of custom protocols implemented to make it "easier" for 3rd-party developers to connect to SMSCs. These are usually based on HTTP and XML (SOAP, if you are lucky).</li> </ul> <p>To sum up, the choice of protocol is not yours to make. It is usually dictated by the SMSC vendor or the mobile operator (in case they have developed some sort of "proxy/gateway", to shield their SMSC from potential programming errors that external developers can make).</p> <p>P.S. in case you are not limited to java, you can also have a look at <a href="http://www.kannel.org/" rel="nofollow noreferrer">Kannel - the Open Source WAP and SMS gateway</a>. I have not used it myself, but as far as I have heard, they should have all major protocols covered.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload