| Delivery report |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through June 21, 2007 ⬆ |
◄ ► |
| Author | Message | ||||
| massi massi New member Username: Massi Post Number: 7 Registered: 12-2005 |
Hello what's the correct steps to setup delivery report in smpp with nowsms 2006 Thanks | ||||
| Malcolm - Now Support Moderator Username: Malcolm Post Number: 169 Registered: 12-2006 |
Generally speaking it all happens automatically. But you have to request a receipt when you submit. Can you clarify your question, and explain how you currently interface to NowSMS? Then I will try to point you toward a good description. -Malcolm | ||||
| massi massi New member Username: Massi Post Number: 8 Registered: 12-2005 |
Hello I interface with nowsms using http request, I use the url parameter deliveredrequest=yes but I don't receive any thing. I use smpp 3.4 and my telecom provider have the delivery request activated. please can you tell me how to configure it Thanks | ||||
| Rui Pereira New member Username: Optimus_user Post Number: 1 Registered: 09-2006 |
Hi, I use a MM7 connection to a MMSC with a large account, but the large account requires an URL for Delivery Reports and Read Reply, but I can not find the URL for that. Can you help me with this issue? Tanks, best regards. | ||||
| mohammed ali New member Username: Mody Post Number: 1 Registered: 04-2007 |
Hello where can i type ReceiptRequest flag that is a URL Parameter pls? | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7024 Registered: 10-2002 |
The correct URL parameter is "&ReceiptRequested=Yes" It is also possible to edit the SMSGW.INI, and under the [SMSGW] header, add ReceiptRequested=Yes ... which will cause this flag to be set for all HTTP submissions. When this "ReceiptRequested" flag is set, it causes NowSMS to request a delivery receipt when submitting the message to an upstream SMSC. These receipt requests are supported when connecting to an SMPP based provider or a GSM modem that supports receipts. (In recent versions, there is also some support for UCP/EMI environments, but we need more real world testing feedback with more UCP/EMI providers.) When you are connecting to an SMPP provider, it is then up to that provider whether or not they will send delivery reports back to you. (So even if you configure everything correctly in NowSMS, they might not support delivery receipts.) If you are submitting to NowSMS via HTTP, then the "SMS Users" account that you are using should NOT have SMPP access enabled. (If the account has SMPP access enabled, NowSMS will queue any delivery receipts that it recieves back to the message queue for this SMPP client.) When a message is submitted via HTTP, the HTTP 200 OK response includes text such as the following: MessageID=54321098.req, Recipient=+xxxxxxxxxx If the message was posted to multiple recipients, this will be repeated for each recipient. You can parse the text from this HTTP response to determine the Message id that NowSMS has assigned to the message. When a delivery receipt comes back into the system, it gets routed to the 2-way command facility (unless SMPP access is enabled for the account that originally submitted the message to NowSMS, as I mentioned above). Normally, the SMSC will prefix the text of all delivery receipts with "id:" ... and if the message is properly formatted as a delivery receipt, but this prefix is not present, NowSMS will reformat the message to include this prefix. To define a 2-way command specific to processing delivery receipts, define the 2-way command with an "SMS Command Prefix" of id:* Leave "Receive Phone Number(s)" blank (or in the context of receipts, it would be the sender address of the originally sent message, so you could define different scripts to process receipts for different sender phone numbers). Then in the "Command to Execute" field, there is a parameter that you can use ... @@RECEIPTMESSAGEID@@, which will contain the message id for which this receipt applies. (This assumes that the service provider returns the message id properly in the receipt.) | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7025 Registered: 10-2002 |
The process of setting up the ability to receive delivery and/or read reply reports from an MMSC over MM7 is the same as if you were configuring NowSMS to receive MMS messages from the MMSC. It is a bit confusing, because we are trying to offer as much flexibility as we can for unusual configurations. But the basics are that you define an "MMSC Routing" definition to define the outbound link for connecting to the MMSC. The receiving link is defined as an "MMSC VASP" definition. The URL that you give to the provider is http://ipaddress:mmscPort/mm7/account=password (ipaddress is the IP of NowSMS, mmscPort is the "HTTP Port Number" configured for the MMSC, account and password are the details for the "MMSC VASP" account) -bn | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7026 Registered: 10-2002 |
If you are submitting using the web form, there is no way to set this flag on a per-message basis unless you edit the HTML template (i.e., "HTML\Send Text Message.htm") to include an option to set a value of "Yes" to a parameter named "ReceiptRequested". Previous discussion of this capability in this thread assumes that you are issuing complete URL requests to send messages ... not simply using the built-in web form. However, one quick and dirty solution ... if you want to have receipt requested set for messages submitted through the built-in web form, is to edit the SMSGW.INI, and under the [SMSGW] header, add ReceiptRequested=Yes ... which will cause this flag to be set for all HTTP submissions. -bn | ||||
| mohammed ali New member Username: Mody Post Number: 2 Registered: 04-2007 |
Thanks for Bryce Norwood but i am confused when i write @@RECEIPTMESSAGEID@@ in Command To Execute the App tell me that is not command . thanks | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7054 Registered: 10-2002 |
That is indeed very true. It is a parameter to be passed to a 2-way command, not a complete command. I'm not sure exactly what you're trying to accomplish ... but basically a delivery receipt is going to come in like a received message. So it gets processed by the 2-way command facility. You still need to define a command to process the message, @@RECEIPTMESSAGEID@@ is just an additional parameter that you can pass to your command. For more information on 2-way SMS, see: http://www.nowsms.com/documentation/ProductDocumentation/2_way_sms_support.htm | ||||
| Rui Pereira New member Username: Optimus_user Post Number: 3 Registered: 09-2006 |
Hi, tks for the URL information. I have inform our MMSC Staff with that but, is still doesn’t work. Here is the log from de MMSC.
BR | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7097 Registered: 10-2002 |
But what happens on the NowSMS end??? Does it see this request? Enable the MMSCDEBUG.LOG (checkbox on the "Serial #" page), and that will show any requests that come back into NowSMS. My quick guess ... I see that the URL is referencing port "8800". That is the default web port for the NowSMS web interface ... but it is not the default HTTP port for the MMSC itself. The MMSC defaults to port "8080". Make sure that the port number specified in this URL is the "HTTP Port Number" on the "MMSC" page of the configuration dialog, and that this port number is different from the "port number for web interface" on the "Web" page of the NowSMS configuration dialog. -bn | ||||
mmsc_log
