Method TUWriteHighSideV

SIP/SIPTransaction.cpp:567–591

It is hardly worth the effort to make a transaction for REGISTER, which occurs outside a dialog and has only one reply, but we need to know when to destroy it.

// It is hardly worth the effort to make a transaction for REGISTER, which occurs outside a dialog
// and has only one reply, but we need to know when to destroy it.
void SipRegisterTU::TUWriteHighSideV(SipMessage *sipmsg) {
	int code = sipmsg->msmCode;
	static const char *pRejectCauseHeader = "P-GSM-Reject-Cause";
	LOG(DEBUG) <<LOGVAR(code);
	if (code == 0) {
		// A register transaction does not receive any requests.
		LOG(ERR) << "Register SIP TU received unexpected message:"<<sipmsg;
		stDestroyV();
	} else if (code == 401) {
		//setDialogState(Fail,sipmsg);
		sendAuthFailMessage(code,sipmsg->smGetRand401(),sipmsg->msmHeaders.paramFind(pRejectCauseHeader));
		setTransactionState(stCompleted);
	} else if (code == 200) {
		// (pat) We can no longer stash Kc directly in the TMSI table because the entry is not created until the MS is validated.
		//stashAuthInfo(sipmsg); // Stash the Kc from the message.
		sendAuthOKMessage(sipmsg);
	} else switch ((code/100) * 100) {
		// These SetDialogState are really only for in-dialog messages.
		case 100: return;	// we dont care.
		case 200: LOG(ERR) << "invalid SIP REGISTER code:"<<code;	// Code in the range 201-299 is allegedly impossible.
		default:
			sendAuthFailMessage(code,"",sipmsg->msmHeaders.paramFind(pRejectCauseHeader));
			return;
	}
}

SipRegisterTU::SipRegisterTU(SipDialog *registrar, SipMessage *request)
{