| HTTP Gateway response |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through September 15, 2006 ⬆ |
◄ ► |
| Author | Message | |||
| lookasms New member Username: Lookasms Post Number: 1 Registered: 01-2006 |
I have a connection with an operator which provides me URL to send sms via HTTP. I configured the NOWSMS for the same and its working fine. When I push any sms to their URL they genereate an JOB-ID through which I can trace the delivery status of messages. Is it possible when i push a message through NOWSMS then in return it capture the genereated job it and store it in any file. I know that can be traced from smsdebug file but thats too cumbersome. any alternate method for it? | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5444 Registered: 10-2002 |
Hi, That's one of the problems with HTTP interfaces. There's no standard for how a message id would be returned. We've done a lot of work on this area for SMPP. I can't promise anything, but could you tell me how this provider returns the message id in an HTTP response? I'm wondering if in the future we might be able to add an option that could at least parse it and log it (in the regular logs, rather than the debug log). -bn | |||
| lookasms New member Username: Lookasms Post Number: 4 Registered: 01-2006 |
hi sorry for late response, they send response like, Job ID: xxxxxxxx Status: 50, OK Thats mean message delivered. is there any patch available for this? | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5497 Registered: 10-2002 |
There is no patch. I'm simply exploring what we could do to better address this requirement. What if we had a configurable parameter that could be defined for an HTTP SMSC connection that indicated text to parse for. For example, "Job ID:" ... and then we would expect to parse the SMSC assigned message id from the text that follows that string. Then, we write the id to the SMSOUT-yyyymmdd.LOG file and include this ID like we do for SMPP enviroments. It would look something like this: 2006-02-01 12:42:02,43E0F2EA.req,127.0.0.1,+44777777777,OK -- HTTP - 192.168.1.12:8800,SubmitUser=bart;SMSCMsgId=43E0E795;Text="quick test" Would that work? | |||
| lookasms New member Username: Lookasms Post Number: 5 Registered: 01-2006 |
One thing i noticed in many HTTP browser response is that they are seperated by a line break character of HTML i.e. <BR> or <br>. did u mean: date time,NOWSMS_msg_id, ? ,to_mobile, NOWSMS_requset_response,local_url,SubmitUser=bart;SMSCMsgId=http_browser_respons e_from_smsc;Text="quick test" ? = What's this parameter If that could be done then it do wonders for many. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5546 Registered: 10-2002 |
Sorry, I should have clarified the parameters ... I was just using an excerpt from a log on a test system here. date time,NowSMS_msg_id,request_IP,to_Mobile,NowSMS_request_response - SMSC_connection_id,SubmitUser=request_user;SMSCMSGID=msgid_from_upstream_SMSC;Te xt=mesasge_text This feature is being implemented into the NowSMS 2006 release, which is due late next week. There will be an SMSGW.INI file setting that can be specified for some text that NowSMS will look for in the response from an HTTP SMSC. It will look for the message id to follow this ... and basically the text up to a line break, or space, or <> delimiter will be considered the message id. We might need to make a few refinements to the logic as we go forward, but this should be a good start. -bn | |||
| alya New member Username: Alya Post Number: 12 Registered: 12-2003 |
Hi, I need to talk about http smsc connection. I make http smsc connection to my operator. when i submit via url the smsc server will give response for my request as xml : -------------------------------- <? xml version=”1.0” ?> <PUSH> <STATUS>status</STATUS> <TRANSID>transid</TRANSID> <MSG>msg</MSG> </PUSH> ----------------------------- this xml is not DLR, but just information about my request. how i can get this reponse (i need this), except nowsms response : ------------ Message Submitted Continue MessageID=44992026.req, Recipient=628161455992 ------------ thank you for your help.. -alya aisha- | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6113 Registered: 10-2002 |
Basically, you can't get it in the NowSMS HTTP response ... because when NowSMS returns its response, the message has only been queued by NowSMS and not yet dispatched to an upstream connection. If you need the "transid" from your example above, it can be parsed out and recorded in the NowSMS log files. To do this, you need to add the following to the [HTTP - server:port] section of SMSGW.INI: MessageIDResponsePrefix=<TRANSID> You'd then see log entries like referenced above in SMSOUT ... each entry would include SMSCMsgId=transid ... -bn | |||
| alya New member Username: Alya Post Number: 13 Registered: 12-2003 |
Hi Bryce, Thank's for the reply. I use v.551k, this parameter (MessageIDResponsePrefix) run on this version?. if no, could you make patch for this version? -tx- alya aisha | |||
| faizal New member Username: Dsdfu Post Number: 2 Registered: 06-2006 |
I am alya friend, i want ask something about issue above, because that issue was from me. if i take the "status" from xml : <? xml version=”1.0” ?> <PUSH> <STATUS>status</STATUS> <TRANSID>transid</TRANSID> <MSG>msg</MSG> </PUSH> what parameter do i take ? thx | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6130 Registered: 10-2002 |
Unfortunately, the MessageIDResponsePrefix setting is not present in v5.51k. And we are only addressing system critical issues with any further maintenance to the v5.51k release. Regarding the other question, the logic is intended to parse a message id (for tracking purposes), as opposed to a status. If you wanted to parse status instead, you would use: MessageIDResponsePrefix=<STATUS> Basically, what this header means is that NowSMS parses the HTTP response, looking for the specified string. It then parses out the text that follows that string, up to a delimiter (line break, "<", etc.) -bn | |||
| Oladimeji Suberu New member Username: Ladisuberu Post Number: 4 Registered: 09-2005 |
I am currently sending messages through a service provider using SMPP. The provider informed me today that they have realtime delivery report with this protocol. How do I configure the NowSms to log this repoort where I can access it. Dimeji | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6303 Registered: 10-2002 |
Hi Dimeji, You need to set ReceiptRequested=Yes when you submit a message. Generalyin SMPP environments, receipts come back with text that starts id: ... so a 2-way command with a prefix of id:* can be used to process receipts. For more info, do a search out here ... search first using a keyword of ReceiptRequested. Next search on "@@RECEIPTMESSAGEID@@", which is the 2-way variable that contains the receipt message id. -bn | |||
