As of Friday October 16th, access to restricted content on this site now requires you to log in with your Genesys account. If you don't have an account, you can request one at these locations: Request MyPartner Portal Account or Request My Support Account.
Jump to: navigation, search

CSTA StopEvent Message

CSTA StopEvent message is generated upon receiving the appropriate Treatment completed BroadWorks message as described in the following table:

BroadWorks Events and the Associated CSTA StopEvent Parameters

BroadWorks Events Parameters CSTA StopEvent Parameters

RoutePointBusyCompletedEvent

Message ID = 0 (zero)

completionReason

Cause

errorReason

N/A (presented as string in BroadWorks)

digits

Extension collectDigits

RoutePointMOHCompletedEvent

Message ID = 1

completionReason

Cause

errorReason

N/A (presented as string in BroadWorks)

digits

Extension collectDigits

RoutePointRingbackCompletedEvent

Message ID = 2

completionReason

Cause

errorReason

N/A (presented as string in BroadWorks)

digits

Extension collectDigits

RoutePointSilenceCompletedEvent

Message ID = 3

completionReason

Cause

errorReason

N/A (presented as string in BroadWorks)

digits

Extension collectDigits

RoutePointTreatmentCompletedEvent

Message ID = 4

completionReason

Cause

errorReason

N/A (presented as string in BroadWorks)

digits

Extension collectDigits

This page was last edited on May 28, 2013, at 20:48.

Feedback

Comment on this article:

blog comments powered by Disqus