(First of all thank you for maintaining this fork! It is highly appreciated.)
The calls stopped going into the dongle-incoming without any obvious reason (incoming SMS and USSD were still working). I didn't change the configuration for a long time, so I thought that it was something external.
Switching the log level to debug in /etc/asterisk/logger.conf
console => notice,warning,error,debug
I saw the following errors after initiating an incoming call to Asterisk from +1234567890 (redacted):
The result was the same as before I set it to 0 (a bit strange to me), but the calls are now working fine (going into case RES_RING: of at_response.c).
Looks like at_response.c needs another case for handling CRING (and perhaps CLIP) when AT+CRC=1 (set by one's service provider externally?)
(First of all thank you for maintaining this fork! It is highly appreciated.)
The calls stopped going into the
dongle-incoming
without any obvious reason (incoming SMS and USSD were still working). I didn't change the configuration for a long time, so I thought that it was something external.Switching the log level to
debug
in/etc/asterisk/logger.conf
I saw the following errors after initiating an incoming call to Asterisk from
+1234567890
(redacted):Since it was
CRING
, notRING
, I was in theRES_UNKNOWN:
case ofat_response.c
After performing a search, I found out that this may be when
AT+CRC
is set to1
(cellular result codes are switched to the extended format).I checked the current value of
CRC
:Set it to
0
Checked if it is indeed
0
The result was the same as before I set it to
0
(a bit strange to me), but the calls are now working fine (going intocase RES_RING:
ofat_response.c
).Looks like
at_response.c
needs anothercase
for handlingCRING
(and perhapsCLIP
) whenAT+CRC=1
(set by one's service provider externally?)