Phone will not stop ringing

Discussion in '3CX Phone System - General' started by aberry, Oct 2, 2015.

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

    aberry New Member

    Joined:
    Jan 13, 2015
    Messages:
    118
    Likes Received:
    7
    Having an intermittend problem with an 'unsupported' IP phone. Every once in a while a phone will get stuck ringing. The only way to fix the issue, is to either reboot the phone, or call voicemail and force a call on the line. Here is the verbose log from the call that caused the neverending ring:

    v=0
    o=3891 8000 8000 IN IP4 172.26.102.134
    s=SIP Call
    c=IN IP4 172.26.102.134
    t=0 0
    m=audio 5004 RTP/AVP 0 8 9 18 101
    a=sendrecv
    a=rtpmap:0 PCMU/8000
    a=ptime:20
    a=rtpmap:8 PCMA/8000
    a=rtpmap:9 G722/8000
    a=rtpmap:18 G729/8000
    a=fmtp:18 annexb=no
    a=rtpmap:101 telephone-event/8000
    a=fmtp:101 0-15
    02-Oct-2015 15:36:52.755 [CM503001]: Call(C:1351): Incoming call from Extn:3891 to <sip:9999@172.26.102.20:5060>
    02-Oct-2015 15:34:53.684 L:1350.2[Extn]: Terminating targets, reason: SIP ;cause=408 ;text="Request Timeout"
    02-Oct-2015 15:34:53.684 Leg L:1350.2[Extn] is terminated: Cause: 408 Request Timeout/INVITE from local
    02-Oct-2015 15:34:53.684 L:1350.2[Extn] got Terminated Recv 408/INVITE from 0.0.0.0:0 tid=b9140a659650756a Call-ID=ODM1Y2FjMjBlZWFhMzZmNGYyYmFiNDNiYTk0NDg5OTc.:
    SIP/2.0 408 Request Timeout
    Via: SIP/2.0/UDP 172.26.102.20:5060;branch=z9hG4bK-d8754z-b9140a659650756a-1---d8754z-;rport
    To: <sip:3891@172.26.102.20>;tag=4456925e
    From: "REDACTED "<sip:360XXXXXXX@172.26.102.20:5060;nf=e>;tag=4b45e57a
    Call-ID: ODM1Y2FjMjBlZWFhMzZmNGYyYmFiNDNiYTk0NDg5OTc.
    CSeq: 1 INVITE
    Content-Length: 0
    02-Oct-2015 15:34:53.684 L:1350.2[Extn] got Failure: Failure Recv 408/INVITE from 0.0.0.0:0 tid=b9140a659650756a Call-ID=ODM1Y2FjMjBlZWFhMzZmNGYyYmFiNDNiYTk0NDg5OTc.:
    SIP/2.0 408 Request Timeout
    Via: SIP/2.0/UDP 172.26.102.20:5060;branch=z9hG4bK-d8754z-b9140a659650756a-1---d8754z-;rport
    To: <sip:3891@172.26.102.20>;tag=4456925e
    From: "REDACTED"<sip:360XXXXXXX@172.26.102.20:5060;nf=e>;tag=4b45e57a
    Call-ID: ODM1Y2FjMjBlZWFhMzZmNGYyYmFiNDNiYTk0NDg5OTc.
    CSeq: 1 INVITE
    Content-Length: 0
    02-Oct-2015 15:34:53.684 Session 370463 has failed in leg L:1350.2[Extn] ; Cause: 408 Request Timeout/INVITE from local
    02-Oct-2015 15:33:50.623 Endpoint Extn:3891 has added contact <sip:3891@172.26.102.134:5060> for device Dev(586):[sip:3891@172.26.102.134:5060;user=phone / 3891]
    02-Oct-2015 15:33:50.623 [CM504001]: Endpoint Extn:3891: new contact is registered. Contact(s): [sip:3891@172.26.102.134:5060 / 3891]
    02-Oct-2015 15:33:49.577 L:1350.2[Extn]: Terminating targets, reason: SIP ;cause=200 ;text="Call terminated on user request"
    02-Oct-2015 15:33:30.883 Provisional response arrived for session 370463 of Leg L:1350.2[Extn]
    02-Oct-2015 15:33:30.883 L:1350.2[Extn] got Provisional Recv 180/INVITE from 172.26.102.134:5060 tid=b9140a659650756a Call-ID=ODM1Y2FjMjBlZWFhMzZmNGYyYmFiNDNiYTk0NDg5OTc.:
    SIP/2.0 180 Ringing
    Via: SIP/2.0/UDP 172.26.102.20:5060;branch=z9hG4bK-d8754z-b9140a659650756a-1---d8754z-;rport=5060
    Contact: <sip:3891@172.26.102.134:5060;user=phone>
    To: <sip:3891@172.26.102.20>;tag=1881986813
    From: "REDACTED "<sip:360XXXXXXX@172.26.102.20:5060;nf=e>;tag=4b45e57a
    Call-ID: ODM1Y2FjMjBlZWFhMzZmNGYyYmFiNDNiYTk0NDg5OTc.
    CSeq: 1 INVITE
    Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, INFO, REFER, UPDATE, MESSAGE
    Supported: replaces, path, timer, eventlist
    User-Agent: Grandstream GXV3275 1.0.3.46
    Allow-Events: talk, hold
    Content-Length: 0
    02-Oct-2015 15:33:30.882 [CM505001]: Endpoint Extn:3891: Device info: Device Identified: [Man: Grandstream;Mod: GXV Series;Rev: General] Capabilities:[reinvite, no-replaces, unable-no-sdp, recvonly] UserAgent: [Grandstream GXV3275 1.0.3.46] PBX contact: [sip:3891@172.26.102.20:5060]
    02-Oct-2015 15:33:30.882 [CM503002]: Call(C:1350): Alerting Extn:3891 by contact <sip:3891@172.26.102.134:5060>
    02-Oct-2015 15:33:30.881 UacSession 370463 has formed leg L:1350.2[Extn]
    02-Oct-2015 15:33:30.781 [CM503025]: Call(C:1350): Calling T:Extn:3891@[Dev:sip:3891@172.26.102.134:5060;user=phone] for L:1350.1[Line:10000<<360XXXXXXX]
    02-Oct-2015 15:33:30.781 Route to L:1350.2[Extn] sends Invite-OUT Send Req INVITE from 0.0.0.0:0 tid=3e369306a4584b59 Call-ID=ODM1Y2FjMjBlZWFhMzZmNGYyYmFiNDNiYTk0NDg5OTc.:
    INVITE sip:3891@172.26.102.134:5060;user=phone SIP/2.0
    Via: SIP/2.0/ ;branch=z9hG4bK-d8754z-3e369306a4584b59-1---d8754z-;rport
    Max-Forwards: 70
    Contact: <sip:360XXXXXXX@172.26.102.20:5060>
    To: <sip:3891@172.26.102.20>
    From: "REDACTED"<sip:360XXXXXXX@172.26.102.20:5060;nf=e>;tag=4b45e57a
    Call-ID: ODM1Y2FjMjBlZWFhMzZmNGYyYmFiNDNiYTk0NDg5OTc.
    CSeq: 1 INVITE
    Alert-Info: <http://www.notused.invalidtld>;info=external
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE
    Content-Type: application/sdp
    Supported: replaces
    Content-Length: 280


    I do notice the line in bold, but am not sure what to make of it yet. Has anyone else had a problem like this?

    Thanks, TJ
     
  2. lneblett

    lneblett Well-Known Member

    Joined:
    Sep 7, 2010
    Messages:
    2,064
    Likes Received:
    58
    One item that I noticed is :
    02-Oct-2015 15:33:50.623 Endpoint Extn:3891 has added contact <sip:3891@172.26.102.134:5060> for device Dev(586):[sip:3891@172.26.102.134:5060;user=phone / 3891]
    02-Oct-2015 15:33:50.623 [CM504001]: Endpoint Extn:3891: new contact is registered. Contact(s): [sip:3891@172.26.102.134:5060 / 3891]

    This was some 20 seconds into the call, so am uncertain if the phone was into its normal registration or if it had some issue that caused it.

    I also noticed that the same extension had IP 172.26.102.20 (To: <sip:3891@172.26.102.20>), but I assume this to be the 3CX server given that when the call went to Vmail, the VM extension was also on that same IP.

    You might want to look at the extension settings and see how the settings for re-invite and replace headers are set and then do some testing by toggling same. I do not know that this will help, but possibly?
     
Thread Status:
Not open for further replies.