Home Forums
|
How to execute the application's ECharts machine (0 viewing)
Favoured: 0
|
|
|
TOPIC: How to execute the application's ECharts machine
|
Vital (User)
Junior Boarder
Posts: 26
|
|
How to execute the application's ECharts machine 1 Year ago
|
|
|
Hi, There is a de_script_ion as below in section 8.1 of "ECharts for SIP Servlets User Mananual Version 2.5 Beta": "the execution of the application's ECharts machine". But how to execute the application's ECharts machine? Could you take the example of "timeBomb" as an example to explain? Thanks.
|
|
|
|
|
|
|
The administrator has disabled public write access. |
|
|
|
Re:How to execute the application's ECharts machin 1 Year ago
|
|
|
if you ran the test (mentioned in the paragraph prior to the one you quote) then you've executed the echarts machine
|
|
|
|
|
|
|
The administrator has disabled public write access. |
Vital (User)
Junior Boarder
Posts: 26
|
|
Re:How to execute the application's ECharts machin 1 Year ago
|
|
|
Thank you very much. But what is its outcome? How to check its outcome? and How to apply a machine into a SIP application? Thanks.
|
|
|
|
|
|
|
The administrator has disabled public write access. |
|
|
|
Re:How to execute the application's ECharts machin 1 Year ago
|
|
|
E4SS automatically dispatches incoming SIP messages to the application's ECharts machine to trigger transitions. See section 5.2 for details. Basically the SIP Servlet container invokes the EChartsSipServlet class, which in turn dispatches the message to the machine's BoxPort or SipPort.
So using timeBomb as an example, when an initial INVITE is received by the container and the container invokes the timeBomb app, TimeBombFSM will be triggered (in this case acts as a B2BUA and sends an INVITE out). When TimeBombFSM reaches TICKING state, the timer starts, and when timer runs out, the FSM transitions to END state and E4SS sends BYE on both sides.
You can see the outcome by observing the SIP messages coming in and going out. You can look at the SIP messages and state transitions in the application's log. (see 8.1)
|
|
|
|
|
|
|
The administrator has disabled public write access. |
|
|
|
|
|
|
|
|
The administrator has disabled public write access. |
|
|
|
|
|
Copyright © 2006-2009 echarts.org