Howto:CH - Telecom Liechtenstein AG - Convoip Trunk SIP-Provider (2017)

From innovaphone wiki
Jump to navigation Jump to search

Summary

Tests for the Convoip_Trunk SIP trunk product of the provider Telecom_Liechtenstein_AG were completed. Test results have been last updated on October 17th, 2018. Check the history of this article for the date of the first publication of the testreport. <internal>Provider SBC: TELES-SBC</internal>


List of Issues found in media-relay Configuration

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 T38ANDAUDIO
The provider does not support fallback to audio-fax if T.38 fails.
RALERT DISC
Call disconnected by far end during alert does not disconnect locally
REVERSE MEDIA
The provider does not support reverse media negotiation (a.k.a. late SDP)
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, 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, REDIR_DIVHDR, REDIR_HISTHDR


Test Results

This SIP provider requires a media-relay configuration. That is, all media traffic between the SIP provider and all endpoints must flow through the SBC. For this reason, a configuration without media-relay has not been tested and hence no test results for this configuration are listed.

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 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.
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
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.
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.
Transport of faxes using T.38 worked to onnet and PSTN destinations. However fallback to audiofax failed.
As a result, T.38 is disabled on the SIP-interface and the use of audio-fax is necessary.
Codecs
supported to/from PSTN: G711A and G711U
supported onnet (VoIP to VoIP): G711A, G711U, G722 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.
SRTP
The provider supports audio encryption using SRTP for onnet calls.
Dialing of Subscriber Numbers
The provider does not support dialling numbers in subscriber number format. Make sure to configure the Dialing Location accordingly.
Call Transfer
OK


Configuration

Use profile CH-Telecom_Liechtenstein_AG-Convoip_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.