Howto:Toplink SIP Provider Compatibility Test: Difference between revisions

From innovaphone wiki
Jump to navigation Jump to search
 
(22 intermediate revisions by 2 users not shown)
Line 8: Line 8:
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 supports all required innovaphone features and is therefore qualified as [[Howto:What_is_a_%22recommended_product%22%3F#SIP_Provider|recommended SIP Provider]].  


Toplink does not support the remote hold feature. When making a blind transfer(using redial key) the remote end will not get a MOH/dialtone from the provider.  
Currently Toplink does not support the transport of DTMF tones via SIP - Info messages. As a result, Media-Relay must be activated on the SIP trunk if ''Mobility'' is used in the PBX.


That beeing said, Toplink has achieved 96% of all possible test points. For more information on the test rating, please refer to [[Howto:SIP_Interop_Test_Description#Summary|Test Description]]
That being said, Toplink has achieved 95% of all possible test points. For more information on the test rating, please refer to [[Howto:SIP_Interop_Test_Description#Summary|Test Description]]




Line 23: Line 23:
** G729
** G729
** G723
** G723
** G726
** T.38 UDP
** T.38 UDP
== Current test state ==
<!-- {{Template:Compat Status "tested"}}-->
<!-- {{Template:Compat Status "in progress"}} -->
{{Template:Compat Status "certified"|certificate=Tpl_sip.business_Toplink_SIP_Provider_-_product-cert.pdf}}
<!-- {{Template:Compat Status "rejected"}} -->
Testing of this product has been finalized November 5th, 2012.


== Testing Enviroment ==
== Testing Enviroment ==
Line 32: Line 39:
[[Image:HFO_SIP_Compatibility_Test_5.PNG]]
[[Image:HFO_SIP_Compatibility_Test_5.PNG]]


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.
This scenario describes a setup where the PBX and phones are in a private network. The IP800 doesn't use an stun server. The IP800 doesn't work as media relay, Media-Relay is needed only for the transport of DTMF-Info SIP - messages(see test on DTMF).


== Test Results ==
== Test Results ==
Line 55: Line 62:
|call using g729
|call using g729
|Yes
|Yes
|----
|call using g722
|No
|----
|----
|Overlapped sending
|Overlapped sending
Line 65: Line 75:
|Yes
|Yes
|----
|----
|CGPN can be supressed
|CGPN can be suppressed
|Yes
|----
|Clip no screening
|Yes
|Yes
|----
|----
|'''Reverse Media Negotiaton'''
|'''Long time call possible(>30 min)'''
|'''Yes'''
|'''Yes'''
|----
|'''External Transfer'''
|'''Yes'''
|----
|NAT Detection
|Yes
|----
|Redundancy
|Yes, see subtopic Redundancy
|----
|SIP over TCP
|No
|----
|----
|'''Voice Quality OK?'''
|'''Voice Quality OK?'''
Line 96: Line 121:
|'''DTMF tones sent correctly'''
|'''DTMF tones sent correctly'''
|'''Yes'''
|'''Yes'''
|----
|DTMF tones sent correctly via SIP-Info
|Yes, requires mediarelay
|----
|----
|'''DTMF tones received correctly'''
|'''DTMF tones received correctly'''
Line 103: Line 131:
=== Hold/Retrieve ===
=== Hold/Retrieve ===


{| border="1"
{| border="1"  
{| border="1"  
!Tested feature
!Tested feature
Line 111: Line 140:
|----
|----
|Held end hears music on hold / announcement from PBX
|Held end hears music on hold / announcement from PBX
|Yes
|Yes, requires disabling of SIP interworking to provider
|----
|Held end hears music on hold / announcement from provider
|No
|}
|}


Line 123: Line 149:
!Result  
!Result  
|----
|----
|'''Call can be transfered'''
|'''Call can be transferred'''
|'''Yes'''
|'''Yes'''
|----
|----
|Held end hears music on hold
|Held end hears music on hold
|Yes
|Yes, requires disabling of SIP interworking to provider
|----
|'''Call returns to transferring device if the third'''
'''Endpoint is not available'''
|'''Yes'''
|}
|}


Line 140: Line 162:
!Result  
!Result  
|----
|----
|'''Call can be transfered'''
|'''Call can be transferred'''
|'''Yes'''
|'''Yes'''
|----
|----
|Held end hears music on hold or dialing tone
|Held end hears music on hold or dialling tone
|Yes
|Yes, requires disabling of SIP interworking to provider
|----
|----
|'''Call returns to transferring device if the third'''  
|'''Call returns to transferring device if the third'''  
Line 157: Line 179:
!Result  
!Result  
|----
|----
|Call can be transfered
|Call can be transferred
|Yes, only for G711A
|----
|Held end hears dialling tone
|Yes
|Yes
|----
|Held end hears dialing tone
|No
|}
|}


Line 179: Line 201:
|'''Yes'''
|'''Yes'''
|}
|}
=== Redundancy ===
No information from the provider was received yet. However tests showed that it is possible to register two SIP - interfaces using the same account. Calls will be then send via the last registered account, if this registration is down the previously registered SIP - Interface is used.


== Configuration ==
== Configuration ==
===Firmware version===
===Firmware version===


All innovaphone devices use V6 SR1 HF3 as firmware.
All innovaphone devices use V9 HF15 as firmware.


=== SIP - Trunk ===
=== SIP - Trunk ===


First of all the SIP Trunk must be configured. Here an example of our Toplink - Trunk. If you want that the Gateway should act as Medialrelay, you must exchange the Gatekeeper Address (blue marking) to an private network address (see [[Howto:Toplink_SIP_Compatibility_Test#Media Relay (Scenario 2 only) | Media Relay (Scenario 2 only)]]); for example 127.0.0.1
First of all the SIP Trunk must be configured. Here an example of our Toplink - Trunk. If you want that the Gateway should act as Medialrelay, you must activate the option ''Media-Relay''. This is needed if the 'Mobility'' feature is required in the PBX - setup.




Line 204: Line 229:
Because Toplink, as most SIP - Providers too, doesn't support overlap sending, you must enable the blockwise sending of the phone number. You can do this by enabling ''Force enblock'' in the automatically generated Routes.
Because Toplink, as most SIP - Providers too, doesn't support overlap sending, you must enable the blockwise 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 suplementary 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:Toplink SIP Compatibility Test 3.PNG]]


[[Image:Toplink SIP Compatibility Test 6.PNG]]
=== Fax ===
The FAX was connected via a BRI(TEL1)-interface to the IP800. When configuring the BRI-interface you must keep in mind that the T.38 codec must be enabled.


=== Media Relay (Scenario 2 only) ===


By enabling Media Relay on the PBX, The IP800 will work as an RTP - Proxy, so all RTP Streams will travel through the IP800. This mode poses a much greater load on the PBX, so the number of concurrent calls will be heavy limited.
[[Image:Toplink SIP Compatibility Test 4.PNG]]


[[Image:Toplink SIP Compatibility Test 5.PNG]]
* In order to sent faxes using t.38 we must also enable "t38_cng_detect" at "http://addr/AC-DSP0/mod_cmd.xml?xsl=dsp.xsl"


You may wonder about the usefullness of putting the localhost address as a private network. However you must insert this entry, if the IP800 SIP GW registers at the PBX on localhost interface.
=== 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.
[[Image:Toplink SIP Compatibility Test 3.PNG]]


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 14:45, 15 August 2013

Innovaphone Compatibility Test Report


Summary

SIP Provider: Toplink

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

Currently Toplink does not support the transport of DTMF tones via SIP - Info messages. As a result, Media-Relay must be activated on the SIP trunk if Mobility is used in the PBX.

That being said, Toplink has achieved 95% 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
    • G723
    • T.38 UDP

Current test state

Recprod.PNG The tests for this product have been completed and it has been approved as a recommended product (Certification document).

Testing of this product has been finalized November 5th, 2012.

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 doesn't use an stun server. The IP800 doesn't work as media relay, Media-Relay is needed only for the transport of DTMF-Info SIP - messages(see test on DTMF).

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 Yes
call using g723 Yes
call using g729 Yes
call using g722 No
Overlapped sending No
early media channel Yes
Fax using T.38 Yes
CGPN can be suppressed Yes
Clip no screening Yes
Long time call possible(>30 min) Yes
External Transfer Yes
NAT Detection Yes
Redundancy Yes, see subtopic Redundancy
SIP over TCP No
Voice Quality OK? Yes

Direct Dial In

Tested feature Result
Inbound(Provider -> Innovaphone) Yes
Outbound(Innovaphone -> Provider) Yes

DTMF

Tested feature Result
DTMF tones sent correctly Yes
DTMF tones sent correctly via SIP-Info Yes, requires mediarelay
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, requires disabling of SIP interworking to provider

Transfer with consultation

Tested feature Result
Call can be transferred Yes
Held end hears music on hold Yes, requires disabling of SIP interworking to provider

Transfer with consultation (alerting only)

Tested feature Result
Call can be transferred Yes
Held end hears music on hold or dialling tone Yes, requires disabling of SIP interworking to provider
Call returns to transferring device if the third

Endpoint is not available

Yes

Blind Transfer

Tested feature Result
Call can be transferred Yes, only for G711A
Held end hears dialling 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

Redundancy

No information from the provider was received yet. However tests showed that it is possible to register two SIP - interfaces using the same account. Calls will be then send via the last registered account, if this registration is down the previously registered SIP - Interface is used.

Configuration

Firmware version

All innovaphone devices use V9 HF15 as firmware.

SIP - Trunk

First of all the SIP Trunk must be configured. Here an example of our Toplink - Trunk. If you want that the Gateway should act as Medialrelay, you must activate the option Media-Relay. This is needed if the 'Mobility feature is required in the PBX - setup.


Toplink SIP Compatibility Test 1.PNG

Number Mapping

The complicated part on this issue is the correct mapping of the outgoing and incoming numbers.

Toplink SIP Compatibility Test 2.PNG


Route Settings

Because Toplink, as most SIP - Providers too, doesn't support overlap sending, you must enable the blockwise sending of the phone number. You can do this by enabling Force enblock in the automatically generated Routes.

Toplink SIP Compatibility Test 3.PNG

Fax

The FAX was connected via a BRI(TEL1)-interface to the IP800. When configuring the BRI-interface you must keep in mind that the T.38 codec must be enabled.


Toplink SIP Compatibility Test 4.PNG


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.

Retrieved from "https://wiki.innovaphone.com/index.php?title=Howto:Toplink_SIP_Provider_Compatibility_Test&oldid=30542"