When applications perform NCC API call control with the EUC protocol, they can process digits in the following ways:
Method used to process digits |
Description |
Inbound calls: Receiving digits all at once |
With EUC TCPs, after NCCEVN_INCOMING_CALL is received, the calledaddr field in the NCC_CALL_STATUS structure contains all received digits. The callingaddr, usercategory and tollcategory fields are NULL. The parameter NCC.X.ADI_EUC.digitnumber determines the number of digits the TCP should expect from the calling party. Default is 7. |
Inbound calls: Receiving digits one at a time |
Make sure the NCC.START.OVERLAPPED.RECEIVING parameter is set. The TCP does not recognize ANI or category digits. Digits are presented in the order in which they arrive. The NCC.X.ADI_EUC.digitnumber parameter determines how many digits to expect. In the case of the P8 Swedish protocol with ANI and redirecting terminal information, the digit string can be received as follows: # firstfield # [secondfield] # d1 ... dn where firstfield and secondfield are contingent to the reception of the corresponding code. The code itself is not presented to the application. |
Outbound calls: Formatting the digit string |
EUC TCPs expect the digit string to be formatted as follows: d1 ... dn ANI and category indicators are not used in EUC TCPs. |