Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Avaya API

Status
Not open for further replies.

Icool

Programmer
Joined
Jan 22, 2025
Messages
2
Hello everyone.

I am using Avaya API (Avaya IP Office CTI Web Services) and I have encountered several problems. Some API functions return an error even though I do everything according to the documentation.

POST https://<server IP>:<server port>/inyama/service/callcontrol/holdCall
when calling this function I get INVALID_INPUT_XML_DATA in response (please believe me I have checked several times what I am sending in the request)

POST https://<server IP>:<server port>/inyama/service/callcontrol/clearCall
when calling this function I get INVALID_INPUT_XML_DATA in response (please believe me I have checked several times what I am sending in the request)

POST https://<server IP>:<server port>/inyama/service/session/heartbeat
when calling this function I get
Invalid page request!

https://<server IP>:<server port>/inyama/service/presence ?jids=
username1@xmpp-domain-name1, username1@xmpp-domain-name2,
username2@xmpp-domain-name1
when calling this function I get in response
chat session not found for the appl session

For all functions I use Application User account.
All other functions work correctly and without errors.
It seems to me that I am making some very small mistake, I would be very grateful for any help.
 
Maybe you could post the sent XML so that we can check if we see issues in it. Even though I mostly just worked with the monitoring API.
 
Yes, of course.

POST https://<server IP>:<server port>/inyama/service/callcontrol/holdCall
Sended message
<?xml version= \'1.0\' encoding= \'utf-16\'?>\n
<ns2:HoldCall xmlns:ns14="http://recording.common.avaya.com/"
xmlns:ns9="http://ccragent.common.avaya.com/" xmlns:ns5="http://com.avaya.inkaba.dal"
xmlns:ns12="http://voicemail.common.avaya.com/" xmlns:ns6="http://com.avaya.inkaba.wstransfer"
xmlns:ns13="http://calllog.common.avaya.com/" xmlns:ns7="http://com.avaya.common.csta.extended"
xmlns:ns10="http://conferencing.common.avaya.com/"
xmlns:ns8="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:ns11="http://conferencing.avaya.com/"
xmlns:ns2="http://www.ecmainternational.org/standards/ecma-323/csta/ed4"
xmlns:ns4="http://schemas.xmlsoap.org/ws/2004/08/addressing"
xmlns:ns3="http://schemas.xmlsoap.org/ws/2004/09/transfer">
<ns2:callToBeHeld>
<ns2:callID>a5bba1cb-b174-441d-8914-125469439de5</ns2:callID>
</ns2:callToBeHeld>
</ns2:HoldCall>


POST https://<server IP>:<server port>/inyama/service/callcontrol/clearCall
Sended message
<?xml version= \'1.0\' encoding= \'utf-16\'?>\n
<ns2:ClearConnection xmlns:ns14="http://recording.common.avaya.com/"
xmlns:ns9="http://ccragent.common.avaya.com/" xmlns:ns5="http://com.avaya.inkaba.dal"
xmlns:ns12="http://voicemail.common.avaya.com/" xmlns:ns6="http://com.avaya.inkaba.wstransfer"
xmlns:ns13="http://calllog.common.avaya.com/" xmlns:ns7="http://com.avaya.common.csta.extended"
xmlns:ns10="http://conferencing.common.avaya.com/"
xmlns:ns8="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:ns11="http://conferencing.avaya.com/"
xmlns:ns2="http://www.ecmainternational.org/standards/ecma-323/csta/ed4"
xmlns:ns4="http://schemas.xmlsoap.org/ws/2004/08/addressing"
xmlns:ns3="http://schemas.xmlsoap.org/ws/2004/09/transfer">
<ns2:connectionToBeCleared>
<ns2:callID>a5bba1cb-b174-441d-8914-125469439de5</ns2:callID>
</ns2:connectionToBeCleared>
</ns2:ClearConnection>
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top