Oct 21 2009

Aastra releases RP to SIP conversion firmware for Aastralink RP phones

Category: 3CX, Asterisk, Response Pointkashan @ 5:21 pm

Aastra released an RP to SIP conversion firmware today. This is designed to help customers of AastraLink RP phones to re-use their existing phones with standard SIP based phone systems and soft switches.

The Aastralink RP phones were originally designed to work only with Microsoft Response Point phone systems including the Aastralink Pro RP system. Since the fate of Response Point is up in the air with Microsoft’s plans for further development on hold, some customers are looking for alternate solutions in case they outgrow RP or in case Microsoft decides to pull the plug on it.

This conversion release provides some investment protection for AastraLink RP customers since it helps simplify the upgrade path by preserving the customer’s investment in phones. This release will change the firmware in the Response Point phone to that of an Aastra standards-based SIP phone – allowing it to be used with standard based SIP PBXs such as the Aastralink Pro 160, 3CX, pbxnsip, Trixbox and hosted soft-switches, such as Asterisk, MetaSwitch and BroadSoft. The conversion process is easily accomplished through the phone’s Web UI, requiring only a TFTP server and the firmware downloaded from our website.

The new conversion firmware can be downloaded here.

Tags: , , , , , , , , , , , , , , , ,


Jun 05 2009

Review of Atcom AG-188N IAX+SIP ATA (VoIP adapter) – Part 7 – Addendum

Category: Asterisk, General, Networkingmichigantelephone @ 10:11 pm

Note: This review was originally posted on the Michigan Telephone, VoIP and Broadband blog

Although I have technically finished up the series on the Atcom AG-188N (sold in North America by CIGear), I wanted to open a post to answer any questions or comments that may arise.

One thing that came up in another thread was that I didn’t say much about how the AG-188N unit can be remotely provisioned by a service provider. That’s because I was primarily writing the review from the end user’s point of view. I’m not a provider, and I guess I assumed that any provider that would be purchasing these units in quantity would be talking to the manufacturer or the distributor with questions about provisioning. I can tell you that there is a page explicitly for setting up provisioning, which looks like this:

Atcom AG-188N Auto Provisioning Configuration screen

Atcom AG-188N Auto Provisioning Configuration screen

Here’s what the fields contain:

  • Current Version — the current version number is displayed
  • Server Address — FTP/TFTP server address
  • Username — FTP server user name
  • Password — FTP server password
  • Config File Name — The name of configuration file
  • Config Encrypt Key — The encrypt key of configuration file
  • Protocol Type — The protocol type used for upgrading — choices are FTP, TFTP, or HTTP
  • Update Interval Time — The AG-188N will check for a new configuration file at the specified interval
  • Update Mode — auto provision mode — choices are:
    • Disable — Will not auto-update
    • Update after reboot — Will auto update after a reboot
    • Update at time interval — Will auto update at the specified interval

The normal way you’d use this is that you’d first create a “master” settings file by making a backup of the settings from one AG-188N that has been configured the way you want it (that is, with whatever “default” settings you want all users to have). You’d use “Backup Config” to save this as a plain text file. You can then open this file in any plain text editor (but use one that preserves the existing line endings, or you may have issues when you attempt to re-upload it). Note the first line of the default file contains this line:

<<VOIP CONFIG FILE>>Version:2.0001

When you change the configuration file, you should bump the version number — presumably that’s how the unit would know there’s a new version. Then, for each unit, you’d customize the file (changing the values that are unique to each extension), and then save the file to your server with a unique filename and the .cfg extension. For example, if you had an extension 200, you might name the edited file 200.cfg, and make sure that filename also is placed in the “Config File Name” field in the configuration file itself. You could upload the customized configuration file to the device the first time by using the Web Update page on the AG-188, or if the unit had already been sent to a customer site, you could send them an e-mail with the settings to enter on the above page.

The question was asked, is there a nice configuration tool such as is supplied for some other adapters? Not to my knowledge, but if you look at the actual format of a configuration file, you’ll realize how easy it would be for any competent programmer to create such a tool. As an example, here’s a sample IAX2 configuration section from the file:

<IAX2 CONFIG MODULE>
Server   Address   :myserver.dyndns.com
Server   Port      :4569
User     Name      :200
User     Password  :securepassword
User     Number    :200
Voice    Number    :
Voice    Text      :
EchoTest Number    :
EchoTest Text      :
Local    Port      :4569
Enable   Register  :1
Refresh  Time      :60
Enable   G.729     :0

All you would need to do is do a search-and-replace on each line in the file — find the values that need to be unique for each extension and then change them. You could do this using a Bash or Perl or PHP script, or probably any of a number of other scripting languages (you could even do it in BASIC, if that’s the language you’re most comfortable using). Or you could get fancy and build a database of settings for each extension, allowing you to change values globally (for example, if changing a server name) or for one extension or a group of extensions. If you do that, and you don’t mind sharing it, please post a link in the comments, because I’m sure there would probably be others who would appreciate such a tool.

I know someone will ask, “How do I use the Config Encrypt Key?” And my answer to that is, doggone if I know, but if encrypting the file is that important to you, you’re probably going to be buying in sufficient quantity that you will be talking directly with the distributor and/or the manufacturer, so ask them. As I said, I wrote this series primarily for end users, and while some end users may want to be able to auto-provision their devices (and there is even some talk of a provisioning tool or module possibly coming in a future version of FreePBX), there are few that would actually need the configuration file to be encrypted, provided that all users are internal and that your FTP or TFTP server (the one used to serve configuration files) is not accessible from the Internet.

Of course, if you have remote users, then you may be concerned about having them FTP or TFTP a plain text configuration file that shows their SIP and/or IAX user name(s) and password(s) with no encryption whatsoever — and if you are not concerned, you probably should be! For those users, I think I’d at least compress the file with a password (using ZIP or some other format that allows password protection of files), then e-mail the compressed file to the customer, and then use some other medium (such as phone or fax) to get the file password to them. They can then uncompress the file, and use the Web Update page on the AG-188N to get the .cfg file into their AG-188N. I realize that’s not very convenient, so if I ever find out how the Config Encrypt Key is implemented, I’ll definitely edit this post to show the information.

Setting up a dial prefix for local calls

Reader Bill asked the following:

I have a couple of the 188N and been trying to get it to prefix 1916 my provider requires all local calls to have a the prefix of your area code to dial local numbers. So far I am failing in how to get this to work.

Can someone point me in the right direction?

Actually, it’s easy, but slightly non-intuitive. In the left-hand menu click on Dial-Peer - again, I know it looks like it’s not a clickable link, but it is. That will bring up the Dial-Peer page, as shown in Part 3 of this series. Now, click the Add button, and you should see this dialog:

Add rule

Atcom AG-188N Dial-Peer screen: Add rule

You need only fill in the three fields shown here. The Phone Number field contains the pattern for a seven digit call — [2-9]xxxxxx (don’t add a trailing T in this case because you want it to match only if exactly seven digits are dialed). The Call Mode should match the mode you normally use for outgoing calls - I used IAX2 in this example but if you normally use SIP then select that. In the Alias field, I entered the modification that Bill wants to make to seven-digit numbers — add:1916 to add the leading 1 plus 916 area code. Enter those values, click Submit, then click on Save Config and you should be all set.

There are actually four different keywords you can use at the start of an alias:

add: As shown here, add is used to add a prefix to the phone number, so (as in this example) you don’t have to dial leading prefix digits on local calls.
all: Replaces the number dialed with the number following the all keyword - this is how you can make a speed dial code.
del: Deletes the first N numbers. N is set in the Delete Length field.
rep: Replaces the first N numbers. N is set in the Delete Length field. Typical example: You’re in a country where the international dialing prefix code is 011 but you are using a carrier that expects you to send 00, followed by country code and number. In the Phone Number field you’d put 011T, then in the Alias field you’d put rep:00, and set the Delete Length to 3. Whenever a user dials a number starting with 011, it will then be changed to 00.

The use of the Dial-Peer page is explained more fully in the AG-188N manual, in the section How to use the dial rule? near the back of the manual.

As I said, this post is intended to be open-ended, in case any other questions or comments about the AG-188N require a response. So if you are interested in this device, you might want to check back from time to time, to see if anything else has been posted.

Disclosure: CIGear provided me with an Atcom AG-188N for review purposes, and allowed me to keep it after I was finished writing this series, and for that I am most grateful.

Previous Installment

Articles in the series: Review of Atcom AG-188N IAX+SIP ATA (VoIP adapter)

Part 1 – The unboxing
Part 2 – Initial setup using IAX
Part 3 – Setting the time and configuring outbound dialing
Part 4 – Setting up SIP, and securing the adapter
Part 5 – Networking and Internal Router
Part 6 – Final Thoughts and Summary Review
Part 7 – Addendum


Jun 03 2009

Review of Atcom AG-188N IAX+SIP ATA (VoIP adapter) – Part 6 - Final Thoughts and Summary Review

Category: Asterisk, General, Networkingmichigantelephone @ 1:07 pm

Note: This review was originally posted on the Michigan Telephone, VoIP and Broadband blog

In yesterday’s installment of this series we discussed the internal router and other networing capabilities of the Atcom AG-188N (sold in North America by CIGear). The one thing that had me a bit puzzled was the implementation of VPN Tunneling. I’ve since been informed that the UDP method of VPN tunneling was implemented for a specific customer, and only works with that customer’s servers. However, the LT2P method does use standard L2TP, but without IPSec, which means it’s not a secure tunnel (there is no encryption used by default with L2TP). The most likely reason for using an L2TP tunnel would be to overcome NAT firewall issues, if for some reason you can’t use the IAX protocol and must use SIP instead. I’ve since added some information to yesterday’s article that includes a link to a blog post that shows how to setup an L2TP server on a Linux box. I’d still be interested in hearing from anyone that actually gets this working, since I haven’t really had the time to experiment with it yet.

Anyway, here are my final thoughts on this unit:

Let me state at the outset: I’m highly impressed with the AG-188N. Please keep that in mind as you read the paragraphs below, because reviews often tend to focus on areas where a product does not meet the reviewer’s expectations. In the case of the AG-188N, my expectations were met and for the most part, far exceeded. The one area where that was not the case was the documentation, and I’ll talk about that in a moment. But in my testing, this unit performed at least as well as any other VoIP adapter I’ve used, and I actually perceived the audio quality to be better than what I hear when using the venerable Linksys/Sipura adapters.

Atcom AG-188N

Atcom AG-188N

The Atcom AG-188N is a solid, well-built unit in an attractive charcoal-grey case. It’s very similar in size to the popular Linksys PAP2, and could be a drop-in replacement in any situation where only a single line (phone port) is required. What most impressed me during my testing was that everything I tested worked at it was supposed to, although not always exactly in the same manner as it would on a Linksys adapter (the need to press the star key to complete a 3-way call being one example). The device supports up to two SIP accounts, but in addition it supports one IAX account (something rarely found in a VoIP adapter in this price range), and you can also connect a PSTN line to the PSTN port on the back to use for calls to emergency services, local calls, etc. If a call comes in using any of the supported methods the phone will ring and you can talk, but call waiting does not appear to work “across technologies” (that is, if you’re on an IAX call and a call comes in on one of your SIP accounts, the device will report BUSY rather than giving you the call waiting beeps).

Call quality is excellent, although out of the box the incoming receiver volume was a bit low, but that was easily adjusted in the device’s configuration. I had no problems using this device with an Asterisk/FreePBX server, it worked as expected and was easy to configure (I daresay easier than the Linksys/Sipura adapters I’ve set up in the past). It does not have as many configuration options as the Sipura, but the settings that are missing are for the most part ones you’d probably never change from the defaults anyway. Actually, about the only settings I really wished for that I did not find were the ability to manually tweak certain tones (in particular, the tone that is sent when you leave the accidentally leave phone off the hook — this unit just provides a fast busy signal at roughly normal volume, which isn’t going to alert anyone that the phone is off the hook) but I’m probably the one person in 1,000 that would even care about that.

Honestly, I’m surprised that this unit hasn’t gained greater acceptance among VoIP users and service providers. Probably the greatest drawback of the unit is that many buyers will compare this with the Linksys PAP2 and notice that the PAP2 has two phone ports, while the AG-188N only has one. But on the other hand, the PAP2 does not support the IAX protocol, and does not include a router with DHCP support and a NAT firewall, not to mention QoS and VPN tunneling, if you can figure out how to configure the latter two. The Atcom AG-188N supports all of this, at a very reasonable price.

The documentation that is provided with this unit, to put it charitably, could be much better. No printed documentation is provided at all, but the included mini-CD contains documentation on several Atcom products including the AG-188N. Unfortunately, it’s in .doc format, which may not be readable if you don’t have Microsoft Word (although there are free online services that can convert .doc files to other formats — Zamzar comes to mind, but there are many others). You can go to the manufacturer’s web site to find PDF versions of the documentation, but at least in the case of the AT-188N, that documentation appears to be older than the .doc files on the disk. You may find that reading the previous articles in this series fills in some of the holes in the documentation.

