[asterisk-bugs] [JIRA] (ASTERISK-28366) Add timeout for response to StasisStart-event

[Joshua C. Colp (JIRA)]

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

Joshua C. Colp closed ASTERISK-28366.
-------------------------------------

    Resolution: Suspended

I'm suspending this as we don't accept feature requests on the issue tracker, but you can bring it up on asterisk-dev or asterisk-app-dev. If you do so I'll continue there, but in general I don't know if this will be viable since there's nothing that requires a channel to be immediately dealt with - and you aren't guaranteed latency so you'd have to be very careful with the timeout value.

> Add timeout for response to StasisStart-event
> ---------------------------------------------
>
>                 Key: ASTERISK-28366
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28366
>             Project: Asterisk
>          Issue Type: New Feature
>      Security Level: None
>          Components: Resources/res_stasis
>    Affects Versions: 16.2.1
>            Reporter: Morten Tryfoss
>            Severity: Trivial
>
> Many people use a connector from Asterisk ARI to for example NATS or similar message bus. In this scenario the connector may be functional (and the stasis app registered), but no listener might be available to serve the request. 
> Another scenario might be something blocking the ARI app causing it to not respond. 
> Is it possible to add a timeout parameter, dialplan variable or similar to specify how much long you want to wait before returning from Stasis() with FAILED or even TIMEOUT?
> I made a quick proof of concept for myself just counting returns of  "r = ast_waitfor(chan, MAX_WAIT_MS);" in res_stasis.c and break out of the loop if it hits a limit. I guess this works because my app always add the channel to a bridge.



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