Juha Heinanen writes:
> how can i find out, where the exception is raised? it appears to be
> occur somewhere after sems is done with the CCCtl::start calls.
by placing INFO calls at various places, i got closer to where the
unexpected exception occurs. in SBCCallLeg.cpp:
INFO("Evaluating sst_config\n");
call_profile.eval_sst_config(ctx,req,call_profile.sst_a_cfg);
INFO("Done with evaluating sst_config\n");
the latter is never executed:
Feb 10 06:07:53 sip sems[6093]: [#b5142b70] [onInvite, SBCCallLeg.cpp:666]
INFO: Evaluating sst_config
Feb 10 06:07:53 sip sems[6093]: [#b5142b70] [processEventsCatchExceptions,
AmSession.cpp:362] ERROR: 500 unexpected exception.
-- juha
_______________________________________________
Semsdev mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/semsdev
