Cms error 310

Коды ошибок nhsms, коды GSM и коды статуса смс сообщений

Коды ошибок запуска программы и отправки СМС:

        0           Сообщение отправлено, и модем/телефон подтвердил 
                    успешную отправку сообщения.

        2           На компьютере нет указанного последовательного порта или
                    не найден указанный конф. файл.

        5           Не удалось открыть указанный порт COM ("нет доступа",
                    скорее всего, порт был занят другой программой).

       87           Ошибка в параметрах запуска программы или параметрах смс.

      121           Нет ответа от модема.

     1460           Нет ответа от модема (тайм-аут)

     7012           Модем не найден 

536870912           Ошибка отправки СМС.

536870929           Модем отклонил попытку отправки сообщения

536870931           Модем сообщил об ошибке отправки

536870932           Модем не сообщил результат отправки

536870933           Получен неправильный ответ модема

536870934           Ошибка ответа модема 

536870935           Одна или несколько частей длинного сообщения не были 
                    отправлены из-за ошибок (этот код ошибки только для длинных 
                    сообщений)

536870936           Все части длинного сообщения не были отправлены из-за ошибок 
                    (этот код ошибки только для длинных сообщений)

Коды ошибок CME ERROR – GSM Equipment related codes

CME ERROR: 0    Phone failure
CME ERROR: 1 	 No connection to phone
CME ERROR: 2 	 Phone adapter link reserved
CME ERROR: 3 	 Operation not allowed
CME ERROR: 4 	 Operation not supported
CME ERROR: 5 	 PH_SIM PIN required
CME ERROR: 6 	 PH_FSIM PIN required
CME ERROR: 7 	 PH_FSIM PUK required
CME ERROR: 10 	 SIM not inserted
CME ERROR: 11 	 SIM PIN required
CME ERROR: 12 	 SIM PUK required
CME ERROR: 13 	 SIM failure
CME ERROR: 14 	 SIM busy
CME ERROR: 15 	 SIM wrong
CME ERROR: 16 	 Incorrect password
CME ERROR: 17 	 SIM PIN2 required
CME ERROR: 18 	 SIM PUK2 required
CME ERROR: 20 	 Memory full
CME ERROR: 21 	 Invalid index
CME ERROR: 22 	 Not found
CME ERROR: 23 	 Memory failure
CME ERROR: 24 	 Text string too long
CME ERROR: 25 	 Invalid characters in text string
CME ERROR: 26 	 Dial string too long
CME ERROR: 27 	 Invalid characters in dial string
CME ERROR: 30 	 No network service
CME ERROR: 31 	 Network timeout
CME ERROR: 32 	 Network not allowed, emergency calls only
CME ERROR: 40 	 Network personalization PIN required
CME ERROR: 41 	 Network personalization PUK required
CME ERROR: 42 	 Network subset personalization PIN required
CME ERROR: 43 	 Network subset personalization PUK required
CME ERROR: 44 	 Service provider personalization PIN required
CME ERROR: 45 	 Service provider personalization PUK required
CME ERROR: 46 	 Corporate personalization PIN required
CME ERROR: 47 	 Corporate personalization PUK required
CME ERROR: 48 	 PH-SIM PUK required
CME ERROR: 100 	 Unknown error
CME ERROR: 103 	 Illegal MS
CME ERROR: 106 	 Illegal ME
CME ERROR: 107 	 GPRS services not allowed
CME ERROR: 111 	 PLMN not allowed
CME ERROR: 112 	 Location area not allowed
CME ERROR: 113 	 Roaming not allowed in this location area
CME ERROR: 126 	 Operation temporary not allowed
CME ERROR: 132 	 Service operation not supported
CME ERROR: 133 	 Requested service option not subscribed
CME ERROR: 134 	 Service option temporary out of order
CME ERROR: 148 	 Unspecified GPRS error
CME ERROR: 149 	 PDP authentication failure
CME ERROR: 150 	 Invalid mobile class
CME ERROR: 256 	 Operation temporarily not allowed
CME ERROR: 257 	 Call barred
CME ERROR: 258 	 Phone is busy
CME ERROR: 259 	 User abort
CME ERROR: 260 	 Invalid dial string
CME ERROR: 261 	 SS not executed
CME ERROR: 262 	 SIM Blocked
CME ERROR: 263 	 Invalid block
CME ERROR: 772 	 SIM powered down

Коды ошибок CMS Error – GSM Network related codes

CMS ERROR: 1     Unassigned number
CMS ERROR: 8     Operator determined barring
CMS ERROR: 10    Call bared
CMS ERROR: 21    Short message transfer rejected
CMS ERROR: 27    Destination out of service
CMS ERROR: 28    Unindentified subscriber
CMS ERROR: 29    Facility rejected
CMS ERROR: 30    Unknown subscriber
CMS ERROR: 38    Network out of order
CMS ERROR: 41    Temporary failure
CMS ERROR: 42    Congestion
CMS ERROR: 47    Recources unavailable
CMS ERROR: 50    Requested facility not subscribed
CMS ERROR: 69    Requested facility not implemented
CMS ERROR: 81    Invalid short message transfer reference value
CMS ERROR: 95    Invalid message unspecified
CMS ERROR: 96    Invalid mandatory information
CMS ERROR: 97    Message type non existent or not implemented
CMS ERROR: 98    Message not compatible with short message protocol
CMS ERROR: 99    Information element non-existent or not implemente
CMS ERROR: 111   Protocol error, unspecified
CMS ERROR: 127   Internetworking , unspecified
CMS ERROR: 128   Telematic internetworking not supported
CMS ERROR: 129   Short message type 0 not supported
CMS ERROR: 130   Cannot replace short message
CMS ERROR: 143   Unspecified TP-PID error
CMS ERROR: 144   Data code scheme not supported
CMS ERROR: 145   Message class not supported
CMS ERROR: 159   Unspecified TP-DCS error
CMS ERROR: 160   Command cannot be actioned
CMS ERROR: 161   Command unsupported
CMS ERROR: 175   Unspecified TP-Command error
CMS ERROR: 176   TPDU not supported
CMS ERROR: 192   SC busy
CMS ERROR: 193   No SC subscription
CMS ERROR: 194   SC System failure
CMS ERROR: 195   Invalid SME address
CMS ERROR: 196   Destination SME barred
CMS ERROR: 197   SM Rejected-Duplicate SM
CMS ERROR: 198   TP-VPF not supported
CMS ERROR: 199   TP-VP not supported
CMS ERROR: 208   D0 SIM SMS Storage full
CMS ERROR: 209   No SMS Storage capability in SIM
CMS ERROR: 210   Error in MS
CMS ERROR: 211   Memory capacity exceeded
CMS ERROR: 212   Sim application toolkit busy
CMS ERROR: 213   SIM data download error
CMS ERROR: 255   Unspecified error cause
CMS ERROR: 300   ME Failure
CMS ERROR: 301   SMS service of ME reserved
CMS ERROR: 302   Operation not allowed
CMS ERROR: 303   Operation not supported
CMS ERROR: 304   Invalid PDU mode parameter
CMS ERROR: 305   Invalid Text mode parameter
CMS ERROR: 310   SIM not inserted
CMS ERROR: 311   SIM PIN required
CMS ERROR: 312   PH-SIM PIN required
CMS ERROR: 313   SIM failure
CMS ERROR: 314   SIM busy
CMS ERROR: 315   SIM wrong
CMS ERROR: 316   SIM PUK required
CMS ERROR: 317   SIM PIN2 required
CMS ERROR: 318   SIM PUK2 required
CMS ERROR: 320   Memory failure
CMS ERROR: 321   Invalid memory index
CMS ERROR: 322   Memory full
CMS ERROR: 330   SMSC address unknown
CMS ERROR: 331   No network service
CMS ERROR: 332   Network timeout
CMS ERROR: 340   No +CNMA expected
CMS ERROR: 500   Unknown error
CMS ERROR: 512   User abort
CMS ERROR: 513   Unable to store
CMS ERROR: 514   Invalid Status
CMS ERROR: 515   Device busy or Invalid Character in string
CMS ERROR: 516   Invalid length
CMS ERROR: 517   Invalid character in PDU
CMS ERROR: 518   Invalid parameter
CMS ERROR: 519   Invalid length or character
CMS ERROR: 520   Invalid character in text
CMS ERROR: 521   Timer expired
CMS ERROR: 522   Operation temporary not allowed
CMS ERROR: 532   SIM not ready
CMS ERROR: 534   Cell Broadcast error unknown
CMS ERROR: 535   Protocol stack busy
CMS ERROR: 538   Invalid parameter

Status of a previously submitted SMS-SUBMIT (статус отправленного сообщения SMS-SUBMIT)

Short message transaction completed

0000000          Short message received by the SME
0000001          Short message forwarded by the SC to the SME but the SC is
                 unable to confirm delivery
0000010          Short message replaced by the SC

Reserved values

0000011..0001111 Reserved
0010000..0011111 Values specific to each SC

Temporary error, SC still trying to transfer SM

0100000          Congestion
0100001          SME busy
0100010          No response from SME
0100011          Service rejected
0100100          Quality of service not available
0100101          Error in SME
0100110..0101111 Reserved
0110000..0111111 Values specific to each SC

Permanent error, SC is not making any more transfer attempts

1000000          Remote procedure error
1000001          Incompatible destination
1000010          Connection rejected by SME
1000011          Not obtainable
1000100          Quality of service not available
1000101          No interworking available
1000110          SM Validity Period Expired
1000111          SM Deleted by originating SME
1001000          SM Deleted by SC Administration
1001001          SM does not exist (The SM may have previously existed in
                 the SC but the SC no longer has knowledge of it or the SM
                 may never have previously existed in the SC)
1001010..1001111 Reserved
1010000..1011111 Values specific to each SC

