Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>My answers are based on .<a href="http://www.smsforum.net/SMPP_v3_4_Issue1_2.zip" rel="nofollow" title="SMPP 3.4 spec">SMPP 3.4 spec</a></p> <p>===</p> <p>I am assuming that your setup looks like this:</p> <ol> <li>You are developing SMPP client (a.k.a. ESME).</li> <li>You have connectivity information to a SMPP server (a.k.a. SMSC).</li> </ol> <p><em><strong>Question 1: What details are required to connect to a smpp server.</em></strong></p> <p>At bare minimum, a ESME needs the following to connect to a SMSC (required at TCP level):</p> <ol> <li>IP of SMSC</li> <li>Port of SMSC</li> </ol> <p>Most SMSC will also require (but this is not mandatory):</p> <ol> <li>system_id (serves as username)</li> <li>password</li> </ol> <p>Some SMSC will also require:</p> <ol> <li>system_type (see section 4.1.1 in SMPP 3.4 spec)</li> <li>address_range (see section 4.1.1 in SMPP 3.4 spec)</li> </ol> <p><em><strong>Question 2: should the code files be deployed on Smpp server or can it be deployed to a different server and try to access the smpp server to send the message.(We did try to connect to the smpp server via filezilla but it was unsuccessful)</em></strong></p> <p>SMSC (i.e. SMPP server) and ESME (i.e. SMPP client) are not required to be on the same box; you can do if you want. Only requirement is that they can connect over TCP.</p> <p>I believe FileZilla is a FTP client and it has got nothing to do with SMSC.</p> <p><em><strong>Question 3: is from number manadatory when we are trying to send a message from system to a mobile.</em></strong></p> <p>I am assuming that you are using SUBMIT_SM to send a message (since you are trying to connect via BIND_TRANSMITTER).</p> <p>In the spec, the <strong>from number</strong> is referred as <strong>source_addr</strong> (see section 4.4.1/5.2.8 in SMPP 3.4 spec). Most SMSC will require <strong>source_addr</strong> however it is not mandatory.</p>
 

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