On Sun, 2009-12-06 at 16:23 -0500, Alfred Campbell wrote: > > Hi, > > > > In order to allow the Mediant1000/2000/3000 gateway to control the MWI > > and Transfer Supplementary Services on a PRI-QSIG link I'm proposing > > adding the following parameters to the Mediant INI file generated by > > sipXconfig. These parameters are supported by the 5.0/5.2/5.4/5.6 > > versions of the Mediant firmware. > > > > Please note that some of these parameters are already being sent to > the > > Audiocodes FXS gateways (as noted below): > > > > EnableMWI (default=0) Already exists for FXS, > > controls sending of MWI > > DefaultNumber (default=ServedUser) Default indicates MWI > > destination will be controlled by NOTIFY contents > > MwiSourceNumber (default blank) Controls calling number in > PRI > > SETUP > > VoiceMailInterface (default=3, hidden) Default indicates PRI-QSIG > MWI > > > > SubscriptionMode (default=1, hidden) Already exists for FXS, but > we > > want no MWI subscription on PRI > > > > TrunkTransferMode (default blank) Controls QSIG transfer > > supplementary service > > > > > > Any comments or suggestions? > > Thanks... > > Dave. > > My only comment is it maybe good to think about how best to > group/present these. I know you have a very specific application you > plan on using these for... Maybe the screens can reflect this? instead > of just adding more cryptic parameters to the Audiocodes it could be > done in a way to enable the functionality you are developing.
Indeed - is there any reason why a normal sipXecs user would manipulate any of these otherwise? Can we just make an abstract setting "Enable SIP MWI to QSIQ MWI" that then does all the right things? _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
