We are using TSAPI interface to communicate with an Avaya switch. We used to connect to host: AVAYA#AESLINK#CSTA#ABCAESSRVR

But an engineer pulled out the power in AES Server and then we found after restarting we couldn't connect. The reason, we found was that the host name to use had to be changed to:

AVAYA#ABCAESLINK#CSTA#ABCAESSRVR

The only reason this became apparent was because the tsapi test tool worked and that used this host.

The part of the string which changed was the switch connection name. The Avaya docs say:

You determine the switch connection name when you administer a Switch Connection in the AE Services Management Console, and the TSAPI service, in turn, gets the information from the
database.

How can this name be changed? We are not aware, but I suppose it is possible that someone might have changed this (although unlikely). Could be changed through an upgrade? Some other reason?

No idea Raghu.

Perhaps try CstaMonitorDevice on each extension (as described by John below) that the agent is logging into.

Angus

Just a guess, do you use MonitorDevice on an ACD Split for agent events (eg agent login/logoff) and MonitorCallsViaDevice for call events (eg delivered, diverted, etc)?

Hello

My question is:
To see call events (eg delivered, diverted) and also agent logon/logoff events on an ACD split, should I be using cstaMonitorDevice or cstaMonitorCallsViaDevice.

The notes in sdk doc says:
1. The Monitor Calls Via Device Service is the call-type Monitor Start Service on a static device identifier in
ECMA-179.
2. The Monitor Device Service is the device-type Monitor Start Service on a static device identifier in ECMA-179.

But I have a dialable number so does that mean I should be using MonitorDevice?

Is cstaMonitorCallsViaDevice just for VDNs/collected digits?

Angus

I believe that VMPro has a programmable interface so that is probably going to be the easiest option.

Abduls option is the most difficult but of course an option.

TAPI option would require you to purchase the devlink tapi licence so you can use in 3rd party mode for each customer where you install. not sure of cost - but not prohibitive if I remember rightly. Have a look at the IP Office CTI Link documentation it is explained in there. You need to install wave drivers and you also need a Wave licence.

Angus

Thanks for the info.

I want to create a simple IVR application that asks some simple question and caller presses 1,2,3,4,5 in response. To support up to 4 simulataneous callers to this 'IVR node' what licence(s) would be required?

Or are you saying that there is no cost for the DMCC xml documentation? Great if that is the case. Can I just download the specs? Please let me know.

I have access to the hardware I require I just need to purchase the DMCC SDK. How do I purchase that? The xml version?

I am investigating developing an IVR type application in DMCC. First question is how do I buy it and how much?

Second question, my application will be written in C++. so will the xml DMCC be the appropriate interface to use?

Hi

Version of simulator is 1.2. Versions of Comm Mgr at sites with real switches will be usually 4.x.

Sorry yes ATTV4_SENDDTMF_TONE. No, if I send a attSendDTMFTone in the exerciser then the confirmation is ATT_SENDDTMF_TONE. If I send via my application which is using v3.1 SDK then I see the Escape Svc, Event Type: ATTV4_SENDDTMF_TONE etc etc Error: VALUE_OUT_OF_RANGE.

PDV4?

Angus

Thanks John, that is what I suspected. We are now receiving logon/off events ok.

Hi

If I want to monitor an ACD Split do I have to monitor a dialable number? My customer has given me a skill number? It is two digits? Would I monitor this skill id? Please advise.

Angus

Hi

Here is my code to send a dtmf tone.
ATTPrivateData_t privateData = {0};
privateData.length = ATT_MAX_PRIVATE_DATA;
const char* tones = "1234";
RetCode_t rc1 = attSendDTMFTone(&privateData, &conn, 0, tones, 0, 0);
RetCode_t rc=cstaEscapeService(m_acsHandle, 0, (PrivateData_t*)&privateData);

attSendDTMFTone returns 0 - ie ACSPOSITIVE_ACK and cstaEscapeService returns an invokeid (positive).

But then in conformation I see CSTA_UNIVERSAL_FAILURE_CONF, invokeid: 10, error: VALUE_OUT_OF_RANGE

This is using a fairly old simulator. Could it be that the simulator is at fault? I have an established call and connectionid specified is correct.

In the simulator I see SERVICE: Escape Svc, Event Type: ATTV$_SENDDTMF_TONE etc etc Error: VALUE_OUT_OF_RANGE.

If I use the attSendDTMF menu item in the simulator then I see same SERVICE message but Event Type: is ATT_SENDDTMF_TONE and no error.

Any help would be much appreciated.

Angus

Hi

Here is event info from the simulator/exerciser.


I usually see the destination dn in "Transferred Device:" - but not in the case of this site.

Angus


12:05:48   0   EVENT:   Transferred:   Primary Old Call: [ Call ID: 567 Static Device ID: 1800 ]
            Secondary Old Call: [ Call ID: 568 Static Device ID: 1800 ]
            Transferring Device: [ Status: ID Provided Type: Explicit Private Local Number
               Device ID: 1800 ]
            Transferred Device: [ Status: ID Not Known ]
            Transferred Connections:   Number of Connections: 2
               Party: [ Call ID: 568 Static Device ID: 1801 ]
               Static Device: [ Status: ID Provided Type: Explicit Private Local Number
               Device ID: 1801 ]
               Party: [ Call ID: 568 Dynamic Device ID: T568#2 ]
               Static Device: [ Status: ID Provided Type: Explicit Public Unknown
               Device ID: T568#2 ]
            Local Conn Info: Null   Cause: TRANSFER
            ==========>>>>>>Cross Ref ID: 1 <<<<<<<==========
         Private Data:   Vendor: ECS
         Event Type :   ATT_TRANSFERRED
            Service: Transferred
            Orig Call Info Reason: Transferred
            OCI Calling Device: [ Status: ID Provided Type: Explicit Private Local Number
               Device ID: 1801 ]
            OCI Called Device: [ Status: ID Provided Type: Explicit Private Local Number
               Device ID: 1800 ]
            OCI TrunkGroup: (null)   OCI Trunk Member: (null)
            OCI Look Ahead Interflow Type: No Interflow
            OCI LAI Priority: Not In Queue
            OCI LAI Hours: 0, Minutes: 0, Seconds: 0
            OCI LAI Source VDN: (null)
            OCI LAI Unicode Source VDN:
            OCI User Entered Code Type: None
            OCI UEC Indicator: Collect   OCI UEC Data: (null)
            OCI UEC Collect VDN: (null)
            OCI UUI Type: None
            OCI Universal Call ID : 00000000000000000000
            OCI Call Originator Type: NO INFO
            OCI Flexible Billing :    NO
            Distributing Device: [ Status: ID Not Known ]
            Transferred Trunk List:   Number of Trunk Connections: 1
               Trunk Info: [ Call ID: 568 Dynamic Device ID: T568#2 ]
               Trunk Group: 10
               Trunk Member: 18

Hello

For some reason, we are not currently getting the transfer destination on a monitored device using the TSAPI interface. We do see the caller ok even on an external call for eg a delivered event. so this is confusing. Can anyone suggest any parameters in CM to look at or indeed any suggestions?

Angus