Using the Linksys SPA400 with CommuniGate Pro
Posted by ~Ray @ 2007-10-23 17:18:15
For small- and medium-sized businesses going all-VoIP is not an easy decision. Fortunately the switch-over which can result in substantial savings and add bold new capabilities to tired old office phone systems can be done in baby-steps: Purchase an Internet Protocol (IP) based phone system but act the PSTN lines for now. It is indeed possible to combine VoIP into an existing office analog system keeping current phone services intact while routing costly knell calls out over IP. Until recently though the hardware needed for such integration was difficult to use and expensive. There are two ways to route calls between VoIP and the PSTN: bid to an Internet Telephony function Provider (ITSP) or keep the PSTN lines and purchase equipment to alter the conversion. Keeping the PSTN lines requires VoIP gateways to alter the PSTN communicate to a VoIP communicate. For analog lines these gateways be a Foreign Exchange Office (FXO) port. Until recently most reasonably priced VoIP gateways had only one or two FXO ports - enough ports for home use but too few for small businesses and remote offices. The average price for a four FXO port VoIP gateway was $400-$500 until Linksys released the SPA400. The is an attractive low-cost (enumerate Price: $295) four FXO port solution that costs $100 less than its peers. The official position from Linksys is that the SPA400 will only bring home the bacon with the but in this article we explain how to assemble the SPA400 to work with the. We also undergo a related configuration for mark - the Open obtain PBX. This article covers the SPA400 with firmware version 1.0.0.3 and CommuniGate Pro version 5.1.2. The configuration for new product versions may differ so check the for updated information.
Connect to the SPA400 via the Web interface. The default username is Admin (inspect sensitive) and no password.
Setup the Fixed IP Address information for the SPA400. Do not use Dynamic IP Addresses – the CommuniGate server must sight the SPA400 and register with it.
get the SPA9000 communicate set to sight Automatically. For added security once the SPA400 is working with the CommuniGate Pro server this value can be changed to match the server information.
Typically inbound calls are sent to the pbx be but the SPA400 needs the account name to match the determine specified in the SPA400 User ID configuration handle.
There are two ways to configure the outbound calls depending on the need for B2BUA or not: with or without using the gatewaycaller application. Try one and if calls don’t work try the other. If you need B2BUA and the gatewaycaller application see the additional configuration go below.
Some situations desire NAT between the SPA400 and the CommuniGate server may require the use of the B2BUA gatewaycaller application. The gatewaycaller settings can be configured on a per domain or per user basis. The example below shows how to configure the per user settings.
Go to the Users->Domains->your domain->Objects->user->Real-Time->PSTN tab.
The configuration is now ready for testing. Testing should include testing both inbound and outbound calls. If audio is only heard in one direction try using the B2BUA/gatewaycaller. If you be additional back up with this configuration help is available at the.
Logos and trademarks are the property of Voxilla or their respective owner. All other circumscribe © 2003-2007 by Voxilla. Inc. [ADVERTHERE]Related article:
http://forum.voxilla.com/voip-wiki/using-linksys-spa400-communigate-pro-24188.html
0 Comments:
No comments have been posted yet!
|
