Revision as of 09:03, April 13, 2018 by MPandian (talk | contribs) (Created page with "= Agent Availability for Routing = Handling how DNs become available for routing is unique to SIP Cluster. It is different from how DN or agent availability is handled in the...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Agent Availability for Routing

Handling how DNs become available for routing is unique to SIP Cluster. It is different from how DN or agent availability is handled in the regular architecture. There are two different use cases:

  • SIP Phone Agents
  • PSTN Phone Agents

DN State for SIP Phone Agents

Consider the following sample diagram:

File:DNStateSIPPhoneAgents.png

The phones are not registered and the DNs are out of service (OOS).

Important
There are several ports on the SIP Server and each port is dedicated to a specific functionality.
  • SIP port - handling SIP traffic.
  • Default port - is the T-Library port and unlike in the regular architecture, only local activity passes through this port. No events about calls on other SIP Servers are sent through the default port. As a result, URS is only aware of call on that particular SIP Server.
  • T-Controller port - The Stat Server is connected to this port. All calls in the SIP Cluster is passed through this port and as a result, the Stat Server is aware of all calls in different SIP servers in the SIP Cluster.
Comments or questions about this documentation? Contact us for support!