< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index  

Re: [reSIProcate] missing Max-Forwards in CANCEL


CANCEL is a single-hop request, and therefore doesn't really need a Max-Forwards header. However, RFC 3261 mandates it, so I am leaning in the direction of just adding it. Any objections?

Best regards,
Byron Campen

Mandatory header Max-Forwards missing in CANCEL.

/Björn

--- Helper.cxx.orig    2008-03-20 14:51:45.000000000 +0100
+++ Helper.cxx    2008-03-20 14:58:11.000000000 +0100
@@ -545,20 +545,21 @@
SipMessage*
Helper::makeCancel(const SipMessage& request)
{
   assert(request.isRequest());
   assert(request.header(h_RequestLine).getMethod() == INVITE);
   SipMessage* cancel = new SipMessage;
RequestLine rLine(CANCEL, request.header (h_RequestLine).getSipVersion());
   rLine.uri() = request.header(h_RequestLine).uri();
   cancel->header(h_RequestLine) = rLine;
+   cancel->header(h_MaxForwards).value() = 70;
   cancel->header(h_To) = request.header(h_To);
   cancel->header(h_From) = request.header(h_From);
   cancel->header(h_CallId) = request.header(h_CallId);
   if (request.exists(h_ProxyAuthorizations))
   {
cancel->header(h_ProxyAuthorizations) = request.header (h_ProxyAuthorizations);
   }
   if (request.exists(h_Authorizations))
   {
cancel->header(h_Authorizations) = request.header (h_Authorizations);
_______________________________________________
resiprocate-devel mailing list
resiprocate-devel@xxxxxxxxxxxxxxx
https://list.resiprocate.org/mailman/listinfo/resiprocate-devel
_______________________________________________
resiprocate-devel mailing list
resiprocate-devel@xxxxxxxxxxxxxxx
https://list.resiprocate.org/mailman/listinfo/resiprocate-devel

Attachment: smime.p7s
Description: S/MIME cryptographic signature