Patton Unregistered

Discussion in '3CX Phone System - General' started by mike49749, May 24, 2015.

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

    Joined:
    May 24, 2015
    Messages:
    1
    Likes Received:
    0
    We are having issues with our 4114 FXO becoming unregistered from our 3CX System.

    It had been working fine until just recently when all lines would unregister. I’m also unable to access the unit at its IP of 192.168.1.128. I have cycled the unit several times with no success. Stopping and starting 3CX services does not work either.

    Here is a snippet of the verbose log. Any insight would be appreciated.
    23-May-2015 18:12:37.408 Update Queue: 806; reg exts: [107,103,101,100]
    23-May-2015 18:12:37.407 Update Queue: 805; reg exts: [100,101,104,102]
    23-May-2015 18:12:36.692 Update Queue: 804; reg exts: [105,100,104,101]
    23-May-2015 18:12:36.692 Update Queue: 800; reg exts: [100,101,104,102]
    23-May-2015 18:11:58.843 Best route: next hop=192.168.1.1 if=12 on transp: 192.168.1.1
    23-May-2015 18:11:58.843 STUN server stun3.3cx.com has IP:192.95.0.175
    23-May-2015 18:11:58.810 STUN server stun2.3cx.com has IP:94.198.96.7
    23-May-2015 18:11:58.775 STUN server stun.3cx.com has IP:198.50.247.220
    23-May-2015 18:08:06.964 Update Queue: 806; reg exts: [107,103,101,100]
    23-May-2015 18:08:06.964 Update Queue: 805; reg exts: [100,101,104,102]
    23-May-2015 18:08:06.250 Update Queue: 804; reg exts: [105,100,104,101]
    23-May-2015 18:08:06.250 Update Queue: 800; reg exts: [100,101,104,102]
    23-May-2015 18:03:36.518 Update Queue: 806; reg exts: [107,103,101,100]
    23-May-2015 18:03:36.518 Update Queue: 805; reg exts: [100,101,104,102]
    23-May-2015 18:03:35.804 Update Queue: 804; reg exts: [105,100,104,101]
    23-May-2015 18:03:35.804 Update Queue: 800; reg exts: [100,101,104,102]
    23-May-2015 17:59:06.082 Update Queue: 806; reg exts: [107,103,101,100]
    23-May-2015 17:59:06.082 Update Queue: 805; reg exts: [100,101,104,102]
    23-May-2015 17:59:05.369 Update Queue: 804; reg exts: [105,100,104,101]
    23-May-2015 17:59:05.368 Update Queue: 800; reg exts: [100,101,104,102]
    23-May-2015 17:54:35.642 Update Queue: 806; reg exts: [107,103,101,100]
    23-May-2015 17:54:35.642 Update Queue: 805; reg exts: [100,101,104,102]
    23-May-2015 17:54:34.927 Update Queue: 804; reg exts: [105,100,104,101]
    23-May-2015 17:54:34.927 Update Queue: 800; reg exts: [100,101,104,102]
    23-May-2015 17:53:56.526 L:141.2[Line:10000>>6250234]: Terminating targets, reason: SIP ;cause=200 ;text="Call terminated on user request"
    23-May-2015 17:53:56.526 Blocking refers for the Call(C:141)
    23-May-2015 17:53:56.526 Call(C:141) is terminated
    23-May-2015 17:53:56.525 ~Target=PSTNline:6250234@(Ln.10000@Patton 4114)
    23-May-2015 17:53:56.525 ~Route=Dev:sip:10003@192.168.1.128:5063
    23-May-2015 17:53:56.525 ~Route=Dev:sip:10002@192.168.1.128:5062
    23-May-2015 17:53:56.525 ~Route=Dev:sip:10001@192.168.1.128:5061
    23-May-2015 17:53:56.525 ~Route=Dev:sip:10000@192.168.1.128:5060
    23-May-2015 17:53:56.525 L:141.2[Line:10000>>6250234]: Terminating targets, reason: SIP ;cause=487 ;text="Request Terminated"
    23-May-2015 17:53:56.525 Reason: SIP ;cause=487 ;text="Request Terminated"
    23-May-2015 17:53:56.525 L:141.1[Extn]: Terminating targets, reason: SIP ;cause=487 ;text="Request Terminated"
    23-May-2015 17:53:56.524 L:141.1[Extn] got Terminated Recv Req CANCEL from 192.168.1.123:5062 tid=1492443615 Call-ID=2094005624@192.168.1.123:
    CANCEL sip:6250234@192.168.1.5:5060 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.123:5062;branch=z9hG4bK1492443615
    Max-Forwards: 70
    To: <sip:6250234@192.168.1.5>
    From: "Parts Dept"<sip:106@192.168.1.5>;tag=667177693
    Call-ID: 2094005624@192.168.1.123
    CSeq: 2 CANCEL
    User-Agent: Yealink SIP-T26P 6.72.0.51
    Content-Length: 0
    23-May-2015 17:53:56.524 Terminated from "Parts Dept"<sip:106@192.168.1.5>;tag=667177693 to <sip:6250234@192.168.1.5>;tag=047dcf02; reason: RemoteBye
    23-May-2015 17:53:56.524 L:141.1[Extn] Sending: OnSendResp Send 487/INVITE from 0.0.0.0:0 tid=1492443615 Call-ID=2094005624@192.168.1.123:
    SIP/2.0 487 Request Terminated
    Via: SIP/2.0/UDP 192.168.1.123:5062;branch=z9hG4bK1492443615
    To: <sip:6250234@192.168.1.5>;tag=047dcf02
    From: "Parts Dept"<sip:106@192.168.1.5>;tag=667177693
    Call-ID: 2094005624@192.168.1.123
    CSeq: 2 INVITE
    Content-Length: 0
    23-May-2015 17:53:56.524 SendMsg from <sip:6250234@192.168.1.5>;tag=047dcf02 to "Parts Dept"<sip:106@192.168.1.5>;tag=667177693
    23-May-2015 17:53:56.524 L:141.1[Extn] Sending: OnSendResp Send 200/CANCEL from 0.0.0.0:0 tid=1492443615 Call-ID=2094005624@192.168.1.123:
    SIP/2.0 200 OK
    Via: SIP/2.0/UDP 192.168.1.123:5062;branch=z9hG4bK1492443615
    Contact: <sip:6250234@192.168.1.5:5060>
    To: <sip:6250234@192.168.1.5>;tag=047dcf02
    From: "Parts Dept"<sip:106@192.168.1.5>;tag=667177693
    Call-ID: 2094005624@192.168.1.123
    CSeq: 2 CANCEL
    Content-Length: 0
    23-May-2015 17:53:56.524 SendMsg from <sip:6250234@192.168.1.5>;tag=047dcf02 to "Parts Dept"<sip:106@192.168.1.5>;tag=667177693
    23-May-2015 17:53:42.759 Route to L:141.2[Line:10000>>6250234] sends Invite-OUT Send Req INVITE from 0.0.0.0:0 tid=025f812aee77f47d Call-ID=YTdmYmFhNzUxOGE4MmY3MzhlODUxNzE5Njc2YzczMDg.:
    INVITE sip:6250234@192.168.1.128:5060 SIP/2.0
    Via: SIP/2.0/ ;branch=z9hG4bK-d8754z-025f812aee77f47d-1---d8754z-;rport
    Max-Forwards: 70
    Contact: <sip:10000@192.168.1.5:5060>
    To: <sip:6250234@192.168.1.128:5060>
    From: "Parts Dept"<sip:10000@192.168.1.5:5060>;tag=a074772b
    Call-ID: YTdmYmFhNzUxOGE4MmY3MzhlODUxNzE5Njc2YzczMDg.
    CSeq: 1 INVITE
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE
    Content-Type: application/sdp
    Supported: replaces
    Content-Length: 332

    v=0
    o=3cxPS 536921243648 512493617153 IN IP4 192.168.1.5
    s=3cxPS Audio call
    c=IN IP4 192.168.1.123
    t=0 0
    m=audio 11792 RTP/AVP 0 8 9 18 101
    a=rtpmap:0 PCMU/8000
    a=rtpmap:8 PCMA/8000
    a=rtpmap:9 G722/8000
    a=rtpmap:18 G729/8000
    a=fmtp:18 annexb=no
    a=fmtp:101 0-15
    a=rtpmap:101 telephone-event/8000
    a=ptime:20
    a=sendrecv
    23-May-2015 17:53:42.754 Outbound URI is used: sip:10000@192.168.1.128:5060
    23-May-2015 17:53:42.754 SLA is globally disabled
    23-May-2015 17:53:42.754 Added leg L:141.2[Line:10000>>6250234]
    23-May-2015 17:53:42.710 [Flow] Call(C:141): making call from L:141.1[Extn] to T:Line:10000>>6250234@[Dev:sip:10000@192.168.1.128:5060,Dev:sip:10001@192.168.1.128:5061,Dev:sip:10002@192.168.1.128:5062,Dev:sip:10003@192.168.1.128:5063]
    23-May-2015 17:53:42.710 Caller '106' is found in the list of allowed extensions: 100-107
    23-May-2015 17:53:42.710 Looking for outbound rule: dialed = [6250234], processed: [6250234]; from-ext:
    23-May-2015 17:53:42.710 [Flow] Building target endpoint to 6250234 from "Parts Dept" <sip:106@192.168.1.5:5060>
    23-May-2015 17:53:42.710 Remote SDP is set for leg L:141.1[Extn]
    23-May-2015 17:53:42.710 OnOffer from "Parts Dept"<sip:106@192.168.1.5>;tag=667177693
    23-May-2015 17:53:42.709 Inbound DID: ''; Phonebook Name: ''
    23-May-2015 17:53:42.704 Outbound URI is used: sip:106@192.168.1.123:5062
    23-May-2015 17:53:42.704 IncomingCall: C:141 from <sip:106@192.168.1.5:5060> to <sip:6250234@192.168.1.5:5060>
    23-May-2015 17:53:42.704 Added leg L:C:141.1[No endpoint yet]
    23-May-2015 17:53:42.704 UasSession 41108 started
    23-May-2015 17:53:42.704 Call from "Parts Dept"<sip:106@192.168.1.5>;tag=667177693 to <sip:6250234@192.168.1.5>;tag=047dcf02
    23-May-2015 17:51:58.678 Best route: next hop=192.168.1.1 if=12 on transp: 192.168.1.1
    23-May-2015 17:51:58.678 STUN server stun3.3cx.com has IP:192.95.0.175
    23-May-2015 17:51:58.628 STUN server stun2.3cx.com has IP:94.198.96.7
    23-May-2015 17:51:58.594 STUN server stun.3cx.com has IP:198.50.247.220
    23-May-2015 17:50:32.488 IPs do not match!
    23-May-2015 17:50:32.488 Compare IPs: incoming=192.168.1.128; external=0.0.0.0
    23-May-2015 17:50:32.488 IPs do not match!
    23-May-2015 17:50:32.488 Compare IPs: incoming=192.168.1.128; external=0.0.0.0
    23-May-2015 17:50:32.488 IPs do not match!
     
  2. CentrexJ

    CentrexJ Member

    Joined:
    May 5, 2009
    Messages:
    380
    Likes Received:
    50
    If you can't reach it by its ip it is either reset itself to dhcp or defective. Try the Patton discovery tool and see if it can find it. Otherwise contact Patton for repair. If out of warranty they have post warranty repair options.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.