08-07-2021, 01:20 PM
As the title suggests, my problem is not related to any modem management software.
The first incoming call after the modem starts up works fine.
But after that first call, regardless of whether I answer it or not, new incoming calls won't go through - They won't even do the ringing tones on the other phone that I'm calling the PinePhone with.
If I had to guess, I'd say the modem is announcing to the network that it is busy or something like that, causing it to not receive any calls, because for what it seems, the call isn't even reaching the modem. Again, I'm just guessing, I don't really know how cellular networks work.
Is there any AT command that would set/unset some busy state like that?
If not, then I was hoping somebody could test to see if you get the same results:
1. Boot an OS and stop ModemManager (I suggest using an sxmo image, not sure how easy it would be to completely stop modem management on other UIs).
2. `sudo screen /dev/ttyUSB2` (or just use atinout or minicom if you prefer)
3. Unlock the SIM (AT+CPIN=<YOUR_SIM_PIN>)
4. Give yourself a call from another phone.
5. You should hear the ringing tones on the calling side.
6. The caller's number should show on the output of "AT+CLCC"
7. Hang up
8. Repeat from step 4. Does the call go through? Can you hear the beeping on the calling side? Does it show up on "AT+CLCC"? Cause for me it doesn't ;-(
9. If everything works without a problem, try again a couple more times just to be sure. It does have some unexpected behavior for me sometimes.
My firmware revision (AT+GMR) is EG25GGBR07A08M2G
Restoring the factory defaults with "AT&F" didn't fix it
The first incoming call after the modem starts up works fine.
But after that first call, regardless of whether I answer it or not, new incoming calls won't go through - They won't even do the ringing tones on the other phone that I'm calling the PinePhone with.
If I had to guess, I'd say the modem is announcing to the network that it is busy or something like that, causing it to not receive any calls, because for what it seems, the call isn't even reaching the modem. Again, I'm just guessing, I don't really know how cellular networks work.
Is there any AT command that would set/unset some busy state like that?
If not, then I was hoping somebody could test to see if you get the same results:
1. Boot an OS and stop ModemManager (I suggest using an sxmo image, not sure how easy it would be to completely stop modem management on other UIs).
2. `sudo screen /dev/ttyUSB2` (or just use atinout or minicom if you prefer)
3. Unlock the SIM (AT+CPIN=<YOUR_SIM_PIN>)
4. Give yourself a call from another phone.
5. You should hear the ringing tones on the calling side.
6. The caller's number should show on the output of "AT+CLCC"
7. Hang up
8. Repeat from step 4. Does the call go through? Can you hear the beeping on the calling side? Does it show up on "AT+CLCC"? Cause for me it doesn't ;-(
9. If everything works without a problem, try again a couple more times just to be sure. It does have some unexpected behavior for me sometimes.
My firmware revision (AT+GMR) is EG25GGBR07A08M2G
Restoring the factory defaults with "AT&F" didn't fix it