Media5 Mediatrix 4104, Reference Manual

Page: 289 / 466

Publication Parameters Reference Manual (SIP Version)
Mediatrix 4104 267
You can configure the “expires” parameter the Mediatrix 4104 sends.

To configure the registration expiration:
1. In the sipMIB , set the sipRegistrationProposedExpirationValue variable with the suggested
expiration delay, in seconds, of a contact in the REGISTER request.
Available values are from 1 s to 86,400 s (one day).
This value does not modify the time before a re-REGISTER.
• The time is the “expires” of the contact in the 200 OK response to the REGISTER
request minus the value set in the
sipReRegistrationTime variable.
• If the “expires” of the contact in the 200 OK response to the REGISTER is not present
or not properly formatted, then the time is the default registration expires minus the
value set in the
sipReRegistrationTime variable.
See “Refreshing Registration” on page 266 for more details.
Setting the variable to 0 disables the expiration suggestion.
Default Registration Expiration
RFC 3261 specifies that, when the “expires” parameter or the “Expires” header is missing or not properly
formatted for a contact of the 200 OK in response to a REGISTER request, the unit must use a default
registration expiration value of 3600 s.
You can configure the value of the default registration expiration.

To configure the default registration expiration:
1. In the sipInteropMIB , set the sipInteropDefaultRegistrationExpiration variable with the default
registration expiration.
The delay before a re-REGISTER is the value set in the sipInteropDefaultRegistrationExpiration
variable minus the value set in the sipReRegistrationTime variable. See “Refreshing Registration”
on page 266 for more details.
The recommended value in RFC 3261 (section 10.2) is 3600 seconds.
2. Restart the Mediatrix 4104 so that the change may take effect.
Publication Parameters
The following describes publication parameters and behaviours you can configure.
Refreshing Publications
You can refresh the publications, i.e., commit the changes you have done to the publications. When refreshing
the publications, all enabled endpoints unpublish themselves from the previous Presence Compositor and
send a new publication to the current Presence Compositor with the current parameters.
Variables whose modification require a registration refresh are:

sipPresenceCompositorStaticHost

sipPresenceCompositorStaticPort
Standards Supported RFC 3261 – SIP: Session Initiation Protocol, section 20.41 (User-Agent)
Standards Supported • RFC 3863 – Presence Information Data Format (PIDF)
• RFC 3903 – Session Initiation Protocol (SIP) Extension for
Event State Publication