Two specific issues with the documentation are that 1) it was apparently poorly translated from Chinese, with numerous spelling, punctuation, and syntax errors, not to mention being borderline incomprehensible in a few places (although it’s far from the worst translation I’ve ever seen), and 2) It is silent in some places where it should be more explanatory. For example, there’s an entire section of the manual on QoS (Quality-of-Service) configuration, but it’s titled “VLAN implement” (so many users would have difficulty finding it) and worse, it really doesn’t explain which of several possible configurations should be used in any given situation. For example, if you are using VoIP but you also have a computer (or a switch with multiple connected computers or devices) connected to the LAN port, how do you make sure that the VoIP packets get priority? That’s the sort of thing that needs to be explained in clear, easy-to-understand language.

And, there are some settings on which the manual is inexplicably silent. Worse yet, the entire section on VPN gives such sparse information that I sincerely doubt that anyone could figure out how to set up a VPN tunnel without getting additional clarification. It doesn’t help that they picked two of the most obscure VPN methods to support - one that’s used only by a single customer (though they don’t mention that in the manual) and the other an implementation that you rarely see anymore (L2TP with IPSec is somewhat common, though still not nearly as popular as some other methods, L2TP without IPSec much less so, although in a perverse way that may be a blessing in disguise - everything I’ve read about IPSec indicates it’s kind of a bear to install). I’m told that Atcom actually has a working OpenVPN implementation, but that it won’t fit in the flash memory and RAM of the device.

But really, none of this will matter to the typical user - there is a Quick Start Guide on the mini-CD that will be enough to get the average user going (or, you could refer to the previous articles in this series!) using IAX or SIP. Most of the router configuration on the AG-188N is fairly self-evident — if you’ve ever set up a router before, you shouldn’t have any difficulty with the one in this device. The places where things get somewhat complicated tend to be mostly places where typical users would fear to tread anyway.

If I could make a suggestion to Atcom, it would be this — For the next iteration of this device, please consider the following: 1) Enough memory for proper support of additional VPN tunneling methods, including OpenVPN, 2) More than one LAN port on the back of the unit (I know this will make it a bit larger, but you already have the AT-188N for those who need the smaller form factor) - it would be good to have at least four LAN ports, 3) the ability to select whether each individual LAN port is tunneled or not tunneled (when a VPN tunnel is active), 4) AT LEAST two phone ports, preferably four (if for no other reason than to make your device competitive with all the other two-line units), 5) Simpler QoS setup — build some default profiles for various situations, or better yet, let users assign QoS priorities on a per port basis (phone ports would default to high priority, LAN ports to medium priority, but each could be changed by the user with simple “radio button” selection), 6) A “greener” power supply — the “wall wart” you’re supplying with the AT-188N throws off too much waste heat (EDIT: And as noted, the “wall wart” that I received failed after approximately seven months’ continuous use), 7) And PLEASE, get someone who is a native English speaker to write or edit the English version of your manual (using proper grammar, spelling and punctuation!), and make sure you document ALL the settings on EVERY screen.

But even with whatever faults it may have, I think that any buyers of a single-line VoIP adapter (ATA) would be extremely happy with this device. It truly delivers more value than you’d expect for such a low price. When the worst thing you can say about a unit is that the documentation could be improved (and how many other products suffer from the same problem nowadays?), that’s really not much of a criticism.

One other thing that surprises me is that the sort of people who like to hack routers and/or network storage devices, and install rewritten and improved firmware, haven’t discovered this unit. When you consider all the energy that’s been put into modifying the firmware and then developing software packages for a device like the Linksys NSLU2, I’d have to think this device would be at least as attractive for that purpose. Sure, it doesn’t have any USB ports, but it’s a network connected device, which means that potentially it could store anything too large to fit in RAM on a network-attached storage device. Maybe the Atcom folks would not appreciate me mentioning the possibility that the firmware could be improved upon, but since the unit does have telnet access I have to think there’s a good chance it’s running some form of Linux “under the hood” — although I could be wrong about that — and I’m just a little bit shocked that those who enjoy digging into the internals of this type of device haven’t (yet) found the AG-188N attractive.

This is a device that really needs additional exposure among the VoIP community, which is one reason I wanted to review it. Sometimes it’s hard to get “word of mouth” going on a new device, but in my opinion this one deserves it. It’s a great, well-built device in any case, but with the ability to use IAX protocol and to tunnel its SIP connections via L2TP, you have two ways to handle those tough situations where most other adapters will connect to your server, and you can make their phone ring, but you only get one-way audio (or even no-way audio in some cases).

I’m going to close this article, and this series, with the list of features and specifications for this unit, from CIGear’s web site, but with the caveat that they probably got this from the manufacturer and I don’t believe it’s 100% accurate (just one example: Both this list and the AG-188N manual say that “Reverse polarity” is supported. But there’s no setting to turn it on or off, and I can tell you that it doesn’t appear to be on by default). So if a particular feature is really important to you, look back through the the screenshots in the previous articles of this series and if you don’t see that feature mentioned, there’s a chance it might not be implemented. This is just another example of a disconnect between the documentation and the actual unit.

Features

Enterprise, small office and residential applications

Key features:
Support two sip servers running at the same time.
Redundancy sip server support.
Support T.38 fax function
Support IAX2 protocol
NAT, Firewall.
DHCP client and server.
Support PPPoE, (used for ADSL, cable modem connecting).
Support major G7.xxx CODEC.
VAD,CNG.
G.165 compliant 32ms echo cancellation
E.164 dial plan and customized dial rules
Support Lifeline.
Hotline.
Call Forward, Call Transfer, 3-way conference calls
Call ID display
DND(Do Not Disturb),Black List,Limit List
Reverse polarity
Voice prompt
Increase Vlan and automatically upgrade configuration file encryption function
support IAX2 and FAX
Increase the time zone function

Data Features
Static/Dynamic WAN IP Addressing
PPPoE

Management
Web, telnet and keypad management.
Adjustable user password and super password
Upgrade firmware through HTTP, FTP or TFTP.
Telnet remote management.
Upload/download setting file
Auto-provision.
Safe mode provide reliability

Interface
Two RJ45 ports, one for WAN, one LAN.
One RJ11 PSTN port for lifeline
One RJ11 FXS port for analog phone.

Data Networking:

MAC Address
TCP:Transmission Control Protocol
DHCP:Dynamic Host Configuration Protocol
PPPoE:PPP Protocol over Ethernet
SNTP, Simple Network Time Protocol
STUN - Simple Traversal of User Datagram …
MD5 Message-Digest Algorithm
DNS:Domain Name Server
RTP: Real-time Transport Protocol
RTCP:Real-time Control Protocol
Telnet:Internet’s remote login protocol
HTTP:Hyper Text Transfer protocol
FTP:File Transfer protocol
TFTP:Trivial File Transfer Protocol

Call control /voip Features
SIP RFC3261,RFC 2543
Tone generation and Local DTMF re-generation according with ITU-T
G.711(A-law or u-law)
G729
AGC(Auto Gain Control)
G.168/165 compliant 16ms echo cancellation
AEC(Auto Echo Cancellation)
VAD (Voice Activity Detection)
CNG(Comfort Noise Generation

Enviromental

Electric requirements
Voltage: 9V ~ 24V
Power adapter: output DC 12V/450 mA

Operating requirement
Operation temperature: 0 to 40° C ( 32° to 104°F)
Storage temperature: -30° to 65° C (-22° to 149°F)
Humidity: 10 to 90% no dew

Regulatory compliance
CE, FCC part 15

Thank you to the folks at CIGear for their patience in answering my questions as I wrote this series of articles!

Disclosure: CIGear provided me with an Atcom AG-188N for review purposes, and allowed me to keep it after I was finished writing this series, and for that I am most grateful.

Previous Installment | Next Installment

Articles in the series: Review of Atcom AG-188N IAX+SIP ATA (VoIP adapter)

Part 1 – The unboxing
Part 2 – Initial setup using IAX
Part 3 – Setting the time and configuring outbound dialing
Part 4 – Setting up SIP, and securing the adapter
Part 5 – Networking and Internal Router
Part 6 – Final Thoughts and Summary Review
Part 7 – Addendum


Jun 03 2009

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

Category: Asterisk, General, Networkingmichigantelephone @ 1:05 pm

Note: This review was originally posted on the Michigan Telephone, VoIP and Broadband blog

In our previous installment we completed setting up the VoIP portion of the Atcom AG-188N (sold in North America by CIGear), touching on some of the other screens in the process. But there’s a whole other side of this great device that I have avoided touching on until today. If I were a TV infomercial pitchman, this might be the point where I’d take a dramatic pause and say, “You’d think there wouldn’t be anything more that we could pack into this small of a package — but wait, there is more —it’s ALSO a ROUTER!!!” And then the studio audience would applaud on cue!

And when I say router, I mean that it includes a DHCP server, NAT (port forwarding), QoS (Quality of Service), and even some limited VPN (Virtual Private Network) Tunneling support. Now, one reason I’ve sort of avoided talking about this is because of all the things I understand with regard to computing and VoIP, the area where my knowledge is weakest is networking. The whole process of getting packets from point A to point B over the Internet is sort of a “black hole” for me. And I’m not one of those reviewers that tries to convince you that I’m smarter than everybody else, and know everything about everything - if you’ve ever taken even one networking class, you’re probably way ahead of me. So what I’m going to do here is show you the screenshots and tell you what I can, but if I make some wildly inaccurate statement, kindly let me know in the comments, okay?

In Part 2 of this series, I showed you the WAN configuration page. Let’s take one more look at it:

Atcom AG-188N WAN configuration screen

Atcom AG-188N WAN configuration screen

As you see, you can enter static IP information, dynamically obtain an IP address, or use PPPoE. Depending on which you choose, you may need to fill in additional information in the text boxes. Most users will simply pick DHCP to obtain an address from an “upstream” router and be done with it — if you’re like me, you may not understand exactly how it works, you’re just glad it does. But, if you need or want to assign a static IP, or need to use a PPPoE server, you have that ability. Most VoIP adapters will let you use DHCP or a static IP address, but I can’t recall seeing any others that offer PPPoE support.

As I mentioned in the previous article, the manual is silent on the usage of the “Mac Authenticating Code” field, but the most likely use is for “cloning” the Mac address of another router or computer, in the unlikely event that your ISP actually cares what you plug into their cable or DSL modem.

Now let’s look at the LAN configuration settings:

Atcom AG-188N LAN configuration screen

Atcom AG-188N LAN configuration screen

If you are sending this unit to someone in a remote location and you don’t know whether they are going to plug a computer, a switch, a router, or nothing at all into the LAN port of this device, the default settings are probably the safest - as long as whatever’s plugged into the LAN port gets its address using DHCP, it should work. Providers could send a unit to a customer, knowing that if the customer simply unplugs the network cable from the back of the computer and plugs it into this unit, then uses another network cable to go from this device to the computer, it will still work in most cases (provided they don’t swap the WAN and LAN port connections, anyway).

In the specific case where the WAN port of this device is connected to another router, it’s true that having two routers “stacked” may not be an optimum situation, since you are doing two levels of Network Address Translation (NAT) — therefore this configuration could interfere with certain services (perhaps ironically, one of the things that would be most likely to be affected adversely would be any SIP-based softphone client running on a computer behind the two levels of NAT). But for most typical end users, the defaults are probably the safest if you have no idea what they are going to do on their end.

However, for those who know what they are doing, you can tweak the settings for a more optimum configuration. The available settings are

  • Bridge Mode: You’d probably want to enable this if you know that the AG-188N will be connected to an “upstream” router, rather than directly to a cable or DSL modem. When this is checked, the AG-188N will not assign IP addresses for devices connected to its LAN port — the AG-188N and any devices plugged into the LAN port will all be on the same network. This would avoid the “double NAT” problem mentioned above. Note that this setting will not take effect until you save the config and reboot the device.
  • IP: The base IP address for the local network. This is also the address that you can use to access the AG-188N configuration pages from devices connected to the LAN port. Normally it should always be in one of the “private” IP address ranges and should always end in .1. In almost all situations it is safe to leave it at the default — the one exception is if the “upstream” network also uses the 192.168.10.x address range, in which case you might want to change the “10″ to some non-conflicting address. You almost certainly must change this if there is already an upstream device (such as an upstream router) using 192.168.10.1.
  • Netmask: If your IP is in the 192.168.x.x range then leave this at the default. If you change the IP to something outside that range, I assume you know what needs to be used here.
  • DHCP Server: Enables DHCP service in LAN port. Leave this checked unless you are using “Bridge Mode”, or have a specific reason for turning it off (such as, ALL connected devices use a fixed IP address).
  • NAT: Enables Network Address Translation. Also leave this checked unless you are using “Bridge Mode.”

Note that it may not hurt anything to leave the DHCP Server and NAT enabled when using “Bridge Mode”, but I simply prefer to leave no doubt that we want the “upstream” router to handle these functions. I discovered that enabling “Bridge Mode” does not seem to totally disable the internal LAN, as evidenced by the fact that even though my computer received its IP address from the “upstream” router (in the 192.168.0.x range), I could still access the AG-188N’s web pages on either the 192.168.10.1 address, and that was true even if I disabled the DHCP Server and NAT. So since I don’t know exactly how things are being handled internally, I just felt it best to tun off those services when running in “Bridge Mode.”

Now let’s look at the DHCP Service configuration page:

Atcom AG-188N DHCP Service configuration screen

Atcom AG-188N DHCP Service configuration screen

I didn’t change anything on this page, and I don’t advise that you do so either unless you know what you are doing. Note that by default, the DHCP server will assign addresses in the range 192.168.10.1 through 192.168.10.30 (with 192.168.10.1 normally being the AG-188N itself), so if you want to assign any device a fixed IP address you’re safe in assigning it anything from 192.168.10.31 through 192.168.10.254 (of course, you’d have to connect the LAN port to a switch in order to connect multiple devices). For the most part the settings seem pretty self-explanatory. The one thing I didn’t fully understand is the setting for “Update Mode”, which has three choices: None, Update firmware, or Update config file. I turned to the manual for enlightenment and this is what it had to say:

Update Mode: Using DHCP updated model, None expressed are not updated, Update firmware update firmware is used to DHCP. Update file is used to configure DHCP updated configuration files.

Um, okay then. Seems like the default choice of “None” is probably right for most users. So, since there’s really nothing to see here (for most users, anyway), let’s move along to the NAT configuration page:

Atcom AG-188N NAT configuration page

Atcom AG-188N NAT configuration page

Again, I didn’t change anything on this page, and most users won’t need to either. The exception would be if you need to map a port to a particular device — this is where you’d do it. Just fill in the blanks for your new port mapping rule, click add, and you’re all set. Under “Transfer Type” your choices are TCP or UDP. Oh, and in case you’re wondering about the first three checkboxes, ALG apparently stands for Application-Level Gateway, and if you click on the link it will take you to a Wikipedia article on the subject.

The Net Service page lets you change certain default port settings used by the AG-188N, and shows you a table of all devices that currently have DHCP leases:

Atcom AG-188N Net Service and DHCP Lease Table screen

Atcom AG-188N Net Service and DHCP Lease Table screen

Most users will not want to change any of these, and I certainly would not advise doing so, but you can if you really want to. If you change the HTTP port and then forget what you changed it to, you probably will not be able to access the Web interface, so be careful here!

The next page we’ll look at is the QoS page:

Atcom AG-188N QoS configuration page

Atcom AG-188N QoS configuration page

QoS stands for “Quality of Service”, and is a method for giving certain packets priority over others. Of all the screens on this device, this is the one of the two that I comprehend the least, and I get the distinct impression that either the author of the manual didn’t fully understand it either, or else felt that anyone changing the parameters on this page would know what they were doing. Here’s what it has to say about this screen (slightly edited to clean up obvious spelling/punctuation/syntax errors):

AG188 implements QoS based on 802.1p. The QoS is used to mark the network communication priority in the data link/MAC sub-layer. AG188 will sort the packets using the QoS and send them to the destination.

  • VLAN Enable — Disable/Enable VLAN function
  • VLAN ID Check Enable - not defined by the manual
  • Voice/Data VLAN differentiated — what the manual has to say about this is borderline incomprehensible, but basically you have three choices Undifferentiated, Tag differentiated, and Data untagged. Here’s the actual, verbatim phrase from the manual: “undifferentiated for Date and voice VLAN is not distinction VLAN tag, Tag differentiated for Date and Voice VLAN is distinction VLAN tag, Date untagged for Date VLAN is distinction VLAN tag.”
  • DiffServ Enable — Disable/Enable Diffserv service
  • DiffServ Value — Configure the Diffserv parameter. The permissible range of values is: 0×28, 0×30, 0×38, 0×48, 0×50, 0×58, 0×68, 0×70, 0×78, 0×88, 0×90, 0×98, 0xb8. The default is 0xb8, which stands for best fast transmission; 28-30 is guarantee for the transmission priority for the 1st rank, 48-58 is guarantee for the transmission priority for the 2nd rank, 68-78 is guarantee for the transmission priority for the 3rd rank, and 88-98 is guarantee for the transmission priority for the 4th rank.
  • Voice VLAN ID — configure the Voice/signaling VLAN ID
  • Data VLAN ID — Assign VLAN id for data stream.
  • Voice 802.1p Priority — Configure the priority of the voice packets in 802.1p protocol.
  • Data 802.1P Priority — Configure the priority of the data packets (non-voice/signaling data) in 802.1p protocol.

There’s also a separate section in the manual on VLAN implementation, which shows several screen captures that will hopefully aid you in setting this up. Honestly, I’d welcome comments from anyone who can further enlighten me on the correct way to set this up. If you don’t use the LAN port, or if you are not pushing much data through the LAN port while on calls, it’s probably okay to leave this not enabled. But if you do use the LAN port, and you experience voice breakups and other weirdness while you are on the phone, the best advice I can give you is to try the various sample configurations in the “VLAN implement” section of the manual. If anyone is an expert on QoS implementation, please leave a comment and help us understand the correct way to configure this!

There’s one more networking-related page to talk about, and it’s the other one that I have relatively little understanding of, although I’d definitely like to increase my knowledge. Let’s look at the VPN Tunnel page:

Atcom AG-188N VPN Tunnel configuration screen

Atcom AG-188N VPN Tunnel configuration page

The AG-188N supports VPN (Virtual Private Network) tunneling using either UDP (apparently a custom format for one specific customer) or L2TP (without IPSec). Unfortunately, it does not support other popular methods, such as IPSec, PPTP, or OpenVPN. For those who may not understand why you’d want to use a VPN tunnel, I’m going to quote an excerpt from the Wikipedia article on VoIP VPN here, since it explains this far better than I could (just replace the reference to “IPSec” with “UDP or L2TP”):

A VoIP VPN combines Voice over IP and Virtual Private Network technologies to offer a method for delivering secure voice. Because VoIP transmits digitized voice as a stream of data, the VoIP VPN solution accomplishes voice encryption quite simply, applying standard data-encryption mechanisms inherently available in the collection of protocols used to implement a VPN.

The VoIP gateway-router first converts the analog voice signal to digital form, encapsulates the digitized voice within IP packets, then encrypts the digitized voice using IPSec, and finally routes the encrypted voice packets securely through a VPN tunnel. At the remote site, another VoIP router decodes the voice and converts the digital voice to an analog signal for delivery to the phone.

…..

Security is not the only reason to pass Voice over IP through a Virtual Private Network, however. Session Initiation Protocol, a commonly used VOIP protocol is notoriously difficult to pass through a firewall because it uses of random port numbers to establish connections. A VPN is one solution to avoid a firewall issue when configuring remote VoIP clients. The VPN virtually moves users inside the same network local as the VoIP server.

Edit: Unfortunately, it turns out that the AG-188N uses L2TP without IPSec, which means that the comments about voice encryption in the above excerpt aren’t applicable - L2TP alone does not offer any form of encryption. However, the final paragraph of the excerpt, talking about how a VPN tunnel could overcome difficulties with firewalls when SIP is used, would still be applicable.

Here’s the explanation of the settings on this page:

  • VPN IP — After the AG-188N has registered successfully on the VPN, the VPN server will assign an IP address to the device. If there is a IP address other than 0.0.0.0 shown here, it means that you are successfully registered on the VPN.
  • UDP Tunnel and L2TP settings — These are obvious from the text field labels. Only fill in the settings for the protocol you plan to use (probably L2TP unless you can somehow reverse-engineer the UDP method).
  • UDP Tunnel and L2TP radio buttons — Click the one corresponding to the type of tunnel you plan to use.
  • Enable VPN — Enable the VPN server — you must choose either UDP or L2TP type in advance.

Some of you may be wondering - if you set up a VPN tunnel, does all traffic get routed through it (including any traffic on the LAN port), or only VoIP traffic? And, if only VoIP traffic, will it route both SIP and IAX protocols over the tunnel, or just one or the other? And unfortunately, I simply don’t know the answer to that at this point. I also don’t know how to set up a VPN using either UDP or L2TP on an Asterisk/FreePBX server, otherwise I might give this a go. If if any of the more popular forms of VPN tunneling were supported (such as IPSec, PPTP, or OpenVPN) I might be able to set those up and administer them using Webmin, but it appears that there are no Webmin modules available to help configure L2TP or UDP tunnels.

Edit: After receiving some clarification that this uses L2TP without IPSec, I Googled a bit and found a blog post entitled “Use Linux to Setup L2TP Server (without IPSec)” that appears to give server installation and configuration instructions that should work under CentOS (the opening paragraph is in Chinese, but the actual steps are all in English, and if you’re curious about that opening paragraph you can always view the Google translation). However, I think I’d try using yum install l2tpd rather than using rpm in the first instruction; if that doesn’t work you can always try the rpm method. It looks like it should be a pretty simple installation, but I have not actually attempted it yet.

At this point, this may be my only real letdown with the AG-188N - I was enthused when I saw that it supported VPN, but that enthusiasm rather quickly deflated when I saw that it really didn’t support any of the more widely-used VPN protocols (Edit: and in particular, none that offer encryption). And granted, my disappointment may be in part based on my lack of proficiency in setting up a VPN server, or some other lack of understanding — feel free to enlighten me! — and in any case, my disappointment here is tempered by the knowledge that no other ATA’s (to the best of my knowledge) support any form of VPN tunneling. The vast majority of users of this device are probably not going to care whether it supports VPN or not, let alone which “flavors” of VPN, but it’s just something that had particular appeal to me.

This is a subject I’d obviously like to know more about — some readers may recall my post, New Products Wanted, part 1: Simple VPN devices (switches and/or routers) — so I welcome any comments that might help me set up one of the supported forms of tunneling, especially if there is a web-based GUI administration utility available (sorry, Linux gurus, I don’t share your affinity for config files and the command line).

There are a few other configuration pages on the AG-188N that I have not discussed separately, either because their purpose and usage is fairly self-evident (Clear Config, Backup Config, WEB Update — the latter lets you upload new firmware or restore backup configuration files) or are of interest primarily to service providers and other “system administrator” types (FTP/TFTP Update, Auto Provisioning). If you really want to see screenshots of any of these, leave a comment and I’ll post them in a followup article.

In the next installment, I plan on wrapping up this series (for now, anyway) with some final thoughts and a summary review. I hope you’ve enjoyed this exploration of the AG-188N up to this point as much as I have!

Disclosure: CIGear provided me with an Atcom AG-188N for review purposes, and allowed me to keep it after I was finished writing this series, and for that I am most grateful.

Previous Installment | Next Installment

Articles in the series: Review of Atcom AG-188N IAX+SIP ATA (VoIP adapter)

Part 1 – The unboxing
Part 2 – Initial setup using IAX
Part 3 – Setting the time and configuring outbound dialing
Part 4 – Setting up SIP, and securing the adapter
Part 5 – Networking and Internal Router
Part 6 – Final Thoughts and Summary Review
Part 7 – Addendum


Jun 03 2009

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

Category: Asterisk, General, Networkingmichigantelephone @ 1:02 pm

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 — perhaps the most compelling reason being that many commercial VoIP providers only offer connections using SIP protocol.

Fortunately, setting up the SIP configuration on this unit is pretty straightforward. Just click on SIP Config (not SIP) in the left-hand menu, and this screen appears:

Atcom AG-188N SIP configuration screen

Atcom AG-188N SIP configuration screen

If you’re connecting to an Asterisk or FreePBX server, you probably only need to fill in the following:

  • Register Server Addr — this is the address of your server, such as 192.168.0.100 or myserver.dyndns.com
  • Register Server Port — the SIP port number of the server — note that while the default of 5060 is most common, there may be cases where a different port is used, so it pays to check.
  • Register Username — just use your extension number here, unless you are instructed otherwise.
  • Register Password — the same as the Asterisk “secret” for your extension.
  • Phone Number — your extension number (again).
  • Display Name — The name you want to appear in the other party’s Caller ID display if you ever do a direct SIP-to-SIP call. FreePBX and most providers will ignore this, instead using the name associated with your account.
  • Enable Register – Always check this box, to enable SIP registration, if you plan to use SIP.
  • SIP(Default Protocol) — This sets the default protocol to SIP for outgoing calls. If you check this box, it automatically unchecks the box that makes IAX the default protocol on the IAX setup screen.

As long as you haven’t changed any of the default settings (as shown on the above screenshot), everything will very likely work. You should try a test call and see if you can connect. If so, I then recommend that you try changing the Register Expire Time — the manual says the default on this is 600 seconds, but as you can see from the screenshot above, it’s actually set to 60 seconds, which means it re-registers once per minute, which may generate a lot of unnecessary traffic between you and the server. The manual also says that the AG-188N “will auto configure this expire time to the server recommended setting if it is different from the SIP server.” Huh? In any case, I’d try setting the registration higher - you can try the 600 second default, but many adapters go even higher (a 3600 second re-registration is not uncommon). However, if you pick up the phone and find you don’t get dial tone sometimes, or if your callers get a congestion signal sometimes, you may need to go for a lower value. I can tell you from personal experience that some users served by a DSL line might need a shorter re-registration interval.

Here’s what the other settings are for. You probably won’t need to change any of these from the default, unless your system administrator or provider specifically tells you to do so:

  • Proxy Server Addr, Proxy Server Port, Proxy Username, Proxy Password — in almost all cases these will be the same as the equivalent Register values, and that’s what the AG-188N assumes if you leave these blank, so very few users would have any need to fill these in.
  • Domain Realm — if you leave this blank, the AG-188N will use the proxy server address as the SIP domain, which in most cases is fine. However, if you are using a dotted IP address (such as 192.168.0.100) as the server address, and the server is misconfigured, you (very rarely) might need to put the server’s external address (such as myserver.dyndns.com) here.
  • Detect Interval Time — this is only applicable if you check the Auto Detect Server checkbox, in which case the AG-188N will try to detect whether the SIP server is available at the interval specified here. I had originally thought that perhaps, if the server could not be detected (or the network connection was lost), the AG-188N would stop delivering dial tone. But nooooo — in my testing it made absolutely no difference. What it actually does is let you use a second, “fallback” SIP account if your first account goes down! See the note on the “Auto Detect server” checkbox below.
  • Encrypt Key — the manual is silent on this, but if the server supports encryption on SIP connections, then I would guess you’d put the key here.
  • DTMF Mode — with SIP connections you have three different ways of sending touch tones to the server: RFC2833, DTMF_RELAY (inband audio), and SIP info. In most cases you’ll leave this at RFC2833, but in some cases, particular if you are having issues with distant systems not recognizing your touch tones, you may want to try a different method. Inband audio should probably be your last choice, but I have seen cases where it’s the only thing that would work. Note that the way the server is configured can also have an effect on how tones are passed - even if you send the tones inband, your server may be converting them to RFC2833 before sending them “upstream.”
  • Local SIP port — the local SIP registeration port, which defaults to 5060, which is almost always what you want to use.
  • RFC Protocol Edition — according to the manual, you would only need to set this to RFC 2543 if you are trying to communicate to devices (such as a CISCO 5300) using the SIP 1.0 protocol. The default is RFC 3261, and unless specifically instructed otherwise, that’s the setting you should use.
  • Server types in SIP config window

    AG-188N Server types in SIP configuration screen

  • Server Type — leave this on “common” unless you happen to be connecting to one of the “uncommon” servers shown in the dropdown (pictured at right).
  • User agent — much as your web browser sends a User Agent string to identify itself, VoiP adapters also send an identification string. By default, the AG-188N sends the rather boring “Voip Phone 1.0″ but you can change that here, although about the only person who would ever see it is the system administrator of the system you’re connecting to. While you could possibly put something more interesting in here (I’ll leave it to your imagination!), I wouldn’t advise it if the system administrator is not known to have any discernible sense of humor. :)

The AG-188N manual is mostly silent with regard to the checkboxes we’ve not already mentioned. In fact, it only mentions these three:

  • Enable Register — Enable or Disable SIP registration. The AG-188N won’t attempt to register with the SIP server if this isn’t checked, so leave it checked as long as you’re using SIP.
  • Auto Detect server — Okay, here’s how the manual describes this one: “co-work with Server Auto Swap and Detect Interval Time. Enable this option, AG-188N will periodically detect whether the public SIP server is available, if the server is unavailable, the AG-188N will switch to the back-up SIP sever, and continue detecting the public sip server. AG-188N will switch back to the primary SIP server if the server is available again.” Yes, folks, this device lets you use TWO sip accounts, and fallback to the second if the first goes down! Interestingly, although the manual makes reference to a “Server Auto Swap” checkbox, I’m sure not seeing it anyhere on this page.
  • Enable Via rport — checked by default, this configures support for RFC 3581. If you really want to know, see this FAQ. If you don’t, just leave it checked.

What about the other checkboxes? Here’s my best guesses, supplemented by additional information from Atcom manuals for some of their other products. I’d leave all of these at the default setting unless you really know what you are doing:

  • Enable PRACK — read this — the phrase “Numerous implementation problems seen in the field” is enough to discourage me from checking this box! Another Atcom manual offers this: “enable the PRACK in SIP which is mainly used in special ring tone, recommend to keep the default setting.” Do you need any other reasons to avoid it?
  • Enable Keep Authentication — feel free to check this if you like, but the unit seems to stay registered without it. A manual for a different Atcom device says that this enables “registration with authentication request to be sent to sever together”, while yet another Atcom manual says that it enables “registering signal together with the authentication information. If enable it, the server will confirm the registering and send back the confirmation massage directly instead of requesting the terminals to send authentication information if needed.” Yeah, that clears it right up for me!
  • Signal Encrypt, RTP Encrypt — if your server supports encryption, and you have filled in the Encrypt Key field, you almost certainly need to check these to make it work.
  • Enable Session Timer — a session timer is a way to determine whether a call session is still active. Apparently this “enables RFC4028 to refresh the SIP sessions”, according to another Atcom manual.
  • Answer With Single Codec — other Atcom manuals say, “only answer the call with a certain Codec.” My best guess here would be that this will only use your “preferred” codec when answering a call. If the server doesn’t support your preference, you probably won’t receive any calls.

Now, above I mentioned that you can actually have two active SIP accounts on this device, in addition to an active IAX account, presumably in addition to having a landline plugged into the PSTN port. I suppose that means that potentially, one phone could receive calls from, or place calls to as many as four different sources! I doubt many people will actually use the device with more than one account, but it’s interesting nonetheless that this adapter has this capability!

I will note that things may not always work quite as you’d hope in a multi-account configuration. I set it up so that there would be one SIP account and one IAX account active on the unit. When I had an active call in progress on one account, I’d try calling the other and I always got a busy signal, even though call waiting is enabled. I had rather hoped that if you were using one account and a call came in on anther, it would activate call waiting, although since I am among those that would probably never have a reason to use this device with multiple accounts, that’s kind of a non-issue for me. Call waiting DOES work if another call comes in on the same account while you are on a call, and there may be situations where it would work across multiple accounts (I didn’t test with two SIP accounts, for example).

The manual seems to confirm my suspicions that IAX and SIP don’t work together as well as one might hope:

How many SIP servers may AG-188N register simultaneously?
AG-188N support 2 SIP servers and a IAX server. The Default server is SIP. If you want to use the IAX server you must set IAX as default protocol in the IAX config page. IAX and SIP can register simultaneously but not work simultaneously. If you set 2 SIP servers in the SIP setting page, you can choose the route (server) by dialing plan which is edited by you. Please see “How to use the dial rule?” for detail.

Before you get too perturbed by this, ask yourself how many other devices let you use multiple accounts from the same phone. And if you’re wondering how you would select which account to use for a particular call when multiple accounts are available, that sort of thing is accomplished in the Dial-Peer screen, which we briefly covered yesterday. You probably will need to read the manual to learn how to set it up.

You might be wondering how you’d set up that second SIP account. That’s accomplished by looking in the “Advance” section of the left-hand menu, and clicking on SIP. When you do that you get this screen:

Atcom AG-188N Advanced SIP configuration screen

Atcom AG-188N Advanced SIP configuration screen

As you can see, it’s pretty much a duplicate of the other SIP configuration screen, but without as many settings, and with the word “Private” inserted into many of the description texts (not sure why they chose the word “Private” to describe the second account, but oh well). Really, there are only five new settings here:

  • STUN Server Addr — If you use a STUN server, enter its address here
  • STUN Server Port — If you use a STUN server, enter the port number here. The default STUN server port is 3478.
  • STUN Effect Time — a different Atcom manual is far less confusing on this item: “STUN detect NAT type interval time. If NAT found a link inactive for a certain time, it will close the link so you need to send a packet within a interval time to keep the link alive.”
  • Enable URI Convert — convert # into %23 when sending URI (from a different Atcom manual, since it’s not in the one for the AG-188N).
  • Enable SIP Stun — A different Atcom manual sums this STUN stuff up nicely: SIP STUN is used for NAT transverse. When you config STUN server’s address and port (default 3478) and enable it, then you can use the normal SIP server to make the IP phone transverse NAT.

I will point out that more than likely, if you define a STUN server on this page, the AG-188N will be able to utilize it whether you are using the primary SIP account, or the “Private” account defined on this page. So it’s just slightly confusing that although at first glance this appears to be the settings for the second account, there are a few items here that could affect the ability of both accounts to penetrate NAT firewalls.

By the way, if you want to know more about STUN you can always try Wikipedia, and if you need to find a public STUN server, just Google public stun servers, and your desire should be met! That said, I’ve never had much luck trying to use a STUN server, and in most cases you won’t need to use one, which perhaps is why these settings were placed on this page.

If you’re starting to see that in many ways this device is more full-featured than some other VoIP adapters that are out there (and probably easier to configure), you can understand why I really like this unit - well, for the most part. And that brings me to the subject of security.

When you first access the unit, you have to login, and that’s to be expected. While some competing adapters don’t force you to use a username and password, they basically only have two accounts — user and admin. The AG-188N has those (well, actually, guest and admin) by default, but you can add more. If you click on “Account Management” in the left-hand menu, it brings you to the screen shown below, minus the entry fields at the bottom — those only come up when you press Add, to add an account:

Atcom AG-188N Account configuration page

Atcom AG-188N Account configuration page

It’s probably obvious that this is also the page you’d go to if you wanted to change a user’s password, or to delete an account.

There are two user levels possible, Root and General. General users only get to see a limited subset of the pages: WAN Config, LAN Config, Audio Settings, WEB Update, FTP/TFTP Update, Auto Provisioning, and Logout & Reboot. I’m not sure why you’d need to add additional users, but you can. Anyway, it appears you have to set a User name and Password for all users.

And normally that would not be any problem at all, except that while writing this review I’ve had to go back into the interface several times to look at the configuration, and if I haven’t done anything in there for a few minutes it apparently logs me off, and then I’m forced to login all over again! While I suppose this is really a good thing — if you happen to leave your browser open to this device and then leave, some mischief-maker can’t come along half an hour later and start changing settings on you — it’s still kind of a pain when you are doing something like this. Oh, well, I guess it really is a good thing!

For those that want extra security, you can go to the “MMI Filter” page and set a filter by address range:

Atcom AG-188N MMI Filter screen

Atcom AG-188N MMI Filter screen

When the MMI filter is enabled, only IP addresses between the start IP and the end IP can access the AG-188N. It’s a good dose of extra security, but be careful not to lock yourself out — and remember, if you ever take your adapter with you when you travel, whatever network you happen to land upon may not be using the same IP range as your home network. So I don’t think I’d advise setting this if you travel a lot, but at least the AG-188N gives you the option, something that some other adapters do not.

What’s next? Well, we haven’t even really touched on the networking functions in this unit. Stay tuned for the next installment!

Disclosure: CIGear provided me with an Atcom AG-188N for review purposes, and allowed me to keep it after I was finished writing this series, and for that I am most grateful.

Previous Installment | Next Installment

Articles in the series: Review of Atcom AG-188N IAX+SIP ATA (VoIP adapter)

Part 1 – The unboxing
Part 2 – Initial setup using IAX
Part 3 – Setting the time and configuring outbound dialing
Part 4 – Setting up SIP, and securing the adapter
Part 5 – Networking and Internal Router
Part 6 – Final Thoughts and Summary Review
Part 7 – Addendum


Jun 03 2009

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

Category: Asterisk, General, Networkingmichigantelephone @ 12:59 pm

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 options are covered there that are not covered in the PDF version. Perhaps someone at Atcom should make the effort to generate new online PDF files from the current documentation.

Also, today I found out that because I didn’t have the latest firmware, there are more CODEC options on the Audio Settings page than what I had pictured - you can now select up to five CODECs, in order of preference. I’ve uploaded an additional screenshot to yesterday’s article, so you can see what’s changed.

Yesterday, we pretty much covered IAX settings that would allow you to receive incoming calls on the AG-188N, but if you’d like the correct time to show on your CallerID display, you probably want to click on the Time Config selection in the left-hand menu, to access this page:

Atcom AG-188N Time configuration page

Atcom AG-188N Time configuration screen

This one is pretty self-explanatory, but note one thing: The time server must support Simple Network Time Protocol a.k.a. SNTP. Some time servers only support NTP. When I tried to use the time server on the Asterisk system, which does NTP only, I got no time information with my incoming calls. However, when I went to the time server pool at ntp.org (specifically us.pool.ntp.org) it seemed to work fine, so apparently their time servers “speak” SNTP. us.pool.ntp.org is a good time server choice if you’re in the U.S.A, while in Canada you’d probably want ca.pool.ntp.org, and if you’re someplace else you can start here and select your continent, then drill down until you find the time server for your country.

Then select your time zone, check “Daylight” if your area observes Daylight Savings Time, and check “select sntp” (if you don’t check that box, it expects that you will be entering the time manually using the lower section!), and Apply. The default timeout of 60 seconds is fine; that’s just how long the device will wait for the time server to respond before giving up. There’s no real reason to use the Manual Timeset section, unless perhaps for some reason you are on a system that has no connection to the Internet (I suppose such “closed” systems must exist somewhere).

You may be wondering if the Daylight time rules are configurable. Not from the Web interface, sorry. Newer Linksys devices, in contrast, let you specify a daylight time change rule (which is a string format that’s clear as mud for many users, but at least they make it possible to install a rule for your area from the Web interface). I had originally thought there was no way to change the rule in the AG-188N, but then I discovered that if you click on “Backup Config” in the left-hand menu, you can save your configuration settings in a plain text file, and in that file there is a section in there that looks like this:

DayLight Shift Min :60
DayLight Start Mon :3
DayLight Start Week:5
DayLight Start Wday:0
DayLight Start Hour:2
DayLight Start Min :0
DayLight End Mon   :10
DayLight End Week  :5
DayLight End Wday  :0
DayLight End Hour  :2
DayLight End Min   :0

If you were to edit those values (using a text editor that does not change the line endings, please!) and then use “Web Update” to reload the configuration, you could change the Daylight time rules. While this is a bit of a pain, it’s probably actually easier to understand than the way Linksys does it. If you need to know when Daylight time starts and ends in your part of the world you can consult Wikipedia, but in most of the United States and Canada, DST starts on the second Sunday of March and ends on the first Sunday of November. Wikipedia says that they don’t observe DST in China, so I have no idea whose DST rule is loaded into the AG-188N, but it sure doesn’t look like the one for the U.S.A. and Canada to me. I’m guessing that the following values should be changed as follows (assuming that they are using “1″ based numbering on week and month):

DayLight Start Week:2
DayLight End Mon   :11
DayLight End Week  :1

If I’m wrong, I’ll bet I’m still closer than the original rule! Anyway, if you do feel brave enough to edit the configuration backup file, after you carefully make the edits, rename the backup file extension from .txt to .cfg before using “Web Update” to load it back in. I actually did it and it took the changes (confirmed by saving another backup), but I’m not suggesting anyone should do it - if you want to try it, you assume the risk that something may go wrong, not me!

Okay, with that out of the way, let’s move on to making outgoing calls. Right out of the box it’s possible to dial some numbers, but if you have ever configured a VoIP adapter in the past, you know there are tweaks that need to be made to accommodate local dialing patterns. For one thing, it you were to use the AG-188N to try dialing a feature code that starts with a “star” character (*), such as *43 for the echo test on a FreePBX box, you’d note that the moment you hit the * key it goes to a busy signal. One reason for that is that by default, the star code indicates that you want to access the PSTN line connected to the PSTN port on the device, instead of the IAX and/or SIP account(s) configured on the AG-188N. This allows one analog phone to use either IAX/SIP or the PSTN. But if you aren’t using the PSTN port, and you are using an account on an Asterisk server, you probably want to be able to dial “star” feature codes without the AG-188N intercepting them. In order to accomplish that, we must select “Dial-Peer” in the left-hand menu - yes, I know it looks like it’s not a link, but it is — trust me. Click on it, and you will see this:

Atcom AG-188N Dial-Peer configuration screen

Atcom AG-188N Dial-Peer configuration screen

By default, there is only one entry here, for *T — you should delete this rule entirely. If you still want to be able to access a phone line plugged into the PSTN port on the device, you could create a new rule, such as **T (which would require two depressions of the * key to select the PSTN line) and use the same parameters as the original *T (in case you are wondering, no you can’t simply modify the existing rule, because when you click on “Modify” you can modify every field except the Number). By the way, the T with no digit after it is the same as T0 (T followed by a zero), which means that there is no delay once the pattern is matched.

You can think of the Dial-Peer page as a variation on speed dialing, and a place to add digits to, or strip digits from a dialed number. According to the AG-188N manual, here’s what can be accomplished on this page:

  • Replace, delete or add a prefix to the dialed number
  • Make a direct IP to IP call
  • Place the call to a different SIP server after dialing a prefix
  • Make PSTN calls using the Lifeline function (the rule I just had you delete or modify above)

If you need to do any of those things, make sure you read the section of the manual dealing with the Dial-Peer configuration page. The specific case of adding a prefix (1 + area code) to a seven digit local number is covered in Part 7 of this series, along with some additional information about dialed number modification using the Dial-Peer page.

Now at this point you might pick up the phone and hit the star key, only to discover that you’re still getting a busy signal. What’s going on? Well, it turns out that there’s one more place where an adjustment needs to be made. In the left-hand menu, select “Digital Map” - that should bring up this page:

Atcom AG-188N Digital Map configuration screen

Atcom AG-188N Digital Map configuration screen

“Digital Map” is a fancy way of saying “Dial Plan” - it’s the dial rules used to determine when a number that has been dialed is complete, and should be sent to the switch. Yes, they used the word “Prefix” in this section - I attribute it to someone picking the wrong English word when translating from Chinese. Either “Pattern” or “Rule” would have probably been a more appropriate choice than “Prefix.”

You’ll note that there’s a rule for a single star (in Texas they’d call it a lone star). :D But, we don’t want the AG-188N to think that dialing is complete after we’ve only pressed the star key once, so using the dropdown and “Delete” key on the bottom line of the page, I deleted that rule. At that point, I had no dial rules at all. I could dial any number, but there would be a five second delay after the last digit dialed before the call went through. Obviously, we don’t want a post-dial delay on calls if that can be avoided, so we should add some rules, or prefixes as they are called here. But first, we’d better know what we can place in the rules:

  • The digits 0-9 and the * character
  • A range of digits in square brackets [ ], for example it could be a range such as [1-4], or use comma to separate individual numbers, such as [1,3,5], or use a list such as [234].
  • x is a “wildcard” character represents any one digit between 0~9
  • Tn if used, must be the last thing on a line, and represents the amount of time we will wait after a pattern is matched to see if the user will depress any additional digits. n can be any number of seconds in the range 0-9. If the n digit is omitted and T used by itself, it means the same as T0, which means there would be no wait at all after the last digit is dialed. However, it appears that either T0 or a T by itself may be redundant in this screen - when a pattern is fully matched it is assumed to be complete, and there would be no further delay unless Tn is used, when n is some non-zero value.

Now, for those used to constructing Dial Plans on a Linksys or Sipura device, the principle here is pretty much the same. Just keep in mind that instead of using a bar character | to separate individual dial plan rules, here you add each separately, and it occupies its own line. Also, instead of using the S (seconds) to indicate a wait delay, here we use T (time in seconds).

The manual gives some usage examples:

  • [1-8]xxx All number from 1000 to 89999 will be sent immediately
  • 9xxxxxxx 8 digits numbers beginning with 9 will be sent immediately
  • 911 The number 911 will be sent immediately
  • 99xT4 3 digits numbers that begin with 99 will be sent after four seconds

So, let’s take a Dial Plan string that we might find on a Linksys or Sipura device in the USA or Canada, where local extensions are assigned numbers in the range 1000 through 1999 and it is desired to have seven digit dialing of calls with one’s own area code, and eleven digit dialing to all other area codes:

([3-9]11|1[01]xx|[2-9]xxxxxxS0|1[2-9]xx[2-9]xxxxxxS0|*xxS0|[*x].S4)

Here’s how each rule would be translated to a “Prefix” on the AG-188N:

  • [3-9]11 — [3-9]11 or [3-9]11T or [3-9]11T0
  • 1[01]xx — 1[01]xx or 1[01]xxT or 1[01]xxT0
  • [2-9]xxxxxxS0 — [2-9]xxxxxx or [2-9]xxxxxxT or [2-9]xxxxxxT0
  • 1[2-9]xx[2-9]xxxxxxS0 —1[2-9]xx[2-9]xxxxxx or 1[2-9]xx[2-9]xxxxxxT or 1[2-9]xx[2-9]xxxxxxT0
  • *xxS0 — *xx or *xxT or *xxT0
  • [*x].S4 — [*0-9].T4

As you can see, the most common patterns translate very easily. But some things are questionable. Note that last example - whereas a Linksys device allows [*x] to represent “any digit or the star key”, the Ag-188N seems to require the slightly more specific [*0-9]. But also, that rule contains a period (.) period character, which on a Linksys/Sipura device means “one or more of the preceeding character.” Here it means any length pattern starting with * or 0-9, with any number of digits (possibly mixed with star key presses) following. This type of rule (or something very similar) is commonly used as a “default” rule, to set a four second timeout for anything that doesn’t fit one of our other rules, such as international numbers. The problem here is that the AG-188N documentation makes absolutely no mention of the period character as having any significance in these settings, yet when I use it as I would on a Linksys/Sipura device, it appears to work in exactly the same manner. Something they forgot to document, perhaps?

