Toolpack monitoring isdn analyzer - Revision history

Lucas Trottier at 17:45, 17 May 2016

2016-05-17T17:45:24Z

Abrassard at 12:02, 5 May 2016

2016-05-05T12:02:08Z

Manon Bélanger: Minor corrections

2016-04-22T12:46:18Z

Minor corrections

Abrassard at 12:04, 22 April 2016

2016-04-22T12:04:54Z

Abrassard: /* Configuring ISDN analyzers in Toolpack Web Portal */

2016-04-22T11:26:43Z

Configuring ISDN analyzers in Toolpack Web Portal

Abrassard: /* Configuring ISDN analyzers in Toolpack Web Portal */

2016-04-21T17:23:12Z

Configuring ISDN analyzers in Toolpack Web Portal

Abrassard: /* Configuring ISDN analyzers in Toolpack Web Portal */

2016-04-21T17:18:29Z

Configuring ISDN analyzers in Toolpack Web Portal

Abrassard: Continuing adding more info to this page

2016-04-21T13:45:29Z

Continuing adding more info to this page

Abrassard: First version of this page

2016-04-21T13:33:50Z

First version of this page

New page

Toolpack ISDN Analyzer is a class that uses Media-only legs and monitoring API to capture HDLC frames from ISDN D-channel timeslot.

The captured ISDN HDLC frames are analyzed, to identify Q.921 and Q.931 frames from the HDLC frames.

Then, ISDN calls are identified from the analyzed Q.931 packets.

=== Capturing each direction of each D-Channel ===
The ISDN analyzer will allocate a pair TDM media-only call legs for each Line service of the ISDN stack that has a D-Channel (primary D-Channel, and backup D-Channel if appropriate).

* The primary Line service of the ISDN stack holds the primary D-channel (timeslot 16 for E1, timeslot 24 for T1/J1).
* For NFAS ISDN stacks, multiple Line services are used. An optional backup D-channel may be present among these line services.

=== Typical ISDN analyzer call flow ===
A typical ISDN analyzer call goes as follows:
* ISDN Q.931 "SETUP" message is detected
** ISDN IEs are analyzed to extract relevant information
*** Call id
*** Channel identification
*** Calling/called numbers
*** And others...
** A new "analyzed" call context is created, bound with the call id
* ISDN Q.931 "PROCEEDING" is detected
** The call changes to "accepted" state
* ISDN Q.931 "ALERTING" is detected
** The call changes to "alerting" state
* ISDN Q.931 "CONNECT" is detected
** The call changes to "answered" state
* ISDN Q.931 "DISCONNECT" is detected
** The call changes to "terminating" state
* ISDN Q.931 "RELEASE" is detected
** The call changes to "terinated" state
* ISDN Q.931 "RELEASE_COMPLETE" is detected
** The call context is destroyed

=== Forwarding analyzed call states to application ===
Each analyzer has been provided a pointer to a "parent" application (a "user") to inform of call state changes.

This "user" is a class that implement the interface ITBCAFAnalyzerUser.

This interface will provide the "user" with the following callbacks from the analyzer, to report new calls and state changes:
* OnAnalyzerCallLegPresent: A new ISDN call was detected
* OnAnalyzerCallLegAccepted: A ISDN call is now "accepted"
* OnAnalyzerCallLegAlerting: A ISDN call is now "alerting" (ringing)
* OnAnalyzerCallLegAnswered: A ISDN call is now "answered"
* OnAnalyzerCallLegTerminating: A ISDN call is now "terminating"
* OnAnalyzerCallLegTerminated: A ISDN call is now terminated
* OnAnalyzerCallLegSuppInfo: Other ISDN message (non call-state affecting) was received

It's up to the user application to decide what should be done with analyzed calls and state changes.

← Older revision		Revision as of 17:45, 17 May 2016
Line 66:		Line 66:

	For more information and step-by-step screen shots of the configuration of ISDN analyzers, please refer to the [[Web Portal Tutorial Guide v2.9]].		For more information and step-by-step screen shots of the configuration of ISDN analyzers, please refer to the [[Web Portal Tutorial Guide v2.9]].
		+
		+	[[Category:Tmonitor_OAM%26P\|ISDN Analyzer]]

← Older revision		Revision as of 12:02, 5 May 2016
Line 64:		Line 64:

	Non-developers that use Toolpack system with built-in Gateway application can also use ISDN analyzers to generate CDR logs or generate corresponding "monitoring" SIP calls to an external monitoring equipment.		Non-developers that use Toolpack system with built-in Gateway application can also use ISDN analyzers to generate CDR logs or generate corresponding "monitoring" SIP calls to an external monitoring equipment.
