[asterisk-bugs] [JIRA] (ASTERISK-22552) Need log messages - res_pjsip_endpoint_identifier_user.so fails to find an endpoint match on inbound REGISTER

[Rusty Newton (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-22552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rusty Newton updated ASTERISK-22552:
------------------------------------

    Description: 
res_pjsip_endpoint_identifier_ip lets us know when it fails to find a match

{noformat}
[Sep 18 13:10:46] DEBUG[24573]: res_pjsip_endpoint_identifier_ip.c:134 ip_identify: '10.24.18.138:5060' did not match any identify section rules
{noformat}

We need a similar DEBUG message for res_pjsip_endpoint_identifier_user  ( I didn't see anything in logging) when it fails to find a match.

It may also make sense to have a WARNING or a higher level VERBOSE (maybe 3) that alerts when an inbound REGISTER has no match. That is something an admin will want to know about, without having to first look into SIP debug.

I was testing with a REGISTER and saw this, but I'd presume this applies to INVITEs and other inbound traffic as well.

  was:
res_pjsip_endpoint_identifier_ip lets us know when it fails to find a match

{noformat}
[Sep 18 13:10:46] DEBUG[24573]: res_pjsip_endpoint_identifier_ip.c:134 ip_identify: '10.24.18.138:5060' did not match any identify section rules
{noformat}

We need a similar DEBUG message for res_pjsip_endpoint_identifier_user  ( I didn't see anything in logging) when it fails to find a match.

It may also make sense to have a WARNING or a higher level VERBOSE (maybe 3) that alerts when an inbound REGISTER has no match. That is something an admin will want to know about, without having to first look into 

I was testing with a REGISTER and saw this, but I'd presume this applies to INVITEs and other inbound traffic as well.

    
> Need log messages - res_pjsip_endpoint_identifier_user.so fails to find an endpoint match on inbound REGISTER
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-22552
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22552
>             Project: Asterisk
>          Issue Type: Improvement
>      Security Level: None
>          Components: Resources/res_pjsip_endpoint_identifier_ip, Resources/res_pjsip_endpoint_identifier_user
>    Affects Versions: SVN
>         Environment: SVN-branch-12-r399268
>            Reporter: Rusty Newton
>            Severity: Minor
>
> res_pjsip_endpoint_identifier_ip lets us know when it fails to find a match
> {noformat}
> [Sep 18 13:10:46] DEBUG[24573]: res_pjsip_endpoint_identifier_ip.c:134 ip_identify: '10.24.18.138:5060' did not match any identify section rules
> {noformat}
> We need a similar DEBUG message for res_pjsip_endpoint_identifier_user  ( I didn't see anything in logging) when it fails to find a match.
> It may also make sense to have a WARNING or a higher level VERBOSE (maybe 3) that alerts when an inbound REGISTER has no match. That is something an admin will want to know about, without having to first look into SIP debug.
> I was testing with a REGISTER and saw this, but I'd presume this applies to INVITEs and other inbound traffic as well.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira