Avaya Interaction Center, Programmer'S Manual, Page: 41 / 138

Request IDs
Issue 2.1 August 2003 41
If an exception is returned, all of the other returned information may be invalid, including
the return code.
Return code
As shown in the response syntax, a return code may be added to the end of the response.
If it is present, this value may give you additional information, but it is not an error indicator.
The type and meaning of this value depends on the server and particular method invoked.
If an exception is returned, this value is not valid.
VTel will internally process most return code issues. Others will be passed through by VTel.
Request IDs
Anything enclosed in square brackets after the request is echoed in the response. This is
optional and can be used by the sender to identify the request by generating a unique ID
number for each.
[VTel.VDUGetOneValue("2df5d9e6003b00007800002a1f430002","ani",)][44]
[VTel.VDUGetOneValue.response(,"2df5d9e6003b00007800002a1f430002","ani",
"5084863244")][44]
This enables the application to match the requests with the corresponding responses. It is
the responsibility of the user application to generate a unique ID number. Sequential
request counters are recommended.
Note:
Note:
No response sequence is guaranteed or implied by this ID number.
Requests of the same or different types may be processed and replied to in
an arbitrary order.
Event messages
Event messages sent from VTel to user applications use a slightly different syntax than
request messages:
[eventid({eventtype,eventname,seqCouple})]