[asterisk-bugs] [JIRA] (ASTERISK-27374) alembic: PJSIP scripts are missing column bundle in ps_endpoints table

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-27374:
------------------------------------------

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.

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].

> alembic: PJSIP scripts are missing column bundle in ps_endpoints table
> ----------------------------------------------------------------------
>
>                 Key: ASTERISK-27374
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27374
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip
>    Affects Versions: 15.0.0
>         Environment: Debian 9 amd64
>            Reporter: Florian Floimair
>            Severity: Minor
>
> git commit 065c3005ad92 added the bundle option to res_pjsip, however this change never made it to the alembic scripts and therefore the ps_endpoint table is missing a column for it.
> This is obvious when trying to use ARI to create PJSIP endpoints which will show a similar error on the CLI than in ASTERISK-27168 due to a mismatch in parameters between JSON and the generated SQL statement.
> I will upload a patch for the alembic scripts today that fixes this issue.



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