Dismiss Notice
We would like to remind you that we’re updating our login process for all 3CX forums whereby you will be able to login with the same credentials you use for the Partner or Customer Portal. Click here to read more.

Can someone pls read my Server activity log

Discussion in '3CX Phone System - General' started by Hammertime, Jul 27, 2009.

Thread Status:
Not open for further replies.
  1. Hammertime

    Joined:
    Feb 5, 2009
    Messages:
    10
    Likes Received:
    0
    Hi,

    I have a question.

    Can you please tell what this means?
    I am running a hotline, and many customers are not getting cut off.
    Sometimes the IVR is not working others times the system just hangs up on customers.

    14:49:35.328 [CM503008]: Call(175): Call is terminated

    14:49:35.328 [CM503019]: Normal call termination. Reason: Agents are logged in but no answer

    14:49:35.328 [CM503016]: Call(175): Target is not registered: <sip:>

    14:49:35.328 [CM503023]: No agents are available in Zep

    14:49:35.312 [CM503015]: Call(175): Attempt to reach <sip:Q812@127.0.0.1:5060> failed. Reason: Not Registered

    14:49:35.312 [CM503016]: Call(175): Target is not registered: Queue812:124

    14:49:35.312 [CM503016]: Call(175): Target is not registered: Queue812:112

    14:49:35.312 [CM503016]: Call(175): Target is not registered: Queue812:126

    14:49:35.312 [CM503016]: Call(175): Target is not registered: Queue812:125Ext.125

    14:49:35.312 [CM503016]: Call(175): Target is not registered: Queue812:911

    14:49:35.312 [CM503016]: Call(175): Target is not registered: Queue812:115

    14:49:35.312 [CM503016]: Call(175): Target is not registered: Queue812:128Ext.128

    14:49:35.312 [CM503016]: Call(175): Target is not registered: Queue812:123

    14:49:35.312 [CM503016]: Call(175): Target is not registered: Queue812:122

    14:49:35.312 [CM503016]: Call(175): Target is not registered: Queue812:121

    14:49:35.312 [CM503016]: Call(175): Target is not registered: Queue812:107

    14:49:35.312 [CM503010]: Making route(s) to <sip:Q812@127.0.0.1:5060>

    14:49:35.296 [CM505001]: Ext.812: Device info: Device Identified: [Man: 3CX Ltd.;Mod: 3CX Queue;Rev: General] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CX Queue] Transport: [sip:127.0.0.1:5060]

    14:49:35.296 [CM503001]: Call(175): Incoming call from Ext.812 to <sip:Q812@127.0.0.1:5060>

    14:49:34.890 [CM503008]: Call(174): Call is terminated

    14:49:34.890 [CM503019]: Normal call termination. Reason: Agents are logged in but no answer

    14:49:34.890 [CM503016]: Call(174): Target is not registered: <sip:>

    14:49:34.890 [CM503023]: No agents are available in Zep

    14:49:34.890 [CM503015]: Call(174): Attempt to reach <sip:Q812@127.0.0.1:5060> failed. Reason: Not Registered

    1) Call is terminated = Meaning the server hung up on the customer?
    2) No agents are avaible = Could this be the resason for all the problems?
    3) Normal call termination = Meaning the server hung up on the customer?
    4) Attemp to reach = Menaing the whole queue is offline?
     
  2. Hammertime

    Joined:
    Feb 5, 2009
    Messages:
    10
    Likes Received:
    0
    I have some more..
    Maybe i have a firewall problem aswell.
    Dont know if this log has something to do with the above log


    15:16:27.437 [MS101003] C:3092.1: Possible firewall problem. Address mapping failed on STUN server 85.119.136.171:3478 for local address ":9010"

    15:16:27.437 [MS201000] Use STUN server 'stun.musimi.dk:3478'

    15:16:27.437 [MS101005] STUN request failed for ports 9010,9011 on STUN server 'stun2.3cx.com:3478'

    15:16:27.312 [MS201000] Use STUN server 'stun2.3cx.com:3478'

    15:16:27.312 [MS101005] STUN request failed for ports 9010,9011 on STUN server 'stun.musimi.dk:3478'

    15:16:27.281 [MS201000] Use STUN server 'stun.musimi.dk:3478'

    15:16:27.281 [MS101005] STUN request failed for ports 9010,9011 on STUN server 'stun2.3cx.com:3478'

    15:16:27.156 [CM503012]: Inbound office hours rule (unnamed) for 10008 forwards to DN:814

    15:16:22.375 [MS105000] C:3091.1: No RTP packets were received:remoteAddr=127.0.0.1:40724,extAddr=0.0.0.0:0,localAddr=127.0.0.1:7404

    15:16:21.562 [CM503008]: Call(2463): Call is terminated

    15:16:21.531 [CM503008]: Call(2463): Call is terminated
     
  3. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    11,071
    Likes Received:
    323
    The second log looks like you don't have all the needed ports forwarded on your router, 9000 to 9015.
     
  4. Hammertime

    Joined:
    Feb 5, 2009
    Messages:
    10
    Likes Received:
    0
    3CX Firewall Checker, v1.0. Copyright (C) 3CX Ltd. All rights reserved.

    <20:37:19>: Phase 1, checking servers connection, please wait...
    <20:37:19>: Stun Checker service is reachable. Phase 1 check passed.
    <20:37:19>: Phase 2a, Check Port Forwarding to UDP SIP port, please wait...
    <20:37:35>: UDP SIP Port is set to 5060. Response received WITH TRANSLATION 16843::5060. Phase 2a check passed with WARNINGS. Some functionality will be LIMITED. For more information, please visit http://www.3cx.com/support/firewall-checker.html

    <20:37:35>: Phase 2b. Check Port Forwarding to TCP SIP port, please wait...
    <20:37:40>: TCP SIP Port is set to 5060. Response received WITH TRANSLATION 16843::5060. Phase 2b check passed with WARNINGS. Some functionality will be LIMITED. For more information, please visit http://www.3cx.com/support/firewall-checker.html

    <20:37:40>: Phase 3. Check Port Forwarding to TCP Tunnel port, please wait...
    <20:37:45>: TCP TUNNEL Port is set to 5090. Response received WITH TRANSLATION 16851::5090. Phase 3 check passed with WARNINGS. Some functionality will be LIMITED. For more information, please visit http://www.3cx.com/support/firewall-checker.html

    <20:37:45>: Phase 4. Check Port Forwarding to RTP external port range, please wait...
    <20:37:51>: UDP RTP Port 9000. Response received WITH TRANSLATION 16852::9000. Phase 4-01 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/support/firewall-checker.html
    <20:37:56>: UDP RTP Port 9001. Response received WITH TRANSLATION 16853::9001. Phase 4-02 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/support/firewall-checker.html
    <20:38:00>: UDP RTP Port 9002. Response received WITH TRANSLATION 16854::9002. Phase 4-03 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/support/firewall-checker.html
    <20:38:05>: UDP RTP Port 9003. Response received WITH TRANSLATION 16855::9003. Phase 4-04 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/support/firewall-checker.html
    <20:38:09>: UDP RTP Port 9004. Response received WITH TRANSLATION 16856::9004. Phase 4-05 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/support/firewall-checker.html
    <20:38:14>: UDP RTP Port 9005. Response received WITH TRANSLATION 16857::9005. Phase 4-06 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/support/firewall-checker.html
    <20:38:18>: UDP RTP Port 9006. Response received WITH TRANSLATION 16858::9006. Phase 4-07 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/support/firewall-checker.html
    <20:38:23>: UDP RTP Port 9007. Response received WITH TRANSLATION 16859::9007. Phase 4-08 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/support/firewall-checker.html
    <20:38:27>: UDP RTP Port 9008. Response received WITH TRANSLATION 16860::9008. Phase 4-09 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/support/firewall-checker.html
    <20:38:32>: UDP RTP Port 9009. Response received WITH TRANSLATION 16861::9009. Phase 4-10 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/support/firewall-checker.html
    <20:38:36>: UDP RTP Port 9010. Response received WITH TRANSLATION 16846::9010. Phase 4-11 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/support/firewall-checker.html
    <20:38:41>: UDP RTP Port 9011. Response received WITH TRANSLATION 16862::9011. Phase 4-12 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/support/firewall-checker.html
    <20:38:45>: UDP RTP Port 9012. Response received WITH TRANSLATION 16848::9012. Phase 4-13 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/support/firewall-checker.html
    <20:38:50>: UDP RTP Port 9013. Response received WITH TRANSLATION 16849::9013. Phase 4-14 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/support/firewall-checker.html
    <20:38:54>: UDP RTP Port 9014. Response received WITH TRANSLATION 16863::9014. Phase 4-15 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/support/firewall-checker.html
    <20:38:59>: UDP RTP Port 9015. Response received WITH TRANSLATION 16864::9015. Phase 4-16 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/support/firewall-checker.html


    Application exit code is 19

    Can someone tell me what might be wrong her`??
     
Thread Status:
Not open for further replies.