Temporary error, SC is not making any more transfer attempts

1100000          Congestion
1100001          SME busy
1100010          No response from SME
1100011          Service rejected
1100100          Quality of service not available
1100101          Error in SME
1100110..1101001 Reserved
1101010..1101111 Reserved
1110000..1111111 Values specific to each SC

Источник

I have similar problem. When I try configure huawei E122 to send SMS by kannel. When i give wrong PIN kannel (bearerbox) receive an error «incorrect password»


2014-05-21 11:15:38 [8419] [6] DEBUG: AT2[modem1]: <— +CPIN: SIM PIN
2014-05-21 11:15:38 [8419] [6] DEBUG: AT2[modem1]: —> AT+CPIN=»1234″^M
2014-05-21 11:15:38 [8419] [6] DEBUG: AT2[modem1]: <— OK
2014-05-21 11:15:38 [8419] [6] DEBUG: AT2[modem1]: <— +CME ERROR: incorrect password
2014-05-21 11:15:38 [8419] [6] ERROR: AT2[modem1]: Generic error: +CME ERROR: incorrect password
2014-05-21 11:15:38 [8419] [6] DEBUG: AT2[modem1]: —> AT+CPIN?^M
2014-05-21 11:15:38 [8419] [6] DEBUG: AT2[modem1]: <— +CPIN: SIM PIN
2014-05-21 11:15:38 [8419] [6] ERROR: AT2[modem1]: Initialization of device failed.

but when I give correct PIN I receive «+CMS ERROR: (U)SIM not inserted»


2014-05-21 10:56:17 [7980] [6] DEBUG: AT2[modem1]: —> AT+CSCA=»+48501200777″^M
2014-05-21 10:56:17 [7980] [6] DEBUG: AT2[modem1]: <— +CMS ERROR: (U)SIM not inserted
2014-05-21 10:56:17 [7980] [6] ERROR: AT2[modem1]: CMS ERROR: +CMS ERROR: (U)SIM not inserted
2014-05-21 10:56:17 [7980] [6] INFO: AT2[modem1]: Cannot set SMS message center, continuing

When I try send sms from Windows XP it works correct.

Logs from this two samples below

Code: Select all

# bearerbox -v 0 /etc/kannel/kannel.conf
2014-05-21 11:15:20 [8419] [0] INFO: Debug_lvl = 0, log_file = <none>, log_lvl = 0
2014-05-21 11:15:20 [8419] [0] WARNING: DLR: using default 'internal' for storage type.
2014-05-21 11:15:20 [8419] [0] INFO: DLR using storage type: internal
2014-05-21 11:15:20 [8419] [0] DEBUG: Kannel bearerbox version `1.4.3'.
Build `Mar 19 2010 03:53:52', compiler `4.4.3'.
System Linux, release 2.6.32-5-686, version #1 SMP Wed Jan 12 04:01:41 UTC 2011, machine i686.
Hostname files.inf, IP 10.10.81.100.
Libxml version 2.7.6.
Using OpenSSL 0.9.8m 25 Feb 2010.
Compiled with MySQL 5.1.45, using MySQL 5.1.49.
Using SQLite 3.6.23.
Using native malloc.

2014-05-21 11:15:20 [8419] [0] INFO: Added logfile `/var/log/kannel/bearerbox.log' with level `0'.
2014-05-21 11:15:20 [8419] [0] INFO: HTTP: Opening server at port 13000.
2014-05-21 11:15:20 [8419] [0] DEBUG: Started thread 1 (gwlib/fdset.c:poller)
2014-05-21 11:15:20 [8419] [1] DEBUG: Thread 1 (gwlib/fdset.c:poller) maps to pid 8419.
2014-05-21 11:15:20 [8419] [0] DEBUG: Started thread 2 (gwlib/http.c:server_thread)
2014-05-21 11:15:20 [8419] [2] DEBUG: Thread 2 (gwlib/http.c:server_thread) maps to pid 8419.
2014-05-21 11:15:20 [8419] [0] DEBUG: Started thread 3 (gw/bb_http.c:httpadmin_run)
2014-05-21 11:15:20 [8419] [3] DEBUG: Thread 3 (gw/bb_http.c:httpadmin_run) maps to pid 8419.
2014-05-21 11:15:20 [8419] [0] DEBUG: starting smsbox connection module
2014-05-21 11:15:20 [8419] [0] INFO: BOXC: 'smsbox-max-pending' not set, using default (100).
2014-05-21 11:15:20 [8419] [0] DEBUG: Started thread 4 (gw/bb_boxc.c:sms_to_smsboxes)
2014-05-21 11:15:20 [8419] [4] DEBUG: Thread 4 (gw/bb_boxc.c:sms_to_smsboxes) maps to pid 8419.
2014-05-21 11:15:20 [8419] [0] DEBUG: Started thread 5 (gw/bb_boxc.c:smsboxc_run)
2014-05-21 11:15:20 [8419] [5] DEBUG: Thread 5 (gw/bb_boxc.c:smsboxc_run) maps to pid 8419.
2014-05-21 11:15:20 [8419] [0] INFO: Set SMS resend frequency to 60 seconds.
2014-05-21 11:15:20 [8419] [0] INFO: SMS resend retry set to unlimited.
2014-05-21 11:15:20 [8419] [0] DEBUG: smsbox MO concatenated message handling enabled
2014-05-21 11:15:20 [8419] [0] INFO: DLR rerouting for smsc id <modem1> disabled.
2014-05-21 11:15:20 [8419] [0] INFO: AT2[modem1]: configuration doesn't show modemtype. will autodetect
2014-05-21 11:15:20 [8419] [0] DEBUG: Started thread 6 (gw/smsc/smsc_at.c:at2_device_thread)
2014-05-21 11:15:20 [8419] [6] DEBUG: Thread 6 (gw/smsc/smsc_at.c:at2_device_thread) maps to pid 8419.
2014-05-21 11:15:20 [8419] [6] DEBUG: AT2[modem1]: detecting modem speed.
2014-05-21 11:15:20 [8419] [0] DEBUG: Started thread 7 (gw/bb_smscconn.c:sms_router)
2014-05-21 11:15:20 [8419] [6] INFO: AT2[modem1]: opening device
2014-05-21 11:15:20 [8419] [0] DEBUG: starting UDP sender/receiver module
2014-05-21 11:15:20 [8419] [0] INFO: Adding interface *
2014-05-21 11:15:20 [8419] [7] DEBUG: Thread 7 (gw/bb_smscconn.c:sms_router) maps to pid 8419.
2014-05-21 11:15:20 [8419] [0] DEBUG: udpc_create: Bound to UDP <0.0.0.0:9200>
2014-05-21 11:15:20 [8419] [0] DEBUG: Started thread 8 (gw/bb_udp.c:udp_receiver)
2014-05-21 11:15:20 [8419] [8] DEBUG: Thread 8 (gw/bb_udp.c:udp_receiver) maps to pid 8419.
2014-05-21 11:15:20 [8419] [6] DEBUG: AT2[modem1]: device opened. Telnet mode = 0
2014-05-21 11:15:20 [8419] [0] DEBUG: Started thread 9 (gw/bb_udp.c:udp_sender)
2014-05-21 11:15:20 [8419] [0] DEBUG: udpc_create: Bound to UDP <0.0.0.0:9201>
2014-05-21 11:15:20 [8419] [9] DEBUG: Thread 9 (gw/bb_udp.c:udp_sender) maps to pid 8419.
2014-05-21 11:15:20 [8419] [0] DEBUG: Started thread 10 (gw/bb_udp.c:udp_receiver)
2014-05-21 11:15:20 [8419] [10] DEBUG: Thread 10 (gw/bb_udp.c:udp_receiver) maps to pid 8419.
2014-05-21 11:15:20 [8419] [0] DEBUG: Started thread 11 (gw/bb_udp.c:udp_sender)
2014-05-21 11:15:20 [8419] [11] DEBUG: Thread 11 (gw/bb_udp.c:udp_sender) maps to pid 8419.
2014-05-21 11:15:20 [8419] [0] DEBUG: starting wapbox connection module
2014-05-21 11:15:20 [8419] [0] DEBUG: Started thread 12 (gw/bb_boxc.c:wdp_to_wapboxes)
2014-05-21 11:15:20 [8419] [0] DEBUG: Started thread 13 (gw/bb_boxc.c:wapboxc_run)
2014-05-21 11:15:20 [8419] [0] DEBUG: starting WDP router
2014-05-21 11:15:20 [8419] [0] DEBUG: Started thread 14 (gw/bearerbox.c:wdp_router)
2014-05-21 11:15:20 [8419] [0] INFO: ----------------------------------------
2014-05-21 11:15:20 [8419] [0] INFO: Kannel bearerbox II version 1.4.3 starting
2014-05-21 11:15:20 [8419] [0] INFO: MAIN: Start-up done, entering mainloop
2014-05-21 11:15:20 [8419] [0] DEBUG: AT2[modem1]: start called
2014-05-21 11:15:20 [8419] [13] DEBUG: Thread 13 (gw/bb_boxc.c:wapboxc_run) maps to pid 8419.
2014-05-21 11:15:20 [8419] [12] DEBUG: Thread 12 (gw/bb_boxc.c:wdp_to_wapboxes) maps to pid 8419.
2014-05-21 11:15:20 [8419] [14] DEBUG: Thread 14 (gw/bearerbox.c:wdp_router) maps to pid 8419.
2014-05-21 11:15:21 [8419] [6] DEBUG: AT2[modem1]: device opened
2014-05-21 11:15:21 [8419] [6] INFO: AT2[modem1]: speed set to 115200
2014-05-21 11:15:21 [8419] [6] DEBUG: AT2[modem1]: --> ^M
2014-05-21 11:15:23 [8419] [6] DEBUG: AT2[modem1]: --> AT^M
2014-05-21 11:15:23 [8419] [6] DEBUG: AT2[modem1]: <-- OK
2014-05-21 11:15:23 [8419] [6] INFO: AT2[modem1]: Closing device
2014-05-21 11:15:23 [8419] [6] INFO: AT2[modem1]: detect speed is 115200
2014-05-21 11:15:23 [8419] [6] DEBUG: AT2[modem1]: detecting modem type
2014-05-21 11:15:23 [8419] [6] INFO: AT2[modem1]: opening device
2014-05-21 11:15:23 [8419] [6] DEBUG: AT2[modem1]: device opened. Telnet mode = 0
2014-05-21 11:15:24 [8419] [6] DEBUG: AT2[modem1]: device opened
2014-05-21 11:15:24 [8419] [6] INFO: AT2[modem1]: speed set to 115200
2014-05-21 11:15:24 [8419] [6] DEBUG: AT2[modem1]: --> ^M
2014-05-21 11:15:26 [8419] [6] DEBUG: AT2[modem1]: --> AT^M
2014-05-21 11:15:26 [8419] [6] DEBUG: AT2[modem1]: <-- OK
2014-05-21 11:15:26 [8419] [6] DEBUG: AT2[modem1]: --> AT&F^M
2014-05-21 11:15:26 [8419] [6] DEBUG: AT2[modem1]: <-- OK
2014-05-21 11:15:26 [8419] [6] DEBUG: AT2[modem1]: --> ATE0^M
2014-05-21 11:15:26 [8419] [6] DEBUG: AT2[modem1]: <-- OK
2014-05-21 11:15:26 [8419] [6] DEBUG: AT2[modem1]: --> ATI^M
2014-05-21 11:15:26 [8419] [6] DEBUG: AT2[modem1]: <-- Manufacturer: huawei
2014-05-21 11:15:26 [8419] [6] DEBUG: AT2[modem1]: <-- Model: E122
2014-05-21 11:15:26 [8419] [6] DEBUG: AT2[modem1]: <-- Revision: 11.009.01.00.55
2014-05-21 11:15:26 [8419] [6] DEBUG: AT2[modem1]: <-- IMEI: 356881037088864
2014-05-21 11:15:26 [8419] [6] DEBUG: AT2[modem1]: <-- +GCAP: +CGSM,+DS,+ES
2014-05-21 11:15:26 [8419] [6] DEBUG: AT2[modem1]: <-- OK
2014-05-21 11:15:26 [8419] [6] DEBUG: AT2[modem1]: Cannot detect modem, using generic
2014-05-21 11:15:26 [8419] [6] DEBUG: AT2[modem1]: Reading modem definitions from </etc/kannel/kannel.conf>
2014-05-21 11:15:26 [8419] [6] DEBUG: AT2[modem1]: Found <1> modems in config
2014-05-21 11:15:26 [8419] [6] DEBUG: AT2[modem1]: --> AT+CSMS=?^M
2014-05-21 11:15:26 [8419] [6] DEBUG: AT2[modem1]: <-- +CME ERROR: SIM PIN required
2014-05-21 11:15:26 [8419] [6] INFO: AT2[modem1]: Closing device
2014-05-21 11:15:26 [8419] [6] INFO: AT2[modem1]: opening device
2014-05-21 11:15:26 [8419] [6] DEBUG: AT2[modem1]: device opened. Telnet mode = 0
2014-05-21 11:15:26 [8419] [6] DEBUG: AT2[modem1]: device opened
2014-05-21 11:15:26 [8419] [6] INFO: AT2[modem1]: Logging in
2014-05-21 11:15:27 [8419] [6] INFO: AT2[modem1]: init device
2014-05-21 11:15:27 [8419] [6] INFO: AT2[modem1]: speed set to 115200
2014-05-21 11:15:27 [8419] [6] DEBUG: AT2[modem1]: --> ATZ^M
2014-05-21 11:15:27 [8419] [6] DEBUG: AT2[modem1]: <-- OK
2014-05-21 11:15:27 [8419] [6] DEBUG: AT2[modem1]: --> AT^M
2014-05-21 11:15:27 [8419] [6] DEBUG: AT2[modem1]: <-- OK
2014-05-21 11:15:27 [8419] [6] DEBUG: AT2[modem1]: --> AT&F^M
2014-05-21 11:15:27 [8419] [6] DEBUG: AT2[modem1]: <-- OK
2014-05-21 11:15:27 [8419] [6] DEBUG: AT2[modem1]: --> ATE0^M
2014-05-21 11:15:27 [8419] [6] DEBUG: AT2[modem1]: <-- OK
2014-05-21 11:15:27 [8419] [6] DEBUG: AT2[modem1]: --> AT+IFC=2,2^M
2014-05-21 11:15:27 [8419] [6] DEBUG: AT2[modem1]: <-- COMMAND NOT SUPPORT
2014-05-21 11:15:31 [8419] [6] INFO: AT2[modem1]: cannot enable hardware handshake
2014-05-21 11:15:31 [8419] [6] DEBUG: AT2[modem1]: --> AT+CPIN?^M
2014-05-21 11:15:31 [8419] [6] DEBUG: AT2[modem1]: <-- +CPIN: SIM PIN
2014-05-21 11:15:31 [8419] [6] DEBUG: AT2[modem1]: --> AT+CPIN="1234"^M
2014-05-21 11:15:31 [8419] [6] DEBUG: AT2[modem1]: <-- OK
2014-05-21 11:15:31 [8419] [6] DEBUG: AT2[modem1]: <-- +CME ERROR: incorrect password
2014-05-21 11:15:31 [8419] [6] ERROR: AT2[modem1]: Generic error: +CME ERROR: incorrect password
2014-05-21 11:15:31 [8419] [6] DEBUG: AT2[modem1]: --> AT+CPIN?^M
2014-05-21 11:15:31 [8419] [6] DEBUG: AT2[modem1]: <-- +CPIN: SIM PIN
2014-05-21 11:15:31 [8419] [6] ERROR: AT2[modem1]: Initialization of device failed.
2014-05-21 11:15:31 [8419] [6] INFO: AT2[modem1]: Closing device
2014-05-21 11:15:31 [8419] [6] ERROR: AT2[modem1]: Couldn't connect (retrying in 10 seconds).

