Howto:IT - Bellnet - SIP Trunk SIP-Provider (2019): Difference between revisions

From innovaphone wiki
Jump to navigation Jump to search
(New page: == Summary == {{Template:SIP_TEST_STATUS_ongoing|update=April 29th, 2019|url=|productname=SIP_Trunk|providername=Bellnet}} === Remarks === - FAX requires exclusive G711A codec - STUN r...)
 
No edit summary
Line 1: Line 1:
== Summary ==  
== Summary ==  
{{Template:SIP_TEST_STATUS_ongoing|update=April 29th, 2019|url=|productname=SIP_Trunk|providername=Bellnet}}
{{Template:SIP_TEST_STATUS_complete|update=April 29th, 2019|url=|productname=Bell Sip Services|providername=Bellnet}}
=== Remarks ===
=== Remarks ===



Revision as of 10:30, 29 April 2019

Summary

Tests for the [ Bell Sip Services] SIP trunk product of the provider Bellnet were completed. Test results have been last updated on April 29th, 2019. Check the history of this article for the date of the first publication of the testreport.

Remarks

- FAX requires exclusive G711A codec
- STUN required on all endpoints if media-relay is not used
- Alert not signalled, 'Carrier w/o Alerting' required in all PBX 'Mobility' objects
- 'Set Calling = Diverting No' recommended in PBX 'Trunk' objects

<internal>Provider SBC: </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).
MOBILITY
The provider can not send DTMF signals via SIP-INFO messages.
REDIR 302
The provider does not support external call redirection using the SIP 302 Redirect response
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.
REVERSE MEDIA
The provider does not support reverse media negotiation (a.k.a. late SDP)
SDP RTCP MUX
The provider does not support receiving a RTCP-MUX attribute in the SDP-part of a SIP message.
Our tests of this feature have shown unstable results (that is, the feature sometimes worked and sometimes did not). This may for example be caused by different equipment used at the provider side (e.g. media gateways) which behave differently.
SIP INFO
The provider does not support conveying DTMF using the SIP-INFO method.

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_INCOMING, CONN_NR, DTMF, EARLY_MEDIA_INBOUND, FAX_AUDIO, FAX_T38_ONNET, FAX_T38, 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, SDP_ICE, SDP_RTCP_MUX, SDP_VIDEO, SIP_INFO, SRTP_INCOMING, SRTP_INTERNAL, SRTP_OUTGOING, SUBSCRIBER_NR, XFER_BLIND, XFER_CONS_ALERT, XFER_CONS_EXT, XFER_CONS

List of Issues found in media-relay Configuration

This section lists the results that differ from the results for the first configuration.

The test results for this configuration are the same, however.

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.
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. However MediaRelay is required, since the provider does not support a change of the remote RTP-endpoint during a call.
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 not successful. This will result in unwanted call termination on calls exceeding a certain time (default 30 minutes). Because of this, further tests were aborted.
Redundancy
Registration of two SIP-interfaces on the same SIP-account is not supported by the provider. As a result, you cannot have a Standby gateway/PBX using the same account for failover or load-balancing purposes.
Correct signalling of Ringing-state
OK
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.
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 and inbound calls to/from the PSTN show the correct connected number.
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".
Additionally transport of faxes to/from the PSTN using the T.38 protocol was tested successfully. However since the provider requires the MediaRelay and Exclusive-Coder setting, T.38 is not activated on the SIP-interface. The reason for this is the non-working fallback to AudioFax of the Fax-interface, in case that the SIP-interface is configured with above options. This limitation applies only to the Fax-interface. If you are not using it for fax calls, you can enable T.38 by using the "Expert Mode" at the SIP-profile.
Codecs
supported to/from PSTN: G711A and G729
supported onnet (VoIP to VoIP): G711A and G729
IP-Fragmentation
OK
Large SIP messages
OK
Reverse Media Negotiation
Reverse-media negotiation is not supported. Therefore, a media-relay with exclusive coder configuration will be activated on the SIP-interface.
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.
Dialing of Subscriber Numbers
OK
Call Transfer
OK


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.
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. However MediaRelay is required, since the provider does not support a change of the remote RTP-endpoint during a call.
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 not successful. This will result in unwanted call termination on calls exceeding a certain time (default 30 minutes). Because of this, further tests were aborted.
Redundancy
Registration of two SIP-interfaces on the same SIP-account is not supported by the provider. As a result, you cannot have a Standby gateway/PBX using the same account for failover or load-balancing purposes.
Correct signalling of Ringing-state
OK
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.
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 and inbound calls to/from the PSTN show the correct connected number.
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".
Additionally transport of faxes to/from the PSTN using the T.38 protocol was tested successfully. However since the provider requires the MediaRelay and Exclusive-Coder setting, T.38 is not activated on the SIP-interface. The reason for this is the non-working fallback to AudioFax of the Fax-interface, in case that the SIP-interface is configured with above options. This limitation applies only to the Fax-interface. If you are not using it for fax calls, you can enable T.38 by using the "Expert Mode" at the SIP-profile.
Codecs
supported to/from PSTN: G711A and G729
supported onnet (VoIP to VoIP): G711A and G729
IP-Fragmentation
OK
Large SIP messages
OK
Reverse Media Negotiation
Reverse-media negotiation is not supported. Therefore, a media-relay with exclusive coder configuration will be activated on the SIP-interface.
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.
Dialing of Subscriber Numbers
OK
Call Transfer
OK


Configuration

Use profile IT-Bellnet-SIP_Trunk in Gateway/Interfaces/SIP to configure this SIP provider.

Please note the following configuration hints:

  • FAX requires exclusive G711A codec
  • STUN required on all endpoints if media-relay is not used
  • 'Set Calling = Diverting No' recommended in PBX 'Trunk' objects
  • Alert not signalled, 'Carrier w/o Alerting' required in all PBX 'Mobility' objects
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.