rdc Posted July 4, 2007 Share Posted July 4, 2007 We replaced a voice modem that worked fine and was able to receive caller id fine here in the US with a TELCTAUSB4 that we bought from you. It won't give the caller id. We are using the same line that we know gives caller id. We have changed the "others" to all 1s for FSK but we can not get caller id. IVM version 4.02 Please tell us what to do before we send it back. Link to comment Share on other sites More sharing options...
pythonpoole Posted July 5, 2007 Share Posted July 5, 2007 I don't own a TELCTAUSB4 device, but is it possible that the the device's settings/configuration need to be changed for the region of the world in which you live? There is no universal Caller ID system. Caller ID works differently in different regions of the world (example Britain, USA and Russia all use distinctly different methods of sending the caller's number to the receiving party). Perhaps the regional settings on the device have to be tweaked to enable the Caller ID function in your area. Link to comment Share on other sites More sharing options...
rdc Posted July 5, 2007 Author Share Posted July 5, 2007 I don't own a TELCTAUSB4 device, but is it possible that the the device's settings/configuration need to be changed for the region of the world in which you live? There is no universal Caller ID system. Caller ID works differently in different regions of the world (example Britain, USA and Russia all use distinctly different methods of sending the caller's number to the receiving party). Perhaps the regional settings on the device have to be tweaked to enable the Caller ID function in your area. WE have changed it fro DTMF to FSK but it still doesn't work. Caller id worked fine with our old modem IF no one can help us soon we will just have to send it back. Email not returned so far from Synway or support at NCH Link to comment Share on other sites More sharing options...
Guest nchto Posted July 6, 2007 Share Posted July 6, 2007 Are you able to receive calls correctly? Is IVM able to detect the key presses? It is likely a configuration or driver issue, and your best bet (unless someone else is able to come up with a solution) is to wait and see what support have to say about this matter. Link to comment Share on other sites More sharing options...
kidtroopa Posted October 5, 2007 Share Posted October 5, 2007 Was there ever a fix for this? I have the latest drivers installed from synway for the shcti 4port USB voicebox...and am still unable to receive CallerID info with both DTMF and FSK settings. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now