Firmware Release Notes AirPrime Q26Elite 4111924 006 January 16, 2012
Firmware Release Note Introduction Important Notice Due to the nature of wireless communications, transmission and reception of data can never be guaranteed. Data may be delayed, corrupted (i.e., have errors) or be totally lost. Although significant delays or losses of data are rare when wireless devices such as the Sierra Wireless modem are used in a normal manner with a well-constructed network, the Sierra Wireless modem should not be used in situations where failure to transmit or receive data could result in damage of any kind to the user or any other party, including but not limited to personal injury, death, or loss of property. Sierra Wireless accepts no responsibility for damages of any kind resulting from delays or errors in data transmitted or received using the Sierra Wireless modem, or for failure of the Sierra Wireless modem to transmit or receive such data. Safety and Hazards Do not operate the Sierra Wireless modem in areas where blasting is in progress, where explosive atmospheres may be present, near medical equipment, near life support equipment, or any equipment which may be susceptible to any form of radio interference. In such areas, the Sierra Wireless modem MUST BE POWERED OFF. The Sierra Wireless modem can transmit signals that could interfere with this equipment. Do not operate the Sierra Wireless modem in any aircraft, whether the aircraft is on the ground or in flight. In aircraft, the Sierra Wireless modem MUST BE POWERED OFF. When operating, the Sierra Wireless modem can transmit signals that could interfere with various onboard systems. Note: Some airlines may permit the use of cellular phones while the aircraft is on the ground and the door is open. Sierra Wireless modems may be used at this time. The driver or operator of any vehicle should not operate the Sierra Wireless modem while in control of a vehicle. Doing some states and provinces, operating such communications devices while in control of a vehicle is an offence. Limitations of Liability implied, including any implied warranties of merchantability, fitness for a particular purpose, or noninfringement. The recipient of the manual shall endorse all risks arising from its use. The information in this manual is subject to change without notice and does not represent a commitment on the part of Sierra Wireless. SIERRA WIRELESS AND ITS AFFILIATES SPECIFICALLY DISCLAIM LIABILITY FOR ANY AND ALL DIRECT, INDIRECT, SPECIAL, GENERAL, INCIDENTAL, CONSEQUENTIAL, PUNITIVE OR EXEMPLARY DAMAGES INCLUDING, BUT NOT LIMITED TO, LOSS OF PROFITS OR REVENUE OR ANTICIPATED PROFITS OR REVENUE ARISING OUT OF THE USE OR INABILITY TO USE ANY SIERRA WIRELESS PRODUCT, EVEN IF SIERRA WIRELESS AND/OR ITS AFFILIATES HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES OR THEY ARE FORESEEABLE OR FOR CLAIMS BY ANY THIRD PARTY. Notwithstanding the foregoing, in no event shall Sierra Wireless and/or its affiliates aggregate liability arising under or in connection with the Sierra Wireless product, regardless of the number of events, occurrences, or claims giving rise to liability, be in excess of the price paid by the purchaser for the Sierra Wireless product. 4111924 Rev006 January 16, 2012 2
Firmware Release Note Introduction Patents This product may contain technology developed by or for Sierra Wireless Inc. This product includes technology licensed from QUALCOMM. This product is manufactured or sold by Sierra Wireless Inc. or its affiliates under one or more patents licensed from InterDigital Group. Copyright 2012 Sierra Wireless. All rights reserved. Trademarks AirCard is a registered trademark of Sierra Wireless. Sierra Wireless, AirPrime, AirLink, AirVantage, Watcher and the Sierra Wireless logo are trademarks of Sierra Wireless.,,, insim, WAVECOM, WISMO, Wireless Microprocessor, Wireless CPU, Open AT are filed or registered trademarks of Sierra Wireless S.A. in France and/or in other countries. Windows and Windows Vista are registered trademarks of Microsoft Corporation. Macintosh and Mac OS are registered trademarks of Apple Inc., registered in the U.S. and other countries. QUALCOMM is a registered trademark of QUALCOMM Incorporated. Used under license. Other trademarks are the property of the respective owners. Contact Information Sales Desk: Post: Phone: 1-604-232-1488 Hours: E-mail: Sierra Wireless 13811 Wireless Way Richmond, BC Canada V6V 3A4 Fax: 1-604-231-1109 Web: www.sierrawireless.com 8:00 AM to 5:00 PM Pacific Time sales@sierrawireless.com Consult our website for up-to-date product descriptions, documentation, application notes, firmware upgrades, troubleshooting tips, and press releases: www.sierrawireless.com 4111924 Rev006 January 16, 2012 3
Firmware Release Note Introduction Document History Version Date Updates 001 April 30, 2010 Creation 002 May 7, 2010 Modified slightly as R2B-to-R5A CRN for earlier release customers. 003 October 13, 2010 Updated for version R5C. 004 December 21,2010 Updated to include comprehensive change list from R2B 005 September 23, 2011 Updated for version 006 January 16, 2012 Corrected the version fix information for the following Issue Change IDs, changing their Version Fix information from R5A to R4C: ANO55808 ANO55495 NEW55494 ANO56457 4111924 Rev006 January 16, 2012 4
Contents 1. INTRODUCTION... 6 1.1. Related References... 6 2. CHANGES INCLUDED IN FIRMWARE... 7 2.1. Change List... 7 3. RESTRICTIONS AND KNOWN ISSUES... 13 3.1. Known Issues... 13 4111924 Rev006 January 16, 2012 5
1. Introduction This document lists the modifications of the AirPrime Q26Elite firmware version R6C as related to the initial R2B release. Note: To verify the latest firmware version is present, use the AT+CGMR command to confirm that the response received is S/W VER: Q26EL001 Sep 13 2011 19:13:07. 1.1. Related References AirPrime Q26Elite Software User Guide and AT Commands Interface Specification Reference: 4111924 AirPrime Q26Elite Product Technical Specification and Customer Design Guidelines Reference: 4111804 4111924 Rev006 January 16, 2012 6
2. Changes Included in Firmware This section defines the changes introduced since the initial R2B release. 2.1. Change List Description of Issue or New Feature Implementation Details Change ID Fix in Version Carrier Specific Sprint MIP error codes Sprint MTU requirement Sprint user roam preference requirement Module reset issue in few APAC RUIMS Sprint OMADM 1.6.7 requirement SIP LCP termination request during power down OTASP call doesn't originate after E911 call Verizon March Req - Device shall avoid a Home system for 15 minutes after multiple Maximum Access Probe exits during better service reselection while on Roam system Missing WERI responses Qualcomm QSC6055 AMSS patch 4.3.90 Enable ability to send AT Commands over USB Implemented new MIP error codes Fix to set the default MTU to 1472 Fix to remove the Affiliated roaming option for +WRMP command. Fix to ensure +SPEAKER setting doesn t cause resets. Implemented Sprint OMADM 1.6.7 requirement Module sends LCP termination request during power down if in a SIP call Fixed issue with OTASP call after E911 call Increase the timer value from 10 min to 15 min for Verizon Fix to ensure the module is sending +WERI response when module comes back to same ROAM network from a HOME network. Integrated Qualcomm QSC6055 AMSS patch 4.3.90 Implemented AT Command parser, unsolicited message handling, and CMUX support over USB AT Command port ANO61698 Sprint DEV61684 Sprint DEV61716 Sprint CUS61138 N/A DEV61495 Sprint ANO61606 Verizon ANO61351 Verizon DEV61277 Verizon ANO60964 ANO61337 ANO60943 DEV61215 DEV57402 DEV59452 ANO60727 ANO60313 ANO61137 ANO60753 N/A N/A N/A 4111924 Rev006 January 16, 2012 7
Firmware Release Note Changes Included in Firmware Description of Issue or New Feature Implementation Details Change ID Fix in Version Carrier Specific ATS0 (auto answer) and AT$QCVAD (expected incoming call type) settings are not stored over power cycle Unable to query +CMUX values during a CMUX session When in an emergency call, if the SPC attempts exceeds the maximum limit the emergency call will be terminated and the module will go offline +CDS unsolicited indications do not display correct year for 2010 and later When the AT+WWAKESET bit mask value 0064 is set, the ring indicator pin remains asserted after module power up and is never deasserted Duplicate SMS message is sometimes sent to network and +CDS reports 107 failure when the SMS was actually sent successfully. After Voice-mail notification is received, listing all SMSs with AT+CMGL fails Sometimes the +CRING unsolicited response is output instead of the RING unsolicited response even though AT+CRC=0 NMEA frames are not reported when there is no GPS fix ATS0 and AT$QCVAD settings are now saved with AT&W and restored at power-up and via ATZ command Enabled the AT+CMUX? query while on a CMUX session Modified call processing functionality to not terminate an emergency call when maximum SPC attempts are reached Fixed display of year field in +CDS unsolicited indications Ensured ring indicator pin is de-asserted after AT+WRID duration timer expires during ring indicator power up notification Fixed issue with SMS retry wait timer not conforming to MO retry interval period in order to ensure duplicate messages are not sent prematurely Removed storing of voice-mail notification in SMS inbox Fixed check of +CRC value and +WUSLMSK mask. On an incoming call, RING will be output when AT+CRC=0 and +WUSLMSK bit 29 is enabled while +CRING will be output when AT+CRC=1 and +WUSLMSK bit 5 is enabled. Added new optional parameter to AT+WGPSTRACK command to indicate if NMEA frames should be output only when final position is reported (default) or at a continuous 1 Hz rate NEW61102 N/A ANO61015 N/A ANO60726 N/A ANO60905 N/A ANO58651 N/A ANO54412 CUS60134 ANO55223 N/A ANO58514 N/A ANO52816 N/A CUS59741 N/A 4111924 Rev006 January 16, 2012 8
Firmware Release Note Changes Included in Firmware Description of Issue or New Feature Implementation Details Change ID Fix in Version Carrier Specific Add AT command to allow customer to configure the GPS lock setting Add AT command to allow customer to configure the GPS privacy level AT+DPRL fails over CMUX Querying AT+CMUX? when no CMUX session is in progress returns last used values instead of default values After originating a data call by entering ATD#777 on CMUX DLC1, entering subsequent AT commands before the data call is connected will abort the data call and NO CARRIER will be returned on DLC2. If the PPP bearer is not active, AT+WIPBR=3,6,15 returns an IP address as 0.0.0.0 active instead of an ERROR code After the IP stack has been started via AT+WIPCFG=1, an ERROR should be returned if AT+WIPCFG=1 is issued again without first stopping the stack. Escaping from socket online data mode to online command mode by entering "+++" intermittently fails Audio PCM format is currently 8-bit ulaw while Product Technical Specification states it should be 13- bit linear Implemented AT command AT+WPPRV to configure the GPS lock setting. Implemented AT command AT+WPPRV to configure the GPS privacy level. Three levels are supported: 0 (low), 1 (medium) and 2 (high) Fixed issue with flushing SIO data over CMUX that resulted in a few bytes of PRL not being written successfully Updated AT+CMUX command to restore default parameter values when CMUX session is closed Fixed CMUX AT Command processing to ensure that subsequent AT Commands entered on DLC1 will not cause the originating data call to be aborted Updated AT+WIPBR=3,6,15 command to return an ERROR if the PPP bearer is not active Updated AT+WIPCFG to return ERROR if AT+WIPCFG=1 is issued when IP stack is already running Fixed corner case with escaping to online command mode Changed Audio PCM format to 13-bit linear NEW52883 ANO49275 ANO61155 NEW52883 ANO49275 ANO61155 N/A N/A CUS58610 N/A ANO52685 N/A DEV60348 DEV50570 N/A ANO53079 N/A ANO52871 N/A CUS58780 N/A ANO59134 N/A 4111924 Rev006 January 16, 2012 9
Firmware Release Note Changes Included in Firmware Description of Issue or New Feature Implementation Details Change ID Fix in Version Carrier Specific ATI3 and AT+CGMR return the incorrect product type for R-UIM variants AT+WPRL returns the PRL version in NV instead of the PRL version on the R-UIM card When MDN is changed, module should not autopopulate tethered NAI and PPP user id When a Network Initiated OMA/DM or FUMO request is received when module is on a active data call, the module fails to initial the OMA/DM session after the data call is terminated Module fails to fall back to roaming system after exhaustion of access probes Add AT command to reset IMSI to factory default in order to allow OMA/DM session when new MDN is assigned to a previously provisioned device Data out of sequence after escaping to Online Command mode when sending over 3000 bytes a. No user option to enter username/password for SIP data call b. SIP Dial-up connection fails in relay mode NAI update occurs only on active MIP profile during MDN change, instead of all enabled MIP profiles Fixed ATI3 and AT+CGMR command responses to return the product type of Q26EL002 for R-UIM variants Updated AT+WPRL to return PRL version the R-UIM card Removed auto-population of tethered NAI and PPP user id when MDN value is changed on Aeris provisioned modules Added detection of NI OMA/DM session when on a active data call and deferred the OMA/DM session until after the data call is terminated. In added, modified behavior to close a dormant data session before attempting to initiate an OMA/DM session. Fixed system determination issue related to avoiding serving system after detection of max access probes Added AT+IMSIDEF command to reset IMSI to factory default Fixed the buffer issue that was causing data out of sequence when sending over 3000 bytes of data a. Added new option to set SIP PPP username/password using AT+WIPBR command b. Added AT+WRLY command to enable SIP Dial-up connection in relay mode Fixed the issue to update NAI of all enabled MIP profiles during MDN change and FEATUREFLAG_MDN_NAI is enabled. CUS59243 R-UIM ANO60312 R-UIM ANO59453 Aeris ANO58198 ANO61636 Sprint CUS60839 Sprint CUS58901 Sprint CUS57617 R5C N/A DEV57934 R5C N/A NEW58194 R5C N/A 4111924 Rev006 January 16, 2012 10
Firmware Release Note Changes Included in Firmware Description of Issue or New Feature Implementation Details Change ID Fix in Version Carrier Specific Allow AT$QCMIPNAI to change MIP NAI when MDN to NAI auto-propagation is enabled Implement R-UIM functionality Unable to enter online data mode with subsequent TCP socket after previous socket was abruptly terminated during data transfer AT+CCED reports incorrect RX RSSI value when module is not actively scanning In extreme situations module may fail to restore from backup file system if power is abruptly removed during certain instances of flash memory writing Enable ability to open multiple UDP sockets on the same local port When a #777 data (i.e., DUN) call is established over CMUX, DCD is not always being deasserted when DTR is de-asserted to end the call. Entering AT&W may cause +WTBMPRS setting to be reset to 3 Add connection status LED indication to GPIO 0 On some modules, system determination always starts up in home network only mode and any band regardless of +WRMP and +WBND settings stored in NV Cannot send or receive data on socket after socket is closed with no service Fixed the issue to allow AT$QCMIPNAI command to change NAI of active MIP profile if MDN to NAI autopropagation is enabled Added support for R-UIM cards. Requires Q26Elite hardware version Q26EL002. Fixed issue with cleaning up TCP socket after abnormal termination Fixed reporting of RX RSSI value Enhanced redundant file system restoration to handle corner case. Enhanced UDP functionality to allow port re-use Fixed issue with DCD when using CMUX Fixed issue with AT&W command Added AT+WLED command to control functionality of connection status LED GPIO 0 Fixed race condition with system determination initialization Fixed race condition when network is lost while in online mode. DEV58402 R5C N/A NEW57783 ANO57785 R5B R-UIM CUS57159 R5A N/A ANO55681 R5A N/A NEW57289 R5A N/A NEW57303 R5A N/A ANO55808 R4C N/A ANO55495 R4C N/A NEW55494 R4C N/A ANO56457 R4C N/A ANO55263 R3A N/A 4111924 Rev006 January 16, 2012 11
Firmware Release Note Changes Included in Firmware Description of Issue or New Feature Implementation Details Change ID Fix in Version Carrier Specific AT parser locks up when using CMUX and trying data call when no system available +CDS messages do not always appear after MOSMS successfully sent Q26 MuxConfTool locks send on Pipe 1 to Module MRU not cleared when using AT+DPRL and AT+WCMT GEO Jumping Prohibition Failure Module does not perform a Power-Down registration after an OTASP CommitSuppress OTAPA/OTASP(non data only) informational messages Fixed CMUX to correctly enable the data flow when the call ends and the channel is switched back to AT mode. Fixed SMS states check list while receiving a submit report. Fixed a frame retransmission issue. Added code to clear the MRU after PRL download Changed device behavior per Bell Mobility requirements Added new feature flag to enable suppression of OTASP/OTAPA messages as per Verizon spec ANO55680 R3A N/A ANO55299 R3A N/A ANO55264 R3A N/A ANO55722 R3A N/A ANO55078 R3A Bell Mobility DEV55622 R3A Verizon 4111924 Rev006 January 16, 2012 12
3. Restrictions and Known Issues 3.1. Known Issues Title Most AT Commands do not work after escaping from online data mode on a CSD call Quick Net Connect is failing OTASP Commit Request is rejected by module due to OTASP_MSG_TYPE value OK not always received after issuing +++ during a CSD call Lockup of module when varying Mux configuration values and using MuxConfTool repeatedly +WIPCFG missing <opt> 1 - Type of Service (TOS) Description Most AT Commands return ERROR after escaping from online data mode while on a CSD call (either MO or MT) Q26Elite is failing Quick Net Connect. Originate an OTASP call without requesting message encryption. After the call is established, the module is asked to use encryption. After the SSD and Akey values are updated, the network sends a Commit Request to the module. The module responds with a Message Reject Order containing ORDQ="00000110'. This ORDQ value means "message requires a capability that is not supported". While on a CSD call, the module issued +++ to escape online data mode. 90% of the time, "OK" is returned after issuing +++. In the other 10% of the time, "OK" is not returned; however, the user does escape from online data mode. When the MuxConfTool is used with varying values and pipes are opened and closed the AT commands port may eventually lock up and module is non-responsive to AT commands. Type of Service (TOS) is not present on the Q26Elite +WIPCFG command. Change ID ANO51880 ANO52008 ANO48944 ANO52837 ANO54802 NEW52760 4111924 Rev006 January 16, 2012 13