29 Dec
2008
29 Dec
'08
8:03 a.m.
On 12/28/08 23:56, Aurelien Grimaud wrote:
Daniel-Constantin Mierla a écrit :
retransmission timers are reset before executing the tm onreply route.
You talk about this with one of the patches I sent or before that?
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://www.asipto.com
On 12/20/08 14:09, Aurelien Grimaud wrote:
Well, actually I dropped the message in an onreply_route armed via tm
and timer were not canceled.
Correct me if I'm wrong, but I think that the timer processing is
*after* the reply_route execution.
Daniel-Constantin Mierla a écrit :
ok, i understand.
On 12/19/08 10:10, Aurelien Grimaud wrote:
> Klaus Darilion a écrit :
>
>
>> Strange!
>>
>> Nevertheless there is no need to drop 100 as 100 is never relayed.
>>
>>
> Yep, my mistake !
>
> The first destination chosen for serial forking was sending a 101
> with sdp, which was relayed to caller.
>
>
101 - I haven't heard of such reply so far ... what is the reason
phrase?
Well, this is a home made reply from a pstn gateway.
The pstn gateway sens request to a pstn network equipement.
As soon as the pstn equipements answers a Progress, a 101 is relayed
to openser.
It contains really early sdp.
I thought it smart.
I am not so sure now !
If you want to get to tm but not relayed upstream, you should drop it
in an onreply_route armed via tm (t_on_reply(...) call), not the
default onreply_route.