604 Does Not Exist Anywhere

Discussion in '3CX Phone System - General' started by aberry, Feb 9, 2016.

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

    aberry New Member

    Joined:
    Jan 13, 2015
    Messages:
    118
    Likes Received:
    7
    Getting a does not exist error on incoming calls to a conference phone. The conference phone can call out just fine, not sure why 3CX says that it can't be found. Log as follows:

    Call incoming to unit that generates 604 error:

    08-Feb-2016 15:53:29.776 Leg L:461.2[Extn] is terminated: Cause: 604 Does Not Exist Anywhere/INVITE from 172.26.102.27:5060
    08-Feb-2016 15:53:29.776 L:461.1[Extn] failed to reach Extn:3510, reason Not Found
    08-Feb-2016 15:53:29.776 Call to T:Extn:3510@[Dev:sip:3510@172.26.102.27:5060;line=15238] from L:461.1[Extn] failed, cause: Cause: 604 Does Not Exist Anywhere/INVITE from 172.26.102.27:5060
    08-Feb-2016 15:53:29.733 [CM503025]: Call(C:461): Calling T:Extn:3510@[Dev:sip:3510@172.26.102.27:5060;line=15238] for L:461.1[Extn]
    08-Feb-2016 15:53:29.697 [CM503027]: Call(C:461): From: Extn:3983 ("Redacted" <sip:3983@172.26.102.20:5060>) to T:Extn:3510@[Dev:sip:3510@172.26.102.27:5060;line=15238]
    08-Feb-2016 15:53:29.697 [CM503004]: Call(C:461): Route 1: from L:461.1[Extn] to T:Extn:3510@[Dev:sip:3510@172.26.102.27:5060;line=15238]


    Successful call out from unit:

    08-Feb-2016 15:53:16.190 Leg L:456.1[Extn] is terminated: Cause: BYE from 172.26.102.27:5060
    08-Feb-2016 15:52:08.419 [CM503007]: Call(C:456): Extn:3510 has joined, contact <sip:3510@172.26.102.27:5060>
    08-Feb-2016 15:52:08.418 L:456.2[Extn] has joined to L:456.1[Extn]
    08-Feb-2016 15:52:05.979 [CM503025]: Call(C:456): Calling T:Extn:3983@[Dev:sip:3983@172.26.102.197:5060;user=phone] for L:456.1[Extn]
    08-Feb-2016 15:52:05.929 [CM503027]: Call(C:456): From: Extn:3510 ("Legal Conference" <sip:3510@172.26.102.20:5060>) to T:Extn:3983@[Dev:sip:3983@172.26.102.197:5060;user=phone]
    08-Feb-2016 15:52:05.929 [CM503004]: Call(C:456): Route 1: from L:456.1[Extn] to T:Extn:3983@[Dev:sip:3983@172.26.102.197:5060;user=phone]
    08-Feb-2016 15:52:05.928 [CM503001]: Call(C:456): Incoming call from Extn:3510 to <sip:3983@172.26.102.20:5060>


    I can't seem to understand why 3CX thinks that it doesn't exist, has anyone else had a similar issue?

    Thanks
     
  2. tsukraw

    tsukraw New Member

    Joined:
    Mar 9, 2012
    Messages:
    190
    Likes Received:
    6
    Could you by chance do a wireshark capture on the 3CX server for both examples?
    A call from the phone to another phone and then the reverse.

    Post those pcaps.

    Also what kind of phones are they?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,360
    Likes Received:
    226
    Does the set actually show, in 3CX as registered? Check the log showing this happening, be sure that the IP/port are correct. An un-registered set will still be able to place calls, just not receive them.
     
  4. aberry

    aberry New Member

    Joined:
    Jan 13, 2015
    Messages:
    118
    Likes Received:
    7
    It does show registered in 3cx, it is a Konftel IP Dect wireless conference phone. They are imho the best conference phone made by human hands. I have verified SIP and RTP ports that are assigned to he phone and they seem to be set correctly. I will get wireshark captures and see what it looks like.

    http://www.konftel.com/Products/Konftel-IP-DECT-10

    Thanks for the responses.
     
  5. aberry

    aberry New Member

    Joined:
    Jan 13, 2015
    Messages:
    118
    Likes Received:
    7
    Attaching my wireshark logs, still not sure yet.
     

    Attached Files:

  6. aberry

    aberry New Member

    Joined:
    Jan 13, 2015
    Messages:
    118
    Likes Received:
    7
    The Konftel Phone itself is logging as well, here is it's log from an incoming call to it that generates the 604 error:

    Received from udp:172.26.102.20:5060 at 09/02/2016 09:11:35 (892 bytes)

    INVITE sip:3510@172.26.102.27:5060;line=25346 SIP/2.0
    Via: SIP/2.0/UDP 172.26.102.20:5060;branch=z9hG4bK-d8754z-1f03a633872d5537-1---d8754z-;rport
    Max-Forwards: 70
    Contact: <sip:3983@172.26.102.20:5060>
    To: <sip:3510@172.26.102.20>;intercom=true
    From: "Redacted"<sip:3983@172.26.102.20:5060;user=phone>;tag=0e1db53f
    Call-ID: YTU4ZjY3NzUwNzQzNmNiYmRjY2U2OGMwZDc5ZjI4YTc.
    CSeq: 1 INVITE
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE
    Content-Type: application/sdp
    Supported: replaces
    User-Agent: 3CXPhoneSystem 14.0.47020.408 (46852)
    Content-Length: 280

    v=0
    o=3cxPS 349301637120 285514661889 IN IP4 172.26.102.20
    s=3cxPS Audio call
    c=IN IP4 172.26.102.20
    t=0 0
    m=audio 7388 RTP/AVP 0 8 9 3 101
    a=rtpmap:0 PCMU/8000
    a=rtpmap:8 PCMA/8000
    a=rtpmap:9 G722/8000
    a=rtpmap:3 GSM/8000
    a=rtpmap:101 telephone-event/8000
    a=sendrecv


    Sent to udp:172.26.102.20:5060 at 09/02/2016 09:11:35 (313 bytes)

    SIP/2.0 100 Trying
    Via: SIP/2.0/UDP 172.26.102.20:5060;branch=z9hG4bK-d8754z-1f03a633872d5537-1---d8754z-;rport=5060
    From: "Redacted" <sip:3983@172.26.102.20:5060;user=phone>;tag=0e1db53f
    To: <sip:3510@172.26.102.20>
    Call-ID: YTU4ZjY3NzUwNzQzNmNiYmRjY2U2OGMwZDc5ZjI4YTc.
    CSeq: 1 INVITE
    Content-Length: 0



    Sent to udp:172.26.102.20:5060 at 09/02/2016 09:11:35 (476 bytes)

    SIP/2.0 604 Does Not Exist Anywhere
    Via: SIP/2.0/UDP 172.26.102.20:5060;branch=z9hG4bK-d8754z-1f03a633872d5537-1---d8754z-;rport=5060
    Max-Forwards: 70
    From: "Redacted" <sip:3983@172.26.102.20:5060;user=phone>;tag=0e1db53f
    To: <sip:3510@172.26.102.20>;tag=j0mwqvygo
    Call-ID: YTU4ZjY3NzUwNzQzNmNiYmRjY2U2OGMwZDc5ZjI4YTc.
    CSeq: 1 INVITE
    Contact: <sip:3510@172.26.102.27;line=25346>
    User-Agent: IPDECT/03.55.0008 (MAC=00087B0FACA0; SER= 00000; HW=1)
    Content-Length: 0


    Received from udp:172.26.102.20:5060 at 09/02/2016 09:11:35 (368 bytes)

    ACK sip:3510@172.26.102.27:5060;line=25346 SIP/2.0
    Via: SIP/2.0/UDP 172.26.102.20:5060;branch=z9hG4bK-d8754z-1f03a633872d5537-1---d8754z-;rport
    Max-Forwards: 70
    To: <sip:3510@172.26.102.20>;tag=j0mwqvygo
    From: "Redacted"<sip:3983@172.26.102.20:5060;user=phone>;tag=0e1db53f
    Call-ID: YTU4ZjY3NzUwNzQzNmNiYmRjY2U2OGMwZDc5ZjI4YTc.
    CSeq: 1 ACK
    Content-Length: 0
     
  7. aberry

    aberry New Member

    Joined:
    Jan 13, 2015
    Messages:
    118
    Likes Received:
    7
    Working now, it looks like in the software I needed to pair a base station to the extension. Not so much a SIP error, but a configuration setting that I was missing. The 604 error was just throwing me off, as I hadn't seen it before.

    Thanks again
     
  8. tlachaus

    Joined:
    Feb 11, 2016
    Messages:
    20
    Likes Received:
    0
    this doesn't apply to your issue, but i'm wondering if you are using a provisioning template for your konftel conference phones with 3cx? or do you just configure them manually?
     
Thread Status:
Not open for further replies.