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: "Paul Gale" <groups@xxxxxxxxxxxxxxxx>
  • Date: Wed, 24 Aug 2005 20:50:26 +0100

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?
>=20
> Paul Gale wrote:
> > Anyone got any updates on the xAP Asterisk connector?
>=20
> 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.
>=20
> 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:
>=20
> xap-header
> {
>    v=3D12
>    hop=3D1
>    uid=3DFFCD2F01
>    class=3DxAPBSC.event
>    source=3Dacme.asterisk.myhouse:mwi.01
>    target=3D*
> }
> output.state
> {
>    state=3Don
>    text=3D1/3
> }
>=20
> 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.
>=20
> 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.
>=20
> Sound ok?  Does anyone know of a schema that could better deal support
> MWI-like functionality?
>=20
> 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.
>=20
> Gregg
>=20
>=20
>=20
>=20
> Yahoo! Groups Links
>=20
>=20
>=20
>=20
>=20




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.