while doing a sems dsm test, i'm getting this kind of stuff to syslog when caller sends bye:
Sep 28 14:38:53 siika /usr/sbin/sip-proxy[26218]: INFO: Routing in-dialog BYE <sip:192.98.102.10:5090> from <sip:[email protected]> Sep 28 14:38:53 siika sems[25484]: [#7f30d8c9d700] [reply, AmBasicSipDialog.cpp:524] ERROR: could not find any transaction matching request cseq Sep 28 14:38:53 siika sems[25484]: [#7f30d8c9d700] [reply, AmBasicSipDialog.cpp:528] ERROR: request cseq=10; reply code=487; callid=3D59451F-5246BFC7000C8209-D83DC700; local_tag=1C85A1FB-5246BFC7000C943B-D8FA0700; remote_tag=5E048D58-5246BFC7000C81F8-D83DC700 Sep 28 14:38:53 siika sems[25484]: [#7f30d8c9d700] [log_stacktrace, log.cpp:217] ERROR: stack-trace(0): /usr/sbin/sems(log_stacktrace+0x22) [0x534722] Sep 28 14:38:53 siika sems[25484]: [#7f30d8c9d700] [log_stacktrace, log.cpp:217] ERROR: stack-trace(1): /usr/sbin/sems(_ZN16AmBasicSipDialog5replyERK12AmSipRequestjRKSsPK10AmMimeBodyS4_i+0xa82) [0x48bff2] Sep 28 14:38:53 siika sems[25484]: [#7f30d8c9d700] [log_stacktrace, log.cpp:217] ERROR: stack-trace(2): /usr/lib/sems/dsm/mod_dlg.so(_Z12replyRequestP10DSMSessionP9AmSessionPSt3mapISsSsSt4lessISsESaISt4pairIKSsSsEEERS7_SC_RK12AmSipRequest+0x2f5) [0x7f30d9e0c865] Sep 28 14:38:53 siika sems[25484]: [#7f30d8c9d700] [log_stacktrace, log.cpp:217] ERROR: stack-trace(3): /usr/lib/sems/dsm/mod_dlg.so(_ZN14DLGReplyAction7executeEP9AmSessionP10DSMSessionN12DSMCondition9EventTypeEPSt3mapISsSsSt4lessISsESaISt4pairIKSsSsEEE+0x42) [0x7f30d9e0ced2] Sep 28 14:38:53 siika sems[25484]: [#7f30d8899700] [execute, DSMCoreModule.cpp:521] INFO: FSM: '==== caller leg hangup at callee' Sep 28 14:38:53 siika sems[25484]: [#7f30d8c9d700] [log_stacktrace, log.cpp:217] ERROR: stack-trace(4): /usr/lib/sems/plug-in//dsm.so(_ZN14DSMStateEngine10runactionsEN9__gnu_cxx17__normal_iteratorIPP10DSMElementSt6vectorIS3_SaIS3_EEEES8_P9AmSessionP10DSMSessionN12DSMCondition9EventTypeEPSt3mapISsSsSt4lessISsESaISt4pairIKSsSsEEERb+0x7b) [0x7f30dd2984bb] Sep 28 14:38:53 siika sems[25484]: [#7f30d8c9d700] [log_stacktrace, log.cpp:217] ERROR: stack-trace(5): /usr/lib/sems/plug-in//dsm.so(_ZN14DSMStateEngine8runEventEP9AmSessionP10DSMSessionN12DSMCondition9EventTypeEPSt3mapISsSsSt4lessISsESaISt4pairIKSsSsEEEb+0x4da) [0x7f30dd29c30a] Sep 28 14:38:53 siika sems[25484]: [#7f30d8c9d700] [log_stacktrace, log.cpp:217] ERROR: stack-trace(6): /usr/lib/sems/plug-in//dsm.so(_ZN7DSMCall5onByeERK12AmSipRequest+0xd1) [0x7f30dd25dba1] Sep 28 14:38:53 siika /usr/sbin/sip-proxy[26205]: INFO: ===== ru/du = <sip:[email protected]:56776;transport=tcp>/<<null>> Sep 28 14:38:53 siika sems[25484]: [#7f30d8c9d700] [log_stacktrace, log.cpp:217] ERROR: stack-trace(7): /usr/sbin/sems(_ZN9AmSession12onSipRequestERK12AmSipRequest+0x1aa) [0x4e7cfa] Sep 28 14:38:53 siika sems[25484]: [#7f30d8c9d700] [log_stacktrace, log.cpp:217] ERROR: stack-trace(8): /usr/sbin/sems(_ZN12AmB2BSession12onSipRequestERK12AmSipRequest+0x103) [0x47f6f3] Sep 28 14:38:53 siika /usr/sbin/sip-proxy[26205]: INFO: BYE <sip:[email protected]:56776;transport=tcp> is NOT gruu Sep 28 14:38:53 siika /usr/sbin/sip-proxy[26205]: INFO: Routing in-dialog BYE <sip:[email protected]:56776;transport=tcp> from <sip:[email protected]> Sep 28 14:38:53 siika sems[25484]: [#7f30d8c9d700] [log_stacktrace, log.cpp:217] ERROR: stack-trace(9): /usr/lib/sems/plug-in//dsm.so(_ZN7DSMCall12onSipRequestERK12AmSipRequest+0x598) [0x7f30dd260fb8] Sep 28 14:38:53 siika sems[25484]: [#7f30d8c9d700] [log_stacktrace, log.cpp:217] ERROR: stack-trace(10): /usr/sbin/sems(_ZN16AmBasicSipDialog11onRxRequestERK12AmSipRequest+0x40b) [0x48d12b] Sep 28 14:38:53 siika sems[25484]: [#7f30d8c9d700] [log_stacktrace, log.cpp:217] ERROR: stack-trace(11): /usr/sbin/sems() [0x4e4c18] Sep 28 14:38:53 siika sems[25484]: [#7f30d8c9d700] [log_stacktrace, log.cpp:217] ERROR: stack-trace(12): /usr/lib/sems/plug-in//dsm.so(_ZN7DSMCall7processEP7AmEvent+0x125f) [0x7f30dd26256f] Sep 28 14:38:53 siika sems[25484]: [#7f30d8c9d700] [log_stacktrace, log.cpp:217] ERROR: stack-trace(13): /usr/sbin/sems(_ZN12AmEventQueue13processEventsEv+0x54) [0x4abfb4] Sep 28 14:38:53 siika sems[25484]: [#7f30d8c9d700] [log_stacktrace, log.cpp:217] ERROR: stack-trace(14): /usr/sbin/sems(_ZN9AmSession28processEventsCatchExceptionsEv+0x24) [0x4e65f4] Sep 28 14:38:53 siika sems[25484]: [#7f30d8c9d700] [log_stacktrace, log.cpp:217] ERROR: stack-trace(15): /usr/sbin/sems(_ZN9AmSession15processingCycleEv+0x4c) [0x4e908c] Sep 28 14:38:53 siika sems[25484]: [#7f30d8c9d700] [log_stacktrace, log.cpp:217] ERROR: stack-trace(16): /usr/sbin/sems(_ZN9AmSession3runEv+0x71) [0x4e43e1] Sep 28 14:38:53 siika sems[25484]: [#7f30d8c9d700] [log_stacktrace, log.cpp:217] ERROR: stack-trace(17): /usr/sbin/sems(_ZN8AmThread6_startEPv+0x49) [0x515e09] Sep 28 14:38:53 siika sems[25484]: [#7f30d8c9d700] [log_stacktrace, log.cpp:217] ERROR: stack-trace(18): /lib/x86_64-linux-gnu/libpthread.so.0(+0x6b50) [0x7f30e326eb50] Sep 28 14:38:53 siika sems[25484]: [#7f30d8c9d700] [log_stacktrace, log.cpp:217] ERROR: stack-trace(19): /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x7f30e2885a7d] the test goes like this: uac -> sems ivr connectCallee - sems dsm mod_dlg (caller/callee) - uas when i studied wireshark dump, i noticed that call id used between sems ivr and sems dsm is 3D5x and callid between sems and uas is 0B1. cseqs from sems ivr to sems dsm are invite=10, prack=11, and re-invite=12. cseq in invite from sems dsm to uas is 10. when sems ivr receives bye from uac (twinkle), wireshark tells that sems sends out two byes to itself: Request-Line: BYE sip:192.98.102.10:5090 SIP/2.0 Message Header Via: SIP/2.0/UDP 192.98.102.10:5090;branch=z9hG4bKMYS3MaRw;rport From: "Juha Heinanen" <sip:[email protected]>;tag=5E048D58-5246BFC7000C81F8-D83DC700 To: sip:[email protected];appl=rec_caller;tag=1C85A1FB-5246BFC7000C943B-D8FA0700 CSeq: 13 BYE Call-ID: 3D59451F-5246BFC7000C8209-D83DC700 Route: <sip:192.98.102.10:5070;lr> Content-Length: 0 Request-Line: BYE sip:192.98.102.10:5090 SIP/2.0 Message Header Via: SIP/2.0/UDP 192.98.102.10:5090;branch=z9hG4bKS6rWna7a;rport From: "Juha Heinanen" <sip:[email protected]>;tag=5E048D58-5246BFC7000C81F8-D83DC700 To: sip:[email protected];appl=rec_caller;tag=1C85A1FB-5246BFC7000C943B-D8FA0700 CSeq: 14 BYE Call-ID: 3D59451F-5246BFC7000C8209-D83DC700 Route: <sip:192.98.102.10:5070;lr> Max-Forwards: 16 User-Agent: Twinkle/1.4.2 Content-Length: 0 they are both using callid of the call between sems ivr and sems dsm. in the first bye, cseq is 13 (one larger that in re-invite), but looks like it is not coming from sems ivr because User-Agent header is missing. the second one is with cseq 14 and it does include User-Agent header so looks it would be coming from sems ivr. after that, sems dsm sends bye correctly to uas. many questions. why does the error message refer to reply code 487 that does not exist anywhere in the wireshark dump: Sep 28 14:38:53 siika sems[25484]: [#7f30d8c9d700] [reply, AmBasicSipDialog.cpp:528] ERROR: request cseq=10; reply code=487; callid=3D59451F-5246BFC7000C8209-D83DC700; local_tag=1C85A1FB-5246BFC7000C943B-D8FA0700; remote_tag=5E048D58-5246BFC7000C81F8-D83DC700 why does the error message tell that cseq is 10 when none of the byes has such a cseq? do the stack trace error messages tell something? if i skip sems ivr and make uac call sems dsm directly, i don't get any errors. would it be possible that sems gets confused when a single call deals with two applications? what to do next in order to get to bottom of this? -- juha _______________________________________________ Semsdev mailing list [email protected] http://lists.iptel.org/mailman/listinfo/semsdev