Of course, you could do away with that last pattern entirely and simply set a default timeout, as shown in the image above, but keep in mind, that controls your maximum interdigit delay during all normal dialing (though NOT the length of the initial dial tone). If you pause to look at a number while dialing, you probably don’t want the device to time out on you too soon. You might prefer to use a long default “Time Out” (something like 25 seconds), but then specify a shorter timeout for international calls, so instead of that final catch-all rule, you might use something a bit more specific, such as 011xxxxx.T4 (which would mean that once you’ve dialed 011 plus five additional digits, your interdigit timeout is reduced to four seconds.

Or, you could simply use a long “Time Out”, but then always hit the pound key # at the end of dialing any number that doesn’t match one of your patterns. That would work as long as the box for ‘End with “#”‘ is checked - when you check that box, it means that the # key signifies the end of the dialed number.

So, here’s an example of what this page might look like after you have converted the Linksys/Sipura Dial Plan string:

Atcom AG-188N Digital Map sample configuration

Atcom AG-188N Digital Map sample configuration

I know that there are a few things that can be done in a Linksys/Sipura Dial Plan that can’t be done on this page, but often those things can be done, just in a different way. For example, if you need to do number translations (where you dial one number but the adapter sends something else), you can do that on the aforementioned Dial-Peer configuration page. And if you want to set up “hotline” service, where the adapter connects to a particular number as soon as someone picks up the phone, that’s also possible, but you’d have to do it from the Call Service configuration page, which is worthy of note because of the capabilities it offers:

Atcom AG-188N Call Service configuration screen

Atcom AG-188N Call Service configuration screen

On this page you can set up the following:

  • Hotline: If you enter a number here, the AG-188N will immediately dial that number after the phone is taken off-hook.
  • Call Forward: You can call forward on busy, no answer, or always. In the case of “no answer”, be sure to set the timeout in the “No Answer Time(seconds)” field.
  • No Disturb: Usually known as “Do Not Disturb”, when enabled this option will refuse all incoming calls.
  • Ban Outgoing: Enable this to ban outgoing calls (useful if, for some reason, you want a phone to receive incoming calls only).
  • Enable Call Transfer: “If A is the AG-188N user, and B calls and talking with A through VoIP. A can press the Hook-Flash to hold the call with B, and then press * and then enter C’s number. B will be transferred to C and can talk with C.” Note that Asterisk and FreePBX users might prefer to use Asterisk’s call transfer facilities.
  • Enable Three Way Call: According to the manual, only the SIP protocol supports this function — but don’t necessarily believe what the manual says (see below). “Assume A is the AG-188N user, and B calls and talking with A through VoIP. A can press Hook-Flash to hold the call with B, then enter C’s number to talk with C, and then press Hook-Flash again switch back to user B, then A can press * to make 3-way conference calls.”
  • Enable Call Waiting: Enable/disable Call Waiting
  • Accept Any Call: If this option is disabled, the AG-188N will refuse the incoming call when the called number is different from AG-188N’s phone number.
  • No Answer Time: no answer call forward time setting.
  • P2P IP Prefix: Configure point to point calling. For example, if you want to call IP 192.168.1.119 Just define 192.168.1. here and you can dial #119 to make the point to point call with the IP phone of 192.168.1.119
  • Use Record Server: Configure the support of server recording, transferring all the recordings to the server.
  • Remote Record No: Configure the recording number - if you upload your recording to this account, you can login to this account to get your voice recording. I assume the idea here is that you have some internal number you can call that will simply begin recording everything it hears - this is certainly possible to set up on an Asterisk server.
  • Black List: incoming calls with these phone numbers will be refused.
  • Limit List: outgoing calls with these phone numbers will be refused. Although the documentation doesn’t say so, I tried using a pattern here (29x to ban calls to all extension 290-299) and it did work. I assume that’s true of the Black List also, which makes both of these settings much more useful.

Note than many of the above features can also be accomplished via FreePBX or Asterisk, using feature codes, but many folks might appreciate the ability to set certain features from a web page rather than having to remember and dial a particular feature code. The only thing I changed on this page was that I enabled Call Transfer, Call Waiting, and Three Way Call (I left Accept Any Call checked as well).

The one thing that initially seemed to be a bit of a disappointment here was the inability to do three-way calling using IAX, according to the manual. I had actually tried to use the feature anyway, failed, and had written a couple of paragraphs lamenting this limitation and suggesting a really crude workaround in Asterisk. But then I took another look at the above description again, and realized that I had done it wrong. The way it works is, you have to call both parties (call the first, flash, and call the second - or - receive incoming call, flash and call second party) and then, when you are in a condition where you can flash back and forth between the two parties, press the * key — that last minor but crucial step is what makes all the difference. I have no idea why the manual would say that only SIP supports this function, but I’m very happy to report that it’s just plain wrong on that point, at least according to my testing.

Call transfer is another function that doesn’t work exactly as it might on some other adapters — for example, on a Linksys/Sipura, you simply flash and call the number you want to transfer the call to, then hang up (either while it is ringing, or after the recipient of the transferred call answers and you’ve had a chance to talk to them before handing over the call). With the AG-188N it’s strictly “blind” transfer — once you flash and then dial * plus the extension number (don’t forget the leading *), the call is immediately transferred. Of course, FreePBX and Asterisk support both “blind” and “attended” transfers internally, so this probably isn’t a big deal if you’re using an Asterisk server (which you would be if you’re using IAX protocol). And I would guess that 95%+ of all transfers are “blind” transfers anyway, judging by calls where I’ve been the one transferred.

Do remember, if you have made any changes after reading this article, to save your configuration, so you don’t lose all your changes when you reboot.

In the next installment, I want to cover setting up a SIP account. I’m expecting it will be pretty straightforward, but I’ll let you know once I actually do it. Overall, I’m still very impressed with this unit.

And now a small bonus, for those that might want to know such things. First of all, here’s a list of things you can do from the telephone handset, just by dialing certain codes:

  • #****# — reboot gateway
  • #*000# — clear settings (don’t do this unless you really need to!)
  • #*100# — set the IP type to static ip
  • #*101# — set IP type to DHCP
  • #*102# — set IP type to PPPoE
  • #*111# — say unit’s ip address (on WAN port)
  • #*222# — say phone number

The settings below need a reboot to take effect:

  • #*103# — change to bridge mode
  • #*104# — change to router mode
  • #*50192.168.1.117# — set WAN port IP address
  • #*51192.168.1.1# — set default gateway IP
  • #*52202.112.10.37# — set dns server
  • #*53255.255.255.0# — set netmask, use 255.255.255.0 if none given

In all of the above, the trailing # is optional, but speeds things up. In the last four examples, I would ASSUME that the star key * substitutes for the dot in the dotted IP addresses.

Also, this unit does have telnet access, or as the manual says, “User may use telnet command to access and manage gateway.” However, as I prefer to work within the GUI, I’ll stick with it. But I mention this because I know there’s a certain class of folks that love to get into the internals of a piece of equipment, and for those folks telnet access might be quite useful.

Disclosure: CIGear provided me with an Atcom AG-188N for review purposes, and allowed me to keep it after I was finished writing this series, and for that I am most grateful.

Previous Installment | Next Installment

Articles in the series: Review of Atcom AG-188N IAX+SIP ATA (VoIP adapter)

Part 1 – The unboxing
Part 2 – Initial setup using IAX
Part 3 – Setting the time and configuring outbound dialing
Part 4 – Setting up SIP, and securing the adapter
Part 5 – Networking and Internal Router
Part 6 – Final Thoughts and Summary Review
Part 7 – Addendum


Jun 03 2009

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

Category: Asterisk, General, Networkingmichigantelephone @ 12:56 pm

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 to the point that I could test the actual audio quality.

First, a clarification from yesterday’s post - I’ve been told that the unit I received had been previously used on a demo and therefore had been repackaged. Normally the power supply comes in a small white box, not wrapped in bubble wrap. Since I had specifically asked for a unit for review purposes, it doesn’t bother me at all that I received a unit that is new for all intents and purposes, but can’t be sold as new - that’s the perfect unit to send to a reviewer. :)

After unboxing the unit, I hooked it up to my local network, plugged a phone into the phone port, and connected the power supply and plugged it in. I picked up the phone and heard a distinctly foreign sounding dial tone (I later figured out it was a Chinese dial tone, probably since the unit is manufactured in China). I knew there had to be a web interface, but had no idea what IP address had been assigned to the unit. This is the point at which I might normally have referred to the manual, but there was no printed manual supplied. The only manual was on a small “mini CD” that came with the unit. Unfortunately, my primary computer is a Mac Mini, which has a front-loading DVD drive (where you shove the CD or DVD into a slot, and the Mac Mini sort of sucks it in). I had no idea if that drive could handle a “mini” CD, or if attempting to insert it would jam up the Mac Mini’s drive. Since I didn’t want to chance it, I took the expedient solution of firing up my old Windows box just long enough to read the CD and copy it to a shared drive, where I could peruse it on my Mac.

Mac Mini + Mini Disk? Nah, not gonna try it!

Mac Mini + Mini Disk? Nah, not gonna try it!

Unfortunately that hit a snag as well - the files on the CD are in .doc (Microsoft Word) format, not the more widely accepted PDF format. I never use .doc format - if I am writing a letter or something I use .rtf (Rich Text Format) which is far more universal. Nevertheless, to its credit, QuickLook on the Mac could display the .doc files (I might have installed a plugin to allow that at some point in the past), albeit in very tiny text. I later discovered that I could download the documentation in PDF format at the manufacturer’s web site, although it actually appears that the documentation on the disk is more complete in some sections.

The documentation revealed that in order to discover which IP address the device was occupying, I needed to pick up the phone and dial #*111#

After doing that, a very North American-sounding male voice read the IP address to me. I entered that address into my web browser, and was greeted by a rather plain but functional Logon page:

Atcom AG-188N Logon screen

Atcom AG-188N Logon screen

Back to the .doc file, which revealed that the default logons are “admin/admin for administrator and guest/guest for user.” So I logged in as an administrator, and got this screen:

Atcom-AG-188N first screen after logon

Atcom AG-188N first screen after logon

Note that there is a left-hand sidebar and a main window. In the upcoming screenshots I’ll only be showing the main window, so let’s get a closer look at that sidebar now:

Atcom AG-188N sidebar

Atcom AG-188N sidebar

As you can see, this unit has many pages of options, but fortunately we don’t need to bother with most of them just to get the device working well enough to make a test call.

The first thing you will probably want to check is the WAN config page. By default, it looked like this (I have deliberately blurred portions of a few items that probably shouldn’t be shown):

AG-188N WAN configuration screen

Atcom AG-188N WAN configuration screen

For the majority of users, the main thing to check here is that it is using the DHCP server on your network to get its address - with the “DHCP” button selected and “Obtain DNS server automatically” checked, you can probably ignore the other text boxes. One thing the documentation is strangely silent on is the use of the “Mac Authenticating Code” field - I would ASSUME that’s so you can “clone” a Mac address, if you happen to be so unlucky as to be served by one of those providers that still actually cares what your router’s MAC address is, and you plan to plug the AG-188N directly into your cable or DSL modem rather than a router.

After that I decided to skip ahead a bit and get the IAX setup working. I clicked on “IAX2 Config” and the following screen came up:

Atcom AG-188N IAX2 configuration screen

Atcom AG-188N IAX2 configuration screen

This is super easy to set up. You only need edit the following fields for use with Asterisk or FreePBX:

  • IAX Server Addr - this is the address of your server, such as 192.168.0.100 or myserver.dyndns.com
  • IAX Server port - leave at 4569
  • Account Name - just use your extension number here
  • Account Password - the same as the Asterisk “secret” for your extension
  • Phone Number - your extension number (again)
  • Local Port - leave at 4569
  • Voice mail, Echo Test fields - just blank out all four (you dial codes like *43 or *98 to reach these in FreePBX)
  • Refresh Time - all the documentation says about this is that it is the “IAX refresh time” - I assume it’s how often the device re-registers with the server. I had originally thought 60 might be a bit too short of an interval, but when I tried a higher value I discovered that calls to the unit failed. So, my advice is, leave it at 60!
  • Enable Register - Always check this box, to enable IAX registration, if you plan to use IAX.
  • Enable G.729 - G.729 is a codec that saves bandwidth at the expense of audio fidelity. Unless you are sure you need it and the server supports it, leave it unchecked.
  • IAX(Default protocol) - I checked this box, because I wanted to test IAX and don’t have SIP configured yet in any case. By default, the AG-188N assumes you want SIP to be the default protocol; this changes that assumption

After you make the above changes, be sure to click the “Apply” button at the bottom. That saves your changes, as long as the unit is not rebooted or powered down. So now I must bring up this important point:

IMPORTANT: After you make changes on any page, you must press the Apply button at the bottom of the page. But then, after you have made all the changes you plan to make, in order to save them pernamently you MUST click on “Save Config” in the left-hand menu, after which you will see:

IMPORTANT! You MUST click this SAVE button to save your changes!

IMPORTANT! You MUST click this SAVE button to save your changes!

CLICK THE SAVE BUTTON!!! If you forget this step, you get to enter all your changes again after the next reboot of the unit!

At this point, I tried making a test call to the unit. The phone rang (a short ring by North American standards) but it was perfectly usable, although to my ear the receiver volume was low (people on the other end could hear me just fine, but I had a bit of trouble hearing them). But I quickly found the fix for those things. Click on “Audio Settings” in the left-hand menu and you will see this screen (if you have the older firmware — the newer firmware has additional CODEC options, as explained below):

Atcom AG-188N Audio configuration screen

Atcom AG-188N Audio configuration screen

As you can see, unless you happen to live in China there are probably a few things you’ll want to change there! So I started by changing these:

  • CODEC - This is the codec you “prefer” to use - in the U.S.A. and Canada you’ll almost certainly want to use g711Ulaw64k (note Ulaw, not Alaw) unless you have a severe limitation on available bandwidth. Your other choices are g711Alaw64k, g729, g726-32k, iLBC, and (if you have the newer firmware — see below) None. Also, in the newer firmware, there are five CODEC settings, allowing you to select up to five CODECs in order of preference.
  • Signal Standard - This controls things like Dial Tone and Ring Length. Your choices are CHINA, USA, JAPAN, UK, ISRAEL, BRASIL (their spelling), TOPCOM, and AUSTRALIA. I’m not sure what country TOPCOM is, but if you live there, you’re supported! :) (Apparently, Topcom is a European communications company that must have their own signal standard.)
  • Input Volume - 0 seemed to work fine for me, but if your callers complain they can’t hear you, try bumping this a number or two.
  • Output Volume - I found 3 or 4 to be a comfortable setting. Note that your preference here may in part depend on the phone you are using, but if you are having trouble hearing the people you are talking to (or if they come through too loud), this is the setting to tweak.

I didn’t touch any of the other settings on this page. Remember to click “Apply”, and then don’t forget to save your configuration! EDIT: After originally posting this article, I was informed that there are now additional CODEC settings on the page that are in the newest firmware, so I went and grabbed that firmware from Atcom’s web site, uploaded it, and this is what the page looks like after configuration and with the additional CODEC settings:

Atcom AG-188N DSP configuration screen - updated firmware

Atcom AG-188N Audio configuration screen - updated firmware

Now I could receive incoming calls, and I could place some outgoing calls. I say “some” because I still needed to make some adjustments for dialing out (those will be covered next).

So, how did it work? Wonderfully! Calls are at least as clear as any other adapter I’ve used. I have a friend who calls me frequently, and he just happened to call while I was setting this up, so when I got it configured I transferred his call to this adapter and he said that I sounded better than on the original connection (which was another phone that’s connected to a Linksys PAP2). On my end, once I had turned up the volume a bit as shown above, he sounded great as well - certainly as good as any other VoIP or landline connection I’ve ever used, and perhaps even a bit better. My friend also said that he didn’t notice the little bit of echo “tail” that he occasionally hears from my end when we use the other phone and adapter - granted, that may be a configuration issue on the PAP2, but it’s worth noting that this unit seems to be performing better in that regard right out of the box. I would certainly have no reservations about recommending this unit to someone based on audio quality.

