No RING when settings was changed

[VasylSamoilov]

If quectel settings were changes, there is a possibility that module will not indicate RING and will not react to incoming calls in console.
Please consider adding AT+QURCCFG="urcport","usbat" to the list of initialization commands.
There are possibly some other commands that can suppress ring indication, they can be considered too.

Per-device user-defined init strings can also be an option, to init some quectel variants properly.

[IchthysMaranatha]

Generally, one time settings are not added to initialization commands, only those that are needed on every reboot.

[VasylSamoilov]

That is understandable, but proper output of ring indication is necessary for proper operation, otherwise you get undefined behavior (it may ring, or it may not). It's not one-time, it should be ensured on every reboot.

[IchthysMaranatha]

Command needed is one time, it persists on every reboot. If someone changes it, he/she should change it back to work with this again.

[VasylSamoilov]

Not the most elegant solution, but it surely can be a documentation item. Closing.

[VasylSamoilov]

Some software like quectels native Qnavigator resets this setting when initializing modem, and default value is (or maybe, depending on module) different from what is required. Implicitly setting this value during initialization can help with a lot of confusion when device is not exclusively used with chan_quectel. This setting is required to be set for proper operation.

[maisx2021]

Hello everyone,
I'm experimenting with the Chan-Quectel script on a RaspPBX running on a Raspberry Pi. It's being detected perfectly by Asterisk in UAC mode, but when I receive a call, Asterisk remains completely silent in the console. What could be the issue? Thank you very much for any assistance.
Maisx

[VasylSamoilov]

try https://github.com/RoEdAl/asterisk-chan-quectel - it's a better fork as far as I tested.