Re: [reSIProcate] internally generated 408/503
isExternal doesn't work. Apparently we are making internally generated
408's appear as external so that the transaction state handles them in
the same manner as external messages. The SipMessage method
getReceivedTransport() works - just look for a return of 0.
BTW: I committed a fix to resip so that we will not blacklist if a 408
response is from the wire.
Scott
> -----Original Message-----
> From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx
> [mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of
> Byron Campen
> Sent: Thursday, October 12, 2006 1:24 PM
> To: Jason Fischl
> Cc: resiprocate
> Subject: Re: [reSIProcate] internally generated 408/503
>
> 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@xxxxxxxxxxxxxxxxxxx
> > https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel