Re: gnokii sendsms problem with special characters after ubuntu upgrade
Pablo Reyes <[email protected]> Tue, 24 Nov 2015 12:23:42 -0300
| Newsgroups | gmane.linux.drivers.gnokii |
|---|---|
| Message-ID | <CABT=2kJKLHoT-hZpOQ+zYq_=yDBD9HtAPXjmjFZMtJ+ztSZbyA@mail.gmail.com> |
any ideas? :( Regards... Pablo Reyes Blog: www.pabloreyes.com.ar On Fri, Oct 23, 2015 at 9:41 AM, Pablo Reyes <[email protected]> wrote: > Hi! > > My model is USB. This is the debug output: > > GNOKII Version 0.6.30 >> LOG: debug mask is 0x1 >> Config read from file gnokiirc-ttyUSB. >> phone instance config: >> model = AT >> port = /dev/ttyUSB60 >> connection = serial >> initlength = default >> serial_baudrate = 19200 >> serial_write_usleep = -1 >> handshake = software >> require_dcd = 0 >> smsc_timeout = 20 >> rfcomm_channel = 0 >> sm_retry = 0 >> Initializing AT capable mobile phone ... >> Serial device: opening device /dev/ttyUSB60 >> Serial device: setting RTS to high and DTR to high >> Message sent: 0x00 / 0x0004 >> 41 54 5a 0d | ATZ >> write: [ATZ<cr>] >> read : [ATZ<cr><cr><lf>OK<cr><lf>] >> Message received: 0x00 / 0x000a >> 02 41 54 5a 0d 0d 0a 4f 4b 0d | ATZ OK >> Received message type 00 >> Message sent: 0x00 / 0x0005 >> 41 54 45 31 0d | ATE1 >> write: [ATE1<cr>] >> read : [OK<cr><lf>] >> Message received: 0x00 / 0x0004 >> 02 4f 4b 0d | OK >> Received message type 00 >> Message sent: 0x00 / 0x000a >> 41 54 2b 43 4d 45 45 3d 31 0d | AT+CMEE=1 >> write: [AT+CMEE=1<cr>] >> read : [OK<cr><lf>] >> Message received: 0x00 / 0x0004 >> 02 4f 4b 0d | OK >> Received message type 00 >> Message sent: 0x06 / 0x0007 >> 41 54 2b 47 4d 4d 0d | AT+GMM >> write: [AT+GMM<cr>] >> read : [E303<cr><lf><cr><lf>OK<cr><lf>] >> Message received: 0x06 / 0x000c >> 02 45 33 30 33 0d 0a 0d 0a 4f 4b 0d | E303 OK >> Received message type 06 >> Message sent: 0x06 / 0x0008 >> 41 54 2b 43 47 4d 49 0d | AT+CGMI >> write: [AT+CGMI<cr>] >> read : [OK<cr><lf>] >> Message received: 0x06 / 0x0004 >> 02 4f 4b 0d | OK >> Received message type 06 >> Message sent: 0x63 / 0x0009 >> 41 54 2b 43 53 43 53 3f 0d | AT+CSCS? >> write: [AT+CSCS?<cr>] >> read : [AT+CMEE=1<cr><cr><lf>OK<cr><lf>] >> Message received: 0x63 / 0x0010 >> 02 41 54 2b 43 4d 45 45 3d 31 0d 0d 0a 4f 4b 0d | AT+CMEE=1 OK >> Received message type 63 >> Initialisation completed >> Message sent: 0x63 / 0x000a >> 41 54 2b 43 53 43 53 3d 3f 0d | AT+CSCS=? >> write: [AT+CSCS=?<cr>] >> read : [AT+GMM<cr><cr><lf>E303<cr><lf><cr><lf>OK<cr><lf>] >> Message received: 0x63 / 0x0015 >> 02 41 54 2b 47 4d 4d 0d 0d 0a 45 33 30 33 0d 0a | AT+GMM E303 >> 0d 0a 4f 4b 0d | OK >> Received message type 63 >> Message sent: 0x23 / 0x0009 >> 41 54 2b 43 53 43 41 3f 0d | AT+CSCA? >> write: [AT+CSCA?<cr>] >> read : [+CSCA: "+54079000890",145<cr><lf><cr><lf>OK<cr><lf>] >> Message received: 0x23 / 0x0021 >> 02 2b 43 53 43 41 3a 20 22 2b 35 34 30 37 39 30 | +CSCA: "+540790 >> 30 30 38 39 30 22 2c 31 34 35 0d 0a 0d 0a 4f 4b | 00890",145 OK >> 0d | >> Received message type 23 >> Cannot read the SMSC number from your phone. If the sms send will fail, >> please use --smsc option explicitely giving the number. >> =====> ENTER gn_sms_send() >> General Data Coding >> Default Alphabet >> encoded size: 4 >> rawsms length: 4 >> rawsms user data length: 4 >> dcs: 0x00 >> Length: 0x04 >> user_data_length: 0x04 >> ValidityIndicator: 2 >> user_data: FD77FF0D >> Input is 6 characters long >> SMS is 4 octets long >> Number of extended alphabet chars: 0 >> Sending >> Message sent: 0x65 / 0x000a >> 41 54 2b 43 4d 47 46 3d 30 0d | AT+CMGF=0 >> write: [AT+CMGF=0<cr>] >> read : [AT+CMGF=0<cr><cr><lf>OK<cr><lf>] >> Message received: 0x65 / 0x0010 >> 02 41 54 2b 43 4d 47 46 3d 30 0d 0d 0a 4f 4b 0d | AT+CMGF=0 OK >> Received message type 65 >> PDU mode set >> Sending initial sequence >> Message sent: 0x66 / 0x000b >> 41 54 2b 43 4d 47 53 3d 31 37 0d | AT+CMGS=17 >> write: [AT+CMGS=17<cr>] >> read : [AT+CMGS=17<cr><cr><lf>> ] >> Message received: 0x66 / 0x000f >> 01 41 54 2b 43 4d 47 53 3d 31 37 0d 0d 0a 3e | AT+CMGS=17 > >> Received message type 66 >> Got response: No error. >> Sending frame: 0011000A8162403566000000AA04FD77FF0D >> Message sent: 0x21 / 0x0025 >> 30 30 31 31 30 30 30 41 38 31 36 32 34 30 33 35 | 0011000A81624035 >> 36 36 30 30 30 30 30 30 41 41 30 34 46 44 37 37 | 66000000AA04FD77 >> 46 46 30 44 1a | FF0D >> write: [0011000A8162403566000000AA04FD77FF0D^Z] >> read : [+CMGS: 143<cr><lf><cr><lf>OK<cr><lf>] >> Message received: 0x21 / 0x0012 >> 02 2b 43 4d 47 53 3a 20 31 34 33 0d 0a 0d 0a 4f | +CMGS: 143 O >> 4b 0d | K >> Received message type 21 >> Send succeeded with reference -1! >> Serial device: closing device > > > My command > echo "ñoño" | gnokii --config gnokiirc-ttyUSB --sendsms 260453xxxx > > My cellphone receive > ")o )o" > > Thanks a lot in advance. Regards... > > > Pablo Reyes > Blog: www.pabloreyes.com.ar > > On Tue, Oct 20, 2015 at 7:37 PM, Daniele Forsi <[email protected]> wrote: > >> Pablo Reyes wrote: >> >> > When migrate to Ubuntu 12 and gnokii v 0.6.30, special characters don't >> > work. >> >> the ñ is part of the Default GSM Alphabet so it must work with every >> device but we need to see the debug output to understand what is going >> wrong; it is enabled in your config with this: >> [logging] >> debug = on >> >> with model=AT it is easy to extract the PDU and then use the fake >> driver to decode it, see "Advanced usage " in >> http://wiki.gnokii.org/index.php/Fake_driver >> -- >> Daniele Forsi >> >> _______________________________________________ >> gnokii-users mailing list >> [email protected] >> https://lists.nongnu.org/mailman/listinfo/gnokii-users >> > > _______________________________________________ gnokii-users mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/gnokii-users