Product Info
Table Of Contents
- 1.Product Overview
- 2.Change Log
- 3.Model Specification
- 4.Introduction to Configuration Menu
- 5.Access the Device
- 6.Language and Time Setting
- 7.LED Setting
- 8.Volume and Tone Configuration
- 9.Network Setting
- 10.Intercom Call
- 11.Audio& Video Codec Configuration
- 12.Phone Book Configuration
- 13.Relay Setting
- 14.Door Access Schedule Management
- 15.Door Unlock Configuration
- 16.Security
- 17.Monitor and Image
- 18. Logs
- 19.Debug
- 20.Firmware Upgrade
- 21.Backup
- 22.Auto-provisioning
- 23.Integration with Third Party Device
- 24.Password Modification
- 25.System Reboot&Reset
- 26.Abbreviations
- 27. Contact us
Multi Tenant Door Phone Administrator Guide
AKUVOX SMART INTERCOM www.akuvox.com
37
Parameter Set-up:
UDP:select “UDP” for unreliable but very efficient transport layer protocol.
UDP is the default transport protocol.
TCP: select “TCP” for Reliable but less-efficient transport layer protocol.
TLS: select “TLS” for Secured and Reliable transport layer protocol.
DNS-SRV: select “DNS-SRV” to obtain DNS record for specifying the
location of servers. And SRV not only records the server address but also
the server port. Moreover, SRV can also be used to configure the priority
and the weight of the server address.
10.3.Call Session Timer
SIP does not define a survival mechanism for established sessions. Although
the user agent can infer whether the session has timed out through a
session-specific mechanism, but the proxy server do not have this
mechanism. In this way. The proxy server sometimes cannot infer whether
the session is still active. For example, when a user agent fails to send a BYE
message at the end of the session, or the BYE message is lost due to
network problems, the proxy server will not know that the session has ended.
In this case, the proxy server will keep the call status and cannot know when
the call status information is invalid. To solve the problem, RFC4028 defines
a survival mechanism for SIP sessions. The user agent or proxy server
periodically sends re-INVITE or UPDATE requests to keep the session active.
The interval of session update requests is determined by its defined
negotiation mechanism. Assuming that no session update request is
received within the interval, the session is deemed to have been terminated.
To do the configuration on the web Account > Advanced > Session Timer
interface.