| Summary: | ASTERISK-04291: [patch] ChanSpy ignores Zap/pseudo | ||
| Reporter: | Clod Patry (junky) | Labels: | |
| Date Opened: | 2005-05-26 20:21:16 | Date Closed: | 2011-06-07 14:10:47 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ( 0) chanspy_pseudo.txt | |
| Description: | With current app_chanspy.c, it will check for any channels which is good. This will work for Zap/pseudo which aren't for audios. So when changing on spyee, we sometimes get something like: May 26 19:03:52 WARNING[28222]: app_chanspy.c:478 start_spying: Attaching SIP/100-5e9a to Zap/pseudo-1584792990 which can be skipped to the next channel. So now it will just print a debug message like: May 26 21:02:48 DEBUG[31188]: apps/app_chanspy.c:745 chanspy_exec: Zap/pseudo-66620732 is a Zap/pseudo channel, ignoring it. and goes to the next channel. In that way there's no needs to change of channel when the current channel's a pseudo, cause it won't take them for spyee. ****** ADDITIONAL INFORMATION ****** Disclaimer on file. | ||
| Comments: | By: Michael Jerris (mikej) 2005-05-27 10:58:54 This depends on meetme's naming of zap pseudo channels. If you really want to know if a channel is real or not we would need somthing on the channel structure to tell us (but we don't have that)... Do we really want meetme specific code in chanspy? Why not use a group, then the pseudo would not be in the group.. By: Clod Patry (junky) 2005-05-27 12:31:01 Apparently i'm the only one to have that need. It was just to play around chanspy. If someone wants to have that in HEAD, feel free to re-open. | ||