SIP Client Resolver determines the target clients by comparing the Request-URI of the incoming SIP request to the information provided in the ECOM plug-in resource file. This resource file is an XML file. All client applications using Client Resolver must be implemented as ECOM plug-ins and must have capabilities.
An application must declare capabilities, that are the supported content types and media formats that use the SIP headers and SDP m-lines. The capabilities must be declared in the code of the plug-in, in the XML file, or in the opaque_data field of the resource file.
The following is the DTD for the ECOM plug-in’s resource file:
The resource ( .rss ) file contains the XML file and the following information:
dll_uid and implementation_uid : These UIDs are supplied on request to Symbian Signed .
Note : These UIDs can be the same.
interface_uid : This must have the value 0x102010DD .
default_data : The application UID (without 0x).
opaque_data : The application capabilities in XML format. This field is empty if application capabilities are defined in the implementation.
The following illustration shows how the SIP Client Resolver subsystem resolves the target client implementation and requests the resolved client to connect to the SIP implementation. In this plan, the default resolution logic is applied.
The following list describes how the target client is resolved using CSIPResolvedClient .
The user receives a SIP request and the target client is defined using CSIPResolvedClient .
The user requests the SIP Client Resolver API implementation for a channel UI to connect to the user.
The user requests the target client to connect to SIP with the resolved UID if there is no connection with the resolved channel UID.
The SIP Client Resolver API implementation starts the target client.
Copyright ©2010 Nokia Corporation and/or its subsidiary(-ies).
All rights
reserved. Unless otherwise stated, these materials are provided under the terms of the Eclipse Public License
v1.0.