I/o Error Or Other Error. Re-connecting
by: [ date ] [ thread ] [ subject ] [ author ] Hi, Your problem is pretty clear from your logs. Kannel cannot connect to your smsc. Either you have the wrong settings, or you have a network problem. You should try connecting to it from the shell. It seems that your transmit port is wrong. Meanwhile, it seems that your receive port is connected, and therefore you can receive stuff from the smsc. Eventually, once your receive connection is establisehed, kannel will stop trying to reconnect the transmit end (this is a known kannel bug). You should really try using transceiver mode if you can. BR, Nikos ----- Original Message ----- From: Lee Vidor To: users at kannel.org Sent: Friday, May 20, 2011 11:23 AM Subject: I/O error or other error. Re-connecting. Hi group, Strange on really. The following is my current setup (from status page) Kannel bearerbox version `svn-r4901'. Build `Apr 18 2011 02:30:03', compiler `4.1.2 20080704 (Red Hat 4.1.2-48)'. System Linux, release 2.6.18-194.32.1.el5, version #1 SMP Wed Jan 5 17:52:25 EST 2011, machine x86_64. Hostname 28793_1_570919, IP 127.0.1.1. Libxml version 2.6.26. Using OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008. Using native malloc. About every hour I get the following message in my kannel log file: 2011-05-20 08:02:28 [4308] [6] ERROR: SMPP[ABCDE]: I/O error or other error. Re-connecting. 2011-05-20 08:02:28 [4308] [6] ERROR: SMPP[ABCDE]: Couldn't connect to SMS center (retrying in 10 seconds). 2011-05-20 08:02:28 [4308] [7] ERROR: SMPP[ABCDE]: I/O error or other error. Re-connecting. 2011-05-20 08:02:28 [4308] [7] ERROR: SMPP[ABCDE]: Couldn't connect to SMS center (retrying in 10 seconds). 2011-05-20 08:02:38 [4308] [6] DEBUG: Connecting to <123.123.123.123> 2011-05-20 08:02:38 [4308] [7] DEBUG: Connecting to <123.123.123.123> Then after this i can no longer submit_sm but can receive deliver_sm for older messages fine. When I then attempt to submit_sm I get the following: 2011-05-20 07:59:54 [553] [9] DEBUG: boxc_receiver: sms received 2011-05-20 07:59:54 [553] [9] DEBUG: send_msg: sendin
SMSC via SMPP and forwards incoming SMS in toour application via HTTP GET method. This part works fine.However, our application requires us to have sender's MNC (Mobile NetworkCode) for each SMS we receive.We have arranged with our SMSC provider to send us this information(service_type) via SMPP, but we are having problems retrieving thisinformation from Kannel in to our application via HTTP GET (the problem isthat there is no escape code (%B) for MNC in Kannel documentation).Do you http://www.kannel.org/pipermail/users/2011-May/015723.html know what needs to be changed in Kannel source so we can receiveservice_type %B MNC?Kind regards,Asim Bucuk Asim Bucuk 2004-11-05 17:05:58 UTC PermalinkRaw Message Forgot to include details below.We are using Kannel Gateway as a bridge between SMSC and our application.Currently, Kannel connects to SMSC via SMPP and forwards incoming SMS in toour application via HTTP http://users.kannel.narkive.com/ewSeITJr/mnc-issue-when-using-kannel-smpp GET method. This part works fine.However, our application requires us to have sender's MNC (Mobile NetworkCode) for each SMS we receive.We have arranged with our SMSC provider to send us this information(service_type) via SMPP, but we are having problems retrieving thisinformation from Kannel in to our application via HTTP GET (the problem isthat there is no escape code (%B) for MNC in Kannel documentation).Do you know what needs to be changed in Kannel source so we can receiveservice_type %B MNC?Config file details >>>group = coreadmin-port = 14000smsbox-port = 14001admin-password = XXX#status-password = XXX#admin-deny-ip = ""admin-allow-ip = ""log-file = "/var/kannel/XXX"log-level = 1box-deny-ip = "*.*.*.*"box-allow-ip = "127.0.0.1"#unified-prefix = "00358,0"#access-log = "access.log"store-file = "kannel.store"#ssl-certkey-file = "mycertandprivkeyfile.pem"group = smscsmsc = smpphost = XXXport = 0receive-port = 10000smsc-username = "XXX"smsc-password = XXXsystem-type = ""address-range = ""group = smsboxbearerbox-host = localhost#sendsms-port = 13013#global-sender = 13013#sendsms-chars = "0123456789 +-"log-file = "/var/kannel/XXX"log-level = 1#access-log = "access.log"group = sms-servicekeyword = defaultget-url = "http://XXX/XXX/XXX.php?user=XXX
in Get Skype Help Windows Desktop Android iPad iPhone Linux Mac Windows RT Skype for TV Skype for Web Windows Desktop https://support.skype.com/en/faq/FA10143/why-do-i-get-a-disk-i-o-error-when-i-try-to-sign-in-to-skype-for-windows-desktop Windows Phone Skype Preview for Windows 10 Search Help & Support. Type a question or keyword Help Skype Everything else Error messages Why do I get a Disk I/O error when I try to sign in to Skype for Windows desktop? If you can’t sign in to Skype due to a disk I/O error, the first step is to make sure you’re i/o error using the latest version of Skype. Download thelatest version of Skype If you still get the error after downloading the latest version, we can help you solve it below. Need to make a call right now?If you don't have time to work through these steps, you can use Skype for Web (Beta) to make calls or send messages direct from your browser. i/o error or You don’t need to download or install Skype. Launch Skype for Web now. To resolve the disk I/O error, choose your operating system below. Windows 10 There are two possible fixes for the Disk I/O error. The first is to delete and re-create your user folder. The second is to change the permissions for your temporary files. To delete and recreate your user folder: Quit Skype.If you can see the Skype icon in the task bar, right-click it and select Quit Skype. If you can’t see it, right-click the task bar and click Task Manager, then select Skype and click End Task. Pressthe Windows and R keys on your keyboard at the same time. In the Run window, type %appdata%\Skype and click OK. In the File Explorer window that opens, find the folder with the same name as your Skype Name (if you’re signing in with a Microsoft account, the folder may start with live#3 instead). You’re about to delete this folder, which means your chat history will be deleted. If you want to save your chat history first, open the folder and copy the