The RejectRegisterRequest
feature issues a SIP error response on the triggering REGISTER leg.
Choosing the SIP error response code
The RejectRegisterRequest
uses the RejectRegisterResponseCode
session state field if it is set. Otherwise the
error response code is derived from the RouteHeaderMode
session state field in the following way:
RouteHeaderMode |
SIP Error response code |
---|---|
|
|
|
|
|
|
Details
Feature script name |
RejectRegisterRequest |
---|---|
Applicable contexts |
SIP service |
Prerequisite features |
None |
Session state inputs and outputs
Inputs
Name | Format | Description |
---|---|---|
RouteHeaderMode
|
One of: not_present (no mode parameter in the route header), mmtel (mmtel scenario), scc (scc scenario) or mmtel_scc (mixed, mmtel and scc scenario) |
|
RejectRegisterResponseCode
|
An |
The SIP error response code to use when rejecting the third party REGISTER request |