Probably, they are not using ssl. The sequence number is quite odd, so to see... for a first bind. But should also not be a problem.
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Bob O\\\'Souna Sent: Tuesday, 11 January, 2011 21:34 To: [email protected] Subject: Re: SMPP Binds not UP Rene Kluwen <rene.kluwen <at> chimit.nl> writes: > > system-id should be set to "usern" on the remote end. > > But not sure if this is your problem. > > == Rene > > -----Original Message----- > From: users-bounces <at> kannel.org [mailto:users-bounces <at> kannel.org] On Behalf > Of Bob O\'Souna > Sent: Tuesday, 11 January, 2011 21:11 > To: users <at> kannel.org > Subject: Re: SMPP Binds not UP > > Rene Kluwen <rene.kluwen <at> chimit.nl> writes: > > > > > Looks like an error on the remote end. > > Which is the smpp client? And what are their settings? > > > > == Rene > > > > -----Original Message----- > > From: users-bounces <at> kannel.org [mailto:users-bounces <at> kannel.org] > On > Behalf > > Of Bob O'Souna > > Sent: Tuesday, 11 January, 2011 18:53 > > To: users <at> kannel.org > > Subject: SMPP Binds not UP > > > > My setup is: > > > > OpenSMPPBox -> BearerBox > > > > Despite all efforts, a particular SMSC cannot bind to mine. the error is > > > > ERROR: Error reading from fd 10: > > ERROR: System error 104: Connection reset by peer > > ERROR: Invalid SMPP PDU received. > > DEBUG: Thread 878 (opensmppbox.c:smpp_to_bearerbox) terminates. > > DEBUG: Thread 877 (opensmppbox.c:function) terminates. > > > > I have ensured that the ssl parameters are not set at the other end and > that > > they are using SMP3.4. My parameters are > > > > opensmppbox.conf > > ================ > > group=opensmppbox > > opensmppbox-id=smppbox > > opensmppbox-port=6201 > > bearerbox-host=localhost > > bearerbox-port=13003 > > our-system-id=Vasco > > source-addr-ton = 1 > > source-addr-npi = 1 > > dest-addr-ton = 1 > > dest-addr-npi = 1 > > log-level=0 > > log-file=/var/log/kannel/opensmppbox.log > > route-to-smsc=MYSENDER > > smpp-logins="/etc/kannel_smpp/smpplogins.txt" > > > > smpplogins.txt > > ============= > > usern passw default *.*.*.* > > > > Please help. > > > > > > Thanks for looking at this! > > The error is definitely on the remote end - but the problem belongs to me! > The > details posted here are that of the SMPP Server. The client (Huawei Infox > 2.6 > SMS Gateway) has set > > Type_name: bind_transceiver > System_type: default > Interface_version: 34 > system_id: Vasco > ton: 1 > npi: 1 > > Any ideas? > > I have tried that - no joy! Here is a PDU dump DEBUG: SMPP[smppbox]: Got PDU: DEBUG: SMPP PDU 0x8e291d8 dump: DEBUG: type_name: bind_transceiver DEBUG: command_id: 9 = 0x00000009 DEBUG: command_status: 0 = 0x00000000 DEBUG: sequence_number: 514868941 = 0x1eb046cd DEBUG: system_id: "usern" DEBUG: password: "passw" DEBUG: system_type: NULL DEBUG: interface_version: 52 = 0x00000034 DEBUG: addr_ton: 1 = 0x00000001 DEBUG: addr_npi: 1 = 0x00000001 DEBUG: address_range: NULL DEBUG: SMPP PDU dump ends DEBUG: SMPP[smppbox]: Sending PDU: DEBUG: SMPP PDU 0x8e737d0 dump: DEBUG: type_name: bind_transceiver_resp DEBUG: command_id: 2147483657 = 0x80000009 DEBUG: command_status: 13 = 0x0000000d DEBUG: sequence_number: 514868941 = 0x1eb046cd DEBUG: system_id: NULL DEBUG: SMPP PDU dump ends ERROR: Error reading from fd 10: ERROR: System error 104: Connection reset by peer ERROR: Invalid SMPP PDU received. (1) Could it be my "default" setting in smpplogins.txt? (2) Could it be that they are actually using ssl somewhere? (They say an emphatic "no"!)
