Re: [Asterisk-Users] *78 *72 and sip?
I know *8 kind of works with SIP but what about the rest should they work do they work with a zap device? *0# sends flash *8# remote call pickup (pickup phone in your group) *67# disable caller id *70# no call waiting *78# do not disturb on *79# do not disturb off *72# enable call forwarding *73# disable call forwarding *82# enable callerid Personally, I'm not in favor of seeing any of these features find their way into the channels, Zap, SIP, or otherwise. This should all be done at the dialplan level, and not at the "invisible" level of the channel driver. I created a large list of features, which implement almost all of the standard CLASS featureset, but all the logic is in the dialplan, and not in the phones or channels. Even call pickup and flash should be handled in the dialplan for Zap drivers, through applications, IMHO. See the bug report/feature request on this topic: http://bugs.digium.com/bug_view_page.php?bug_id=071 JT ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] *78 *72 and sip?
I agree they should stay at the dialplan level. bkw On Mon, 8 Sep 2003, John Todd wrote: > >I know *8 kind of works with SIP > >but what about the rest should they work > >do they work with a zap device? > >*0# sends flash > >*8# remote call pickup (pickup phone in your group) > >*67# disable caller id > >*70# no call waiting > >*78# do not disturb on > >*79# do not disturb off > >*72# enable call forwarding > >*73# disable call forwarding > >*82# enable callerid > > Personally, I'm not in favor of seeing any of these features find > their way into the channels, Zap, SIP, or otherwise. This should all > be done at the dialplan level, and not at the "invisible" level of > the channel driver. > > I created a large list of features, which implement almost all of the > standard CLASS featureset, but all the logic is in the dialplan, and > not in the phones or channels. Even call pickup and flash should be > handled in the dialplan for Zap drivers, through applications, IMHO. > > See the bug report/feature request on this topic: > http://bugs.digium.com/bug_view_page.php?bug_id=071 > > JT > > > ___ > Asterisk-Users mailing list > [EMAIL PROTECTED] > http://lists.digium.com/mailman/listinfo/asterisk-users > ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] *78 *72 and sip?
On Monday 08 September 2003 01:56 pm, Brian West wrote: > I agree they should stay at the dialplan level. It's not a matter of staying; it's a matter of moving. Those features are already present within the chan_zap channel driver. -Tilghman ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] *78 *72 and sip?
HAHA I haven't used zap channels so I wasn't aware they existed there! :P bkw On Mon, 8 Sep 2003, Tilghman Lesher wrote: > On Monday 08 September 2003 01:56 pm, Brian West wrote: > > I agree they should stay at the dialplan level. > > It's not a matter of staying; it's a matter of moving. Those > features are already present within the chan_zap channel > driver. > > -Tilghman > > ___ > Asterisk-Users mailing list > [EMAIL PROTECTED] > http://lists.digium.com/mailman/listinfo/asterisk-users > ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] *78 *72 and sip?
I agree the * functions should be selectable and doing this at the dial plan level seems a good place to put them. Having not look at the code. I don't know how hard this will be. Digium wants $150 an hour for contract work, I wonder if Mark could give me a quote on adding these features either to the sip channel drive or to the dial plan? I would need a good ball park figure to get a PO cut. If anyone thinks they can do this work in a timely manner I would not mind a quote from you as well. (Wish I had the time to do it myself. Would be a good way to get my head around this code base.) Brian West wrote: I agree they should stay at the dialplan level. bkw On Mon, 8 Sep 2003, John Todd wrote: I know *8 kind of works with SIP but what about the rest should they work do they work with a zap device? *0# sends flash *8# remote call pickup (pickup phone in your group) *67# disable caller id *70# no call waiting *78# do not disturb on *79# do not disturb off *72# enable call forwarding *73# disable call forwarding *82# enable callerid Personally, I'm not in favor of seeing any of these features find their way into the channels, Zap, SIP, or otherwise. This should all be done at the dialplan level, and not at the "invisible" level of the channel driver. I created a large list of features, which implement almost all of the standard CLASS featureset, but all the logic is in the dialplan, and not in the phones or channels. Even call pickup and flash should be handled in the dialplan for Zap drivers, through applications, IMHO. See the bug report/feature request on this topic: http://bugs.digium.com/bug_view_page.php?bug_id=071 JT ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] *78 *72 and sip?
How hard do you think it would be? Tilghman Lesher wrote: On Monday 08 September 2003 01:56 pm, Brian West wrote: I agree they should stay at the dialplan level. It's not a matter of staying; it's a matter of moving. Those features are already present within the chan_zap channel driver. -Tilghman ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] *78 *72 and sip?
On Monday 08 September 2003 02:15 pm, James Sizemore wrote: > How hard do you think it would be? It's not difficult at all. While most of the functionality must stay within the channel driver (and implemented in each channel driver, as needed), you could easily move the trigger code into a registered application. -Tilghman ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users