[sr-dev] Using t_suspend()/t_continue() multiple times on the same transaction
Dunkley, Peter
peter.dunkley at acision.com
Wed Jul 2 23:19:47 CEST 2014
This was more than two years ago. To be honest, I cannot remember what solution I came up with in the end.
Peter
On 2 Jul 2014, at 10:24, dennis <dennis.yu at live.cn> wrote:
>
> Peter Dunkley <peter.dunkley at ...> writes:
>
>>
>>
>> Hi,
>> I am trying to use t_suspend()/t_continue() multiple times on the same
> transaction. Calling t_suspend() more than once works, but the second time
> I call t_continue() the transaction is killed and a 500 response is sent.
> It is the "if (branch == t->nr_of_outgoings)" check from the code fragment
> below (from t_suspend.c:t_continue()) that results in the transaction being
> killed - you can see the debug/error line I added to determine this in the
> fragment.
>> Is using t_suspend()/t_continue() multiple times something that should
> work?
>> Thanks,
>> Peter
>> if (t->uas.status < 200) {
>> /* No final reply has been sent yet.
>> * Check whether or not there is any pending branch.
>> */
>> for ( branch = 0;
>> branch < t->nr_of_outgoings;
>> branch++
>> ) {
>> if ((t->uac[branch].request.buffer != NULL)
>> && (t->uac[branch].last_received < 200)
>> )
>> break;
>> }
>> if (branch == t->nr_of_outgoings) {
>> /* There is not any open branch so there is
>> * no chance that a final response will be
> received. */
>> ret = 0;
>> LM_ERR("branch == t->nr_of_outgoings\n");
>> goto kill_trans;
>> }
>> }
>>
>>
>
>
> hi Peter,
> are you find any solution? the same problem occur in my circumstance.
>
>
>
>
> _______________________________________________
> sr-dev mailing list
> sr-dev at lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
________________________________
This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you for understanding.
More information about the sr-dev
mailing list