[asterisk-bugs] [JIRA] Updated: (ASTERISK-20287) Broken hangupcause passtrough
Rusty Newton (JIRA)
noreply at issues.asterisk.org
Tue Aug 21 11:10:08 CDT 2012
[ https://issues.asterisk.org/jira/browse/ASTERISK-20287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rusty Newton updated ASTERISK-20287:
------------------------------------
Regression: Yes
> Broken hangupcause passtrough
> -----------------------------
>
> Key: ASTERISK-20287
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-20287
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Applications/app_dial
> Affects Versions: 1.8.15.0, 1.8.16.0
> Reporter: Konstantin Suvorov
>
> Setup: [PBX1] -- IAX2 -- [PBX2]
> When you dial from PBX1 with 'g' option, and execute Hangup(custom-cause-code) on PBX2, custom-cause-code will NOT be set to HANGUPCAUSE variable on PBX1.
> PBX1 dialplan excerpt:
> ...
> same => n(dial),Dial(IAX2/${LOGIN}:${PASSWORD}@${HOST}:${PORT}/client,5,g)
> same => n,NoOp(Hangup cause: ${HANGUPCAUSE})
> ...
> PBX2 dialplan excerpt:
> ...
> same => n,Hangup(1)
> In this setup you will get hangupcause=16 instead of expected 1.
> I think this is caused by misplaces 'else' statement in app_dial.c (Revision: 369258, Line 2999) after 1.8.15.0 update.
> In 1.8.13.0 (and I think in 1.8.14.x) it was OK.
> Please fix this, cause this breaks advanced phone routing schemes.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the asterisk-bugs
mailing list