SIP Provider MDCC (DE)

The SIP Trunk from MDCC is not released for central connection in the data center.

 

When creating the actual SIP trunk, a SIP URI must be entered after entering the phone number range so that incoming calls can be assigned. The assigned number block must be taken into account in the correct format.

Example

Number block: +49 391 223344550... +49 361 223344559

In this case, the SIP URI must be entered in the format +493912233445*@*.

Codec Configuration

In the codec dialog for FAX transmission via T.38 the two options "Remove T.38 codec from initial invite" and "Prohibit T.38 reinvite by sender" must be activated.

• 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
  • G.711u
• Incoming/outgoing DTMF signaling in accordance with via RFC2833
• FAX transmission via T.38 and G.711 fallback

Restrictions

None

Test date

18/08/2023 on SwyxWare 13.27

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.