−
−	~~In the Web Portal, using ISDN analyzers is done by:~~
−	* Enabling "Monitoring" in the "Web Profile"
−	** Click Configurations on the left menu
−	** Select the current configuration for editing
−	** Expand "Web Profile"
−	** Enable "Gateway Application" if not already done
−	** Enable "Monitoring"
−	* Create TDM Line Interfaces and Line Services (by using the "TDM Line Interfaces" section from the left menu)
−	** Make sure the line services "Length" is set to "Monitoring"
−	* Assign the TDM Line Services to a TDM Media NAP (by using the "NAPs" section from the left menu)
−	* Creating "Line Service Pairs"
−	** Click "Line Service Pairs" Section in the left menu
−	** Use "Create Line Service Pair" link to create one or multiple "line service pairs"
−	* Create a "ISDN Analyzer"
−	** Click "Create new ISDN Analyzer" link
−	** Fill-out the required information in the page

	For more information and step-by-step screen shots of the configuration of ISDN analyzers, please refer to the [[Web Portal Tutorial Guide v2.9]].		For more information and step-by-step screen shots of the configuration of ISDN analyzers, please refer to the [[Web Portal Tutorial Guide v2.9]].

@@ Line 7: / Line 7: @@
 == Capturing each direction of each D-Channel ==
-The ISDN analyzer will allocate a pair TDM media-only call legs for each Line service of the ISDN stack that has a D-Channel (primary D-Channel, and backup D-Channel if appropriate).
+The ISDN analyzer will allocate a pair of TDM media-only call legs for each Line service of the ISDN stack that has a D-Channel (primary D-Channel, and backup D-Channel if appropriate).
 * The primary Line service of the ISDN stack holds the primary D-channel (timeslot 16 for E1, timeslot 24 for T1/J1).
@@ Line 30: / Line 30: @@
 ** The call changes to "terminating" state
 * ISDN Q.931 "RELEASE" is detected
-** The call changes to "terinated" state
+** The call changes to "terminated" state
 * ISDN Q.931 "RELEASE_COMPLETE" is detected
 ** The call context is destroyed
@@ Line 61: / Line 61: @@
 == Configuring ISDN analyzers in Toolpack Web Portal ==
-Developers can use ISDN analzyers in their application by using the class CTBCAFAnalyzerIsdn (which uses parameters define by CTBCAFAnalyzerIsdnParams).
+Developers can use ISDN analzyers in their application by using the class CTBCAFAnalyzerIsdn (which uses parameters defined by CTBCAFAnalyzerIsdnParams).
 Non-developers that use Toolpack system with built-in Gateway application can also use ISDN analyzers to generate CDR logs or generate corresponding "monitoring" SIP calls to an external monitoring equipment.

← Older revision		Revision as of 12:04, 22 April 2016
Line 1:		Line 1:
		+	[[Image:Monitoring_isdn_analyzer.png\|thumb\|300px]]
	Toolpack ISDN Analyzer is a class that uses Media-only legs and monitoring API to capture HDLC frames from ISDN D-channel timeslot.		Toolpack ISDN Analyzer is a class that uses Media-only legs and monitoring API to capture HDLC frames from ISDN D-channel timeslot.

@@ Line 72: / Line 72: @@
 ** Enable "Monitoring"
 * Create TDM Line Interfaces and Line Services (by using the "TDM Line Interfaces" section from the left menu)
 * Assign the TDM Line Services to a TDM Media NAP (by using the "NAPs" section from the left menu)
 * Creating "Line Service Pairs"

@@ Line 71: / Line 71: @@
 ** Enable "Gateway Application" if not already done
 ** Enable "Monitoring"
 * Creating "Line Service Pairs"
 ** Click "Line Service Pairs" Section in the left menu

@@ Line 5: / Line 5: @@
 Then, ISDN calls are identified from the analyzed Q.931 packets.
-=== Capturing each direction of each D-Channel ===
+== Capturing each direction of each D-Channel ==
 The ISDN analyzer will allocate a pair TDM media-only call legs for each Line service of the ISDN stack that has a D-Channel (primary D-Channel, and backup D-Channel if appropriate).
@@ Line 11: / Line 11: @@
 * For NFAS ISDN stacks, multiple Line services are used. An optional backup D-channel may be present among these line services.
-=== Typical ISDN analyzer call flow ===
+== Typical ISDN analyzer call flow ==
 A typical ISDN analyzer call goes as follows:
 * ISDN Q.931 "SETUP" message is detected
@@ Line 48: / Line 48: @@
 It's up to the user application to decide what should be done with analyzed calls and state changes.