Howto:SPA8000 - Linksys - Testreport
Summary
Linksysy SPA8000 is a 8 port FXS - adapter. The product is compatible with innovaphone's v8 PBX software and therefore qualified as recommended 3rd. party gateway. The advanced features need some configuration changes as described in this article.
Certification Status
The tests for this product have been completed.
Testing of this product has been finalized October 12th, 2009.
Version
Firmware Version:
6.1.3
Hardware Version:
1.0.0
innovaphone Firmware:
V8
Device Setup
| Tested feature | Result |
|---|---|
| Register Device w/o specific configuration (requires DHCP) | No |
| DHCP is default | Yes |
| DHCP yields timeserver and time displays correctly | No |
| SNTP config has TZ string for timezone/dst autoconfig | No |
| DHCP yields correct default gateway | Yes |
| Device supports magic registration (e.g. by serial) | No |
| Fixed registrations works | Yes |
| Device registers w/o Extension (just by name) | Yes |
| Device registers by extension | N/A |
| Device registers with password | Yes |
| Device registers multiple identities | Yes |
| Device supports STUN protocol | Yes, not tested |
| Device sends NAT - keepalive messages | Yes, not tested |
| Device refreshes the PBX registration | Yes |
| Device supports SIP over TCP | Yes, not tested |
| Device supports SRTP | Yes, not tested |
| Device supports SIPS (SIP over TLS) | Yes |
| Device supports HTTPS | Partially, only as HTTPS client (provisioning) |
| Device supports VAD (Voice activity detection) | Yes |
Test Results
Basic Call
| Tested feature | Result |
|---|---|
| call using g711a | Yes |
| call using g711u | Yes |
| call using g729 | Yes |
| Overlapped sending | No |
| Early media channel | Yes |
| Device shows called id number | N/A |
| Device shows called id name | N/A |
| Device shows called id display info | N/A |
| Fax using T.38 | Yes |
| CGPN can be supressed | Yes |
| Reverse Media Negotiaton | Yes |
| Device shows CDPN/CGPN on incoming call | Yes |
| Device shows CDPN/CGPN on outgoing call | Yes |
| Device shows connected number | No |
| Device shows diverting number | No |
| Device supports distinctive ringing | Yes, not tested |
| Device supports asymetric codec negotiation | Yes |
| Device supports codec renegotiation during a conversation | Yes |
| Device shows correct display message in case of busy CDPN | No, it plays busy tone. |
| Device shows correct display message in case of not existing CDPN | No, it plays audio tone. |
| Device shows correct display message in case that the call is declined | No, it plays busy tone. |
| SOAP Call works? | Yes |
| Long Time Call (>30 min) works? | Yes |
| Voice Quality OK? | Yes |
DTMF
| Tested feature | Result |
|---|---|
| DTMF tones sent correctly | Yes |
| DTMF tones received correctly | Yes |
Hold/Retrieve
| Tested feature | Result |
|---|---|
| Device handles incoming hold (sendonly) correctly | Yes |
| Device can put a call on hold using correctly(inactive or sendonly) | Yes |
Transfer with consultation
| Tested feature | Voice Ok? | MoH Ok? |
|---|---|---|
| inno1 calls inno2. inno2 transfers to testphone. | Yes | Yes |
| inno1 calls inno2. inno1 transfers to testphone. | Yes | Yes |
| inno1 calls testphone. inno1 transfers to inno2. | Yes | Yes |
| inno1 calls testphone. testphone transfers to inno2. | Yes | Yes |
| testphone calls inno1. inno1 transfers to inno2. | Yes | Yes |
| testphone calls inno1. testphone transfers to inno2. | Yes | Yes |
Transfer with consultation (alerting only)
| Tested feature | Voice Ok? | MoH Ok? |
|---|---|---|
| inno1 calls inno2. inno2 transfers to testphone. | Yes | Yes |
| inno1 calls inno2. inno1 transfers to testphone. | Yes | Yes |
| inno1 calls testphone. inno1 transfers to inno2. | Yes | Yes |
| inno1 calls testphone. testphone transfers to inno2. | Yes | Yes |
| testphone calls inno1. inno1 transfers to inno2. | Yes | Yes |
| testphone calls inno1. testphone transfers to inno2. | Yes | Yes |
Blind Transfer
| Tested feature | Voice Ok? |
|---|---|
| inno1 calls inno2. inno2 transfers to testphone. | Yes |
| inno1 calls inno2. inno1 transfers to testphone. | Yes |
| inno1 calls testphone. inno1 transfers to inno2. | Yes |
| inno1 calls testphone. testphone transfers to inno2. | Yes |
| testphone calls inno1. inno1 transfers to inno2. | Yes |
| testphone calls inno1. testphone transfers to inno2. | Yes |
Blind Transfer (alerting only)
| Tested feature | Voice Ok? |
|---|---|
| inno1 calls inno2. inno2 transfers to testphone. | Yes |
| inno1 calls testphone. testphone transfers to inno2. | N/A |
| testphone calls inno1. inno1 transfers to inno2. | Yes |
Broadcast Group & Waiting Queue
| Tested feature | Result |
|---|---|
| testphone makes call to a Broadcast Group. inno1 picks up. | Yes |
| inno1 makes call to a Broadcast Group. testphone picks up. | Yes |
| testphone makes call to a Waiting Queue. inno1 picks up before announcement is played. | Yes |
| testphone makes call to a Waiting Queue. inno1 picks up after announcement is played. | Yes |
| inno1 makes call to a Waiting Queue. testphone picks up. | Yes |
Advanced Features
MOH Server
The SPA8000 can work as Music on Hold Server for its own FXS ports but also as MOH source for external devices. This feature was tested successfully but requires adjustments to the SIP default settings of the SPA8000.
Voicemail
The SPA8000 can be used with the innovaphone Voicemail. MWI indications are received at the corresponding analog device and are signaled using a stutter dial tone. This feature was tested successfully but requires adjustments to the codec default settings of the SPA8000.
Provisioning
The SPA8000 can retrieve configuration and firmware files using TFTP, HTTP, and HTTPS. As a result, the CF card can be used for provisioning purposes. In contrast to innovaphone devices, the HTTP Update Server URL can not be distributed via DHCP. Therefore a staging mechanism must be used for initial deployment. A TFTP server will answer the initial request of the SPA8000 offering the HTTP URL to the innovaphone device (with CF) containing the device specific configuration files.
NAT
The SPA8000 uses besides the STUN protocol, NAT Keep-Alive mechanism compatible with innovaphone. Therefore the device can be installed behind a NAT router.
DTMF Feature Codes & Vertical Service Activation Codes
All service codes were tested successfully. The Linksys Activation Codes offer also a possibility to configure Call Forward. However it is recommended to use instead the according innovaphone DTMF feature code. In Case that Linksys Cfwd Codes are used, the innovaphone PBX will not be notified about a active Call Forward situation. This will result in unexpected call flows and should not be used.
When using a Linksys adapter instead of an innovaphone a/b interface, the following interface features will miss:
- Set Pin
- Lock/Unlock
- Do not Disturb internal calls
- Do not Disturb external calls
- Clear Local Settings
- Logout User
- Local Clear of MWI
In contrast to this, you have the following additional service codes when using a Linksys adapter.
- Call Return - This code calls the last caller.
- Call Redial - Redials the last number called.
- Blind Transfer - Begins a blind transfer of the current call to the extension specified after the activation code.
- Call Forward Last - Forwards the last inbound or outbound calls to the extension specified after the activation code.
- Block Last - Blocks the last inbound call.
- Accept Last - Accepts the last outbound call. It lets the call ring through when do not disturb or call forwarding of all calls are enabled.
- Call Waiting per Call - Enables call waiting for the next call.
- Block CID - Blocks caller ID on all outbound calls.
- Block CID per Call - Blocks caller ID on the next outbound call.
- Block ANC - Blocks all anonymous calls.
- CID Activate - Enables caller ID generation.
- CID Deactivate - Disables caller ID generation.
- Distinctive Ring - Enables the distinctive ringing feature.
- Speed Dial - Assigns a speed dial number.
- Secure Calls - Makes all outbound calls secure (not tested, probably SIPS & SRTP).
- Conference - The user must enter the code before dialing the third party for a conference call.
- Attended xfer - The user must enter the code before dialing the third party for a call transfer.
- modem line toggle - Modem pass-through mode can be triggered only by pre-dialing this code.
- fax line toggle - Toggles the line to a fax machine.
Conference
The SPA8000 is able to do a 3 party conference(using maximal 2 FXS ports). In case that more participants are required an external Conference Server can be used. The innovaphone Conference Object can be used as External Confernce Server for the SPA8000.
Configuration
innovaphone configuration
Add a new PBX object of type "user" for each FXS port.
3rd party product configuration
To register a FXS port at the innovaphone PBX, go to the respective Line tab (e.g. L1) and configure the settings previously used when creating the PBX User. As Proxy enter the IP address of the innovaphone PBX.
Additionally, for enviroments were exclusive codecs are configured, the Release Unused Codec must be set to No.
Fax
In order to receive incoming fax calls using T.38, configure in the respective FXS Line settings the option FAX Passthru Method to None.
MoH Server
If the Music on Hold feature of the Linksys device should be used, the feature Streaming Audio Server (SAS) must be activated. The SAS is activated at the FXS port streaming the Music on Hold. The maximum amount of concurrent Music on Hold channels is limited to 10 calls. In order to allow the SPA8000 to play MoH using an innovaphone PBX, the SIP setting RFC 2543 Call Hold must be changed to No.
The remaining FXS port will enter the User ID used at the SAS port as MOH Server.
Voicemail
If the Voicemail feature of the SPA8000 should be used with the innovaphone VM, the Voice Mail Server setting must be configured with the SIP URI of the Voicemail account (e.g. 736@172.16.3.63 = VM-nr.(73) + User-nr.(6)@ip-address of PBX). The default codec used by the SPA8000 is G711u. This will result in problems when using the standard innovaphone VM-files. To circumvent this problems configure the Preferred Codec as G711a.
NAT
In case you have to pass a NAT router to reach your PBX, the NAT keep - alive mechanism must be enabled for the respective line. This should suffice in most installations, if not have a look at the SPA8000 manuals at the topic regarding NAT traversal and activate STUN.