So you may be asking, have I found anything not to like so far? Well, only one very minor thing, maybe. The “wall wart” power supply that comes with the unit has the following specifications:

  • Input: 100-240V~50-60 Hz 0.18A
  • Output: 12 volts - 0.5 A
  • Has FCC and UL certifications

It’s a rather small unit, typical of a “wall wart” except for one thing - when connected to the AG-188N and plugged in, it gets a little bit warmer than I’d expect - sometimes. Yesterday, it seemed to be running a little warm, not “burn your hand” warm or anything like that, but definitely the warmest of the dozen or so “wall warts” in my immediate vicinity. I then unplugged it overnight, and after reconnecting it this morning (and leaving it plugged into the wall but not connected to the adapter for an hour or so, during which time it ran cool as a cucumber), today it seems to be only about as warm as some of the others, maybe even not quite as warm as a couple of them. So what changed - my sense of touch, or did the actual amount of heat produced decrease? Is the AG-188N drawing less current today? Did the fact that I plugged it into a different outlet on my UPS make some difference? Was I just oversensitive to temperature last night? I dunno, and it may remain one of the mysteries of life. :) Anyway, it’s not something I’m really concerned about.

EDIT: In hindsight, perhaps I should have been concerned. About seven months after I wrote this review — on the day after Christmas (a.k.a. Boxing Day), to be exact — I noticed that none of the LED’s were lit on the adapter, that the phone that was plugged into it was dead, and that the “wall wart” was now stone cold. I grabbed another, similar power supply that I happened to have lying around, except this one is rated for 1 A instead of 0.5 A, and connected it up and the adapter sprang back to life.  I note that the 1 A unit runs at about the same temperature as other “wall warts” nearby (a bit warm, but much cooler than the original unit), so that makes me suspect that the 0.5 A supply might be just a bit undersized, although it’s also quite possible that I just got a defective one. By the way, the replacement “wall wart” came from a VoIP adapter someone had given me that was useless to him because it was “locked” to a particular provider (and unlockable, as far as anyone knows).  I always tell people, if you are ever going to throw out a piece of electronic equipment, at least hang onto things like power supplies and cables - you just never know when they might come in handy!

Next up, we take on outbound dial plans, and maybe more… stay tuned!

Disclosure: CIGear provided me with an Atcom AG-188N for review purposes, and allowed me to keep it after I was finished writing this series, and for that I am most grateful.

Previous Installment | Next Installment

Articles in the series: Review of Atcom AG-188N IAX+SIP ATA (VoIP adapter)

Part 1 – The unboxing
Part 2 – Initial setup using IAX
Part 3 – Setting the time and configuring outbound dialing
Part 4 – Setting up SIP, and securing the adapter
Part 5 – Networking and Internal Router
Part 6 – Final Thoughts and Summary Review
Part 7 – Addendum


Jun 03 2009

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

Category: Asterisk, General, Networkingmichigantelephone @ 12:53 pm

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 firewall that just doesn’t play well with SIP. If you have any doubts that this is a real issue, Google the phrase “one-way audio.”

The crux of the problem is that SIP uses a wide number of ports, and unless you get everything set up exactly so at both ends, you may find that although the VoiP adapter will register with the server, when you actually attempt to place a call it will go through but neither party will be able to hear the other, or more commonly, only one party will be able to hear the other.

It’s an especially frustrating problem for VoIP providers, because a certain number of customers — we don’t know how many, because it’s not the sort of statistic providers like to report — cancel their VoIP service because they just can’t get it working in the first place, and the one-way audio probably certainly must account for a not-insignificant percentage of those cancellations.

There is another protocol that Asterisk supports, called IAX (actually it’s now up to IAX2, but we’ll just call it IAX to keep things simple). It works quite well in “difficult” situations because it only uses ONE port for all information. Therefore, if you can see the device register on your Asterisk system, you know that you’re also going to get audio. Assuming you don’t have problems with excessive packet loss or something of that nature, an IAX connection will almost always work, even if the end user is behind some sort of funky router (or even a chain of routers). The main reason that IAX hasn’t been more widely used is that there has been a real lack of decent ATA’s that support IAX (also, I’ve heard some comments that it doesn’t “scale” well in very large installations, but unless you plan on competing with one of the large commercial VoIP providers, I wouldn’t worry about that). For a while, Digium (the company behind Asterisk) made a unit called the IAXy, but like much of the hardware that Digium sells it was priced just a tad on the high side, and everyone was looking for a less expensive solution, so SIP-based ATA’s have become the norm.

But that doesn’t mean that the need for a decent IAX-based adapter has gone away. Just about every Asterisk system administrator has run into one or two “tough cases” where SIP just wasn’t cutting it, and if they did manage to resolve the issue they probably acquired a few grey hairs in the process. If you are the administrator of an Asterisk system, perhaps you’d just like to be able to pre-configure an ATA before sending it to someone that’s doing some off-site work for you, and know that when they receive it they can plug it into whatever crappy old router they happen to have and it’s probably going to work — right out of the box, with no frustrating hours of “… try changing this setting …” as you burn up cell phone minutes.

Recently I became aware of the fact that there’s an adapter available that can communicate using both IAX and SIP, and it even has both a WAN and a LAN port so that if the end-user doesn’t even have a router, they can plug this unit into the cable or DSL modem, and then plug their computer into the LAN port on the adapter and both will work. I made arrangements to obtain a unit for review purposes, and in the coming days I plan to tell you more about this device. It’s called the Atcom AG-188N and it’s sold in North America by CIGear. Just to give you a small preview, here are a few “unboxing” pictures. The small box below came inside a larger carton with all the requisite packing peanuts, but I’m not a “pro” at making these photos (a couple came out way too blurry to use) so I decided to just show you the interesting part:

Good things come in small packages

Good things come in small packages

Out of the carton

Out of the carton

Contents of the box, without the bubble wrap

Contents of the box, without the bubble wrap

Closeup of the AG-188N, sorry it's a bit blurry

Closeup of the AG-188N, sorry it's a bit blurry

The back side, showing the connections, from CIGear's web site.

The back side, showing the connections, from CIGear's web site.

EDIT: Since I first posted this review I’ve since found out that the particular unit I received had been previously used on a demo and therefore had been repackaged. Normally the power supply comes in a small white box, not wrapped in bubble wrap. Since I had specifically asked for a unit for review purposes, it doesn’t bother me at all that I received a unit that is new for all intents and purposes, but can’t be sold as new - that’s the perfect unit to send to a reviewer.

Note that the yellow ruler doesn’t come with the unit, it’s just a 7″ ruler I had lying around that I put in the pictures to give you an idea of relative sizes. Actually, if you set this unit next to a Linksys PAP2 you’d be very hard-pressed to tell any difference in the size. One thing notably missing from the contents of the box: A network cable. If you were going to buy these in quantity to send out to users, you’d probably also want to obtain some some network cables in bulk, so you could throw a cable in with each shipment, because for every guy like me who’s somehow obtained a small surplus of them, there will always be the folks that only have ONE network cable to their name.

One thing you may notice in the last image above is that there is a phone port and a PSTN (telephone company line) port. Yes, that does mean that this is a single line unit. But, don’t get the idea that because there is a PSTN port, that this is the full equivalent of something like a Sipura SPA-3000 or Linksys SPA-3102, because it isn’t — the PSTN port is a “passthru” port, allowing you to send some calls to the PSTN and others to your VoIP provider based on the pattern dialed, and letting you receive calls from both the PSTN and your VoIP provider without the need use two separate telephones. The difference between this and one of the aforementioned Linksys/Sipura boxes is that you can configure the Linksys/Sipura’s PSTN port to be a trunk on the Asterisk server (essentially an FXO port), and that particular functionality is not included with this unit.

EDIT: The above paragraph was edited slightly after receiving some clarification from CIGear — they also offered this additional information: With one phone hooked to the ‘phone’ jack, you can dial a star code to access the PSTN line instead of the SIP/IAX configured on the ATA. So, one analog phone enables you to use either SIP/IAX or the PSTN. However, people using the ATA with Asterisk have a problem when they want to dial Asterisk * codes like *97 for voicemail (as the * takes you to PSTN). The solution is to delete the “lifeline *T” option from “Dial-Peer” menu (this gets a bit into configuration, which will be discused much more thoroughly in upcoming posts).

Of course, you don’t HAVE to connect a PSTN line to this unit, and you don’t HAVE to connect a computer to the LAN port — I have used it successfully tonight without doing either. Ah, but I’m getting ahead of myself a bit - more on that in the next installment, after I’ve had some time to spend working with the unit and reading the documentation (yes, I did get it working mostly without referring to the documentation, so for those who hate wading through documentation, fear not — it’s really not difficult to set up)!

Disclosure: CIGear provided me with an Atcom AG-188N for review purposes, and allowed me to keep it after I was finished writing this series, and for that I am most grateful.

Next installment

Articles in the series: Review of Atcom AG-188N IAX+SIP ATA (VoIP adapter)

Part 1 – The unboxing
Part 2 – Initial setup using IAX
Part 3 – Setting the time and configuring outbound dialing
Part 4 – Setting up SIP, and securing the adapter
Part 5 – Networking and Internal Router
Part 6 – Final Thoughts and Summary Review
Part 7 – Addendum


Jun 01 2009

Sutus BC200: All-In-One Small Business IT/Telecom Solution

Category: Asterisk, General, Networking, VARkashan @ 5:52 pm

The Sutus Business Central 200 or BC200 is way more than a phone system. It offers an integrated solution to small business IT and communications. The BC200 server includes: phone system, file server, email server, router, firewall, wireless access point, VPN remote access server, automated backups, VoIP and Standard phone line support and more. The BC200 is a complete IT and communication solution for up to 25 users.

Cost Savings: Compared to buying components separately, the BC200, being a single appliance, dramatically reduces the total cost of ownership including purchase, training, support, ongoing maintenance, and upgrade costs.

Simple and Easy to support: The BC200 delivers advanced management functionality for all the integrated applications in a single, workflow-based interface. The BC200 is secure and easy to support - with remote management and upgrades.

What’s required? The Business Central solution comes in a compact bundle consisting of the BC200 server/router and a PSTN gateway (The Gateway 310). The only other parts required are Polycom IP phones. The BC200 works with Windows, Mac and Linux environments. You can continue to use the email and file browsing applications you are familiar with.

Key Features

Here are some of the important features of the Business Central 200:

Phone Services

  • Enterprise Class Telephone Support
  • Voicemail to Email
  • Auto Attendent
  • Standard Phone Line Support
  • VoIP Phone Line Support
  • Shared Call Groups
  • Custom Call Routing
  • Hold, Transfer, Speed Dial, Conferencing
  • Audio on Hold
  • Program quick dial numbers for your Polycom phone through a web browser

Network Infrastructure

  • WiFi Wireless Access Point 802.11 b/g
  • 8 Port PoE 10/100 Router
  • NAT + SPI Firewall
  • VPN Remote Access
  • Intelligent Fax Routing
  • GigE 10/100/1000 Expansion Port
  • Domain Controller
  • Standards Based Infrastructure

Data Services

  • File Server
  • Email Server
  • Robust, Journaled File System
  • Secure file storage for users and groups
  • Automated Backups
  • RAID 1 (Disk Mirroring) Support
  • 2 X 250Gb Hard Drives
  • Intranet Server

Security

  • NAT
  • Stateful Packet Inspection Firewall
  • Secure IMAP Client Support
  • Secure SMTP Email Support
  • Single Services Sign On
  • Robust Reboot and Recovery

Here are some interesting product reviews to check out:

Dec 2008: ITBusinessEdgeSutus Product Review

Nov 2008: GetConnectedSutus Product Review

Nov 2008: ISP-Planet - A Small Business VoIP Box

Sutus Business Central BC200 is available through CI Gear. For more product information or to purchase a BC200, visit:

http://www.cigear.com/sutus-phonedatanetwork-system-c-156.html

Tags: , , , , , , , , , , , , , , , , , ,


May 22 2009

Problem with Realtek LAN Card and the Solution (Elastix/Atom)

Category: Asterisk, GeneralFarhan Sabir @ 5:47 pm

I had the same problem with a ELX-3000. The appliance use a ATOM and a RealTek Lan IC.

I simply did what was posted another site…..

****************

Atom and r8101E driver

To get the Atom box to work this is what I did.
Grab a USB key drive.

Go into the BIOS and disable the card and reboot.

Once running download the driver from and copy to USB key drive.

downloadcenter.intel.com/Detail_Desc.asp…ductID=2916&D…

Compile the driver by following the directions in the file downloaded.

Remove the r8169 driver completely, this is the reason that this and all other r8169 based systems will not boot the iso.

reboot into the bios and enable the card.

