Posted: Tue Jan 13, 2004 8:18 am Post subject: [Asterisk-doc] capi-application reference
hello to everyone,
this night i wrote a first CAPI application reference in docbook. Now the question is
whether to put it into the normal application reference or to make a
subsection for each channeltype-independent apps. Any suggestions would be
great.
<para>
Forwards an unanswered call to another party (does not rely on sservice
CD).
It only works if the call is unanswered.
</para>
<para>
<informalexample>
<programlisting>
exten=>s,1,Wait(1)
exten=>s,2,capiCD(5551234)
</programlisting>
</informalexample>
</para>
<formalpara>
<title>capiHOLD : Put the call on HOLD</title>
<para>
<function>capiHOLD()</function>
</para>
</formalpara>
<para>
Puts an answered call on hold. This has nothing to do with asterisk's MOH
It depends on which HOLD your telephony provider gives you. Never use the
Wait application after capiHOLD. But it is possible to use the capiECT
function to transfer the call to another party.
</para>
<para>
<informalexample>
<programlisting>
exten=>s,1,capiHOLD
</programlisting>
</informalexample>
</para>
<para>
Transfer a HOLDED call to another party using FromMSN as the
callerid/outgoing msn. This application is able to tell you on the phone which MSN is
calling you (SayCallerID) rsp. which was called (SayCalledID).
</para>
<para>
<informalexample>
<programlisting>
exten => 1,1,Answer
exten => 1,2,capiHOLD
exten => 1,3,capiECT,555123:123555|SayCallerID
</programlisting>
</informalexample>
</para>
Posted: Tue Jan 13, 2004 3:39 pm Post subject: [Asterisk-doc] capi-application reference
On Tue, 2004-01-13 at 01:18, Daniel Heinzen wrote:
Quote:
this night i wrote a first CAPI application reference in docbook. Now the question is
whether to put it into the normal application reference or to make a
subsection for each channeltype-independent apps. Any suggestions would be
great.
Thanks! I know absolutely nothing about CAPI, so I'm not sure either
where we should put this. Does someone with more brains than me want to
tell me where to put this, and I'll take care of adding it to the book?
Posted: Tue Jan 13, 2004 10:38 pm Post subject: [Asterisk-doc] capi-application reference
On Tue, 2004-01-13 at 11:15, Olle E. Johansson wrote:
Quote:
Jared,
CAPI is a channel just like the rest of them, the only difference is that it's
not part of the standard distribution.
I realize that.
Quote:
I would suggest that channel specific CLI commands and applications are documented
for each channel.
Sounds good. If I don't hear any more opinions, I'll make an appendix
called "Channel Specific CLI Commands" and one called "Channel Specific
Applications", and they we'll have a good place to put this stuff.
Posted: Wed Jan 14, 2004 5:35 am Post subject: [Asterisk-doc] capi-application reference
On Tue, 2004-01-13 at 16:38, Jared Smith wrote:
Quote:
On Tue, 2004-01-13 at 11:15, Olle E. Johansson wrote:
> Jared,
> CAPI is a channel just like the rest of them, the only difference is that it's
> not part of the standard distribution.
>
I realize that.
> I would suggest that channel specific CLI commands and applications are documented
> for each channel.
Sounds good. If I don't hear any more opinions, I'll make an appendix
called "Channel Specific CLI Commands" and one called "Channel Specific
Applications", and they we'll have a good place to put this stuff.
How many apps are channel specific? ZapRas, and ???
--
Steven Critchfield <critch@basesys.com>
Posted: Wed Jan 14, 2004 3:00 pm Post subject: [Asterisk-doc] capi-application reference
Hi!
Quote:
> I would suggest that channel specific CLI commands and applications are documented
> for each channel.
Sounds good. If I don't hear any more opinions, I'll make an appendix
called "Channel Specific CLI Commands" and one called "Channel Specific
Applications", and they we'll have a good place to put this stuff.
I am not 100% sure this is a good idea - as a result info about
applications will be scattered all over the place, making them hard to
find. This would e.g. also apply to ZapBarge, IsChanAvailable etc.
And then how do you treat cases for applications that are applicable to,
say, 3 channels and not just 1, do you repeat this everywhere then (not
sure if I can find a real-world example for this, though)?
Really, I don't know which way to go here, hard to decide...
Posted: Wed Jan 14, 2004 5:05 pm Post subject: [Asterisk-doc] capi-application reference
Philipp von Klitzing wrote:
Quote:
Hi!
>>I would suggest that channel specific CLI commands and applications are documented
>>for each channel.
>
>Sounds good. If I don't hear any more opinions, I'll make an appendix
>called "Channel Specific CLI Commands" and one called "Channel Specific
>Applications", and they we'll have a good place to put this stuff.
I am not 100% sure this is a good idea - as a result info about
applications will be scattered all over the place, making them hard to
find. This would e.g. also apply to ZapBarge, IsChanAvailable etc.
And then how do you treat cases for applications that are applicable to,
say, 3 channels and not just 1, do you repeat this everywhere then (not
sure if I can find a real-world example for this, though)?
Really, I don't know which way to go here, hard to decide...
That's why I like the Wiki, we can easily cross-reference :-)
To turn around, I agree with Philipp. But I would propose not mixing the
CAPI commands and other non-asterisk.org channels with what's included in
the "official release".
I think it is important to cover what works where. If an application only
works in three channels, write that down.
Posted: Thu Jan 15, 2004 2:15 pm Post subject: [Asterisk-doc] capi-application reference
On Wed, 2004-01-14 at 10:05, Olle E. Johansson wrote:
Quote:
That's why I like the Wiki, we can easily cross-reference :-)
We can and will be adding cross-references to the book, but you are
absolutely right... it's easier to do with the Wiki.
Quote:
To turn around, I agree with Philipp. But I would propose not mixing the
CAPI commands and other non-asterisk.org channels with what's included in
the "official release".
I think it is important to cover what works where. If an application only
works in three channels, write that down.
Yes, we should be absolutely clear that these applications only work on
certain channels... Here's another idea... what if we put these
channel-specific applications in a section at the end of that Appendix
called "Channel Specific Applications", and then put a cross-reference
in the main list of applications, so that people can still find them
alphabetically... Does this strike the right balance between ease of
reference and making it clear that they are channel-specific?
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum