Howto:NL - KPN - Vast bellen Dienst VoIP Connect SIP-Provider (3rdParty 2017)

From innovaphone wiki
Jump to navigation Jump to search

Summary

Tests for the Vast_bellen_Dienst_VoIP_Connect SIP trunk product of the provider KPN were completed. Test results have been last updated on August 25th, 2017. Check the history of this article for the date of the first publication of the testreport.

However the tested SIP trunk is not available for nightly tests yet! The provider doesn't offer the possibility to test the SIP-trunk regularly and automatically (e.g. before firmware releases). As a result, we do not know if it will still work or will work with different firmware than the one we tested with.

Tested Firmware: 12r2 Service Release 3 (125210)

Remarks

  • The testresults are not from an automatic test. The test is done manual on a KPN location in Houten(NL) in a dedicated test envirement.

The test desciption is mainly based on the MEDIA RELAY configuration but there also some tests performed with direct RTP. If you want to use direct RTP configuration instead of MEDIA RELAY configuration, you need to configure all endpoints with Codec G711A exclusive or only with the by KPN supported codecs (G711 and G722)

Certification Status and test results

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


Testing of this product has been finalized 23 August , 2017.

Vendor

KPNNLlogo.png


KPN NL


Product name

KPN Vast bellen Dienst VoIP Connect

Configuration

Use profile NL-KPN-Vast_bellen_Dienst_VoIP_Connect in Gateway/Interfaces/SIP to configure this SIP provider.

A most recent v12r2 firmware or higher is required to use this SIP-profile. For hints regarding upgrade to v12r2, see Howto:Firmware Upgrade V12r1 V12r2

New profiles are added in the course of our V12R2 software Service Releases, see Support:DVL-Roadmap Firmware 12r2. Here is an up to date list of tested SIP providers.

Disclaimer

These tests look at a number of interoperability scenarios between innovaphone SIP devices and a given SIP trunk product. As we are enhancing our testing procedures, nature and number of these tests will vary.

All test results document the fact how the tested combination performs in the tested scenario. It explicitly does not comment on the question what the reason is for the behaviour nor if and how it could be changed. It thus does not imply that either the SIP trunk provider or the innovaphone device fails in any way. It merely says that the combination does not perform as defined by the test.

If not mentioned otherwise, all tests are repeated on a weekly basis (a.k.a. nightly tests) using the then-current innovaphone firmware. If a tested combination keeps performing differently from the state documented here during nightly tests, we reserve the right to update this article accordingly.

Some tests do not have consistent results. This may occur for various reasons. If so, we document the tests result as being unstable.

Some of the tested SIP trunk products are not available for nightly tests. In this case, the fact will be noted in the Summary section.