TekSIP is a SIP Registrar and Proxy. TekSIP tested on Microsoft Windows XP, Vista, Windows 7, and Windows 2003/2008 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. 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. Please click here for more details.
What's new in this version:
- TekSIP can run in 64 bits mode in 64 bits systems.
- TekSIP uses built-in database engine, TekSIP.mdb is not used anymore. You need to re-enter extension and routing information.