| Summary: | ASTERISK-00584: [request] More common "builtin" functionality handling | ||
| Reporter: | Paul Cadach (pcadach) | Labels: | |
| Date Opened: | 2003-11-27 14:13:08.000-0600 | Date Closed: | 2011-06-07 14:04:40 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | I think Asterisk requires more common way to handle diffirent types of peripheral devices such as phones and channels. Currently, some channels have "built in" functionality to support locally-connected devices (phones) to handle some sort of transfers/forwards, call waiting, conferencing, etc., and implementing new functions will require to include it to other channels which supports such "locally-connected" devices. ****** ADDITIONAL INFORMATION ****** Common functionality for external devices already exists - it's *pbx* functions. I think handling of local devices just require a mechanism like for *pbx*, for example, *switch* functions, which will handle all activity on the phones. Also, usual app_disa can just call *switch* functionality and will provide exactly same interface like for "local" users. | ||
| Comments: | By: Paul Cadach (pcadach) 2004-03-21 12:56:32.000-0600 Some phones also have builtin call-handling features (hold, transfer, call park, conferencing, etc.), so I think internal bridge code used by dial application requires some sort of hooks to handle those features (for example, user presses 'call park' button and phone/channel driver remembers an extension which must be dialled to pick-up parked call; when user press 'call park' again call will be un-parked from stored slot). By: Brian West (bkw918) 2004-04-17 23:02:38 If this is something you would be intrested in please post back and we will go form there... just trying to clean house. Thanks, House Keeping... | ||