> > > > 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. >
The Audiocodes Mediant1000 parameters will look similar to the Audiocodes FXS gateway parameters, I've just attached screenshots to http://track.sipfoundry.org/browse/XX-7193 The "Calling Party Number" and "Called Party Number" are new for the Mediant1000 and control the contents of the PRI SETUP message used for MWI. Dave. _______________________________________________ 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/
