TekSIP is a SIP Registrar / Proxy for Windows.
Version: 4.1.3TekSIP is a SIP Registrar and Proxy.
License: Free To Try $239.00
Operating System: Windows
TekSIP tested on Microsoft Windows (Vista, Windows 7 / 8/10, 2008-2019 Server).
TekSIP complies with RFC 3261, RFC 3263, RFC 3311, RFC 3581 and RFC 3891. It supports NAT traversal, UPnP and ENUM. Please see technical details about NAT traversal in Readme.txt.
You can select IP address to be listened, alternative SIP routes for outgouing calls.
TekSIP has a Presence Server (SIP / SIMPLE based). You can also log session details and errors into a log file.
TekSIP supports RADIUS Authentication (RFC 2865) and RADIUS Accounting (RFC 2866).
TekSIP can optionally act as a B2BUA for incoming 3xx SIP responses.
TekSIP can act as RTP Proxy and record auido treams if RTP proxy is enabled.
TekSIP can register to upstream SIP servers to receive incoming calls.
TekSIP monitors failed registration and call attempts from suspicious endpoints and blacklists them.
You can monitor black listed endpoints through TekSIP Manager and you can remove black listed endpoints from quarantine list if required. You can also ban specific user agents.
TekSIP runs as a Windows service.
TekSIP supports auto provisioning of IP phones based on SUBSCRIBE / NOTIFY PnP mechanism.
TekSIP supports IPv6 with IPv4.
You can deploy TekSIP as a proxy for standard SIP phones to connect to a Microsoft Lync system. Lync supports IP phones only if they support SRTP with SIP TLS transport.
TekSIP register standard SIP phones on behalf of them to a Lync system and maintain their presence status.
Version 4.1.3: Route hunting [Requires SP license]. WebRTC improvements.
Version 4.1.0: Routing has two sub sections; Destinations and Routes. You can have multiple route entries for a number prefix. Media Encryption option in route profiles for outgoing calls when RTP proxy is enabled. IPv6 support and improved RTP stack.
Version 4.0.6: IPv6 support and improved RTP stack.
Version 4.0.4: Route capacity options and IP filtering are added.
Version 4.0.3: .NET Framework 4.6.1 upgrade. Improved TCP and RTCP stack.
Version 3.9.0: You can specify a routing entry for a prefix which routes calls to a dynamically registered endpoint (Extension) in SP edition