Jim,
Not sure what your asking here but if the call is stuck on a DN that your softphone is taking control of then of course you can program it to release it. Your underlying problem is why is a call “stuck on the DN”.. More info required i.e are you registering an Extension etc..
there is a bug with either our softphone or Genesys T-Server.
After a failover in HA T-Server, some way, out active X or T-Server deletes the active calls from its memory despite the actual call still being handled by it. So, pressing release button, generates an EventError (invalid ConnID).
If I restart softphone and query DN (RequestRegister), T-Server returns the conn-id for the call that it thinks the current agent is still handling. What I need is to release that call from T-Server memory before I can get my client to login again.
The underlying causes are being addressed, but it will take some time so I need to come up with a clever code to retrieve Conn-ID on the dn and release it.
I tried using Genesys ActiveX library, but there is nothing there to specify ConnID. Can this be done using Genesys Active X or do we need to use (oh god, I hope not - tlib)? All I want to do is issue a RequestReleaseCall(ThisConnID:xxxxxx, ThisDN:yyyyy) to clean it up.