Re: [sr-dev] double record-routing also at outbound edge

If the edge proxy does not add a flow-token to the Path: header how will INVITEs ever get to client devices behind NATs?

The location record in the registrar will not contain a valid (NAT aware) route back to the client.

Regards,

Peter

On 25/04/13 16:02, Juha Heinanen wrote:

Juha Heinanen writes:

...

i would like to change the test so that warning comes only if gruu is not supported:

if (use_ob == 0) {
	if ((get_supported(_m) & F_OPTION_TAG_OUTBOUND)
	        && contact->reg_id) {
	        if (!(get_supported(_m) & F_OPTION_TAG_GRUU)) {
		        LM_WARN("Outbound used by UAC but not supported by edge proxy\n");
		        rerrno = R_OB_UNSUP_EDGE;
		        goto error;
	        }
	} else {
		/* ignore ;reg-id parameter */
		use_regid = 0;
	}
}

actually, it would be better for the edge proxy in gruu case to add ;ob param to path header, but leave out flow token. that way, the operation would be fully conforming to outbound rfc.

-- juha

---

sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev