reSIProcate

Mailing Lists

Source Code

Google Search:



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

Re: [reSIProcate] application timer in resiprocate architecture

Please note, any files I mention are referring to svn head.

Answers inlined:

Hi,

I have few questions regarding the AppTimerQueue in reSIProcate architecture.

1. How this AppTimerQueue is initialized for timers for each of the TUs? It is
connected with the SIP Stack Obj box in the arch. diag.


In svn head, there is only one queue of app timers (see resip/stack/TimerQueue.hxx for the definition of TuSelectorTimerQueue); stuff coming out of this queue is de-multiplexed based on the TransactionUser* contained in the message (see resip/stack/Message.hxx), and passed to the appropriate TU's fifo.

2. What is the significance of SIP Stack Obj block in the architecture design
as it looks like referring to the SIP stack only (as the name suggests). So I
want to know what exact functionality it is supposed for.


The SIP Stack Obj in the architecture design diagram refers to a instance of the SipStack class. It is effectively intended as an abstraction-layer on top of stuff like TransactionController/TransactionState, TransportSelector and the TUSelector. Its secondary duty is to coordinate all the pieces of the system in their processing.

3. What can be the scenarios where I would need to tell the application about
the timeouts. Only one that I can think of is that on UAS side, receiving a
request if the TU does not provision within 200ms then the transaction layer
can send a provisional response to the peer. Here it will be good to send a
timeout to the App.

The stack automatically sends a provisional if the TU does not in 200ms (by default). No prompting of the TU is necessary. The AppTimerQueue is intended to allow the TU to set up arbitrary timers for anything under the sun. For example, repro uses this mechanism to schedule call-processing events (ie, if this target doesn't answer in 3 sec, move on to this other target; see repro/ForkControlMessage.hxx).


Thanks,

Regards,
Nilay
_______________________________________________
resiprocate-devel mailing list

Best regards,
Byron Campen


Attachment: smime.p7s
Description: S/MIME cryptographic signature