Howto:FR - OVH Telecom - SIP Trunk SIP-Provider (2016): Difference between revisions
m (→Remarks) |
|||
Line 1: | Line 1: | ||
== Summary == | == Summary == | ||
{{Template:SIP_TEST_STATUS_complete|update= | {{Template:SIP_TEST_STATUS_complete|update=May 15th, 2024|url=https://www.ovhtelecom.fr/telephonie/sip-trunk|productname=SIP_Trunk|providername=OVH_Telecom}} | ||
=== Remarks === | === Remarks === | ||
{{ Template:SIP_TEST_NO_NIGHTLY_TESTS | fw-version = | {{ Template:SIP_TEST_NO_NIGHTLY_TESTS | fw-version = 14r1 Service Release 14 (1410509)}} | ||
<internal>Provider SBC: Cirpack/v4.70 (gw_sip)</internal> | <internal>Provider SBC: Cirpack/v4.70 (gw_sip)</internal> | ||
Line 24: | Line 23: | ||
{{SIP_TEST_ISSUES_MR_INTRO}} | {{SIP_TEST_ISSUES_MR_INTRO}} | ||
; MOBILITY : {{SIP_TEST_FACT_WORKSINALTERNATE_NOT_IN_PRIMARY}} | ; MOBILITY : {{SIP_TEST_FACT_WORKSINALTERNATE_NOT_IN_PRIMARY}} | ||
== Test Results == | == Test Results == |
Latest revision as of 11:18, 15 May 2024
Summary
Tests for the SIP_Trunk SIP trunk product of the provider OVH_Telecom were completed. Test results have been last updated on May 15th, 2024. Check the history of this article for the date of the first publication of the testreport.
Remarks
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: 14r1 Service Release 14 (1410509) <internal>Provider SBC: Cirpack/v4.70 (gw_sip)</internal>
List of Issues found in no media-relay Configuration
This is a list of all issues found in a configuration where the media stream between endpoints and the SIP provider - as opposed to the signalling - is not routed through the SBC.
- CLNS ONNET
- Onnet-Calls (that is, within the provider's network) do not allow foreign calling party numbers (CGPN). In other words, clip no screening is not possible for on-net calls.
- CLNS
- Outgoing calls cannot be sent with a foreign calling party number (CLI).
- FAX T38
- The provider does not fully support T.38 fax
- MOBILITY
- The provider can not send DTMF signals via SIP-INFO messages.
- RALERT DISC
- Call disconnected by far end during alert does not disconnect locally
- REDIR DIVHDR
- The provider does not support maintaining the original caller ID for redirected calls (e.g. CFU) when the original caller is present in a
Diversion:
header. - REDIR HISTHDR
- The provider does not support maintaining the original caller ID for redirected calls (e.g. CFU) when the original caller is present in a
History-Info:
header. - SIP INFO
- The provider does not support conveying DTMF using the SIP-INFO method.
- SUBSCRIBER NR
- The provider does not support dialling numbers in subscriber number format.
Here is the list of test-cases that have been performed for this provider: 180_RINGING, BASIC_CALL, CLIR, CLNS_ONNET, CLNS, CONN_NR_DIFF, CONN_NR, DTMF, EARLY_MEDIA_INBOUND, FAX_AUDIO, FAX_T38, FAX_T38_ONNET, FAX_T38ANDAUDIO, G711A_ONNET, G711A, G711U_ONNET, G711U, G722_ONNET, G722, G729_ONNET, G729, HOLD_RETRIEVE, IP_FRAGMENTATION, LARGE_SIP_MESSAGES, MOBILITY, OPUS_NB, OPUS_WB, RALERT_DISC, REDIR_302, REDIR_DIVHDR, REDIR_HISTHDR, REVERSE_MEDIA, SIP_INFO, SRTP_INCOMING, SRTP_INTERNAL, SRTP_OUTGOING, XFER_BLIND, XFER_CONS_ALERT, XFER_CONS_EXT, XFER_CONS, SUBSCRIBER_NR
List of Issues found in media-relay Configuration
This section lists the results that differ from the results for the first configuration.
- MOBILITY
- This feature, which does not work in the first configuration, works fine in the second configuration.
Test Results
This section explains the test results for all possible configurations in more detail.
Configuration without media-relay
- Registration
- The provider supports only UDP as transport protocol. As a result, the SIP-communication is not encrypted(TLS). Moreover it requires all involved network elements to support IP-fragmentation.
- DTMF (RFC2833)
- The provider can convey DTMF digits using the RTP payload method as per RFC2833.
- Session Timer
- The tests regarding the SIP-session timer were successful. This means that either no session expiry is used or that it is used and works. It does not imply that session expiry actually is used.
- NAT Traversal
- The provider detects clients behind NAT and can handle calls to them without requiring the clients to use NAT-traversal methods like STUN.
- Redundancy
- Registration of two SIP-interfaces on the same SIP-account is supported by the provider. However, the provider has no failover mechanism if one device is down. As a result, you can use both SIP-interfaces for load-balancing purposes. If one device is down, for 2 minutes incoming and outgoing calls might be rejected/fail.
- Correct signalling of Ringing-state
- OK
- An outgoing call that is disconnected by the far end during alert is not disconnected locally. Typically, the provider may play a message to the effect that the call has been rejected or the call can not be completed so that the calling user will hang up. This may be OK, however, it may create issues with automated calls (e.g. fax or modem) which do not listen to the announcement and keep waiting for the far end to accept the call.
- CLIR
- OK
- Clip No Screening (CLNS)
- CLIP no screening (CLNS) is not possible, that is, outgoing calls can only have the own subscriber number (or extension), no foreign numbers as calling line id. This affects for example externally forwarded and mobility calls. Call redirection using the SIP 302 Redirect header is supported by the provider. Rerouting can be enabled by setting the Reroute supported check-mark in the corresponding Trunk object configuration. Also, the Interworking check-mark must be set in the route used for calls from and to the SIP provider.
- However, during our test other interop problems were discovered when the Interworking Flag is enabled. Therefore it is not recommended to use the call redirection via SIP 302 Redirect header.
- Also, there is no other method available for this provider to make sure externally forwarded calls will show proper calling line identification (CLI). In this case, we recommend to set the Set Calling = Diverting No check-mark in the PBX Trunk object. This way, the forwarded call will at least carry the diverting party number (DGPN) as calling party number (CGPN/CLI) when alerting at the forwarded-to target. Otherwise it would either show no CLI at all or the lowest subscriber number associated with the trunk only.
- COLP
- Outbound calls to the PSTN show the correct connected number. However incoming calls from the PSTN do not.
- A caller from the PSTN will receive an incorrect connected number that differs from the dialled number. This might lead to the caller cancelling the call.
- For outbound calls to the PSTN, an update of the connected number is not signalled to the caller.
- Early-Media
- The provider supports early-media for outbound calls (hence inbound early media) to the PSTN.
- Fax
- Transport of faxes to/from the PSTN via G.711 codec was tested successfully. However, all fax endpoints must be configured with exclusive codec "G711A".
- Transport of faxes using T.38 worked to onnet destinations. However it failed to PSTN destination. Fallback to audiofax worked.
- As a result, T.38 is enabled on the SIP-interface, the use of audio-fax is necessary.
- Codecs
- supported to/from PSTN: G711A, G711U and G729
- supported onnet (VoIP to VoIP): G711A, G711U and G729
- IP-Fragmentation
- OK
- Large SIP messages
- OK
- Reverse Media Negotiation
- OK
- Mobility Calls
- Transmitting DTMF-tones as SIP-INFO messages is not supported. In a no-media-relay configuration, DTMF signalling can thus not be conveyed to the PBX. Mobility calls will not work.
- Neither Clip no screening (CLNS) nor call redirection using the SIP Diversion: or History-Info is supported. Calls forwarded to mobility devices will thus not have the original callers calling line id (CLI). In this case, we recommend to set the Set Calling = Diverting No check-mark in the PBX Trunk object. This way, the mobility call will at least carry the mobility user's own extension as calling party number (CGPN/CLI) when alerting at the mobile device. Otherwise it would either show no CLI at all or the lowest subscriber number associated with the trunk only.
- SRTP
- The provider does not support audio encryption using SRTP.
- Call Transfer
- OK
- Provider supports dialling subscriber numbers
- The provider does not support dialling numbers in subscriber number format. Make sure to configure the Dialing Location accordingly.
Configuration with media-relay
- Registration
- The provider supports only UDP as transport protocol. As a result, the SIP-communication is not encrypted(TLS). Moreover it requires all involved network elements to support IP-fragmentation.
- DTMF (RFC2833)
- The provider can convey DTMF digits using the RTP payload method as per RFC2833.
- Session Timer
- The tests regarding the SIP-session timer were successful. This means that either no session expiry is used or that it is used and works. It does not imply that session expiry actually is used.
- NAT Traversal
- The provider detects clients behind NAT and can handle calls to them without requiring the clients to use NAT-traversal methods like STUN.
- Redundancy
- Registration of two SIP-interfaces on the same SIP-account is supported by the provider. However, the provider has no failover mechanism if one device is down. As a result, you can use both SIP-interfaces for load-balancing purposes. If one device is down, for 2 minutes incoming and outgoing calls might be rejected/fail.
- Correct signalling of Ringing-state
- OK
- An outgoing call that is disconnected by the far end during alert is not disconnected locally. Typically, the provider may play a message to the effect that the call has been rejected or the call can not be completed so that the calling user will hang up. This may be OK, however, it may create issues with automated calls (e.g. fax or modem) which do not listen to the announcement and keep waiting for the far end to accept the call.
- CLIR
- OK
- Clip No Screening (CLNS)
- CLIP no screening (CLNS) is not possible, that is, outgoing calls can only have the own subscriber number (or extension), no foreign numbers as calling line id. This affects for example externally forwarded and mobility calls. Call redirection using the SIP 302 Redirect header is supported by the provider. Rerouting can be enabled by setting the Reroute supported check-mark in the corresponding Trunk object configuration. Also, the Interworking check-mark must be set in the route used for calls from and to the SIP provider.
- However, during our test other interop problems were discovered when the Interworking Flag is enabled. Therefore it is not recommended to use the call redirection via SIP 302 Redirect header.
- Also, there is no other method available for this provider to make sure externally forwarded calls will show proper calling line identification (CLI). In this case, we recommend to set the Set Calling = Diverting No check-mark in the PBX Trunk object. This way, the forwarded call will at least carry the diverting party number (DGPN) as calling party number (CGPN/CLI) when alerting at the forwarded-to target. Otherwise it would either show no CLI at all or the lowest subscriber number associated with the trunk only.
- COLP
- Outbound calls to the PSTN show the correct connected number. However incoming calls from the PSTN do not.
- A caller from the PSTN will receive an incorrect connected number that differs from the dialled number. This might lead to the caller cancelling the call.
- For outbound calls to the PSTN, an update of the connected number is not signalled to the caller.
- Early-Media
- The provider supports early-media for outbound calls (hence inbound early media) to the PSTN.
- Fax
- Transport of faxes to/from the PSTN via G.711 codec was tested successfully. However, all fax endpoints must be configured with exclusive codec "G711A".
- Transport of faxes using T.38 worked to onnet destinations. However it failed to PSTN destination. Fallback to audiofax worked.
- As a result, T.38 is enabled on the SIP-interface, the use of audio-fax is necessary.
- Codecs
- supported to/from PSTN: G711A, G711U and G729
- supported onnet (VoIP to VoIP): G711A, G711U and G729
- IP-Fragmentation
- OK
- Large SIP messages
- OK
- Reverse Media Negotiation
- OK
- Mobility Calls
- Transmitting DTMF-tones as SIP-INFO messages is not supported, however mobility calls are still possible as in the media-relay configuration, the SBC will convey DTMF signalling to the PBX.
- Neither Clip no screening (CLNS) nor call redirection using the SIP Diversion: or History-Info is supported. Calls forwarded to mobility devices will thus not have the original callers calling line id (CLI). In this case, we recommend to set the Set Calling = Diverting No check-mark in the PBX Trunk object. This way, the mobility call will at least carry the mobility user's own extension as calling party number (CGPN/CLI) when alerting at the mobile device. Otherwise it would either show no CLI at all or the lowest subscriber number associated with the trunk only.
- SRTP
- The provider does not support audio encryption using SRTP.
- Call Transfer
- OK
- Provider supports dialling subscriber numbers
- The provider does not support dialling numbers in subscriber number format. Make sure to configure the Dialing Location accordingly.
Configuration
Use profile FR-OVH_Telecom-SIP_Trunk 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.