Howto:NIAnet SIP Provider Compatibility Test: Difference between revisions
m New page: '''Innovaphone Compatibility Test Report''' == Summary == '''SIP Provider: NIAnet''' <!-- The provider supports all required innovaphone features and is therefore qualified as [[Howto:... |
|||
| (19 intermediate revisions by the same user not shown) | |||
| Line 6: | Line 6: | ||
'''SIP Provider: NIAnet''' | '''SIP Provider: NIAnet''' | ||
The provider does '''not''' support all required innovaphone features and is therefore '''not''' a [[Howto:What_is_a_%22recommended_product%22%3F#SIP_Provider|recommended SIP Provider]]. | |||
The provider | |||
NIAnet does not support the DDI feature, by thus making the provider not suited for large installations. As a result, you must configure one SIP trunk for every extension and are limited to 16 SIP - trunks per innovaphone gateway. | |||
That | That being said, NIAnet has achieved 77% of all possible test points. For more information on the test rating, please refer to [[Howto:SIP_Interop_Test_Description#Summary|Test Description]] | ||
** | * '''Provider Homepage:''' http://www.nianet.dk/ | ||
* '''Product name:''' [http://www.nianet.dk/Default.aspx?ID=65 nia-tele] | |||
* '''Features:''' | |||
** Fax over IP (T.38) | ** Fax over IP (T.38) | ||
** DTMF | ** DTMF | ||
* Supported Codecs by the provider | * Supported Codecs by the provider | ||
** | ** G711A | ||
** G729 | ** G729 | ||
** T.38 UDP | ** T.38 UDP | ||
== Current test state == | == Current test state == | ||
{{Template:Compat Status "tested"}} | |||
{{Template:Compat Status "in progress"}} | <!-- {{Template:Compat Status "in progress"}} --> | ||
<!-- {{Template:Compat Status "certified"|certificate=Tpl_sip.business_Toplink_SIP_Provider_-_product-cert.pdf}}--> | <!-- {{Template:Compat Status "certified"|certificate=Tpl_sip.business_Toplink_SIP_Provider_-_product-cert.pdf}}--> | ||
<!-- {{Template:Compat Status "rejected"}} --> | <!-- {{Template:Compat Status "rejected"}}--> | ||
Testing of this product has been finalized January 9th, 2009. | |||
== Testing Enviroment == | == Testing Enviroment == | ||
| Line 72: | Line 72: | ||
|---- | |---- | ||
|Fax using T.38 | |Fax using T.38 | ||
| | |Yes | ||
|---- | |---- | ||
|CGPN can be supressed | |CGPN can be supressed | ||
|Yes | |Yes | ||
|---- | |||
|'''Long time call possible(>30 min)''' | |||
|'''Yes''' | |||
|---- | |---- | ||
|'''Voice Quality OK?''' | |'''Voice Quality OK?''' | ||
| Line 114: | Line 117: | ||
|---- | |---- | ||
|'''Call can be put on hold''' | |'''Call can be put on hold''' | ||
|''' | |'''Yes''' | ||
|---- | |---- | ||
|Held end hears music on hold / announcement from PBX | |Held end hears music on hold / announcement from PBX | ||
| | |Yes | ||
|---- | |---- | ||
|Held end hears music on hold / announcement from provider | |Held end hears music on hold / announcement from provider | ||
| Line 154: | Line 157: | ||
|'''Call returns to transferring device if the third''' | |'''Call returns to transferring device if the third''' | ||
'''Endpoint is not available''' | '''Endpoint is not available''' | ||
|''' | |'''Yes''' | ||
|} | |} | ||
| Line 164: | Line 167: | ||
|---- | |---- | ||
|Call can be transfered | |Call can be transfered | ||
| | |Yes | ||
|---- | |---- | ||
|Held end hears dialing tone | |Held end hears dialing tone | ||
| | |Yes | ||
|} | |} | ||
| Line 177: | Line 180: | ||
|---- | |---- | ||
|'''Caller can make a call to a Broadcast Group''' | |'''Caller can make a call to a Broadcast Group''' | ||
|''' | |'''Yes''' | ||
|---- | |---- | ||
|'''Caller can make a call to a Waiting Queue''' | |'''Caller can make a call to a Waiting Queue''' | ||
|''' | |'''Yes''' | ||
|---- | |---- | ||
|'''Announcement if nobody picks up the call''' | |'''Announcement if nobody picks up the call''' | ||
|''' | |'''Yes''' | ||
|} | |} | ||
== Configuration == | == Configuration == | ||
===Firmware version=== | ===Firmware version=== | ||
All innovaphone devices use | All innovaphone devices use V7 HF1 as firmware. | ||
=== SIP - Trunk === | === SIP - Trunk === | ||
First of all the SIP Trunk must be configured. Here an example of our | First of all the SIP Trunk must be configured. Here an example of our NIAnet - Trunk. | ||
[[Image:NIAnet SIP Compatibility Test 1.PNG]] | |||
[[Image: | |||
=== Number Mapping === | === Number Mapping === | ||
The complicated part on this issue is the correct mapping of the outgoing and incoming numbers. | The complicated part on this issue is the correct mapping of the outgoing and incoming numbers. NIAnet expects the CGPN for outgoing calls to be in national number format. | ||
[[Image:NIAnet SIP Compatibility Test 2.PNG]] | |||
=== Route Settings === | === Route Settings === | ||
Because | Because NIAnet, as most SIP - Providers too, doesn't support overlap sending, you must enable the block wise sending of the phone number. You can do this by enabling ''Force enblock'' in the automatically generated Routes. | ||
The second setting you must check is Interworking(QSIG,SIP). This feature must be enabled to properly relay | The second setting you must check is Interworking(QSIG,SIP). This feature must be enabled to properly relay supplementary services, like Hold over the SIP Trunk. If this checkbox is unchecked only basic call Information like connect and disconnect will be forwarded by the Gateway. | ||
[[Image: | [[Image:NIAnet SIP Compatibility Test 3.PNG]] | ||
=== Fax === | === Fax === | ||
The FAX was connected via a IP22 to the IP800. When configuring the IP22 you must keep in mind that you will use the analog interface for fax communication. Thats why the T.38 codec must be enabled. | The FAX was connected via a IP22 to the IP800. When configuring the IP22 you must keep in mind that you will use the analog interface for fax communication. Thats why the T.38 codec must be enabled. | ||
[[Image:NIAnet SIP Compatibility Test 4.PNG]] | |||
[[Image: | |||
Now the PBX and the phones are setup correctly. You should be able to make call in both directions and send and receive fax messages. | Now the PBX and the phones are setup correctly. You should be able to make call in both directions and send and receive fax messages. | ||
[[Category:Compat|{{PAGENAME}}]] | [[Category:Compat|{{PAGENAME}}]] | ||
Latest revision as of 16:51, 3 March 2010
Innovaphone Compatibility Test Report
Summary
SIP Provider: NIAnet
The provider does not support all required innovaphone features and is therefore not a recommended SIP Provider.
NIAnet does not support the DDI feature, by thus making the provider not suited for large installations. As a result, you must configure one SIP trunk for every extension and are limited to 16 SIP - trunks per innovaphone gateway.
That being said, NIAnet has achieved 77% of all possible test points. For more information on the test rating, please refer to Test Description
- Provider Homepage: http://www.nianet.dk/
- Product name: nia-tele
- Features:
- Fax over IP (T.38)
- DTMF
- Supported Codecs by the provider
- G711A
- G729
- T.38 UDP
Current test state
The tests for this product have been completed.
Testing of this product has been finalized January 9th, 2009.
Testing Enviroment
Scenario NAT
This scenario describes a setup where the PBX and phones are in a private network. The IP800 must 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.
Basic Call
| Tested feature | Result |
|---|---|
| call using g711a | Yes |
| call using g711u | No |
| call using g723 | No |
| call using g729 | Yes |
| Overlapped sending | No |
| early media channel | Yes |
| Fax using T.38 | Yes |
| CGPN can be supressed | Yes |
| Long time call possible(>30 min) | Yes |
| Voice Quality OK? | Yes |
Direct Dial In
| Tested feature | Result |
|---|---|
| Inbound(Provider -> Innovaphone) | No |
| Outbound(Innovaphone -> Provider) | No |
DTMF
| Tested feature | Result |
|---|---|
| DTMF tones sent correctly | Yes |
| DTMF tones received correctly | Yes |
Hold/Retrieve
| Tested feature | Result |
|---|---|
| Call can be put on hold | Yes |
| Held end hears music on hold / announcement from PBX | Yes |
| Held end hears music on hold / announcement from provider | Yes |
Transfer with consultation
| Tested feature | Result |
|---|---|
| Call can be transfered | Yes |
| Held end hears music on hold | Yes |
| Call returns to transferring device if the third
Endpoint is not available |
Yes |
Transfer with consultation (alerting only)
| Tested feature | Result |
|---|---|
| Call can be transfered | Yes |
| Held end hears music on hold or dialing tone | Yes |
| Call returns to transferring device if the third
Endpoint is not available |
Yes |
Blind Transfer
| Tested feature | Result |
|---|---|
| Call can be transfered | Yes |
| Held end hears dialing tone | Yes |
Broadcast Group & Waiting Queue
| Tested feature | Result |
|---|---|
| Caller can make a call to a Broadcast Group | Yes |
| Caller can make a call to a Waiting Queue | Yes |
| Announcement if nobody picks up the call | Yes |
Configuration
Firmware version
All innovaphone devices use V7 HF1 as firmware.
SIP - Trunk
First of all the SIP Trunk must be configured. Here an example of our NIAnet - Trunk.
Number Mapping
The complicated part on this issue is the correct mapping of the outgoing and incoming numbers. NIAnet expects the CGPN for outgoing calls to be in national number format.
Route Settings
Because NIAnet, as most SIP - Providers too, doesn't support overlap sending, you must enable the block wise sending of the phone number. You can do this by enabling Force enblock in the automatically generated Routes.
The second setting you must check is Interworking(QSIG,SIP). This feature must be enabled to properly relay supplementary services, like Hold over the SIP Trunk. If this checkbox is unchecked only basic call Information like connect and disconnect will be forwarded by the Gateway.
Fax
The FAX was connected via a IP22 to the IP800. When configuring the IP22 you must keep in mind that you will use the analog interface for fax communication. Thats why the T.38 codec must be enabled.
Now the PBX and the phones are setup correctly. You should be able to make call in both directions and send and receive fax messages.