Hi,
> I assume you should be putting a max forward header field in all requests According to chapter 8.1.1.6, yes. > and I would guess you should put it in responses I don't think so. If a request has been able to reach the UAS, within the allowed number of hops, I think the response should also be allowed to reach the UAC. Setting a Max-Forwards header in the response, with a LOWER value than in the request, could prevent this and the response would never reach the UAC. You should remember that the response always uses the same path as the request, so there is no risk for "response loops" etc. Regards, Christer Holmberg Ericsson Finland > but I do not see a Max-Forward field used in the responses in > draft-ietf-sipping-call-flows-00, and it does not seem to make sense putting > the header in a 100 trying message, since that message is not forwarded > on... > > any ideas? > > thanks, > mike feldman > [EMAIL PROTECTED] > _______________________________________________ > Sip-implementors mailing list > [EMAIL PROTECTED] > http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
