Announcement

Collapse
No announcement yet.
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Bridge not accessible this morning

    Good afternoon folks,

    I have run into an issue only about 2 or 3 times where the bridge is not accessible. When dialing the extension for the Bridge, it goes directly to our regular auto-attendant instead of grabbing a port and going to the bridge attendant. I also cannot access either the web console or admin console. The only way to get access back to it is to power-cycle the server. Checking alert logs once it's rebooted yields no messages.

    I checked the Shoretel event logs and I don't know if this is related but I found this error recorded about the same time we had issues.

    Date(mm/dd/yyyy): 5/28/2009
    Time: 7:56:01 AM (GMT -07:00)
    Event ID: 246
    Source: ShoreWare
    Type: Information
    Category: TMS
    Description:
    The Telephony Management Server has logged an informational debug message. The debug message contents are:

    S:\TMS\NCC\NccTsp\Ncc1stPartyEvent.cpp(5450) : Assertion failed: (strSIPCallID.length() > 0)
    This doesn't happen very often but as usual it's at 8am when departments need to jump on a call. Anyone else had this issue or seen the error above?

  • #2
    We get those events all the time. For us it's mostly Unknown Caller ID's in which the system is ignoring.

    According to ShoreTel Maintenance Guide for 7.5:

    246
    Information The Telephony Management Server has logged an informational debug message. The debug message contents are:<Message>
    A logic assertion within TMS failed.
    No action, unless the event is accompanied by system failures.
    If system failures are occurring, contact ShoreTel Support.

    Comment

    Working...
    X