Version 1.5 has just been released with the following features.
SSL/TLS Rewrite
A new secure socket abstraction is implemented in PJLIB. The API is implemented using the native CSecureSocket for Symbian platform and OpenSSL for other platforms. With this API, new type of implementations (such as native Windows SSPI) could be written in the future.
The SIP TLS transport has been rewritten to make use of this secure socket API, while maintaining the existing SIP TLS transport API. The secure socket API will also make way for other SSL/TLS based transports in the future, such as TLS TURN client connection.
QoS Framework
All transports in the library (such as SIP UDP/TCP/TLS transports, UDP media transport, and STUN/TURN/ICE transports) have been equipped with QoS (Quality of Service) settings. The QoS framework abstracts QoS technologies such as the Type of Service/DiffServ Code Point (ToS/DSCP) fields, Wi-Fi Multimedia (WMM) priorities, and IEEE 802.1p tagging (via SO_PRIORITY) in a generic manner, while providing flexibility for applications to adjust the settings manually if wanted.
The QoS framework has been tested on Symbian, Windows Mobile 6, Linux, and MacOS X. Note that currently it is not available on Windows XP and later.
Please see the new QoS wiki page for more info.
Message Summary/Message Waiting Indication (MWI) Support
Added support for both subscription based MWI (RFC 3842) and unsolicited MWI that is used by a popular PBX. For more information please see ticket #982.
Presence Enhancements
Ticket #937 among other things implemented automatic buddy’s presence resubscription upon receiving several specific termination causes. Ticket #411 and #364 improved the PUBLISH request handling.
SIP INVITE/CANCEL Destination Fixes
Ticket #917 and #936 fixed the following problems:
- CANCEL request may be sent to different server than the INVITE when DNS SRV is used
- INVITE request retry because of 401/407 response may be sent to different server than the INVITE when DNS SRV is used
- CANCEL request will be sent with UDP if the INVITE was sent with TCP because of 1300 bytes message size/MTU limit (it must be sent with the same transport)
Please get the new version from PJSIP download page as usual.
pjsip blog 
There is a bug in PJNAT or test server.
When client performs longterm challenge with server and sends wrong message integrity attribute – server responds with 401 error.
Maybe better is Bad Request ?
The behavior is correct, as the spec mandates the server to send 401, see http://tools.ietf.org/html/rfc5389#section-10.2.2
Hello,
I have troubles with PocketPJ version. I fill in all fields in settings form: Domain=sipnet.ru; User=nil2l; Passwd=pwd; DNS=sipnet.ru and the rest fields are default.
Then it passes all states and on “Registering…” idles few seconds
and gives error (503?) with this text
“SIP registration error: Service Unavailable”
I guess I set wrong DNS field or another params which are defaults.
Give me please some working example of this settings.
P.S. There only 3 params in fring app for SIP: usr, pwd and proxy address. And it works well.
found a bug:
at file:pjproject\pjsip\src\pjsip\sip_transport.c
function:send_raw_resolver_callback
line:1375
after call the pjsip_tpmgr_send_raw, the app will crash; because raw_data and tdata use the same pool,
after call the pjsip_tpmgr_send_raw, the pool had released.
thanks.
That is exactly what it’s supposed to do, so I’m not sure where the bug is. Also I couldn’t find the function name and/or location that you mentioned.
For problems like these, lets discuss it in the PJSIP mailing list instead.
hi,
Is there a way to configure the TLS on windows mobile. I am using pjsip 1.5
thanks & regards
susheel tickoo