Buy or Renew
Buy or Renew
Cisco + Splunk: It’s a new day for your data. Learn more.
 
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
642
Views
0
Helpful
3
Replies

Finesse TRANSFER_SST can't receive all notifications

windleaf5188
Level 1
Level 1

‎09-17-2018 07:10 AM

Hello, I use Finesse Cisco Finesse 11.5 API. When I want to send a action "transfer_sst" by those params:

{ method: 'PUT',
url: 'http://finesse2.cc.tel.mcra.fr/finesse/api/Dialog/352345030',
headers:
{ 'Content-Type': 'application/xml',
Authorization: 'Basic NzEzMTAwMDo3MTMxMDAw' },
body: '<Dialog><requestedAction>TRANSFER_SST</requestedAction><toAddress>7106031</toAddress><targetMediaAddress>7131000</targetMediaAddress></Dialog>' }

 

I can send successfully to "7106031". But I get just one notification from finesse:

 

  1. {associatedDialogUri: "", fromAddress: "7140998", id: "2130706541", mediaProperties: {…}, mediaType: "Voice", …}
    1. associatedDialogUri: ""
    2. fromAddress: "7140998"
    3. id: "2130706541"
    4. mediaProperties:
      1. DNIS: "7106031"
      2. callType: "CONSULT"
      3. callvariables: {CallVariable: Array(10)}
      4. dialedNumber: "7106031"
      5. outboundClassification: ""
      6. __proto__: Object
    5. mediaType: "Voice"
    6. participants:
      1. 7140998:
        1. actions: Array(2)
          1. 0: "UPDATE_CALL_DATA"
          2. 1: "DROP"
          3. length: 2
          4. __proto__: Array(0)
        2. mediaAddress: "7140998"
        3. mediaAddressType: "AGENT_DEVICE"
        4. startTime: "2018-09-17T13:57:34.037Z"
        5. state: "INITIATING"
        6. stateCause: ""
        7. stateChangeTime: "2018-09-17T13:57:34.037Z"
        8. __proto__: Object
      2. Participant: {actions: Array(2), mediaAddress: "7140998", mediaAddressType: "AGENT_DEVICE", startTime: "2018-09-17T13:57:34.037Z", state: "INITIATING", …}
      3. __proto__: Object
    7. state: "INITIATING"
    8. toAddress: "7106031"
    9. uri: "/finesse/api/Dialog/2130706541"

 

I have to refresh my page to get the notification of "ready" status.

 

Some one can help me? Thanks very much !

 

Labels:
0 Helpful
3 Replies 3

dekwan
Cisco Employee
Cisco Employee

‎09-17-2018 12:00 PM

Hi,

 

The "Ready" status is a user notification vs a dialog notification. Is your application listening to that node as well? I would suggest calling these apis via postman and using a XMPP client such as pidgin or adium to view the notifications and see if it is an application issue or an issue with Finesse.

 

Thanx,

Denise

0 Helpful

windleaf5188
Level 1
Level 1
In response to dekwan

‎09-18-2018 06:10 AM

Thank you. When I try with postman and pidgin, I can have all notifications. And now I see where is my problem.

