OID reference

sipUAMaximumSessionExpirationDelay

1.3.6.1.4.1.4935.20.20.1.1.10.1.30

Description

Suggested maximum time for the periodical session refreshes. This value will be reflected in the Session-Expires header. Increasing the maximum will help to reduce network traffic, but will also make 'dead' calls longer to detect. This value is expressed in seconds (s). To disable the session timer service, set the ma…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.4935.20.20.1.1.10.1 (sipUAIfEntry)
Node code
30
Node name
sipUAMaximumSessionExpirationDelay
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.4935.20.20.1.1.10.1.30
URN notation
urn:oid:1.3.6.1.4.1.4935.20.20.1.1.10.1.30
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 4935 20 20 1 1 10 1 30}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) mediatrix(4935) mediatrixIpTelephonySignaling(20) sip(20) sipMIB(1) sipMIBObjects(1) sipUAIfTable(10) sipUAIfEntry(1) sipUAMaximumSessionExpirationDelay(30)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) mediatrix(4935) mediatrixIpTelephonySignaling(20) sip(20) sipMIB(1) sipMIBObjects(1) sipUAIfTable(10) sipUAIfEntry(1) sipUAMaximumSessionExpirationDelay(30)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) mediatrix(4935) mediatrixIpTelephonySignaling(20) sip(20) sipMIB(1) sipMIBObjects(1) sipUAIfTable(10) sipUAIfEntry(1) sipUAMaximumSessionExpirationDelay(30)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) mediatrix(4935) mediatrixIpTelephonySignaling(20) sip(20) sipMIB(1) sipMIBObjects(1) sipUAIfTable(10) sipUAIfEntry(1) sipUAMaximumSessionExpirationDelay(30)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) mediatrix(4935) mediatrixIpTelephonySignaling(20) sip(20) sipMIB(1) sipMIBObjects(1) sipUAIfTable(10) sipUAIfEntry(1) sipUAMaximumSessionExpirationDelay(30)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) mediatrix(4935) mediatrixIpTelephonySignaling(20) sip(20) sipMIB(1) sipMIBObjects(1) sipUAIfTable(10) sipUAIfEntry(1) sipUAMaximumSessionExpirationDelay(30)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) mediatrix(4935) mediatrixIpTelephonySignaling(20) sip(20) sipMIB(1) sipMIBObjects(1) sipUAIfTable(10) sipUAIfEntry(1) sipUAMaximumSessionExpirationDelay(30)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) mediatrix(4935) mediatrixIpTelephonySignaling(20) sip(20) sipMIB(1) sipMIBObjects(1) sipUAIfTable(10) sipUAIfEntry(1) sipUAMaximumSessionExpirationDelay(30)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) mediatrix(4935) mediatrixIpTelephonySignaling(20) sip(20) sipMIB(1) sipMIBObjects(1) sipUAIfTable(10) sipUAIfEntry(1) sipUAMaximumSessionExpirationDelay(30)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) mediatrix(4935) mediatrixIpTelephonySignaling(20) sip(20) sipMIB(1) sipMIBObjects(1) sipUAIfTable(10) sipUAIfEntry(1) sipUAMaximumSessionExpirationDelay(30)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) mediatrix(4935) mediatrixIpTelephonySignaling(20) sip(20) sipMIB(1) sipMIBObjects(1) sipUAIfTable(10) sipUAIfEntry(1) sipUAMaximumSessionExpirationDelay(30)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) mediatrix(4935) mediatrixIpTelephonySignaling(20) sip(20) sipMIB(1) sipMIBObjects(1) sipUAIfTable(10) sipUAIfEntry(1) sipUAMaximumSessionExpirationDelay(30)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) mediatrix(4935) mediatrixIpTelephonySignaling(20) sip(20) sipMIB(1) sipMIBObjects(1) sipUAIfTable(10) sipUAIfEntry(1) sipUAMaximumSessionExpirationDelay(30)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) mediatrix(4935) mediatrixIpTelephonySignaling(20) sip(20) sipMIB(1) sipMIBObjects(1) sipUAIfTable(10) sipUAIfEntry(1) sipUAMaximumSessionExpirationDelay(30)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) mediatrix(4935) mediatrixIpTelephonySignaling(20) sip(20) sipMIB(1) sipMIBObjects(1) sipUAIfTable(10) sipUAIfEntry(1) sipUAMaximumSessionExpirationDelay(30)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) mediatrix(4935) mediatrixIpTelephonySignaling(20) sip(20) sipMIB(1) sipMIBObjects(1) sipUAIfTable(10) sipUAIfEntry(1) sipUAMaximumSessionExpirationDelay(30)}
OID-IRI notation
  • /1/3/6/1/4/1/4935/20/20/1/1/10/1/30
  • /ISO/Identified-Organization/6/1/4/1/4935/20/20/1/1/10/1/30
  • /ISO/3/6/1/4/1/4935/20/20/1/1/10/1/30
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/4935/mediatrixIpTelephonySignaling/sip/sipMIB/sipMIBObjects/sipUAIfTable/sipUAIfEntry/sipUAMaximumSessionExpirationDelay
  • /iso/identified-organization/dod/internet/private/enterprise/mediatrix/mediatrixIpTelephonySignaling/sip/sipMIB/sipMIBObjects/sipUAIfTable/sipUAIfEntry/sipUAMaximumSessionExpirationDelay
  • /iso/identified-organization/dod/internet/private/enterprises/4935/mediatrixIpTelephonySignaling/sip/sipMIB/sipMIBObjects/sipUAIfTable/sipUAIfEntry/sipUAMaximumSessionExpirationDelay
  • /iso/identified-organization/dod/internet/private/enterprises/mediatrix/mediatrixIpTelephonySignaling/sip/sipMIB/sipMIBObjects/sipUAIfTable/sipUAIfEntry/sipUAMaximumSessionExpirationDelay
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/4935/mediatrixIpTelephonySignaling/sip/sipMIB/sipMIBObjects/sipUAIfTable/sipUAIfEntry/sipUAMaximumSessionExpirationDelay
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/mediatrix/mediatrixIpTelephonySignaling/sip/sipMIB/sipMIBObjects/sipUAIfTable/sipUAIfEntry/sipUAMaximumSessionExpirationDelay
  • /iso/identified-organization/dod/internet/private/vendor-objects/4935/mediatrixIpTelephonySignaling/sip/sipMIB/sipMIBObjects/sipUAIfTable/sipUAIfEntry/sipUAMaximumSessionExpirationDelay
  • /iso/identified-organization/dod/internet/private/vendor-objects/mediatrix/mediatrixIpTelephonySignaling/sip/sipMIB/sipMIBObjects/sipUAIfTable/sipUAIfEntry/sipUAMaximumSessionExpirationDelay
  • /iso/org/dod/internet/private/enterprise/4935/mediatrixIpTelephonySignaling/sip/sipMIB/sipMIBObjects/sipUAIfTable/sipUAIfEntry/sipUAMaximumSessionExpirationDelay
  • /iso/org/dod/internet/private/enterprise/mediatrix/mediatrixIpTelephonySignaling/sip/sipMIB/sipMIBObjects/sipUAIfTable/sipUAIfEntry/sipUAMaximumSessionExpirationDelay
  • /iso/org/dod/internet/private/enterprises/4935/mediatrixIpTelephonySignaling/sip/sipMIB/sipMIBObjects/sipUAIfTable/sipUAIfEntry/sipUAMaximumSessionExpirationDelay
  • /iso/org/dod/internet/private/enterprises/mediatrix/mediatrixIpTelephonySignaling/sip/sipMIB/sipMIBObjects/sipUAIfTable/sipUAIfEntry/sipUAMaximumSessionExpirationDelay
  • /iso/org/dod/internet/private/ldap-enterprise/4935/mediatrixIpTelephonySignaling/sip/sipMIB/sipMIBObjects/sipUAIfTable/sipUAIfEntry/sipUAMaximumSessionExpirationDelay
  • /iso/org/dod/internet/private/ldap-enterprise/mediatrix/mediatrixIpTelephonySignaling/sip/sipMIB/sipMIBObjects/sipUAIfTable/sipUAIfEntry/sipUAMaximumSessionExpirationDelay
  • /iso/org/dod/internet/private/vendor-objects/4935/mediatrixIpTelephonySignaling/sip/sipMIB/sipMIBObjects/sipUAIfTable/sipUAIfEntry/sipUAMaximumSessionExpirationDelay
  • /iso/org/dod/internet/private/vendor-objects/mediatrix/mediatrixIpTelephonySignaling/sip/sipMIB/sipMIBObjects/sipUAIfTable/sipUAIfEntry/sipUAMaximumSessionExpirationDelay
  • Additional combinations skipped.

