Subject says it all. I ran into an issue with a buggy Asterisk where the re-INVITE (refresh) from my app would overlap with a re-INVITE from the Asterisk. Both parties respond with '491 Request pending' and that's it.
The bug in Asterisk is that it never actually retries the re-INVITE (yes, it's a very old version; no, an upgrade is _not_ possible *grrr*). The effect is, that I've got a dangling call (re-INVITE from Asterisk came because the caller hung up) because my application only hangs up calls if some kind of higher level error occurs. When I understand RFC3261 correctly, the UAC must retry the request after some time and since (again: if I understand correctly) the UAC/UAS roles are transaction based: Shouldn't BOTH parties retry their INVITE requests? I'll have to backport the fix in Asterisk but isn't this a problem in Sofia, too? Regards, Andreas ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ Sofia-sip-devel mailing list Sofia-sip-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