Another question, in the action transfer_sst, I can get 3 notifications from dialog node:

  1. {associatedDialogUri: "", fromAddress: "7133794", id: "2130706597", mediaProperties: {…}, mediaType: "Voice", …}
    1. associatedDialogUri: ""
    2. fromAddress: "7133794"
    3. id: "2130706597"
    4. mediaProperties: {DNIS: "7106031", callType: "CONSULT", dialedNumber: "7106031", outboundClassification: "", callvariables: {…}}
    5. mediaType: "Voice"
    6. participants:
      1. 7133794: {actions: Array(2), mediaAddress: "7133794", mediaAddressType: "AGENT_DEVICE", startTime: "2018-09-18T12:58:32.883Z", state: "INITIATING", …}
      2. Participant:
        1. actions: (2) ["UPDATE_CALL_DATA", "DROP"]
        2. mediaAddress: "7133794"
        3. mediaAddressType: "AGENT_DEVICE"
        4. startTime: "2018-09-18T12:58:32.883Z"
        5. state: "INITIATING"
        6. stateCause: ""
        7. stateChangeTime: "2018-09-18T12:58:32.883Z"
        8. __proto__: Object
      3. __proto__: Object
    7. state: "INITIATING"
    8. toAddress: "7106031"
    9. uri: "/finesse/api/Dialog/2130706597"

 

  1. {associatedDialogUri: "", fromAddress: "07133794", id: "352345518", mediaProperties: {…}, mediaType: "Voice", …}
    1. associatedDialogUri: ""
    2. fromAddress: "07133794"
    3. id: "352345518"
    4. mediaProperties: {DNIS: "7131000", callType: "TRANSFER", dialedNumber: "3244", outboundClassification: "", callvariables: {…}}
    5. mediaType: "Voice"
    6. participants:
      1. 7131000: {actions: undefined, mediaAddress: "7131000", mediaAddressType: "AGENT_DEVICE", startTime: "2018-09-18T12:58:26.500Z", state: "DROPPED", …}
      2. 07133794: {actions: Array(6), mediaAddress: "07133794", mediaAddressType: "", startTime: "2018-09-18T12:58:26.500Z", state: "ACTIVE", …}
      3. Participant: Array(2)
        1. 0: {actions: Array(6), mediaAddress: "07133794", mediaAddressType: "", startTime: "2018-09-18T12:58:26.500Z", state: "ACTIVE", …}
        2. 1: {actions: undefined, mediaAddress: "7131000", mediaAddressType: "AGENT_DEVICE", startTime: "2018-09-18T12:58:26.500Z", state: "DROPPED", …}
        3. length: 2
        4. __proto__: Array(0)
      4. __proto__: Object
    7. state: "ACTIVE"
    8. toAddress: "3244"
    9. uri: "/finesse/api/Dialog/352345518"

 

 

 

  1. {associatedDialogUri: "", fromAddress: "7133794", id: "2130706597", mediaProperties: {…}, mediaType: "Voice", …}
    1. associatedDialogUri: ""
    2. fromAddress: "7133794"
    3. id: "2130706597"
    4. mediaProperties: {DNIS: "7106031", callType: "TRANSFER", dialedNumber: "7106031", outboundClassification: "", callvariables: {…}}
    5. mediaType: "Voice"
    6. participants:
      1. 7133794: {actions: undefined, mediaAddress: "7133794", mediaAddressType: "AGENT_DEVICE", startTime: "2018-09-18T12:58:32.883Z", state: "DROPPED", …}
      2. Participant:
        1. actions: undefined
        2. mediaAddress: "7133794"
        3. mediaAddressType: "AGENT_DEVICE"
        4. startTime: "2018-09-18T12:58:32.883Z"
        5. state: "DROPPED"
        6. stateCause: "OTHER"
        7. stateChangeTime: "2018-09-18T12:58:32.883Z"
        8. __proto__: Object
      3. __proto__: Object
    7. state: "DROPPED"
    8. toAddress: "7106031"
    9. uri: "/finesse/api/Dialog/2130706597"

 

In theses actions, I can get the state from the notification finesse node: "messge.state" or "message.participants.Participant.state" or "message.participants.7131000.state". Sometimes, they are the same things, and sometimes they are differents.

 

So, I don't know which state I should use.

 

 

0 Helpful

dekwan
Cisco Employee
Cisco Employee
In response to windleaf5188

‎09-18-2018 08:53 AM

Hi,

Glad you were able to figure out your original problem.

For your question about states, there should only be two types. 1) message.state and 2) message.participants.<user extension>.state for every participant in the call.

For message.state, it is the state of the overall call. For message.participants.<user extension>.state, it is the state for that particular participant. For example, if you have a call between extension 1234 and extension 5678, then extension 1234 puts the call on hold, the states will look like this:
- message.state: ACTIVE
- message.participants.1234.state: HELD
- message.participants.5678.state: ACTIVE

The call itself is active because the call has been established between the two parties. 5678 is also ACTIVE because it is still on the call, but 1234 is in HELD because thats what that user did. Does that make sense?

Thanx,
Denise
0 Helpful
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Customers Also Viewed These Support Documents