Howto:Business Trunking - Proximus - SIP Provider: Difference between revisions

From innovaphone wiki
Jump to navigation Jump to search
 
(13 intermediate revisions by 2 users not shown)
Line 12: Line 12:
As main/unique features we have the Redundancy mechanism and Emergency calls handling that require a specific configuration. It's necessary to run the latest '''v11r2''' firmware to operate with this SIP Trunk.
As main/unique features we have the Redundancy mechanism and Emergency calls handling that require a specific configuration. It's necessary to run the latest '''v11r2''' firmware to operate with this SIP Trunk.


CLIP No Screening isn't supported by regulation however Rerouting it's possible with Business Trunking, and rerouted calls display the original caller CLIP to the redirected party/destination.
CLIP No Screening isn't supported by regulation. However Rerouting is possible with Business Trunking and rerouted calls display the original caller CLIP to the redirected party/destination.


Extensive Fax tests were made also with IP22 and successfully both T.38 and G.711 fax calling are possible with different call scenarios.
Extensive Fax tests were successfully made also with an IP22. Both T.38 and G.711 fax calling are possible with different call scenarios.


* Features:
* Features:
Line 35: Line 35:


<!--{{Template:Compat Status "planned"}} -->
<!--{{Template:Compat Status "planned"}} -->
{{Template:Compat Status "in progress"}}
<!--{{Template:Compat Status "in progress"}}-->
<!--{{Template:Compat_Status_"referral_prod."|certificate=SIP-Trunk_-_LCR_Telecom_-_SIP_Provider_-_product-cert.pdf}} -->
<!-- {{Template:Compat_Status_"referral_prod."|certificate=Business_Trunking_-_Proximus_-_SIP_Provider_-_product-cert.pdf}} -->
<!-- {{Template:Compat Status "tested"(sip provider)}} -->
<!--{{Template:Compat Status "tested"(sip provider)}} -->
<!-- {{Template:Compat Status "rejected"}} -->
<!-- {{Template:Compat Status "rejected"}} -->
<!-- {{Template:Compat_Status_"referral_prod."-no-certificate}} -->
<!--{{Template:Compat_Status_"referral_prod."-no-certificate}}-->
{{Template:Compat_Status_"engineered_prod."|certificate=Business_Trunking_-_Proximus_-_SIP_Provider_-_product-cert.pdf‎}}


<!-- Testing of this product has been finalized April 1st, 2015. -->
Testing of this product has been finalized July 3rd, 2015.


== Testing Enviroment ==
== Testing Enviroment ==
Line 55: Line 56:


== Test Results ==
== Test Results ==
[[Media:Innovaphone_V11r2_IP-PBX Report-v1_02072015.pdf | Proximus Validation Report]]


== Configuration ==
== Configuration ==
Line 60: Line 63:
===Firmware version===
===Firmware version===


All innovaphone devices use V11r2.
All innovaphone devices use V11r2 SR2.


=== SIP - Trunk ===
=== SIP - Trunk ===
Line 66: Line 69:
* External Trunk to SIP Provider
* External Trunk to SIP Provider
[[Image:Bussiness Trunking_-_Proximus_-_SIP_Provider_Compatibility_Test_1.png]]
[[Image:Bussiness Trunking_-_Proximus_-_SIP_Provider_Compatibility_Test_1.png]]
'''Note:''' The official domain it's "ims.belgacom.be", imst.belgacom.be it was the test platform used for the SIP Certification tests.


* Internal Trunk to PBX
* Internal Trunk to PBX
Line 83: Line 88:
=== Emergency Calls ===
=== Emergency Calls ===


Calling to emergency numbers, it's necessary special manipulation of the CLIP to provide essencial information to the emergency agents:
When calling to emergency numbers, it's necessary to manipulate the CLIP in order to provide essential information to the emergency agents:


  1. R-URI/CLIP manipulation: 1992+1AB+ZIP code as called party number
  1. R-URI/CLIP manipulation: 1992+1AB+ZIP code as called party number
Line 96: Line 101:
[[Image:Bussiness Trunking_-_Proximus_-_SIP_Provider_Compatibility_Test_8.png]]
[[Image:Bussiness Trunking_-_Proximus_-_SIP_Provider_Compatibility_Test_8.png]]


In our example the two different IP address represent two different locations (Multi location scenario) with different ZIP codes, the number 1992 it's fixed and must be prefixed always.
In our example the two different IP addresses represent two different locations (Multi location scenario) with different ZIP codes, the number 1992 is fixed and must be prefixed always.


*2. For the second point (EVN) we use the CGPN MAPS at the routes.
*2. For the second point (EVN) we use the CGPN MAPS at the routes.
Line 104: Line 109:
=== Extra Options ===
=== Extra Options ===


* '''Disable Interworking of Hold Notifications to SIP Provider'''
==== Disable Interworking of Hold Notifications to SIP Provider ====


During the tests we concluded that when interworking the hold-notify message to SIP and sending to SIP Provider two consecutive Re-Invites with "send-only" attribute the IMS platform reply to the second re-invite with "inactive" so by doing this the call it's put on hold without any Music on Hold just silence.
During the tests we concluded that when interworking the hold-notify message to SIP and sending to the SIP Provider two consecutive Re-Invites with "send-only" attributes, the IMS platform replies to the second re-invite with "inactive". By doing so this call is put on hold without any Music on Hold - just silence.
To avoid this behaviour we need to disable the interworking of the hold-notify message by setting:  
To avoid this behaviour we need to disable the interworking of the hold-notify message by this setting:  


  !config add SIP /no-hr-notify
  !config add SIP /no-hr-notify
Line 113: Line 118:
  !config activate
  !config activate


* '''SIP Options Interval (Optional)'''
==== SIP Options Interval (Optional) ====


The IMS from Proximus uses SIP Options to monitor the SIP Trunks, so it's mandatory that Innovaphone replies to incoming SIP Options received, this it's done by default. Additionally we can also send SIP Options to the SIP Proxy and have similar mechanism for redundancy mechanism, when the remote Proxy doesn't reply to outgoing SIP Options the Innovaphone Gateway will send the call to the next interface. We can set:
The IMS from Proximus uses SIP Options to monitor the SIP Trunks, so it's mandatory that Innovaphone replies to incoming SIP Options received. This is done by default. Additionally we can also send SIP Options to the SIP Proxy and have similar mechanism for redundancy. If the remote Proxy doesn't reply to outgoing SIP Options, the Innovaphone Gateway will send the call to the next interface. To enable sending of Options - messages, the following setting must be done:


  !config add SIP /options-interval 30
  !config add SIP /options-interval 30
Line 121: Line 126:
  !config activate
  !config activate


* '''Remove Comfort Noise (CN) Capability from SDP'''
==== Remove Comfort Noise (CN) Capability from SDP ====


During the tests we found out some specific 3rd party devices connected to the IMS network when doing the coder negotiation to a single coder preference repeat the coder negotiation till they have only 1 coder in the offer or till they reach a specific number of retries. Since Innovaphone by default always include the payload 13 (Comfort Noise) this would made the remote device to do multiple re-invites to try to reach to a single coder/payload in the offer.
During the tests we found out that some specific 3rd party devices connected to the IMS network support only a single coder/payload in the offer. When doing the coder negotiation, this devices repeat the coder negotiation until they have only 1 coder in the offer or until they reach a specific number of retries. Since Innovaphone by default always include the payload 13 (Comfort Noise) in addition to the used voice coder/payload, this would make the remote device to do multiple re-invites to try to reach the single coder/payload in the offer.
To avoid this we could disable the sending of Comfort Noise capability since isn't used and by design was implemented for Lync Interop.
To avoid unnecessary signalling, we should disable the sending of Comfort Noise capability.


  !config add SIP /rem-cn-capability
  !config add SIP /rem-cn-capability
Line 130: Line 135:
  !config activate
  !config activate


* '''Setting of P-Asserted ID instead of P-Preferred ID'''
==== Setting of P-Asserted ID instead of P-Preferred ID ====


When using the feature of ReRouting the call (SIP 302 Move Temporary) to the SIP Trunk the IMS platform check the P-Asserted ID setting. By default we send as P-Preferred ID so that will not work properly for that reason we need to change to:
When using the feature of ReRouting the call (SIP 302 Move Temporary) to the SIP Trunk, the IMS platform checks the P-Asserted ID setting. By default we send as P-Preferred ID instead, so that will not work. As a result, we need to configure the following setting:


  !config add SIP /pai
  !config add SIP /pai
Line 138: Line 143:
  !config activate
  !config activate


* '''Trunkline Object Settings'''
==== Trunkline Object Settings ====


[[Image:Bussiness Trunking_-_Proximus_-_SIP_Provider_Compatibility_Test_6.png]]
[[Image:Bussiness Trunking_-_Proximus_-_SIP_Provider_Compatibility_Test_6.png]]


** '''Reroute Supported''': Rerouting it's supported with Business Trunking, the original calling number will be displayed to the redirected destination.
* '''Reroute Supported''': Rerouting is supported with Business Trunking, the original calling number will be displayed to the redirected destination.


** '''Set Calling=Diverting No''': This option it's mandatory since Proximus always check the "From" Number and must be part of the PBX and not an external number (original number). CLIP NO Screening isn't allowed.
* '''Set Calling=Diverting No''': This option is mandatory since Proximus always checks that the "From" Number is a part of the PSTN-number assigned to the Trunk and not an external number (original number). CLIP NO Screening isn't allowed.


** '''No Presence/Dialog Subscribe''' : This option it's optional, just to avoid the sending of unnecessary SIP Presence requests to outside.
* '''No Presence/Dialog Subscribe''' : This option is optional. It avoids the sending of unnecessary SIP Presence requests to the Provider.


=== Known limitations ===
=== Known limitations ===

Latest revision as of 18:03, 20 December 2016

3rdPartyGoldfischglas 03.png

Innovaphone Compatibility Test Report

Summary

SIP Provider: Proximus

The tests were made by Proximus Netcenter Lab (previous name Belgacom) following their Compatibility Certification Plan for interoperability with Proximus IMS network. No tests have been conducted by innovaphone.

Innovaphone passed all the required tests and is therefore qualified as compatible Vendor/Device for this product/service.

As main/unique features we have the Redundancy mechanism and Emergency calls handling that require a specific configuration. It's necessary to run the latest v11r2 firmware to operate with this SIP Trunk.

CLIP No Screening isn't supported by regulation. However Rerouting is possible with Business Trunking and rerouted calls display the original caller CLIP to the redirected party/destination.

Extensive Fax tests were successfully made also with an IP22. Both T.38 and G.711 fax calling are possible with different call scenarios.

  • Features:
    • Direct Dial In
    • DTMF
    • CGPN can be suppressed
    • Emergency Calls
    • Redundancy
    • Fax over IP (T.38/G711)
    • Rerouting


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

Current test state

EngineeredProd.png The tests for this product have been completed and it has been approved as a engineered product (Certification document).

Testing of this product has been finalized July 3rd, 2015.

Testing Enviroment

Bussiness Trunking - Proximus - SIP Provider Compatibility Test 10.png

Test Results

Proximus Validation Report

Configuration

Firmware version

All innovaphone devices use V11r2 SR2.

SIP - Trunk

  • External Trunk to SIP Provider

Bussiness Trunking - Proximus - SIP Provider Compatibility Test 1.png

Note: The official domain it's "ims.belgacom.be", imst.belgacom.be it was the test platform used for the SIP Certification tests.

  • Internal Trunk to PBX

Bussiness Trunking - Proximus - SIP Provider Compatibility Test 2.png

  • 2 Different Trunks for Fixed and Mobile and redundancy of both, so total of 4 External Trunks

Bussiness Trunking - Proximus - SIP Provider Compatibility Test 4.png

Number Mapping

Bussiness Trunking - Proximus - SIP Provider Compatibility Test 3.png

  • Internal Extensions are 2XX.

Route Settings

Bussiness Trunking - Proximus - SIP Provider Compatibility Test 5.png

Emergency Calls

When calling to emergency numbers, it's necessary to manipulate the CLIP in order to provide essential information to the emergency agents:

1. R-URI/CLIP manipulation: 1992+1AB+ZIP code as called party number
2. From-header manipulation: EVN (emergency virtual number) as CLI

Based on the location (Subnet/IP Address of the Endpoint) it's necessary to send the correct ZIP code.

  • 1. To achieve the first requirement we need to create Number MAP Object for each special Emergency Number (ex: 117, 119, 112)

Bussiness Trunking - Proximus - SIP Provider Compatibility Test 7.png

Bussiness Trunking - Proximus - SIP Provider Compatibility Test 8.png

In our example the two different IP addresses represent two different locations (Multi location scenario) with different ZIP codes, the number 1992 is fixed and must be prefixed always.

  • 2. For the second point (EVN) we use the CGPN MAPS at the routes.

Bussiness Trunking - Proximus - SIP Provider Compatibility Test 9.png

Extra Options

Disable Interworking of Hold Notifications to SIP Provider

During the tests we concluded that when interworking the hold-notify message to SIP and sending to the SIP Provider two consecutive Re-Invites with "send-only" attributes, the IMS platform replies to the second re-invite with "inactive". By doing so this call is put on hold without any Music on Hold - just silence. To avoid this behaviour we need to disable the interworking of the hold-notify message by this setting:

!config add SIP /no-hr-notify
!config write
!config activate

SIP Options Interval (Optional)

The IMS from Proximus uses SIP Options to monitor the SIP Trunks, so it's mandatory that Innovaphone replies to incoming SIP Options received. This is done by default. Additionally we can also send SIP Options to the SIP Proxy and have similar mechanism for redundancy. If the remote Proxy doesn't reply to outgoing SIP Options, the Innovaphone Gateway will send the call to the next interface. To enable sending of Options - messages, the following setting must be done:

!config add SIP /options-interval 30
!config write
!config activate

Remove Comfort Noise (CN) Capability from SDP

During the tests we found out that some specific 3rd party devices connected to the IMS network support only a single coder/payload in the offer. When doing the coder negotiation, this devices repeat the coder negotiation until they have only 1 coder in the offer or until they reach a specific number of retries. Since Innovaphone by default always include the payload 13 (Comfort Noise) in addition to the used voice coder/payload, this would make the remote device to do multiple re-invites to try to reach the single coder/payload in the offer. To avoid unnecessary signalling, we should disable the sending of Comfort Noise capability.

!config add SIP /rem-cn-capability
!config write
!config activate

Setting of P-Asserted ID instead of P-Preferred ID

When using the feature of ReRouting the call (SIP 302 Move Temporary) to the SIP Trunk, the IMS platform checks the P-Asserted ID setting. By default we send as P-Preferred ID instead, so that will not work. As a result, we need to configure the following setting:

!config add SIP /pai
!config write
!config activate

Trunkline Object Settings

Bussiness Trunking - Proximus - SIP Provider Compatibility Test 6.png

  • Reroute Supported: Rerouting is supported with Business Trunking, the original calling number will be displayed to the redirected destination.
  • Set Calling=Diverting No: This option is mandatory since Proximus always checks that the "From" Number is a part of the PSTN-number assigned to the Trunk and not an external number (original number). CLIP NO Screening isn't allowed.
  • No Presence/Dialog Subscribe : This option is optional. It avoids the sending of unnecessary SIP Presence requests to the Provider.

Known limitations

Related Articles