[reSIProcate] Internal 408/503 msg. marked External

[Scott Godin]

I'm not a 100% sure, but I think it's marked as an external to trick the
transaction state machine into processing the response as if it had come
from an External source.  If you want to see if a message is internally
generated of not, use the getReceivedTransport() call - if it returns
NULL (0), then the message was internally generated.

 

Scott

 

From: resiprocate-devel-bounces at list.resiprocate.org
[mailto:resiprocate-devel-bounces at list.resiprocate.org] On Behalf Of
Nilay Tripathi
Sent: Tuesday, July 17, 2007 2:20 AM
To: resiprocate-devel
Subject: [reSIProcate] Internal 408/503 msg. marked External

 

Hi,

I was trying out some timeout cases, when I had this problem !!
If I try to make a call without connectivity, I get 503 which is
internally generated. 503 SIP msg. returns true for msg.isExternal()
check.

While looking into makeResponse in Helper.cxx (Line 435/436), the
response is marked as External by calling response.setFromExternal(). 

If we are creating a response for an internal request, is it correct to
mark it as external from a UA's perspective ?? 

Regards,
Nilay

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20070717/3977b119/attachment.htm>