<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>13 mar 2013 kl. 17:36 skrev "Mark Michelson" <<a href="mailto:reviewboard@asterisk.org">reviewboard@asterisk.org</a>>:</div><br class="Apple-interchange-newline"><blockquote type="cite"><pre style="font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255); margin: 0px; padding: 0px; white-space: pre-wrap; word-wrap: break-word; ">In order to keep things simple, there are certain operations we will not do if there is currently a reinvite transaction in progress. These things are
1) Send any sort of session refresh request (INVITE or UPDATE)
2) End a session
</pre><br class="Apple-interchange-newline"></blockquote></div>That's cool. So if Asterisk sends me a re-invite and I keep it happy sending a 18x every minute, you can not send a BYE!<div><br></div><div>Sweet. But not good. In fact, pretty dangerous. Keep working on this :-) There has to be a way to have two concurrent transactions open. You will need it anyway, like sending an UPDATE during an INVITE or PRACKs., those lovely glorius and sweet PRACKs.</div><div><br></div><div>/O</div></body></html>