RE: SB Error + VOIP routing

["Paul Gale" <groups2@xxxxxxxxxxxxxxxx>]

Thanks Gregg - sorry - should have been clearer, I've been using SB
from the early days and rate it very highly :) The Asterisk integration is
what interests me now :)

Re Asterisk - well, it's more than just and answering machine I want - the
ability to get emailed messages and call routing via the menus are great
too plus I'd really like to develop an IVR system too that links into the
HA systems and alarm (not sure where to start with that one though). I have
HS and other apps linked to HomeVision and Comfort etc...

Paul.

> -----Original Message-----
> From: xap_automation@xxxxxxx
> [mailto:xap_automation@xxxxxxx] On
Behalf Of Gregg Liming
> Sent: 09 February 2007 11:44
> To: xap_automation@xxxxxxx
> Subject: Re: [xap_automation] SB Error + VOIP routing
>
> Hi Paul,
>
> Quoting Paul Gale (2/9/07 4:32 AM):
>
> > Not having followed this thread before - what will Asterisk and
SB
> > allow you to do? i.e. what functionality?
>
> There isn't really any new capability that exists--rather, axc and SB
> now fully/properly work together.  From a pure functionality
> stand-point, SB provides considerable abilities in the areas of CID
> lookups, logging and dialing.
>
> When I first wrote axc, I was relying on mh rather than SB.  After
> finally understanding what SB can do (the jabber conduit / Four combo
> was the "icing" on the cake), I've since shifted from mh's
telephony
> support to SB.  It's really hard to fully appreciate just how good SB
> is
> unless you've used something that is lacking/marginal before.
>
> > I need to get my Asterisk box going again - I was using Asterisk
@
> > Home - should I try that again or do a native Asterisk install?
>
> From a technical standpoint, it shouldn't matter.  I personally only
> use
> native * (both personally and for work) and likely won't consider AAH.
> As a result, there are things that AAH does and/or terminology used
> that
> I am unfamiliar with.  However, I believe that there have been other
> AAH
> users that have been able to config axc based upon their setup.
>
> > I have
> > an SPA3000 and really wanted to use Asterisk as a glorified
answer
> > machine and longer term get into VOIP.
>
> If it's only an answering service that you're wanting, axc and SB are
> overkill; for that matter, so is * (IMO).
>
> > Asterisk was such a steep
> > learning curve :(
>
> I can agree with that.  In my opinion, that learning curve is
> worthwhile
> only if you fully leverage what * can do and that you need PBX-like
> functionality.
>
> FWIW: I still use a netcallerid box tied to mh that separately feeds
> CID
> info to SB.  I use it because it properly handles call-waiting CID
data
> on PSTN whereas * does not.  If I lived in a PSTN-only world, I'd
never
> use *.
>
> Gregg
>
>
>
> Yahoo! Groups Links
>
>
>