[asterisk-bugs] [JIRA] (ASTERISK-25020) Mismatched response to outgoing REGISTER request

Mark Michelson (JIRA) noreply at issues.asterisk.org
Mon Apr 27 12:40:32 CDT 2015


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

Mark Michelson updated ASTERISK-25020:
--------------------------------------

    Attachment: Fatal_404_response

I am attaching Fatal_404_response to the issue. This is the log accompanying the issue. I have anonymized the file by replacing all IP addresses with "ip_addr". These shouldn't have any bearing on the actual issue, so for now I'm not trying to differentiate between different ones. If it becomes problematic, I can re-anonymize them but differentiate between the IP addresses involved.

> Mismatched response to outgoing REGISTER request
> ------------------------------------------------
>
>                 Key: ASTERISK-25020
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25020
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip
>    Affects Versions: 13.1.0
>            Reporter: Mark Michelson
>         Attachments: Fatal_404_response
>
>
> Internal testing at Digium encountered a situation where some mysterious happenings occurred regarding an outbound REGISTER. The logs show an outbound REGISTER occurring, then receiving a 401 response to the REGISTER. After this, there are a series of incoming REGISTER transactions and outbound OPTIONS transactions. And at the very end, there is an error message showing that the outbound registration failed due to a fatal 404 response being received.
> The logs show no such 404 response being received in response to the outbound REGISTER. What's odd, though, is that immediately before the warning is printed, there is a 404 received in response to an outbound OPTIONS request. Based on the limited debugging, the conclusion may be that somehow, the 404 response to the OPTIONS request somehow got treated as a response to a REGISTER.



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



More information about the asterisk-bugs mailing list