[reSIProcate] internally generated 408/503

[Byron Campen]

	I think calling SipMessage::isExternal() should do the trick. When  
the stack simulates 408, it constructs the SipMessage in such a way  
that mIsExternal is set to false. I imagine the same thing happens  
for simulated 503 due to DNS blacklisting.

Best regards,
Byron Campen

> Hi folks,
>
> Can anybody think of a way to know that a response (e.g. 408 or 503)
> was generated internally by the stack rather than received off the
> wire? I couldn't think of an obvious way to do this without adding
> some additional stuff to SipMessage and Helper.
>
> Jason
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel at list.sipfoundry.org
> https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel

-------------- 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/20061012/ef569d4b/attachment.bin>