Did Not Change A Thing, yet the system quit working

Discussion in '3CX Phone System - General' started by NRG, Feb 12, 2009.

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

    NRG

    Joined:
    Dec 24, 2008
    Messages:
    31
    Likes Received:
    0
    So, I got into the office this morning, and all calls coming in from nexVortex will not transfer to the proper extensions. In fact my extension will not ring AT ALL. I can make calls out, calls get transfered to VM, but will not ring on my phone. This is very frustrating as I have changed nothing on the system. Check log below.



    10:37:42.234 [CM504002]: Ext.111: a contact is unregistered. Contact(s): []

    10:37:41.718 [CM504002]: Ext.111: a contact is unregistered. Contact(s): []

    10:37:19.500 [CM503008]: Call(3): Call is terminated

    10:37:19.500 [CM503008]: Call(3): Call is terminated

    10:37:15.593 [CM503015]: Call(3): Attempt to reach <sip:111@127.0.0.1:5060> failed. Reason: No Answer

    10:37:15.593 [CM503003]: Call(3): Call to sip:111@127.0.0.1:5060 has failed; Cause: 408 Request Timeout; internal


    10:36:43.453 [CM503004]: Call(3): Calling: Ext:Sip.111@[Dev:sip:111@127.0.0.1:5060]

    10:36:43.453 [CM503010]: Making route(s) to <sip:111@127.0.0.1:5060>

    10:36:39.687 [MS211000] C:3.1: 66.234.135.60:53876 is delivering DTMF using RTP payload (RFC2833). In-Band DTMF tone detection is disabled for this call segment.

    10:36:35.531 [CM503007]: Call(3): Device joined: sip:800@127.0.0.1:40600;rinstance=e968b2c27c55ff01

    10:36:35.531 [CM503007]: Call(3): Device joined: sip:69.30.45.229:5061

    10:36:35.531 [CM505001]: Ext.800: Device info: Device Identified: [Man: 3CX Ltd.;Mod: 3CX IVR;Rev: 1] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CX IVR] Transport: [sip:127.0.0.1:5061]

    10:36:35.515 [CM503002]: Call(3): Alerting sip:800@127.0.0.1:40600;rinstance=e968b2c27c55ff01

    10:36:35.031 [CM503004]: Call(3): Calling: Ext:Ext.800@[Dev:sip:800@127.0.0.1:40600;rinstance=e968b2c27c55ff01]

    10:36:35.031 [CM503010]: Making route(s) to <sip:800@192.168.1.3:5061>

    10:36:35.031 [CM505003]: Provider:[nexVortex] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Sippy] Transport: [sip:192.168.1.3:5061]

    10:36:35.015 [CM503001]: Call(3): Incoming call from xxxxxxxxxx@(Ln.10000@nexVortex) to <sip:800@192.168.1.3:5061>

    10:36:34.953 [CM503012]: Inbound office hours rule (unnamed) for 10000 forwards to DN:800

    10:36:16.765 [CM503008]: Call(2): Call is terminated

    10:36:16.750 [CM503008]: Call(2): Call is terminated

    10:36:11.218 [CM503015]: Call(2): Attempt to reach <sip:111@127.0.0.1:5060> failed. Reason: No Answer

    10:36:11.218 [CM503003]: Call(2): Call to sip:111@127.0.0.1:5060 has failed; Cause: 408 Request Timeout; internal


    10:35:39.078 [CM503004]: Call(2): Calling: Ext:Sip.111@[Dev:sip:111@127.0.0.1:5060]

    10:35:39.078 [CM503010]: Making route(s) to <sip:111@127.0.0.1:5060>

    10:35:35.265 [MS211000] C:2.1: 66.234.135.60:44876 is delivering DTMF using RTP payload (RFC2833). In-Band DTMF tone detection is disabled for this call segment.

    10:35:31.359 [CM503007]: Call(2): Device joined: sip:800@127.0.0.1:40600;rinstance=e968b2c27c55ff01

    10:35:31.343 [CM503007]: Call(2): Device joined: sip:69.30.45.229:5061

    10:35:31.343 [CM505001]: Ext.800: Device info: Device Identified: [Man: 3CX Ltd.;Mod: 3CX IVR;Rev: 1] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CX IVR] Transport: [sip:127.0.0.1:5061]

    10:35:31.328 [CM503002]: Call(2): Alerting sip:800@127.0.0.1:40600;rinstance=e968b2c27c55ff01

    10:35:30.859 [CM503004]: Call(2): Calling: Ext:Ext.800@[Dev:sip:800@127.0.0.1:40600;rinstance=e968b2c27c55ff01]

    10:35:30.859 [CM503010]: Making route(s) to <sip:800@192.168.1.3:5061>

    10:35:30.859 [CM505003]: Provider:[nexVortex] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Sippy] Transport: [sip:192.168.1.3:5061]

    10:35:30.843 [CM503001]: Call(2): Incoming call from xxxxxxxxxx@(Ln.10000@nexVortex) to <sip:800@192.168.1.3:5061>

    10:35:30.765 [CM503012]: Inbound office hours rule (unnamed) for 10000 forwards to DN:800
     
  2. NRG

    NRG

    Joined:
    Dec 24, 2008
    Messages:
    31
    Likes Received:
    0
    So, I did a Firewll check, and 5060 was having translation issues(mine SIP is set to 5061), and 5061 was showing up clear. Then, I restarted the server, and 5061 was having translation issues along with 5060. Then I restrated server, router, and IP Modem. 5060 then showed clear, and 5061 was having translation issues. So I set 3CX to 5060 from 5061, and all seems right, of course till the next time 5060 gets translation issues for no apparent reason, and 5061 becomes clear for no apparent reason.

    Can anyone explain why the ports are vacillating like they are? It bounces from 5060 being clear, to 5060 having translation issues. At the same time 5061 will do just the opposite.
     
  3. SY

    SY Well-Known Member
    3CX Support

    Joined:
    Jan 26, 2007
    Messages:
    1,825
    Likes Received:
    2
    Could you please describe exact call scenario, expected routing and specify what is the device "111"? (Is it remote?)
    The log just point that extension 111 is not reachable for PBX.

    Thanks
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.