Stefan Sayer writes: > could there be an issue with the transaction matching when there's a > call originating from SEMS and going through the same SEMS instance in > B2B mode (sbc)? > > I am experiencing the problem that the ACK seemingly clears the > transaction (transaction goes to TS_REMOVED), but the 200 is > retransmitted from the B2B (until it times out waiting for ACK and the > call is terminated). This doesn't happen if I use a separate SEMS > instance for the B2B. > > Could it be that the transactions are mixed up and the wrong > transaction is removed when processing the ACK?
stefan, the matching problem i was referring to in the previous message, looks similar to what you describe in above. i have my conf_auth ivr app before sems conference application, i.e, call flow is ua -> proxy -> sems (conf_auth) -> proxy -> sems (conference) conf auth app makes connectCallee call to conference (via proxy) if authentication succeeds. when conference app receives invite from conf_auth, there is one record-route entry added by the proxy and of course the same when conf_auth app receives 200 ok from conference app. but when conf_auth then sends ack to this 200 ok, the ack contains TWO route entries, which looks wrong to me. i have both debug log and wireshark dump available if needed. this is with latest 1.4 from git. -- juha _______________________________________________ Semsdev mailing list [email protected] http://lists.iptel.org/mailman/listinfo/semsdev
