July CCXML Implementation Report: 7_3: unhandled conference.unjoined

• From: Petr Kuba <kuba@optimsys.cz>
• Date: Wed, 28 Jul 2010 01:19:31 +0200
• To: www-voice <www-voice@w3.org>
• Message-ID: <4C4F6983.5000403@optimsys.cz>

Hello www-voice,

In 7_3, assert 412, the following code is used:



    		<transition event="connection.disconnected" 
state="ASSERTION_NMBR_425">
    			<conf:comment expr=" 'Current state : ' + current_state + ' , 
Event: ' + event$.name"/>
    			<dialogterminate dialogid="DialogID"/>
         </transition>

    		<transition event="conference.unjoined" state="ASSERTION_NMBR_425">
    			<conf:comment expr=" 'Current state : ' + current_state + ' , 
Event: ' + event$.name"/>
        </transition>


         <transition event="dialog.exit" state="ASSERTION_NMBR_425">
        		<conf:comment expr=" 'Current state : ' + current_state + ' , 
Event: ' + event$.name"/>
        		<send targettype="'ccxml'" target="session.id" 
name="name_prepare_new"/>
		</transition>



<dialogterminate> results in two events:

1) conference.unjoined
2) dialog.exit

The problem is that the order of these two events is not specified and 
if conference.unjoined is receiver after dialog.exit then it is 
processed by the consequent assertion. This results in unexpected event 
being reported.



Thanks,
Petr

-- 
   Petr Kuba, Project Manager
   OptimSys, s.r.o
   kuba@optimsys.cz
   Tel: +420 541 143 065
   Fax: +420 541 143 066
   http://www.optimsys.cz

Received on Tuesday, 27 July 2010 23:20:19 UTC