| Receiving Escape 1B Problem |  Search
|
|
NowSMS Support Forums ⬆ MMS & SMS Technical Discussions (unsupported) ⬆ Archive through November 21, 2009 ⬆ |
◄ ► |
| Author | Message | |||
| Juan Moreno New member Username: Jamg Post Number: 1 Registered: 11-2009 |
Hi, I am developing an App where the SMS is sent in HEX mode. The problem comes, when an 0x1B or escape is sent, as some SIMs receive it and transform it automatically to an 0x20 or space. How can I make the ME to stop the transform? I've read in 3GPP TS 23.038, that a receiving entity which does not understand the meaning of this escape mechanism shall display it as a space character. How can I make it to understand the single shift mechanism? I dont mind about the characters in the tables, but about the unchanged hexa values. Any way to solve this?? Thanks a lot!!  | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1448 Registered: 08-2008 |
Hi Juan, Unless you're doing something wrong in your encoding ... there's nothing that you can do to make a device understand something that it doesn't understand (short of updating the firmware in the device). It does seem unusual that a device would not understand these extended characters. Are you sure the problem is with the devices? I've seen some operator networks where these characters can't be sent correctly phone-to-phone. -- Des NowSMS Support | |||
| Juan Moreno New member Username: Jamg Post Number: 2 Registered: 11-2009 |
Well, i've done some test... I have 3 different MEs: 3 Phones (1P,2P,3P), the GSM Modem; and also 3 SIMs of the same operator. Sending the same message... Sending from: Mdm w SIM2, Receiving: Mdm SIM2, Result: OK Sending from: Mdm w SIM1, Receiving: Mdm SIM1, Result: OK Sending from: 1P SIM1, Receiving: Mdm SIM2, Result: Error; Seems 1P fault Sending from: Mdm SIM1, Receiving: 2P SIM2, Result: Error; SIM1 sending fault? Sending from: Mdm SIM1, Receiving: 3P SIM3, Result: OK; SIM2 Rx fault? By the way Sending from: Mdm SIM2, Receiving: 1P SIM1, Result: OK; Sending from: 2P SIM2, Receiving: Mdm SIM1, Result: OK; Could it be an SIM2 config issue? AT+COPS=0 AT+CMGF=1 AT+CSMP=17,169,0,0 AT+CNMI=1,1,0,0,0 AT+CSCS= “HEX” AT+CSAS AT&W Regadrs | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7870 Registered: 10-2002 |
Hmm ... That is odd. You should do more combination tests to confirm that the problem is with SIM2. If the problem is with SIM2, I can't imagine what it would be. Is it possible that the default SMSC address is different on SIM2? (Some operators provision different SMSC addresses to spread the load.) -bn | |||
| Juan Moreno New member Username: Jamg Post Number: 3 Registered: 11-2009 |
Thanks for the support guys!! Both SIMs are on the same SMSC address.. The last test shows that also SIM2 in 1P receives fine, but it corrupts the data in 2P and Mdm. I'm running out of ideas. The only thing I can think of is that this SIM2 is not default configured to handle alphabet extensions and that some MEs help it overriding this mechanism to decode fine. How can I see which alphabets is a SIM supporting?? | |||