Code: Select all

2014-05-21 10:56:06 [7980] [0] INFO: Debug_lvl = 0, log_file = <none>, log_lvl = 0
2014-05-21 10:56:06 [7980] [0] WARNING: DLR: using default 'internal' for storage type.
2014-05-21 10:56:06 [7980] [0] INFO: DLR using storage type: internal
2014-05-21 10:56:06 [7980] [0] DEBUG: Kannel bearerbox version `1.4.3'.
Build `Mar 19 2010 03:53:52', compiler `4.4.3'.
System Linux, release 2.6.32-5-686, version #1 SMP Wed Jan 12 04:01:41 UTC 2011, machine i686.
Hostname xxxxxxxxxxxxxxx
Libxml version 2.7.6.
Using OpenSSL 0.9.8m 25 Feb 2010.
Compiled with MySQL 5.1.45, using MySQL 5.1.49.
Using SQLite 3.6.23.
Using native malloc.

2014-05-21 10:56:06 [7980] [0] INFO: Added logfile `/var/log/kannel/bearerbox.log' with level `0'.
2014-05-21 10:56:06 [7980] [0] INFO: HTTP: Opening server at port 13000.
2014-05-21 10:56:06 [7980] [0] DEBUG: Started thread 1 (gwlib/fdset.c:poller)
2014-05-21 10:56:06 [7980] [1] DEBUG: Thread 1 (gwlib/fdset.c:poller) maps to pid 7980.
2014-05-21 10:56:06 [7980] [0] DEBUG: Started thread 2 (gwlib/http.c:server_thread)
2014-05-21 10:56:06 [7980] [2] DEBUG: Thread 2 (gwlib/http.c:server_thread) maps to pid 7980.
2014-05-21 10:56:06 [7980] [0] DEBUG: Started thread 3 (gw/bb_http.c:httpadmin_run)
2014-05-21 10:56:06 [7980] [3] DEBUG: Thread 3 (gw/bb_http.c:httpadmin_run) maps to pid 7980.
2014-05-21 10:56:06 [7980] [0] DEBUG: starting smsbox connection module
2014-05-21 10:56:06 [7980] [0] INFO: BOXC: 'smsbox-max-pending' not set, using default (100).
2014-05-21 10:56:06 [7980] [0] DEBUG: Started thread 4 (gw/bb_boxc.c:sms_to_smsboxes)
2014-05-21 10:56:06 [7980] [4] DEBUG: Thread 4 (gw/bb_boxc.c:sms_to_smsboxes) maps to pid 7980.
2014-05-21 10:56:06 [7980] [0] DEBUG: Started thread 5 (gw/bb_boxc.c:smsboxc_run)
2014-05-21 10:56:06 [7980] [0] INFO: Set SMS resend frequency to 60 seconds.
2014-05-21 10:56:06 [7980] [0] INFO: SMS resend retry set to unlimited.
2014-05-21 10:56:06 [7980] [0] DEBUG: smsbox MO concatenated message handling enabled
2014-05-21 10:56:06 [7980] [0] INFO: DLR rerouting for smsc id <modem1> disabled.
2014-05-21 10:56:06 [7980] [0] INFO: AT2[modem1]: configuration doesn't show modemtype. will autodetect
2014-05-21 10:56:06 [7980] [0] DEBUG: Started thread 6 (gw/smsc/smsc_at.c:at2_device_thread)
2014-05-21 10:56:06 [7980] [6] DEBUG: Thread 6 (gw/smsc/smsc_at.c:at2_device_thread) maps to pid 7980.
2014-05-21 10:56:06 [7980] [6] DEBUG: AT2[modem1]: detecting modem speed.
2014-05-21 10:56:06 [7980] [0] DEBUG: Started thread 7 (gw/bb_smscconn.c:sms_router)
2014-05-21 10:56:06 [7980] [6] INFO: AT2[modem1]: opening device
2014-05-21 10:56:06 [7980] [0] DEBUG: starting UDP sender/receiver module
2014-05-21 10:56:06 [7980] [5] DEBUG: Thread 5 (gw/bb_boxc.c:smsboxc_run) maps to pid 7980.
2014-05-21 10:56:06 [7980] [7] DEBUG: Thread 7 (gw/bb_smscconn.c:sms_router) maps to pid 7980.
2014-05-21 10:56:06 [7980] [0] INFO: Adding interface *
2014-05-21 10:56:06 [7980] [0] DEBUG: udpc_create: Bound to UDP <0.0.0.0:9200>
2014-05-21 10:56:06 [7980] [0] DEBUG: Started thread 8 (gw/bb_udp.c:udp_receiver)
2014-05-21 10:56:06 [7980] [0] DEBUG: Started thread 9 (gw/bb_udp.c:udp_sender)
2014-05-21 10:56:06 [7980] [6] DEBUG: AT2[modem1]: device opened. Telnet mode = 0
2014-05-21 10:56:06 [7980] [0] DEBUG: udpc_create: Bound to UDP <0.0.0.0:9201>
2014-05-21 10:56:06 [7980] [0] DEBUG: Started thread 10 (gw/bb_udp.c:udp_receiver)
2014-05-21 10:56:06 [7980] [0] DEBUG: Started thread 11 (gw/bb_udp.c:udp_sender)
2014-05-21 10:56:06 [7980] [0] DEBUG: starting wapbox connection module
2014-05-21 10:56:06 [7980] [11] DEBUG: Thread 11 (gw/bb_udp.c:udp_sender) maps to pid 7980.
2014-05-21 10:56:06 [7980] [0] DEBUG: Started thread 12 (gw/bb_boxc.c:wdp_to_wapboxes)
2014-05-21 10:56:06 [7980] [12] DEBUG: Thread 12 (gw/bb_boxc.c:wdp_to_wapboxes) maps to pid 7980.
2014-05-21 10:56:06 [7980] [9] DEBUG: Thread 9 (gw/bb_udp.c:udp_sender) maps to pid 7980.
2014-05-21 10:56:06 [7980] [8] DEBUG: Thread 8 (gw/bb_udp.c:udp_receiver) maps to pid 7980.
2014-05-21 10:56:06 [7980] [10] DEBUG: Thread 10 (gw/bb_udp.c:udp_receiver) maps to pid 7980.
2014-05-21 10:56:06 [7980] [0] DEBUG: Started thread 13 (gw/bb_boxc.c:wapboxc_run)
2014-05-21 10:56:06 [7980] [0] DEBUG: starting WDP router
2014-05-21 10:56:06 [7980] [0] DEBUG: Started thread 14 (gw/bearerbox.c:wdp_router)
2014-05-21 10:56:06 [7980] [13] DEBUG: Thread 13 (gw/bb_boxc.c:wapboxc_run) maps to pid 7980.
2014-05-21 10:56:06 [7980] [0] INFO: ----------------------------------------
2014-05-21 10:56:06 [7980] [0] INFO: Kannel bearerbox II version 1.4.3 starting
2014-05-21 10:56:06 [7980] [0] INFO: MAIN: Start-up done, entering mainloop
2014-05-21 10:56:06 [7980] [14] DEBUG: Thread 14 (gw/bearerbox.c:wdp_router) maps to pid 7980.
2014-05-21 10:56:06 [7980] [0] DEBUG: AT2[modem1]: start called
2014-05-21 10:56:07 [7980] [6] DEBUG: AT2[modem1]: device opened
2014-05-21 10:56:07 [7980] [6] INFO: AT2[modem1]: speed set to 115200
2014-05-21 10:56:07 [7980] [6] DEBUG: AT2[modem1]: --> ^M
2014-05-21 10:56:09 [7980] [6] DEBUG: AT2[modem1]: --> AT^M
2014-05-21 10:56:09 [7980] [6] DEBUG: AT2[modem1]: <-- OK
2014-05-21 10:56:09 [7980] [6] INFO: AT2[modem1]: Closing device
2014-05-21 10:56:09 [7980] [6] INFO: AT2[modem1]: detect speed is 115200
2014-05-21 10:56:09 [7980] [6] DEBUG: AT2[modem1]: detecting modem type
2014-05-21 10:56:09 [7980] [6] INFO: AT2[modem1]: opening device
2014-05-21 10:56:09 [7980] [6] DEBUG: AT2[modem1]: device opened. Telnet mode = 0
2014-05-21 10:56:10 [7980] [6] DEBUG: AT2[modem1]: device opened
2014-05-21 10:56:10 [7980] [6] INFO: AT2[modem1]: speed set to 115200
2014-05-21 10:56:10 [7980] [6] DEBUG: AT2[modem1]: --> ^M
2014-05-21 10:56:12 [7980] [6] DEBUG: AT2[modem1]: --> AT^M
2014-05-21 10:56:12 [7980] [6] DEBUG: AT2[modem1]: <-- OK
2014-05-21 10:56:12 [7980] [6] DEBUG: AT2[modem1]: --> AT&F^M
2014-05-21 10:56:12 [7980] [6] DEBUG: AT2[modem1]: <-- OK
2014-05-21 10:56:12 [7980] [6] DEBUG: AT2[modem1]: --> ATE0^M
2014-05-21 10:56:12 [7980] [6] DEBUG: AT2[modem1]: <-- OK
2014-05-21 10:56:12 [7980] [6] DEBUG: AT2[modem1]: --> ATI^M
2014-05-21 10:56:12 [7980] [6] DEBUG: AT2[modem1]: <-- Manufacturer: huawei
2014-05-21 10:56:12 [7980] [6] DEBUG: AT2[modem1]: <-- Model: E122
2014-05-21 10:56:12 [7980] [6] DEBUG: AT2[modem1]: <-- Revision: 11.009.01.00.55
2014-05-21 10:56:12 [7980] [6] DEBUG: AT2[modem1]: <-- IMEI: xxxxxxxxxxxxxx
2014-05-21 10:56:12 [7980] [6] DEBUG: AT2[modem1]: <-- +GCAP: +CGSM,+DS,+ES
2014-05-21 10:56:12 [7980] [6] DEBUG: AT2[modem1]: <-- OK
2014-05-21 10:56:12 [7980] [6] DEBUG: AT2[modem1]: Cannot detect modem, using generic
2014-05-21 10:56:12 [7980] [6] DEBUG: AT2[modem1]: Reading modem definitions from </etc/kannel/kannel.conf>
2014-05-21 10:56:12 [7980] [6] DEBUG: AT2[modem1]: Found <1> modems in config
2014-05-21 10:56:12 [7980] [6] DEBUG: AT2[modem1]: --> AT+CSMS=?^M
2014-05-21 10:56:12 [7980] [6] DEBUG: AT2[modem1]: <-- +CSMS: (0,1)
2014-05-21 10:56:12 [7980] [6] DEBUG: AT2[modem1]: <-- OK
2014-05-21 10:56:12 [7980] [6] INFO: AT2[modem1]: Phase 2+ is supported
2014-05-21 10:56:12 [7980] [6] INFO: AT2[modem1]: Closing device
2014-05-21 10:56:12 [7980] [6] INFO: AT2[modem1]: opening device
2014-05-21 10:56:12 [7980] [6] DEBUG: AT2[modem1]: device opened. Telnet mode = 0
2014-05-21 10:56:12 [7980] [6] DEBUG: AT2[modem1]: device opened
2014-05-21 10:56:12 [7980] [6] INFO: AT2[modem1]: Logging in
2014-05-21 10:56:13 [7980] [6] INFO: AT2[modem1]: init device
2014-05-21 10:56:13 [7980] [6] INFO: AT2[modem1]: speed set to 115200
2014-05-21 10:56:13 [7980] [6] DEBUG: AT2[modem1]: --> ATZ^M
2014-05-21 10:56:13 [7980] [6] DEBUG: AT2[modem1]: <-- OK
2014-05-21 10:56:13 [7980] [6] DEBUG: AT2[modem1]: --> AT^M
2014-05-21 10:56:13 [7980] [6] DEBUG: AT2[modem1]: <-- OK
2014-05-21 10:56:13 [7980] [6] DEBUG: AT2[modem1]: --> AT&F^M
2014-05-21 10:56:13 [7980] [6] DEBUG: AT2[modem1]: <-- OK
2014-05-21 10:56:13 [7980] [6] DEBUG: AT2[modem1]: --> ATE0^M
2014-05-21 10:56:13 [7980] [6] DEBUG: AT2[modem1]: <-- OK
2014-05-21 10:56:13 [7980] [6] DEBUG: AT2[modem1]: --> AT+IFC=2,2^M
2014-05-21 10:56:13 [7980] [6] DEBUG: AT2[modem1]: <-- COMMAND NOT SUPPORT
2014-05-21 10:56:17 [7980] [6] INFO: AT2[modem1]: cannot enable hardware handshake
2014-05-21 10:56:17 [7980] [6] DEBUG: AT2[modem1]: --> AT+CPIN?^M
2014-05-21 10:56:17 [7980] [6] DEBUG: AT2[modem1]: <-- +CPIN: READY
2014-05-21 10:56:17 [7980] [6] DEBUG: AT2[modem1]: <-- OK
2014-05-21 10:56:17 [7980] [6] DEBUG: AT2[modem1]: --> AT+CSCA="+48501200777"^M
2014-05-21 10:56:17 [7980] [6] DEBUG: AT2[modem1]: <-- +CMS ERROR: (U)SIM not inserted
2014-05-21 10:56:17 [7980] [6] ERROR: AT2[modem1]: CMS ERROR: +CMS ERROR: (U)SIM not inserted
2014-05-21 10:56:17 [7980] [6] INFO: AT2[modem1]: Cannot set SMS message center, continuing
2014-05-21 10:56:17 [7980] [6] DEBUG: AT2[modem1]: --> AT+CMGF=0^M
2014-05-21 10:56:17 [7980] [6] DEBUG: AT2[modem1]: <-- OK
2014-05-21 10:56:17 [7980] [6] DEBUG: AT2[modem1]: --> AT+CSMS=?^M
2014-05-21 10:56:17 [7980] [6] DEBUG: AT2[modem1]: <-- +CSMS: (0,1)
2014-05-21 10:56:17 [7980] [6] DEBUG: AT2[modem1]: <-- OK
2014-05-21 10:56:17 [7980] [6] INFO: AT2[modem1]: Phase 2+ is supported
2014-05-21 10:56:17 [7980] [6] DEBUG: AT2[modem1]: --> AT+CSMS=1^M
2014-05-21 10:56:17 [7980] [6] DEBUG: AT2[modem1]: <-- +CSMS: 1,1,0
2014-05-21 10:56:17 [7980] [6] DEBUG: AT2[modem1]: <-- OK
2014-05-21 10:56:17 [7980] [6] DEBUG: AT2[modem1]: --> AT+CNMI=1,2,0,1,0^M
2014-05-21 10:56:17 [7980] [6] DEBUG: AT2[modem1]: <-- OK
2014-05-21 10:56:17 [7980] [6] INFO: AT2[modem1]: AT SMSC successfully opened.
2014-05-21 10:56:19 [7980] [6] DEBUG: AT2[modem1]: --> AT+CPMS?^M
2014-05-21 10:56:19 [7980] [6] DEBUG: AT2[modem1]: <-- +CPMS: "SM",0,0,"SM",0,0,"SM",0,0
2014-05-21 10:56:19 [7980] [6] DEBUG: AT2[modem1]: <-- OK

