Dialogic DMG1008MTLDNI User Manual download pdf (Page 16)

7. Troubleshooting

7.1. Important Debugging Tools

• Ethereal/Wireshark – Used to view and analyze the network captures provided by the

Dialogic

gateway diagnostic firmware.

• Adobe Audition -- Used to review and analyze the audio extracted from the network captures

to troubleshoot any audio-related issues.

7.2. Important Gateway Trace Masks

These keys are helpful during troubleshooting scenarios and should be considered keys to activate by

default for all troubleshooting cases.

• voip prot and voip code – this allows the collection of all SIP-related messages as they

are sent from and received by the gateway. This data is important in cases where you feel that

the gateway is not able to communicate properly with the messaging server.

• tel event and tel code – This allows the collection of circuit-side activity of the emulated

station set, such as display updates, key presses, light transitions and hook state changes.

This data is important in the following scenarios:

o Call control problems (dropped calls, failing transfers, etc…)

o Integration problems (incorrect mailbox placement, missed auto-attendant greetings

etc…)

These keys are helpful during specific issues and can be enabled for targeted troubleshooting of very

specific cases. Activation of these keys may generate large amounts of data on busy systems and

increase the size of the collected log files, but should not harm system performance.

• dspcpi (all keys) – This allows the collection of tone-related data. This data is helpful in cases

where you think you have problems detecting 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. This data is important in the following scenarios:

o Failing transfers

o Failing outbound calls (play to phone)

o Dropped calls (callers cut off while leaving messages, etc…)

•

adept (all keys) – This allows the collection of rule-parsing data. This data is required in the

troubleshooting of integration-related issues.

NOTE: Turning on all traces is not recommended. Doing this floods the debug stream with significant

amounts of information that can cause delays in determining the root cause of a problem.

1 2 ... 11 12 13 14 15 16 17 18 19 20 21 22

No comments

Dialogic DMG1008MTLDNI User Manual Page 16