[asterisk-bugs] [JIRA] (ASTERISK-20716) "s" extension in comebackcontext not honored

[Rusty Newton (JIRA)]

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

Rusty Newton updated ASTERISK-20716:
------------------------------------

    Assignee: Chris Gentle  (was: Rusty Newton)
      Status: Waiting for Feedback  (was: Open)

Acknowledged, this does look like a bug. Configuration looks correct, and it's not behaving as advertised in features.conf.

Thanks. Can you also post a log with VERBOSE and DEBUG messages enabled as requested above? https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information

                
> "s" extension in comebackcontext not honored
> --------------------------------------------
>
>                 Key: ASTERISK-20716
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20716
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Features/Parking
>    Affects Versions: 11.0.1
>         Environment: Linux, Ubuntu Server 12.04.1, 32bit
>            Reporter: Chris Gentle
>            Assignee: Chris Gentle
>            Severity: Minor
>         Attachments: extensions.conf, features.conf, log
>
>
> Assume the following defined in features.conf:
> comebacktoorigin=no
> comebackcontext=parkedcallstimeout
> Parked calls that are sent back to parkedcallstimeout do not use the "s" extension if it is defined.  An error is generated in the Asterisk log as follows:
> {noformat}
> [2012-11-19 20:46:58] WARNING[23894][C-0000003e] pbx.c: Channel 'SIP/gentlec-000000c9' sent to invalid extension but no invalid handler: context,exten,priority=parkedcallstimeout,SIP_gigaset,1
> {noformat}
> Defining a specific extension, SIP_gigaset in this case, works.  However, this does not agree with the documented behavior in the features.conf sample file.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira