Release of 255
12 November, 2010 - 14:32
Fix SEGV when xAP messages have > 50 key/value pairs. Limit increased to 150, when limit is reach it will reset to index 0 and start overwritting the header (with a debug notice if this happens). 80 keys is about 1300 bytes so you'd be pushed to get to 150 within 1500 bytes anyway.
13 November, 2010 - 11:24
#2
SMS issue
Brett,
Just noticed my sms has stopped working. When I try to start debug, I get this:
# xap-sms -d 5
SMS Connector for xAP v12
Copyright (C) DBzoo, 2009-2010
[crt][init.c:111:discoverBroadcastNetwork] errno 126 (Cannot assign requested address)
[crt][init.c:111:discoverBroadcastNetwork] Unable to query capabilities of interface eth0
Just letting you know. I'm going to go through the process of resetting phone etc.
I have a problem on my phone in that the "wipe all msgs in inbox" option doesn't seem to work.
I have to manully delete each message to clear the phone down, are messages handled by hah supposed to be deleted from the phone's buffer in the proicess?
13 November, 2010 - 12:25
#3
Command Syntax
The command syntax is wrong, you need to specify the port ie :-
xap-sms -d 5 -s /dev/ttyUSB1 -i br0
The spaces are also significant. So in this example debug level is 5, my serial cable is connected to USB port 1, the interface port is br0, it a zero and not an oh. This can be configured through the web interface, so I'd check your setting there first incase the upgrade has altered something.
If your not sure which USB port to use, disconnect the cable, get a telnet session going, reconnect the cable and run dmesg, you should then see the USB port that is used.
Hope this helps.
Karl
13 November, 2010 - 15:03
#5
SMS Class
Deleted post.
13 November, 2010 - 15:08
#6
Boy cried wolf
Apologies, it was my phone playing up, mem had filled up and for some reason had turned itself off.
Brett, have you slept?