Hi, this question was answered by me before (please learn: first search archive then ask).
A: this is intentionally that smpp link (thread) terminates, because smsc sent error in bind_response (invalid password) and in order to not abuse smsc, your account will not be closed or ip blocked, kannel doesn't retry. P.S. I believe we need FAQ ;) Roman wrote: > Hi, All > > I have kannel 1.4.0 stable installed and have some problems with SMPP > re-connection. > > Log file have the following lines: > 2004-12-03 13:59:38 [46351] [7] ERROR: connect failed > 2004-12-03 13:59:38 [46351] [7] ERROR: System error 61: Connection refused > 2004-12-03 13:59:38 [46351] [7] ERROR: error connecting to server > `xx.xx.xx.xx' at port `pppp' 2004-12-03 13:59:38 [46351] [7] ERROR: > SMPP[zzz]: Couldn't connect to server. 2004-12-03 13:59:38 [46351] [7] > ERROR: SMPP[zzz]: Couldn't connect to SMS center (retrying in 10 seconds). > 2004-12-03 13:59:48 [46351] [7] DEBUG: SMPP[zzz]: Sending PDU: 2004-12-03 > 13:59:48 [46351] [7] DEBUG: SMPP PDU 0x8148400 dump: > 2004-12-03 13:59:48 [46351] [7] DEBUG: type_name: bind_transceiver > 2004-12-03 13:59:48 [46351] [7] DEBUG: command_id: 9 = 0x00000009 > 2004-12-03 13:59:48 [46351] [7] DEBUG: command_status: 0 = 0x00000000 > 2004-12-03 13:59:48 [46351] [7] DEBUG: sequence_number: 578 = 0x00000242 > 2004-12-03 13:59:48 [46351] [7] DEBUG: system_id: "system_id" > 2004-12-03 13:59:48 [46351] [7] DEBUG: password: "password" > 2004-12-03 13:59:48 [46351] [7] DEBUG: system_type: "VMA" > 2004-12-03 13:59:48 [46351] [7] DEBUG: interface_version: 52 = > 0x00000034 > 2004-12-03 13:59:48 [46351] [7] DEBUG: addr_ton: 0 = 0x00000000 > 2004-12-03 13:59:48 [46351] [7] DEBUG: addr_npi: 0 = 0x00000000 > 2004-12-03 13:59:48 [46351] [7] DEBUG: address_range: NULL > 2004-12-03 13:59:48 [46351] [7] DEBUG: SMPP PDU dump ends. > 2004-12-03 13:59:52 [46351] [7] DEBUG: Optional parameter tag (0x0210) > 2004-12-03 13:59:52 [46351] [7] DEBUG: Optional parameter length read as 1 > 2004-12-03 13:59:52 [46351] [7] DEBUG: SMPP[zzz]: Got PDU: > 2004-12-03 13:59:52 [46351] [7] DEBUG: SMPP PDU 0x8148400 dump: > 2004-12-03 13:59:52 [46351] [7] DEBUG: type_name: bind_transceiver_resp > 2004-12-03 13:59:52 [46351] [7] DEBUG: command_id: 2147483657 = > 0x80000009 > 2004-12-03 13:59:52 [46351] [7] DEBUG: command_status: 14 = 0x0000000e > 2004-12-03 13:59:52 [46351] [7] DEBUG: sequence_number: 578 = 0x00000242 > 2004-12-03 13:59:52 [46351] [7] DEBUG: system_id: NULL > 2004-12-03 13:59:52 [46351] [7] DEBUG: sc_interface_version: 52 = > 0x00000034 2004-12-03 13:59:52 [46351] [7] DEBUG: SMPP PDU dump ends. > 2004-12-03 13:59:52 [46351] [7] ERROR: SMPP[zzz]: SMSC rejected login to > transmit, code 0x0000000e (Invalid Password). 2004-12-03 13:59:52 [46351] > [7] ERROR: SMPP[zzz]: I/O error or other error. Re-connecting. 2004-12-03 > 13:59:52 [46351] [7] DEBUG: Thread 7 (gw/smsc/smsc_smpp.c:io_thread) > terminates. > > Why thread 7 terminates? Why it does not re-connect to SMSC? Thread 7 > die, but bearerbox still working and another SMSC connection stay active. > Is it a bug or a config error? > I think that bearerbox have to reconnecting to SMSC infinitely often, > or not? > Only when I restart bearerbox thread 7 and link to zzz-smsc become > active. > > SMSC config: > > group = smsc > smsc = smpp > smsc-id = zzz > denied-smsc-id = "another_smsc" > transceiver-mode = 1 > host = xx.xx.xx.xx > port = pppp > our-host = oo.oo.oo.oo > smsc-username = "username" > smsc-password = "password" > system-type = "VMA" > source-addr-ton = 0 > source-addr-npi = 1 > dest-addr-ton = 1 > dest-addr-npi = 1 > > > Thank you beforehand. > > Best regards, Roman. -- Thanks, Alex
