Features

• Support platforms: Windows 2000/XP/Vista/7/8, iOS, Android.
• Webphone: Support IE and Firefox, Chrome.
• Support servers: Cisco CallManager, OpenSER, Kamailio, OpenSIPS, Asterisk, Mitel, Freeswitch, SIPX, Radvision, Nortel, Avaya and other SIP Platforms.
• Support development tools: Java, Objective-C, MS Visual C#, MS Visual Basic, MS Visual C++, Delphi XE2, Javascript/HTML.
• Audio codecs(Windows OS): G.711 aLaw/uLaw, G.722.1, G.722, SPEEX, SPEEX-WB, AMR, AMR-WB, GSM, iLBC, G.729, isac, isac-wb.
• Audio codecs(iOS, Android): G.729, PCMA, PCMU, GSM, G.722, AMR, AMR-WB, SPEEX, SPEEXWB
• AMR, AMR-WB codec: comply with RFC 4867 support, inlcude Bandwidth- Efficient and Octet - Aligned mode, amr-red, amr-maxptime, ptime.
• Video codecs(Windows OS): H.263, H.263-1998, H.264, VP8.
• Video codecs(iOS, Android): H.263, H.263+, H.264.
• Audio record: record audio as wav, ogg and MP3 file.
• Video record: record video as AVI file.
• Support 720P, SVGA, XVGA, VGA, QVGA, CIF, QCIF resolution.
• Support play AVI file to remote side.
• Support play wave file to remote side.
• Allows send PCM data to remote side instead of microphone input.
• Acoustic Echo Cancellation, Automatic gain control, Comfort Noise Generation, Voice Activity Detector support.
• Call transfer: Attended transfer, Blind transfer.
• Call forwarding
• Call hold, mute speaker, mute microphone.
• Do not disturb(DND), Auto answer(AA).
• Audio conferencing(Windows OS): support maximum 100 parties audio conferencing.
• Video conferencing(Windows OS): support maximum 30 parties video conferencing.
• STUN support.
• IPv6 support.
• Outbound proxy server support.
• QoS support.
• Support TLS/SRTP(usually use to avoid SIP blocking)
• Access incoming aduio stream directly.
• Access incoming video stream directly.
• Access incoming SIP message directly.
• Access received & sending RTP packet directly.
• Support adding custom SIP header.
• Support modify SIP header.
• Support send "INFO", "OPTIONS" adn "MESSAGE" message.
• IM Support: SIMPLE(Presence, Subscribe, Pager message) and XMPP.
• Message waiting Indicator(MWI)
• DTMF support: Send DTMF tone(RFC2833 and SIP INFO method), detect DTMF tone(RFC2833 and SIP INFO method).
• Multiple Calls.
• Audio Tuning Wizard and device manage support.
• Video Tuning Wizard and device manage support.
• Microphone & Speaker Device Selector
• Microphone & Speaker Volume control

Supported RFCs

• RFC 3261: SIP: Session Initiation Protocol
• RFC 3420: Internet Media Type message/sipfrag
• RFC 4508: Conveying Feature Tags with the Session Initiation Protocol (SIP) REFER Method
• RFC 4566: SDP: Session Description Protocol
• RFC 4867: RTP Payload Format and File Storage Format for the Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate Wideband (AMR-WB) Audio Codecs.
• RFC 3711: The Secure Real-time Transport Protocol (SRTP)
• RFC 3389: Real-time Transport Protocol (RTP) Payload for Comfort Noise (CN).
• RFC 1847: Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted
• RFC 2045: Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies
• RFC 2046: Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types
• RFC 2181: Clarifications to the DNS Specification
• RFC 2617: HTTP Authentication: Basic and Digest Access Authentication
• RFC 3428: Session Initiation Protocol (SIP) Extension for Instant Messaging
• RFC 3550: RTP: A Transport Protocol for Real-Time Applications.
• RFC 3265: Session Initiation Protocol (SIP)-Specific Event Notification
• RFC 3311: The SIP UPDATE Method
• RFC 3263: Session Initiation Protocol (SIP): Locating SIP Servers
• RFC 3891: The Session Initiation Protocol (SIP) "Replaces" Header
• RFC 3581: An Extension to the Session Initiation Protocol (SIP) for Symmetric Response Routing
• RFC 4320: Actions Addressing Identified Issues with the Session Initiation Protocol's (SIP) Non-INVITE Transaction
• RFC 3325: Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks
• RFC 3326: The Reason Header Field for the Session Initiation Protocol (SIP)
• RFC 2782: A DNS RR for specifying the location of services (DNS SRV)
• RFC 2915: The Naming Authority Pointer (NAPTR) DNS Resource Record
• RFC 2976: The SIP INFO Method
• RFC 3486: Compressing the Session Initiation Protocol (SIP)
• RFC 3515: The Session Initiation Protocol (SIP) Refer Method
• RFC 4474: Enhancements for Authenticated Identity Management in the Session Initiation Protocol (SIP)
• RFC 3892: The Session Initiation Protocol (SIP) Referred-By Mechanism
• RFC 3903: Session Initiation Protocol (SIP) Extension for Event State Publication
• RFC 4028: Session Timers

Partially Supported RFCs

• RFC 3264: An Offer/Answer Model with the Session Description Protocol (SDP) (This is only partially supported, since many of the responsibilities are up to the app)
• RFC 3327: Session Initiation Protocol (SIP) Extension Header Field for Registering Non-Adjacent Contacts (Only the Path header field is supported. No logic is provided. This will change when the outbound implementation is merged in.)
• RFC 3608: Session Initiation Protocol (SIP) Extension Header Field for Service Route Discovery During Registration (The Service-Route header field is supported, registrar mechanism is not. The endpoint mechanism appears to be supported).
• RFC 3388: Grouping of Media Lines in the Session Description Protocol (SDP) (trivial support; apps have access to group attributes, but groups are not handled for the app)
• RFC 3313: Private Session Initiation Protocol (SIP) Extensions for Media Authorization (Only the P-Media-Authorization header field is supported. No logic is provided.)
• RFC 4488: Suppression of Session Initiation Protocol (SIP) REFER Method Implicit Subscription (The Refer-Sub header field is supported, and there is some endpoint support.)
• RFC 3841: Caller Preferences for the Session Initiation Protocol (SIP) (Only Accept-Contact, Reject-Contact, and Request-Disposition header fields are supported. No proxy support.)
• RFC 3323: A Privacy Mechanism for the Session Initiation Protocol (SIP) (The Privacy header field is supported. Server logic is not provided, but endpoint logic is.)
• RFC 3329: Security Mechanism Agreement for the Session Initiation Protocol (SIP) (Only the Security-Client, Security-Server, and Security-Verify header fields are supported, the proxy mechanisms are not.)
• RFC 3605: Real Time Control Protocol (RTCP) attribute in Session Description Protocol (SDP) (trivial support)
• RFC 4483: A Mechanism for Content Indirection in Session Initiation Protocol (SIP) Messages (Trivially supported, the application layer must do most of the work.)
• RFC 3911: The Session Initiation Protocol (SIP) "Join" Header (Only the Join header field is supported, no other support.)
• RFC 3966: The tel URI for Telephone Numbers (Partial support. The isub and phone-context parameters are not supported. The comparator isn't implemented.)