Media5 Mediatrix 4104, Справочное руководство

Страница: 288 / 466

Chapter 18 - SIP Protocol Features Registration Parameters
266 Mediatrix 4104
3. Enable the SIP penalty box feature by setting the sipPenaltyBoxEnable variable to enable .
The penalty box is always “active”. This means that even if the feature is disabled, IP addresses are
marked as invalid, but they are still tried. This has the advantage that when the feature is enabled,
IP addresses that were already marked as invalid are instantly put into the penalty box.
Registration Parameters
The following describes registration parameters and behaviours you can configure.
Refreshing Registration
You can refresh the registration, i.e., commit the changes you have done to the registration. When refreshing
the registration, all enabled endpoints unregister themselves from the previous registrar and send a new
registration to the current registrar with the current parameters.
Variables whose modification require a registration refresh are:

sipRegistrarStaticHost

sipRegistrarStaticPort

sipUAMainUsername

sipUADisplayName

sipServerSelectConfigSource

sipTransportRegistrationEnable

sipTransportEnable (if sipTransportRegistrationEnable is enabled)

sipTransportQValue (if sipTransportRegistrationEnable is enabled)

To refresh the registrations:
1. In the sipMIB , set the sipRegistrationCmdRefresh variable with the proper behaviour.
The following values are available:
• noOp: No operation.
• refresh: Refresh registrations.
2. Define the time, in seconds, at which a registered unit begins updating its registration before the
registration expiration in the
sipReRegistrationTime variable.
For instance, if the variable is set to 43 and the registration lasts one hour, the unit will send new
REGISTER requests 59 minutes and 17 seconds after receiving the registration acknowledgement
(43 seconds before the unit becomes unregistered).
This value MUST be lower than the value of the Expires header of the contact in the 200 OK
response to the REGISTER, otherwise the unit rapidly sends REGISTER requests continuously.
Registration Expiration
The SIP protocol allows an entity to specify the “expires” parameter of a contact in a REGISTER request. The
server can return this “expires” parameter in the 200 OK response or select another “expires”. In the
REGISTER request, the “expires” is a suggestion the entity makes.
The “expires” parameter indicates how long, in seconds, the user agent would like the binding to be valid.
Note:
Normally, the Mediatrix 4104 cannot make or receive calls until the REGISTER has completed
successfully. Because the timeout for a SIP transaction in UDP is 32 seconds, it is possible to have an
ongoing re-REGISTER transaction at the same moment that the registration itself expires. This could
happen if
sipReRegistrationTime is set to a value lower than 32.
In that case, the user agent becomes unregistered, and will become registered again only when the re-
REGISTER request is answered with a positive response from the server. See
“Unregistered Line
Behaviour” on page 222 for a workaround if the unit cannot make calls during that period.