SIP Provider Vodafone (DE) (kb4919)
The information in this article applies to:
- SwyxWare 11
- SwyxWare 2015
Information und configuration hints for SIP provider Vodafone (Germany).
The Vodafone SIP Trunk V3.2.1 was first tested and released with a SwyxWare 2015 R40.1.
The Vodafone SIP Trunk R.4a was first tested and released with a SwyxWare 126.96.36.199. A migration from Vodafone SIP Trunk V3.2.1 to R.4a is possible without any problems, since both versions of the SIP Trunk can use the same provider profile.
Vodafone is offering a registerless SIP trunk. This means that the authentication is based on the public IP address of the SwyxWare server. Therefore, you need a static, public IP address from your ISP. For SIP communication with a provider SwyxWare does not use the standard SIP port 5060 but the port 65002. When ordering a Vodafone SIP Trunk it must be pointed out that SwyxWare communicates via this SIP Trunk so that the correct port configuration can be set up on the Vodafone side. For a connection via a NAT component a port forwarding rule must be set up, from the public port 65002 of the NAT gateway to the IP address of the SwyxWare server with port 65002. For a direct connection no additional adjustments have to be made.
You may possibly also receive 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. However, this information is not needed.
SwyxWare: The SIP Trunk from Vodafone can be used with SwyxWare 2015 R40.1 or higher. When using an earlier version of SwyxWare, incompatibilities cannot be excluded and the use is at the user's own risk.
SwyxON: The SIP Trunk from Vodafone is not suitable for operation in data centers.
During creation of the SIP Trunkgroup, profile 'Vodafone (DE)' has to be selected. If the profile is not included in the corresponding list, you can download the required CustomProviderProfiles.config for SwyxWare at the end of this article. Extended information about how to use this file can be found at Configuration and Adaptation of SIP Providers via Provider Profiles (kb3436).
During creation of the actual trunk, in the codec configuration dialog, T.38 has to be deselected as supported codec. This step could also be performed afterwards in the properties of the SIP trunk, underneath the 'Codecs' tab.
Important: From SwyxWare 2015 R40.2 on, the provider profile for Vodafone is already available in the list of provider profiles and the CustomProviderProfiles.config is no longer necessary.
- Incoming/outgoing national calls
- Incoming/outgoing international calls
- Correct Calling Line Identification (CLI) on national and international calls
- CLIP No Screening (SIP trunk R.4a)
- Holding and retrieving calls
- Toggeling between two calls
- Call transfer
Mutually supported codec:
- Incoming/outgoing DTMF signaling in accordance with via RFC2833
- FAX transmission via G.711
- CLIP No Screening did not work in our tests when ISDN network was the target (SIP Trunk V3.2.1 only)
- No announcement when a mobile user puts a call on hold (SIP Trunk V3.2.1 only)
20/04/2017: SIP Trunk V3.2.1 with SwyxWare 2015 R40.1
22/01/2019: SIP Trunk R.4a with SwyxWare 188.8.131.52
- CustomProviderProfiles_Vodafone (DE)
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.