cannot dial out

Discussion in '3CX Phone System - General' started by pdq, Aug 9, 2010.

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

    pdq

    Joined:
    Dec 3, 2009
    Messages:
    82
    Likes Received:
    0
    New install, outbound rule and PAtton 4114 configuration entered. Inbound calls work fine. I get a fast busy immediasley when I click dial.

    Logs:

    15:41:23.741 [CM503020]: Normal call termination. Reason: Not found
    15:41:23.740 [CM503016]: Call(8): Attempt to reach <sip:8819414560559@192.168.11.14> failed. Reason: Not Found
    15:41:23.739 [CM503014]: Call(8): No known route to target: <sip:8819414560559@192.168.11.14>
    15:41:23.734 [CM503010]: Making route(s) to <sip:8819414560559@192.168.11.14>
    15:41:23.723 [CM505001]: Ext.110: Device info: Device Identified: [Man: Cisco;Mod: SPA Series;Rev: General] Capabilities:[reinvite, replaces, unable-no-sdp, no-recvonly] UserAgent: [Cisco/SPA502G-7.1.3a] PBX contact: [sip:110@192.168.11.14:5060]
    15:41:23.715 [CM503001]: Call(8): Incoming call from Ext.110 to <sip:8819414560559@192.168.11.14>
    15:38:58.751 [CM503008]: Call(7): Call is terminated
    15:38:53.394 Currently active calls - 1: [7]
    15:38:44.305 [CM503007]: Call(7): Device joined: sip:100@192.168.11.106:5060
    15:38:44.296 [CM503007]: Call(7): Device joined: sip:10001@192.168.11.36:5062
    15:38:23.394 Currently active calls - 1: [7]


    Frustrated in Florida
     
  2. pdq

    pdq

    Joined:
    Dec 3, 2009
    Messages:
    82
    Likes Received:
    0
    Frustration fixed due to _____.
     
  3. mfm

    mfm Active Member

    Joined:
    Mar 4, 2010
    Messages:
    641
    Likes Received:
    2
    Not sure what your last post means,. but your logs are telling you that you do not have an outbound rule to satisfy the number being dialed.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. pdq

    pdq

    Joined:
    Dec 3, 2009
    Messages:
    82
    Likes Received:
    0
    It means I found the issue in the outbound rule.
     
Thread Status:
Not open for further replies.