The HSIPT trunk from Brirtish Telecom (BT) trunk is a SIP trunk with user authentication. You have received information about UserID, UserName and UserPassword, whereas the nameing may differ.
BT is operating with a number of different servers. Therefore it is not possible to preconfigure the Registrar server, the Proxy Server and the Realm in the "SIP" tab of the Trunkgroup Properties dialog. In this field, please enter the information that BT has named you.
Configuration
Important: From SwyxWare 11.00 on, the provider profile for British Telecom HSIPT (UK) is available in the list of provider profiles and the CustomProviderProfiles.config is no longer necessary.
During creation of the SIP Trunkgroup, the profile 'British HSIPT Telecom (UK)' must be selected. A detailed configuration guide can be downloaded at the end of this article.
In case that the SwyxWare server is running with a private IP address and the 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.
Tested Features
- Incoming/outgoing national calls
- Correct Calling Line Identification (CLI) on national
- Holding and retrieving calls
- Toggeling between two calls
- Call transfer
- Conferencing
- Mutually supported codecs: G.711a/ G.711µ/ G.722/ G.729/ T.38 for FAX negotiation
- Incoming/outgoing DTMF signaling in accordance with via RFC2833
- T.38 Negotiation and FAX Transmission
Restrictions:
CLIP No Screening is not supported
Test date:
05/07/2017 with SwyxWare 2015 R40.3.0
CustomProviderProfiles_BTHSIPT(UK)
kb4957_CustomProviderProfiles_BTHSIPT(UK).zip
SwyxWareHowTo_BTHSIPT.pdf
kb4957_SwyxWareHowTo_BTHSIPT.pdf
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.
Comments
0 comments
Please sign in to leave a comment.