Hi,
A regression was found (thanks to Jeremy Geras for reporting it) under which ClientSubscriptionHandler::onNewSubscription isn't called for the normal SUBSCRIBE/202/NOTIFY use case.
The bug was introduced in revision 10128 as an attempt to fix another, less common, bug that prevented onNewSubscription from being called when failures happened. More details can be obtained here:
http://list.resiprocate.org/archive/resiprocate-devel/thrd83.html#08362
The code changed in revision 10128 has been reverted on the mainline until a proper fix for the latter bug can be identified.