[asterisk-bugs] [JIRA] (ASTERISK-29665) pjproject silently drops registration requests using RFC 8898 syntax

[Asterisk Team (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-29665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=256405#comment-256405 ] 

Asterisk Team commented on ASTERISK-29665:
------------------------------------------

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.

Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/].

> pjproject silently drops registration requests using RFC 8898 syntax
> --------------------------------------------------------------------
>
>                 Key: ASTERISK-29665
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29665
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: pjproject/pjsip
>    Affects Versions: 18.6.0
>         Environment: FreePBX 15.0.17.55, OBi2182 phone running firmware version 6.2.3 (Build: 5330.1311)
>            Reporter: Robert Lenoil
>
> If a user agent tries to register using the OAuth-based token mechanism specified in [RFC 8898|https://www.rfc-editor.org/rfc/rfc8898.pdf], sip_transport.c logs error #2616 and discards the registration request, instead of returning a 407 Proxy Authentication Required error. The user agent, receiving no response from the server, repeatedly resends the registration request, with frequency as set in the user agent's configuration.
> This came about when a service provider set in the OBi2182 that was previously used for Google Voice was changed to SIP and loaded with the registration data for the Asterisk server. The phone, instead of erasing the previous auth token when the service provider is changed, tries sending the old token to the Asterisk server. Presumedly, once the phone receives an error from the server it will then discard the token and try to re-register with an allowed authentication mechanism, but receiving no response, it just assumes the server is down and forever tries to register. Until the server or client software is fixed, the service provider slot is rendered permanently unavailable for SIP connections.



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