[reSIProcate] [repro-devel] Open issue: Server transaction lifetime
Byron Campen
bcampen at estacado.net
Tue Aug 8 15:37:52 CDT 2006
On Aug 8, 2006, at 3:32 PM, Jason Fischl wrote:
> On 8/8/06, Byron Campen <bcampen at estacado.net> wrote:
>> Actually, this is a bad example; we end up parsing the topmost Via
>> when we grab the transaction id. The point here is that really
>> bizarre stuff can show up at the TU.
>>
>
> We parse everything that is required in the transaction in the
> Transport before the TransactionState object is created. The code is
> all in Transport::basicCheck. The
>
> The items such as To, From, Call-ID are dialog-specific and are not
> required in order to produce a failure response to a request.
No, it doesn't. basicCheck() relies on Helper::validateMessage(),
which just makes a bunch of calls to SipMessage::exists().
SipMessage::exists() doesn't parse anything.
Best regards,
Byron Campen
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2369 bytes
Desc: not available
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20060808/02b106f9/attachment.bin>
More information about the resiprocate-devel
mailing list