Any help will be greatly appreciated.

Best Regards,
Krystian

Источник

Код ошибки 310: ERR_TOO_MANY_REDIRECTS при попытке зайти на сайт означает, что браузер попал в бесконечный цикл переадресации. К примеру, одна страница сайта перенаправляет пользователя на другую, на которой стоит редирект обратно.

Обычно ошибка на стороне сайта, когда при использовании CMS (WordPress, Joomla) неправильно настроен файл htaccess. Ошибка может возникать при неправильном переносе сайта с хостинга на хостинг или при некорректном переезде на SSL-сертификат. Владельцам сайтов стоит убедиться, что все редиректы в htaccess прописаны верно.

Раньше браузеры тормозили на этом моменте, пытаясь выполнить бесконечный цикл переадресаций. Сейчас Google Chrome или Яндекс Браузер быстро распознают цикл и покажут ошибку ERR_TOO_MANY_REDIRECTS (This page isn’t working. domain.com redirected you too many times., слишком много редиректов) или This webpage has a redirect loop problem.

Ошибка ERR-TOO-MANY-REDIRECTS

Если ошибка с редиректами возникает только на одном сайте, значит проблема в htaccess и нужно ждать, пока владелец сайта все починит. Если же бесконечные редиректы появились во всех браузерах и/или при заходе на любой сайт, то проблема на стороне пользователя. Ниже — советы по исправлению ошибки со стороны пользователя и со стороны владельца сайта.

