[sr-dev] [tracker] Comment added: UAC generates messages with a NULL body which failes in SANITY module check

sip-router bugtracker at sip-router.org
Mon May 20 23:19:16 CEST 2013


THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#295 - UAC generates messages with a NULL body which failes in SANITY module check
User who did this - oren avraham (orenav)

----------
Here is my code
$uac_req(method) = "REGISTER";
		$uac_req(ruri) = $sht(websocket=>$si:$sp:ruri);
		$uac_req(furi) = $sht(websocket=>$si:$sp:furi);
		$uac_req(turi) = $sht(websocket=>$si:$sp:turi);
		$uac_req(hdrs) = $sht(websocket=>$si:$sp:hdrs);
		if (uac_req_send() < 0)
			xlog("L_ERROR","Failed sending unregister request");

and also a code for debug the sanity check:
if (!sanity_check("2")) {
		xlog("SANITY: uri scheme\n");
		exit;
	}
 
 	if (!sanity_check("4")) {
		xlog("SANITY: no mininal set of required headers\n");
		exit;
	}
	
	if (!sanity_check("64")) {
		xlog("SANITY: cseq value\n");
		exit;
	}
	
	if (!sanity_check("32")) {
		xlog("SANITY: cseq method\n");
		exit;
	}
	
	if (!sanity_check("128")) {
		xlog("SANITY: content length: cl=$cl rb= $rb bs=$bs mb=$mb\n");
		exit;
	}
	
 	if (!sanity_check("256")) {
	/* the register contains an invalid expires value and is replied with a 400 */
		xlog("SANITY: invalid expires\n");
		exit;
	}
	
	if (!sanity_check("1024","7")) {
	/* the register contains an invalid expires value and is replied with a 400 */
		xlog("SANITY: bad uris\n");
		exit;
	}
	
	if(!sanity_check("1511", "7"))
	{
		xlog("Malformed SIP message from $si:$sp\n");
		exit;
	}

I generate the message from a saved register message, that i've altered its expired contact parameter to 0.
When the generated message is run within main_route it gets to the sanity check and fails with check no.128 and its $rb is null.

Hope it was helpfull..

----------

More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=295#comment882

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.



More information about the sr-dev mailing list