SIP Provider i4IP (NL) (kb5247)
The information in this article applies to:
- SwyxWare 11
Information und configuration hints for SIP provider i4IP (Netherlands).
I4IPis 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.
In case that the SwyxWare server is running with a private IP address and the static, public IP address is provided by NAT gateway, it is necessary to configure a STUN server in the properties of the SIP trunk group, under the tab 'SIP'. A list of public STUN servers can e.g. be found at http://www.voip-info.org/wiki/view/STUN.
I4IP is offering the possibility to configure the SIP Trunk on the provider side via a web interface. Please be aware that changes in the settings must be reflected by the SwyxWare setting and adopted accordingly.
For FAX transmission via T.38, I4IP is offering separate SIP trunk. If this is required, a separate SIP trunk group must be created and a corresponding SIP trunk. For the trunk group, the routing record must have a higher priority than the one f the other trunk group. Additionally, the FAX User must be configured as exclusive user for that trunk group.
Numberblock: +31 36 1234560 ... +31 36 1234569
In this case, the SIP URI must be entered in the format 036123456*@*.
For your convenience the generated CustomProviderProfiles.config is available for download 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).
Important: From SwyxWare 126.96.36.199 on, the provider profile for i4IP 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
- Holding and retrieving calls
- Toggeling between two calls
- Call transfer
- Mutually supported codecs:
- Incoming/outgoing DTMF signaling in accordance with via RFC2833
- T38 negotiation and FAX transmission
CLIP No Screening: Not supported by i4IP
06/05/2019 mit SwyxWare 188.8.131.52
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.