Dialogic 2000 Series Note d'installation et de configuration - Page 17
Parcourez en ligne ou téléchargez le pdf Note d'installation et de configuration pour {nom_de_la_catégorie} Dialogic 2000 Series. Dialogic 2000 Series 17 pages. Media gateway
Également pour Dialogic 2000 Series : Manuel de démarrage rapide (4 pages)
Imprimer la page
6.
Troubleshooting
Debugging Tools
6.1
•
Ethereal/Wireshark – Used to view and analyze the network captures provided by the DMG2000
diagnostic firmware.
•
Adobe Audition – Used to review and analyze the audio extracted from the network captures in order to
troubleshoot any audio-related issues.
7. Gateway Trace Masks
These keys are helpful during troubleshooting scenarios and should be considered as keys to activate by default
for all troubleshooting.
•
voip prot and voip code – These allow the collection of all SIP-related messages as they are sent
from and received by the DMG2000. Such data can be important, as in cases where you believe the
DMG2000 is unable to communicate properly with the messaging server.
•
tel event and tel code – These allow the collection of all circuit-side activity. Such data can be
important, such as when addressing the following scenarios:
o
Call control problems (dropped calls, failing transfers, etc.)
o
Integration problems (incorrect mailbox placement, missed auto-attendant greetings etc.)
•
teldrv prot – This allows the collection of all ISDN messages both transmitted and received on the
DMG2000 front end interface. This data can be very important, such as when addressing the following
scenarios:
o
Call control problems (dropped calls, failing transfers, etc.)
o
Integration problems (incorrect mailbox placement, missed auto-attendant greetings etc.)
•
RouteTable (all keys) – This will allow the collection of events around the parsing of the dial
plan. This will enable the user to see the calling and called numbers being sent to the gateway and see
how they being changed by the dial plan configuration.
The following keys are helpful when confronting certain issues and can be enabled for targeted troubleshooting
of specific problems. Activating these keys may generate large amounts of data on busy systems and increase
the size of the collected log files, but doing so will not harm system performance.
•
dspif (all keys) – This allows the collection of tone related data. Such data is very helpful in cases
where you think you have problems relating to detection specific tones that should be, should not be, or
are expected to be present at specific times during the call. If you do not suspect a tone related issue,
this key may be left disabled.
NOTE: Turning on all traces is not recommended. Doing so floods the debug stream with significant amounts of
information that can cause delays in determining the root cause of a problem.
Additional information regarding the Dialogic
following link:
http://www.dialogic.com/support/helpweb/mg/default.aspx
®
Dialogic
2000 Media Gateway Series Installation and Configuration Note
®
2000 Media Gateway Series (DMG2000) can be found at the
17