I pointed this issue out months ago to everyone when I still worked on this project. This is one of the main reasons that I would not update the kernel since this module was completely borken in a lot of distros. Here is a link from Intel that shows which distros have issues with this driver. Try booting a standard CentOS 5.2 disk on a r8169/r8101/etc.. based system and see what happens. It will kernel panic, just like the new 2.6.2 iso will.

http://www.intel.com/support/motherboards/desktop/d945gclf/sb/CS-...

**************

It worked for me…I hope it does for you…

Guy

[Originally posted by Guy Beaupre of abaplab.com on April 24, 2009]

Tags: , , , , ,


Mar 12 2009

Sangoma: Linux Beta Driver - Wanpipe 3.3.16 Release

Category: Asterisk, NetworkingFarhan Sabir @ 11:07 am

Sangoma has released a new 3.3.X series driver.

Sangoma Linux 3.3.16 Driver Location
http://wiki.sangoma.com/wanpipe-linux-drivers

This is the last 3.3.X Beta driver
By next week this driver will be renamed as new STABLE 3.4.1

The new beta 3.5.1 driver will be released by next week.

* Mon Mar 11 2009 Nenad Corbic - Beta - 3.3.16
=====================================================================

- Fixed S514 2 Byte receive

- A14X Serial Driver Update
Added clock recovery option
Added control of DTR/RTS on startup using
DTR_CTRL and RTS_CTRL config variables.

- AFT T1/E1 BERT Feature
Ability to run Bert tests on T1/E1 cards using wanpipemon

- AFT HWEC
Hardware DTMF detection now detects FAX tones as well,
and passes then up to Zaptel/Asterisk

- PPP Protocol
Added option to disable MAGIC number in negotiation
Set MAGIC_DISABLE=YES in ppp profile section.

- Updates for new 2.6.X kernels
Added queue check on shutdown
Support for latest 2.6 kernels

- Updated T3/E3 Code
The T3/E3 dma logic had a bug that was demonstrated under
high load. Was introduced in 3.3.15 release.

- Added hardware probe DUMP
wanrouter hwprobe dump
To be used by developers to easily parse the hwprobe output

- ADSL Update
Bug fix in adsl. Could cause period disconnects on
some equipment. The SNR value was not being properly reported
the the upstream.

SANGOMA NEWS UPDATE - 20090312

Tags: , , , ,


Dec 31 2008

Software phone systems can save you money!

Category: 3CX, Asterisk, Generalkashan @ 7:26 pm

For decades, a handful of giant manufacturers have maintained a virtual monopoly in the SMB phone systems market. This has resulted in expensive, proprietary technology that was difficult to manage and costly to maintain. By some estimates, only a third of small businesses have implemented phone systems for these reasons. This leaves the majority of this segment underserved!

Introducing the software pbx or phone system. A software phone system is an application designed to perform all the features of a purpose built pbx but built to run on standard computer hardware. Since software phone systems can be installed on commonly available computers, much of the cost associated with proprietary phone system hardware has been eliminated, which means software phone systems save you money!

Most phone system solutions available today are based on Voice over IP (VoIP). This does not mean that these systems will not connect with traditional phone services. In fact, the majority of phone systems available today support both traditional phone lines as well as VoIP.

Here are the 4 key ingredients required to build your own phone system.

1- Computer Hardware

2- Phone System Software

3- Phones

4- Gateways

Computer Hardware

Selecting suitable computer hardware is an important factor since your new phone system will depend on a reliable platform to run on. If your phone system project is for play, any reasonably equipped computer will do. If your phone system implementation is intended for business use, it would be wise to check with your software provider for recommended hardware products. For mission critical enterprise applications, a hardened server is highly recommended.

Software

Selection of software depends as much on personal preference as it does on features and capability. Some users are more comfortable working in a Windows environment while others are comfortable with Linux or Mac OS X. There are software based phone system solutions available for just about any platform. Most of these solutions are easy enough to install and manage and offer a plethora of features and functionality.
Since the defacto industry standard for voice communication these days is Session Initiation Protocol (SIP), software selected should support SIP.
Without delving into a detailed feature listing (We’ll save that for another article!), here are some of the more popular features that most people look for in a new phone system:

1-    Call Handling (Hold, Transfer, Conference, Forward, Park, Auto Attendant, Digital Receptionist, IVR, etc.)

2-    Unified Communication and Mobility (User Portal, Voicemail to Email, Unified Messaging, Single Number, Remote Access, Soft Phone, etc.)

3-    3rd Party Application Integration (Outlook, Salesforce / Web-based CRM, Exchange, Fax, etc.)

4-    Management (Web based Configuration, Backup/Restore, Call Logging/Reporting, etc.)

5-    SIP Trunk (VoIP) support to connect to one or more ITSPs (Internet Telephony Service Provider)

Windows based phone systems: 3CX, pbxnsip

Linux based phone systems: Asterisk, Elastix, Trixbox

Mac OS X based phone systems: pbxnsip

Phones

The phone is the interface between your end users and the system so factors such as ease of use, end user features, aesthetic appeal, call quality, ease of support should be considered when choosing phones. There are 3 major categories of end user devices that will work with your new system:
1-    Hardware IP Phone (Desk Phone, Wireless Phone, Conference Phone, etc.)
2-    Software IP Phone (PC/Mac Software Client, Smart Phone Mobile Client)
3-    Traditional Analog Phone via ATA (Analog Terminal Adapter)

There is no shortage of options when it comes to phone selection. Check with the software provider, your vendor and user forums for recommended models before deciding on what phones to order.

Gateway

A gateway is a device used to connect your VoIP based phone system to the public telephone network. Without a gateway, most SMB phone systems are still able to connect to the outside world using a SIP (VoIP) trunk. The SIP trunk connects your phone system to an ITSP (Internet Telephony Service Provider) who then relays your calls to and from the public telephone network. However, using only VoIP means that you are entirely dependant on your Internet connection to for phone access to the outside world.
The gateway enables you to connect analog POTS lines (Plain Old Telephone Service) or digital ISDN BRI and PRI (T1/E1) lines directly to your phone system. You can continue to take advantage of VoIP but also keep some direct connectivity to the public telephone network for reliability and failover.

Here are some of the options available when it comes to gateways.
1-    PCI Telephony Cards
2-    External Ethernet Gateways
3-    External USB Gateways

PCI Telephony Cards: There are PCI and PCIe based telephony cards available for a variety of platforms that will enable you to create your own gateway for your phone system. If you are comfortable installing hardware in your computer, this may be the simplest and most cost effective solution for you. If you’re not sure about getting under the hood of your system, this might not be the best solution for you.

External Ethernet Gateways: There are many external Ethernet based gateway devices on the market that will enable you to connect with a variety of telephony interfaces. These gateways are network devices that connect with all your phone lines and communicate with your phone system over Ethernet.

External USB Gateways: Some platforms support external USB based gateway devices that will enable you to connect with a variety of telephony interfaces. USB gateways are like peripherals that interface with your phone system on a USB port. These gateways also support a variety telephony interfaces for your phone lines and analog devices.

If you have a question or are just looking for help with planning your ideal software based phone system, feel free to comment on this post or call me at 1-866-924-4292.

Tags: , , , , , , , , , , , , , , , , , , , , , ,


Nov 20 2008

Elastix Workshop and Presentation in Toronto

Category: Asteriskkashan @ 10:25 pm

Jose Landivar, one of the founders of Elastix will be hosting a workshop and presentation on Wednesday, November 26th, 2008 in Toronto.

Elastix is an asterisk-based linux appliance that integrates the best tools available into a single, easy-to-use interface. It also adds its own set of utilities and allows for the creation of third party modules.

From 5pm to 7pm, Jose will be hosting a free “Getting Started” workshop on Elastix. Those interested in participating should bring a laptop capable of running vmware player and associated cables for power and networking.

From 7pm to 8pm, Jose will discuss how Elastix differs from other Asterisk-based distributions. He will also discuss the road map for the Elastix project.

Location

Committee Room 3
North York Civic Centre (in Mel Lastman Square)
5100 Yonge St.,
North York, ON
(Google map link)

See you there!

Kashan Chaudhry

CI Gear

Tags: , ,


Nov 14 2008

High-Availability/Failover Asterisk clusters

Category: Asteriskkashan @ 9:36 am

If you use PRIs and are looking to create a reliable, fault tolerant, highly available system with Asterisk, the foneBRIDGE by Redfone is a solution worth looking into. The foneBRIDGE provides quick, reliable and robust T1/E1 fail-over allowing IT Managers and System Integrators to implement Asterisk in the most demanding of environments where downtime simply can not be tolerated. The foneBRIDGE is now available in a 1U Rack Mountable Enclosure that supports upto 8 T1/E1 interfaces.

High Availability

The general objective of deploying HA (High-Availability) in a server environment is to provide reliability, availability, and serviceability (RAS). In the traditional Asterisk implementation model, T1/E1 connectivity is provided by PCI based interface cards on a single server. In this scenario the systems overall integrity and availability is limited by the reliability of that single server. For many businesses, taking this gamble on a mission critical function such as voice is unacceptable.

As an externalized point of T1/E1 termination, the foneBRIDGE is decoupled from the single server limitation and when combined with the proper tool set can be implemented to provide rapid and automatic failover amongst a cluster of servers.

The most common tool set used to provide this functionality when paired with the foneBRIDGE and Asterisk is the ‘heartbeat’ tool from the Linux-HA project www.linux-ha.org. As the name employs, ‘heartbeat’ monitors the state of 2 or more nodes (servers) in an Asterisk cluster. If it detects a fault, for example when a primary node stops responding to the heartbeat messages it executes scripts that allow it to quickly failover to a secondary server. All of this is done transparently and without user intervention.

Rapid Recovery

With the foneBRIDGE, rapid failover and system recovery can occur in seconds, not minutes or hours. Through the foneBRIDGEs’ rapid re-configuration options, it can be programed on the fly through high availability tools to begin routing the TDM stream and calls to a secondary standby server in under one second. Add to that the short amount of time it takes the server to start Asterisk and clear circuit alarms and your stand-by server can be operational and handling calls in under 3 seconds, all transparently and without administrator intervention.

Uptime During Maintenance and Upgrades

Over are the days when it was necessary to bring down a server for patching or software upgrades. With foneBRIDGE, the server admin can manually failover to a back-up server and maintain the voice system operational while performing upgrades or patching on the primary server. This unique feature also lends itself nicely to the ability to failover to a server where production testing can be done on new code releases or features and in the event of a bug discovery or issue that may jeopardize the integrity of operations the system admin can easily fail back to a primary server with only seconds of downtime.

Scalability

With connectivity externalized, and placed on the Ethernet not tied to any PCI card or single server, adding additional T1/E1 capacity to an Asterisk implementation is simplified and can be realized with little or no downtime to operations.

For more information, visit the foneBRIDGE product page

Tags: , , , , , , , , , , ,


Nov 10 2008

Sangoma NetBorder Express VoIP Gateway

Category: Asterisk, Response Point, VARkashan @ 9:19 am

Last month, Sangoma launched the the NetBorder Express VoIP Gateway product line. NetBorder Express is a SIP to TDM Gateway on a card. It is a full-fledged VoIP Gateway to connect Legacy Networks to SIP and VoIP Networks.

NetBorder Express is a “ready to go” solution—much like an external gateway, but it also provides the flexibility of building your own gateway. It offers easy integration into your own application for installation, configuration and management, plus it can be installed in the same computer server.

Empowered by Sangoma’s NetBorder Express Software, NetBorder Express TDM to SIP Gateway Cards include G.168 Telco-Grade Echo Cancellation with 128 ms echo tails without call capacity reduction to provide optimum operating conditions for applications, such as Speech Recognition IVRs and International Toll Bypass. NetBorder Express cards also feature Sangoma’s award-winning field upgradeable crashproof firmware design.

NetBorder Express communicates with applications such as IP-PBXs, Speech Enabled IVRs, Conferencing Servers, Contact Center or Trunking Gateways directly with the ubiquitous SIP control protocol to reduce deployment time, complexity and cost for next generation network application deployments.

Available in one to eight ports of T1/E1, NetBorder Express Gateway Cards are an excellent value for installations ranging anywhere from 24 to 240 simultaneous calls. For larger systems, several gateway cards can be combined in the same server to support up to 960 simultaneous calls. (Analog and ISDN BRI Gateway cards are coming soon.)

Platforms
For now, this solution is for Windows only. Compatibility testing is currently being finalized with a number of industry-leading Windows-based IP PBX application developers. Watch for the news as it is released for compatibility.

A port to Linux is also being worked on so that it will also be Asterisk and other linux application compatible for those of you who are most comfortable in that market, but an ETA for this project has not been finalized.

Check out the NetBorder Express products page.

Tags: , , , , , , , , , , , , , ,


Next Page »