DEVICE_STATE does not work with a new webrtc extension

[michel.tecinfo]

Hello. My greetings to all.
.When I create a new extension in the database, webrct records, makes and receives calls, but DEVICE_STATE does not reflect the status of the device unless I do module reload res_pjsip.so. After that, DEVICE_STATE works for the extension normally.

exten => _3700,1,NoCDR
same => n,Set(STATUSWEBRTC=${DEVICE_STATE(PJSIP/${EXTEN})})
same => n,NoOp(TEANS extension status is ${STATUSWEBRTC})
same => n,GotoIf($[“${STATUSWEBRTC}” = “UNAVAILABLE”]?unavailable)
same => n,Dial(${PJSIP_DIAL_CONTACTS(${EXTEN})},120,rTt)
same => n,Hangup()

if I remove the device state check the extension works perfectly.

[jcolp]

Device state doesn't change only for new accounts

Qualify support was rewritten in PJSIP, because of poor performance. Trying to have it be dynamic had disastrous performance consequences, to the degree that Asterisk would hang at startup for awhile loading things under .conf file usage - which is the vast majority of usage. Therefore you have to inform Asterisk you’ve added things to the database to have them monitored using the “pjsip reload qualify aor” or “pjsip reload qualify endpoint” CLI commands.

No AMI ContactStatus events for newly created PJSIP clients

Where is configuration being stored? Are you using realtime? If so then Asterisk has to be told about the AOR using the “pjsip reload qualify aor” or “pjsip reload qualify endpoint” CLI commands, which can be done over AMI. Trying to do this automatically proved to be disastrous to performance.

[michel.tecinfo]

Yes, I am using realtime. I only have this problem with the webrtc extensions. I am using Asterisk 20. Does the problem also occur in the new version of Asterisk 22? Will it be resolved if I update?

[jcolp]

It’s how it works. The links I gave include an explanation I wrote previously.