Strange behaviour with specifying the smsc to send through via the http interface with the latest cvs. If you switch SMSC, then the 1st time the query is run, Kannel is picking up parameters for the _last_ smsc it used before not the new one you specify
Next time you run the same query it picks up the new parameters (ie. the parameters from the last query) and works. Anyone seen this happening before? -> 1st Send (to use SMSC1) GET /cgi-bin/sendsms?username=username&password=password&to=+447777777777&from=username&text=Test+Message&smsc=SMSC2 HTTP/1.0 -> Response (note ton0 and npi0) 2002-03-20 11:53:08 [10] DEBUG: boxc_receiver: sms received 2002-03-20 11:53:08 [5] DEBUG: First character = 2 and 2nd character = 1 2002-03-20 11:53:08 [5] DEBUG: Manually set to ton = 0 and npi = 0 2002-03-20 11:53:08 [5] DEBUG: ton = 0 and npi = 0 -> 2nd Send (to use SMSC2) GET /cgi-bin/sendsms?username=username&password=password&to=+447777777777&from=username&text=Test+Message&smsc=SMSC2 HTTP/1.0 -> Response (note incorrect ton0 and npi0 read from the configuration file even though SMSC changed) 2002-03-20 11:53:27 [10] DEBUG: boxc_receiver: sms received 2002-03-20 11:53:27 [5] DEBUG: First character = A and 2nd character = B 2002-03-20 11:53:27 [5] DEBUG: Manually set to ton = 0 and npi = 0 2002-03-20 11:53:27 [5] DEBUG: ton = 0 and npi = 0 2002-03-20 11:53:27 [5] WARNING: SMPP: PDU NUL terminated string has no NUL. 2002-03-20 11:53:27 [5] ERROR: SMPP: SMSC returned error code 0x00000069 in respons e to submit_sm. -> 3rd Send (to use SMSC2) GET /cgi-bin/sendsms?username=username&password=password&to=+447777777777&from=username&text=Test+Message&smsc=SMSC2 HTTP/1.0 -> Response (note correct ton5 and npi6 picked up from configuration file) 2002-03-20 11:53:38 [10] DEBUG: boxc_receiver: sms received 2002-03-20 11:53:38 [7] DEBUG: First character = A and 2nd character = B 2002-03-20 11:53:38 [7] DEBUG: Manually set to ton = 5 and npi = 6 2002-03-20 11:53:38 [7] DEBUG: ton = 5 and npi = 6 -- Alex Judd http://www.skywire.co.uk
