[asterisk-bugs] [JIRA] (PRI-185) MWI on QSIG

[Richard Mudgett (JIRA)]

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

Richard Mudgett commented on PRI-185:
-------------------------------------

Features requests without patches are not accepted through the issue tracker. Features requests are openly discussed on the mailing lists, forums, and IRC [1]. Please see the Asterisk Issue Guidelines [2] for more information on feature request and patch submission.

[1] http://asterisk.org/community/discuss
[2] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines

There is no current development on this project at Digium so you will need to supply a patch.

> MWI on QSIG
> -----------
>
>                 Key: PRI-185
>                 URL: https://issues.asterisk.org/jira/browse/PRI-185
>             Project: LibPRI
>          Issue Type: Improvement
>      Security Level: None
>          Components: General
>         Environment: HP DL360 Server running Linux with Digium 1TE245 Dual-port E1 Card.
>            Reporter: Ken Nugent
>            Assignee: Richard Mudgett
>
> We sell an Asterisk-based product which provides a message announcement feature. The system provides a bridging function between two E1 spans -
>  ingress calls arriving on one span are answered, they receive a pre-recorded message and are then forwarded to the egress span. Installations are either PRI-ISDN or QSIG.
> We have recently encountered the issue of MWI not being supported on QSIG where our system is interconnected in a link between two PABX's. We see the following message in the span trace:
> "!! ROSE invoke operation not handled on switchtype:Q.SIG switch! ROSE_QSIG_MWIActivate"
> ...and we see the following code in pri_facility.c
> "#if 0 /* Not handled yet */ 
> case ROSE_QSIG_MWIActivate:
> break;
> case ROSE_QSIG_MWIDeactivate:
> break;
> case ROSE_QSIG_MWIInterrogate:
> break;
> #endif /* Not handled yet */
> "
> ...Given the "Not handled yet", we were just wondering what the options are. Is there a chance of having the MWI feature completed sufficiently for our purposes - we are wanting to have the MWI message received correctly on the ingress side and a corresponding message sent on the egress side (both E1/QSIG). We have a client who is potentially willing to pay for the development if that helps. We need to understand a plan for moving forward by 26/5/2017 so your prompt reply would be greatly appreciated.
> Many thanks,
> Ken.



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