Howto:VoIP-Telecom - SIP Provider Compatibility Test: Difference between revisions

From innovaphone wiki
Jump to navigation Jump to search
No edit summary
Line 1: Line 1:
{{Template:3rd Party Input}}'''Voip-Telecom innovaphone Compatibility Test Report'''
'''Voip-Telecom innovaphone Compatibility Test Report'''


== Summary ==
== Summary ==

Revision as of 10:32, 25 July 2011

Voip-Telecom innovaphone Compatibility Test Report

Summary

SIP Provider: VoIP-Telecom

The provider supports all required innovaphone features and is therefore qualified as recommended SIP Provider.

That beeing said, the provider has achieved 97,5% of all possible test points. For more information on the test rating, please refer to Test Description

The Provider have NAT Detection system so we don't need to use STUN Server to work with. It's recommended to use media-relay to guarantee that there is no problem with media in some type of calls (like external transfers).


  • Features:
    • Direct Dial In
    • Fax over IP (T.38)
    • DTMF
    • NAT Detection
    • Suppress the Number if Requested.


  • Supported Codecs by the provider
    • G711
    • G729
    • G723
    • T.38 UDP

Current test state

This product is being tested right now. The test is not yet completed.


Testing Enviroment

Scenario NAT

HFO SIP Compatibility Test 5.PNG

This scenario describes a setup where the PBX and phones are in a private network. The IP800 should use a stun server, in order to send correct SIP - messages. The IP800 works as media relay, all RTP - streams go through the PBX.

Test Results

For more information on the test procedure, please read the following wiki article: SIP Interop Test Description. Bold lines in the test results indicate a KO-criteria.

Voip-telecom SIP Compatibility Test 2.png


Configuration

Firmware version

All innovaphone devices use V9hf1 build 90600.01 as firmware.

SIP - Trunk

Voip-telecom SIP Compatibility Test 3.png

Number Mapping

Voip-telecom SIP Compatibility Test 4.png

Route Settings

Since the Provider support Overlap sending there is no need to use "force enblock" option in the routes. We recommend the use of "Interworking QSIG/SIP" option in the routes.