Strange system error

Discussion in '3CX Phone System - General' started by jduncan, Aug 13, 2007.

  1. jduncan

    Joined:
    Jul 26, 2007
    Messages:
    31
    Likes Received:
    0
    Hi all, i got a strange error and could not figure out what was wrong. It was not till i arrived into office that i saw one of our Grandstream BT-200 phones had "locked up". The last dialed number was displayed and the time was frozen at 3:32pm from the day before! Rebooting the phone fixed the issue. But the phone locking up was not all...It brought down the entire system with it. We could not make any outgoing or receive any incoming calls over the PSTN lines through the GX-4104 gateway. Any ideas? Here is the error from the server logs:

    17:16:44.734 MediaServerReporting::RTPReceiver [MS005001] Call(57) Ext.302: payload #126 doesn't correspond initial SDP datalen=4
    17:16:34.515 MediaServerReporting::RTPReceiver [MS005001] Call(57) Ext.302: payload #126 doesn't correspond initial SDP datalen=4
    17:16:24.296 MediaServerReporting::RTPReceiver [MS005001] Call(57) Ext.302: payload #126 doesn't correspond initial SDP datalen=4
    17:16:14.187 MediaServerReporting::RTPReceiver [MS005001] Call(57) Ext.302: payload #126 doesn't correspond initial SDP datalen=4
    17:16:03.921 MediaServerReporting::RTPReceiver [MS005001] Call(57) Ext.302: payload #126 doesn't correspond initial SDP datalen=4
    17:15:53.640 MediaServerReporting::RTPReceiver [MS005001] Call(57) Ext.302: payload #126 doesn't correspond initial SDP datalen=4
    17:15:43.406 MediaServerReporting::RTPReceiver [MS005001] Call(57) Ext.302: payload #126 doesn't correspond initial SDP datalen=4
    17:15:33.187 MediaServerReporting::RTPReceiver [MS005001] Call(57) Ext.302: payload #126 doesn't correspond initial SDP datalen=4
     
  2. SY

    SY Well-Known Member
    3CX Staff

    Joined:
    Jan 26, 2007
    Messages:
    1,821
    Likes Received:
    1
    Is this Extension 302 said BT200?

    Thanks,
    Stepan
     
  3. jduncan

    Joined:
    Jul 26, 2007
    Messages:
    31
    Likes Received:
    0
    Thanks for the response...

    Well this was a very recent installation and its my first so i was not too familiar with everything. The ext 302 was actually another phone that was trying to make a call while the system was apparently crashed. The extension in question is actually 301. But this was all i got out of the log in the time period. Unless there is a way to see the full log.
     
  4. Costas3CX

    Costas3CX New Member

    Joined:
    Jan 23, 2007
    Messages:
    217
    Likes Received:
    0
    C:\Program Files\3CX PhoneSystem\Data\Logs

    the logs are there.

    When you need to send people the logs to examine them and locate the problem for you, you just go to General/Support/ and you generate support info. All confidential data, such as VOIP provider passwords, will be automatically removed from the file. Logs are included in the file. But best way to locate a problem is, (and this is generally speaking not in this particular case) , when you have a problem, you restart 6 services related to 3cx and you reproduce the problem. Then you generate support info. This ensures that logs are empty (they clear after you restart services) and only contain the 1 call or 1 action that gives you trouble...
     
  5. SY

    SY Well-Known Member
    3CX Staff

    Joined:
    Jan 26, 2007
    Messages:
    1,821
    Likes Received:
    1
    Sorry, but I'm slightly confused by this information...

    From log:
    Call from Extension 302 ( Call(57) ) was connected (provided log doesn't show other party of call but you can find all log entries related to this call) and was at least 1 minute and 15 sec long.

    You say:
    system was apparently crashed and Extension just _tried_ to make call :)


    Which type of phone plays Extension 302 role? Is it X-lite or eyeBeam softphone?

    Thanks,
    Stepan
     

Share This Page