SNMP properties

Value type
Unsigned32
Maximum access defined by MIB
read-write
Status in MIB
current
Default value
3600

Using this OID with SNMP

At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition. The index encoding is not inferred here.

Published row index: ifIndex.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.4935.20.20.1.1.10.1.30

Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

The displayed source records contain one distinct definition. Compare its source records.

sipUAMaximumSessionExpirationDelay OBJECT-TYPE
            SYNTAX  Unsigned32 (0 | 180..3600)
            MAX-ACCESS  read-write
            STATUS  current
            DESCRIPTION "Suggested maximum time for the periodical session refreshes.

                         This value will be reflected in the Session-Expires header.

                         Increasing the maximum will help to reduce network traffic,
                         but will also make 'dead' calls longer to detect.

                         This value is expressed in seconds (s).

                         To disable the session timer service, set the maximum session
                         timer expiration value to 0. However, this is not recommended since
                         it will make 'dead' calls impossible to detect.


                         Questions & Answers
                         ---------------------------------------------

                         Q - What is the session timer extension?

                         A - The session timer extension allows the detection of the premature end of a
                             call caused by a network problem or a peer's failure.

                             The session timer mechanism simply resends an INVITE every n seconds.
                             A sucessful response (200 OK) to this INVITE will signify that the peer
                             is still alive and reachable.  A timeout to this INVITE may mean that there
                             are problems in the signaling path, or that the peer is simply not there
                             anymore.  In that case the call will be shut down using normal SIP means.


                         Q - SDP in Session Timer reINVITEs:

                         A - The reINVITE is sent with the last SDP that was negotiated.
                             Reception of a session timer reinvite should not modify the
                             connection characteristics.


                         Q - Relation between minimum and maximum values:

                         A - A UA that receives a Session-Expires header whose value is smaller than the
                             minimum it is willing to accept will reply a 422 Timer too low to the
                             INVITE and terminate the call.  The phone will not ring.

                             It is up to the caller to decide what to do when it receives a 422 to its
                             INVITE. Mediatrix units will automatically retry the INVITE, with a
                             Session-Expires value equal to the minimum value that the UAS was ready to
                             accept (found in the Min-SE header). This means that the maximum value as set
                             in the Mediatrix unit might not be respected. This has the advantageous effect
                             of establishing the call even if the two endpoints have conflicting values.
                             Mediatrix units will also keep retrying as long as they get 422 answers with
                             different Min-SE values.


                         Q - Who refreshes?

                         A - Re-sending a session timer INVITE is referred to as refreshing the session.
                             Normally, the UAS that receives the INVITE will have the last
                             word on who refreshes.  Mediatrix units will always let the UAC
                             (caller) do the refreshes if the caller supports session timers.
                             In the case the caller does not support session timers, the
                             Mediatrix unit will assume the role of the refresher.


                         Also see sipUAMinimumSessionExpirationDelay."
            DEFVAL { 3600 }
            ::=  {  sipUAIfEntry 30}

