[asterisk-bugs] [JIRA] (ASTERISK-15720) Buggy parse of request-line in function check_user_full()

[Matt Jordan (JIRA)]

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

Matt Jordan closed ASTERISK-15720.
----------------------------------

    Resolution: Suspended

> Buggy parse of request-line in function check_user_full()
> ---------------------------------------------------------
>
>                 Key: ASTERISK-15720
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-15720
>             Project: Asterisk
>          Issue Type: Bug
>          Components: Channels/chan_sip/General
>            Reporter: nick_lewis
>            Severity: Minor
>
> Before get_destination() does a proper parsing of the request-line to find the pvt->exten, pvt->domain etc, check_user_full does a buggy parse of it to build a contact. The buggy parser does not correctly handle the userinfo portion of the request-line if it contains a password or a ";" character
> ****** ADDITIONAL INFORMATION ******
> Is getting the pvt->exten at this stage really necessary? Could the contact instead be set to S_OR(peer->username,peer->peername). Does it matter about the user portion of the contact at this stage as long as it is in the correct dialog?
> If the requested exten does need to be in the contact then the request-line should be parsed properly before check_user_full and get_destination



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