asterisk users - Sep 2003 - Final version of ZapScan

Hey folks --

Some of you had asked about getting my modification to ZapBarge that lets 
you monitor active Zap channels, scanning through them with the # key.

I had posted a version a few days ago that was pretty crude; it didn't 
check to see which channels were active and assumed you had 23.

I've finished a new version that checks to see what channels are actually 
active and pulls that info from the global data structures, so it should 
work on any system.  It will exit if there are no active Zap channels; 
otherwise keep pressing the # key to change channels and it will loop 
through.

Again, it's a patch to app_zapbarge.c and can be saved as a separate app 
called app_zapscan.c.

Patch is here:
http://asterisk.toad.net/app_zapbarge.c-change-to-zapscan

Comments welcome!

Dave

====================================================================David C.
Troy   [dave@toad.net]                   410-384-2500 Sales
ToadNet - Want to go fast?                        410-544-1329 FAX
570 Ritchie Highway, Severna Park, MD 21146-2925  www.toad.net

On Thu, 11 Sep 2003, David C. Troy wrote:
> Some of you had asked about getting my modification to ZapBarge that lets
> you monitor active Zap channels, scanning through them with the # key.
>
Neat application! Its almost what im looking for...

Would it be possible (perhaps by using an argument to ZapScab) to only
monitor one way of the conversation?

Strange request perhaps, but sometimes i run into a situation where one
participant of a MeetMe conference is stuttering. (Most often due to lack
of bandwidth) Naturally this effects all in the conference and i would
like to be able to listen in on what people are sending to the conference
so i could find the "offender" and look into their equipment/setup.

Whould this be possible? Would it bee simple to implement?
Could it be implemented soon?

	/Chris