Wilfried Goesgens wrote:
On Thu, Mar 17, 2005 at 09:14:04AM +0200, Owen Simwanda wrote:
I am running kannel 1.4.0 on fedora 2 using a siemens modem for an vitual smsc. Problem is some times the system workis fine with no problems then at other times it just stops responding completing then again it starts working and the cyccle continues. When it is giving problems the following log is what i see.i have include a copy of my configuration.
LOG2005-03-17 09:03:30 [4041] [7] ERROR: AT2[telecel]: Error occurs: ERROR (error number not known to us. ask google and add it.) 2005-03-17 09:03:30 [4041] [7] DEBUG: AT2[cel]: send command status: -1 2005-03-17 09:03:30 [4041] [7] DEBUG: AT2[cel]: --> AT+CMGS=42^M 2005-03-17 09:03:30 [4041] [7] DEBUG: AT2[cel]: <-- > 2005-03-17 09:03:30 [4041] [7] DEBUG: AT2[cel]: send command status: 1 2005-03-17 09:03:30 [4041] [7] DEBUG: AT2[cel]: --> 0011000B916290869091F10000A71FD9771D149EAFCB6490FB4D47A7DD6750D84D062541E4341994A68700 2005-03-17 09:03:31 [4041] [7] DEBUG: AT2[cel]: --> ^Z 2005-03-17 09:03:31 [4041] [7] DEBUG: AT2[cel]: <-- > 2005-03-17 09:03:31 [4041] [7] DEBUG: AT2[cel]: <-- ERROR 2005-03-17 09:03:31 [4041] [7] ERROR: AT2[cel]: Error occurs: ERROR (error number not known to us. ask google and add it.) 2005-03-17
This usually happens if something goes wrong with sending. there are more specific error codes, but the modem doesn't specify one.
this may be caused by the modem being buzy receiving messages, the message containing errnous content... Maybe a more modern firmware for your modem may help you out.
Things like these happen moreoften under heavy load then when sending a single message during idle times.
hmm, ok if this is the modem's fault, like it's busy reading MO messages or the load is too high, we should be aware of this and thread the "failing" as temporary failure not as permanent failure, right? Hence we'd re-queue the MT message and give it another try.
Is there any evidence how this can be reproduced? I could test this on a Siemens M20 modem and some Falcoms.
Can be distinguish temporary failures here with permanent (like corruct PDU sequence) here?
Stipe
mailto:stolj_{at}_wapme.de ------------------------------------------------------------------- Wapme Systems AG
Vogelsanger Weg 80 40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0 fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de http://www.wapme-systems.de/ -------------------------------------------------------------------
