Welcome to

Welcome to!

This site was created as a place to share stories, tips, and troubleshooting help with ShoreTel/Mitel systems. ShoreTel/Mitel is obviously the MOST exciting VoiP platform on the market right now, and we realized there was no centralized place to discuss this platform, but now there is. Please feel free to join and share your experiences.

Please Note: This site IS NOT owned, funded, or managed by ShoreTel/Mitel, Inc. although you may find ShoreTel/Mitel employees sharing there experiences and expertise. If you would like more information on ShoreTel/Mitel systems, contact BTX at [email protected]

As always please support the advertisers that help support our site.

Thank You,
See more
See less
  • Filter
  • Time
  • Show
Clear All
new posts

  • Searching Log For Hunt group busy

    I am searching the logs for a case of "I know we made the huntgroup unbusy using *18 XXXX" but I am having a hard time finding some decisive string to search for. This is a multisite with over 20 hunt groups. Any thoughts? Searching for Star_Key gets me close, but I was hoping to find a log file or a string in the TMSNCC that is more decisive.

  • #2
    In TmsNcc,

    1. Locate these lines
    12:51:10.652 ( 2168: 3136) U-PE: 2000001E InService
    12:48:54.256 ( 2168: 3136) U-PE: 2000001E OutOfServiceBusyOut

    2. Search up from there to locate this line which has the same handle (2000001E)
    12:44:38.463 ( 2168: 3136) U-CE: 2000001E "sip:[email protected]:5441"


    • #3
      what is (2168: 3136)?
      I was hoping for for an identifier to the hunt group. I did try the OUtofservicebusyout string and that did seem to work.


      • #4
        2168: 3136 is the process and thread ID. Note that OutOfServiceBusyOut will be logged when you busy it out and InService will be logged when you make it available again. You can get the extension of the hunt group from the sip: line.