Yuan LIU wrote: >>P[ 2] --> None >> -- SMS[-1] RX 93 00 6D >> -- SMS[0] TX 10 98 96 00 10 01 00 00 11 06 00 00 00 00 00 00 00 >> 12 >>03 00 02 00 04 13 65 00 53 65 63 75 72 69 74 79 20 72 65 73 65 61 72 >>63 68 65 72 73 20 68 61 76 65 20 74 72 61 63 65 64 20 73 70 61 6D 2D >>73 65 6E 64 69 6E 67 20 62 6F 74 6E 65 74 20 63 6C 69 65 6E 74 73 20 >>62 61 63 6B 20 74 6F 20 6E 65 74 77 6F 72 6B 73 20 72 75 6E 20 62 79 >>20 74 68 65 20 55 53 20 6D 69 6C 69 74 61 72 79 2E 17 01 00 01 18 0A >>00 30 34 33 34 34 33 39 30 30 30 1B 01 00 01 1C 03 00 00 00 00 E8 >>P[ 2] I IND :DISCONNECT oad:0434439000 dad:0622100000 pid:19 >>state:CONNECTED [snip] > > The operator seems to hang up on you.
Yeah, that's the way I read it too. > Good thing is, the operator is at least responding to your call and > sending you that initial answer. Yep, with the other two SMSC numbers I had, I didn't even get that far. This one (0622100000) seems to support ETSI ES 201 912, at least. > This may sound bizarre but try the s option and operate in mttx mode. > I vaguely remember seeing a comment about one operator does some role > reversal. (May not be due to protocol 2.) OK, I'll try that. > If you have an extra channel to spare with (seems you do), can also > try to set up a context to receive SMS so you know all your > commands/dial plan are working before testing against operator. Yep, good idea. Thanks for your help, Yuan Liu. /Per Jessen, Zürich _______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