Со стороны пользователя:

  1. Сверить настройки даты и времени. Неверно выставленные настройки могут вызывать бесконечную переадресацию на многих защищенных сайтах.
  2. Очистить кэш и файлы cookie. Расположение и способ очистки куки на своем браузере можно посмотреть в статье Где находятся Cookie. Можно очистить куки только для того домена, на котором появляется ошибка.
  3. Отключить все лишние плагины и расширения. В ряде случаев надстройки для браузера могут устанавливаться без ведома пользователя — стоит проверить, не активно ли чего лишнего.
  4. Если ничего не помогает и редиректы продолжаются на всех сайтах, можно полностью сбросить настройки браузера. В Google Chrome это можно сделать, введя в адресной строке chrome://settings/resetProfileSettings. Вся не сохраненная информация из браузера будет удалена.

Возврат к стандартным настройкам должен гарантированно исправить ошибку ERR_TOO_MANY_REDIRECTS, если она действительно появилась по вине браузера. Сначала следует попробовать очистку кэша и cookies, также можно воспользоваться другим браузером. Если ошибка появляется только на одном сайте, но во всех браузерах — проблема в сайте.

Что делать владельцу сайта:

  1. Проверить корректность содержимого файла htaccess.
  2. Отключить плагины и функционал сторонних сервисов, использующие редиректы.
  3. Если недавно прописывались редиректы для чего-либо — проверить их на корректность. Особенно касается SSL и его первоначальной настройки.
  4. Очистить кэш обратного прокси-сервера, если используется (Cloudflare, Sucuri). В Cloudflare не должна быть включена опция Flexible SSL, если на сайте уже есть сертификат — иначе выйдет тот самый бесконечный цикл редиректов.
  5. Если ничего непонятно — использовать утилиту Redirect Checker. Она поможет определить, что именно и как перенаправляется. К примеру, это может быть цикличный редирект с http на https.

С настройками сервера и содержимым файла htaccess стоит ознакомиться в любом случае. Неожиданные проблемы с сайтом часто говорят о взломе или вирусах — а это гораздо большая проблема, чем просто редирект.

Источник

0 Пользователей и 1 Гость просматривают эту тему.

  • 2 Ответов
  • 7690 Просмотров

В общем-то, есть форум: http://team-med.ru/forum/index.html?view=listcat&catid=0&func=listcat&do=index.html… если зайти в любую тему — выскакивает ошибка:

На этой странице обнаружена циклическая переадресация
Веб-страница http://team-med.ru/forum.html?func=view&catid=0&id=3&view=listcat#3 привела к избыточному количеству переадресаций. Чтобы устранить эту проблему, можно удалить файлы cookie для этого сайта или разрешить файлы cookie независимых поставщиков. Если проблема сохранится, возможно, она связана с конфигурацией сервера, а не с вашим компьютером.
Вот несколько советов и рекомендаций:
Обновите эту страницу позже.
Подробнее об этой неполадке.
Ошибка 310 (net::ERR_TOO_MANY_REDIRECTS): Обнаружено слишком много переадресаций.

При отключенном SEO в опциях сайта — все работает, при включенном — такая беда.

Настройки SEO самого форума не помогают: перепробовал все комбинации.

На сайте установлены:
— Joomla 1.5.23
— kunena 1.6.3
— JoomSEF 3.8.2

« Последнее редактирование: 29.05.2011, 22:13:35 от ChaosHead »

Записан

Это вы наверное пункт меню меняли.
Нужно у далить пункт меню форум и меню kunenamenu. Потом в админке форума есть кнопка создать меню. Потом переносите пункт меню форум в то меню, которое нужно.

Записан

Создание сайтов, шаблонов, помощь в решении проблем.

да, помогло… еще скачал дополнение JoomSEF для Kunena — теперь и на форуме красивые адреса тем :)

Источник

There are two types of GSM error codes: CMS Error codes and CME Error codes that your GSM may return when sending an SMS.

The CMS error codes start with ‘+CMS Error:‘ and are always network related errors. The CME error codes start with ‘+CME Error:‘ and are always device (equipment) related errors.

CME Errors (GSM equipment errors)

CME Error Description
0 Phone failure
1 No connection to phone
2 Phone adapter link reserved
3 Operation not allowed
4 Operation not supported
5 PH_SIM PIN required
6 PH_FSIM PIN required
7 PH_FSIM PUK required
10 SIM not inserted
11 SIM PIN required
12 SIM PUK required
13 SIM failure
14 SIM busy
15 SIM wrong
16 Incorrect password
17 SIM PIN2 required
18 SIM PUK2 required
20 Memory full
21 Invalid index
22 Not found
23 Memory failure
24 Text string too long
25 Invalid characters in text string
26 Dial string too long
27 Invalid characters in dial string
30 No network service
31 Network timeout
32 Network not allowed, emergency calls only
40 Network personalization PIN required
41 Network personalization PUK required
42 Network subset personalization PIN required
43 Network subset personalization PUK required
44 Service provider personalization PIN required
45 Service provider personalization PUK required
46 Corporate personalization PIN required
47 Corporate personalization PUK required
48 PH-SIM PUK required
100 Unknown error
103 Illegal MS
106 Illegal ME
107 GPRS services not allowed
111 PLMN not allowed
112 Location area not allowed
113 Roaming not allowed in this location area
126 Operation temporary not allowed
132 Service operation not supported
133 Requested service option not subscribed
134 Service option temporary out of order
148 Unspecified GPRS error
149 PDP authentication failure
150 Invalid mobile class
256 Operation temporarily not allowed
257 Call barred
258 Phone is busy
259 User abort
260 Invalid dial string
261 SS not executed
262 SIM Blocked
263 Invalid block
772 SIM powered down

CMS Errors (GSM Network errors)

