[asterisk-bugs] [JIRA] (ASTERISK-25413) pjsip.con indentify_by setting useless for IP-only identification

[Jacek Konieczny (JIRA)]

Jacek Konieczny created ASTERISK-25413:
------------------------------------------

             Summary: pjsip.con indentify_by setting useless for IP-only identification
                 Key: ASTERISK-25413
                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25413
             Project: Asterisk
          Issue Type: Bug
      Security Level: None
          Components: Resources/res_pjsip
    Affects Versions: 13.5.0
            Reporter: Jacek Konieczny


According to https://wiki.asterisk.org/wiki/display/AST/Asterisk+13+Configuration_res_pjsip :
{quote}
identify_by

An endpoint can be identified in multiple ways. Currently, the only supported option is username, which matches the endpoint based on the username in the From header.

Endpoints can also be identified by IP address; however, that method of identification is not handled by this configuration option. See the documentation for the identify configuration section for more details on that method of endpoint identification. If this option is set to username and an identify configuration section exists for the endpoint, then the endpoint can be identified in multiple ways.
{quote}

Indeed, 'username' is the only allowed value here. It is also the default. That becomes a problem when one wants a SIP trunk identified and authenticated by IP-address only – unauthenticated requests from any other IP would also be accepted when the username matches.

I think there should be a way to disable the username-based endpoint identification. I patched Asterisk to make it possible to disable {{identify_by=username}}, but the patch is only a hack/workaround, as the code behind the {{identify_by}} seems to be designed for some other user.



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