The expected values are already written (and work). This would just be to define the MOH to loop or not. This would be a single line entry in the freeswitch side, as has been explained to me.
On Fri, Apr 23, 2010 at 10:34 AM, Bogdan Brezoi <[email protected]> wrote: > Hi, > > I'm working on http://track.sipfoundry.org/browse/XX-8070 (MOH Behavior > Type) . It looks like for this issue - from sipXconfig point of view - > it should be sufficient to have a new setting in the UI which will tell > if the normal/loop mode it should be used for the system MOH. This > setting would be written in a configuration file and used by > sipXivr/Freeswitch (if I am not mistaking, sipXivr is resopnsible for > MOH playing) to change the way MOH is played. > If this is the case, we would need to know some details about what it is > expected from sipXconfig to generate (the name and the possible values > of the parameter, and the configuration file in which it should be > written). > If am wrong or missing something, please advise. > > Thanks, > Bogdan > _______________________________________________ > 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/ > -- ====================== Tony Graziano, Manager Telephone: 434.984.8430 Fax: 434.984.8431 Email: [email protected] LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 Fax: 434.984.8427 Helpdesk Contract Customers: http://www.myitdepartment.net/gethelp/ Why do mathematicians always confuse Halloween and Christmas? Because 31 Oct = 25 Dec.
_______________________________________________ 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/
