Can somone help me with this debug?

VitalPBX Community Support General Discussion Can somone help me with this debug?

  • Post
    PolycomNoob
    Participant

    Some of my Polycom ip335 are rebooting nonstop, and so others are not!

    Thanks, guys! 

     

    [2019-05-30 19:58:58] NOTICE[7284]: chan_sip.c:30416 sip_poke_noanswer: Peer ‘601’ is now UNREACHABLE! Last qualify: 15
    Really destroying SIP dialog ’60f32b0c2b68ff061dca12e13653dfb8@192.168.1.208:5060′ Method: OPTIONS
    Retransmitting #6 (no NAT) to 192.168.1.203:5060:
    NOTIFY sip:601@192.168.1.203 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.208:5060;branch=z9hG4bK278ad527
    Max-Forwards: 70
    From: “asterisk” <sip:asterisk@192.168.1.208>;tag=as464a2a5c
    To: <sip:601@192.168.1.203>
    Contact: <sip:asterisk@192.168.1.208:5060>
    Call-ID: 2bedd5a91d726e814208129c2d3817c5@192.168.1.208:5060
    CSeq: 102 NOTIFY
    User-Agent: VitalPBX
    Event: message-summary
    Content-Type: application/simple-message-summary
    Content-Length: 89

    Messages-Waiting: yes
    Message-Account: sip:*97@192.168.1.208
    Voice-Message: 4/0 (0/0)


    Retransmitting #6 (no NAT) to 192.168.1.203:5060:
    NOTIFY sip:601@192.168.1.203 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.208:5060;branch=z9hG4bK27931ddc
    Max-Forwards: 70
    From: “asterisk” <sip:asterisk@192.168.1.208>;tag=as74fd4fd0
    To: <sip:601@192.168.1.203>
    Contact: <sip:asterisk@192.168.1.208:5060>
    Call-ID: 3bc2897e75244c79505e60397809e52b@192.168.1.208:5060
    CSeq: 102 NOTIFY
    User-Agent: VitalPBX
    Event: message-summary
    Content-Type: application/simple-message-summary
    Content-Length: 89

    Messages-Waiting: yes
    Message-Account: sip:*97@192.168.1.208
    Voice-Message: 4/0 (0/0)


    [2019-05-30 19:59:01] WARNING[7284]: chan_sip.c:4119 retrans_pkt: Retransmission timeout reached on transmission 2bedd5a91d726e814208129c2d3817c5@192.168.1.208:5060 for seqno 10 2 (Non-critical Request) — See https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions
    Packet timed out after 6399ms with no response
    [2019-05-30 19:59:01] WARNING[7284]: chan_sip.c:4119 retrans_pkt: Retransmission timeout reached on transmission 3bc2897e75244c79505e60397809e52b@192.168.1.208:5060 for seqno 10 2 (Non-critical Request) — See https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions
    Packet timed out after 6400ms with no response
    Really destroying SIP dialog ‘2bedd5a91d726e814208129c2d3817c5@192.168.1.208:5060’ Method: NOTIFY
    Really destroying SIP dialog ‘3bc2897e75244c79505e60397809e52b@192.168.1.208:5060’ Method: NOTIFY
    Reliably Transmitting (no NAT) to 192.168.1.203:5060:
    OPTIONS sip:601@192.168.1.203 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.208:5060;branch=z9hG4bK2003a1e0
    Max-Forwards: 70
    From: “asterisk” <sip:asterisk@192.168.1.208>;tag=as0962d2c5
    To: <sip:601@192.168.1.203>
    Contact: <sip:asterisk@192.168.1.208:5060>
    Call-ID: 4275f8e60bc586a2087721a0175147c5@192.168.1.208:5060
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 31 May 2019 00:59:08 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Content-Length: 0


    Retransmitting #1 (no NAT) to 192.168.1.203:5060:
    OPTIONS sip:601@192.168.1.203 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.208:5060;branch=z9hG4bK2003a1e0
    Max-Forwards: 70
    From: “asterisk” <sip:asterisk@192.168.1.208>;tag=as0962d2c5
    To: <sip:601@192.168.1.203>
    Contact: <sip:asterisk@192.168.1.208:5060>
    Call-ID: 4275f8e60bc586a2087721a0175147c5@192.168.1.208:5060
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 31 May 2019 00:59:08 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Content-Length: 0


    Retransmitting #2 (no NAT) to 192.168.1.203:5060:
    OPTIONS sip:601@192.168.1.203 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.208:5060;branch=z9hG4bK2003a1e0
    Max-Forwards: 70
    From: “asterisk” <sip:asterisk@192.168.1.208>;tag=as0962d2c5
    To: <sip:601@192.168.1.203>
    Contact: <sip:asterisk@192.168.1.208:5060>
    Call-ID: 4275f8e60bc586a2087721a0175147c5@192.168.1.208:5060
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 31 May 2019 00:59:08 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Content-Length: 0


    Retransmitting #3 (no NAT) to 192.168.1.203:5060:
    OPTIONS sip:601@192.168.1.203 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.208:5060;branch=z9hG4bK2003a1e0
    Max-Forwards: 70
    From: “asterisk” <sip:asterisk@192.168.1.208>;tag=as0962d2c5
    To: <sip:601@192.168.1.203>
    Contact: <sip:asterisk@192.168.1.208:5060>
    Call-ID: 4275f8e60bc586a2087721a0175147c5@192.168.1.208:5060
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 31 May 2019 00:59:08 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Content-Length: 0


    Retransmitting #4 (no NAT) to 192.168.1.203:5060:
    OPTIONS sip:601@192.168.1.203 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.208:5060;branch=z9hG4bK2003a1e0
    Max-Forwards: 70
    From: “asterisk” <sip:asterisk@192.168.1.208>;tag=as0962d2c5
    To: <sip:601@192.168.1.203>
    Contact: <sip:asterisk@192.168.1.208:5060>
    Call-ID: 4275f8e60bc586a2087721a0175147c5@192.168.1.208:5060
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 31 May 2019 00:59:08 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Content-Length: 0


    Really destroying SIP dialog ‘4275f8e60bc586a2087721a0175147c5@192.168.1.208:5060’ Method: OPTIONS
    Reliably Transmitting (no NAT) to 192.168.1.203:5060:
    OPTIONS sip:601@192.168.1.203 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.208:5060;branch=z9hG4bK251a769b
    Max-Forwards: 70
    From: “asterisk” <sip:asterisk@192.168.1.208>;tag=as10fd6314
    To: <sip:601@192.168.1.203>
    Contact: <sip:asterisk@192.168.1.208:5060>
    Call-ID: 4d55810e03a410d2638b1c0451949b52@192.168.1.208:5060
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 31 May 2019 00:59:22 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Content-Length: 0


    Retransmitting #1 (no NAT) to 192.168.1.203:5060:
    OPTIONS sip:601@192.168.1.203 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.208:5060;branch=z9hG4bK251a769b
    Max-Forwards: 70
    From: “asterisk” <sip:asterisk@192.168.1.208>;tag=as10fd6314
    To: <sip:601@192.168.1.203>
    Contact: <sip:asterisk@192.168.1.208:5060>
    Call-ID: 4d55810e03a410d2638b1c0451949b52@192.168.1.208:5060
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 31 May 2019 00:59:22 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Content-Length: 0


    Retransmitting #2 (no NAT) to 192.168.1.203:5060:
    OPTIONS sip:601@192.168.1.203 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.208:5060;branch=z9hG4bK251a769b
    Max-Forwards: 70
    From: “asterisk” <sip:asterisk@192.168.1.208>;tag=as10fd6314
    To: <sip:601@192.168.1.203>
    Contact: <sip:asterisk@192.168.1.208:5060>
    Call-ID: 4d55810e03a410d2638b1c0451949b52@192.168.1.208:5060
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 31 May 2019 00:59:22 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Content-Length: 0


    Retransmitting #3 (no NAT) to 192.168.1.203:5060:
    OPTIONS sip:601@192.168.1.203 SIP/2.0
    Via: SIP/2
    .0/UDP 192.168.1.208:5060;branch=z9hG4bK251a769b
    Max-Forwards: 70
    From: “asterisk” <sip:asterisk@192.168.1.208>;tag=as10fd6314
    To: <sip:601@192.168.1.203>
    Contact: <sip:asterisk@192.168.1.208:5060>
    Call-ID: 4d55810e03a410d2638b1c0451949b52@192.168.1.208:5060
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 31 May 2019 00:59:22 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Content-Length: 0


    Retransmitting #4 (no NAT) to 192.168.1.203:5060:
    OPTIONS sip:601@192.168.1.203 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.208:5060;branch=z9hG4bK251a769b
    Max-Forwards: 70
    From: “asterisk” <sip:asterisk@192.168.1.208>;tag=as10fd6314
    To: <sip:601@192.168.1.203>
    Contact: <sip:asterisk@192.168.1.208:5060>
    Call-ID: 4d55810e03a410d2638b1c0451949b52@192.168.1.208:5060
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 31 May 2019 00:59:22 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Content-Length: 0


    Really destroying SIP dialog ‘4d55810e03a410d2638b1c0451949b52@192.168.1.208:5060’ Method: OPTIONS

    <— SIP read from UDP:192.168.1.203:5060 —>
    REGISTER sip:192.168.1.208:5060 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.203;branch=z9hG4bKbd010bf8C05B0C53
    From: “Garage” <sip:601@192.168.1.208>;tag=5D06ECB2-D191DA6D
    To: <sip:601@192.168.1.208>
    CSeq: 1 REGISTER
    Call-ID: 52a5367e-cb3eb579-f60b8444@192.168.1.203
    Contact: <sip:601@192.168.1.203>;methods=”INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER”
    User-Agent: PolycomSoundPointIP-SPIP_335-UA/3.2.4.0267
    Accept-Language: en
    Max-Forwards: 70
    Expires: 120
    Content-Length: 0

    <————->
    — (12 headers 0 lines) —
    Sending to 192.168.1.203:5060 (no NAT)
    Sending to 192.168.1.203:5060 (no NAT)

    <— Transmitting (no NAT) to 192.168.1.203:5060 —>
    SIP/2.0 401 Unauthorized
    Via: SIP/2.0/UDP 192.168.1.203;branch=z9hG4bKbd010bf8C05B0C53;received=192.168.1.203
    From: “Garage” <sip:601@192.168.1.208>;tag=5D06ECB2-D191DA6D
    To: <sip:601@192.168.1.208>;tag=as4e48f5bc
    Call-ID: 52a5367e-cb3eb579-f60b8444@192.168.1.203
    CSeq: 1 REGISTER
    Server: VitalPBX
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    WWW-Authenticate: Digest algorithm=MD5, realm=”asterisk”, nonce=”5417b484″
    Content-Length: 0

    <————>
    Scheduling destruction of SIP dialog ’52a5367e-cb3eb579-f60b8444@192.168.1.203′ in 32000 ms (Method: REGISTER)

    <— SIP read from UDP:192.168.1.203:5060 —>
    REGISTER sip:192.168.1.208:5060 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.203;branch=z9hG4bK5c6f6ddf3E190D4A
    From: “Garage” <sip:601@192.168.1.208>;tag=5D06ECB2-D191DA6D
    To: <sip:601@192.168.1.208>
    CSeq: 2 REGISTER
    Call-ID: 52a5367e-cb3eb579-f60b8444@192.168.1.203
    Contact: <sip:601@192.168.1.203>;methods=”INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER”
    User-Agent: PolycomSoundPointIP-SPIP_335-UA/3.2.4.0267
    Accept-Language: en
    Authorization: Digest username=”601″, realm=”asterisk”, nonce=”5417b484″, uri=”sip:192.168.1.208:5060″, response=”dc7d608b1f629b06c7a512054a4e3e46″, algorithm=MD5
    Max-Forwards: 70
    Expires: 120
    Content-Length: 0

    <————->
    — (13 headers 0 lines) —
    Sending to 192.168.1.203:5060 (no NAT)
    Reliably Transmitting (no NAT) to 192.168.1.203:5060:
    OPTIONS sip:601@192.168.1.203 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.208:5060;branch=z9hG4bK19ba5b4c
    Max-Forwards: 70
    From: “asterisk” <sip:asterisk@192.168.1.208>;tag=as21941fd5
    To: <sip:601@192.168.1.203>
    Contact: <sip:asterisk@192.168.1.208:5060>
    Call-ID: 5d231f0337c40b71127185621d4ca72f@192.168.1.208:5060
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 31 May 2019 00:59:31 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Content-Length: 0

    <— Transmitting (no NAT) to 192.168.1.203:5060 —>
    SIP/2.0 200 OK
    Via: SIP/2.0/UDP 192.168.1.203;branch=z9hG4bK5c6f6ddf3E190D4A;received=192.168.1.203
    From: “Garage” <sip:601@192.168.1.208>;tag=5D06ECB2-D191DA6D
    To: <sip:601@192.168.1.208>;tag=as4e48f5bc
    Call-ID: 52a5367e-cb3eb579-f60b8444@192.168.1.203
    CSeq: 2 REGISTER
    Server: VitalPBX
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Expires: 120
    Contact: <sip:601@192.168.1.203>;expires=120
    Date: Fri, 31 May 2019 00:59:31 GMT
    Content-Length: 0

    <————>
    Scheduling destruction of SIP dialog ’52a5367e-cb3eb579-f60b8444@192.168.1.203′ in 32000 ms (Method: REGISTER)

    <— SIP read from UDP:192.168.1.203:5060 —>
    SIP/2.0 200 OK
    Via: SIP/2.0/UDP 192.168.1.208:5060;branch=z9hG4bK19ba5b4c
    From: “asterisk” <sip:asterisk@192.168.1.208>;tag=as21941fd5
    To: “Garage” <sip:601@192.168.1.203>;tag=CCDFE990-71536C6B
    CSeq: 102 OPTIONS
    Call-ID: 5d231f0337c40b71127185621d4ca72f@192.168.1.208:5060
    Contact: <sip:601@192.168.1.203>
    Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER
    Supported: 100rel,replaces,100rel,timer,replaces,norefersub
    User-Agent: PolycomSoundPointIP-SPIP_335-UA/3.2.4.0267
    Accept-Language: en
    Accept: application/sdp,text/plain,message/sipfrag,application/dialog-info+xml
    Accept-Encoding: identity
    Content-Length: 0

    <————->
    — (14 headers 0 lines) —
    [2019-05-30 19:59:32] NOTICE[7284]: chan_sip.c:24879 handle_response_peerpoke: Peer ‘601’ is now Reachable. (15ms / 2000ms)
    Really destroying SIP dialog ‘5d231f0337c40b71127185621d4ca72f@192.168.1.208:5060’ Method: OPTIONS
    Really destroying SIP dialog ’52a5367e-cb3eb579-f60b8444@192.168.1.203′ Method: REGISTER
    Reliably Transmitting (no NAT) to 192.168.1.203:5060:
    OPTIONS sip:601@192.168.1.203 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.208:5060;branch=z9hG4bK1a71e81a
    Max-Forwards: 70
    From: “asterisk” <sip:asterisk@192.168.1.208>;tag=as25c98e11
    To: <sip:601@192.168.1.203>
    Contact: <sip:asterisk@192.168.1.208:5060>
    Call-ID: 22f53a247397ccc2374fafb56b47abd8@192.168.1.208:5060
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 31 May 2019 01:00:32 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Content-Length: 0


    Retransmitting #1 (no NAT) to 192.168.1.203:5060:
    OPTIONS sip:601@192.168.1.203 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.208:5060;branch=z9hG4bK1a71e81a
    Max-Forwards: 70
    From: “asterisk” <sip:asterisk@192.168.1.208>;tag=as25c98e11
    To: <sip:601@192.168.1.203>
    Contact: <sip:asterisk@192.168.1.208:5060>
    Call-ID: 22f53a247397ccc2374fafb56b47abd8@192.168.1.208:5060
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 31 May 2019 01:00:32 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Content-Length: 0


    Retransmitting #2 (no NAT) to 192.168.1.203:5060:
    OPTIONS sip:601@192.168.1.203 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.208:5060;branch=z9hG4bK1a71e81a
    Max-Forwards: 70
    From: “asterisk” <sip:asterisk@192.168.1.208>;tag=as25c98e11
    To: <sip:601@192.168.1.203>
    Co
    ntact: <sip:asterisk@192.168.1.208:5060>
    Call-ID: 22f53a247397ccc2374fafb56b47abd8@192.168.1.208:5060
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 31 May 2019 01:00:32 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Content-Length: 0


    Retransmitting #3 (no NAT) to 192.168.1.203:5060:
    OPTIONS sip:601@192.168.1.203 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.208:5060;branch=z9hG4bK1a71e81a
    Max-Forwards: 70
    From: “asterisk” <sip:asterisk@192.168.1.208>;tag=as25c98e11
    To: <sip:601@192.168.1.203>
    Contact: <sip:asterisk@192.168.1.208:5060>
    Call-ID: 22f53a247397ccc2374fafb56b47abd8@192.168.1.208:5060
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 31 May 2019 01:00:32 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Content-Length: 0


    Retransmitting #4 (no NAT) to 192.168.1.203:5060:
    OPTIONS sip:601@192.168.1.203 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.208:5060;branch=z9hG4bK1a71e81a
    Max-Forwards: 70
    From: “asterisk” <sip:asterisk@192.168.1.208>;tag=as25c98e11
    To: <sip:601@192.168.1.203>
    Contact: <sip:asterisk@192.168.1.208:5060>
    Call-ID: 22f53a247397ccc2374fafb56b47abd8@192.168.1.208:5060
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 31 May 2019 01:00:32 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Content-Length: 0


    [2019-05-30 20:00:36] NOTICE[7284]: chan_sip.c:30416 sip_poke_noanswer: Peer ‘601’ is now UNREACHABLE! Last qualify: 15
    Really destroying SIP dialog ’22f53a247397ccc2374fafb56b47abd8@192.168.1.208:5060′ Method: OPTIONS
    [2019-05-30 20:00:39] NOTICE[7284]: chan_sip.c:15823 sip_reregister: — Re-registration for 251980_local@chicago2.voip.ms
    [2019-05-30 20:00:40] NOTICE[7284]: chan_sip.c:24831 handle_response_register: Outbound Registration: Expiry for chicago2.voip.ms is 120 sec (Scheduling reregistration in 105 s)
    Reliably Transmitting (no NAT) to 192.168.1.203:5060:
    OPTIONS sip:601@192.168.1.203 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.208:5060;branch=z9hG4bK70b6fc1c
    Max-Forwards: 70
    From: “asterisk” <sip:asterisk@192.168.1.208>;tag=as62c61830
    To: <sip:601@192.168.1.203>
    Contact: <sip:asterisk@192.168.1.208:5060>
    Call-ID: 6a94ec3947901e0e31d08d2410e3ce26@192.168.1.208:5060
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 31 May 2019 01:00:46 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Content-Length: 0


    Retransmitting #1 (no NAT) to 192.168.1.203:5060:
    OPTIONS sip:601@192.168.1.203 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.208:5060;branch=z9hG4bK70b6fc1c
    Max-Forwards: 70
    From: “asterisk” <sip:asterisk@192.168.1.208>;tag=as62c61830
    To: <sip:601@192.168.1.203>
    Contact: <sip:asterisk@192.168.1.208:5060>
    Call-ID: 6a94ec3947901e0e31d08d2410e3ce26@192.168.1.208:5060
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 31 May 2019 01:00:46 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Content-Length: 0

    <— SIP read from UDP:192.168.1.203:5060 —>
    REGISTER sip:192.168.1.208:5060 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.203;branch=z9hG4bKbd010bf8C05B0C53
    From: “Garage” <sip:601@192.168.1.208>;tag=5D06ECB2-D191DA6D
    To: <sip:601@192.168.1.208>
    CSeq: 1 REGISTER
    Call-ID: 52a5367e-cb3eb579-f60b8444@192.168.1.203
    Contact: <sip:601@192.168.1.203>;methods=”INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER”
    User-Agent: PolycomSoundPointIP-SPIP_335-UA/3.2.4.0267
    Accept-Language: en
    Max-Forwards: 70
    Expires: 120
    Content-Length: 0

    <————->
    — (12 headers 0 lines) —
    Sending to 192.168.1.203:5060 (no NAT)
    Sending to 192.168.1.203:5060 (no NAT)

    <— Transmitting (no NAT) to 192.168.1.203:5060 —>
    SIP/2.0 401 Unauthorized
    Via: SIP/2.0/UDP 192.168.1.203;branch=z9hG4bKbd010bf8C05B0C53;received=192.168.1.203
    From: “Garage” <sip:601@192.168.1.208>;tag=5D06ECB2-D191DA6D
    To: <sip:601@192.168.1.208>;tag=as166f3d0d
    Call-ID: 52a5367e-cb3eb579-f60b8444@192.168.1.203
    CSeq: 1 REGISTER
    Server: VitalPBX
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    WWW-Authenticate: Digest algorithm=MD5, realm=”asterisk”, nonce=”7181705b”
    Content-Length: 0

    <————>
    Scheduling destruction of SIP dialog ’52a5367e-cb3eb579-f60b8444@192.168.1.203′ in 32000 ms (Method: REGISTER)

    <— SIP read from UDP:192.168.1.203:5060 —>
    REGISTER sip:192.168.1.208:5060 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.203;branch=z9hG4bK5c6f6ddf3E190D4A
    From: “Garage” <sip:601@192.168.1.208>;tag=5D06ECB2-D191DA6D
    To: <sip:601@192.168.1.208>
    CSeq: 2 REGISTER
    Call-ID: 52a5367e-cb3eb579-f60b8444@192.168.1.203
    Contact: <sip:601@192.168.1.203>;methods=”INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER”
    User-Agent: PolycomSoundPointIP-SPIP_335-UA/3.2.4.0267
    Accept-Language: en
    Authorization: Digest username=”601″, realm=”asterisk”, nonce=”7181705b”, uri=”sip:192.168.1.208:5060″, response=”c65c33a3f03d7f58d4d8dba8769ae70e”, algorithm=MD5
    Max-Forwards: 70
    Expires: 120
    Content-Length: 0

    <————->
    — (13 headers 0 lines) —
    Sending to 192.168.1.203:5060 (no NAT)
    [2019-05-30 20:00:47] NOTICE[7284]: chan_sip.c:30487 sip_poke_peer: Still have a QUALIFY dialog active, deleting
    Reliably Transmitting (no NAT) to 192.168.1.203:5060:
    OPTIONS sip:601@192.168.1.203 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.208:5060;branch=z9hG4bK488a1b41
    Max-Forwards: 70
    From: “asterisk” <sip:asterisk@192.168.1.208>;tag=as61972eb1
    To: <sip:601@192.168.1.203>
    Contact: <sip:asterisk@192.168.1.208:5060>
    Call-ID: 6b06237b1e522f246b9fb0f851728277@192.168.1.208:5060
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 31 May 2019 01:00:47 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Content-Length: 0

    <— Transmitting (no NAT) to 192.168.1.203:5060 —>
    SIP/2.0 200 OK
    Via: SIP/2.0/UDP 192.168.1.203;branch=z9hG4bK5c6f6ddf3E190D4A;received=192.168.1.203
    From: “Garage” <sip:601@192.168.1.208>;tag=5D06ECB2-D191DA6D
    To: <sip:601@192.168.1.208>;tag=as166f3d0d
    Call-ID: 52a5367e-cb3eb579-f60b8444@192.168.1.203
    CSeq: 2 REGISTER
    Server: VitalPBX
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Expires: 120
    Contact: <sip:601@192.168.1.203>;expires=120
    Date: Fri, 31 May 2019 01:00:47 GMT
    Content-Length: 0

    <————>
    Scheduling destruction of SIP dialog ’52a5367e-cb3eb579-f60b8444@192.168.1.203′ in 32000 ms (Method: REGISTER)
    Really destroying SIP dialog ‘6a94ec3947901e0e31d08d2410e3ce26@192.168.1.208:5060’ Method: OPTIONS

    <— SIP read from UDP:192.168.1.203:5060 —>
    SIP/2.0 200 OK
    Via: SIP/2.0/UDP 192.168.1.208:5060;branch=z9hG4bK488a1b41
    From: “asterisk” <sip:asterisk@192.168.1.208>;tag=as61972eb1
    To: “Garage” <sip:601@192.168.1.203>;tag=CCDFE990-71536C6B
    CSeq: 102 OPTIONS
    Call-ID: 6b06237b1e522f246b9fb0f851728277@192.
    168.1.208:5060
    Contact: <sip:601@192.168.1.203>
    Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER
    Supported: 100rel,replaces,100rel,timer,replaces,norefersub
    User-Agent: PolycomSoundPointIP-SPIP_335-UA/3.2.4.0267
    Accept-Language: en
    Accept: application/sdp,text/plain,message/sipfrag,application/dialog-info+xml
    Accept-Encoding: identity
    Content-Length: 0

     

     

    0
Viewing 1 replies (of 1 total)
  • Replies
Viewing 1 replies (of 1 total)
  • You must be logged in to reply to this topic.