CMS Error Description
1 Unassigned number
8 Operator determined barring
10 Call bared
21 Short message transfer rejected
27 Destination out of service
28 Unindentified subscriber
29 Facility rejected
30 Unknown subscriber
38 Network out of order
41 Temporary failure
42 Congestion
47 Recources unavailable
50 Requested facility not subscribed
69 Requested facility not implemented
81 Invalid short message transfer reference value
95 Invalid message unspecified
96 Invalid mandatory information
97 Message type non existent or not implemented
98 Message not compatible with short message protocol
99 Information element non-existent or not implemente
111 Protocol error, unspecified
127 Internetworking , unspecified
128 Telematic internetworking not supported
129 Short message type 0 not supported
130 Cannot replace short message
143 Unspecified TP-PID error
144 Data code scheme not supported
145 Message class not supported
159 Unspecified TP-DCS error
160 Command cannot be actioned
161 Command unsupported
175 Unspecified TP-Command error
176 TPDU not supported
192 SC busy
193 No SC subscription
194 SC System failure
195 Invalid SME address
196 Destination SME barred
197 SM Rejected-Duplicate SM
198 TP-VPF not supported
199 TP-VP not supported
208 D0 SIM SMS Storage full
209 No SMS Storage capability in SIM
210 Error in MS
211 Memory capacity exceeded
212 Sim application toolkit busy
213 SIM data download error
255 Unspecified error cause
300 ME Failure
301 SMS service of ME reserved
302 Operation not allowed
303 Operation not supported
304 Invalid PDU mode parameter
305 Invalid Text mode parameter
310 SIM not inserted
311 SIM PIN required
312 PH-SIM PIN required
313 SIM failure
314 SIM busy
315 SIM wrong
316 SIM PUK required
317 SIM PIN2 required
318 SIM PUK2 required
320 Memory failure
321 Invalid memory index
322 Memory full
330 SMSC address unknown
331 No network service
332 Network timeout
340 No +CNMA expected
500 Unknown error
512 User abort
513 Unable to store
514 Invalid Status
515 Device busy or Invalid Character in string
516 Invalid length
517 Invalid character in PDU
518 Invalid parameter
519 Invalid length or character
520 Invalid character in text
521 Timer expired
522 Operation temporary not allowed
532 SIM not ready
534 Cell Broadcast error unknown
535 Protocol stack busy
538 Invalid parameter

Источник

Connect

  • Add your SIM card to the Telit GSM modem and attach it via USB port to your server.
  • To find the port where your GSM modem is attached, execute the following script after you’ve marked it as executable.

#!/bin/bash
for sysdevpath in $(find /sys/bus/usb/devices/usb*/ -name dev); do
(
syspath=”${sysdevpath%/dev}”
devname=”$(udevadm info -q name -p $syspath)”
[[ “$devname” == “bus/”* ]] && continue
eval “$(udevadm info -q property –export -p $syspath)”
[[ -z “$ID_SERIAL” ]] && continue
echo “/dev/$devname – $ID_SERIAL”
)
done

# ./listdev.sh/dev/ttyACM0 - Telit_wireless_solutions_Telit_Wireless_Module_351579057468926/dev/ttyACM1 - Telit_wireless_solutions_Telit_Wireless_Module_351579057468926/dev/ttyACM2 - Telit_wireless_solutions_Telit_Wireless_Module_351579057468926/dev/ttyACM3 - Telit_wireless_solutions_Telit_Wireless_Module_351579057468926/dev/ttyACM4 - Telit_wireless_solutions_Telit_Wireless_Module_351579057468926/dev/ttyACM5 - Telit_wireless_solutions_Telit_Wireless_Module_351579057468926/dev/ttyACM6 - Telit_wireless_solutions_Telit_Wireless_Module_351579057468926/dev/input/mouse2 - VMware_VMware_Virtual_USB_Mouse/dev/input/event4 - VMware_VMware_Virtual_USB_Mouse/dev/input/js0 - VMware_VMware_Virtual_USB_Mouse/dev/input/mouse3 - VMware_VMware_Virtual_USB_Mouse/dev/input/event5 - VMware_VMware_Virtual_USB_Mouse

Take a note of the device-path (/dev/ttyACM0)

Configuration

/etc/smsd.conf: This sample configuration file works fine in our productive environment on a SIM card without PIN code enabled – if you need to configure a PIN (if enabled) try configuring “pin=” . Make sure you use the correct device-path from above (device=/dev/ttyACM0) at “device=”.

# Example smsd.conf. Read the manual for a description
# once your configuration is OK, set log level lower (5 is good in most cases)
devices=GSM1
logfile=/var/log/smsd/smsd.log
loglevel=8
user=root
infofile=/var/run/smsd/smsd.working
pidfile=/var/run/smsd/smsd.pid
# 3.1.5 introduced smart logging
smart_logging=yes

[GSM1]
init=ATE0
incoming=no
rtscts=no
cs_convert=yes
report=no
mode=new
device=/dev/ttyACM0
pin=0014
baudrate=115200

Testing

Configure your hyperterminal session by using minicom -s

# minicom -s

Select “Serial port setup”

Make sure your settings looks like this (A – Serial Device must match the path from above, E – Bps/Par/Bits must be 19200 8N1 or 115200 8N1). Press ENTER to save your setting.

Select Exit to open the connection to the GSM modem

The connection is initalized

The connection is open, the GSM modem is ready to receive commands

Send SMS by using AT commands. NOTE: In this example we have removed the PIN of the SIM card, if the PIN is still present make sure you are properly authenticated – additional details please see the chapter ‘PIN codes by using AT commands’ below)ATOKAT+CMGF=1 -----> set message format, see AT referenceOKAT+CMGS="+41796316771"> Hello World!><PRESS CTRL-Z to send the message>
+CMGS: 255OK

To exit minicom press CRTL-A and then x or q.

Services

Make sure the smsd service is enabled to start on boot# chkconfig --list smsdsmsd 0:off 1:off 2:off 3:on 4:off 5:off 6:off

Enable the service on boot for runlevel 3,4 and 5 by using the following command# chkconfig smsd on

To start/stop the service use following command# service smsd stop# service smsd start

Make sure the smsd service is running by using the command line
# service smsd statussmsd (pid 1476 1475) is running...
Or check the service status via OP5 webbased GUI

Make sure you can send a SMS message by using OP5 webbased GUI.

To send SMS notifications, make sure your contacts have filled out the ‘Pager’ information

Troubleshooting

CMS Error: 314

AT+CMGS="+41796316771"+CMS ERROR: 314
CMS Error: 314 usualy means the device is busy and you have to try later again. Sometimes you can try as long as you want, you wont become able to send messages. If this is the case try to reset your GSM modem by using following command and try again afterwards, you may have solved the problem with that.

AT&F

CMS Error: 500

CMS ERROR: 500 is unfortunately a very generic error message. Try to send an SMS directly without storing it to the SIM.

AT+CMGS    ‘ Send an SMS directly without storing to the SIM
AT+CMGW   ‘ Writing an SMS to the SIM card and then send the SMS
AT+CMGR    ‘ By using the CMGR command you can verify if the SMS is written to SIM and it’s current status

Read your configured Service-Center number configured on your SIM card to send SMS messages (for example the number of Swisscom)AT+CSCA?
+CSCA: "+41794999000",145

If the number is not correctly configured then change it by usingAT+CSCA="+41794999000",145
OK

PIN codes by using AT commands

If you have a PIN code enabled SIM card and want to remove / disable the PIN code by using AT commands, then follow these commands. Suppose 9546 is the current PIN code, replace 9546 with your PIN code. Query the state of the SIM card by using the CPIN? command and remove the SIM code afterwards.

AT+CPIN?
+CPIN: SIM PIN ----> pin codes need to be entered
OK
AT+CPIN="9546"
OKAT+CLCK="SC",0,"9546" ----> disable pin code
OKAT+CPIN?
+CPIN: READY

Attached some examples about PIN and PUK management:

AT+CLCK="SC",1,"0000",1 ---->When you want to set pin code "0000"
OK
--Reboot module
AT+CPIN?
+CPIN: SIM PIN
OK
AT+CPIN="0000"
OK
AT+CPWD="SC","0000","1234" ---->When you want to change the pin code to "1234"
OK
--Reboot module
AT+CPIN?
+CPIN: SIM PIN
OK
AT*PSPRAS?
*PSPRAS: 3,10,255,255
OK
AT+CPIN="7777" ---->Input the wrong pin code will reduce the available try times
+CME ERROR: incorrect password
AT*PSPRAS?
*PSPRAS: 2,10,255,255
OK
AT+CPIN="1234"
OK
AT+CPIN?
+CPIN: SIM PUK
OK
AT+CPIN="44753796","1234" ---->When you want to input the PUK code after you input 3 times of the wrong pin.
OK

GSM connection state details

Check for Received Signal Strength & Quality

AT+CSQ
+CSQ: 13,1
Wait for the response in format: +CSQ: <rssi>, <ber>

<rssi>
Integer from 0 to 99 indicates the received signal strength. NOTE: Signal strength less than 6 indicates only 1 antenna bar, the quality of a connection will be poor and the connection may even drop.

<rssi> value Signal strength  Indication (for devices with a User Interface (MMI)) 
0 -113 dBm or less Signal is VERY low: at the extreme sensibility limit
1 -111 dBm MMI may indicate only 1 antenna bar
2 -109 dBm MMI may indicate only 1 antenna bar
3 -107 dBm MMI may indicate only 1 antenna bar
4 -105 dBm MMI may indicate only 1 antenna bar
5 -103 dBm MMI may indicate only 1 antenna bar
6 -101 dBm MMI may indicate 2 antenna bars
7 -99 dBm MMI may indicate 2 antenna bars
8 -97 dBm MMI may indicate 2 antenna bars
9 -95 dBm MMI may indicate 2 antenna bars
10 -93 dBm MMI may indicate 3 antenna bars
11 -91 dBm MMI may indicate 3 antenna bars
12 -89 dBm MMI may indicate 3 antenna bars
13 -87 dBm MMI may indicate 3 antenna bars
14 -85 dBm MMI may indicate 3 antenna bars
15 -83 dBm MMI may indicate 4 antenna bars
16 -81 dBm MMI may indicate 4 antenna bars
17 -79 dBm MMI may indicate 4 antenna bars
18 -77 dBm MMI may indicate 4 antenna bars
19 -75 dBm MMI may indicate 4 antenna bars
20 -73 dBm MMI may indicate 4 antenna bars
21 -71 dBm MMI may indicate 4 antenna bars
22 -69 dBm MMI may indicate 4 antenna bars
23 -67 dBm MMI may indicate 4 antenna bars
24 -65 dBm MMI may indicate 4 antenna bars
25 -63 dBm MMI may indicate 4 antenna bars
26 -61 dBm MMI may indicate 4 antenna bars
27 -59 dBm MMI may indicate 4 antenna bars
28 -57 dBm MMI may indicate 4 antenna bars
29 -55 dBm MMI may indicate 4 antenna bars
30 -53 dBm MMI may indicate 4 antenna bars
31 -51 dBm or more MMI may indicate 4 antenna bars
99 not detected MMI may indicate flashing antenna bars

