Blink contact management has been completely refactored starting with Blink Pro 1.9.0 and Blink Lite 1.7.0.

Performance¶

• Faster load at start
• Faster processing for merging XCAP changes
• XCAP documents are fetched in parallel

User Interface¶

• New Edit Contact panel to manage all new features
• Subscription policy can be managed easily inside the edit contact panel
• New button for creating Contacts, Groups and scrolling to a particular Group
• Cmd L Shortcut to collapse/expand the current group
• Drag and drop possible from Contacts from Address Book Group to Blink Groups
• Merge Contacts when drag and drop a Contact on top of another
• Move Contacts when drag and drop between Groups
• Address Book addresses are aggregated per Contact
• Right click on Contact to start session to any address part of the Contact
• Address Book Contacts can be added to the Contacts List
• LDAP results can be added to the Contacts List
• LDAP results can be appended to existing Contacts
• Contact can be edited when right click on its Favourite entry

Contacts¶

• Each Contact can have multiple addresses
• Each address can have a type
• Each Contact can be present in multiple groups or no group

Groups¶

• New Groups added for contacts with no groups and all contacts
• Groups can be collapsed and expanded using Cmd-L shortcut

Backup and Restore¶

• All Contact attributes are preserved
• Groups and Contact group membership are part of the backup
• Automatic weekly backup
• Automatic backup when migrating from a previous (< 1.9.0) Blink version

XCAP Storage¶

• All changes are serialized and multiple clients can perform concurrent changes on other attrributes of same Contact
• Multiple changes are performed atomically in a transaction
• Implemented OMA specifications
• Contacts are now ready to handle Presence and Dialog Events (roadmap)

SylkServer can now act as a transparent gateway between SIP and XMPP protocols. This functionality can be used by a SIP service provider to bridge out to XMPP domains or to receive incoming requests from XMPP domains for its local SIP users. In a similar fashion, a XMPP service provider can use the gateway to bridge out to SIP domains and handle incoming requestes from SIP domains to the XMPP users it serves.

A chat media session or a presence dialog initiated by an incoming connection on the XMPP side is translated into an outgoing request on the SIP side and the other way around. To make this possible, proper SIP or XMPP records must exists into the DNS zone for the domain that needs the gateway service.

A complete description of the gateway design and its implementation can be found here: DesignXMPP

Features¶

The following gateway features have been implemented, click on their name to see a full description:

• Instant Messaging (Chat sessions and Single messages)
• Presence translation (SIMPLE)
• Multi-party conferencing for chat (XMPP MUC and MSRP switch) - 2013-02-13

Availability¶

The software is now available as source code download. To use the software you also need the latest development branch of SIP SIMPLE Client SDK. You can manually build a Debian package from the sources http://projects.ag-projects.com/projects/documentation/wiki/Repositories#Manual-Installation

Live testing¶

SylkServer has been integrated with SIP2SIP service

Using a sip2sip.info account, one can start a MSRP chat session to a @gmail.com or @jabber.org address or from these XMPP domain to any @sip2sip.info user. The SIP server will route the session request through the SylkServer XMPP gateway application and chat sessions can be established between the SIP users of sip2sip domain and XMPP users of gmail.com and jabber.com domains.

For testing Presence functionality you can use any SIP SIMPLE client or the command line tools sip-subscribe-presence, sip-subscribe-winfo and sip-publish-presence from the sipclients package

Roadmap¶

• Public release as a Debian package
• Jingle audio and video sessions
• File transfers

It is now possible to have access in real time to the SIP trace and RTP media statistics for each session. To access the trace:

Using Blink¶

Select your SIP2SIP account and go to menu Tools -> Call History

Other clients¶

Login using your SIP account credentials to http://x.sip2sip.info and go to History tab.

Each session has a Trace link, click on it. A new web page opens listing all SIP packets logged by the server. Click on each packet to expand its content.

The next release of SIP SIMPLE Client SDK will feature a comprehensive suite of SIP SIMPLE Presence specifications:

• SIP Specific Event Notification (SUBSCRIBE and NOTIFY methods) RFC3265
• SIP Extension for Event State Publication (PUBLISH method) RFC3903
• Presence Data Model (PIDF) RFC3863, RFC4479, RFC4480
• Watcher-info Event Package RFC3857, RFC3858
• Rich Presence Extensions to PIDF RFC4480
• Contact Information Extension to PIDF RFC4482
• User Agent Capability Extension to PIDF RFC5196
• XCAP Protocol RFC4825
• Common Policy RFC4745
• Presence Rules RFC5025
• Resource Lists RFC4826
• RLS Services RFC4826
• PIDF manipulation RFC4827
• XCAP Diff RFC5874
• OMA Reference Release Definition for XDM v1.1 and Presence SIMPLE v1.1 Implementation Guidelines
• OMA XML Document Management V1.1