Hi Daniel
The branch is a tmp branch and Jason has also been using it to do
improvements to the general TM supend/continue functionality.
We are just in final stages and cleaning, load and memory testing. Once
thats there we will provide a single patch for discussion.
Regards
Richard.
On 12 J
Hello,
is still work on this patch on personal branches? I have seen Jason
committing stuff, although some patched seemed to be to sip request
suspend/continue.
Also, for review, would be good to have a single patch generated (diff
between the branches), because is hard to follow with patche
Hi
Thanks very much for the quick feedback. My comments inline.
Regards
Richard.
On 6 July 2013 19:48, Daniel-Constantin Mierla wrote:
> Hello,
>
> the patch cannot be applied as it is. The comments contain references to
> request processing, which is obviously wrong. Then I have seen code
>
Hello,
the patch cannot be applied as it is. The comments contain references to
request processing, which is obviously wrong. Then I have seen code
specific to requests, like managing the request uri or dst uri -- these
fields shouldn't be set for replies, it's ok as safety to clear them up,
Hi
I've finally got working functionality for t-suspend and t_continue for SIP
responses in the tmp/tm_async_reply_support branch.
I've memory and load tested the branch and have also isolated the changes
so that if there are problems they will only be experienced if you use the
new API functions
Hi Daniel and other TM experts
We have been working on a prototype for being able to use the t_suspend()
and t_continue() methods for SIP responses. The version in branch
/tmp/tm_async_reply_support is working, though still needs to be 100%
tested and only works for 1 branch (i.e. no forking)**
Hello,
t_suspend() and t_continue() are only for requests at this moment.
Cheers,
Daniel
On 3/6/13 2:49 PM, Richard Good wrote:
Hi
We are using the t_suspend and t_continue functionality to
asynchronously send Diameter messages.
This works nicely when we suspend and resume on a SIP request
Hi
We are using the t_suspend and t_continue functionality to asynchronously
send Diameter messages.
This works nicely when we suspend and resume on a SIP request. However in
some circumstances we want to send a Diameter message on a SIP response.
I have found that the SIP responses continue to