<bet>
Integer from 0 to 7 and 99 reports the received signal quality measured on the radio traffic channel (error bit rate in percent)

Check if device is registered to the network

AT+CREG?
+CREG: 0,1

Wait for response in the format: +CREG: <mode>, <stat>

<mode>
0 GSM
2 UTRAN

<stat>
0 – not registered, ME is not currently searching a new operator to register to
1 – registered, home network
2 – not registered, but ME is currently searching a new operator to register to
3 – registration denied
4 – unknown
5 – registered, roaming

Overall overview

“battchg” – battery charge level – battery charge level indicator range 0..5
“signal”   – signal quality – signal quality indicator, range: 0 to 7, 99 – not measurable
“service” – service availability – service availability indicator, range: 0 – not registered to any network, 1 – registered

AT+CIND=?
+CIND: (("battchg",(0-5,99)),("signal",(0-7,99)),("service",(0,1)),("sounder",()

Reboot device

AT#REBOOT

Check device hardware

Manufacturer Identification
AT+GMI
Telit
Model Identification
AT+GMM
HE910-D
Revidion Identification
AT+GMR
12.00.024
Serial Identification
AT+GSN
00007406xx

GSM Equipment and Network Error Codes

When controlling GSM devices using AT commands, the device can respond with either “OK” or “ERROR”. Sometimes you will receive an error and you do not know the cause of this error. That’s why most advanced GSM devices support extended errors. Instead of just displaying the “ERROR” message, it also shows an error number. The syntax of this extended error is either “+CMS ERROR: xxx” or “+CME ERROR: xxx”. When the error starts with “+CME ERROR”, it means that the error is a device specific error code. For instance, you are trying to read a phonebook entry before entering a pincode. When there is a network error, for instance, when you try to send an SMS message when there is no network coverage, you will receive an error which starts with “+CMS ERROR”. To enable these extended commands, execute the following commands, or add them to your modems init string:

AT+CMEE=1 AT&W

Below you can find a list containing almost every error code supported by GSM devices.

CME ERROR’s (GSM Equipment related codes)
Error Description
CME ERROR: 0 Phone failure
CME ERROR: 1 No connection to phone
CME ERROR: 2 Phone adapter link reserved
CME ERROR: 3 Operation not allowed
CME ERROR: 4 Operation not supported
CME ERROR: 5 PH_SIM PIN required
CME ERROR: 6 PH_FSIM PIN required
CME ERROR: 7 PH_FSIM PUK required
CME ERROR: 10 SIM not inserted
CME ERROR: 11 SIM PIN required
CME ERROR: 12 SIM PUK required
CME ERROR: 13 SIM failure
CME ERROR: 14 SIM busy
CME ERROR: 15 SIM wrong
CME ERROR: 16 Incorrect password
CME ERROR: 17 SIM PIN2 required
CME ERROR: 18 SIM PUK2 required
CME ERROR: 20 Memory full
CME ERROR: 21 Invalid index
CME ERROR: 22 Not found
CME ERROR: 23 Memory failure
CME ERROR: 24 Text string too long
CME ERROR: 25 Invalid characters in text string
CME ERROR: 26 Dial string too long
CME ERROR: 27 Invalid characters in dial string
CME ERROR: 30 No network service
CME ERROR: 31 Network timeout
CME ERROR: 32 Network not allowed, emergency calls only
CME ERROR: 40 Network personalization PIN required
CME ERROR: 41 Network personalization PUK required
CME ERROR: 42 Network subset personalization PIN required
CME ERROR: 43 Network subset personalization PUK required
CME ERROR: 44 Service provider personalization PIN required
CME ERROR: 45 Service provider personalization PUK required
CME ERROR: 46 Corporate personalization PIN required
CME ERROR: 47 Corporate personalization PUK required
CME ERROR: 48 PH-SIM PUK required
CME ERROR: 100 Unknown error
CME ERROR: 103 Illegal MS
CME ERROR: 106 Illegal ME
CME ERROR: 107 GPRS services not allowed
CME ERROR: 111 PLMN not allowed
CME ERROR: 112 Location area not allowed
CME ERROR: 113 Roaming not allowed in this location area
CME ERROR: 126 Operation temporary not allowed
CME ERROR: 132 Service operation not supported
CME ERROR: 133 Requested service option not subscribed
CME ERROR: 134 Service option temporary out of order
CME ERROR: 148 Unspecified GPRS error
CME ERROR: 149 PDP authentication failure
CME ERROR: 150 Invalid mobile class
CME ERROR: 256 Operation temporarily not allowed
CME ERROR: 257 Call barred
CME ERROR: 258 Phone is busy
CME ERROR: 259 User abort
CME ERROR: 260 Invalid dial string
CME ERROR: 261 SS not executed
CME ERROR: 262 SIM Blocked
CME ERROR: 263 Invalid block
CME ERROR: 772 SIM powered down
CMS ERROR’s (GSM Network related codes)
Error Description
CMS ERROR: 1 Unassigned number
CMS ERROR: 8 Operator determined barring
CMS ERROR: 10 Call bared
CMS ERROR: 21 Short message transfer rejected
CMS ERROR: 27 Destination out of service
CMS ERROR: 28 Unindentified subscriber
CMS ERROR: 29 Facility rejected
CMS ERROR: 30 Unknown subscriber
CMS ERROR: 38 Network out of order
CMS ERROR: 41 Temporary failure
CMS ERROR: 42 Congestion
CMS ERROR: 47 Recources unavailable
CMS ERROR: 50 Requested facility not subscribed
CMS ERROR: 69 Requested facility not implemented
CMS ERROR: 81 Invalid short message transfer reference value
CMS ERROR: 95 Invalid message unspecified
CMS ERROR: 96 Invalid mandatory information
CMS ERROR: 97 Message type non existent or not implemented
CMS ERROR: 98 Message not compatible with short message protocol
CMS ERROR: 99 Information element non-existent or not implemente
CMS ERROR: 111 Protocol error, unspecified
CMS ERROR: 127 Internetworking , unspecified
CMS ERROR: 128 Telematic internetworking not supported
CMS ERROR: 129 Short message type 0 not supported
CMS ERROR: 130 Cannot replace short message
CMS ERROR: 143 Unspecified TP-PID error
CMS ERROR: 144 Data code scheme not supported
CMS ERROR: 145 Message class not supported
CMS ERROR: 159 Unspecified TP-DCS error
CMS ERROR: 160 Command cannot be actioned
CMS ERROR: 161 Command unsupported
CMS ERROR: 175 Unspecified TP-Command error
CMS ERROR: 176 TPDU not supported
CMS ERROR: 192 SC busy
CMS ERROR: 193 No SC subscription
CMS ERROR: 194 SC System failure
CMS ERROR: 195 Invalid SME address
CMS ERROR: 196 Destination SME barred
CMS ERROR: 197 SM Rejected-Duplicate SM
CMS ERROR: 198 TP-VPF not supported
CMS ERROR: 199 TP-VP not supported
CMS ERROR: 208 D0 SIM SMS Storage full
CMS ERROR: 209 No SMS Storage capability in SIM
CMS ERROR: 210 Error in MS
CMS ERROR: 211 Memory capacity exceeded
CMS ERROR: 212 Sim application toolkit busy
CMS ERROR: 213 SIM data download error
CMS ERROR: 255 Unspecified error cause
CMS ERROR: 300 ME Failure
CMS ERROR: 301 SMS service of ME reserved
CMS ERROR: 302 Operation not allowed
CMS ERROR: 303 Operation not supported
CMS ERROR: 304 Invalid PDU mode parameter
CMS ERROR: 305 Invalid Text mode parameter
CMS ERROR: 310 SIM not inserted
CMS ERROR: 311 SIM PIN required
CMS ERROR: 312 PH-SIM PIN required
CMS ERROR: 313 SIM failure
CMS ERROR: 314 SIM busy
CMS ERROR: 315 SIM wrong
CMS ERROR: 316 SIM PUK required
CMS ERROR: 317 SIM PIN2 required
CMS ERROR: 318 SIM PUK2 required
CMS ERROR: 320 Memory failure
CMS ERROR: 321 Invalid memory index
CMS ERROR: 322 Memory full
CMS ERROR: 330 SMSC address unknown
CMS ERROR: 331 No network service
CMS ERROR: 332 Network timeout
CMS ERROR: 340 No +CNMA expected
CMS ERROR: 500 Unknown error
CMS ERROR: 512 User abort
CMS ERROR: 513 Unable to store
CMS ERROR: 514 Invalid Status
CMS ERROR: 515 Device busy or Invalid Character in string
CMS ERROR: 516 Invalid length
CMS ERROR: 517 Invalid character in PDU
CMS ERROR: 518 Invalid parameter
CMS ERROR: 519 Invalid length or character
CMS ERROR: 520 Invalid character in text
CMS ERROR: 521 Timer expired
CMS ERROR: 522 Operation temporary not allowed
CMS ERROR: 532 SIM not ready
CMS ERROR: 534 Cell Broadcast error unknown
CMS ERROR: 535 Protocol stack busy
CMS ERROR: 538 Invalid parameter

Reference Guide

Download offline copy: Telit 3G HE910 3G/HSDPA/GSM Modem AT Command Reference R10

Источник
  • This topic has 5 replies, 3 voices, and was last updated 2 months, 3 weeks ago by rakesh.nagar@thegatewaydigital.com.

Viewing 6 posts — 1 through 6 (of 6 total)

  • Author

    Posts

  • December 21, 2016 at 11:29 am

    #16124

    Hello,

    I am facing the following problem. I cannot send SMS messages from Multitech Conduit Gateway. My approach description is bellow.

    1. Unlocked SIM card inserted.
    2. Cellular enabled using Conduit GUI (first problems occured)
    a) Even the SIM card is unlocked GUI reported warning that SIM card is locked.
    b) Based on a) I entered SIM card PIN and restard Conduit. GUI reported ERROR that SIM card is locked.
    c) Finally I decide to leave PIN box empty and restart Conduit again.
    3. All attempts to send SMS using proper NODE-RED node failed and therefore I decide to go to step 4.
    4. I connet to Conduit using putty through SSH and try to use sms utility. All commands (i.e. sms list all) failed with the following ERROR: [ERROR] atcmd.c:atcmd_expect_line:373: expected OK but got +CMS ERROR: 310!

    Could you please advice me how to get over these problems?

    Radim Malinowski

    December 21, 2016 at 2:09 pm

    #16128

    Hi Radim

    What is the serial number of your Conduit?
    +CMS ERROR 310 is an indication the SIM is not inserted. Can you please
    describe the SIM card orientation in the SIM card slot.
    http://www.multitech.net/developer/products/conduit/installing-conduit-sim-card/
    Try using the radio-query utility to issue AT Commands directly to the cellular radio. http://www.multitech.net/developer/software/mlinux/using-mlinux/utilities/radio-cmd-usage/

    Using the Radio-query utility issue the AT Commands below and post their response.
    at+cpin?
    at+cgreg?
    at+csq
    at+cmgf?
    at+cops=? (wait 30 seconds for response)

    -Best Regards

    December 23, 2016 at 3:48 am

    #16135

    Hi Steve,

    first of all thank you for such a quick reply.

    Serial number: 18814853

    I read SIM card installing guide before I insert SIM card into Conduit therefore orientation is correct. When SIM card wasn´t inserted properely an error message showed up in Conduit GUI. Now I don´t see any error message.

    Radio-query utility responses

    admin@mtcdt:~# radio-cmd at+cpin?
    ERROR
    admin@mtcdt:~# radio-cmd at+cgreg?
    +CGREG: 0,0

    OK
    admin@mtcdt:~# radio-cmd at+csq
    +CSQ: 24,1

    OK
    admin@mtcdt:~# radio-cmd at+cmgf?
    +CMS ERROR: 310
    admin@mtcdt:~# radio-cmd at+cops=? (no response – wait for 2 min)
    admin@mtcdt:~# radio-cmd at+cops=? (no response – wait for 2 min)

    Best regards
    Radim

    December 27, 2016 at 2:06 pm

    #16150

    Hi Radim

    The “ERROR” response to at+cpin? indicates that the SIM card is not detected
    by the cellular radio. This would be the same behavior if the SIM card is
    removed from the device altogether.

    +CGREG: 0,0 response indicates the cellular radio is not “registered” on the
    cellular network, and is not trying (indicative of the SIM not being detected).
    +CSQ:24,1 response indicates a detected receive signal strength of 24 out of 31
    If you are certain you have the correct size SIM properly oriented in the device, my only suggestion is to try another (2FF) SIM card and see if the cellular radio detects it.

    -Best Regards

    January 2, 2017 at 6:51 am

    #16185

    Hi Steve,

    thank you for your advices. Everything works now. I misunderstood term MiniSIM card and I used MicroSIM instead. Sorry for troubles.

    Have a nice day and whole new year.

    Best regards
    Radim

    November 17, 2022 at 8:43 am

    #33258

    Hello Steve,

    I am trying to connect the sim, to the network, using

    pppd call gsm connect, following this reference: https://www.multitech.net/developer/software/mlinux/using-mlinux/mlinux-cellular-connection/

    But, I see that, it is not able to connect to the network. By surfing over the internet, I reached to this page.

    I tried above commands, & I saw that,

    radio-cmd at+cpin

    is showing ERROR. That means, sim is not detected.

    So, I think, there is some issue with some detection. So, if you can help someway, it would be good.

    I am using Multitech conduit, with mLinux installed in it, version greater than 5.

    If you need any more details, please ask.

  • Author

    Posts

Viewing 6 posts — 1 through 6 (of 6 total)

  • You must be logged in to reply to this topic.
Источник

Send SMS using AT commands

Some advanced GSM modems like WaveCom and Multitech, support the SMS text mode.
This mode allows you to send SMS messages using AT commands, without the need to encode
the binairy PDU field of the SMS first. This is done by the GSM modem

Check if your GSM phone or modem supports SMS text mode

To check if your modem supports this text mode, you can try the following command:

AT+CMGF=1 <ENTER>

If the modem reponds with “OK” this mode is supported.
Please note that using this mode it is onluy possible to send simple text messages. It is not possible
to send multipart, Unicode, data and other types of messages.

Setting up the modem

If the modem contains a SIM card with is secured with a PIN code, we have to enter this pin code first:

AT+CPIN=”0000″ <ENTER> (replace 0000 with your PIN code).

Please not that in most cases you have only 3 attemps to set the correct PIN code.
After setting the PIN code, wait some seconds before issueing the next command to give the modem some time
to register with the GSM network.

In order to send a SMS, the modem has to be put in SMS text mode first using the following command:

AT+CMGF=1 <ENTER>

In text mode there are some additional parameters that can be set.
Using the following command we can read the current values:

AT+CSMP? <ENTER>

The modem will reponse with a string like this:

+CSMP: 1,169,0,0

OK

The first value is a combination of some option bits:

bit 7 RP Reply path, not used in text mode
bit 6 UDHI User Data Header Information
bit 5 SRR Set this bit to request a delivery report
bit 3,4 VPF Validity Period, set b4=1 if a VP value is present
bit 2 RD Reject Duplicates, do not return a message ID when a message with the same destination and ID is still pending
bit 0,1 MTI Message Type Indicator
b1=0 & b0=0 -> SMS-DELIVER
b1=0 & b0=1 -> SMS-SUBMIT

Bit 0 of the message is always set when sending messages (SMS-SUBMIT). So the first value should be 1 or higher.
The second parameter sets the Validity Period of the message. This value is encoded as follows:

0 – 143 (VP + 1) x 5 minutes
144 – 167 12 Hours + ((VP-143) x 30 minutes)
168 – 196 (VP-166) x 1 day
197 – 255 (VP-192) x 1 week

The third parameter contains the PID (Protocol Identifier). This parameter is only used for advanced messaging.
The fourth parameter contains the DCS (Data Coding Scheme). This parameter is used to select the characterset/messagetype.
When setting the DCS parameter to ‘0’ standard 7 bit text is send. When setting this parameter to ’16’ the message is sent as a flash message.

To send a message with a validity period of 1 day, the parameters have to be set like this:

Bit 0 and 4 of the first field has to be set, so the first value will become 1 + 16 = 17.

Send the following command to the modem to set this parameters:

AT+CSMP=17,167,0,16 <ENTER>

If the modem responds with “OK” ,the modem is ready to send (flash) text messages with a validity period of 1 day.

Sending the message

To send the SMS message, type the following command:

AT+CMGS=”+31638740161″ <ENTER>

Replace the above phone number with your own cell phone number. The modem will respond with:

>

You can now type the message text and send the message using the <CTRL>-<Z> key combination:

Hello World ! <CTRL-Z>

After some seconds the modem will respond with the message ID of the message, indicating that the message was sent correctly:

+CMGS: 62

The message will arrive on the mobile phone shortly.

Sending an Unicode SMS message

Some modems also have the capability to send Unicode or UCS2 messages without encoding a PDU.
You can send Unicode messages by only converting the Unicode data to a HEX string and send this string to the modem.

To check whether your modem supports this mode, just type the following command:

AT+CSCS=?

This commands displays the codepages supported by the modem. The modem will respond like this:

+CSCS: (“GSM”,”PCCP437″,”CUSTOM”,”HEX”)

If this string contains “HEX” or “UCS2”, Unicode seems to be supported.
To specify that you will use an HEX string to send the message, set the codepage to “HEX” or “UCS2” depending on the modem response.
In our example we will set the modem to “HEX” :

AT+CSCS=”HEX” <ENTER>

Next, we have to specify the correct DCS (Data Coding Scheme) for Unicode messages, which is 0x08.
We can set this value by changing the fourth parameter of the AT+CSMP command to ‘8’:

AT+CSMP=1,167,0,8 <ENTER>

The modem is now ready to send messages as Unicode. Now is the time to send the actual message:

AT+CMGS=”+31638740161″ <ENTER>

Replace the above phone number with your own cell phone number. The modem will respond with:

>

The only thing you have to program by yourself, is a simple routine which converts the Unicode string to an hexidecimal string like this:

مرحبا

Which is ‘Hello’ in arabic will be converted like this:

“06450631062D06280627”

You can send this hexidecimal string to the modem:

06450631062D06280627 <CTRL-Z>

After some seconds the modem will respond with the message ID of the message, indicating that the message was sent correctly:

+CMGS: 63

The message will arrive on the mobile phone shortly.

Источник

Понравилась статья? Поделить с друзьями:
  • Cms client ошибка пароля как исправить
  • Cms 314 error
  • Cmos ошибка при загрузке windows
  • Cmos settings wrong как исправить
  • Cmos reset ошибка 502