Dialogic 2000 Series Manuel d'utilisateur télécharger pdf (Page 11)

6.2 Important Gateway Trace Masks

These keys are helpful during all 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 all circuit-side activity of the

emulated station set such as display updates, key presses, light transitions and hook

state changes. This data is very 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…)

• teldrv prot – This allows the collection of all ISDN messages both transmitted and

received on the gateways front-end interface. This data is very 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…)

• RouteTable (all keys) – This allows you to look inside the routing table engine

and see how matching rules and CPID manipulation rules work with respect to your call.

This data is very important in the following scenarios:

o Call routing problem (reaching the incorrect IBM Lotus Sametime Unified

Telephony client or no client at all, etc…)

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 ... 6 7 8 9 10 11 12

Pas de commentaire

Dialogic 2000 Series Manuel d'utilisateur Page 11