| Juphoon SIP
Complies with RFCs and Drafts |
| RFC 3261 |
Session Initiation Protocol |
| RFC 3262 |
Reliability of Provisional Response |
| RFC 3263 |
Locating SIP Servers |
| RFC 3264 |
An Offer-Answer Model with Session Description |
| RFC 3265 |
Specific Event Notification |
| RFC 3311 |
The SIP UPDATE method |
| RFC 3312 |
Integration of Resource Management and Session Initiation Protocol (SIP) |
| RFC 3313 |
Private SIP Extensions for Media Authorization |
| RFC 3323 |
A Private mechanism for the SIP |
| RFC 3325 |
Private Extensions to the SIP for Asserted
Identity within Trusted Networks |
| RFC 3326 |
The Reason Header |
| RFC 3329 |
Security Mechanism Agreement for the SIP |
| RFC 3372 |
SIP for Telephones (SIP-T): Context and
Architectures |
| RFC 3428 |
Session Initiation Protocol (SIP) Extension
for Instant Messaging |
| RFC 3515 |
The REFER method RFC 2806 URLs for Telephone
Calls |
| RFC 2806 |
URLs for Telephone Calls |
| RFC 2976 |
The SIP INFO Method |
| RFC 3204 |
MIME media types for ISUP and QSIG Objects |
| RFC 3581 |
An Extension to the SIP for Symmetric Response
Routing |
| RFC 3841 |
Caller Preferences for the Session Initiation Protocol (SIP) |
| RFC 3891 |
The Session Initiation Protocol (SIP) "Replaces" Header |
| RFC 3892 |
The Session Initiation Protocol (SIP) Referred-By Mechanism |
| RFC 3903 |
Session Initiation Protocol (SIP) Extension
for Event State Publication |
| RFC 3911 |
The Session Initiation Protocol (SIP) "Join"
Header |
| RFC 3455 |
Private Header (P-Header) Extensions to the
Session Initiation Protocol (SIP) for the 3GPP |
| RFC 3327 |
SIP Extension Header Field for Registering
Non-Adjacent Contacts |
| RFC 3608 |
SIP Extension Header Field for Service Route
Discovery During Registration |
| RFC 2368 |
The mailto URL scheme RFC 2327 Session Description Protocol |
| RFC 4028 |
Session Timers in the Session Initiation Protocol (SIP) |
|
| Juphoon SIP Codec |
- Fast scan, one time ABNF codec (hand written parser)
- Over 86 headers explicit parsing
- SIP, SIPS, TEL, IM, MAILTO, ABSO URI scheme
- 3GPP \ IMS SIP services headers
- Security mechanism headers
- MIME body and multi-bodies
- Entire or partial parsing of headers, can be
configured
- Any extension of SIP methods and headers comply
with the SIP ABNF
- SDP message body
- 3GPP Extension
- Qos support
- Sigcomp support |
| Juphoon SIP Process |
- INVITE Client/Server, non-INVITE Client/Server
transactions
- Early dialog, established dialog and multi dialog
- Dialog forking
- Auto completing message header
- Classified and Organized primitives of SIP message
- Only need about 2K bytes memory per session/call |
| Juphoon SIP Transport |
- UDP/TCP transport
- NAT Traversal for SIP
- DNS (NAPTR, SRV, A record support) |
| Juphoon SIP Applications |
- Multi-upper users of multi-entities
- Support User Agent, Proxy Server, Redirect Server,
Registrar
|
| Juphoon SIP Sipping
Services Support |
- Call Hold
- Consultation Hold
- Music On Hold
- Transfer - Unattended (subscribe/notify)
- Transfer - Attended (subscribe/notify)
- Transfer - Instant Messaging
- Call Forwarding Unconditional
- Call Forwarding - Busy
- Call Forwarding - No Answer
- 3-way Conference - Third Party is Added
- 3-way Conference - Third Party Joins
- Single Line Extension
- Fined - Me
- Call Management (Incoming Call Screening)
- Call Management (Outgoing Call Screening)
- Call Park
- Call Pickup, two (or more) parts can pick up each
others' calls
- Automatic Redial
- Click to Dial
- ...
|
| Juphoon SIP Library |
- Win32(VC6.0)
lsip.lib 1578k(include liblsip.a & libsip.a), zos.lib 551k, sdp.lib 173k, lrtp.lib 90k
- Linux(GCC 3.2.2)
liblsip.a 273k libsip.a 350k, libzos.a 273k, libsdp.a 66k, liblrtp.a 48k
- VxWorks(Cygnus 2.7.2 (GCC))
liblsip.a 286k libsip.a 432k libzos.a 295k libsdp.a 81k liblrtp.a 47k
|
| Juphoon SIP Other Key
Technologies |
- Resource statistics and powerful tracing,
logging and error handling
- Powerful ABNF parser
- Powerful Timer mechanism
- Powerful FSM mechanism
- Resources (Dbuf, session, dialog, transaction etc.)
dump control
- Stable and excellent performance in data buffer
control
- Thread safe and simple communication
- Multi-timer for applications in different
scenes
- Resource Garbage Bin
- Strict Coding rules
- Uniform naming conventions
|
