[reSIProcate] response matching

[Byron Campen]

	SipStack keeps track of all the needed transaction information. If  
you simply must look at the code, it is down in  
TransactionState::process. SipStack does not keep track of dialog-state.

Best regards,
Byron Campen

> I have problem with the sipstack:process(fdset) here:
>
> When the following method implemented:
>
> stack.process(fdset);
>
> "how does it know which response is for which request?"--if there  
> are 5 requests with different subscribe request, and results in 4  
> responses  with 200k and  1 responses with 100k.
>
>
> ---Does the reSIProcate parse the message header in order to know  
> which response(or notify) matches which request(for example, a  
> specific  subscribe ).
>
> Could anybody help me with this matching? where is the code  
> handling this? by transaction Id or dialog Id?
>
> Get your own web address.
> Have a HUGE year through Yahoo! Small Business.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20070301/57aa4957/attachment.htm>