SMPP - SMSC

SMPP - SMSC SearchSearch
Author Message
Anonymous
 
Posted on Wednesday, June 23, 2004 - 02:19 am:   

Our operator wont next Scheme for services.
Server get SMS via SMPP and not response SM_SUBMITSM_RESP, server send completly processing SMS our services and send it abonent. Then wait Notice of delivery, then response SM_SUBMIT_RESP via SMPP. It is possible? It will possible in next version on your product?
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 2901
Registered: 10-2002
Posted on Friday, June 25, 2004 - 04:00 pm:   

Hi,

Do you mean that your service provider does not return an SMPP Submit Response until after it has actually delivered the message?

That is highly irregular.

Without some type of response, we cannot know if the message submission was successful.

We have been looking at adding sliding window support to the SMPP implementation. However, even with that, the intent would be to send "x" messages, and not to send more until some messages were acknowledged. (And "x" would likely be a relatively small number such as 3 to 5.)

Are you sure that your operator works as you describe? If the recipient is off-line, it could be several hours (or days) before the message is delivered. That is a long time to wait for an acknowledgement.

-bn
Anonymous
 
Posted on Monday, June 28, 2004 - 05:09 am:   

My operator, want nexttehnical issue for smpp session:
SMSC: SUBMIT_SM (comand id 1)
I: working for SMS and generate request
I: SUBMIT_SM
SMSC: SM_SUBMIT_RESP
I: SUBMIT_SM
SMSC: SM_SUBMIT_RESP
..........
And I wating for delivery report, then I need sent SMSC for comand id 1
I: SM_SUBMIT_RESP

My operarotr want this sheme only!
Sory for my bad english.....
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 2922
Registered: 10-2002
Posted on Monday, June 28, 2004 - 06:57 pm:   

Normally, your operator would be sending a DELIVER_SM ... and you would be responding with DELIVER_SM_RESP. (Assuming that you are connected to the SMSC as a client.)

Are you saying that you do not want to generate the DELIVER_SM_RESP until you have actually processed the message? Unfortunately, we do not have a way to facilitate this. And I'm not sure how we would do this.

Do you know why this is required for your setup?
Azizul Haleem
New member
Username: Mazizh

Post Number: 1
Registered: 06-2004
Posted on Thursday, July 01, 2004 - 02:39 pm:   

Hi,

My company has purchased Value SMS Service from local SMS provider and they are giving SMSC through SMPP/TCPIP in that service they are giving one Static IP & Receiving port i.e. 4 digit port like 6611 , so if any local user will send SMS to 6611 then it will come to their Service Center and through SMPP/TCPIP we‘ll receive it in our office, Can any one tell me please how can I configure that SMSC Type in NowSMS Software on my server to receive and store all SMSs in database to display reports accordingly. My server has Windows 2000 advance server , SQL Server 2000 & IIS 5.0 and NowSMS Software V5.50 installed.
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 2983
Registered: 10-2002
Posted on Wednesday, July 07, 2004 - 07:49 pm:   

Hi Azizul,

I also replied to your query via e-mail, but will post my reply here as well. (Apologies for the delay in response.)

The configuration of an SMPP connection in NowSMS is relatively simple. On the "SMSC" page of the NowSMS configuration dialog, you need to add an SMSC connection of the "SMPP over TCP/IP" type.

Usually, you will need to specify the host name or IP address of your provider's SMPP server, and the port number that they are using. You will also need to configure a username and password. The other parameters are optional, and may only be required if there are specific requirements of your mobile operator. The default settings work with most operators. (If you experience problems making the connection, we can help you troubleshoot.

Also, it helps if you can forward us any information your provider gives you about your account ... different providers often use different terminology, so we can help you translate that into the settings that need to be
configured in NowSMS.)

The following link explains the SMPP parameters:

http://www.nowsms.com/documentation/ProductDocumentation/configuring_smsc_connec tions/SMPP_SMSC.htm

Regarding the actual receiving of messages, and logging them into a database, you would need to supply an HTTP script to provide the database interface. (As you are using IIS and SQL Server 2000, you would most likely write the script in ASP.)

Basically, you would configure NowSMS, so that every time it receives an SMS message, it generates an HTTP request to call this script. The information about the sender of the message, and the text of the message would be passed as parameters in the HTTP request. So the script on your web server would parse those parameters, and take the appropriate action on the received
messages.

The script that you define is configurable, but it would most likely take on a format like this:

http://server/path/filename.asp?sender=SENDERPHONENUMBER&text=text+of+the+messag e

Here is a link with more info on configuring these commands:

http://www.nowsms.com/documentation/ProductDocumentation/2_way_sms_support.htm

One other note. I see that you are in the UAE, so you may have the requirement to receive Arabic text in your received messages. By default, NowSMS passes the text of received messages to a script using the UTF-8 character set (an encoding for Unicode). If you have problems working in UTF-8, it is possible to configure NowSMS to pass received message text to your application using a local character set, such as Arabic. To configure NowSMS to use the Arabic character set for passing received message text to a script, you need to manually edit the SMSGW.INI file, and under the [SMSGW] section header, add ReceiveSMSCharset=iso-8859-6 (that is the character set name for Arabic).

-bn