[asterisk-bugs] [JIRA] (ASTERISK-27946) dial (API): Storage of dialed target uses AST_MAX_EXTENSION when it shouldn't

[Asterisk Team (JIRA)]

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

Asterisk Team updated ASTERISK-27946:
-------------------------------------

    Target Release Version/s: 17.4.0

> dial (API): Storage of dialed target uses AST_MAX_EXTENSION when it shouldn't
> -----------------------------------------------------------------------------
>
>                 Key: ASTERISK-27946
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27946
>             Project: Asterisk
>          Issue Type: Improvement
>      Security Level: None
>          Components: Applications/app_page, Core/Dial
>    Affects Versions: 15.4.1
>            Reporter: Joshua Elson
>            Severity: Minor
>              Labels: pjsip
>      Target Release: 13.33.0, 16.10.0, 17.4.0
>
>
> We are seeing more issues in what we'd consider "normal" circumstances where Dial strings are exceeding AST_MAX_EXTENSION and AST_CHANNEL_NAME length, currently set to 80.
> In particular, PJSIP_DIAL_CONTACTS expansion is often producing dial strings such as these:
> PJSIP/102-RelativelyLongStringName/sip:102-RelativelyLongStringName at 100.100.100.190:11881;transport=TCP
> When called by Page application - Page($\{PJSIP_DIAL_CONTACTS($\{EXTEN})}) - for instance, this ends up getting cut off awkwardly and producing failed dial attempts:
> dial.c: Called 102-RelativelyLongStringName/sip:102-RelativelyLongStringName at 100.100.100.190:11
> Would raising AST_MAX_EXTENSION from 80 to 100 or something slightly more be an acceptable solution here?



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