Asterisk 18.5.17 Endpoint is still unavailable after Agent is logged in

Hi All,

After Endpoint is created, we logged in a Agent, the contact is created properly but Endpoint status is still unavailable.

https://issues.asterisk.org/jira/browse/ASTERISK-28393
https://issues.asterisk.org/jira/browse/ASTERISK-28056

it seems that the issue is similar to the jira above. However when I checked the code, I believe the version of 18.5.17 already have those fixes.

I checked the debug log, after the agent is logged in, the contact is added but seems the process is stopped at this point, but it did not call “pjsip_options.c”. so the status is still unavailable.

[2023-04-08 04:05:20.445] VERBOSE[17979] res_pjsip_registrar.c: Added contact ‘sip:2044@103.199.7.5:53643;ob’ to AOR ‘2044@1.collabos.com’ with expiration of 300 seconds

The status is changed to “Not In Use” only after I did a “module reload res_pjsip.so” or “reload”.

[2023-04-08 04:05:48.968] DEBUG[17980] res_pjsip/pjsip_options.c: Synchronizing AOR ‘2044@1.collabos.com’ with current state of configuration and world
[2023-04-08 04:05:48.968] DEBUG[17980] res_pjsip/pjsip_options.c: Configuring AOR ‘2044@1.collabos.com’ with current state of configuration and world
[2023-04-08 04:05:48.974] DEBUG[17980] res_pjsip/pjsip_options.c: AOR ‘2044@1.collabos.com’ is unqualified, number of available contacts is therefore ‘1’
[2023-04-08 04:05:48.974] DEBUG[17980] res_pjsip/pjsip_options.c: AOR ‘2044@1.collabos.com’ now has 1 available contacts

I attached the logs including the asterisk debug log, pjsip.conf, “pjsip show endpoint” and “commands to create the endpoint” – that would be high appreciate if you can help to have a look and share your idea/advice

*Notes: The issue have happened all times on our labs (Asterisk 18.4 and 18.5)

pjsip_conf.txt (913 Bytes)

full_debug_log_level_05.txt (520.7 KB)
commands_add_endpoint_to_asterisk_DB.txt (679 Bytes)
pjsip_show_endpoint.txt (16.0 KB)

If using realtime then see this other topic:

You have to tell Asterisk you’ve created the AOR so it can monitor it.

Thank you very much for your help,

I have tried this “pjsip reload qualify aor 2046@1.collabos.com”, it works well
I think we will implement to send a AMI action after a new User is created

root@ip-172-31-34-95:/etc/asterisk/bkup# asterisk -rx “pjsip reload qualify aor 2046@1.collabos.com
Synchronizing AOR ‘2046@1.collabos.com’

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.