1 / 90

Unity Traces & Troubleshooting

Unity Traces & Troubleshooting. Michael Hollowell CCIE #4114 (Oct 4, 1998) UCBU – Senior Escalation Engineer rev: 06/06/11. Agenda. The playing field. Setting the traces. Customizing the traces. Gathering everything up. Diagnotistic Examples Q&A. On-line Troubleshooting Guides.

jalila
Télécharger la présentation

Unity Traces & Troubleshooting

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Unity Traces & Troubleshooting Michael HollowellCCIE #4114 (Oct 4, 1998) UCBU – Senior Escalation Engineerrev: 06/06/11

  2. Agenda • The playing field. • Setting the traces. • Customizing the traces. • Gathering everything up. • Diagnotistic Examples • Q&A.

  3. On-line Troubleshooting Guides • Unity trouble shooting Guides • http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_troubleshooting_guides_list.html • 5.0 Trouble shooting Guide • http://www.cisco.com/en/US/docs/voice_ip_comm/unity/5x/troubleshooting/guide/ex/5xcutsgex.html

  4. The Playing Field – Ways to Trouble shoot • Windows System / Application Event Log • Diagnostic Logging via the Unity Diagnostic Tool (UDT) • Port Status Monitor (2.0+) • GUSI (2.0 +) • Low Level Debugging • Miscellaneous Logs

  5. System / Application Log – Gathering Apps • Eventvwr.exe -> Save Log File As... • - .evt (GMT adjusted time) • - .csv (current server time) • GUSI (Gather Unity System Info. 2.x+) • UDT -> Gather Standard Logs - AvCsMGr, App, & Sys Logs Select Logs*Over a specified Time Frame *Option to export App & Sys to CSV is there, by default it is not included

  6. Reading System/Application Logs • EVT - eventvwr -> open log file…Should be opened on a Unity server of the same version in order to decode events properly.* • - Unity Diagnostic Viewer • CSV • - Excel, Notepad, Word, etc. * timestamps might not match Diags

  7. UDT Traces - Gathering Correct way: Using UDT –> Gather log Files Incorrect Way: Taking them dircectly from the \commserver\logs directory unless otherwise specified.

  8. This is your log… This is your log formatted • Plucked from the \commserver\logs directory: • 16:38:52:094,AvDiagnostics_MC,1225,3760,-1,,Notifier,24,John Doe,0,Text(0x1),Urgent Only 16:38:52:093,AvDiagnostics_MC,1221,5784,-1,,Notifier,20,0x5e90001,32,Any 16:38:52:125,AvDiagnostics_MC,1258,3760,-1,,Notifier,16,Queued,John Doe.jdoe@local.com • Gathered from the UDT*: • 16:38:52:094 (AvDiagnostics_MC,1225,Notifier,24) [Thread 3760] John Doe has 0 messages of type Text(0x1) Urgent Only 16:38:52:093 (AvDiagnostics_MC,1221,Notifier,20) [Thread 5784] Ticket 0x5e90001 granted for resource 32 (requested Any) 16:38:52:125 (AvDiagnostics_MC,1258,Notifier,16) [Thread 3760] Queued SMTP task for mailuser=John Doe, addr#=jdoe@local.com. * You can format the unformatted logs by placing them into the \commserver\logs directory of the same Unity version from which the logs were pulled from and then use UDT to gather/format them.

  9. Port Status Monitor (2.x +) • Replaced the Original Port Status Monitor (PSM) • Allows you to monitor the voiceports in real time • Unity version 4.2 and later • Latest version 2.0.2.4 • Easiest tool for watching MWI activity and User interaction. • Training Video: • ftp://ftpeng.cisco.com/lindborg/Unity42/NEWPSM.exe

  10. GUSI (2.0 +) • Gather Unity System Information • Current Version 2.0.4 • Key New Feature within 2.x - Configuration Conformance Checking • Always check with ciscounitytools.com for latest version • Online help file: • http://ciscounitytools.com/Applications/Unity/GUSI/Help/GatherUnitySystemInfo.htm

  11. Debugging • Advanced Use Only • Windbg.exe • - May require Unity, Microsoft, or other 3rd party Symbols • - Best to get a memory dump • Use “!analyze –v” • dbgview.exe • - VMO client issues

  12. Miscellaneous Logs • \<os install>\system32\logfiles\... • …\w3svc1\ex<#>.log …\HTTPERR\httperr1.log • (www logs enable by default : PCA, SAweb) • …\smtpsvc1 (VPIM, Bridge, Text Paging, etc.) • (must enable first on the protocol) • \<os install>\KB*.log (list of all KBs installed on the system) • (can also use add/remove programs)

  13. Agenda • The playing field. • Setting the traces. • Customizing the traces. • Gathering everything up. • Diagnotistic Examples • Q&A.

  14. Unity Architecture

  15. Unity ArchitectureFor More Information … A lot more detail about the architecture diagram, with information about the Unity components and processes in it, can be found in these resources: • Unity Architecture Overview 4.0(3) • Cisco Unity Deployment and Solutions Guide We’re not going to go into quite that level of detail in this presentation, but we’ll do a couple of process walkthroughs to get an idea of how to understand and apply the architecture diagram.

  16. The Complexity of Unity DiagsMultiple Log Managers AvCsMgr process Log Manager diag_AvCsMgr_20060126_220003.txt AvDSAD process Log Manager diag_AvDSAD_20060126_220003.txt Each Unity process runs its own copy of the log manager, and creates its own diagnostic file.

  17. The Complexity of Unity DiagsComponent vs. Process Example AvCsMgr process MIU Component Log Manager diag_AvCsMgr_20060126_220003.txt Example: Gathering MIU Traces • Set MIU Traces in Unity Diagnostic Tool • Reproduce Behavior • Use UDT to gather AvCsMgrdiag file, because the MIU component lives in the AvCsMgr process

  18. The Complexity of Unity DiagsSame Component, Different Processes AvCsMgr process Some components run under more than one process. For example, you can find output from DOH traces in diag files from each of several Unity processes. DOH component CsBridgeConnector process DOH component AvUmrSyncSvr process DOH component

  19. The Complexity of Unity DiagsSome Diag Files Are Outside the UDT UDT AvCsMgr process Log Manager diag_AvCsMgr_20060126_220003.txt Unity Setup tempu.log PWResults.html OsqlDump_

  20. \Commserver\Log File Naming Convention diag_AvCsMgr_20060126_220003.txt Diag = Diagnostic type AvCsMgr = LogMgr owning Process 20060126 = Date using YYYYMMDD 220003 = Time using HHMMSS Where the Date/Time is when the log file was CREATED.

  21. \commserver\logData Files Take a good look at the Commserver\Logs directory, and you’ll notice some files obviously related to Unity components, that start with “data.” These files are actually used to generate Unity reports, and are not a core part of the Unity diag functionality. They’re worth mentioning here, because people sometimes mistakenly gather them directly from the Commserver\Logs directory, thinking they are Unity diags.

  22. UDT – MACRO / MICRO • MACRO (as of 5.0.1) • MICRO (most components broken out) AMIS Problems AMIS Message Traces Delays in Answering Calls Call Flow Diagnostics Conversation State Traces Bridge Directory Sync Traces VPIM Directory Sync Traces Directory Monitor Traces Call Control (Miu) Traces Traces for MWI Problems Traces for other notification problems Skinny TSP traces Unity Startup Media (Wave) Traces 1 - High Media (Wave) Traces 2 - Medium Media (Wave) Traces 3 - Low Secure Messaging Traces Text to Speech (TTS) Traces

  23. Setting the Traces : Default Recommendations • Look for a relevant MACRO trace • Always include : • - Conversation State Traces • - Call Flow Diagnostics • Additional Traces to focus on specific problem : • - AvRdbSvr 11 (SQL query Generation) • - DOH 10+ & MALEx 10+ (Exchange Mailbox issues) • - notescommon 10+ & MALLn 10+ (Domino Issues) • - AvSaDbConn 10+ (SAWeb add/modify/delete issues) • - NodeMgr 10+ (Failover issues) - DSAD 10+ (Local Unity Objects to/from AD Sync) - DSGlobalCatalog 10+ (Object not local to Unity to/from AD sync) - DSDomino 10+ (Unity/from to Domino Sync)

  24. Agenda • The playing field. • Setting the traces. • Customizing the traces. • Gathering everything up. • Diagnotistic Examples • Q&A.

  25. Customizing Traces – Personal Macro • Place/Review them at :\commserver\utilities\unitydiagnostictool\udtxml\ • Filename MUST start with H. • Filename MUST have an .xml extension. • File contents MUST be in XML format. • Example* : HTTAC-PhoneView.xml *Complete PhoneView Trace in Notes Section

  26. Customized Macro Trace - Example • <?xml version="1.0"?> • <GA NAME="Phone View"> • <DESCRIPTION>These traces help you troubleshoot Cisco Unity Phone View Issues.</DESCRIPTION> • <TRACE NAME="For TAPI and SIP"> • <DESCRIPTION>These traces help you troubleshoot Cisco Unity Phone View Issues.</DESCRIPTION> • <DIAG GROUP="CDE"> • <FLAG ID="01" /> • <FLAG ID="20" /> • <FLAG ID="21" /> • <FLAG ID="22" /> • <FLAG ID="23" /> • </DIAG> • </TRACE> • </GA>

  27. Agenda • The playing field. • Setting the traces. • Customizing the traces. • Gathering everything up. • Diagnotistic Examples • Q&A.

  28. UDT – Gathering Logs • If not sure, gather all over a time frame • - Note Time on the Unity Server • - Recreate the Issue • - Set start time to be the time from above • - Gather for the default 1 hour • Preferred : • - Press Start New Log File • - Recreate the Issue • - Press Start New Log File • - Gather ‘Select Logs’ grab the second one to bottom

  29. Addition Information to include • GUSI (Grab latest version available on unitytools.com) • Unity Time when the issue was occurring. • Affected Subscriber, Distribution lists, DC/GC Server, Exchange/Domino Servers, Port the call arrived on, etc. • Background information (step by step of what was recreated) • Working* vs. Non-working Trace *working can be a lab recreate using your own server mocking up the customers environment if working is not available on the customers server.

  30. Quirky things to gather on the Unity Server • Skinny shows up in SvcHost starting Unity 4.x and later. • Permission Wizard:<logged in acct>\temp\PWResults.html • Unexpected Notes terminations:<lotus notes>\Data\IBM_Technical_Support (zip up entire directory)

  31. Personal Communication Assistant • Setup • \<logged in account>\temp\cscoserv_*.log\ • Application Logging • \CommServer\Cscoserv\Tomcat\Logs\ciscopca*.txt • \<OS install>\system32\logfiles\w3svc1\ex<#>.log

  32. Unity Upgrade Failures • 5.x and later • \commserver\logs\tempu_<date/time>.log • \<logged in account>\temp\syscheck.log • \commserver\logs\osqldump_<date/time>.txt • \commserver\logs\sqlsync_<#>.txt • \commserver\logs\cfgCUApp_<date/time>.txt • \Commserver\Logs\diag_Install_<date/time>.txt • 4.x and earlier • \<logged in account>\temp\tempu.log • \<logged in account>\temp\syscheck.log • \commserver\logs\osqldump_<date/time>.txt • \commserver\logs\sqlsync_<#>.txt • \commserver\logs\cfgCUApp_<date/time>.txt • \Commserver\Logs\diag_Install_<date/time>.txt

  33. Exchange Server – Miscellaneous Logs • Application and System Event Logs • Message Tracking (if delivery related – must be enabled) • - <Exchange Server Path>\Web.log • SMTP Logs (if routing off the local exchange server – must be enabled) • IVC logs (Voice Connector – need to bump up the level) • - <Exchange Server Path>\VoiceGateway\logFiles • - GwIvc_<date>.log (diags) • - GwIvc_perf_<date>.log (perfs)

  34. Domino – Miscellaneous Logs • Log.nsf • - Tip : Create a blank NSF based on the log.ntf template and cut/paste the relevant timeframe into it. • - Has to be viewed via Notes client • - 3 Categories : Mail Routing, Replication, & Misc. Events • Message Tracking - <domino>\data\mtdata\mtstore.nsf - Has to be viewed via Notes client

  35. Agenda • The playing field. • Setting the traces. • Customizing the traces. • Gathering everything up. • Diagnotistic Examples • Q&A.

  36. Some General Techniques for Reading Diag Files • Use Find to look for strings seen elsewhere • Use Findstr to filter • Working vs. Non-working • Pay attention to timing • Beware error reports by themselves • Assemble a story out the diag lines.

  37. Diagnostic Example – Basic Call Flow • Background: • - Caller 8015 leaves a voicemail for 8005 • Traces Enabled: (All found within UDT Macro) • All Call Flow Diag- Conv State Traces- Call Control (Miu) Traces- Traces for MWI problems- SKinny TSP Traces Traces Gathered: - AvCsMgr (diag_AvCsMgr_20110106_220000_fmtd.txt)- SvcHost (diag_svchost_20110106_220000_fmtd.txt)

  38. Diagnostic Example – Basic Call Flow • Unity Diagnostic Tool • - Found in Tools Depot on the Unity Sever

  39. Diagnostic Example – Basic Call Flow • Last File listed within each tree is the most current diagnostic file

  40. Diagnostic Example – Basic Call Flow • Navigating the diag Files • - Start backwards search starting from the bottom of the file (since this is the most current information) • - Our example, a voicemail is being left for Extension 8005, so we will search for “8005” 10:59:25:772 **NOT FORMATTED**,AvDiagnostics_MC,162,4156,-1,,SkinnyTSP,12,[Thread 0x0000103C] [Device 6]StationCallInfoV2Message: Extracted CallerID='8015' () CalledID='8005' () RedirectReason=2=RfrCallFwdRNA LastRedirectingID='8005' () LastRedirectReason=2=RfrCallFwdRNA - To isolate this call only, we can use the [Device 6] identifier

  41. Diagnostic Example – Basic Call Flow • To extract this one call flow use “Wingrep” or windows “find” • Example (from the windows CLI): • find "[Device 6]" .\diag_svchost_20110106_220000_fmtd.txt > .\call.txt • This will parse out all occurrences of [Device 6] and place them into a file named “call.txt”

  42. Diagnostic Example – Basic Call Flow 10:59:25:771 **NOT FORMATTED**,AvDiagnostics_MC,162,4156,-1,,SkinnyTSP,12,[Thread 0x0000103C] [Device 6] Receive StationSetRingerMessage (20 bytes) ringMode=2=StationInsideRing ringDuration=1=StationNormalRing lineInstance=1 callReference=26043776 … 10:59:25:771 **NOT FORMATTED**,AvDiagnostics_MC,162,4156,-1,,SkinnyTSP,24,[Thread 0x0000103C] [Device 6] CAvSkinnyCallStatus::SignalCallState: callState=4=TsRingIn callReference=26043776 … 10:59:25:959 **NOT FORMATTED**,AvDiagnostics_MC,162,4156,-1,,SkinnyTSP,24,[Thread 0x0000103C] [Device 6] CAvSkinnyCallStatus::SignalCallState: callState=1=TsOffHook callReference=26043776 … 10:59:25:960 **NOT FORMATTED**,AvDiagnostics_MC,162,4156,-1,,SkinnyTSP,24,[Thread 0x0000103C] [Device 6] CAvSkinnyCallStatus::SignalCallState: callState=5=TsConnected callReference=26043776 … 10:59:52:162 **NOT FORMATTED**,AvDiagnostics_MC,162,4156,-1,,SkinnyTSP,12,[Thread 0x0000103C] [Device 6] Receive StationCallStateMessage (28 bytes) callState=2=TsOnHook lineInstance=1 callReference=26043776 privacy=0=PrivacyNone precedence=[precedenceLv=4 precedenceDm=0] Callstates : 4=TsRingIn -> 1=TsOffHook -> 5=TsConnected -> 2=TsOnHook

  43. Diagnostic Example – Basic Call Flow • To find various call flows within AvCsMgr • Example • find " CallInfo" .\diag_AvCsMgr_20110106_220000_fmtd.txt > callinfo.txt • (Note there is a space after the first double quote before the callinfo word) 10:58:50:460 (AvDiagnostics_MC,2195,MiuGeneral,12) [Thread 4212] [Port 1] [B259F01316B443F58D74C607FDFF2976] [Thread 0x00001074] [Port 1] INTEGRATION CallInfo received (Origin Internal | Reason FwdNoAnswer | CallerID 8015 | CalledID 8005 | RedirectingID 8005). 10:59:25:772 (AvDiagnostics_MC,2195,MiuGeneral,12) [Thread 4220] [Port 1] [8985A5D73D924EFABBE5CEAB14E778BA] [Thread 0x0000107C] [Port 1] INTEGRATION CallInfo received (Origin Internal | Reason FwdNoAnswer | CallerID 8015 | CalledID 8005 | RedirectingID 8005). Since only two calls were found we will have to isolate the call in question via the time the call came in found via monitoring PSM or through SVCHost diag (in this case - 10:59:25 time frame). *** To isolate, use the Call GUID : [8985A5D73D924EFABBE5CEAB14E778BA]

  44. Diagnostic Example – Basic Call Flow • Using the unique call guid, we can isolate a certain call within the AvCsMgr Diag: • Example: • find “[8985A5D73D924EFABBE5CEAB14E778BA]” .\diag_AvCsMgr_20110106_220000_fmtd.txt > callguid.txt

  45. Diagnostic Example – Basic Call Flow • Call routing properly 10:59:25:772 (AvDiagnostics_MC,642,RulerDomain,11) [Thread 4220] [Port 1] [8985A5D73D924EFABBE5CEAB14E778BA] CRulerDomain::FindFirstTrueRule: StartIndex=[0] 10:59:25:771 (AvDiagnostics_MC,1316,RulerDomain,11) [Thread 4220] [Port 1] [8985A5D73D924EFABBE5CEAB14E778BA] Evaluating Rule 'Attempt Forward to Greeting' in Domain 'Routing'. 10:59:25:772 (AvDiagnostics_MC,1319,RulerDomain,11) [Thread 4220] [Port 1] [8985A5D73D924EFABBE5CEAB14E778BA] Expression 'Reason IN 2 4 8 64' evaluates to true. 10:59:25:771 (AvDiagnostics_MC,1317,RulerDomain,11) [Thread 4220] [Port 1] [8985A5D73D924EFABBE5CEAB14E778BA] Rule 'Attempt Forward to Greeting' in Domain 'Routing' evaluated to TRUE. 10:59:25:772 (AvDiagnostics_MC,642,RulerDomain,11) [Thread 4220] [Port 1] [8985A5D73D924EFABBE5CEAB14E778BA] CRulerDomain::FindFirstTrueRule: Rule evaluates to TRUE; Index=[1] 10:59:25:771 (AvDiagnostics_MC,1325,RulerDomain,11) [Thread 4220] [Port 1] [8985A5D73D924EFABBE5CEAB14E778BA] First Rule to evaluate to TRUE in Domain 'Routing' is 'Attempt Forward to Greeting': Action='AttemptForward'. Call Routing is decided upon based on whether the call was:- “Direct” call into Unity- “Forwarded” call into Unity “Attempt Forward to Greeting” is one of the Unity’s default “Forwarded” rules

  46. Diagnostic Example – Basic Call Flow • Bad Forwarded routing rule 12:05:40:055 (AvDiagnostics_MC,642,RulerDomain,11) [Thread 4220] [Port 1] [F12392F48B7E4A55AFDCEE298462574A] CRulerDomain::FindFirstTrueRule: StartIndex=[0] 12:05:40:056 (AvDiagnostics_MC,1316,RulerDomain,11) [Thread 4220] [Port 1] [F12392F48B7E4A55AFDCEE298462574A] Evaluating Rule 'New-Rule' in Domain 'Routing'. 12:05:40:055 (AvDiagnostics_MC,1319,RulerDomain,11) [Thread 4220] [Port 1] [F12392F48B7E4A55AFDCEE298462574A] Expression 'DialedNumber == 8005' evaluates to true. 12:05:40:056 (AvDiagnostics_MC,1319,RulerDomain,11) [Thread 4220] [Port 1] [F12392F48B7E4A55AFDCEE298462574A] Expression 'Reason IN 2 4 8' evaluates to true. 12:05:40:055 (AvDiagnostics_MC,1317,RulerDomain,11) [Thread 4220] [Port 1] [F12392F48B7E4A55AFDCEE298462574A] Rule 'New-Rule' in Domain 'Routing' evaluated to TRUE. 12:05:40:056 (AvDiagnostics_MC,642,RulerDomain,11) [Thread 4220] [Port 1] [F12392F48B7E4A55AFDCEE298462574A] CRulerDomain::FindFirstTrueRule: Rule evaluates to TRUE; Index=[0] 12:05:40:055 (AvDiagnostics_MC,1325,RulerDomain,11) [Thread 4220] [Port 1] [F12392F48B7E4A55AFDCEE298462574A] First Rule to evaluate to TRUE in Domain 'Routing' is 'New-Rule': Action='AD'

  47. Diagnostic Example – Basic Call Flow “New-rule” was mistakenly added to Unity causing “Forwarded” calls to subscriber 8005 to go to a “Directory Handler” rather than the default “Attempt Forward”. This will only affect “Forwarded” calls into this subscriber and not a direct call from that subscriber. Rules are evaluated from top to bottom, first “True” match will be executed.

  48. Diagnostic Example – Basic Call Flow • Prompt Playout 10:59:26:444 (AvDiagnostics_MC,1394,PhraseServer,11) [Thread 4220] [Port 1] [8985A5D73D924EFABBE5CEAB14E778BA] [10:59:26] PhraseID - SystemStandard 10:59:26:443 (AvDiagnostics_MC,1394,PhraseServer,11) [Thread 4220] [Port 1] [8985A5D73D924EFABBE5CEAB14E778BA] Prompt Name - C:\CommServer\Localize\Prompts\ENU\G711\AvPHGreet\AvPHGreetENU021.wav 10:59:26:444 (AvDiagnostics_MC,1394,PhraseServer,11) [Thread 4220] [Port 1] [8985A5D73D924EFABBE5CEAB14E778BA] Prompt Name - C:\CommServer\Localize\Prompts\ENU\G711\AvCommon\Numbers\AvCommonENU208.wav 10:59:26:443 (AvDiagnostics_MC,1394,PhraseServer,11) [Thread 4220] [Port 1] [8985A5D73D924EFABBE5CEAB14E778BA] Prompt Name - C:\CommServer\Localize\Prompts\ENU\G711\AvCommon\Numbers\AvCommonENU200.wav 10:59:26:444 (AvDiagnostics_MC,1394,PhraseServer,11) [Thread 4220] [Port 1] [8985A5D73D924EFABBE5CEAB14E778BA] Prompt Name - C:\CommServer\Localize\Prompts\ENU\G711\AvCommon\Numbers\AvCommonENU200.wav 10:59:26:443 (AvDiagnostics_MC,1394,PhraseServer,11) [Thread 4220] [Port 1] [8985A5D73D924EFABBE5CEAB14E778BA] Prompt Name - C:\CommServer\Localize\Prompts\ENU\G711\AvCommon\Numbers\AvCommonENU052.wav 10:59:26:444 (AvDiagnostics_MC,1394,PhraseServer,11) [Thread 4220] [Port 1] [8985A5D73D924EFABBE5CEAB14E778BA] Prompt Name - C:\CommServer\Localize\Prompts\ENU\G711\AvPHGreet\AvPHGreetENU019.wav 10:59:26:443 (AvDiagnostics_MC,1394,PhraseServer,11) [Thread 4220] [Port 1] [8985A5D73D924EFABBE5CEAB14E778BA] Prompt Name - C:\CommServer\Localize\Prompts\ENU\G711\AvPHGreet\AvPHGreetENU016.wav prompts.ini file can be viewed in each directory for the text representation of each wav file [AvPHGreetENU019] Text=is not available. [AvPHGreetENU016] Text=Record your message at the tone. When you are finished, hang-up or hold for more options. [AvPHGreetENU021] Text=Extension... [AvCommonENU208] Text=eight (trailing) [AvCommonENU200] Text=zero (trailing) [AvCommonENU052] Text=five (leading)

  49. Diagnostic Example – Basic Call Flow • Enter / Leaving Functions 10:59:36:600 (**,-1,Conversation,1) [Thread 4220] [Port 1] [8985A5D73D924EFABBE5CEAB14E778BA] [Port 1] GetMailBoxStatusbyMailuser: Entering function File: E:\views\TBM17_view\un_Conv1\Scripted\ConvSub\PHGreeting.cpp Line: 1229 10:59:36:724 (AvDiagnostics_MC,1462,MALEx,12) [Thread 4220] [Port 1] [8985A5D73D924EFABBE5CEAB14E778BA] Mailbox - Logon cn=user 8015 cn=Recipients ou=Exchange Administrative Group (FYDIBOHF23SPDLT) o=EFT 85 on - Thread: 0000107CH Instance: 029531B8H 10:59:36:740 (**,-1,Conversation,12) [Thread 4220] [Port 1] [8985A5D73D924EFABBE5CEAB14E778BA] [Port 1] GetMailBoxStatusbyMailuser: spMailUser->get_PrimaryMailbox(spMailbox.put()) returned: 0x00000000 File: E:\views\TBM17_view\un_Conv1\Scripted\ConvSub\PHGreeting.cpp Line: 1239 10:59:36:756 (AvDiagnostics_MC,1440,MALEx,12) [Thread 4220] [Port 1] [8985A5D73D924EFABBE5CEAB14E778BA] Diagnostic: Mailbox size is 47.00 KB 10:59:36:757 (AvDiagnostics_MC,1440,MALEx,12) [Thread 4220] [Port 1] [8985A5D73D924EFABBE5CEAB14E778BA] Diagnostic: Mailbox Send Receive Limit is 2411520.00K 10:59:36:756 (AvDiagnostics_MC,1440,MALEx,12) [Thread 4220] [Port 1] [8985A5D73D924EFABBE5CEAB14E778BA] Diagnostic: Mailbox Send Limit is 2097152.00K 10:59:36:757 (AvDiagnostics_MC,1440,MALEx,12) [Thread 4220] [Port 1] [8985A5D73D924EFABBE5CEAB14E778BA] Diagnostic: Mailbox Warning Limit is 1991680.00K 10:59:36:757 (**,-1,Conversation,1) [Thread 4220] [Port 1] [8985A5D73D924EFABBE5CEAB14E778BA] [Port 1] GetMailBoxStatusbyMailuser: Leaving function hr=0x00000000 File: E:\views\TBM17_view\un_Conv1\Scripted\ConvSub\PHGreeting.cpp Line: 1274 hr=0x00000000 means successful

  50. Diagnostic Example – Basic Call Flow 10:59:26:335 (AvDiagnostics_MC,1394,CDE,10) [Thread 4220] [Port 1] [8985A5D73D924EFABBE5CEAB14E778BA] Port [1] Next state is [c:\commserver\localize\scripts\phgreeting.cde!Root] 10:59:26:366 (AvDiagnostics_MC,1394,CDE,10) [Thread 4220] [Port 1] [8985A5D73D924EFABBE5CEAB14E778BA] Port [1] Next state is [c:\commserver\localize\scripts\phgreeting.cde!PlayGreeting] 10:59:36:771 (AvDiagnostics_MC,1394,CDE,10) [Thread 4220] [Port 1] [8985A5D73D924EFABBE5CEAB14E778BA] Port [1] Next state is [c:\commserver\localize\scripts\phgreeting.cde!PlayPostGreetingRecording] 10:59:36:788 (AvDiagnostics_MC,1394,CDE,10) [Thread 4220] [Port 1] [8985A5D73D924EFABBE5CEAB14E778BA] Port [1] Next state is [c:\commserver\localize\scripts\phgreeting.cde!Java_PreRecord] 10:59:36:787 (AvDiagnostics_MC,1394,CDE,10) [Thread 4220] [Port 1] [8985A5D73D924EFABBE5CEAB14E778BA] Port [1] Next state is [c:\commserver\localize\scripts\phgreeting.cde!Play_PreRecordMsg] 10:59:36:787 (AvDiagnostics_MC,1394,CDE,10) [Thread 4220] [Port 1] [8985A5D73D924EFABBE5CEAB14E778BA] Port [1] Next state is [c:\commserver\localize\scripts\phgreeting.cde!Java_RecordMsg] 10:59:36:788 (AvDiagnostics_MC,1394,CDE,10) [Thread 4220] [Port 1] [8985A5D73D924EFABBE5CEAB14E778BA] Port [1] Next state is [c:\commserver\localize\scripts\phgreeting.cde!RecordMsg] 10:59:44:663 (AvDiagnostics_MC,1394,CDE,10) [Thread 4220] [Port 1] [8985A5D73D924EFABBE5CEAB14E778BA] Port [1] Next state is [c:\commserver\localize\scripts\phgreeting.cde!Java_RunEditMsg] 10:59:44:662 (AvDiagnostics_MC,1394,CDE,10) [Thread 4220] [Port 1] [8985A5D73D924EFABBE5CEAB14E778BA] Port [1] Next state is [c:\commserver\localize\scripts\phgreeting.cde!Play_RunEditMsg] 10:59:44:662 (AvDiagnostics_MC,1394,CDE,10) [Thread 4220] [Port 1] [8985A5D73D924EFABBE5CEAB14E778BA] Port [1] Next state is [c:\commserver\localize\scripts\phgreeting.cde!RunEditMsg] 10:59:44:741 (AvDiagnostics_MC,1394,CDE,10) [Thread 4220] [Port 1] [8985A5D73D924EFABBE5CEAB14E778BA] Port [1] Next state is [c:\commserver\localize\scripts\messageediting.cde!PlayMessageMenu] 10:59:47:991 (AvDiagnostics_MC,1394,CDE,10) [Thread 4220] [Port 1] [8985A5D73D924EFABBE5CEAB14E778BA] Port [1] Next state is [c:\commserver\localize\scripts\messageediting.cde!CheckMsgLength] 10:59:47:990 (AvDiagnostics_MC,1394,CDE,10) [Thread 4220] [Port 1] [8985A5D73D924EFABBE5CEAB14E778BA] Port [1] Next state is [c:\commserver\localize\scripts\messageediting.cde!CheckForSecureMessagingForOutsideCallers] 10:59:47:990 (AvDiagnostics_MC,1394,CDE,10) [Thread 4220] [Port 1] [8985A5D73D924EFABBE5CEAB14E778BA] Port [1] Next state is [c:\commserver\localize\scripts\messageediting.cde!SendMsg] 10:59:49:334 (AvDiagnostics_MC,1394,CDE,10) [Thread 4220] [Port 1] [8985A5D73D924EFABBE5CEAB14E778BA] Port [1] Next state is [c:\commserver\localize\scripts\messageediting.cde!ConfirmSend] 10:59:51:005 (AvDiagnostics_MC,1394,CDE,10) [Thread 4220] [Port 1] [8985A5D73D924EFABBE5CEAB14E778BA] Port [1] Next state is [c:\commserver\localize\scripts\phgreeting.cde!AfterMsg] 10:59:52:177 (AvDiagnostics_MC,1394,CDE,10) [Thread 4220] [Port 1] [8985A5D73D924EFABBE5CEAB14E778BA] Port [1] Next state is [c:\commserver\localize\scripts\phgreeting.cde!DoHangup]

More Related