[Asterisk-Dev] Windows

[list at asd-group.com]

I just have, on your suggestion, and it looks interesting. The integration
you talk of is exactly what I wanted to achieve but with Exchange 2003,
which in turn works well with (also very automated) Outlook 2003 clients.

By choosing a TDM board instead of a TAPI-based one, I didn't want to start
a cascade effect that will change every single bit of software currently in
use, on servers and clients!!

For now, I will port the drivers to Win32 as and when I can, and run a
reduced Asterisk on the Exchange 2003 box (with which it will be
integrated). I think this will work well as a system even on an Epia 1ghz,
just like Asterisk & Opengroupware would under Linux. Further down the
track, this *will* all go Linux, but not just yet.

Overtime and buying more hardware is not an option unfortunately - on
long-term sick leave at the moment and am using this to occupy my time and
*avoid* spending more cash!! :-)

-----Original Message-----
From: asterisk-dev-bounces at lists.digium.com
[mailto:asterisk-dev-bounces at lists.digium.com] On Behalf Of Daniel Pocock
Sent: Tuesday, 21 September 2004 6:07 PM
To: Asterisk Developers Mailing List
Subject: Re: [Asterisk-Dev] Windows



If that's all you are worried about, why not look at 
http://www.opengroupware.org ?

You could run that and Asterisk on the same box with Linux, maybe there 
is even some scope for integration between the two products?  Surely 
time spent on such integration would only give you more features and be 
more worthwhile than time spent porting Asterisk drivers to Windows.

If you really don't want an extra box, why not consider hosting your 
Asterisk with someone in a data center, possibly using a shared server?  
All your incoming and outgoing traffic will have to be IAX or SIP, but 
there are many quality providers to choose from now.

list at asd-group.com wrote:

>Thanks but it's nothing to do with GUI's. Unless MS releases a version of
>Exchange 2003 server that runs on Linux, this box will continue to be a
>WS2003 box, which means that I'll need WIN32 drivers for the TDM. Using a
>second box isn't an option at this time.
>
>I haven't heard of Trojans being transmitted by DTMF yet - but I guess its
>just a matter of time 8-)
>
>-----Original Message-----
>From: asterisk-dev-bounces at lists.digium.com
>[mailto:asterisk-dev-bounces at lists.digium.com] On Behalf Of Kevin Walsh
>Sent: Tuesday, 21 September 2004 4:42 PM
>To: Asterisk Developers Mailing List
>Subject: RE: [Asterisk-Dev] Windows
>
>list at asd-group.com wrote:
>  
>
>>(Article auto-converted from unnecessary HTML to nice plain text.)
>>
>>Sorry for swearing, but has anyone on this list done (or is now doing)
>>anything on Windows with the Digium TDM card or Asterix generally? 
>>
>>Also would anyone be interested in helping port the TDM drivers/DSP code
>>to Windows? 
>>
>>    
>>
>Are you looking to bring the security and reliability, that the MS
>Windows platform is known for, to your PBX?  I wouldn't bother.
>There's no need for a GUI on an Asterisk server, and your system will
>run a lot more efficiently on a dedicated, bare minimum GNU/Linux
>server.
>
>If you really can't live without a GUI then it would be better to
>create one that can connect to your Asterisk server via its management
>interface.  I think you'll find a few of those, if you look around.
>The ones released under the GPL (if any) may be worth taking a look at,
>if you need that sort of thing.  I wouldn't even bother to download the
>proprietary ones.
>
>  
>
_______________________________________________
Asterisk-Dev mailing list
Asterisk-Dev at lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-dev
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev