Message |
[+]
Engagement Designer
» Track Email Conversation, 14/03/2024 13:46:10
» Go to message
|
|
DevConnect does not provide API Assistance for Oceana. That support comes directly from the product team to Oceana customers. I do not have detailed instructions on the mechanism to request support for Oceana APIs, but would imagine Customers are expected to open onecare tickets with the nature of their API support questions.
|
|
[+]
Avaya Client SDK - General
» Communication Services API (JavaScript) - getLocalNumber?, 04/03/2024 08:41:34
» Go to message
|
|
There are so many ways to manipulate called number, in so many places - the answer is no. In a few rare cases you can get one of the vector directory numbers (there can be a sequence of VDNs used - you only get one of the numbers) in lieu of some other version of the extension that is ringing - that occurs in the context of contact center calls and it is my impression that is not what you are working on.
|
|
[+]
Avaya Orchestration Designer
» AOD 8.1.2 patch to fix the copy/cut & paste bug , 27/02/2024 15:06:19
» Go to message
|
|
correct, there is no product generally available (public) release that contains the fix to the issue.
|
|
[+]
Avaya Orchestration Designer
» AOD 8.1.2 patch to fix the copy/cut & paste bug , 27/02/2024 14:54:52
» Go to message
|
|
The current Experience Portal release remains at 8.1.2
You can check to see if there are newer releases by using
www.avaya.com/support
selecting Software Downloads
Entering Experience Portal
Selecting a release of 8.1.x
clicking the search magnifying glass
looking at the listed releases.
And yes if you need the patch, please open a DevConnect Support Ticket.
|
|
[+]
Avaya Client SDK - General
» Communication Services API (JavaScript) - Abbreviations in the SDK, 26/02/2024 12:52:24
» Go to message
|
|
The acronym AMM stands for Avaya Multimedia Messaging.
The acronym ACS stands for Avaya Communication Server Configuration.
The acronym UCCP stands for Unified Communications and Collaboration Platform.
The acronym WCS stands for Web Collaboration Service.
|
|
[+]
Avaya Client SDK - General
» Communication Services API (JavaScript) - Abbreviations in the SDK, 26/02/2024 08:47:51
» Go to message
|
|
Context often helps in this situation as many acroynms have multiple expansions.
AMM might be Avaya Meetings Manager
ACS might be Avaya Client Servcices
|
|
[+]
Avaya Client SDK - General
» Is there a SetAgents method in Communication Control Toolkit (CCT) SOAP API?, 21/02/2024 12:33:44
» Go to message
|
|
|
|
[+]
JTAPI
» Inquiry on CTI Information for Calls Transferred from CUCM to Avaya, 21/02/2024 07:06:12
» Go to message
|
|
First to enable TSAPI tracing see this FAQ https://www.devconnectprogram.com/site/global/products_resources/avaya_aura_application_enablement_services/support/faq/tsapi/index.gsp?tab=general&accordion=faq-5-collapse
JTAPI utilizes TSAPI within AE Services, so that will show you what is occurring.
I am unable to read the chinese characters in the diagram and do not have access to someone who can. It reads like someone on the right places a call into sales office 1 which is sent to CUCM and delivered to a 'CC (agent?). 'That agent appears to transfer the call back to the Avaya sales office where it is delivered to a 'sales office 1(agent?).' To understand what information CUCM sends to Avaya you would want to create monitors on 'sales office 1 agent,'and perhaps on a Vector Directory Number that is used to handle the call before distributing it to sales office 1 agents. (two separate monitors - use 'monitor calls via device' for the VDN monitor).
As to the content of the CTI messaging, that is hard to say. We do not have exposure to how Cisco and Genesys manage call information. It would be best to simply create a test bed and enable the tracing and run whatever call scenarios you need and observe what data Cisco is sending to Avaya. Given with CTI there are a number of ways to do a transfer, and a number of configuration possibilites with respect to handling other out of band meta data the possibilities with the information that is provided are pretty open ended (there are a lot of them). The original calling party information may or may not be available, or it could be substituted by the CUCM CC agent information. There may be UCID information from when the call was handled by the Avaya system before it was sent to CUCM - there may not. CUCM may have attached UUI information - it may not have - Things could be configured so that in the first call let Avaya added UUI, Cisco may pass that back to Avaya as the call is transfered, or it could replace it. Digit manipulation may have changed calling or called party numbers from what the originating system sent. etcetera. I really can not guess my way to a useful answer here so much depends on system configuration, and intent, and need. At a minimum I would expect calling and called numbers. However calling may be the original number (unlikely) or it could be CUCM CC Agent's number. UCID could be from the first call leg in Avaya, or it could be a new UCID and teh two values only associatable based on information provided by the CUCM CTI event stream.
|
|
[+]
Avaya Client SDK - General
» Communication Services API (JavaScript) - WCSCollabProvider, 16/02/2024 11:34:04
» Go to message
|
|
please provide some details on your environment, who supplied it, who configured it? I am looking for company, not individual there. There are a lot of possibities for the environment you are utilizing. In general a business partner or Avaya Professional Services would have deployed and have responsibilities related to initial configuration of the environment, and you would be under a maintenance contract with someone for different levels of 'day 2' support. It could be their responsibility assuming you are using a production environment, or it might be yours - especially if you are in some form of lab environment your company put together and your team did the configuration for the environment. I suggest finding out who did the initial configuration of meetings server and asking them if there is a support contract in place.
|
|
[+]
Avaya Client SDK - General
» Conferences vs Meetings, 14/02/2024 11:41:20
» Go to message
|
|
Commonly a meeting is scheduled (i.e. a meet me arangement) where people dial into a meeting bridge.
Conference is more ad-hoc where A and B are talking and one of them adds in C through some sequence of actions (hold, call, join/answer or answer/join)
Both result in a multi party conversation being possible.
Meetings tend to have some management interface allowing operations like lecture mode, muting parties that conferences do not have available equivilents.
Meeting managment UIs tend to have some mechansim to dial out to a participant(s) to add them to the meeting, but that is typically done very differently than you would see in an ad-hoc conference situation. i.e they are called and when they answer they are joined into the meeting automatically - although there is screening capabilities in some meeting systems allowing the moderator to avoid adding answering machines and the like into conferences.
However, as you travel the world and work with non-English language native speakers, the terminology becomes used however the writer/speaker is familiar with the words themselves resulting in confusion.
|
|
[+]
Avaya Client SDK - General
» Meeting Management Service API Reference (JavaScript) - missing documentation, 13/02/2024 07:23:52
» Go to message
|
|
We are hunting for the current content owners.
|
|
[+]
Avaya Client SDK - General
» Communication Services API (JavaScript) - ConferenceType, 08/02/2024 09:00:12
» Go to message
|
|
From the perspective of the Client SDK, yes.
Unfortunately, there are only so many words in the English language that can be used to communicate concepts with. And I agree it would be best if the documentation for a SDK sticks to one term for a concept throughout the documentation package, but often when multiple people create and maintain the content that is not adhered to consistently. Communication Manager can be configured to support meet-me voice conferences; however the Client SDK does not integrate with the meet-me capability available with Communication Manager.
|
|
[+]
Avaya Client SDK - General
» Communication Services API (JavaScript) - ConferenceType, 08/02/2024 08:16:40
» Go to message
|
|
CM is the standard accroynm for Avaya Aura Communication Manager.
Scopia is an outdated name for the Radvision product Avaya acquired that hosts multi party video conferencing.
As to how they are used, I infer they relate to what product is hosting the conference, however you will have to await someone who has more product expertise for a definitive answer.
|
|
[+]
Avaya Client SDK - General
» Communication Services API (JavaScript) - Distinguish between voice mail and real person, 01/02/2024 10:25:55
» Go to message
|
|
there should be a difference you can note in the indication of what party answered the call to indicate the called party was not the extension that answered the call (triggered teh established event). The system does not know what is behind any extension (recorded voice, or human). There is a set of services called answering machine detection that is available to outbound dialers under an Advanced TSAPI license using the makePredictiveCall() services if the call was placed using Application Enablement Services CTI services, but I doubt that is your use case.
|
|
[+]
Client development for Avaya Vantage devices
» Avaya Vantage 3 BT Handset doesn't work with 3rd part App, 26/01/2024 07:21:07
» Go to message
|
|
Reach out to the developer of the third-party SIP app and inquire about compatibility with the K175 Vantage 3 model. They may need to update their app or provide specific instructions for the newer model.
|
|