| Summary: | ASTERISK-02126: [request] Specify ZapBarge audio direction | ||
| Reporter: | lesnet (lesnet) | Labels: | |
| Date Opened: | 2004-07-27 12:26:29 | Date Closed: | 2011-06-07 14:05:12 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Core/NewFeature |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | ZapBarge currently listens to TX/RX (both) directions of the conversation. this is not usefull when trying to isolate app_meetme noise problems. You have to be able to listen to the ?input/caller? side of the conversation (ie: what they are sending to the system, not what you are sending them) Changing in app_zapbarge.c: ztc.confmode = ZT_CONF_MONITORBOTH; --to-- ztc.confmode = ZT_CONF_MONITOR; Solves this problem by allowing you to listen to what the caller is sayign on the line, but not hearing the entire app_meetme conference. So, it would be nice to be able to provide a direction parameter to say whether you want to listen to TX/RX, TX, or just RX. | ||
| Comments: | By: twisted (twisted) 2004-07-27 12:28:40 lesnet, I'm going to have to ask you to please make your requests start with [Request] in the title, as well as if you have already achieved them, instead of posting requests, file a disclaimer and post a patch. Otherwise, your requests for meetme will need to be moved to the wiki for the next verison of the confrencing application. By: Brian West (bkw918) 2004-08-11 23:07:17 The problem with meetme and iax is know and I think solved as of late. No need to modify zapbarge because it wont catch the problem. | ||