Hi all, I invested some time in going through the transaction implementation of the NIST stack and observed the below.
The same retransmission timer logic, which is used for non-Invite client transaction is used for the invite retransmissions too. Hence I was able to observe the pattern, which I have described in my previous mail. I was able to change this behavior by tweaking the code a bit and things worked fine after that . Now, I need one clarification on this, Is it OK for the Invite client transaction to follow the same retransmission timer behavior as the Non-Invite client transaction. That is, instead of T1, 2*T1, 4*T1,.....,64*T1 it follows T1, 2*T1, ... , min( pow(2,n) * T1 , T2). Is it a bug ? Please correct me if i am wrong. Thanks & Regards, Nabeel On 8/31/07, nabeel mohamed <[EMAIL PROTECTED] > wrote: > > Hi Arif, > > Thanks for confirming that it is not the problem with the TAHI test bed. I > too felt the same. > > But, am waiting to hear the observations from someone, who had tested the > NIST implementation of INVITE retransmissions. I feel that there are no > issues with the > configuration of the stack properties. > > Thanks, > Nabeel > > On 8/31/07, Arif <[EMAIL PROTECTED]> wrote: > > > > we are currently testing our proxy implementation with the TAHI test bed > > and we have not had any issue with the test bed configuration.. so i assume > > it must be some 'configuration' issue with ur NIST stack.. > > > > regards > > > > > > arif > > > > ------------------------------ > > Be a better Heartthrob. Get better relationship answers > > <http://us.rd.yahoo.com/evt=48255/*http://answers.yahoo.com/dir/_ylc=X3oDMTI5MGx2aThyBF9TAzIxMTU1MDAzNTIEX3MDMzk2NTQ1MTAzBHNlYwNCQUJwaWxsYXJfTklfMzYwBHNsawNQcm9kdWN0X3F1ZXN0aW9uX3BhZ2U-?link=list&sid=396545433>from > > someone who knows. > > Yahoo! Answers - Check it out. > > > > > _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
