|
|
SMS Server Tools 3 Community |
Welcome, Guest. The forum is currently read-only, but will open soon. |
Wed Mar 12, 2025 20:10 |
Page: 1 2 Next
Keywords: Mode: All keywords (AND) |
Sat Mar 30, 2024 17:45
|
MareAlta: After re-installing PlaySms, messages are not going anymore to Backup folder!
But, PlaySMS can't catch/read incoming SMS! The incoming SMS is now on incoming folder as it should be! But PlaySMS does notinhg!
One note for SMSD
File mode creation mask: 022 (0644, rw-r--r--)
Shouldn't be 775?
Best Regards
Rui Silva
|
Fri Mar 29, 2024 12:44
|
MareAlta: Operating system name and version: CENTOS7
Version of smsd: Last Version using Yum installer
Smsd installed from: sources / package repository / from elsewhere...
Name and model of a modem / phone: Huawei E169
Interface: USB
Here is my config file
devices = GSM91, GSM92
logfile = /var/log/smsd/smsd.log
loglevel = 7
user = smstools
# 3.1.5 introduced smart logging
# once your configuration is OK, set log level lower (5 is good in most cases)
smart_logging = yes
infofile = /run/smsd/smsd.working
pidfile = /run/smsd/smsd.pid
logfile = /var/log/smsd/smsd.log
outgoing = /var/spool/sms/outgoing
checked = /var/spool/sms/checked
failed = /var/spool/sms/failed
incoming = /var/spool/sms/incoming
sent = /var/spool/sms/sent
#delaytime = 10
incoming_utf8 = yes
decode_unicode_text = yes
autosplit = 5
receive_before_send = yes
national_prefixes = +351
[GSM91]
device = /dev/ttyUSB0
#imei = 35xxxxxxxxxxx
#imsi = 268xxxxxxxxxx
init = AT+CPMS="SM","SM","SM";+CNMI=2,0,0,2,1
memory_start=0
incoming = yes
report = yes
smsc = +35193121314
baudrate = 19200
[GSM92]
device = /dev/ttyUSB3
#imei = 35xxxxxxxxxxxxxx
#imsi = 26xxxxxxxxxxxxxx
init = AT+CPMS="SM","SM","SM";+CNMI=2,0,0,2,1
memory_start=0
incoming = yes
report = yes
smsc = +35193121314
baudrate = 19200
--------------------------------------------------
SMSD Log
2024-03-29 12:23:31,6, GSM91: Used memory is 1 of 30
2024-03-29 12:23:31,6, GSM91: Trying to get stored message 0
2024-03-29 12:23:31,7, GSM91: -> AT+CMGR=0
2024-03-29 12:23:31,7, GSM91: Command is sent, waiting for the answer
2024-03-29 12:23:31,7, GSM91: <- +CMGR: 0,,31 07915391131213F4240C915391634325330000423092213262000DD4F29C5E0691CBA069730A02 OK
2024-03-29 12:23:31,5, GSM91: SMS received, From: 351xxxxxxxxx
2024-03-29 12:23:31,6, GSM91: Wrote an incoming message file: /var/spool/sms/incoming/GSM91.VQYBSj
2024-03-29 12:23:31,6, GSM91: Deleting message 0
SMSD works fine with modems!
When receiving SMS, PlaySMS can't find incoming SMS
I've checked SMS folders and have a "backup" folder created by smstools.
I've already erased, but when I restart "smsd restart", it auto creates backup folder again!
PlaySMS can send SMS, and its going well but can't catch all incoming messages!
They disapear from incoming folder and are automaticly moved to Backup Folder.
Thanks in advance fro any help
Best Regards
Rui Silva
|
Wed Mar 24, 2021 15:24
|
MareAlta: Hello!
What about an ping command with result to your sms response? For example ping www.nasa.gov
and send to you the result in an sms!
Regards
Rui
|
Wed Mar 24, 2021 15:14
|
MareAlta: SOLVED
Issue: International Prefixes
Well, i'ved upload the csv file with no international prefixes! So, wente to smsd.conf and added the international prefixes on the file +351!
Everything was going well with no problem! But when I started the Play SMS service with subscribe sms, the system could't send, but could reeive. Why? Because, when the system was sending, there was an conflict with two international prefixes. So, the system could not send the sms with +351 and another +351!
I've re-uploaded the phonebook with international prefixes on each contact ad everything works correctly!
|
Sat Feb 20, 2021 17:17
|
MareAlta: An update:
PlaySMS can send every day, an sheduled test message, as I programed!
But sending an manual sms through "compose message", doesn't send! It gives Error 500!
If I try smssend command, it does the same error 500!
|
Thu Feb 18, 2021 20:01
|
MareAlta: Here is a fresh Log os smsd.conf:
2021-02-18 19:56:59,6, GSM91: Checking if modem needs PIN
2021-02-18 19:56:59,6, GSM91: Initializing modem
2021-02-18 19:57:00,6, GSM91: Signal Strength Indicator: (19,99) -75 dBm (Good), Bit Error Rate: not known or not detectable
2021-02-18 19:57:00,6, GSM91: Checking if Modem is registered to the network
2021-02-18 19:57:01,6, GSM91: Modem is registered to the network
2021-02-18 19:57:01,6, GSM91: Location area code: 0C, Cell ID: 4FAE
2021-02-18 19:57:01,6, GSM91: Signal Strength Indicator: (19,99) -75 dBm (Good), Bit Error Rate: not known or not detectable
2021-02-18 19:57:01,6, GSM91: Selecting PDU mode
2021-02-18 19:57:03,5, GSM91: CGSN: 353xxxxxxxxxxxx
2021-02-18 19:57:03,5, GSM91: IMSI: 268xxxxxxxxxxxxx
2021-02-18 19:57:03,6, GSM91: Checking if reading of messages is supported
2021-02-18 19:57:03,7, GSM91: ## Start of device details
2021-02-18 19:57:03,7, GSM91: # Manufacturer identification:
2021-02-18 19:57:04,7, GSM91: -> AT+CGMI
2021-02-18 19:57:04,7, GSM91: <- huawei
OK
2021-02-18 19:57:04,7, GSM91: # Model identification:
2021-02-18 19:57:04,7, GSM91: -> AT+CGMM
2021-02-18 19:57:04,7, GSM91: <- K3520
OK
2021-02-18 19:57:04,7, GSM91: # Revision identification:
2021-02-18 19:57:04,7, GSM91: -> AT+CGMR
2021-02-18 19:57:05,7, GSM91: <- 11.314.12.00.00
OK
2021-02-18 19:57:05,7, GSM91: # New message indications, list of supported modes:
2021-02-18 19:57:05,7, GSM91: -> AT+CNMI=?
2021-02-18 19:57:05,7, GSM91: <- +CNMI: (0,1,2),(0,1,2,3),(0,2),(0,1,2),(0,1)
OK
2021-02-18 19:57:05,7, GSM91: # New message indications, current settings:
2021-02-18 19:57:05,7, GSM91: -> AT+CNMI?
2021-02-18 19:57:06,7, GSM91: <- +CNMI: 2,0,0,2,1
OK
2021-02-18 19:57:06,7, GSM91: # Preferred message storage, list of supported mem's:
2021-02-18 19:57:06,7, GSM91: -> AT+CPMS=?
2021-02-18 19:57:06,7, GSM91: <- +CPMS: ("ME","MT","SM","SR"),("ME","MT","SM","SR"),("ME","MT","SM","SR")
OK
2021-02-18 19:57:06,7, GSM91: # Phonebook storage, available mem's:
2021-02-18 19:57:06,7, GSM91: -> AT+CPBS=?
2021-02-18 19:57:07,7, GSM91: <- +CPBS: ("SM","DC","FD","LD","MC","ME","RC","EN","ON")
OK
2021-02-18 19:57:07,7, GSM91: # List messages, list of supported stat's:
2021-02-18 19:57:07,7, GSM91: -> AT+CMGL=?
2021-02-18 19:57:07,7, GSM91: <- +CMGL: (0-4)
OK
2021-02-18 19:57:07,7, GSM91: # Delete message, list of supported values:
2021-02-18 19:57:07,7, GSM91: -> AT+CMGD=?
2021-02-18 19:57:08,7, GSM91: <- +CMGD: (),(0-4)
OK
2021-02-18 19:57:08,7, GSM91: # Phone activity status, list of supported stat's:
2021-02-18 19:57:08,7, GSM91: -> AT+CPAS=?
2021-02-18 19:57:08,7, GSM91: <- +CPAS: (0,3,4)
OK
2021-02-18 19:57:08,7, GSM91: # TE character set, list of supported charset's:
2021-02-18 19:57:08,7, GSM91: -> AT+CSCS=?
2021-02-18 19:57:09,7, GSM91: <- +CSCS: ("IRA","GSM","UCS2")
OK
2021-02-18 19:57:09,7, GSM91: # TE character set, current setting:
2021-02-18 19:57:09,7, GSM91: -> AT+CSCS?
2021-02-18 19:57:09,7, GSM91: <- +CSCS: "IRA"
OK
2021-02-18 19:57:09,7, GSM91: ## End of device details
2021-02-18 19:57:09,6, GSM91: Checking memory size
2021-02-18 19:57:10,6, GSM91: Used memory is 0 of 30
2021-02-18 19:57:10,6, GSM91: No SMS received
2021-02-18 19:57:10,6, GSM91: Sending SMS from to 35193xxxxxxx
2021-02-18 19:57:10,6, GSM91: Checking if modem is ready
2021-02-18 19:57:10,6, GSM91: Pre-initializing modem
2021-02-18 19:57:11,6, GSM91: Initializing modem
2021-02-18 19:57:12,6, GSM91: Signal Strength Indicator: (19,99) -75 dBm (Good), Bit Error Rate: not known or not detectable
2021-02-18 19:57:12,6, GSM91: Checking if Modem is registered to the network
2021-02-18 19:57:12,6, GSM91: Modem is registered to the network
2021-02-18 19:57:12,6, GSM91: Selecting PDU mode
2021-02-18 19:57:36,3, smsd: FATAL ERROR: Looks like another smsd (27873) is running. I (26377) quit now.
2021-02-18 19:57:36,2, smsd: Smsd mainprocess terminated abnormally. PID: 26377.
2021-02-18 19:57:40,3, GSM91: The modem answer was not OK: +CMS ERROR: 500 (Unknown error)
2021-02-18 19:57:40,5, GSM91: Waiting 4 sec. before retrying
2021-02-18 19:57:44,6, GSM91: Checking if modem is ready
2021-02-18 19:57:45,6, GSM91: Pre-initializing modem
2021-02-18 19:57:47,6, GSM91: Initializing modem
2021-02-18 19:57:48,6, GSM91: Signal Strength Indicator: (19,99) -75 dBm (Good), Bit Error Rate: not known or not detectable
2021-02-18 19:57:48,6, GSM91: Checking if Modem is registered to the network
2021-02-18 19:57:49,6, GSM91: Modem is registered to the network
2021-02-18 19:57:49,6, GSM91: Selecting PDU mode
2021-02-18 19:57:58,5, smsd: Moved file /var/spool/sms/outgoing/send_THzPer to /var/spool/sms/checked
2021-02-18 19:58:20,3, GSM91: The modem answer was not OK: +CMS ERROR: 500 (Unknown error)
2021-02-18 19:58:20,5, GSM91: Waiting 4 sec. before retrying
2021-02-18 19:58:24,6, GSM91: Checking if modem is ready
2021-02-18 19:58:30,6, GSM91: Pre-initializing modem
2021-02-18 19:58:30,6, GSM91: Initializing modem
2021-02-18 19:58:34,6, GSM91: Signal Strength Indicator: (19,99) -75 dBm (Good), Bit Error Rate: not known or not detectable
2021-02-18 19:58:34,6, GSM91: Checking if Modem is registered to the network
2021-02-18 19:58:34,6, GSM91: Modem is registered to the network
2021-02-18 19:58:34,6, GSM91: Cell ID changed: 4FAE -> 0
2021-02-18 19:58:35,6, GSM91: Signal Strength Indicator: (19,99) -75 dBm (Good), Bit Error Rate: not known or not detectable
2021-02-18 19:58:35,6, GSM91: Selecting PDU mode
2021-02-18 19:59:02,3, GSM91: The modem answer was not OK: +CMS ERROR: 500 (Unknown error)
2021-02-18 19:59:02,4, GSM91: Sending SMS to 35193xxxxxxx failed, trying time 112 sec. Retries: 2.
2021-02-18 19:59:02,6, GSM91: Moved file /var/spool/sms/checked/send_VjuI3c to /var/spool/sms/failed/send_VjuI3c
2021-02-18 19:59:02,6, GSM91: Checking device for incoming SMS
2021-02-18 19:59:02,6, GSM91: Checking if modem is ready
|
Thu Feb 18, 2021 19:47
|
MareAlta: Operating system name and version: CENTOS 7
Version of smsd:
Smsd installed from: sources / package repository / from elsewhere...
Name and model of a modem / phone: Huawei E169 & Huawei K3520
Interface: USB
Everything was fine until today! Everyday I schedule server to send me an SMS all morning at 09:00. Today everything was fine.
At the end of the morning i tried a auto-respond SMS from playsms. That was when i suspect something wasn't rigth! Sms would get to my phone!
I've sended SMS, system did work. But sending sms, NO! I'v took of SIM card and inserted on cellphone! Messages in & out with no problem.
Inserted again SIM card on Huawei K3520. Calls are on going, receive SMS works too. But sending SMS, NO!
It's allways giving 500 Error.
As I have two modems working, I tried to change USB port to Huawei E169!
All messages were received. But could send an SMS. Again Error 500
Here is some log:
2021-02-18 19:45:20,5, smsd: Moved file /var/spool/sms/outgoing/out.20210218194518.0.1.168 to /var/spool/sms/checked
2021-02-18 19:45:53,3, GSM91: The modem answer was not OK: +CMS ERROR: 500 (Unknown error)
2021-02-18 19:45:53,5, GSM91: Waiting 4 sec. before retrying
2021-02-18 19:46:29,3, GSM91: The modem answer was not OK: +CMS ERROR: 500 (Unknown error)
2021-02-18 19:46:29,5, GSM91: Waiting 4 sec. before retrying
|
Mon Sep 30, 2019 16:21
|
MareAlta:
Global settings:
incoming_utf8 = yes
decode_unicode_text = yes
Running as smstools:smstools.
2019-09-30 15:32:27,2, smsd: There was 1 error while reading the config file:
2019-09-30 15:32:27,2, smsd: - Unknown setting for modem GSM91: incoming_utf8
2019-09-30 15:32:27,2, smsd: There was 1 major problem found.
2019-09-30 15:32:27,2, smsd: Smsd mainprocess terminated.
With decode is working. Only incoming_utf8, is not working! The message breaks!
It's working now!
I've removed incoming_utf8 from the modem config and pasted before modem config!
It's now working!
Everything is ok now!
Thank You for your help KEKE!
|
Mon Sep 30, 2019 15:50
|
MareAlta:
Global settings:
incoming_utf8 = yes
decode_unicode_text = yes
Running as smstools:smstools.
2019-09-30 15:32:27,2, smsd: There was 1 error while reading the config file:
2019-09-30 15:32:27,2, smsd: - Unknown setting for modem GSM91: incoming_utf8
2019-09-30 15:32:27,2, smsd: There was 1 major problem found.
2019-09-30 15:32:27,2, smsd: Smsd mainprocess terminated.
With decode is working. Only incoming_utf8, is not working! The message breaks!
|
Tue Sep 24, 2019 12:09
|
MareAlta: An update to this problem!
When sending from Android (xiaomi for example) an SMS with á ó ã etc, the message it's cutted and the rest of the message is lost!
When sending from Windows 10 mobile (lumia 950), The entire message appears but clean of ´, ~, ` or ª etc
e.g.
Android SMS - Olá! Bom dia = Ol
Windows 10 Mobile (lumia 950) - Olá! Bom dia = Ola! Bom dia
Weard...!
Regards
Rui
|
Tue Sep 24, 2019 08:33
|
MareAlta: Yes it works. Thank You very much. Just one thing!
If somebody use á or ã sms will be cut! I went to see the log and this was there:
SMS received, From: 3519xxxxxxx
2019-09-24 08:30:03,5, GSM91: Cannot convert 2. character
2019-09-24 08:30:03,5, GSM91: Cannot convert 4. character
Any sugestions?
Regards
Rui
|
Mon Sep 23, 2019 07:33
|
MareAlta: Wait, Keke, it's smething related with modem and probably the AT string (I am saying)!
Because, i'm sending some SMS's to the number, and it doesn't appear on smsd log.
Only the short message when asking for report.
Meaning= I don't get any incoming normal SMS
Should it be the AT string?
|
Mon Sep 23, 2019 07:29
|
MareAlta:
If you need to use PlaySMS, and are not willing to modify it, there are several settings available to get a rid of this issue.
I using playsms that i found free and usefull. And I don't have any problem modifying it. Just don't know where for now!
But, i'm open to other free software or hand made scripts!
My use os sms is not for comercial pruposes. it's only for my associates!
Regards
Rui
|
Mon Sep 23, 2019 07:25
|
MareAlta: Ok Keke, Thank You for your help!
I wll have to ask playsms where are incoming sms, because everything is empty on inbox!
Best regards
Rui
|
Sun Sep 22, 2019 15:21
|
MareAlta: CENTOS7/FREEPBX/PLAYSMS:
Last Version of smsd: Last version available on September 2019
Smsd installed from: smstools3 webiste following instructions
Name and model of a modem / phone: Huawei E169
Interface: USB
Everything si working fine, except this:
If i send an SMS, the system sends, and when it gets report, the log reports the short message receveid and imediately delete's the same message!
Also, i'm not getting incoming messages!
Here's my setup:
# Modem configuration
[GSM91]
#CGSN: 359xxxxxxxxxxxx
#IMSI: 268xxxxxxxxxxxxx
device = /dev/ttyUSB0
#init = AT+CPMS="SM"
memory_start=0
queues = assp
incoming = yes
report = yes
baudrate = 19200
report_device_details = yes
And in log smsd.log
I have to send 1 short message for /var/spool/sms//out.20190922140901.0.1.21
2019-09-22 15:09:02,6, GSM91: Checking device for incoming SMS
2019-09-22 15:09:02,6, GSM91: Checking if modem is ready
2019-09-22 15:09:02,6, GSM91: Pre-initializing modem
2019-09-22 15:09:03,6, GSM91: Signal Strength Indicator: (15,99) -83 dBm (Good), Bit Error Rate: not known or not detectable
2019-09-22 15:09:03,6, GSM91: Checking if Modem is registered to the network
2019-09-22 15:09:04,6, GSM91: Modem is registered to the network
2019-09-22 15:09:04,6, GSM91: Selecting PDU mode
2019-09-22 15:09:04,6, GSM91: Checking memory size
2019-09-22 15:09:05,6, GSM91: Used memory is 0 of 30
2019-09-22 15:09:05,6, GSM91: No SMS received
2019-09-22 15:09:05,6, GSM91: Sending SMS from ASSP to 35193xxxxxxx
2019-09-22 15:09:05,6, GSM91: Checking if modem is ready
2019-09-22 15:09:05,6, GSM91: Pre-initializing modem
2019-09-22 15:09:06,6, GSM91: Signal Strength Indicator: (15,99) -83 dBm (Good), Bit Error Rate: not known or not detectable
2019-09-22 15:09:06,6, GSM91: Checking if Modem is registered to the network
2019-09-22 15:09:07,6, GSM91: Modem is registered to the network
2019-09-22 15:09:07,6, GSM91: Selecting PDU mode
2019-09-22 15:09:10,5, GSM91: SMS sent, Message_id: 32, To: 35193xxxxxxx, sending time 5 sec.
2019-09-22 15:09:10,6, GSM91: Moved file /var/spool/sms//out.20190922140901.0.1.21 to /var/spool/sms/sent/out.20190922140901.0.1.21
2019-09-22 15:09:10,6, GSM91: Checking device for incoming SMS
2019-09-22 15:09:10,6, GSM91: Checking memory size
2019-09-22 15:09:10,6, GSM91: Used memory is 0 of 30
2019-09-22 15:09:10,6, GSM91: No SMS received
2019-09-22 15:09:10,6, GSM91: Checking device for incoming SMS
2019-09-22 15:09:10,6, GSM91: Checking memory size
2019-09-22 15:09:11,6, GSM91: Used memory is 0 of 30
2019-09-22 15:09:11,6, GSM91: No SMS received
2019-09-22 15:09:21,6, GSM91: Checking device for incoming SMS
2019-09-22 15:09:21,6, GSM91: Checking if modem is ready
2019-09-22 15:09:21,6, GSM91: Pre-initializing modem
2019-09-22 15:09:22,6, GSM91: Signal Strength Indicator: (15,99) -83 dBm (Good), Bit Error Rate: not known or not detectable
2019-09-22 15:09:22,6, GSM91: Checking if Modem is registered to the network
2019-09-22 15:09:23,6, GSM91: Modem is registered to the network
2019-09-22 15:09:23,6, GSM91: Selecting PDU mode
2019-09-22 15:09:23,6, GSM91: Checking memory size
2019-09-22 15:09:24,6, GSM91: Used memory is 1 of 30
2019-09-22 15:09:24,6, GSM91: Trying to get stored message 0
2019-09-22 15:09:24,5, GSM91: SMS received (report, Message_id: 32, Status: 0,Ok,short message received by the SME), From: 351936345233
2019-09-22 15:09:24,6, GSM91: Wrote an incoming message file: /var/spool/sms/incoming/GSM91.4vAfS6
2019-09-22 15:09:24,6, GSM91: Deleting message 0
2019-09-22 15:09:25,6, GSM91: Checking device for incoming SMS
2019-09-22 15:09:25,6, GSM91: Checking memory size
2019-09-22 15:09:26,6, GSM91: Used memory is 0 of 30
2019-09-22 15:09:26,6, GSM91: No SMS received
_____________________________________________________________________
The incoming folder, also changes date & time of folder when it receives the sms!
But the folder is allways empty!
Also incoming SMS, nor appear on smsd.log nor on incoming folder.
Thanks in advance, if someone could help!
Regards_
Rui aka MareAlta
|
Sun Nov 17, 2013 16:14
|
MareAlta: I'm going to search for this tutorial or if you have an tutorial with this, please put it here.
I'm interested in this too! When you say script, my mind stops, because i dont' know quite well how to run the scripts.
But i'm an adventurous to this matter and i'm going to try!
Just put here some tutorial if you have!
|
Sun Nov 17, 2013 16:09
|
MareAlta: Operating system name and version: CENTOS 5
Version of smsd: Latest
Smsd installed from: Source
Name and model of a modem / phone: 3 x Huawei E220 - 3 diferent operators
Interface: USB
I have a question/curiosity.
I don't know about other operators in the world. But here in Portugal we have this:
You can send an sms to 130+93XXXXXXX (or 13093XXXXXXX). The message will appear directly on the phone screen.
But i tried to send an message with the command "sendsms"
Detination: 35113093XXXXXXX
Message: Hello sms test
But it fails, saying the number is invalid.
I have 3 modems configured operators prefix 35193, 35191, 35196.
I've added 35113093 to smsd.conf right after 35193 prefix. Like This:
Optimus 35193, 35113093
________________________________
Another issue is like this:
If i send an sms with the word "Saldo" to the internal number 1693, it will return an message with the pretended information.
But when trying with sendsms the sms fails!
The same thing to the other operators.
Can someone help me with this?
Thanks
Best Regards to All
|
Sun Oct 06, 2013 15:10
|
MareAlta: @Keke
[SOLVED]
I've disabled the initial PIN REQUEST on SIM CARD.
It's now working perfectly! No more errors or usb-storage, etc.
Queues are working fine, without any problems.
|
Fri Oct 04, 2013 23:26
|
MareAlta: I'm not bodering you more with this, but this is my last statement, and i will not talk about it anymore.
As I sad in my previous posts, we have GSM for basic call and SMS service. And i wrote that 3G and 4G are complements of a GSM network.
So to give you an answer about a new device to buy, I went to AT&T's web site and found an 4G modem. Now look the specs that it has:
Wireless Technology
4G-LTE Band 2, 4, 5 and 17
4G HSPA+ HSPA+ with enhanced backhaul
3G - UMTS 850/1900/2100MHz
GPRS/EDGE 850/900/1800/1900MHz
GPS compatiable
Mobile Hotspot Up to 10 devices (Windows® 7 users only via connection client)
HUAWEI E220 has 2 of those lines pasted. starting by 3G and GPRS!
My conclusion is pointing to SIM CARD.
Take your modem to an AT&T's store, ask for SIM CARD swap.
And another conclusion! IT's not your huawei modem. Is the sim card.
Based on what you wrote
Quote
It never wants to acknowledge AT&T's towers, but it shows T-Mobile.
So the modem works, otherwise it wouldn't search any network.
Best regards and all of luck to solve the problem!
MAreAlta
|
Fri Oct 04, 2013 13:58
|
MareAlta: Ok! Just one last try with this:
Google for this program - MDMA
Mobile Data Monitoring Aplication
With this software you will be able to monitor the status of you modem!
Why i'm telling you this!
With MDMA you can confirgure Modem to work specificly with a certain frequency, or all!
See if with your 4G SIM CARD, all frequencies (except 4G, that doesn't exist on huawei) are enabled! If not, check all and aply. See the result. You are not going to damage the modem. Only activating (possibly) other working frequencies!
Do this, install this program here is the url
http://mymodem.in/mdma-a-mobile-data-monitoring-application-version-1-1-0-0-released/
I'm not giving up! I can't believe that chaging a cell network to an higher platform, makes an 3G device stop working!
Another thing! 4G LTE works only with data package! Not GSM! If you make a phone call or SMS, it works under GSM!
I'm not telling that you are wrong!
I just can't believe!
Here in Portugal we have 4G network - I'm on a 4G network and working wtih 2 Huawei E220 & Huawei E1550.
I'll rest my case!
|
Fri Oct 04, 2013 00:22
|
MareAlta: Ok! It's diferent device. But what device have you tried?
Did you insert any init string?
Try to remove PIN just for test propose!
Show the .conf of that device, if you please!
Hold on! Let's see another thing! Power issue!
How many usb ports do you have in your board? How many ports are beeing used? Wht type of devices are pluged-in?
I'm asking this because, this "hang" of that another device, could be stopping for some lack of power! The same way huawei E220, can't get enough signal strenght, probably due to the lack of power! It's a perspective that you should observe!
When we have more than one device consuming power thru usb, devices can stop working because they don't have enough power!
|
Thu Oct 03, 2013 22:27
|
MareAlta: Ok! So CLAIM to your network operator for lack of signal.
Did you get some notice from netowrk operator, with information of chaging the comunications platform?
As you say and quote
When sitting here sometimes it shows no signal, other times it shows signal ranging from Workable to Marginal.
Workable! That's bad!
Maybe your network is on that are that some IT technicians call "shadow area". There are some areas in land around the world, where the signal doesn't get enough. Operators usualy install repeaters in the area.
Here in Portugal we have the same issue, for example near Chaves, North of Portugal. And another example is with new TDT - Digital TV. The same problem.
Resuming, in my previous posts i sad that GSM allways work and 3G & 4G are complements (advantages).
plus: cell phones have more gain then usb modems. That's why you can get some signal.
An experience(another): try if you can, to get an usb cable - My two modems E220 are working with a cannon usb camera. The cable is the same. The ideia is to elevate the modem, trying to get some signal. Can do this experiment?
My last sugestion is, claim to your network operator, to get more signal.
If you are really thinking in changing modem, my advice is to get an Huawei. As far i can get till now, huawei works perfect with smstools and your platform.
Here is something very important, when buying 4G Modem.
HUAWEI E397Bu-501: 4G LTE FDD Band 4(1700/2100MHz) and Band 17 (700MHz)
HUAWEI E397Bu-7: 4G LTE FDD 1800/2100MHz
HUAWEI E397u-53: 4G LTE FDD Band 13 (700 MHz), 1700/2100MHz
HUAWEI E397u-56: 4G LTE FDD (B4) 2100 mhz
As you can read, there are diferent working frequencies. It depends on your country.
Hope i could help you more.
Just let me know what was the next step that you are going to make.
If you will use an 4G huawei modem, tell something about it.
Best regards
MareAlta
|
Thu Oct 03, 2013 18:41
|
MareAlta: lsmod | grep usb
lsmod | grep usb
usbserial 33065 1 option
usb_storage 80929 0
scsi_mod 144277 13 be2iscsi,ib_iser,iscsi_tcp,bnx2i,libcxgbi,libiscsi2,scsi_transport_iscsi2,scsi_dh,sr_mod,sg,usb_storage,libata,sd_mod
|
Thu Oct 03, 2013 18:17
|
MareAlta: @Keke, i need your help, please!
After all, the Huawei E1550 was flashed well. Linux it's not identifying well the modems. Now i have 2 Huawei E220 and 1 E1550. One of the E220 (optimus) is working well without any problem. The other E220 (tmn) an E1550 (vodafone), linux doesn't interpretate well the modem.
It gives them as usb storage and it doesn't convert them to modem. (I think)
I think that's someting with modprobe but i don't know how to do this.
After googling a while, can't found nothing concrete to change this.
lsusb
Bus 003 Device 003: ID 12d1:1003 Huawei Technologies Co., Ltd. E220 HSDPA Modem / E230/E270/E870 HSDPA/HSUPA Modem
Bus 003 Device 001: ID 0000:0000
Bus 003 Device 002: ID 12d1:1003 Huawei Technologies Co., Ltd. E220 HSDPA Modem / E230/E270/E870 HSDPA/HSUPA Modem
Bus 004 Device 001: ID 0000:0000
Bus 005 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 002 Device 002: ID 045e:0750 Microsoft Corp. Wired Keyboard 600
Bus 001 Device 008: ID 12d1:1446 Huawei Technologies Co., Ltd. E1552/E1800/E173 (HSPA modem)
Bus 001 Device 001: ID 0000:0000
When i do ls -ltr /dev/ttyUSB* i get this:
ls -ltr /dev/ttyUSB*
crw-rw---- 1 root uucp 188, 0 Out 3 13:10 /dev/ttyUSB0
crw-rw---- 1 root uucp 188, 1 Out 3 13:10 /dev/ttyUSB1
And a dmesg | grep usb
usbcore: registered new driver usbfs
usbcore: registered new driver hub
usbcore: registered new driver hiddev
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
usb usb1: configuration #1 chosen from 1 choice
usb usb2: configuration #1 chosen from 1 choice
usb usb3: configuration #1 chosen from 1 choice
usb usb4: configuration #1 chosen from 1 choice
usb usb5: configuration #1 chosen from 1 choice
usb 2-1: new low speed USB device using uhci_hcd and address 2
usb 2-1: configuration #1 chosen from 1 choice
input,hidraw0: USB HID v1.11 Keyboard [Microsoft Wired Keyboard 600] on usb-0000:00:10.0-1
input,hidraw0: USB HID v1.11 Device [Microsoft Wired Keyboard 600] on usb-0000:00:10.0-1
usb 3-1: new full speed USB device using uhci_hcd and address 2
usb 3-1: configuration #1 chosen from 1 choice
usb-storage: probe of 3-1:1.0 failed with error -5
usb-storage: probe of 3-1:1.1 failed with error -5
usb-storage: device found at 2
usb-storage: waiting for device to settle before scanning
usbcore: registered new driver usb-storage
usbcore: registered new driver usbserial
drivers/usb/serial/usb-serial.c: USB Serial support registered for generic
usbcore: registered new driver usbserial_generic
drivers/usb/serial/usb-serial.c: USB Serial Driver core
drivers/usb/serial/usb-serial.c: USB Serial support registered for GSM modem (1-port)
usb 3-1: GSM modem (1-port) converter now attached to ttyUSB0
usb 3-1: GSM modem (1-port) converter now attached to ttyUSB1
usbcore: registered new driver option
drivers/usb/serial/option.c: USB Driver for GSM modems: v0.7.1
usb-storage: device scan complete
usb 2-2: new full speed USB device using uhci_hcd and address 3
usb 2-2: configuration #1 chosen from 1 choice
usb-storage: probe of 2-2:1.0 failed with error -5
usb-storage: probe of 2-2:1.1 failed with error -5
usb-storage: device found at 3
usb-storage: waiting for device to settle before scanning
usb-storage: device scan complete
usb 2-2: USB disconnect, address 3
usb 2-2: new full speed USB device using uhci_hcd and address 4
usb 2-2: configuration #1 chosen from 1 choice
usb-storage: probe of 2-2:1.0 failed with error -5
usb-storage: probe of 2-2:1.1 failed with error -5
usb-storage: device found at 4
usb-storage: waiting for device to settle before scanning
usb-storage: device scan complete
usb 2-2: USB disconnect, address 4
usb 1-2: new high speed USB device using ehci_hcd and address 6
usb 1-2: configuration #1 chosen from 1 choice
usb-storage: device found at 6
usb-storage: waiting for device to settle before scanning
usb-storage: device found at 6
usb-storage: waiting for device to settle before scanning
usb-storage: device scan complete
usb-storage: device scan complete
usb 3-2: new full speed USB device using uhci_hcd and address 3
usb 3-2: configuration #1 chosen from 1 choice
usb-storage: probe of 3-2:1.0 failed with error -5
usb-storage: probe of 3-2:1.1 failed with error -5
usb-storage: device found at 3
usb-storage: waiting for device to settle before scanning
usb-storage: device scan complete
usb 1-2: USB disconnect, address 6
usb 1-2: new high speed USB device using ehci_hcd and address 8
usb 1-2: configuration #1 chosen from 1 choice
usb-storage: device found at 8
usb-storage: waiting for device to settle before scanning
usb-storage: device found at 8
usb-storage: waiting for device to settle before scanning
usb-storage: device scan complete
usb-storage: device scan complete
Thank you for your help in this matter!
|
Thu Oct 03, 2013 17:32
|
MareAlta: Huawei E220 when it blinks Green twice, it means the modem didn't registered on the network.
When it blinks once, means that it's registered and GSM (or 2G) is available.
When it blinks blue once, means 2G & 3G are available.
I think that you know that. No ofense. ;)
Have you observed this?
|
Page: 1 2 Next
Time in this board is UTC.
|
|
|
 |
|
 |
|