The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

Re: Update on xAP Asterisk?


  • Subject: Re: Update on xAP Asterisk?
  • From: "Christopher" <eldoradoboy@xxxxxxxxx>
  • Date: Thu, 15 Sep 2005 20:05:29 -0000

I too am interested in XAP enabling my asterisk PBX. I currently run
a Homeseer 1.7 setup with the XAP connector, im looking to be able
to control homeseer devices, execute homeseer scripts etc via Auto
attendants or extensions on my asterisk PBX. I thought that someone
by the name of patrick lidstone had asterisk fully xap enabled.. did
he not release his code or programs to the public? is this project
abandoned on his end? or is gregg's project another to operate as
well, i am available for any testing like im sure many others are. I
started with asterisk@home but have pretty much abandoned editing my
configs with AMP due to the limited functionality and so im pretty
much using it now as a regular distro and manually edit my configs.
-Christopher
--- In xap_automation@xxxxxxx, "Paul Gale" <groups@s...>
wrote:
> Hi Gregg,
>
> Thanks for that - yes, the message waiting was a high priority for
me.
>
> I'll look forward to your work on this.
>
> Paul.
>
> > -----Original Message-----
> > From: xap_automation@xxxxxxx
> > [mailto:xap_automation@xxxxxxx] On
Behalf Of Gregg Liming
> > Sent: 24 August 2005 19:37
> > To: xap_automation@xxxxxxx
> > Subject: Re: [xap_automation] Update on xAP Asterisk?
> >
> > Paul Gale wrote:
> > > Anyone got any updates on the xAP Asterisk connector?
> >
> > The work that I had started was put on "hold" while I
finished
BSC
> > support for misterhouse.  That's wrapping up this week; so, I'll
restart
> > working on the asterisk connector again.
> >
> > As I recall, you were most interested in some sort of MWI-like
(message
> > waiting indicator) capability--right?  If so, I'm unaware of any
> > applicable ways that the telephony schema supports this; so, I'm
> > somewhat thinking of using BSC to report number of messages via
the text
> > field.  If I can get both "new" (i.e., unheard) and
"old" message
> > counts, then I'm thinking of something like the following:
> >
> > xap-header
> > {
> >    v=12
> >    hop=1
> >    uid=FFCD2F01
> >    class=xAPBSC.event
> >    source=acme.asterisk.myhouse:mwi.01
> >    target=*
> > }
> > output.state
> > {
> >    state=on
> >    text=1/3
> > }
> >
> > So, the subaddress has a group of "mwi" (to permit
queries of all
> > possible voicemail boxes) and an endpoint of the asterisk mailbox
> > number.  The text value is delimitted with a slash.  The first
part is
> > the number of unheard messages and the last part is the number
of old
> > messages.  I'm also thinking that as soon as the number of
unheard
> > messages drops to 0, then the state is set as off.
> >
> > I'm almost positive that the information from * manager
interface has to
> > be polled (i.e., there is no "new message waiting"
event).  If
that's
> > the case, then I'd probably set the polling interval consistent
w/ the
> > heartbeat--every 60 seconds.  The application would maintain
internal
> > track of the new & old messages to determine when to send out
an
event.
> >
> > Sound ok?  Does anyone know of a schema that could better deal
support
> > MWI-like functionality?
> >
> > Also, I somewhat picked BSC for this as I don't know of any
current
> > application support for MWI and assumed that you might want to
use
> > something that can generically process BSC events (e.g., xAP
Desktop).
> > Let me know if you have something else in mind.
> >
> > Gregg
> >
> >
> >
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
> >







xAP_Automation Main Index | xAP_Automation Thread Index | xAP_Automation Home | Archives Home

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.