I think you should read the code completely in function *_receive_sms() there is DLR handler please CMIIW Stipe :)
On May 10, 2012, at 10:21 PM, Wilmar Campos wrote: > Hi To All, > I am trying to understand what methods are available to the the DLR from a > SMSC HTTP Generic configuration. > > I found this explanation, but it does not include anything about DLR for this > type of SMSC. > 01452 * (Semi-)generic HTTP interface > 01453 * > 01454 * This 'generic' type will handle the 'send-url' directive in the > 01455 * group the same way the 'sms-service' for smsbox does, via > 01456 * URLTranslation. Response interpretation is based on the three > 01457 * regex value that match against the reponse body. The HTTP reponse > 01458 * code is not obeyed. > 01459 * > 01460 * It handles mainly MT messages, due to the fact that MO traffic > 01461 * can't be abstracted in a universal way. Therefor we use the > 01462 * Kannel sendsms interface layout as generic fallback. So if your > 01463 * SMSC provider needs to send MO messages, he needs to implement > 01464 * the Kannel sendsms HTTP interface variables. > 01465 * > 01466 * Example config group: > 01467 * > 01468 * group = smsc > 01469 * smsc = http > 01470 * system-type = generic > 01471 * send-url = "http://<foobar>/<uri>?from=%P&to=%p&text=%b" > 01472 * status-success-regex = "ok" > 01473 * status-permfail-regex = "failure" > 01474 * status-tempfail-regex = "retry later" > 01475 * > 01476 * Note that neither 'smsc-username' nor 'smsc-password' is required, > 01477 * since they are coded into the the 'send-url' value directly. > 01478 * > 01479 * Stipe Tolj <[email protected]> > 01480 */ > > Any help is apreciated. > > Thanks, > > -- > WC Willy Mularto F300HD+MR18DE (NLC1725)
