INFO

SIP Provider ecotel sipTrunk 2.0 (DE) (kb4989)

The information in this article applies to:

  • SwyxWare 11.00

[ Summary | Information | Links ]


Summary

Information und configuration hints for SIP provider ecotel, sipTrunk 2.0 (Germany).


Information

General information

The information published here applies exclusively to ecotel sipTrunk2.0, but not to sipAccount2.0.

The ecotel sipTrunk 2.0 is a SIP trunk with user authentication. You will receive information to register the SIP trunk.

Configuration

During creation of the SIP trunkgroup, profile 'ecotel sipTrunk 2.0 (DE)' has to be selected.
IMPORTANT: After creation of the SIP trunkgroup, underneath the properties of the trunkgroup, in the field 'Realm' of the 'SIP' tab, the customer individual value has to entered. This value is named 'SIP Registrar/Domain/Realm' in the documents from ecotel, i.e. '12345678.sip-ecotel.de'. Until SwyxWare 11.10.1 including, it is necessary to change the entries underneath the properties of the trunkgroup for the fields 'Registrar' and 'Proxy' from  "trunk.sip-ecotel.de" to "trunk3.sip-ecotel.de" .
During the following creation of the actual SIP trunk, when providing the registration information, in the fields 'User ID' and 'Username' the 'Benutzername' from the ecotel documents have to be entered.
After specifying the number range, it is necessary to configure a SIP URI for the trunk. The assigned number block and the numberformat must be considered.

Example
Numberblock: +49 231 9988776600 ... +49 231 9988776699
In this case, the SIP URI must be entered in the format 004923199887766*@*.

In the codec dialog, T.38 has to be deselected as supported codec.

Tested Features

  • Incoming/outgoing national calls
  • Incoming/outgoing international calls
  • Correct Calling Line Identification (CLI) on national and international calls
  • CLIP No Screening
  • Holding and retrieving calls
  • Toggeling between two calls
  • Call transfer
  • Conferencing
  • Mutually supported codecs:
    • G.711A
  • Incoming/outgoing DTMF signaling in accordance with via RFC2833
  • Fax transmission via G.711

Restrictions
FAX transmission via T.38 is not supported

Test date:
03/01/2018 with SwyxWare 11.10.1

Overview of tested SIP provider


Links

As far as software supplied or used by us, includes open source elements the additional terms under https://www.swyx.com/open-source apply in addition. An overview which products from the Swyx portfolio include open source elements and which open source license is relevant can be found under https://www.swyx.com/open-source.

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.


Comment

Comment on this article



If we have any follow-up questions, where can we contact you?

E-Mail Address (optional)


Note

This feedback form can't be used for support requests. Those requests must be directed to your Swyx reseller or distributor.