Off the top of my head....

1. create a custom script in sage crm that stores the sid in localstorage

...in wwwroot/custom/js

2. create a html page that is hosted on the sage crm server and opened instead of the .../eware.dll

eg

....custompages/cti/opensesame.html?no=8877661612

3.in the opensesame.html parse out the querystring

no=8877661612

and then pick up the SID from localstorage and build the url

http://svr-sage/crm/eware.dll/Do?SID=171528635821040&Act=Search&Find=Phone&SearchText=8877661612

and then redirect to that url.or do

window.location =http://svr-sage/crm/eware.dll/Do?SID=171528635821040&Act=Search&Find=Phone&SearchText=8877661612

Having your telephony system open an intermediary page rather than hitting eware.dll directly means you have a layer in between where you can grab the SID, build the full URL, and redirect. It also gives you a nice place to handle any edge cases.

One thing to consider beyond the basic screen pop is what happens when the phone number matches more than one record, or no records at all. We have built something similar for 3CX and a number of other telephony platform integrations where the inbound call triggers a lookup and presents the user with matched persons or just companies before launching into CRM. It handles the multiple match scenario and gives the user a choice rather than just landing on the first result.

There is a short demo of it here if it is useful as a reference for how the flow can work end to end:

www.linkedin.com/.../urn:li:activity:7434631154953080832