We have a NMS AG4000 Dual T1 on NA2003-1. We have Teleflow running on 2 connections - ISDN and CAS Wink0 protocol. <br>When we received a call on the CAS connection, no CallerID was displayed. We receive the Called ID OK. <br>Everything work well on the ISDN connection, receiving both ANI and DNI. <br>Please advice.

Caller ID support under CAS is a little different. First of all, both the Called ID and Caller ID are sent as a single, long string of digits. These should ALL be received in the Called ID in your TeleFlow application. (Basically, the DNIS string is extended to include the ANI string) <br> <br>Typically, you will be provided with a string something like this: <br>*CalledID*CallerID* <br>You then need to write a parser in your TeleFlow application to break the called id and caller id into separate TeleFlow variables, to do with them what you wish in the application. <br> <br>This assumes that your Telco sends this. They will sometimes state that they do not support CallerID under CAS/RBS. If this is the case, you would have to switch to using only ISDN.

Our telco sends out a 3 digit DNI or CALLEDID number and Teleflow captures that perfectly (3 digits exactly). What is missing seems to be the CALLERID which shows up blank. <br> <br>Our telco does send our CallerID and said that they expects Teleflow to reply with KP or something before they send the CallerID. How do I get Teleflow to send out a CallerID request signal?

Anyone has any suggestion on how to solve the problem?

The only suggestion we have would be to switch to using wnk1 support instead, and have the DNIS and ANI provided in the way I previously suggested. (you would need to set your protocol to wnk1, and have the Telco make the appropriate changes as well...)