Re: Connection failed ?
Andreas Fink <[email protected]>
| Newsgroups | gmane.comp.mobile.kannel.devel |
|---|---|
| Message-ID | <[email protected]> |
On Freitag, September 19, 2003, at 11:22 Uhr, Stamatopoulos Panagiotis ([email protected]) wrote: > Stipe, > > Thanks for the response, BUT this is not exactly what I am asking for. > I > already implemented the scenario you describe (could not fetch). In my > scenario the HTTP request is delivered to the HTTP server, BUT BEFORE > the > HTTP server delivers the expected response to kannel, the connection > goes > down. who brings the connection down? Is it because kannel doesnt wait long enough or because the server closes down. It can also be a proxy server or firewall in the middle which cuts... > So kannel thinks that everything is ok (it delivered the http request > sucessfully), BUT it gets no response-SMS and the user receives > nothing in > his mobile (as the connection is down). > Any further ideas ? > > Thanks in advance > > Panagiotis Stamatopoulos > > > > -----Original Message----- > From: Stipe Tolj [mailto:[email protected]] > Sent: Friday, September 19, 2003 11:32 AM > To: [email protected] > Cc: [email protected] > Subject: Re: Connection failed ? > > >> An SMS is sent from a user's mobile phone to kannel. Kannel >> identifies the >> specific service, and a URL is requested via the GET-method. Kannel > expects >> the response from the URL, BUT, the connection between kannel and HTTP >> Server is lost, BEFORE kannel receives the response SMS, that is >> supposed > to >> return as an answer to user. Is there any way to handle this >> situation, > e.g. >> sending an SMS to the user after waiting for 2 or 3 minutes and not >> having > a >> response from the HTTP server? I understand that kannel can handle >> some >> situations like requestfailed, couldnotfetch, requestfailed, >> emptymessage, >> but I don't think that can handle the above scenario. Am I correct? >> Do you have any ideas ? Waiting for your response. Thanks in advance > > yes, Kannel (or specifically the smsbox) can handle this. smsbox can > have an HTTP request queueing mechanism where you can have several > tries to deliver the HTTP request to the HTTP server. Please see > user's guide for configuration directives. > > Now as smsbox will tried all HTTP GETs as failed, when no answer is > given, it will retry to N times that you can configure. If it fails > for all N times, then the smsbox will pass a "could not fetch" message > to the user via bearerbox. > > Stipe > > [email protected] > ------------------------------------------------------------------- > Wapme Systems AG > > Vogelsanger Weg 80 > 40470 Düsseldorf > > Tel: +49-211-74845-0 > Fax: +49-211-74845-299 > > E-Mail: [email protected] > Internet: http://www.wapme-systems.de > ------------------------------------------------------------------- > wapme.net - wherever you are > ########################################### > > This message has been scanned by F-Secure Anti-Virus for Microsoft > Exchange. > > Andreas Fink Global Networks Switzerland AG ------------------------------------------------------------------ Tel: +41-61-6666333 Fax: +41-61-6666334 Mobile: +41-79-2457333 Global Networks, Inc. Clarastrasse 3, 4058 Basel, Switzerland Web: http://www.global-networks.ch/ [email protected] ------------------------------------------------------------------