Hi All,
I am trying to use the DSM example mentioned in b2b_connect_audio and I have
the following problem:
I am not able to post events from leg-b to leg-a. I see this in the debug:
[#7f1f8d3af700/21736] [runactions, DSMStateEngine.cpp:236] DEBUG: executing
'set($b_status=FAILED)'
[#7f1f8d3af700/21736] [execute, DSMCoreModule.cpp:546] DEBUG: set
$b_status='FAILED'
[#7f1f8d3af700/21736] [runactions, DSMStateEngine.cpp:236] DEBUG: executing
'set($code=#code)'
[#7f1f8d3af700/21736] [execute, DSMCoreModule.cpp:546] DEBUG: set
$code='407'
[#7f1f8d3af700/21736] [runactions, DSMStateEngine.cpp:236] DEBUG: executing
'set($reason=#reason)'
[#7f1f8d3af700/21736] [execute, DSMCoreModule.cpp:546] DEBUG: set
$reason='Proxy Authentication Required'
[#7f1f8d3af700/21736] [runactions, DSMStateEngine.cpp:236] DEBUG: executing
'postEvent($b_leg_var.a_ltag, b_status;code;reason)'
[#7f1f8d3af700/21736] [execute, DSMCoreModule.cpp:253] DEBUG: adding
postEvent param b_status=FAILED
[#7f1f8d3af700/21736] [execute, DSMCoreModule.cpp:253] DEBUG: adding
postEvent param code=407
[#7f1f8d3af700/21736] [execute, DSMCoreModule.cpp:253] DEBUG: adding
postEvent param reason=Proxy Authentication Required
[#7f1f8d3af700/21736] [execute, DSMCoreModule.cpp:260] DEBUG: posting event
to session ''
[#7f1f8d3af700/21736] [runactions, DSMStateEngine.cpp:236] DEBUG: executing
'log(2,$b_leg_var.a_ltag)'
[#7f1f8d3af700/21736] [execute, DSMCoreModule.cpp:443] INFO: FSM:
$b_leg_var.a_ltag ''
The line "posting event to session" is blank. The code written is on the
callee script:
transition "failed callee leg" START - failed / {
set($b_status=FAILED);
-- copy code and reason to other leg so it can be used as reply code
set($code=#code);
set($reason=#reason);
postEvent($b_leg_var.a_ltag, b_status;code;reason);
log(2, $b_leg_var.a_ltag);
stop(false);
} -> END;
How do I get the variable in the first application to be visible in the
second application that is called??
Any ideas will be appreciated.
Thanks,
--- Jayesh
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems
