No notification from Connection Monitor Server API (Known Issue)
The Connection Monitor Server API (ConnMon) does not send a notification if two different applications connect to the network through the same access point(AP) and using the same network bearer.
The Connection Monitor Server API (ConnMon) sends a notification (EConnMonCreateConnection) when a new connection is created. However, when there's already an active connection and another application requests a connection, the existing connection is shared between both applications. ConnMon does not send a notification in this situation as no new connection is established.
A new connection would be established only if the application specifically requests a different bearer (for instance, WLAN vs. GPRS) or a connection method (IAP) with a different access point name (APN).
Instead of monitoring subconnections, it's possible to request connection attributes from the Connection Monitor Server. This can be done by using the KClientInfo parameter for the function RConnectionMonitor::GetPckgAttribute().
With the following code, it's possible to detect if there are other applications using the same connection:
// connectionId is the ID value of a specific connection. Connection IDs
// can be obtained with RConnectionMonitor::GetConnectionInfo()
monitor.GetPckgAttribute( connectionId, 0, KClientInfo, clientBuf, status );
User::WaitForRequest( status );
if( status.Int() == KErrNone )
// Count of the clients using the connection
TUint count = clientBuf().iCount;
// The uid of the first client (there are max 10 UIDs in the array)
TUid uid = clientBuf().iUid;
The KClientInfo attribute is used to retrieve the client UID for all clients using a specific connection. The information is transferred through a package of type TConnMonClientEnumBuf. The package class has a fixed size array, and it is limited to a maximum of 10 (KConnMonMaxClientUids) UIDs.