3CX server doesn't accept ACK on 200 OK

Discussion in '3CX Phone System - General' started by Jeroen, Feb 25, 2015.

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

    Joined:
    Feb 25, 2015
    Messages:
    3
    Likes Received:
    0
    When I try to make a call with my SIP device to a SIP Phone the 3CX server doesn't accept my ACK on the 200 OK when the Phone is picked up it repeats the 200 OK serveral times and then disconnects the session.
    This is how the messages look:

    INVITE sip:100@192.168.0.112 SIP/2.0
    Via: SIP/2.0/UDP 192.168.0.179:5060;branch=z9hG4bK9b198305313d45b9
    From: "101" <sip:101@192.168.0.112>;tag=7967
    To: "100" <sip:100@192.168.0.112>
    Contact: <sip:101@192.168.0.179:5060>
    Call-ID: 9b1983051da148cc
    CSeq: 3 INVITE
    Supported:
    Allow: INVITE,ACK,CANCEL,BYE,INFO
    Max-Forwards: 70

    Content-Type: application/sdp
    Content-Length: 134

    v=0
    o=- 1 1 IN IP4 192.168.0.179
    s=SIP Call
    c=IN IP4 192.168.0.179
    t=0 0
    m=audio 5062 RTP/AVP 8
    a=sendrecv
    a=rtpmap:8 PCMA/8000

    SIP/2.0 407 Proxy Authentication Required
    Via: SIP/2.0/UDP 192.168.0.179:5060;branch=z9hG4bK9b198305313d45b9
    Proxy-Authenticate: Digest nonce="414d535c0afe7a4b10:ad3659e4a570f563653a2e230079473f",algorithm=MD5,realm="3CXPhoneSystem"
    To: "100"<sip:100@192.168.0.112>;tag=5d18f214
    From: "101"<sip:101@192.168.0.112>;tag=7967
    Call-ID: 9b1983051da148cc
    CSeq: 3 INVITE
    User-Agent: 3CXPhoneSystem 12.5.39117.982 (38810)
    Content-Length: 0

    ACK sip:100@192.168.0.112 SIP/2.0
    Via: SIP/2.0/UDP 192.168.0.179:5060;branch=z9hG4bK9b198305313d45b9
    From: "101" <sip:101@192.168.0.112>;tag=7967
    To: "100" <sip:100@192.168.0.112>
    Contact: <sip:101@192.168.0.179:5060>
    Call-ID: 9b1983051da148cc
    CSeq: 3 ACK

    Supported:
    Allow: INVITE,ACK,CANCEL,BYE,INFO
    Max-Forwards: 70
    Content-Length: 0

    INVITE sip:100@192.168.0.112 SIP/2.0
    Proxy-Authorization: Digest algorithm=MD5, username="101", uri="sip:101@192.168.0.112", realm="3CXPhoneSystem", nonce="414d535c0afe7a4b10:ad3659e4a570f563653a2e230079473f", response="7ec3df08d8b4f2b6a662313ce348f772"
    Via: SIP/2.0/UDP 192.168.0.179:5060;branch=z9hG4bK9b1983054f764d48
    From: "101" <sip:101@192.168.0.112>;tag=7967
    To: "100" <sip:100@192.168.0.112>
    Contact: <sip:101@192.168.0.179:5060>
    Call-ID: 9b1983051da148cc
    CSeq: 4 INVITE
    Supported:
    Allow: INVITE,ACK,CANCEL,BYE,INFO
    Max-Forwards: 70
    Content-Type: application/sdp
    Content-Length: 134

    v=0
    o=- 1 1 IN IP4 192.168.0.179
    s=SIP Call
    c=IN IP4 192.168.0.179
    t=0 0
    m=audio 5062 RTP/AVP 8
    a=sendrecv
    a=rtpmap:8 PCMA/8000

    SIP/2.0 100 Trying
    Via: SIP/2.0/UDP 192.168.0.179:5060;branch=z9hG4bK9b1983054f764d48
    To: "100" <sip:100@192.168.0.112>
    From: "101" <sip:101@192.168.0.112>;tag=7967
    Call-ID: 9b1983051da148cc
    CSeq: 4 INVITE
    Content-Length: 0

    SIP/2.0 180 Ringing
    Via: SIP/2.0/UDP 192.168.0.179:5060;branch=z9hG4bK9b1983054f764d48
    Contact: <sip:100@192.168.0.112>
    To: "100"<sip:100@192.168.0.112>;tag=fd48cf23
    From: "101"<sip:101@192.168.0.112>;tag=7967
    Call-ID: 9b1983051da148cc
    CSeq: 4 INVITE
    User-Agent: 3CXPhoneSystem 12.5.39117.982 (38810)
    Content-Length: 0

    SIP/2.0 200 OK
    Via: SIP/2.0/UDP 192.168.0.179:5060;branch=z9hG4bK9b1983054f764d48
    Contact: <sip:100@192.168.0.112:5060>
    To: "100"<sip:100@192.168.0.112>;tag=fd48cf23
    From: "101"<sip:101@192.168.0.112>;tag=7967
    Call-ID: 9b1983051da148cc
    CSeq: 4 INVITE
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE
    Content-Type: application/sdp
    Supported: replaces
    User-Agent: 3CXPhoneSystem 12.5.39117.982 (38810)
    Content-Length: 170

    v=0
    o=3cxPS 119286005760 440049598465 IN IP4 192.168.0.112
    s=3cxPS Audio call
    c=IN IP4 192.168.0.112
    t=0 0
    m=audio 7004 RTP/AVP 8
    a=rtpmap:8 PCMA/8000
    a=sendrecv

    After this ACK the 200 OK message is repeaded several times and then the session is disconnected.

    ACK sip:100@192.168.0.112 SIP/2.0
    Via: SIP/2.0/UDP 192.168.0.179:5060;branch=z9hG4bK9b1983054f764d48
    From: "101" <sip:101@192.168.0.112>;tag=7967
    To: "100" <sip:100@192.168.0.112>
    Contact: <sip:101@192.168.0.179:5060>
    Call-ID: 9b1983051da148cc
    CSeq: 4 ACK
    Supported:
    Allow: INVITE,ACK,CANCEL,BYE,INFO
    Max-Forwards: 70
    Content-Length: 0

    SIP/2.0 200 OK
    Via: SIP/2.0/UDP 192.168.0.179:5060;branch=z9hG4bK9b1983054f764d48
    Contact: <sip:100@192.168.0.112:5060>
    To: "100"<sip:100@192.168.0.112>;tag=fd48cf23
    From: "101"<sip:101@192.168.0.112>;tag=7967
    Call-ID: 9b1983051da148cc
    CSeq: 4 INVITE
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE
    Content-Type: application/sdp
    Supported: replaces
    User-Agent: 3CXPhoneSystem 12.5.39117.982 (38810)
    Content-Length: 170

    v=0
    o=3cxPS 119286005760 440049598465 IN IP4 192.168.0.112
    s=3cxPS Audio call
    c=IN IP4 192.168.0.112
    t=0 0
    m=audio 7004 RTP/AVP 8
    a=rtpmap:8 PCMA/8000
    a=sendrecv
     
  2. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,767
    Likes Received:
    286
    A few questions...

    Did this just start happening? New install? New sets?

    What are you using, in other words, what is the SIP device and the SIP Phone? make/ model/ firmware?
     
  3. Jeroen

    Joined:
    Feb 25, 2015
    Messages:
    3
    Likes Received:
    0
    On one side Im using a Grandstream GXP2000, that seems to work fine.
    On the other side im using a embedded deveice we build our selfs, it worked fine with version 8 of 3CX but now it has to work with the new version 12.
     
  4. Jeroen

    Joined:
    Feb 25, 2015
    Messages:
    3
    Likes Received:
    0
    I have found the problem, the ACK on the 200 Ok was missing the tag in the To: .... line
     
Thread Status:
Not open for further replies.