I would like to use capabilities of CallDirectionNotification for the application initiated calls.
Example scenario is:
1. Application starts "BUSY" DirectionNotification for B party
2. ThirdPartyCall makes call between A and B parties (SCID is present in SOAP header)
3. Application receives notification about B party busy and redirects call to C party.
My problem is that CallDirectionNotification works fine only for network initiated calls.
When A to B call is application initiated then notifications are not triggered.
Is there something that needs to be configured on gatekeeper to enable interaction between ThirdPartyCall and CallDirectionNotification?
I'm using WLNG 4.0.