HandsetBugs » History » Version 2
zecke, 02/19/2016 10:48 PM
| 1 | 1 | zecke | |
|---|---|---|---|
| 2 | 2 | zecke | h1. Bugs found in various Mobile Stations |
| 3 | |||
| 4 | |||
| 5 | 1 | zecke | While implementing we observe various things and we attempt to keep track on the issue, their consequence and the phones/firmware version exposing these bugs. |
| 6 | |||
| 7 | |||
| 8 | |||
| 9 | 2 | zecke | h2. Unknown Handsets |
| 10 | |||
| 11 | |||
| 12 | 1 | zecke | For certain issue we have collected the IMEIs and need to find the corresponding device and put it into the table below. |
| 13 | |||
| 14 | 2 | zecke | |
| 15 | h3. Sending the TMSI of the old/previous network |
||
| 16 | |||
| 17 | 1 | zecke | On LOCATION UPDATING REQUEST some handsets do not clear their TMSI and send a TMSI of a foreign network to us. This means we know IMSI, IMEI and TMSI from the previous network. |
| 18 | |||
| 19 | 2 | zecke | |
| 20 | h3. Protocol bug with sending CONNECTED after SETUP on mobile originated calls |
||
| 21 | |||
| 22 | 1 | zecke | On mobile originated calls the BSC will receive a SETUP message and it is legal to respond with CONNECTED. Up to our knowledge the mobile station should display the call as connected but some handsets do not do this. |
| 23 | |||
| 24 | 2 | zecke | |
| 25 | h2. Bug table |
