HTTP SMSC | Search |
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through April 16, 2015 ⬆ |
◄ ► |
Author | Message | |||
Mathew Mathachan New member Username: Mathewm Post Number: 49 Registered: 04-2011 |
Hi, We configured a SMSC as HTTP over TCP(Custom). Though we return HTTP status code 200 on web app for requests posted by nowSMS, the nowSMS Gateway does not generate the SMSDLV call back. Appreciate your support Mathew | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5081 Registered: 08-2008 |
Hi Mathew, HTTP acceptance of a message does not usually mean that the message has been delivered, so in most scenarios, it would not be appropriate to generate a delivery report at this stage. There are ways for an HTTP service to generate a delivery report at a later stage via a separate transaction. However, that is complicated, and if you do want to generate a delivery report on HTTP acceptance, that is possible. These are the relevant settings. * Delivery Receipts: Add SMSC specific configuration options for delivery receipt handling under the SMSC specific section of SMSGW.INI (e.g., [SMPP - server:port]. DeliveryReportEnroute=Yes will cause NowSMS to generate an "ENROUTE" delivery receipt back to the client as soon as the message is submitted upstream, if a delivery report was requested by the client. (These options can be used together to cause NowSMS to generate delivery reports instead of the upstream provider.) * SMS Delivery Receipts: When using DeliveryReportEnroute=Yes to generate delivery reports when a message is successfully dispatched to an SMSC connnection, an additional setting has been added to allow the message status to be specified. By default, NowSMS uses a value of ENROUTE to indicate that the message is in-transit. DeliveryReportEnrouteStat=TEXT (in the SMSC specific section, combined with DeliveryReportEnroute=Yes) can be used to specify alternate values. Possible values that map to SMPP status include ACCEPTD and DELIVRD. -- Des NowSMS Support |