[asterisk-bugs] [JIRA] (ASTERISK-27788) pjsip does not write log file entries when an endpoint becomes (un)reachable/lagged

[Gregory Massel (JIRA)]

Gregory Massel created ASTERISK-27788:
-----------------------------------------

             Summary: pjsip does not write log file entries when an endpoint becomes (un)reachable/lagged
                 Key: ASTERISK-27788
                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27788
             Project: Asterisk
          Issue Type: Bug
      Security Level: None
          Components: Resources/res_pjsip
    Affects Versions: 13.20.0
         Environment: Ubuntu 16.04.4 LTS, x86_64, Asterisk 13.20.0.
            Reporter: Gregory Massel
            Severity: Minor


chan_sip (with qualify=yes) writes log entries such as:

[Mar  6 10:02:21] NOTICE[19683] chan_sip.c: Peer 'xxx' is now Lagged. (3552ms / 3000ms)
[Mar 29 18:40:09] NOTICE[19683] chan_sip.c: Peer 'xxx' is now UNREACHABLE!  Last qualify: 9
[Mar 29 18:40:20] NOTICE[19683] chan_sip.c: Peer 'xxx' is now Reachable. (1286ms / 3000ms)

However, chan_pjsip does NOT write similar log entries.

With pjsip, if an endpoint or aor has qualify=yes, it will monitor it, however, no log entry is written when it becomes unreachable and subsequently becomes reachable again.

This would typically also need to log upon inbound registration.

This is a feature parity issue.




--
This message was sent by Atlassian JIRA
(v6.2#6252)