It's just a function that I see in SBC's. I could see some usefulness in killing a hung call for example, without restarting a service. It would also be useful in stopping a call in progress with a user who needs to stop calling a number they've been asked to stop calling (receptionist talking to her boyfriend way too much).
I'm also accustomed to seeing it in gateways. Since sipXbridge is taking on those roles, I thought I'd ask. >>> "M. Ranganathan" <[email protected]> 05/10/09 8:34 PM >>> On Sun, May 10, 2009 at 1:52 PM, Tony Graziano <[email protected]> wrote: > With typical SBC's which handle remote NAT traversal or siptrunking, it is > possible to view calls in progress and remote users coming through the system. > > While you can see registrations via the "registration" function, and calls in > progress via CDR, it makes sense to have a separate option in sipXconfig to > see the calls or remote workers using sipXbridge. Also with the option to > "cancel" an active call or "kill" a remote registration via the interface as > a SBC management function. It is fairly straightforward to implement this functionality in sipxbridge. The problem as usual is going to be how to display this information in a sensible manner so the user knows what call to cancel. Not sure if Cancel would be on the top of my list of useful additions. However, it would at least, be of use to show the active registrations. > > Does this make any sense? If so, could sipXbridge be extended to offer this > functionality? > > Tony > > _______________________________________________ > sipx-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev > -- M. Ranganathan _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