Meaning

Descriptions

1 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

Suggested maximum time for the periodical session refreshes. This value will be reflected in the Session-Expires header. Increasing the maximum will help to reduce network traffic, but will also make 'dead' calls longer to detect. This value is expressed in seconds (s). To disable the session timer service, set the maximum session timer expiration value to 0. However, this is not recommended since it will make 'dead' calls impossible to detect. Questions & Answers --------------------------------------------- Q - What is the session timer extension? A - The session timer extension allows the detection of the premature end of a call caused by a network problem or a peer's failure. The session timer mechanism simply resends an INVITE every n seconds. A sucessful response (200 OK) to this INVITE will signify that the peer is still alive and reachable. A timeout to this INVITE may mean that there are problems in the signaling path, or that the peer is simply not there anymore. In that case the call will be shut down using normal SIP means. Q - SDP in Session Timer reINVITEs: A - The reINVITE is sent with the last SDP that was negotiated. Reception of a session timer reinvite should not modify the connection characteristics. Q - Relation between minimum and maximum values: A - A UA that receives a Session-Expires header whose value is smaller than the minimum it is willing to accept will reply a 422 Timer too low to the INVITE and terminate the call. The phone will not ring. It is up to the caller to decide what to do when it receives a 422 to its INVITE. Mediatrix units will automatically retry the INVITE, with a Session-Expires value equal to the minimum value that the UAS was ready to accept (found in the Min-SE header). This means that the maximum value as set in the Mediatrix unit might not be respected. This has the advantageous effect of establishing the call even if the two endpoints have conflicting values. Mediatrix units will also keep retrying as long as they get 422 answers with different Min-SE values. Q - Who refreshes? A - Re-sending a session timer INVITE is referred to as refreshing the session. Normally, the UAS that receives the INVITE will have the last word on who refreshes. Mediatrix units will always let the UAC (caller) do the refreshes if the caller supports session timers. In the case the caller does not support session timers, the Mediatrix unit will assume the role of the refresher. Also see sipUAMinimumSessionExpirationDelay.

Sources for this description

Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)

See 1 matching source record

Evidence

Source records

1 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 1Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 record · 1 source

Description 1

sipUAMaximumSessionExpirationDelay · currentMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 source

Status in source: current.

