By xAP Manager on 27 June 2010 23:34:23

I started to create a TapiRex notification plugin to generate a xAP CID.Incomming message when a new call was received.

I currently use TapiRex on my NodeZero to repsond to new calls (PSTN and VoIP). This is achieved by use of the ActiveTSP TAPI driver to access my Asterisk (PBX in a flash) PBX. This provides me with call notifications and log on my MediaCenter PC.

I wanted to also provide a xAP message with the caller details as each call comes in.

I downloaded the TapiRex SDK and modified the DotNetSamplePlugin to use the xFx V2 library.

I firstly had problems getting xFx to find the xFx.dll.config file. Through the use of the SysInternals ProcessMonitor I was able to discover that I needed to put xfx.dll and xfx.dll.config in the same folder as TapiRex (in my case p:\programe files\tapirex).

I built and tested this on my development PC (Windows 7 & VS2008). When I deployed this to my NodeZero, TapiRex didn't find my plugin. I then discovered that the NotificationPlugins registry...

Read More »

By xAP Manager on 01 May 2007 00:08:26

As a consequence of developing the MCEVMail application I spun off this gateway to provide a simple gateway between Asterisk Voice Mail and xAP.

The gateway currently relies on AXC CTI2Info xAP messages to trigger the message sending. When an axc message arrives the gateway checks to see if the associated mailbox is in the gateway watch list (XML file). If it is then a xAP multi body message is sent that lists the folders within that mailbox and the number of messages in each folder. A subsequent multibody xAP messages are sent for each folder listing details of the messages (callerid, duration, URL to audio, ....) . The URL provides http audio header and audio stream (Content-Type: audio/wav).

Full details of the xAP message schema for xAPVMail can be found here

I am adding some simple commands to the gateway. Currently, Status.Request is supported for a MailBox folder and/or message. I will also add a polling interval to enable triggering for...

Read More »

By Media Centre on 30 April 2007 19:26

Progress on Vista MCE to date

Read More »

By Asterisk Man on 07 February 2007 20:05

I bit the bullet and plugged my TDM400P back into my BT PSTN line and lo & behold no echo at all. So it would appear the version of Zaptel in Trixbox 2.0 beta is fixed. I still have random success with calling line ID (CLID) being presented, even though my DECT handsets have no problem displaying it!

By Media Centre on 28 January 2007 17:14

A short summary of the configuration being used at NodeZero

Read More »

By Asterisk Man on 31 December 2006 09:04

Settings that I have been using for SIP and IAX Trunks with VoIPTalk.org

Read More »

By Asterisk Man on 31 December 2006 09:00

First, none of this is anything to due with problems with the TrixBox product. It has taken me many days to get my VoIP PSTN service back up and going and I will share my story here. All the issues relate to changing many things all at once. Are you sitting comfortably......?

Some  weeks ago my SIP VoIP call quality went really bad; echo, call break up and one-way audio. At the same time I was experiencing internet performance problems so I put it down to that. Later it transpired that a full factory reset of my ADSL router was required. So I reverted back to my Zpatel TDM400P to bridge my Asterisk server to my PSTN line. Since moving to VoIP I had stopped publishing this number as I have always had poor echo issues with the TDM400P and unreliable Calling Line ID (CLID). After many days and many configurations I was unable to fix the echo, in fact it got a lot worse! Now my Wife was very displeased and so I shutdown my TrixBox server and reverted to a DECT regular phone.

Not being one to give up...

Read More »

By Darren Lock on 08 November 2006 04:32

Logical Concept Diagram for DarrensGarage

Read More »

By Darren Lock on 06 November 2006 02:25

I have added RSS feeds for the Yahoo xAP Automation and xAP Developer groups see the xAP page for more details

By HomeSeer Manager on 05 November 2006 21:31

I finally decided to bite the bullet and go with V2 of HomeSeer as my primary automation controller. This was largely due to its maturity, stability, performance & importantly its range of plugins and support from others. Notably, James' xAP HomeSeer conduitMainLobby bridge.

HomeSeer has very good latency with respect to responding to X10 commands received via CM12 and issuing an immediate command back out on the power again. Also, combined with the HomeSeer W80032RF plugin I now find X10 device response to a RF wall switch or motion detector far more acceptable.

The only decision I have to make going forward now is whether to develop HomeSeer plugins to plug my gaps or continue developing xAPplications . I prefer the latter as once stable, I can share these with the xAP community irrespective of  whether they are using HS or not.

...

Read More »