i am using master also

:)

i was strugling with missing module because closePlaylist, but after
changing to flushPlaylist every ERROR gone

just compare
DSMCall.cpp
DSMCoreModule.cpp
SystemDSM.cpp

root@voip-db1:/usr/local/src# diff -y sems/apps/dsm/SystemDSM.cpp
sems-1.4.3/apps/dsm/SystemDSM.cpp | grep close
NOT_IMPLEMENTED(flushPlaylist());                             |
NOT_IMPLEMENTED(closePlaylist(bool notify));

root@voip-db1:/usr/local/src# diff -y sems/apps/dsm/DSMCall.cpp
sems-1.4.3/apps/dsm/DSMCall.cpp | grep close
void DSMCall::flushPlaylist() {                               | void
DSMCall::closePlaylist(bool notify) {
  DBG("flush playlist\n");                                    |
DBG("close playlist\n");
  playlist.flush();                                           |
playlist.close(notify);
    rec_file->close();
...


regards
ivan


On Thu, Jun 6, 2013 at 8:20 PM, Ivan Milivojevic <[email protected]> wrote:

> hi juha
>
> i still have the ERROR in log but sems doesnt stop...
>
> Jun  6 20:15:21 voip-db1 sems[9452]: [#7fef58e16740] [SCSetAction,
> DSMCoreModule.cpp:604] ERROR:  expected two parameters separated with '='
> in expression '$pin=""' for P11SCSetAction
> Jun  6 20:15:21 voip-db1 sems[9452]: [#7fef58e16740] [SCSetAction,
> DSMCoreModule.cpp:604] ERROR:  expected two parameters separated with '='
> in expression '$pin=""' for P11SCSetAction
> Jun  6 20:15:21 voip-db1 sems[9452]: [#7fef58e16740] [loadFile,
> DSMStateDiagramCollection.cpp:113] WARNING:  consistency check failed on
> 'confpin' from file '/usr/local/etc/sems/dsm/confpin.dsm':
> Jun  6 20:15:21 voip-db1 sems[9452]: [#7fef58e16740] [loadFile,
> DSMStateDiagramCollection.cpp:116] WARNING:
>  ------------------------------------------#012confpin: State 'END': hangup
> is not handled#012confpin: State 'BYE': hangup is not handled#012confpin:
> State 'FIN': hangup is not
> handled#012#012------------------------------------------
> Jun  6 20:15:21 voip-db1 sems[9452]: [#7fef58e16740] [registerApps,
> DSM.cpp:390] INFO:  DSM state machine registered: confpin.
> Jun  6 20:15:21 voip-db1 sems[9452]: [#7fef58e16740] [main, sems.cpp:539]
> INFO:  Starting application timer scheduler
> Jun  6 20:15:21 voip-db1 sems[9452]: [#7fef58e16740] [main, sems.cpp:542]
> INFO:  Starting session container
> Jun  6 20:15:21 voip-db1 sems[9452]: [#7fef58e16740] [main, sems.cpp:550]
> INFO:  Starting media processor
> Jun  6 20:15:21 voip-db1 sems[9452]: [#7fef58e16740] [main, sems.cpp:553]
> INFO:  Starting RTP receiver
> Jun  6 20:15:21 voip-db1 sems[9452]: [#7fef58e16740] [main, sems.cpp:556]
> INFO:  Starting SIP stack (control interface)
> Jun  6 20:15:21 voip-db1 sems[9452]: [#7fef553ad700] [run,
> udp_trsp.cpp:295] INFO:  Started SIP server UDP transport on xxxx:5070
> Jun  6 20:15:21 voip-db1 sems[9452]: [#7fef563bd700] [run,
> AmSessionContainer.cpp:120] INFO:  monitoring module not loaded, monitoring
> disabled
>
> 1.4.3               => 1.5.0
> closePlaylist  => flushPlaylist
>
> regards
> ivan
>
>
> On Thu, Jun 6, 2013 at 8:03 PM, Juha Heinanen <[email protected]> wrote:
>
>> Ivan Milivojevic writes:
>>
>> > I got the same error but mine dsm scipt is working without errors..i am
>> > using the same code for addkey..maybe something else is wrong
>>
>> ivan,
>>
>> in your case, actions that contain set($pin=""); are enclosed with {}s:
>>
>> > transition "start_pin_entry" START - invite / {
>> >          log(2,>> start_pin_entry);
>> >          set($tryAgain=0);
>> >          set($pin="");
>> ...
>>
>> in test.dsm that is not the case:
>>
>> transition "start pin entry" sess_started - / set($pin = "") -> ADDKEY;
>>
>> i tried and enclosed the action with {}s:
>>
>> transition "start pin entry" sess_started - / {set($pin = ""); } ->
>> ADDKEY;
>>
>> after that, the error was gone.
>>
>> my conclusion is that the bug in test.dsm is the missing {}s, not the set
>> itself.
>>
>> -- juha
>>
>> ps. have you figured out what closePlaylist() should be replaced with?
>>
>> -- juha
>>
>
>
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems

Reply via email to