On Tue, Oct 11, 2005 at 02:36:56PM +0200, Lars-Hendrik Schneider wrote: > 2005-10-10 15:12:54 [8244] [6] DEBUG: AT2[2]: <-- +CPMS: "SM",0,20,"SM",0,20 > 2005-10-10 15:12:54 [8244] [6] DEBUG: AT2[2]: <-- OK > 2005-10-10 15:13:56 [8244] [6] DEBUG: AT2[2]: --> AT+CPMS?^M > 2005-10-10 15:13:56 [8244] [6] DEBUG: AT2[2]: <-- +CPMS: "SM",0,20,"SM",0,20 > 2005-10-10 15:13:56 [8244] [6] DEBUG: AT2[2]: <-- OK > 2005-10-10 15:14:12 [8244] [6] DEBUG: AT2[2]: <-- +CMT: ,33 > 2005-10-10 15:14:12 [8244] [6] DEBUG: AT2[2]: <-- > 0791947106004034040C9194613203967900005001015141008010525098CD7685C5AE33FBBD3EBBD6 > 2005-10-10 15:14:12 [8244] [6] DEBUG: AT2[2]: Numeric sender (international) > <+49162123456> > 2005-10-10 15:14:12 [8244] [6] DEBUG: AT2[2]: User data length read as (16) > 2005-10-10 15:14:12 [8244] [6] DEBUG: AT2[2]: Udh decoding done len=16 udhi=0 > udhlen=0 udh='' > 2005-10-10 15:14:12 [8244] [6] DEBUG: AT2[2]: --> AT+CNMA^M > Some wavecoms seem to handle cnma not in an apropriate way, if there isn't some more vodoo magic. i get an "ERROR" back in that case from some of them. I didn't have the time to look into this closer yet. I think the new driver behaves a bit different... The first solution is not to enable direct routing to the te by initializing the modem by at+cnmi....
Wilfried Goesgens
