Cisco Phone Transfer not Completing

Discussion in '3CX Phone System - General' started by ITWorks, Nov 17, 2007.

  1. ITWorks

    ITWorks New Member

    Joined:
    Apr 7, 2007
    Messages:
    121
    Likes Received:
    0
    3CX Phone System Version 3.1.2434.0
    Cisco 2811 Router with ISDN PRI
    Cisco 7941 Phones

    I have not been able to successfully complete transfers with Cisco phones and 3CX. In the scenario displayed in the packet capture below I have received an incoming call from 9072223333 on an ISDN PRI line (10.1.3.13) and it is answered by 2224444. 2224444 (extension 4444) transfers the call to extension 4419. Outside caller begins to hear music on hold. 4419 answers call but now also hears the music on hold. Message on 4444 indicates “cannot complete transfer”. And complete transfer never occurs. I have tried every available setting on the advanced options for the ISDN gateway.

    I have tried Alpha 4 and do not get the 3CX error below and occasionally do get successful transfers, but most times not.

    In the 3CX Log below I do not understand why the To: is 907222333 when that is the outside caller number and the call is being transferred to 4419.

    I would appreciate any help someone could provide.


    3CX LOG:

    [CM010001] Line configuration does not allow identification of the source of this call. Check Advanced Options for Gateways and Providers and match a field to a correct value from the following: Contact IP: '10.1.3.7'; From: '2224444'; To: '9072223333'; Rline: '9072223333'; Contact: '2224444'


    PACKET CAPTURE: two packets

    No. Time Source Destination Protocol Info
    1718 12.550655 10.1.3.7 10.1.3.3 SIP Request: REFER sip:9072223333@10.1.3.3:5060

    Frame 1718 (746 bytes on wire, 746 bytes captured)
    Ethernet II, Src: Cisco_52:c7:58 (00:1b:54:52:c7:58), Dst: Intel_b4:ff:de (00:02:b3:b4:ff:de)
    Internet Protocol, Src: 10.1.3.7 (10.1.3.7), Dst: 10.1.3.3 (10.1.3.3)
    User Datagram Protocol, Src Port: 49236 (49236), Dst Port: 5060 (5060)
    Session Initiation Protocol
    Request-Line: REFER sip:9072223333@10.1.3.3:5060 SIP/2.0
    Method: REFER
    [Resent Packet: False]
    Message Header
    Via: SIP/2.0/UDP 10.1.3.7:5060;branch=z9hG4bK05d29bcd
    Transport: UDP
    Sent-by Address: 10.1.3.7
    Sent-by port: 5060
    Branch: z9hG4bK05d29bcd
    From: "2224444"<sip:2224444@10.1.3.7:5060;transport=udp>;tag=001b5452c758001076fc022d-dc7a813d
    SIP Display info: "2224444"
    SIP from address: sip:2224444@10.1.3.7:5060
    SIP tag: 001b5452c758001076fc022d-dc7a813d
    To: "9072223333"<sip:9072223333@10.1.3.13>;tag=f2708061
    SIP Display info: "9072223333"
    SIP to address: sip:9072223333@10.1.3.13
    SIP tag: f2708061
    Call-ID: ZWNhNjFhMWU2NmJlZThlNmIyZjAyNDE5NWE3NGUwMDM.
    Max-Forwards: 70
    Date: Sat, 17 Nov 2007 05:46:36 GMT
    CSeq: 102 REFER
    Sequence Number: 102
    Method: REFER
    User-Agent: Cisco-CP7941G/8.3.0
    Contact: <sip:2224444@10.1.3.7:5060;transport=udp>
    Contact Binding: <sip:2224444@10.1.3.7:5060;transport=udp>
    Refer-To: <sip:4419@10.1.3.3;user=phone?Replaces=001b5452-c758000a-d256ef17-fac412f1%4010.1.3.7%3Bto-tag%3D3c1fcf3f%3Bfrom-tag%3D001b5452c7580011c82b31db-4657bec5>
    Referred-By: <sip:4414@10.1.3.3>
    Content-Length: 0

    No. Time Source Destination Protocol Info
    1739 12.752382 10.1.3.3 10.1.3.7 SIP Status: 404 User Not Found
    Frame 1739 (407 bytes on wire, 407 bytes captured)
    Ethernet II, Src: Intel_b4:ff:de (00:02:b3:b4:ff:de), Dst: Cisco_52:c7:58 (00:1b:54:52:c7:58)
    Internet Protocol, Src: 10.1.3.3 (10.1.3.3), Dst: 10.1.3.7 (10.1.3.7)
    User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 5060 (5060)
    Session Initiation Protocol
    Status-Line: SIP/2.0 404 User Not Found
    Status-Code: 404
    [Resent Packet: False]
    Message Header
    Via: SIP/2.0/UDP 10.1.3.7:5060;branch=z9hG4bK05d29bcd
    Transport: UDP
    Sent-by Address: 10.1.3.7
    Sent-by port: 5060
    Branch: z9hG4bK05d29bcd
    To: "9072223333"<sip:9072223333@10.1.3.13>;tag=f2708061
    SIP Display info: "9072223333"
    SIP to address: sip:9072223333@10.1.3.13
    SIP tag: f2708061
    From: "2224444"<sip:2224444@10.1.3.7:5060;transport=udp>;tag=001b5452c758001076fc022d-dc7a813d
    SIP Display info: "2224444"
    SIP from address: sip:2224444@10.1.3.7:5060
    SIP tag: 001b5452c758001076fc022d-dc7a813d
    Call-ID: ZWNhNjFhMWU2NmJlZThlNmIyZjAyNDE5NWE3NGUwMDM.
    CSeq: 102 REFER
    Sequence Number: 102
    Method: REFER
    User-Agent: 3CXPhoneSystem
    Content-Length: 0
     
  2. miraportuga

    miraportuga Member

    Joined:
    Aug 7, 2007
    Messages:
    297
    Likes Received:
    0
    On the gateway you're using to test this, or Voip line, go to the configuration, Other Options, check "Use ip in contacts" and below put '10.1.3.7' . Usually thats whats need to be done when that message appears...

    Cheers
     
  3. ITWorks

    ITWorks New Member

    Joined:
    Apr 7, 2007
    Messages:
    121
    Likes Received:
    0
    cisco phone transfers

    Thank you miraportuga,
    That is how the line is configured. In fact it would not receive calls until the "use IP in contacts" was checked.
    I am working to understand what should be occuring when there is a transfer so I can identify what is wrong with this one. I am stumped.
    Cheers.
    Mark
     
  4. ITWorks

    ITWorks New Member

    Joined:
    Apr 7, 2007
    Messages:
    121
    Likes Received:
    0
    Now able to transfer calls from Cisco phones

    The problem with not being able to complete call trasfers from Cisco phones has been resolved. The problem was in the phone's cnf.xml file. It appears to be important in the following section of the cnf.xml configuration that the contact be the extension number registered in the 3CX configuration and not the E.164 number or user SIP ID.

    <line button="1">
    <featureID>9</featureID>
    <featureLabel>222-4444</featureLabel>
    <proxy>10.1.3.3</proxy>
    <port>5060</port>
    <name>4444</name>
    <displayName>2224444</displayName>
    <autoAnswer>
    <autoAnswerEnabled>2</autoAnswerEnabled>
    </autoAnswer>
    <callWaiting>3</callWaiting>
    <authName>4444</authName>
    <authPassword>4444</authPassword>
    <sharedLine>false</sharedLine>
    <messageWaitingLampPolicy>1</messageWaitingLampPolicy>
    <messagesNumber>9999</messagesNumber>
    <ringSettingIdle>4</ringSettingIdle>
    <ringSettingActive>5</ringSettingActive>
    <contact>4444</contact>
    <forwardCallInfoDisplay>
    <callerName>true</callerName>
    <callerNumber>false</callerNumber>
    <redirectedNumber>false</redirectedNumber>
    <dialedNumber>true</dialedNumber>
    </forwardCallInfoDisplay>
    </line>
     

Share This Page