What's new in gsm-ussd 0.4.0-25
Jun 5, 2011
- A big internal redesign as a base for further development.
- Two more Huawei modems identified as needing PDU encoding.
New in gsm-ussd 0.3.3 (Jun 9, 2010)
New in gsm-ussd 0.3.2 (Jun 1, 2010)
- Two distinct changes went into gsm-ussd..
- First: After entering the PIN, the modem first has to register in its net. gsm-ussd waits for that and only proceeds if the modem reports a successful registration, but some modems are a bit too optimistic. They might be freshly registered, but USSD queries still time out. Now, gsm-ussd waits for another turn if the modem just registered to give it time so settle, so that USSD queries can succeed.
- Second: If several programs are using one and the same serial interface, the data coming from the modem get corrupted. After all, a serial interface is a point-to-point connection; having more than the modem and one program on the interface has to break. In Linux, access to serial interface is regulated by lock files saved in /var/lock. Sadly, up to now gsm-ussd did not adhere to this convention, so if there was still a picocom running (for debugging purposes), both stepped over each other, ruining everything in the progress. This bug is done now, gsm-ussd will create lock files or quit if one already exists.
New in gsm-ussd 0.3.0 (May 25, 2010)
- gsm-ussd now supports USSD sessions. Normally, USSD queries are one-shot commands: You ask for some info like your prepaid account balance, receive an answer and you're done. But sometimes, the answer requests more information from you and displays a simple menu or some text with instructions which data to enter.
- Now you can a further calls to gsm-ussd to
- a) enter the requested data or choose menu entries until you're done
- b) cancel the session.