3CXphone for windows outbound call

Discussion in 'Windows' started by crudi, Jan 4, 2016.

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

    Joined:
    Jan 4, 2016
    Messages:
    3
    Likes Received:
    0
    We have some issue with the 3CXphone for Windows and Snom phone.
    When we try to make any outbound call by CTI mode, the 3CXphone for windows communicate to the snom the 300 ID!
    3cx Phone System, Snom and PC belong to the same LAN.

    3CXphone for windows Version 14.0.45
    snom320-SIP Firmware-Version: snom320-SIP 8.7.5.35
    3cx Phone System Version 14 Service Pack 2


    3XC Server Manager Log
    04-gen-2016 12:08:22.837 Leg L:218.1[Extn] is terminated: Cause: BYE from PBX
    04-gen-2016 12:08:22.786 [CM503020]: Call(C:218): Normal call termination. Call originator: Extn:309. Reason: Disabled by Forwarding Rule
    04-gen-2016 12:08:22.786 L:218.1[Extn] forwards call from Extn:300 to EndCall:EndCall based on rule Fwd[Available/NoAnsw]
    04-gen-2016 12:08:22.786 L:218.1[Extn] failed to reach Extn:300, reason No Answer
    04-gen-2016 12:07:52.748 [CM503025]: Call(C:218): Calling T:Extn:300@[Dev:sip:300@192.168.0.91:61602;rinstance=0-25d705693ea740009d9ddd49434f4409;ob,Dev:sip:300@192.168.0.58:1027;line=6nlhjmjf] for L:218.1[Extn]
    04-gen-2016 12:07:52.728 [CM503025]: Call(C:218): Calling T:Extn:300@[Dev:sip:300@192.168.0.91:61602;rinstance=0-25d705693ea740009d9ddd49434f4409;ob,Dev:sip:300@192.168.0.58:1027;line=6nlhjmjf] for L:218.1[Extn]
    04-gen-2016 12:07:52.681 [CM503027]: Call(C:218): From: Extn:309 ("xxxxxxx" <sip:309@192.168.0.117:5060>) to T:Extn:300@[Dev:sip:300@192.168.0.91:61602;rinstance=0-25d705693ea740009d9ddd49434f4409;ob,Dev:sip:300@192.168.0.58:1027;line=6nlhjmjf]
    04-gen-2016 12:07:52.681 [CM503004]: Call(C:218): Route 1: from L:218.1[Extn] to T:Extn:300@[Dev:sip:300@192.168.0.91:61602;rinstance=0-25d705693ea740009d9ddd49434f4409;ob,Dev:sip:300@192.168.0.58:1027;line=6nlhjmjf]
    04-gen-2016 12:07:52.679 [CM503001]: Call(C:218): Incoming call from Extn:309 to <sip:300@192.168.0.117:5060>

    Any help would be appreciated.
     
  2. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,375
    Likes Received:
    231
    I'm not clear on how this is an "outbound calls". This would appear to be an internal call from ext 309 to 300. It would seem to fail because of a forwarding rule set in extension 300, from the looks of the logs. Does ext 300 have some sort of forwarding in place?
     
  3. crudi

    Joined:
    Jan 4, 2016
    Messages:
    3
    Likes Received:
    0
    That is the question!
    If we make an outbound call from the snom ip phone (ext 309) everything works fine, but if we make an external call from the 3CXphone for windows (ext 309) in CTI mode it call the ext 300!
    The web page of IP Snom Interface shows the ext 300 in the Dialed Numbers, instead of the external number called.
    It seems that any external number is called up by the 3CXphone for windows, contacts the ext 300!
    The 3CXphone for windows works fine to call any internal extension.
    The configuration of extensions works fine for all IP Snom Phone.

    Thanks again for the help.
     
  4. NickD_3CX

    NickD_3CX Support Team
    Staff Member 3CX Support

    Joined:
    Jun 2, 2014
    Messages:
    1,255
    Likes Received:
    63
    I am going to make a wild guess here and ask the following, what modifications have you made to the template? Also, have you replaced the "line" keys on the snom phone with the BLF key that calls ext 300?

    I have seen this once before and I was banging my head against the wall until I figured it out...
     
  5. crudi

    Joined:
    Jan 4, 2016
    Messages:
    3
    Likes Received:
    0
    Thanks a lot NickD_3CX.
    We are going crazy for this problem!
    It was enough to set at least one function key as active line on Snom and it worked.
    Thanks again.
     
  6. NickD_3CX

    NickD_3CX Support Team
    Staff Member 3CX Support

    Joined:
    Jun 2, 2014
    Messages:
    1,255
    Likes Received:
    63
    Glad it worked :) .

    Locking topic as the solution was found
     
Thread Status:
Not open for further replies.