SIP Provider SpeakUp (NL)

General

The SIP Trunk from SpeakUp (NL) was first tested and released with a SwyxWare 2011R2.

SpeakUp is offering a SIP trunk with user authentication. You have received information about UserID, UserName and UserPassword, whereas the naming may differ, or you might have only received UserName and -password. In this case, UserID and UserName are identical. 

Platforms

SwyxWare

The SIP Trunk from SpeakUp (NL) can be used without restrictions from SwyxWare 2011R2 on.

SwyxON

The SIP Trunk from SpeakUp (NL) is not released for central connection in the data center.

Configuration

When creating the SIP trunk group, select the profile 'SpeakUp (NL)'.

Tested Features

• Incoming/outgoing national calls
• Incoming/outgoing international calls
• Correct Calling Line Identification (CLI) on national and international calls
• Holding and retrieving calls
• Toggeling between two calls
• Call transfer
• Conferencing
• Mutually supported codecs: G.711a/ G.711µ/ G.729
• Incoming/outgoing DTMF signaling in accordance with via RFC2833
• T.38 negotiation and FAX transmission

T38 / FAX support: 

It is possible to use an ordinary SIP trunk from SpeakUp for T.38 negotiation and FAX transmission. Since SpeakUp does not perform any transcoding, this relies on the end-to-end support of T.38. Additionally, SpeakUp is offering dedicated T.38 SIP trunks. The following steps are necessary to integrate the T.38 SIP trunk from SpeakUp:

1. Creation of a second SIP trunkgroup, profile: SpeakUp (NL)
2. The entries for SIP Registrar and Proxy for this second trunkgroup muss be changed to t38-sbc.speakup.nl
3. Creation of the associated SIP trunk (Account, numbers)
4. A public number of the available T.38 number range muss be assigned to all FAX channels
5. The routing record for the T.38 SIP trunkgroup must have a higher priority than the routing record for the actual Voice SIP trunkgroup. Additionally, usage of the T.38 trunkgroup must be limited to the number that was assigned to the FAX channels

With this configuration, the T.38 calls are assigning the correct SIP trunk. On the SIP level, the caller ID will be the number that was assigned to the FAX channels. The actual number will be signaled as FAX-station ID in the T.38 protocol.

Restrictions

• CLIP No Screening is not allowed in the Netherlands

Test date

01/10/2012 with SwyxWare2011R2, QF3
30/01/2014 with SwyxWare2013R3
02/06/2015 with SwyxWare2015R2

Disclaimer

Verifying interoperability between different SIP providers and the Swyx solution is part of the Enreach Technology Alliance Programme (TAP) tasks. Due to different implementations of the SIP RFCs, it is necessary to determine and provide an individual configuration for each SIP provider.

Within the TAP, Enreach tests a large number of national and international SIP providers in order to make statements about the interoperability with the Swyx solution and the functional scope of the respective SIP trunk. These results and, if needed, configuration advice are published in Help Center articles.

Enreach is in close contact with selected SIP providers to ensure a quick troubleshooting in case of incompatibilities. In addition, tests are repeated at regular intervals to ensure consistent quality.

Despite regular retests it cannot be excluded that incompatibilities with the Swyx solution may occur due to changes in the SIP connection on the provider side or that the provided profile is no longer valid. After creating the trunk group or SIP trunk, the profile settings should be compared with the provider's information and adjusted accordingly in case of deviations.

However, should incompatibilities or problems occur with a tested SIP trunk, no claims for recourse against Enreach GmbH can be derived from this. In such cases, you can contact Enreach Support via your specialist dealer.

The third-party contact information included in this article is provided to help you find the technical support you need. This contact information is subject to change without notice. Swyx in no way guarantees the accuracy of this third-party contact information nor is responsible for it's content.