Howto:Xtratelecom - Trunk SIP - SIP Provider Compatibility Test: Difference between revisions

From innovaphone wiki
Jump to navigation Jump to search
No edit summary
Line 4: Line 4:


'''SIP Provider: Xtratelecom'''
'''SIP Provider: Xtratelecom'''
<!--
The provider supports all required innovaphone features and is therefore qualified as [[Howto:What_is_a_%22recommended_product%22%3F#SIP_Provider|recommended SIP Provider]].


The provider was tested by our partner ''Makenai Solutions, Innovation & Creative Ideas''. This product is listed due to a customer testimonial. No tests have been conducted by innovaphone.


...
The provider supports all required innovaphone features and is therefore qualified as [[Howto:What_is_a_%22recommended_product%22%3F#SIP_Provider|recommended SIP Provider]].  
 
That being said, the provider has achieved x% of all possible test points. For more information on the test rating, please refer to [[Howto:SIP_Interop_Test_Description#|Test Description]]
-->
<!-- Mention all important tests that were not passed in the summary.
 
E.g. in case that the provider doesn't support Reverse Media-Negotiation, mention in the summary that media relay and an exclusive coder setting must be configured:
 
Since the provider doesn't support Reverse Media negotiation, media relay and an exclusive coder setting must be configured. Opposed to a SIP trunk not needing Media-Relay, the transport of all RTP packets by the gateway will result in a higher CPU load for a call. As a result, the amount of concurrent calls is considerably lower compared to a SIP-Provider that doesn't require Media-Relay.
-->


The provider doesn't support Reverse Media negotiation, so media relay and an exclusive coder setting must be configured.
The provider doesn't support Reverse Media negotiation, so media relay and an exclusive coder setting must be configured.
Line 25: Line 15:
Fax is supported, but it needs an extra SIP trunk in the PBX side pointing to a different IP. Xtratelecom defines it as a service called 'Endpoint de fax' that needs to be purchased separately.
Fax is supported, but it needs an extra SIP trunk in the PBX side pointing to a different IP. Xtratelecom defines it as a service called 'Endpoint de fax' that needs to be purchased separately.


<!-- in case of customer testimonial, please make sure that the fact that it is not tested by innovaphone is also mentioned in the summary-->
That being said, the provider has achieved 90% of all possible test points. For more information on the test rating, please refer to [[Howto:SIP_Interop_Test_Description#|Test Description]]
<!--
 
* Features:
* Features:


Line 36: Line 26:
** G711
** G711
** G729
** G729
** G723
** G726
** T.38 UDP
** T.38 UDP
-->


== Current test state ==
== Current test state ==


<!--{{Template:Compat Status "planned"}} -->
<!--{{Template:Compat Status "planned"}} -->
{{Template:Compat Status "in progress"}}
<!-- {{Template:Compat Status "in progress"}} -->
<!-- {{Template:Compat_Status_"referral_prod."|certificate=Tpl_sip.business_Toplink_SIP_Provider_-_product-cert.pdf}} -->
{{Template:Compat_Status_"referral_prod."|certificate=Xtratelecom_-_Trunk_SIP_-_SIP_Provider_-_product-cert.pdf}}
<!-- {{Template:Compat_Status_"engineered_prod."|certificate=Tpl_sip.business_Toplink_SIP_Provider_-_product-cert.pdf}} -->
<!-- {{Template:Compat_Status_"engineered_prod."|certificate=Tpl_sip.business_Toplink_SIP_Provider_-_product-cert.pdf}} -->
<!-- {{Template:Compat_Status_"rec._prod."|certificate=Tpl_sip.business_Toplink_SIP_Provider_-_product-cert.pdf}} -->
<!-- {{Template:Compat_Status_"rec._prod."|certificate=Tpl_sip.business_Toplink_SIP_Provider_-_product-cert.pdf}} -->
Line 52: Line 39:
<!-- {{Template:Compat_Status_"referral_prod."-no-certificate}} -->
<!-- {{Template:Compat_Status_"referral_prod."-no-certificate}} -->


<!-- Testing of this product has been finalized January 1st, 1970. -->
Testing of this product has been finalized December 4th, 2014.


== Testing Enviroment ==
== Testing Environment ==


[[Image:SIPProviderTestTopology1.PNG]]
[[Image:SIPProviderTestTopology1.PNG]]
Line 60: Line 47:
This scenario describes a setup where the PBX and phones are in a private network.  
This scenario describes a setup where the PBX and phones are in a private network.  


There are 3 major configuration variants of the SIP trunk, which one is used depends on the test results. The variants are:
The SIP trunk is configured with Media Relay and exclusive coder. This is the case when the test for "Reverse Media Negotiation" fails
 
* the SIP trunk is configured without Media Relay and without exclusive coder. This is the case if all tests were successful
* the SIP trunk is configured with Media Relay and STUN but without exclusive coder. This is the case when the test for "NAT Traversal" fails
* the SIP trunk is configured with Media Relay and exclusive coder. This is the case when the test for "Reverse Media Negotiation" fails
 
The test scenario should describe which SIP trunk configuration is needed.


== Test Results ==
== Test Results ==


For more information on the test procedure, please read the following wiki article: [[Howto:SIP_Interop_Test_Description|SIP Interop Test Description]]. Bold lines in the test results indicate a KO-criteria.
For more information on the test procedure, please read the following wiki article: [[Howto:SIP_Interop_Test_Description|SIP Interop Test Description]]. Bold lines in the test results indicate a KO-criteria.
{{FIXME|reason=Note: Possible test results are Ok, Nok, Not tested, N/A(not available). Ok, Nok, N/A are self explanatory. "Not tested" is more a temporary note - if its still in the test after finishing, then the summary should explain why the feature was not tested. Remove this note in the final report}}


=== Basic Call ===
=== Basic Call ===
Line 390: Line 369:


=== Number Mapping ===
=== Number Mapping ===
 
The provider will send and receive all numbers (CGPN & CDPN) in national number format. Incoming calls from international numbers were not tested, the expectation would be that they are signalled in international number format.


=== Route Settings ===
=== Route Settings ===
Line 397: Line 376:


The provider does not support overlapped sending, so Force Enblock must be activated in the route from RS1 to SIP1.
The provider does not support overlapped sending, so Force Enblock must be activated in the route from RS1 to SIP1.
=== Media Relay ===
=== Fax ===


[[Category:Compat|{{PAGENAME}}]]
[[Category:Compat|{{PAGENAME}}]]

Revision as of 18:56, 11 December 2014

Innovaphone Compatibility Test Report

Summary

SIP Provider: Xtratelecom

The provider was tested by our partner Makenai Solutions, Innovation & Creative Ideas. This product is listed due to a customer testimonial. No tests have been conducted by innovaphone.

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

The provider doesn't support Reverse Media negotiation, so media relay and an exclusive coder setting must be configured.

The provider supports redundancy. As long as the IP addresses of the PBXs are defined in the Xtratelecom side they can send and receive calls to/from any of them.

Fax is supported, but it needs an extra SIP trunk in the PBX side pointing to a different IP. Xtratelecom defines it as a service called 'Endpoint de fax' that needs to be purchased separately.

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

  • Features:
    • Direct Dial In
    • Fax over IP (T.38)
    • DTMF
  • Supported Codecs by the provider
    • G711
    • G729
    • T.38 UDP

Current test state

Referralprod.PNGThis product is listed due to a customer testimonial. No tests have been conducted by innovaphone.

Testing of this product has been finalized December 4th, 2014.

Testing Environment

SIPProviderTestTopology1.PNG

This scenario describes a setup where the PBX and phones are in a private network.

The SIP trunk is configured with Media Relay and exclusive coder. This is the case when the test for "Reverse Media Negotiation" fails

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.

Basic Call

Tested feature Result
call using g711a Ok
call using g711u Ok
call using g723 N/A
call using g729 Ok
call using g722 Nok
Overlapped sending Nok
early media channel Ok
Fax using T.38 Ok
T.38 Transcoding by the provider Ok
Reverse Media Negotiation Nok
CGPN can be suppressed Ok
CLIP no screening Nok
Long time call possible(>30 min) Ok
External Transfer Ok
NAT Detection Nok
Redundancy Ok
SIP over TCP Ok
Voice Quality OK? OK

Direct Dial In

Tested feature Result
Inbound(Provider -> Innovaphone) Ok
Outbound(Innovaphone -> Provider) Ok
Loop In call(Innovaphone -> Provider -> Innovaphone) Ok

DTMF

Tested feature Result
DTMF tones sent correctly via RTP-events(RFC 2833) Ok
DTMF tones sent correctly via SIP-Info Ok
DTMF tones received correctly via RTP-events(RFC 2833) Ok

Hold/Retrieve

Tested feature Result
Call can be put on hold Ok
Held end hears music on hold / announcement from PBX Ok

Transfer with consultation

Tested feature Result
Call can be transferred Ok
Held end hears music on hold Ok

The following tests are made to test if call transfer is working.

Tested feature Voice Ok? MoH Ok?
inno1 calls inno2. inno2 transfers to PSTN-phone. Ok Ok
inno1 calls PSTN-phone. inno1 transfers to inno2. Ok Ok
inno1 calls PSTN-phone. PSTN-phone transfers to inno2. Ok Ok
PSTN-phone calls inno1. inno1 transfers to inno2. Ok Ok
PSTN-phone calls inno1. PSTN-phone transfers to inno2. Ok Ok
PSTN-phone calls inno1. inno1 transfers to other PSTN-phone-2. Ok Ok

Transfer with consultation (alerting only)

Tested feature Result
Call can be transferred Ok
Held end hears music on hold or dialling tone Ok
Call returns to transferring device if the third

Endpoint is not available

Ok

The following tests are made to test if call transfer is working.

Tested feature Voice Ok? MoH Ok?
inno1 calls inno2. inno2 transfers to PSTN-phone. Ok Ok
inno1 calls PSTN-phone. inno1 transfers to inno2. Ok Ok
inno1 calls PSTN-phone. PSTN-phone transfers to inno2. Ok Ok
PSTN-phone calls inno1. inno1 transfers to inno2. Ok Ok
PSTN-phone calls inno1. PSTN-phone transfers to inno2. Ok Ok
PSTN-phone calls inno1. inno1 transfers to other PSTN-phone-2. Ok Ok

Blind Transfer

Tested feature Result
Call can be transferred Ok
Held end hears dialling tone Ok

The following tests are made to test if call transfer is working.

Tested feature Voice Ok?
inno1 calls inno2. inno2 transfers to PSTN-phone. Ok
inno1 calls PSTN-phone. inno1 transfers to inno2. Ok
inno1 calls PSTN-phone. PSTN-phone transfers to inno2. Ok
PSTN-phone calls inno1. inno1 transfers to inno2. Ok
PSTN-phone calls inno1. PSTN-phone transfers to inno2. Ok
PSTN-phone calls inno1. inno1 transfers to other PSTN-phone-2. Ok

CFU / CFB Transfer

Tested feature Result
Call can be forward Ok
Held end hears dialling tone Ok

CFNR / Blind Transfer (alerting only)

Tested feature Result
Call can be transferred or forward Ok
Held end hears dialling tone Ok

The following tests are made to test if call transfer is working.

Tested feature Voice Ok?
inno1 calls inno2. inno2 transfers to PSTN-phone. Ok
inno1 calls PSTN-phone. PSTN-phone transfers to inno2. Ok
PSTN-phone calls inno1. inno1 transfers to inno2. Ok
PSTN-phone calls inno1. inno1 transfers to other PSTN-phone-2. Ok

Broadcast Group & Waiting Queue

Tested feature Result
Caller can make a call to a Broadcast Group Ok
Caller can make a call to a Waiting Queue Ok
Announcement if nobody picks up the call Ok

Configuration

Firmware version

All innovaphone devices use 10.00 sr16 as firmware.

SIP - Trunk

Voice trunk

SIP trunk Xtratelecom.JPG

Fax trunk

Fax SIP trunk Xtratelecom.JPG

Number Mapping

The provider will send and receive all numbers (CGPN & CDPN) in national number format. Incoming calls from international numbers were not tested, the expectation would be that they are signalled in international number format.

Route Settings

Routes.JPG

The provider does not support overlapped sending, so Force Enblock must be activated in the route from RS1 to SIP1.