Avaya Partner 18 Connection Manual page 307

Appendix C: Running AT&TBuzz in Export via
Paste Link DDE Mode
where:
handle is an integer that refers to the handle of the telephone call.
caller id is the telephone number of the calling party.
line label is the label of the line that the call came in on.
call origin info is the complete call origin string. For PARTNER systems,
the call origin info is identical to the caller id.
A macro should be written in the other application to parse the string when it is
received. It may want to look up the caller id in its data base and display that
record. The macro governs what is done in that other application when new
Caller ID information is received.
The other application may also want to send information back to AT&TBuzz to
be displayed in the Call Label field of the call record list box. The application
will have to:
1. Initiate a DDE conversation with AT&TBuzz using the "Call_Label" topic.
2. Use the DDE Poke command to send the strings.
3. Terminate the conversation.
The string must be in the CF_TEXT clipboard format and look like this:
"<handle>", "<string of info.>"
where
handle is an integer that refers to the handle of the telephone call. This
number was passed to the application with the Caller ID and should be
passed back to AT&TBuzz so it knows to which call the string belongs.
string of info. can be anything the application would like AT&TBuzz to
display (for example, the name of the caller). The string can be up to
122 characters in length. If the string contains any quotation marks, they
should be doubled (for example, "James ""Jimmy"" Smith").
The Readme file has examples of macros in some common applications.
C-2