just to summarize, this second connectCallee problem seems to be due to the fact that that def onOtherReply(self, code, reason) function of my ivr script does not get called in
[email protected] -> sems (connectCallee) -> [email protected] scenario, when sems receives replies from [email protected]. when this function does not get called, the script logic, of course, goes haywire. debug show that sems clearly receives such replies: May 21 08:46:07 sip sems[10789]: [#b57ffb70] [onB2BEvent, AmB2BSession.cpp:876] DEBUG: 100 reply received from other leg May 21 08:46:07 sip sems[10789]: [#b57ffb70] [onB2BEvent, AmB2BSession.cpp:147] DEBUG: B2BSipReply: 100 Trying (fwd=false) ... May 21 08:46:08 sip sems[10789]: [#b57ffb70] [onB2BEvent, AmB2BSession.cpp:876] DEBUG: 180 reply received from other leg May 21 08:46:08 sip sems[10789]: [#b57ffb70] [onB2BEvent,AmB2BSession.cpp:147] DEBUG: B2BSipReply: 180 Ringing (fwd=false) ... May 21 08:46:12 sip sems[10789]: [#b57ffb70] [onB2BEvent, AmB2BSession.cpp:876] DEBUG: 200 reply received from other leg May 21 08:46:12 sip sems[10789]: [#b57ffb70] [onB2BEvent, AmB2BSession.cpp:147] DEBUG: B2BSipReply: 200 OK (fwd=false) however, those do not cause onOtherReply called, because the debug statement in the beginning of onOtherReply function does not show up in debug log. as i mentioned, this ivr script used to work earlier, but i don't remember, in which version of sems. -- juha _______________________________________________ Sems mailing list [email protected] http://lists.iptel.org/mailman/listinfo/sems
