< Previous by Date Date Index Next by Date >
  Thread Index Next in Thread >

[reSIProcate] Multiple non-invite client transactions


Hello,

 

My usecase has multiple info request/response transactions during a session. What I am finding is that the Timer K which moves the NICT from the Completed to Terminated states has not fired.

 

Questions:

 

Is it possible to set Timer K to some other value other than T4? If so, how?

 

This seems to be allowed in RFC 3261 pg 258

RFC 2543 was silent on whether a UA could initiate a new

transaction to a peer while another was in progress. That is now

specified here. It is allowed for non-INVITE requests, disallowed

for INVITE.”

Is this an issue or has it been fixed in the latest release?

 

Finally, here is the exception raised:

UsageUseException::Cannot start a non-invite transaction until the previous one has completed

 

 

Thanks for all your help, I really appreciate it, and I’m really sorry if this is covered in the archives or wiki – I couldn’t find it.

 

Stephen Keohane