Juha Heinanen writes:
> > May 10 15:18:58 siika sems[8318]: [#7f1f589fc700] [execute,
> > DSMCoreModule.cpp:569] WARNING: FSM: 'received info'
> > May 10 15:18:58 siika sems[8318]: [#7f1f589fc700] [reply,
> > AmBasicSipDialog.cpp:571] ERROR: could not find any transaction matching
> > request cseq
> > May 10 15:18:58 siika sems[8318]: [#7f1f589fc700] [reply,
> > AmBasicSipDialog.cpp:575] ERROR: request cseq=10; reply code=200;
> > callid=5a264b397dea8269; local_tag=2242B17D-536E192B000D2A47-59103700;
> > remote_tag=9d880afbede7b116
>
> i did check from pcap that call id/from/to tags of INFO request match
> that of the dialog and since this is the first request from callee to
> caller, cseq can be anything, i.e., 10 should be fine.
>
> why is transaction matching failing?
i haven't been able to figure this out. i added a syslog INFO() call here:
void AmBasicSipDialog::onRxRequest(const AmSipRequest& req)
...
INFO("AmBasicSipDialog::onRxRequest setting uas_trans cseq '%d'\n", req.cseq);
uas_trans[req.cseq] = req;
and got to syslog:
May 11 07:55:15 siika sems[8279]: [#7ff77c5a6700] [onRxRequest,
AmBasicSipDialog.cpp:315] INFO: AmBasicSipDialog::onRxRequest setting
uas_trans cseq '10'
and right after that i got error message:
May 11 07:55:15 siika sems[8279]: [#7ff77c4a5700] [reply,
AmBasicSipDialog.cpp:572] ERROR: could not find any transaction matching
request cseq
May 11 07:55:15 siika sems[8279]: [#7ff77c4a5700] [reply,
AmBasicSipDialog.cpp:576] ERROR: request cseq=10; reply code=200;
callid=7d1daacc307e22d1; local_tag=6CA0148B-536F02AD00015278-7D0B1700;
remote_tag=67e6de71c23aaa24
why is the transaction not found even when both syslog messages show the
same cseq value 10? is AmBasicSipDialog::onRxRequest() dealing with
different AmBasicSipDialog object than AmBasicSipDialog::reply()?
-- juha
_______________________________________________
Semsdev mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/semsdev
