[asterisk-bugs] [JIRA] (ASTERISK-25078) sig_pri: Publish progress codes.

[Richard Mudgett (JIRA)]

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

Richard Mudgett commented on ASTERISK-25078:
--------------------------------------------

Cause 127 is a network interworking code that doesn't have a set procedure specifying how it should be used.

Unfortunately, your idea of setting a channel variable isn't going to work because it will be set on the wrong channel.  The channel the cause information is available on is the outgoing channel of the Dial when you need that information on the dialing channel.  The HANGUPCAUSE function gets its information from the AST_CONTROL_PVT_CAUSE_CODE frame.  The problem is HANGUPCAUSE only keeps the last value produced by each dialed channel.  You may want to consider a solution based on the AST_CONTROL_PVT_CAUSE_CODE frame such as adding the ability to keep all values from each channel and being able to retrieve specified values.

> sig_pri: Publish progress codes.
> --------------------------------
>
>                 Key: ASTERISK-25078
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25078
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_dahdi
>    Affects Versions: SVN, 11.17.1, 13.3.2
>            Reporter: Corey Farrell
>            Assignee: Rusty Newton
>            Severity: Minor
>         Attachments: chan_dahdi.conf, pridebug.txt
>
>
> I'm dealing with a PRI provider who frequently responds to calls with PROGRESS code 127.  These usually timeout, and result in Asterisk reporting NOANSWER.  Over 60% of the NOANSWER calls on one system have progress code 127 (found in logs), so If we have 5000 outbound NOANSWER calls, probably 3000 of them are really 'unknown telco error'.
> It would be very useful to be able to determine the last progress code received after Dial.  This way if DIALSTATUS is NOANSWER, we can check PRILASTPROGRESS and possibly use it instead of HANGUPCAUSE.
> Is this something that would be accepted - setting a channel variable from pri_dchannel in sig_pri.c?   It would be done near the code to deal with broken PRI's that send AST_CAUSE_USER_BUSY as progress.  If not is there another work-around that I'm not considering?



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