Review of Atcom AG-188N IAX+SIP ATA (VoIP adapter) – Part 5 – Networking and Internal Router

...

Review of Atcom AG-188N IAX+SIP ATA (VoIP adapter) – Part 4 – Setting up SIP, and securing the adapter

Note: This review was originally posted on the Michigan Telephone, VoIP and Broadband blog After yesterday’s installment we had pretty much configured the VoIP side of the Atcom AG-188N (sold in North America by CIGear) using the IAX protocol. Of course, even though IAX is the superior protocol for getting audio through difficult firewalls, there are still many reasons someone might need to use SIP —...

Review of Atcom AG-188N IAX+SIP ATA (VoIP adapter) – Part 3 – Setting the time and configuring outbound dialing

Note: This review was originally posted on the Michigan Telephone, VoIP and Broadband blog In yesterday’s installment of this review of the Atcom AG-188N (sold in North America by CIGear), I had mentioned that you could download the documentation from the manufacturer’s web site in .PDF format. Since then I have come to realize that the .doc files on the CD are actually a bit more complete – some...

Review of Atcom AG-188N IAX+SIP ATA (VoIP adapter) – Part 2 – Initial setup using IAX

Note: This review was originally posted on the Michigan Telephone, VoIP and Broadband blog In yesterday’s installment I explained why, in some cases, IAX is the superior protocol to use for VoIP calls. Of course, having a superior protocol doesn’t count for much if the calls don’t sound good. So, my first goal with the AG-188N (sold in North America by CIGear) was to try and get it up and running...

Review of Atcom AG-188N IAX+SIP ATA (VoIP adapter) – Part 1 – The unboxing

Note: This review was originally posted on the Michigan Telephone, VoIP and Broadband blog One of the problems often encountered with VoIP is the use of the SIP protocol, specifically when used between a VoIP adapter such as the venerable Linksys PAP2 (or something similar) and an Asterisk server. Everything works great until you try to deploy an adapter at a remote location and the user has some kind of funky NAT...