[asterisk-bugs] [Asterisk 0017880]: Remove dahdi and meetme dependency for page function
Asterisk Bug Tracker
noreply at bugs.digium.com
Wed Aug 25 12:39:45 CDT 2010
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=17880
======================================================================
Reported By: ip-rob
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 17880
Category: Applications/app_page
Reproducibility: N/A
Severity: feature
Priority: normal
Status: feedback
Asterisk Version: 1.6.2.11
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2010-08-17 19:29 CDT
Last Modified: 2010-08-25 12:39 CDT
======================================================================
Summary: Remove dahdi and meetme dependency for page function
Description:
Most of the features now are independent of dahdi for a timing source now
that there is kernel timing available in 1.6.2. app_page.c is still
dependent upon dahdi and meetme because uses meetme to merge the channels.
It would be better to remove that dependency. I've attached a diff which
changes the application to confbridge rather than meetme. The recording
feature isn't available but it seems like a better solution than the
existing app_page.c since it removes the dependencies.
Would it be possible to have the application detect if meetme is available
at build time and then make the "r" option available if meetme is there?
======================================================================
----------------------------------------------------------------------
(0126328) ip-rob (reporter) - 2010-08-25 12:39
https://issues.asterisk.org/view.php?id=17880#c126328
----------------------------------------------------------------------
That is a good idea. The best option would be to check for the page
application and if it is available go ahead and use that option. If not,
then write a warning the log that confbridge is being used instead and
recording isn't available. Then use confbridge to mix the channels.
I've been testing confbridge a little more and am having a few issues
getting things to work. I'll see what I can do but I don't have any
license on file to submit a patch.
FYI, this is the same approach that patches I've supplied to freepbx do as
well, check for an application that may require dahdi and if it is
available use it (e.g. meetme) and if not, then use an alternative
(confbridge) and reduce the options displayed to the end user. This would
be a similar tack taken in app_page.c.
Does that make sense?
Issue History
Date Modified Username Field Change
======================================================================
2010-08-25 12:39 ip-rob Note Added: 0126328
======================================================================
More information about the asterisk-bugs
mailing list