On Tue, 2008-05-27 at 10:47 -0400, M. Ranganathan wrote: > On Tue, May 27, 2008 at 10:37 AM, Scott Lawrence <[EMAIL PROTECTED]> wrote: > > > > On Tue, 2008-05-27 at 08:28 -0400, M. Ranganathan wrote: > >> Hello, > >> > >> It would be of interest to record calls that pass through sipxbridge . > > > > I'm curious - why do this in sipXbridge? Wouldn't a general recording > > service that could be inserted in any call be better? > > That would be true but since media flows direct end to end in our > system, would that not be problematic? IMHO, the use case for > sipxbridge recording is clear and the solution is easily accomplished.
> For use case, one can envision a scenario where where customers call > in and are put on the park server till the next human attendant > becomes available. When the human picks up, you would want to record > the conversation for "quality assurance purposes". It is easy to > accomplish this in sipxbridge because all the media is bridged and I > can add a media leg to send data to the recorder when the human picks > up ( presumably voicemail is the right place to send it ? ). Nothing > prevents us from turning off recording in sipxbridge when we come up > with a more general solution. The use case you describe seems to me to be more naturally solved in sipXacd, which is where "quality assurance purposes" are most relevant. Putting the feature there would make it work regardless of whether the call came through sipXbridge or some other gateway. It might well be that a general purpose recording solution could be built using substantially the same software as the sipXbridge SBC function, but I think it would be better to think of it as something different that happens to share most of the same software (indeed, the difference might only be configuration). The trick (as you imply) is knowing which calls _might_ need the recording function so that you know which calls to route through the recorder (or when to transfer them so that they go through the recorder). -- Scott Lawrence tel:+1.781.229.0533;ext=162 or sip:[EMAIL PROTECTED] sipXecs project coordinator - SIPfoundry http://www.sipfoundry.org/sipXecs CTO, Voice Solutions - Bluesocket Inc. http://www.bluesocket.com/ http://www.pingtel.com/ _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