Names: sipUAMaximumSessionExpirationDelay

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "sipUAMaximumSessionExpirationDelay",
    "OBJECT-TYPE",
    "SYNTAX",
    "Unsigned32",
    "(",
    "0",
    "|",
    "180",
    ".",
    ".",
    "3600",
    ")",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"Suggested maximum time for the periodical session refreshes. This value will be reflected in the Session-Expires header. Increasing the maximum will help to reduce network traffic, but will also make 'dead' calls longer to detect. This value is expressed in seconds (s). To disable the session timer service, set the maximum session timer expiration value to 0. However, this is not recommended since it will make 'dead' calls impossible to detect. Questions & Answers --------------------------------------------- Q - What is the session timer extension? A - The session timer extension allows the detection of the premature end of a call caused by a network problem or a peer's failure. The session timer mechanism simply resends an INVITE every n seconds. A sucessful response (200 OK) to this INVITE will signify that the peer is still alive and reachable. A timeout to this INVITE may mean that there are problems in the signaling path, or that the peer is simply not there anymore. In that case the call will be shut down using normal SIP means. Q - SDP in Session Timer reINVITEs: A - The reINVITE is sent with the last SDP that was negotiated. Reception of a session timer reinvite should not modify the connection characteristics. Q - Relation between minimum and maximum values: A - A UA that receives a Session-Expires header whose value is smaller than the minimum it is willing to accept will reply a 422 Timer too low to the INVITE and terminate the call. The phone will not ring. It is up to the caller to decide what to do when it receives a 422 to its INVITE. Mediatrix units will automatically retry the INVITE, with a Session-Expires value equal to the minimum value that the UAS was ready to accept (found in the Min-SE header). This means that the maximum value as set in the Mediatrix unit might not be respected. This has the advantageous effect of establishing the call even if the two endpoints have conflicting values. Mediatrix units will also keep retrying as long as they get 422 answers with different Min-SE values. Q - Who refreshes? A - Re-sending a session timer INVITE is referred to as refreshing the session. Normally, the UAS that receives the INVITE will have the last word on who refreshes. Mediatrix units will always let the UAC (caller) do the refreshes if the caller supports session timers. In the case the caller does not support session timers, the Mediatrix unit will assume the role of the refresher. Also see sipUAMinimumSessionExpirationDelay.\"",
    "DEFVAL",
    "{",
    "3600",
    "}",
    "::=",
    "{",
    "sipUAIfEntry",
    "30",
    "}"
  ],
  "syntax_tree": [
    [
      "ApplicationSyntax",
      "Unsigned32",
      [
        "integerSubType",
        [
          [
            0
          ],
          [
            180,
            3600
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "Suggested maximum time for the periodical session refreshes. This value will be reflected in the Session-Expires header. Increasing the maximum will help to reduce network traffic, but will also make 'dead' calls longer to detect. This value is expressed in seconds (s). To disable the session timer service, set the maximum session timer expiration value to 0. However, this is not recommended since it will make 'dead' calls impossible to detect. Questions & Answers --------------------------------------------- Q - What is the session timer extension? A - The session timer extension allows the detection of the premature end of a call caused by a network problem or a peer's failure. The session timer mechanism simply resends an INVITE every n seconds. A sucessful response (200 OK) to this INVITE will signify that the peer is still alive and reachable. A timeout to this INVITE may mean that there are problems in the signaling path, or that the peer is simply not there anymore. In that case the call will be shut down using normal SIP means. Q - SDP in Session Timer reINVITEs: A - The reINVITE is sent with the last SDP that was negotiated. Reception of a session timer reinvite should not modify the connection characteristics. Q - Relation between minimum and maximum values: A - A UA that receives a Session-Expires header whose value is smaller than the minimum it is willing to accept will reply a 422 Timer too low to the INVITE and terminate the call. The phone will not ring. It is up to the caller to decide what to do when it receives a 422 to its INVITE. Mediatrix units will automatically retry the INVITE, with a Session-Expires value equal to the minimum value that the UAS was ready to accept (found in the Min-SE header). This means that the maximum value as set in the Mediatrix unit might not be respected. This has the advantageous effect of establishing the call even if the two endpoints have conflicting values. Mediatrix units will also keep retrying as long as they get 422 answers with different Min-SE values. Q - Who refreshes? A - Re-sending a session timer INVITE is referred to as refreshing the session. Normally, the UAS that receives the INVITE will have the last word on who refreshes. Mediatrix units will always let the UAC (caller) do the refreshes if the caller supports session timers. In the case the caller does not support session timers, the Mediatrix unit will assume the role of the refresher. Also see sipUAMinimumSessionExpirationDelay."
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      3600
    ]
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.4935)

Perron Stephane

Siblings (4)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.4935.20.20.1.1.10.1.10 sipUAMainUsername00
1.3.6.1.4.1.4935.20.20.1.1.10.1.15 sipUADisplayName00
1.3.6.1.4.1.4935.20.20.1.1.10.1.20 sipUAOtherAcceptedUsernames00
1.3.6.1.4.1.4935.20.20.1.1.10.1.35 sipUAMinimumSessionExpirationDelay00