Reply To: RE: Setting up FXO for outbound calls

VitalPBX Community Support General Discussion Setting up FXO for outbound calls Reply To: RE: Setting up FXO for outbound calls

    mmcs
    Participant

    Followup asterisk log

    8.1.126;rport=63347
    From: <sip:303@192.168.1.149:25069>;tag=l4qd8azu61
    To: <sip:702@192.168.1.149:25069;user=phone>;tag=as34ae58ab
    Call-ID: bf9d195b2343-b374j1ddupdb@snomSoft-000413FFFFFF
    CSeq: 31 SUBSCRIBE
    Server: VitalPBX
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Expires: 3600
    Contact: <sip:702@192.168.1.149:25069>;expires=3600
    Content-Length: 0

    <————>
    set_destination: Parsing <sip:303@192.168.1.126:63347;line=ojn9itpa> for address/port to send to
    set_destination: set destination to 192.168.1.126:63347
    Reliably Transmitting (no NAT) to 192.168.1.126:63347:
    NOTIFY sip:303@192.168.1.126:63347;line=ojn9itpa SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.149:25069;branch=z9hG4bK0f82f563;rport
    Max-Forwards: 70
    From: <sip:702@192.168.1.149:25069;user=phone>;tag=as34ae58ab
    To: <sip:303@192.168.1.149:25069>;tag=l4qd8azu61
    Contact: <sip:702@192.168.1.149:25069>
    Call-ID: bf9d195b2343-b374j1ddupdb@snomSoft-000413FFFFFF
    CSeq: 117 NOTIFY
    User-Agent: VitalPBX
    Subscription-State: active
    Event: dialog
    Content-Type: application/dialog-info+xml
    Content-Length: 211

    <?xml version=”1.0″?>
    <dialog-info xmlns=”urn:ietf:params:xml:ns:dialog-info” version=”15″ state=”full” entity=”sip:702@192.168.1.149:25069″>
    <dialog id=”702″>
    <state>terminated</state>
    </dialog>
    </dialog-info>

    <— SIP read from UDP:192.168.1.126:63347 —>
    SIP/2.0 200 Ok
    Via: SIP/2.0/UDP 192.168.1.149:25069;branch=z9hG4bK0f82f563;rport=25069
    From: <sip:702@192.168.1.149:25069;user=phone>;tag=as34ae58ab
    To: <sip:303@192.168.1.149:25069>;tag=l4qd8azu61
    Call-ID: bf9d195b2343-b374j1ddupdb@snomSoft-000413FFFFFF
    CSeq: 117 NOTIFY
    Content-Length: 0

    <————->
    — (7 headers 0 lines) —

    <— SIP read from UDP:192.168.1.126:63347 —>
    SUBSCRIBE sip:703@192.168.1.149:25069;user=phone SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.126:63347;branch=z9hG4bK-h21w1tw9jt05;rport
    From: <sip:303@192.168.1.149:25069>;tag=r2dqkncf98
    To: <sip:703@192.168.1.149:25069;user=phone>;tag=as0ad4c65a
    Call-ID: bf9d195b2343-t0pauad4cq11@snomSoft-000413FFFFFF
    CSeq: 30 SUBSCRIBE
    Max-Forwards: 70
    Contact: <sip:303@192.168.1.126:63347;line=ojn9itpa>;flow-id=1
    Event: dialog
    Accept: application/dialog-info+xml
    Expires: 3600
    Content-Length: 0

    <————->
    — (12 headers 0 lines) —
    Found peer ‘303’ for ‘303’ from 192.168.1.126:63347

    <— Transmitting (no NAT) to 192.168.1.126:63347 —>
    SIP/2.0 401 Unauthorized
    Via: SIP/2.0/UDP 192.168.1.126:63347;branch=z9hG4bK-h21w1tw9jt05;received=192.168.1.126;rport=63347
    From: <sip:303@192.168.1.149:25069>;tag=r2dqkncf98
    To: <sip:703@192.168.1.149:25069;user=phone>;tag=as0ad4c65a
    Call-ID: bf9d195b2343-t0pauad4cq11@snomSoft-000413FFFFFF
    CSeq: 30 SUBSCRIBE
    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=”52737ec0″
    Content-Length: 0

    <————>
    Scheduling destruction of SIP dialog ‘bf9d195b2343-t0pauad4cq11@snomSoft-000413FFFFFF’ in 6400 ms (Method: SUBSCRIBE)

    <— SIP read from UDP:192.168.1.126:63347 —>
    SUBSCRIBE sip:703@192.168.1.149:25069;user=phone SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.126:63347;branch=z9hG4bK-z43nr5q2arch;rport
    From: <sip:303@192.168.1.149:25069>;tag=r2dqkncf98
    To: <sip:703@192.168.1.149:25069;user=phone>;tag=as0ad4c65a
    Call-ID: bf9d195b2343-t0pauad4cq11@snomSoft-000413FFFFFF
    CSeq: 31 SUBSCRIBE
    Max-Forwards: 70
    Contact: <sip:303@192.168.1.126:63347;line=ojn9itpa>;flow-id=1
    Event: dialog
    Accept: application/dialog-info+xml
    Authorization: Digest username=”303″,realm=”asterisk”,nonce=”52737ec0″,uri=”sip:703@192.168.1.149:25069;user=phone”,response=”6255c3aa661053ebd72a69d4a22967dc”,algorithm=md5
    Expires: 3600
    Content-Length: 0

    <————->
    — (13 headers 0 lines) —
    Found peer ‘303’ for ‘303’ from 192.168.1.126:63347
    Looking for 703 in cos-all (domain 192.168.1.149)
    Scheduling destruction of SIP dialog ‘bf9d195b2343-t0pauad4cq11@snomSoft-000413FFFFFF’ in 3610000 ms (Method: SUBSCRIBE)

    <— Transmitting (no NAT) to 192.168.1.126:63347 —>
    SIP/2.0 200 OK
    Via: SIP/2.0/UDP 192.168.1.126:63347;branch=z9hG4bK-z43nr5q2arch;received=192.168.1.126;rport=63347
    From: <sip:303@192.168.1.149:25069>;tag=r2dqkncf98
    To: <sip:703@192.168.1.149:25069;user=phone>;tag=as0ad4c65a
    Call-ID: bf9d195b2343-t0pauad4cq11@snomSoft-000413FFFFFF
    CSeq: 31 SUBSCRIBE
    Server: VitalPBX
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Expires: 3600
    Contact: <sip:703@192.168.1.149:25069>;expires=3600
    Content-Length: 0

    <————>
    set_destination: Parsing <sip:303@192.168.1.126:63347;line=ojn9itpa> for address/port to send to
    set_destination: set destination to 192.168.1.126:63347
    Reliably Transmitting (no NAT) to 192.168.1.126:63347:
    NOTIFY sip:303@192.168.1.126:63347;line=ojn9itpa SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.149:25069;branch=z9hG4bK799ca2e1;rport
    Max-Forwards: 70
    From: <sip:703@192.168.1.149:25069;user=phone>;tag=as0ad4c65a
    To: <sip:303@192.168.1.149:25069>;tag=r2dqkncf98
    Contact: <sip:703@192.168.1.149:25069>
    Call-ID: bf9d195b2343-t0pauad4cq11@snomSoft-000413FFFFFF
    CSeq: 117 NOTIFY
    User-Agent: VitalPBX
    Subscription-State: active
    Event: dialog
    Content-Type: application/dialog-info+xml
    Content-Length: 211

    <?xml version=”1.0″?>
    <dialog-info xmlns=”urn:ietf:params:xml:ns:dialog-info” version=”15″ state=”full” entity=”sip:703@192.168.1.149:25069″>
    <dialog id=”703″>
    <state>terminated</state>
    </dialog>
    </dialog-info>

    <— SIP read from UDP:192.168.1.126:63347 —>
    SIP/2.0 200 Ok
    Via: SIP/2.0/UDP 192.168.1.149:25069;branch=z9hG4bK799ca2e1;rport=25069
    From: <sip:703@192.168.1.149:25069;user=phone>;tag=as0ad4c65a
    To: <sip:303@192.168.1.149:25069>;tag=r2dqkncf98
    Call-ID: bf9d195b2343-t0pauad4cq11@snomSoft-000413FFFFFF
    CSeq: 117 NOTIFY
    Content-Length: 0

    <————->
    — (7 headers 0 lines) —
    Retransmitting #4 (no NAT) to 204.11.192.134:5060:
    OPTIONS sip:doll5.callcentric.com SIP/2.0
    Via: SIP/2.0/UDP 70.27.176.52:25069;branch=z9hG4bK757e53c3
    Max-Forwards: 70
    From: “asterisk” <sip:17778376747@70.27.176.52:25069>;tag=as1ba12148
    To: <sip:doll5.callcentric.com>
    Contact: <sip:17778376747@70.27.176.52:25069>
    Call-ID: 10465dd2443522fc5d5a1b9b60707b5c@70.27.176.52:25069
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 08 Jun 2018 04:34:43 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Content-Length: 0


    Really destroying SIP dialog ‘10465dd2443522fc5d5a1b9b60707b5c@70.27.176.52:25069’ Method: OPTIONS
    [2018-06-08 00:34:47] DEBUG[3797]: chan_sip.c:22347 sip_dump_history:
    ———- SIP HISTORY for ‘10465dd2443522fc5d5a1b9b60707b5c@70.27.176.52:25069’
    [2018-06-08 00:34:47] DEBUG[3797]: chan_sip.c:22351 sip_dump_history: * SIP Call
    [2018-06-08 00:34:47] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 001. TxReqRel OPTIONS / 1
    02 OPTIONS – OPTIONS
    [2018-06-08 00:34:47] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 002. ReTx 1000 OPTIONS sip:doll5.callcentric.com SIP/2.0
    [2018-06-08 00:34:47] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 003. ReTx 1000 OPTIONS sip:doll5.callcentric.com SIP/2.0
    [2018-06-08 00:34:47] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 004. ReTx 1000 OPTIONS sip:doll5.callcentric.com SIP/2.0
    [2018-06-08 00:34:47] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 005. ReTx 1000 OPTIONS sip:doll5.callcentric.com SIP/2.0
    [2018-06-08 00:34:47] DEBUG[3797]: chan_sip.c:22360 sip_dump_history:
    ———- END SIP HISTORY for ‘10465dd2443522fc5d5a1b9b60707b5c@70.27.176.52:25069’
    Retransmitting #4 (no NAT) to 204.11.192.133:5060:
    OPTIONS sip:doll4.callcentric.com SIP/2.0
    Via: SIP/2.0/UDP 70.27.176.52:25069;branch=z9hG4bK2329c363
    Max-Forwards: 70
    From: “asterisk” <sip:17778376747@70.27.176.52:25069>;tag=as1a4b09d1
    To: <sip:doll4.callcentric.com>
    Contact: <sip:17778376747@70.27.176.52:25069>
    Call-ID: 52a2e9f413a890bb067bf64813cdb60e@70.27.176.52:25069
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 08 Jun 2018 04:34:43 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Content-Length: 0


    Really destroying SIP dialog ’52a2e9f413a890bb067bf64813cdb60e@70.27.176.52:25069′ Method: OPTIONS
    [2018-06-08 00:34:47] DEBUG[3797]: chan_sip.c:22347 sip_dump_history:
    ———- SIP HISTORY for ’52a2e9f413a890bb067bf64813cdb60e@70.27.176.52:25069′
    [2018-06-08 00:34:47] DEBUG[3797]: chan_sip.c:22351 sip_dump_history: * SIP Call
    [2018-06-08 00:34:47] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 001. TxReqRel OPTIONS / 102 OPTIONS – OPTIONS
    [2018-06-08 00:34:47] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 002. ReTx 1000 OPTIONS sip:doll4.callcentric.com SIP/2.0
    [2018-06-08 00:34:47] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 003. ReTx 1000 OPTIONS sip:doll4.callcentric.com SIP/2.0
    [2018-06-08 00:34:47] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 004. ReTx 1000 OPTIONS sip:doll4.callcentric.com SIP/2.0
    [2018-06-08 00:34:47] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 005. ReTx 1000 OPTIONS sip:doll4.callcentric.com SIP/2.0
    [2018-06-08 00:34:47] DEBUG[3797]: chan_sip.c:22360 sip_dump_history:
    ———- END SIP HISTORY for ’52a2e9f413a890bb067bf64813cdb60e@70.27.176.52:25069′
    Retransmitting #4 (no NAT) to 204.11.192.132:5060:
    OPTIONS sip:doll3.callcentric.com SIP/2.0
    Via: SIP/2.0/UDP 70.27.176.52:25069;branch=z9hG4bK46fd62a7
    Max-Forwards: 70
    From: “asterisk” <sip:17778376747@70.27.176.52:25069>;tag=as50ad3c53
    To: <sip:doll3.callcentric.com>
    Contact: <sip:17778376747@70.27.176.52:25069>
    Call-ID: 1963268865e6ab094c121c1d107e145c@70.27.176.52:25069
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 08 Jun 2018 04:34:43 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Content-Length: 0


    Really destroying SIP dialog ‘1963268865e6ab094c121c1d107e145c@70.27.176.52:25069’ Method: OPTIONS
    [2018-06-08 00:34:47] DEBUG[3797]: chan_sip.c:22347 sip_dump_history:
    ———- SIP HISTORY for ‘1963268865e6ab094c121c1d107e145c@70.27.176.52:25069’
    [2018-06-08 00:34:47] DEBUG[3797]: chan_sip.c:22351 sip_dump_history: * SIP Call
    [2018-06-08 00:34:47] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 001. TxReqRel OPTIONS / 102 OPTIONS – OPTIONS
    [2018-06-08 00:34:47] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 002. ReTx 1000 OPTIONS sip:doll3.callcentric.com SIP/2.0
    [2018-06-08 00:34:47] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 003. ReTx 1000 OPTIONS sip:doll3.callcentric.com SIP/2.0
    [2018-06-08 00:34:47] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 004. ReTx 1000 OPTIONS sip:doll3.callcentric.com SIP/2.0
    [2018-06-08 00:34:47] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 005. ReTx 1000 OPTIONS sip:doll3.callcentric.com SIP/2.0
    [2018-06-08 00:34:47] DEBUG[3797]: chan_sip.c:22360 sip_dump_history:
    ———- END SIP HISTORY for ‘1963268865e6ab094c121c1d107e145c@70.27.176.52:25069’
    [2018-06-08 00:34:48] NOTICE[3797]: chan_sip.c:15753 sip_reregister: — Re-registration for 17778376747@callcentric.com
    REGISTER 12 headers, 0 lines
    Reliably Transmitting (no NAT) to 204.11.192.38:5060:
    REGISTER sip:callcentric.com SIP/2.0
    Via: SIP/2.0/UDP 70.27.176.52:25069;branch=z9hG4bK4538aac2
    Max-Forwards: 70
    From: <sip:17778376747@callcentric.com>;tag=as0639dd20
    To: <sip:17778376747@callcentric.com>
    Call-ID: 5dbf0590744338383b91f39d1f00bbe8@192.168.1.149
    CSeq: 162 REGISTER
    Supported: replaces, timer
    User-Agent: VitalPBX
    Authorization: Digest username=”17778376747″, realm=”callcentric.com”, algorithm=MD5, uri=”sip:sip:callcentric.com”, nonce=”4777db1c929d80cb7cb271c957b9c4d0″, response=”495017cafc94cf28567aed2f4ae64fc4″
    Expires: 120
    Contact: <sip:17778376747@70.27.176.52:25069>
    Content-Length: 0

    <— SIP read from UDP:204.11.192.38:5060 —>
    SIP/2.0 407 Proxy Authentication Required
    v: SIP/2.0/UDP 70.27.176.52:25069;branch=z9hG4bK4538aac2
    f: <sip:17778376747@callcentric.com>;tag=as0639dd20
    t: <sip:17778376747@callcentric.com>
    i: 5dbf0590744338383b91f39d1f00bbe8@192.168.1.149
    CSeq: 162 REGISTER
    Proxy-Authenticate: Digest realm=”callcentric.com”, domain=”sip:callcentric.com”, nonce=”81256542efe122996b7ba6d857f270df”, opaque=””, stale=TRUE, algorithm=MD5
    l: 0

    <————->
    — (8 headers 0 lines) —
    Responding to challenge, registration to domain/host name callcentric.com
    REGISTER 12 headers, 0 lines
    Reliably Transmitting (no NAT) to 204.11.192.38:5060:
    REGISTER sip:callcentric.com SIP/2.0
    Via: SIP/2.0/UDP 70.27.176.52:25069;branch=z9hG4bK326021b2
    Max-Forwards: 70
    From: <sip:17778376747@callcentric.com>;tag=as0639dd20
    To: <sip:17778376747@callcentric.com>
    Call-ID: 5dbf0590744338383b91f39d1f00bbe8@192.168.1.149
    CSeq: 163 REGISTER
    Supported: replaces, timer
    User-Agent: VitalPBX
    Proxy-Authorization: Digest username=”17778376747″, realm=”callcentric.com”, algorithm=MD5, uri=”sip:sip:callcentric.com”, nonce=”81256542efe122996b7ba6d857f270df”, response=”7dd3c19d958d3cd079d85afeeb2fc672″
    Expires: 120
    Contact: <sip:17778376747@70.27.176.52:25069>
    Content-Length: 0

    <— SIP read from UDP:204.11.192.38:5060 —>
    SIP/2.0 200 Ok
    v: SIP/2.0/UDP 70.27.176.52:25069;branch=z9hG4bK326021b2
    f: <sip:17778376747@callcentric.com>;tag=as0639dd20
    t: <sip:17778376747@callcentric.com>
    i: 5dbf0590744338383b91f39d1f00bbe8@192.168.1.149
    CSeq: 163 REGISTER
    m: <sip:17778376747@70.27.176.52:25069>;expires=60
    l: 0

    <————->
    — (8 headers 0 lines) —
    [2018-06-08 00:34:48] NOTICE[3797]: chan_sip.c:24591 handle_response_register: Outbound Registration: Expiry for callcentric.com is 60 sec (Scheduling reregistration in 45 s)
    Really destroying SIP dialog ‘5dbf0590744338383b91f39d1f00bbe8@192.168.1.149’ Method: REGISTER
    [2018-06-08 00:34:48] DEBUG[3797]: chan_sip.c:22347 sip_dump_history:
    ———- SIP HISTORY for ‘5dbf0590744338383b91f39d1f00bbe8@192.168.1.149’
    [2018-06-08 00:34:48] DEBUG[3797]: chan_sip.c:22351 sip_dump_history: * SIP Call
    [2018-06-08 00:34:48] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 001. RegistryInit Account: 17778376747@callcentric.com
    [2018-06-08 00:34:48] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 002. AuthResp Auth response sent for 17778376747 in realm callcentric.com – n
    [2018-06-08 00:34:48] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 003. TxReqRe
    l REGISTER / 162 REGISTER – REGISTER
    [2018-06-08 00:34:48] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 004. Rx SIP/2.0 / 162 REGISTER / 407 Proxy Authentication Required
    [2018-06-08 00:34:48] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 005. AuthResp Auth response sent for 17778376747 in realm callcentric.com – n
    [2018-06-08 00:34:48] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 006. RegistryAuth Try: 1
    [2018-06-08 00:34:48] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 007. TxReqRel REGISTER / 163 REGISTER – REGISTER
    [2018-06-08 00:34:48] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 008. Rx SIP/2.0 / 163 REGISTER / 200 Ok
    [2018-06-08 00:34:48] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 009. NeedDestroy Setting needdestroy because Registration successfull
    [2018-06-08 00:34:48] DEBUG[3797]: chan_sip.c:22360 sip_dump_history:
    ———- END SIP HISTORY for ‘5dbf0590744338383b91f39d1f00bbe8@192.168.1.149’
    Retransmitting #4 (no NAT) to 192.168.1.149:5060:
    REGISTER sip:192.168.1.149 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.149:25069;branch=z9hG4bK6297ada6
    Max-Forwards: 70
    From: <sip:310@192.168.1.149>;tag=as0ee36123
    To: <sip:310@192.168.1.149>
    Call-ID: 37eb67f31d99933716e88fc063090695@192.168.1.149
    CSeq: 186 REGISTER
    Supported: replaces, timer
    User-Agent: VitalPBX
    Expires: 120
    Contact: <sip:310@192.168.1.149:25069>
    Content-Length: 0

    <— SIP read from UDP:192.168.1.141:25069 —>

    <————->
    Retransmitting #5 (no NAT) to 192.168.1.149:5060:
    REGISTER sip:192.168.1.149 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.149:25069;branch=z9hG4bK6297ada6
    Max-Forwards: 70
    From: <sip:310@192.168.1.149>;tag=as0ee36123
    To: <sip:310@192.168.1.149>
    Call-ID: 37eb67f31d99933716e88fc063090695@192.168.1.149
    CSeq: 186 REGISTER
    Supported: replaces, timer
    User-Agent: VitalPBX
    Expires: 120
    Contact: <sip:310@192.168.1.149:25069>
    Content-Length: 0


    Reliably Transmitting (no NAT) to 192.168.1.149:5060:
    OPTIONS sip:310@192.168.1.147:5060 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.149:25069;branch=z9hG4bK655d3c8c
    Max-Forwards: 70
    From: “asterisk” <sip:asterisk@192.168.1.149:25069>;tag=as280d954b
    To: <sip:310@192.168.1.147:5060>
    Contact: <sip:asterisk@192.168.1.149:25069>
    Call-ID: 5c44dc006757f9fb55ae402c6e6f16b8@192.168.1.149:25069
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 08 Jun 2018 04:34:55 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.149:5060:
    OPTIONS sip:310@192.168.1.147:5060 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.149:25069;branch=z9hG4bK655d3c8c
    Max-Forwards: 70
    From: “asterisk” <sip:asterisk@192.168.1.149:25069>;tag=as280d954b
    To: <sip:310@192.168.1.147:5060>
    Contact: <sip:asterisk@192.168.1.149:25069>
    Call-ID: 5c44dc006757f9fb55ae402c6e6f16b8@192.168.1.149:25069
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 08 Jun 2018 04:34:55 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Content-Length: 0


    Retransmitting #6 (no NAT) to 192.168.1.149:5060:
    REGISTER sip:192.168.1.149 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.149:25069;branch=z9hG4bK6297ada6
    Max-Forwards: 70
    From: <sip:310@192.168.1.149>;tag=as0ee36123
    To: <sip:310@192.168.1.149>
    Call-ID: 37eb67f31d99933716e88fc063090695@192.168.1.149
    CSeq: 186 REGISTER
    Supported: replaces, timer
    User-Agent: VitalPBX
    Expires: 120
    Contact: <sip:310@192.168.1.149:25069>
    Content-Length: 0


    Reliably Transmitting (no NAT) to 204.11.192.134:5060:
    OPTIONS sip:doll5.callcentric.com SIP/2.0
    Via: SIP/2.0/UDP 70.27.176.52:25069;branch=z9hG4bK252d71a6
    Max-Forwards: 70
    From: “asterisk” <sip:17778376747@70.27.176.52:25069>;tag=as4e4bcc65
    To: <sip:doll5.callcentric.com>
    Contact: <sip:17778376747@70.27.176.52:25069>
    Call-ID: 14fcf5e417c80ca857ca9e57509c44ce@70.27.176.52:25069
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 08 Jun 2018 04:34:57 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Content-Length: 0


    Reliably Transmitting (no NAT) to 204.11.192.133:5060:
    OPTIONS sip:doll4.callcentric.com SIP/2.0
    Via: SIP/2.0/UDP 70.27.176.52:25069;branch=z9hG4bK79af07e3
    Max-Forwards: 70
    From: “asterisk” <sip:17778376747@70.27.176.52:25069>;tag=as5919c05b
    To: <sip:doll4.callcentric.com>
    Contact: <sip:17778376747@70.27.176.52:25069>
    Call-ID: 1753fdf2512fb51c5a4c7e391d7eb708@70.27.176.52:25069
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 08 Jun 2018 04:34:57 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Content-Length: 0


    Reliably Transmitting (no NAT) to 204.11.192.132:5060:
    OPTIONS sip:doll3.callcentric.com SIP/2.0
    Via: SIP/2.0/UDP 70.27.176.52:25069;branch=z9hG4bK1c2b95f3
    Max-Forwards: 70
    From: “asterisk” <sip:17778376747@70.27.176.52:25069>;tag=as364bead9
    To: <sip:doll3.callcentric.com>
    Contact: <sip:17778376747@70.27.176.52:25069>
    Call-ID: 431d1e5c33f4013273a039c517782c57@70.27.176.52:25069
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 08 Jun 2018 04:34:57 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.149:5060:
    OPTIONS sip:310@192.168.1.147:5060 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.149:25069;branch=z9hG4bK655d3c8c
    Max-Forwards: 70
    From: “asterisk” <sip:asterisk@192.168.1.149:25069>;tag=as280d954b
    To: <sip:310@192.168.1.147:5060>
    Contact: <sip:asterisk@192.168.1.149:25069>
    Call-ID: 5c44dc006757f9fb55ae402c6e6f16b8@192.168.1.149:25069
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 08 Jun 2018 04:34:55 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Content-Length: 0


    Retransmitting #1 (no NAT) to 204.11.192.134:5060:
    OPTIONS sip:doll5.callcentric.com SIP/2.0
    Via: SIP/2.0/UDP 70.27.176.52:25069;branch=z9hG4bK252d71a6
    Max-Forwards: 70
    From: “asterisk” <sip:17778376747@70.27.176.52:25069>;tag=as4e4bcc65
    To: <sip:doll5.callcentric.com>
    Contact: <sip:17778376747@70.27.176.52:25069>
    Call-ID: 14fcf5e417c80ca857ca9e57509c44ce@70.27.176.52:25069
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 08 Jun 2018 04:34:57 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Content-Length: 0


    Retransmitting #1 (no NAT) to 204.11.192.133:5060:
    OPTIONS sip:doll4.callcentric.com SIP/2.0
    Via: SIP/2.0/UDP 70.27.176.52:25069;branch=z9hG4bK79af07e3
    Max-Forwards: 70
    From: “asterisk” <sip:17778376747@70.27.176.52:25069>;tag=as5919c05b
    To: <sip:doll4.callcentric.com>
    Contact: <sip:17778376747@70.27.176.52:25069>
    Call-ID: 1753fdf2512fb51c5a4c7e391d7eb708@70.27.176.52:25069
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 08 Jun 2018 04:34:57 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Content-Length: 0

    < br />—
    Retransmitting #1 (no NAT) to 204.11.192.132:5060:
    OPTIONS sip:doll3.callcentric.com SIP/2.0
    Via: SIP/2.0/UDP 70.27.176.52:25069;branch=z9hG4bK1c2b95f3
    Max-Forwards: 70
    From: “asterisk” <sip:17778376747@70.27.176.52:25069>;tag=as364bead9
    To: <sip:doll3.callcentric.com>
    Contact: <sip:17778376747@70.27.176.52:25069>
    Call-ID: 431d1e5c33f4013273a039c517782c57@70.27.176.52:25069
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 08 Jun 2018 04:34:57 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.1:13400 —>

    <————->
    Retransmitting #3 (no NAT) to 192.168.1.149:5060:
    OPTIONS sip:310@192.168.1.147:5060 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.149:25069;branch=z9hG4bK655d3c8c
    Max-Forwards: 70
    From: “asterisk” <sip:asterisk@192.168.1.149:25069>;tag=as280d954b
    To: <sip:310@192.168.1.147:5060>
    Contact: <sip:asterisk@192.168.1.149:25069>
    Call-ID: 5c44dc006757f9fb55ae402c6e6f16b8@192.168.1.149:25069
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 08 Jun 2018 04:34:55 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Content-Length: 0


    Retransmitting #2 (no NAT) to 204.11.192.134:5060:
    OPTIONS sip:doll5.callcentric.com SIP/2.0
    Via: SIP/2.0/UDP 70.27.176.52:25069;branch=z9hG4bK252d71a6
    Max-Forwards: 70
    From: “asterisk” <sip:17778376747@70.27.176.52:25069>;tag=as4e4bcc65
    To: <sip:doll5.callcentric.com>
    Contact: <sip:17778376747@70.27.176.52:25069>
    Call-ID: 14fcf5e417c80ca857ca9e57509c44ce@70.27.176.52:25069
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 08 Jun 2018 04:34:57 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Content-Length: 0


    Retransmitting #2 (no NAT) to 204.11.192.133:5060:
    OPTIONS sip:doll4.callcentric.com SIP/2.0
    Via: SIP/2.0/UDP 70.27.176.52:25069;branch=z9hG4bK79af07e3
    Max-Forwards: 70
    From: “asterisk” <sip:17778376747@70.27.176.52:25069>;tag=as5919c05b
    To: <sip:doll4.callcentric.com>
    Contact: <sip:17778376747@70.27.176.52:25069>
    Call-ID: 1753fdf2512fb51c5a4c7e391d7eb708@70.27.176.52:25069
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 08 Jun 2018 04:34:57 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Content-Length: 0


    Retransmitting #2 (no NAT) to 204.11.192.132:5060:
    OPTIONS sip:doll3.callcentric.com SIP/2.0
    Via: SIP/2.0/UDP 70.27.176.52:25069;branch=z9hG4bK1c2b95f3
    Max-Forwards: 70
    From: “asterisk” <sip:17778376747@70.27.176.52:25069>;tag=as364bead9
    To: <sip:doll3.callcentric.com>
    Contact: <sip:17778376747@70.27.176.52:25069>
    Call-ID: 431d1e5c33f4013273a039c517782c57@70.27.176.52:25069
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 08 Jun 2018 04:34:57 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.149:5060:
    OPTIONS sip:310@192.168.1.147:5060 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.149:25069;branch=z9hG4bK655d3c8c
    Max-Forwards: 70
    From: “asterisk” <sip:asterisk@192.168.1.149:25069>;tag=as280d954b
    To: <sip:310@192.168.1.147:5060>
    Contact: <sip:asterisk@192.168.1.149:25069>
    Call-ID: 5c44dc006757f9fb55ae402c6e6f16b8@192.168.1.149:25069
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 08 Jun 2018 04:34:55 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Content-Length: 0


    Really destroying SIP dialog ‘5c44dc006757f9fb55ae402c6e6f16b8@192.168.1.149:25069’ Method: OPTIONS
    [2018-06-08 00:34:59] DEBUG[3797]: chan_sip.c:22347 sip_dump_history:
    ———- SIP HISTORY for ‘5c44dc006757f9fb55ae402c6e6f16b8@192.168.1.149:25069’
    [2018-06-08 00:34:59] DEBUG[3797]: chan_sip.c:22351 sip_dump_history: * SIP Call
    [2018-06-08 00:34:59] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 001. TxReqRel OPTIONS / 102 OPTIONS – OPTIONS
    [2018-06-08 00:34:59] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 002. ReTx 1000 OPTIONS sip:310@192.168.1.147:5060 SIP/2.0
    [2018-06-08 00:34:59] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 003. ReTx 1000 OPTIONS sip:310@192.168.1.147:5060 SIP/2.0
    [2018-06-08 00:34:59] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 004. ReTx 1000 OPTIONS sip:310@192.168.1.147:5060 SIP/2.0
    [2018-06-08 00:34:59] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 005. ReTx 1000 OPTIONS sip:310@192.168.1.147:5060 SIP/2.0
    [2018-06-08 00:34:59] DEBUG[3797]: chan_sip.c:22360 sip_dump_history:
    ———- END SIP HISTORY for ‘5c44dc006757f9fb55ae402c6e6f16b8@192.168.1.149:25069’
    Retransmitting #3 (no NAT) to 204.11.192.134:5060:
    OPTIONS sip:doll5.callcentric.com SIP/2.0
    Via: SIP/2.0/UDP 70.27.176.52:25069;branch=z9hG4bK252d71a6
    Max-Forwards: 70
    From: “asterisk” <sip:17778376747@70.27.176.52:25069>;tag=as4e4bcc65
    To: <sip:doll5.callcentric.com>
    Contact: <sip:17778376747@70.27.176.52:25069>
    Call-ID: 14fcf5e417c80ca857ca9e57509c44ce@70.27.176.52:25069
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 08 Jun 2018 04:34:57 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Content-Length: 0


    Retransmitting #3 (no NAT) to 204.11.192.133:5060:
    OPTIONS sip:doll4.callcentric.com SIP/2.0
    Via: SIP/2.0/UDP 70.27.176.52:25069;branch=z9hG4bK79af07e3
    Max-Forwards: 70
    From: “asterisk” <sip:17778376747@70.27.176.52:25069>;tag=as5919c05b
    To: <sip:doll4.callcentric.com>
    Contact: <sip:17778376747@70.27.176.52:25069>
    Call-ID: 1753fdf2512fb51c5a4c7e391d7eb708@70.27.176.52:25069
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 08 Jun 2018 04:34:57 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Content-Length: 0


    Retransmitting #3 (no NAT) to 204.11.192.132:5060:
    OPTIONS sip:doll3.callcentric.com SIP/2.0
    Via: SIP/2.0/UDP 70.27.176.52:25069;branch=z9hG4bK1c2b95f3
    Max-Forwards: 70
    From: “asterisk” <sip:17778376747@70.27.176.52:25069>;tag=as364bead9
    To: <sip:doll3.callcentric.com>
    Contact: <sip:17778376747@70.27.176.52:25069>
    Call-ID: 431d1e5c33f4013273a039c517782c57@70.27.176.52:25069
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 08 Jun 2018 04:34:57 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Content-Length: 0


    Retransmitting #7 (no NAT) to 192.168.1.149:5060:
    REGISTER sip:192.168.1.149 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.149:25069;branch=z9hG4bK6297ada6
    Max-Forwards: 70
    From: <sip:310@192.168.1.149>;tag=as0ee36123
    To: <sip:310@192.168.1.149>
    Call-ID: 37eb67f31d99933716e88fc063090695@192.168.1.149
    CSeq: 186 REGISTER
    Supported: replaces, timer
    User-Agent: VitalPBX
    Expires: 120
    Contact: <sip:310@192.168.1.149:25069>
    Content-Length: 0


    Retransmitting #4 (no NAT) to 204.11.192.134:5060:
    OPTIONS sip:doll5.callcentric.com SIP/2.0
    Via: SIP/2.0/UDP 70.27.176.52:25069;branch=z9hG4bK252d71a6
    Max-Forwards: 70
    From: “asterisk” <sip:17778376747@70.27.176.52:25069>;tag=as4e4bcc65
    To: <sip:doll5.callcentric.com>
    Contact: <sip:17778376747@70.27.176.52:25069>
    Call-ID: 14fcf5e417c80ca857ca9e57509c44ce@70.27.176.52:25069
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 08 Jun 2018 04:34:57 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Content-Length: 0


    Retransmitting #4 (no NAT) to 204.11.192.133:5060:
    OPTIONS sip:doll4.callcentric.com SIP/2.0
    Via: SIP/2.0/UDP 70.27.176.52:25069;branch=z9hG4bK79af07e3
    Max-Forwards: 70
    From: “asterisk” <sip:17778376747@70.27.176.52:25069>;tag=as5919c05b
    To: <sip:doll4.callcentric.com>
    Contact: <sip:17778376747@70.27.176.52:25069>
    Call-ID: 1753fdf2512fb51c5a4c7e391d7eb708@70.27.176.52:25069
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 08 Jun 2018 04:34:57 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Content-Length: 0


    Really destroying SIP dialog ’14fcf5e417c80ca857ca9e57509c44ce@70.27.176.52:25069′ Method: OPTIONS
    [2018-06-08 00:35:01] DEBUG[3797]: chan_sip.c:22347 sip_dump_history:
    ———- SIP HISTORY for ’14fcf5e417c80ca857ca9e57509c44ce@70.27.176.52:25069′
    [2018-06-08 00:35:01] DEBUG[3797]: chan_sip.c:22351 sip_dump_history: * SIP Call
    [2018-06-08 00:35:01] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 001. TxReqRel OPTIONS / 102 OPTIONS – OPTIONS
    [2018-06-08 00:35:01] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 002. ReTx 1000 OPTIONS sip:doll5.callcentric.com SIP/2.0
    [2018-06-08 00:35:01] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 003. ReTx 1000 OPTIONS sip:doll5.callcentric.com SIP/2.0
    [2018-06-08 00:35:01] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 004. ReTx 1000 OPTIONS sip:doll5.callcentric.com SIP/2.0
    [2018-06-08 00:35:01] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 005. ReTx 1000 OPTIONS sip:doll5.callcentric.com SIP/2.0
    [2018-06-08 00:35:01] DEBUG[3797]: chan_sip.c:22360 sip_dump_history:
    ———- END SIP HISTORY for ’14fcf5e417c80ca857ca9e57509c44ce@70.27.176.52:25069′
    Really destroying SIP dialog ‘1753fdf2512fb51c5a4c7e391d7eb708@70.27.176.52:25069’ Method: OPTIONS
    [2018-06-08 00:35:01] DEBUG[3797]: chan_sip.c:22347 sip_dump_history:
    ———- SIP HISTORY for ‘1753fdf2512fb51c5a4c7e391d7eb708@70.27.176.52:25069’
    [2018-06-08 00:35:01] DEBUG[3797]: chan_sip.c:22351 sip_dump_history: * SIP Call
    [2018-06-08 00:35:01] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 001. TxReqRel OPTIONS / 102 OPTIONS – OPTIONS
    [2018-06-08 00:35:01] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 002. ReTx 1000 OPTIONS sip:doll4.callcentric.com SIP/2.0
    [2018-06-08 00:35:01] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 003. ReTx 1000 OPTIONS sip:doll4.callcentric.com SIP/2.0
    [2018-06-08 00:35:01] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 004. ReTx 1000 OPTIONS sip:doll4.callcentric.com SIP/2.0
    [2018-06-08 00:35:01] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 005. ReTx 1000 OPTIONS sip:doll4.callcentric.com SIP/2.0
    [2018-06-08 00:35:01] DEBUG[3797]: chan_sip.c:22360 sip_dump_history:
    ———- END SIP HISTORY for ‘1753fdf2512fb51c5a4c7e391d7eb708@70.27.176.52:25069’
    Retransmitting #4 (no NAT) to 204.11.192.132:5060:
    OPTIONS sip:doll3.callcentric.com SIP/2.0
    Via: SIP/2.0/UDP 70.27.176.52:25069;branch=z9hG4bK1c2b95f3
    Max-Forwards: 70
    From: “asterisk” <sip:17778376747@70.27.176.52:25069>;tag=as364bead9
    To: <sip:doll3.callcentric.com>
    Contact: <sip:17778376747@70.27.176.52:25069>
    Call-ID: 431d1e5c33f4013273a039c517782c57@70.27.176.52:25069
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 08 Jun 2018 04:34:57 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Content-Length: 0


    Really destroying SIP dialog ‘431d1e5c33f4013273a039c517782c57@70.27.176.52:25069’ Method: OPTIONS
    [2018-06-08 00:35:01] DEBUG[3797]: chan_sip.c:22347 sip_dump_history:
    ———- SIP HISTORY for ‘431d1e5c33f4013273a039c517782c57@70.27.176.52:25069’
    [2018-06-08 00:35:01] DEBUG[3797]: chan_sip.c:22351 sip_dump_history: * SIP Call
    [2018-06-08 00:35:01] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 001. TxReqRel OPTIONS / 102 OPTIONS – OPTIONS
    [2018-06-08 00:35:01] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 002. ReTx 1000 OPTIONS sip:doll3.callcentric.com SIP/2.0
    [2018-06-08 00:35:01] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 003. ReTx 1000 OPTIONS sip:doll3.callcentric.com SIP/2.0
    [2018-06-08 00:35:01] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 004. ReTx 1000 OPTIONS sip:doll3.callcentric.com SIP/2.0
    [2018-06-08 00:35:01] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 005. ReTx 1000 OPTIONS sip:doll3.callcentric.com SIP/2.0
    [2018-06-08 00:35:01] DEBUG[3797]: chan_sip.c:22360 sip_dump_history:
    ———- END SIP HISTORY for ‘431d1e5c33f4013273a039c517782c57@70.27.176.52:25069’
    REGISTER 11 headers, 0 lines
    Reliably Transmitting (no NAT) to 192.168.1.149:5060:
    REGISTER sip:192.168.1.149 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.149:25069;branch=z9hG4bK21655d35
    Max-Forwards: 70
    From: <sip:310@192.168.1.149>;tag=as0ee36123
    To: <sip:310@192.168.1.149>
    Call-ID: 37eb67f31d99933716e88fc063090695@192.168.1.149
    CSeq: 187 REGISTER
    Supported: replaces, timer
    User-Agent: VitalPBX
    Expires: 120
    Contact: <sip:310@192.168.1.149:25069>
    Content-Length: 0


    [2018-06-08 00:35:01] NOTICE[3797]: chan_sip.c:15906 sip_reg_timeout: — Registration for ‘310@192.168.1.149’ timed out, trying again (Attempt #86)
    Really destroying SIP dialog ’37eb67f31d99933716e88fc063090695@192.168.1.149′ Method: REGISTER
    [2018-06-08 00:35:01] DEBUG[3797]: chan_sip.c:22347 sip_dump_history:
    ———- SIP HISTORY for ’37eb67f31d99933716e88fc063090695@192.168.1.149′
    [2018-06-08 00:35:01] DEBUG[3797]: chan_sip.c:22351 sip_dump_history: * SIP Call
    [2018-06-08 00:35:01] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 001. RegistryInit Account: 310@192.168.1.149
    [2018-06-08 00:35:01] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 002. TxReqRel REGISTER / 186 REGISTER – REGISTER
    [2018-06-08 00:35:01] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 003. ReTx 1000 REGISTER sip:192.168.1.149 SIP/2.0
    [2018-06-08 00:35:01] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 004. ReTx 2000 REGISTER sip:192.168.1.149 SIP/2.0
    [2018-06-08 00:35:01] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 005. ReTx 4000 REGISTER sip:192.168.1.149 SIP/2.0
    [2018-06-08 00:35:01] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 006. ReTx 4000 REGISTER sip:192.168.1.149 SIP/2.0
    [2018-06-08 00:35:01] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 007. ReTx 4000 REGISTER sip:192.168.1.149 SIP/2.0
    [2018-06-08 00:35:01] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 008. ReTx 4000 REGISTER sip:192.168.1.149 SIP/2.0
    [2018-06-08 00:35:01] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 009. ReTx 4000 REGISTER sip:192.168.1.149 SIP/2.0
    [2018-06-08 00:35:01] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 010. NeedDestroy Setting needdestroy because registration timeout
    [2018-06-08 00:35:01] DEBUG[3797]: chan_sip.c:22360 sip_dump_history:
    ———- END SIP HISTORY for ’37eb67f31d99933716e88fc063090695@192.168.1.149′
    Reliably Transmitting (no NAT) to 192.168.1.143:25069:
    OPTIONS sip:203@192.168.1.143:25069 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.149:25069;branch=z9hG4bK1e2c1059
    Max-Forwards: 70
    From: “asterisk” <sip:asterisk@192.168.1.149:25069>;tag=as2901f67b
    To: <sip:203@192.168.1.143:25
    069>
    Contact: <sip:asterisk@192.168.1.149:25069>
    Call-ID: 469c49e36a3be6e36d1adf066963d176@192.168.1.149:25069
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 08 Jun 2018 04:35:02 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.149:5060:
    REGISTER sip:192.168.1.149 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.149:25069;branch=z9hG4bK21655d35
    Max-Forwards: 70
    From: <sip:310@192.168.1.149>;tag=as0ee36123
    To: <sip:310@192.168.1.149>
    Call-ID: 37eb67f31d99933716e88fc063090695@192.168.1.149
    CSeq: 187 REGISTER
    Supported: replaces, timer
    User-Agent: VitalPBX
    Expires: 120
    Contact: <sip:310@192.168.1.149:25069>
    Content-Length: 0

    <— SIP read from UDP:192.168.1.143:25069 —>
    SIP/2.0 200 OK
    Via: SIP/2.0/UDP 192.168.1.149:25069;branch=z9hG4bK1e2c1059
    From: “asterisk” <sip:asterisk@192.168.1.149:25069>;tag=as2901f67b
    To: <sip:203@192.168.1.143:25069>;tag=999215687
    Call-ID: 469c49e36a3be6e36d1adf066963d176@192.168.1.149:25069
    CSeq: 102 OPTIONS
    User-Agent: Yealink SIP-T26P 6.70.0.150
    Content-Length: 0

    <————->
    — (8 headers 0 lines) —
    Really destroying SIP dialog ‘469c49e36a3be6e36d1adf066963d176@192.168.1.149:25069’ Method: OPTIONS
    [2018-06-08 00:35:02] DEBUG[3797]: chan_sip.c:22347 sip_dump_history:
    ———- SIP HISTORY for ‘469c49e36a3be6e36d1adf066963d176@192.168.1.149:25069’
    [2018-06-08 00:35:02] DEBUG[3797]: chan_sip.c:22351 sip_dump_history: * SIP Call
    [2018-06-08 00:35:02] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 001. TxReqRel OPTIONS / 102 OPTIONS – OPTIONS
    [2018-06-08 00:35:02] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 002. Rx SIP/2.0 / 102 OPTIONS / 200 OK
    [2018-06-08 00:35:02] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 003. NeedDestroy Setting needdestroy because got OPTIONS response
    [2018-06-08 00:35:02] DEBUG[3797]: chan_sip.c:22360 sip_dump_history:
    ———- END SIP HISTORY for ‘469c49e36a3be6e36d1adf066963d176@192.168.1.149:25069’
    Retransmitting #2 (no NAT) to 192.168.1.149:5060:
    REGISTER sip:192.168.1.149 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.149:25069;branch=z9hG4bK21655d35
    Max-Forwards: 70
    From: <sip:310@192.168.1.149>;tag=as0ee36123
    To: <sip:310@192.168.1.149>
    Call-ID: 37eb67f31d99933716e88fc063090695@192.168.1.149
    CSeq: 187 REGISTER
    Supported: replaces, timer
    User-Agent: VitalPBX
    Expires: 120
    Contact: <sip:310@192.168.1.149:25069>
    Content-Length: 0


    Reliably Transmitting (no NAT) to 192.168.1.142:25069:
    OPTIONS sip:202@192.168.1.142:25069 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.149:25069;branch=z9hG4bK5b5d7018
    Max-Forwards: 70
    From: “asterisk” <sip:asterisk@192.168.1.149:25069>;tag=as6ad6ab93
    To: <sip:202@192.168.1.142:25069>
    Contact: <sip:asterisk@192.168.1.149:25069>
    Call-ID: 70623c4f7fe848ec3450949104689e84@192.168.1.149:25069
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 08 Jun 2018 04:35:03 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.142:25069 —>

    <————->

    <— SIP read from UDP:192.168.1.142:25069 —>
    SIP/2.0 200 OK
    Via: SIP/2.0/UDP 192.168.1.149:25069;branch=z9hG4bK5b5d7018
    From: “asterisk” <sip:asterisk@192.168.1.149:25069>;tag=as6ad6ab93
    To: <sip:202@192.168.1.142:25069>;tag=1134392826
    Call-ID: 70623c4f7fe848ec3450949104689e84@192.168.1.149:25069
    CSeq: 102 OPTIONS
    User-Agent: Yealink SIP-T26P 6.70.0.150
    Content-Length: 0

    <————->
    — (8 headers 0 lines) —
    Really destroying SIP dialog ‘70623c4f7fe848ec3450949104689e84@192.168.1.149:25069’ Method: OPTIONS
    [2018-06-08 00:35:03] DEBUG[3797]: chan_sip.c:22347 sip_dump_history:
    ———- SIP HISTORY for ‘70623c4f7fe848ec3450949104689e84@192.168.1.149:25069’
    [2018-06-08 00:35:03] DEBUG[3797]: chan_sip.c:22351 sip_dump_history: * SIP Call
    [2018-06-08 00:35:03] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 001. TxReqRel OPTIONS / 102 OPTIONS – OPTIONS
    [2018-06-08 00:35:03] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 002. Rx SIP/2.0 / 102 OPTIONS / 200 OK
    [2018-06-08 00:35:03] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 003. NeedDestroy Setting needdestroy because got OPTIONS response
    [2018-06-08 00:35:03] DEBUG[3797]: chan_sip.c:22360 sip_dump_history:
    ———- END SIP HISTORY for ‘70623c4f7fe848ec3450949104689e84@192.168.1.149:25069’
    Retransmitting #3 (no NAT) to 192.168.1.149:5060:
    REGISTER sip:192.168.1.149 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.149:25069;branch=z9hG4bK21655d35
    Max-Forwards: 70
    From: <sip:310@192.168.1.149>;tag=as0ee36123
    To: <sip:310@192.168.1.149>
    Call-ID: 37eb67f31d99933716e88fc063090695@192.168.1.149
    CSeq: 187 REGISTER
    Supported: replaces, timer
    User-Agent: VitalPBX
    Expires: 120
    Contact: <sip:310@192.168.1.149:25069>
    Content-Length: 0


    Retransmitting #4 (no NAT) to 192.168.1.149:5060:
    REGISTER sip:192.168.1.149 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.149:25069;branch=z9hG4bK21655d35
    Max-Forwards: 70
    From: <sip:310@192.168.1.149>;tag=as0ee36123
    To: <sip:310@192.168.1.149>
    Call-ID: 37eb67f31d99933716e88fc063090695@192.168.1.149
    CSeq: 187 REGISTER
    Supported: replaces, timer
    User-Agent: VitalPBX
    Expires: 120
    Contact: <sip:310@192.168.1.149:25069>
    Content-Length: 0


    Reliably Transmitting (no NAT) to 192.168.1.149:5060:
    OPTIONS sip:310@192.168.1.147:5060 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.149:25069;branch=z9hG4bK79588c1a
    Max-Forwards: 70
    From: “asterisk” <sip:asterisk@192.168.1.149:25069>;tag=as69415edf
    To: <sip:310@192.168.1.147:5060>
    Contact: <sip:asterisk@192.168.1.149:25069>
    Call-ID: 6da619ff43e8efa046571d9301c6c43a@192.168.1.149:25069
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 08 Jun 2018 04:35:09 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.149:5060:
    OPTIONS sip:310@192.168.1.147:5060 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.149:25069;branch=z9hG4bK79588c1a
    Max-Forwards: 70
    From: “asterisk” <sip:asterisk@192.168.1.149:25069>;tag=as69415edf
    To: <sip:310@192.168.1.147:5060>
    Contact: <sip:asterisk@192.168.1.149:25069>
    Call-ID: 6da619ff43e8efa046571d9301c6c43a@192.168.1.149:25069
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 08 Jun 2018 04:35:09 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Content-Length: 0


    Reliably Transmitting (no NAT) to 204.11.192.134:5060:
    OPTIONS sip:doll5.callcentric.com SIP/2.0
    Via: SIP/2.0/UDP 70.27.176.52:25069;branch=z9hG4bK59bb1bba
    Max-Forwards: 70
    From: “asterisk” <sip:17778376747@70.27.176.52:25069>;tag=as4682022c
    To: <sip:doll5.callcentric.com>
    Contact: <sip:17778376747@70.27.176.52:25069>
    Call-ID: 352550dc24ad521f7c4b855957e603ec@70.27.176.52:25069
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 08 Jun 2018 04:35:11 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Content-Length: 0


    Reliably Transmitting (n
    o NAT) to 204.11.192.133:5060:
    OPTIONS sip:doll4.callcentric.com SIP/2.0
    Via: SIP/2.0/UDP 70.27.176.52:25069;branch=z9hG4bK62c88c95
    Max-Forwards: 70
    From: “asterisk” <sip:17778376747@70.27.176.52:25069>;tag=as480ef614
    To: <sip:doll4.callcentric.com>
    Contact: <sip:17778376747@70.27.176.52:25069>
    Call-ID: 322056d9091831182582fec32ede3085@70.27.176.52:25069
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 08 Jun 2018 04:35:11 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Content-Length: 0


    Reliably Transmitting (no NAT) to 204.11.192.132:5060:
    OPTIONS sip:doll3.callcentric.com SIP/2.0
    Via: SIP/2.0/UDP 70.27.176.52:25069;branch=z9hG4bK042cdde7
    Max-Forwards: 70
    From: “asterisk” <sip:17778376747@70.27.176.52:25069>;tag=as34949b70
    To: <sip:doll3.callcentric.com>
    Contact: <sip:17778376747@70.27.176.52:25069>
    Call-ID: 65ee92341561d29e42c37b2006a143bd@70.27.176.52:25069
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 08 Jun 2018 04:35:11 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.149:5060:
    OPTIONS sip:310@192.168.1.147:5060 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.149:25069;branch=z9hG4bK79588c1a
    Max-Forwards: 70
    From: “asterisk” <sip:asterisk@192.168.1.149:25069>;tag=as69415edf
    To: <sip:310@192.168.1.147:5060>
    Contact: <sip:asterisk@192.168.1.149:25069>
    Call-ID: 6da619ff43e8efa046571d9301c6c43a@192.168.1.149:25069
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 08 Jun 2018 04:35:09 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Content-Length: 0


    Retransmitting #1 (no NAT) to 204.11.192.134:5060:
    OPTIONS sip:doll5.callcentric.com SIP/2.0
    Via: SIP/2.0/UDP 70.27.176.52:25069;branch=z9hG4bK59bb1bba
    Max-Forwards: 70
    From: “asterisk” <sip:17778376747@70.27.176.52:25069>;tag=as4682022c
    To: <sip:doll5.callcentric.com>
    Contact: <sip:17778376747@70.27.176.52:25069>
    Call-ID: 352550dc24ad521f7c4b855957e603ec@70.27.176.52:25069
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 08 Jun 2018 04:35:11 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Content-Length: 0


    Retransmitting #1 (no NAT) to 204.11.192.133:5060:
    OPTIONS sip:doll4.callcentric.com SIP/2.0
    Via: SIP/2.0/UDP 70.27.176.52:25069;branch=z9hG4bK62c88c95
    Max-Forwards: 70
    From: “asterisk” <sip:17778376747@70.27.176.52:25069>;tag=as480ef614
    To: <sip:doll4.callcentric.com>
    Contact: <sip:17778376747@70.27.176.52:25069>
    Call-ID: 322056d9091831182582fec32ede3085@70.27.176.52:25069
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 08 Jun 2018 04:35:11 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Content-Length: 0


    Retransmitting #1 (no NAT) to 204.11.192.132:5060:
    OPTIONS sip:doll3.callcentric.com SIP/2.0
    Via: SIP/2.0/UDP 70.27.176.52:25069;branch=z9hG4bK042cdde7
    Max-Forwards: 70
    From: “asterisk” <sip:17778376747@70.27.176.52:25069>;tag=as34949b70
    To: <sip:doll3.callcentric.com>
    Contact: <sip:17778376747@70.27.176.52:25069>
    Call-ID: 65ee92341561d29e42c37b2006a143bd@70.27.176.52:25069
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 08 Jun 2018 04:35:11 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.144:25069 —>

    <————->
    Retransmitting #3 (no NAT) to 192.168.1.149:5060:
    OPTIONS sip:310@192.168.1.147:5060 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.149:25069;branch=z9hG4bK79588c1a
    Max-Forwards: 70
    From: “asterisk” <sip:asterisk@192.168.1.149:25069>;tag=as69415edf
    To: <sip:310@192.168.1.147:5060>
    Contact: <sip:asterisk@192.168.1.149:25069>
    Call-ID: 6da619ff43e8efa046571d9301c6c43a@192.168.1.149:25069
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 08 Jun 2018 04:35:09 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Content-Length: 0


    Retransmitting #5 (no NAT) to 192.168.1.149:5060:
    REGISTER sip:192.168.1.149 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.149:25069;branch=z9hG4bK21655d35
    Max-Forwards: 70
    From: <sip:310@192.168.1.149>;tag=as0ee36123
    To: <sip:310@192.168.1.149>
    Call-ID: 37eb67f31d99933716e88fc063090695@192.168.1.149
    CSeq: 187 REGISTER
    Supported: replaces, timer
    User-Agent: VitalPBX
    Expires: 120
    Contact: <sip:310@192.168.1.149:25069>
    Content-Length: 0


    Retransmitting #2 (no NAT) to 204.11.192.134:5060:
    OPTIONS sip:doll5.callcentric.com SIP/2.0
    Via: SIP/2.0/UDP 70.27.176.52:25069;branch=z9hG4bK59bb1bba
    Max-Forwards: 70
    From: “asterisk” <sip:17778376747@70.27.176.52:25069>;tag=as4682022c
    To: <sip:doll5.callcentric.com>
    Contact: <sip:17778376747@70.27.176.52:25069>
    Call-ID: 352550dc24ad521f7c4b855957e603ec@70.27.176.52:25069
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 08 Jun 2018 04:35:11 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Content-Length: 0


    Retransmitting #2 (no NAT) to 204.11.192.133:5060:
    OPTIONS sip:doll4.callcentric.com SIP/2.0
    Via: SIP/2.0/UDP 70.27.176.52:25069;branch=z9hG4bK62c88c95
    Max-Forwards: 70
    From: “asterisk” <sip:17778376747@70.27.176.52:25069>;tag=as480ef614
    To: <sip:doll4.callcentric.com>
    Contact: <sip:17778376747@70.27.176.52:25069>
    Call-ID: 322056d9091831182582fec32ede3085@70.27.176.52:25069
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 08 Jun 2018 04:35:11 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Content-Length: 0


    Retransmitting #2 (no NAT) to 204.11.192.132:5060:
    OPTIONS sip:doll3.callcentric.com SIP/2.0
    Via: SIP/2.0/UDP 70.27.176.52:25069;branch=z9hG4bK042cdde7
    Max-Forwards: 70
    From: “asterisk” <sip:17778376747@70.27.176.52:25069>;tag=as34949b70
    To: <sip:doll3.callcentric.com>
    Contact: <sip:17778376747@70.27.176.52:25069>
    Call-ID: 65ee92341561d29e42c37b2006a143bd@70.27.176.52:25069
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 08 Jun 2018 04:35:11 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Content-Length: 0


    Reliably Transmitting (NAT) to 192.168.1.1:13400:
    OPTIONS sip:300@192.168.1.131:13400 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.149:25069;branch=z9hG4bK52365cff;rport
    Max-Forwards: 70
    From: “asterisk” <sip:asterisk@192.168.1.149:25069>;tag=as3a4e134f
    To: <sip:300@192.168.1.131:13400>
    Contact: <sip:asterisk@192.168.1.149:25069>
    Call-ID: 49b629e80c3833b32d13bc44490aa4f1@192.168.1.149:25069
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 08 Jun 2018 04:35:13 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.1:13400 —>
    SIP/2.0 200 OK
    Via: SIP/2.0/UDP 192.168.1.149:25069;branch=z9hG4bK52365cff;rport=25069;received=70.27.176.52
    From: “asterisk” <sip:asterisk@192.168.1.149:25069>;tag=as3a4e134f
    To: <sip:300@192.168.1.131:13400>;tag=2119583426
    Call-ID: 49b629e80c3833b32d13bc44490aa4f1@192.168.1.149:25069
    CSeq: 102 OPTIONS
    Supported: replaces, path, eventlist
    User-Agent: Grandstream Wave 1.0.3.10
    Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, INFO, REFER, UPDATE, MESSAGE
    Content-Length: 0

    <————->
    — (10 headers 0 lines) —
    Really destroying SIP dialog ’49b629e80c3833b32d13bc44490aa4f1@192.168.1.149:25069′ Method: OPTIONS
    [2018-06-08 00:35:13] DEBUG[3797]: chan_sip.c:22347 sip_dump_history:
    ———- SIP HISTORY for ’49b629e80c3833b32d13bc44490aa4f1@192.168.1.149:25069′
    [2018-06-08 00:35:13] DEBUG[3797]: chan_sip.c:22351 sip_dump_history: * SIP Call
    [2018-06-08 00:35:13] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 001. TxReqRel OPTIONS / 102 OPTIONS – OPTIONS
    [2018-06-08 00:35:13] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 002. Rx SIP/2.0 / 102 OPTIONS / 200 OK
    [2018-06-08 00:35:13] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 003. NeedDestroy Setting needdestroy because got OPTIONS response
    [2018-06-08 00:35:13] DEBUG[3797]: chan_sip.c:22360 sip_dump_history:
    ———- END SIP HISTORY for ’49b629e80c3833b32d13bc44490aa4f1@192.168.1.149:25069′
    Retransmitting #4 (no NAT) to 192.168.1.149:5060:
    OPTIONS sip:310@192.168.1.147:5060 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.149:25069;branch=z9hG4bK79588c1a
    Max-Forwards: 70
    From: “asterisk” <sip:asterisk@192.168.1.149:25069>;tag=as69415edf
    To: <sip:310@192.168.1.147:5060>
    Contact: <sip:asterisk@192.168.1.149:25069>
    Call-ID: 6da619ff43e8efa046571d9301c6c43a@192.168.1.149:25069
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 08 Jun 2018 04:35:09 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Content-Length: 0


    Really destroying SIP dialog ‘6da619ff43e8efa046571d9301c6c43a@192.168.1.149:25069’ Method: OPTIONS
    [2018-06-08 00:35:13] DEBUG[3797]: chan_sip.c:22347 sip_dump_history:
    ———- SIP HISTORY for ‘6da619ff43e8efa046571d9301c6c43a@192.168.1.149:25069’
    [2018-06-08 00:35:13] DEBUG[3797]: chan_sip.c:22351 sip_dump_history: * SIP Call
    [2018-06-08 00:35:13] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 001. TxReqRel OPTIONS / 102 OPTIONS – OPTIONS
    [2018-06-08 00:35:13] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 002. ReTx 1000 OPTIONS sip:310@192.168.1.147:5060 SIP/2.0
    [2018-06-08 00:35:13] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 003. ReTx 1000 OPTIONS sip:310@192.168.1.147:5060 SIP/2.0
    [2018-06-08 00:35:13] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 004. ReTx 1000 OPTIONS sip:310@192.168.1.147:5060 SIP/2.0
    [2018-06-08 00:35:13] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 005. ReTx 1000 OPTIONS sip:310@192.168.1.147:5060 SIP/2.0
    [2018-06-08 00:35:13] DEBUG[3797]: chan_sip.c:22360 sip_dump_history:
    ———- END SIP HISTORY for ‘6da619ff43e8efa046571d9301c6c43a@192.168.1.149:25069’
    Retransmitting #3 (no NAT) to 204.11.192.134:5060:
    OPTIONS sip:doll5.callcentric.com SIP/2.0
    Via: SIP/2.0/UDP 70.27.176.52:25069;branch=z9hG4bK59bb1bba
    Max-Forwards: 70
    From: “asterisk” <sip:17778376747@70.27.176.52:25069>;tag=as4682022c
    To: <sip:doll5.callcentric.com>
    Contact: <sip:17778376747@70.27.176.52:25069>
    Call-ID: 352550dc24ad521f7c4b855957e603ec@70.27.176.52:25069
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 08 Jun 2018 04:35:11 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Content-Length: 0


    Retransmitting #3 (no NAT) to 204.11.192.133:5060:
    OPTIONS sip:doll4.callcentric.com SIP/2.0
    Via: SIP/2.0/UDP 70.27.176.52:25069;branch=z9hG4bK62c88c95
    Max-Forwards: 70
    From: “asterisk” <sip:17778376747@70.27.176.52:25069>;tag=as480ef614
    To: <sip:doll4.callcentric.com>
    Contact: <sip:17778376747@70.27.176.52:25069>
    Call-ID: 322056d9091831182582fec32ede3085@70.27.176.52:25069
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 08 Jun 2018 04:35:11 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Content-Length: 0


    Retransmitting #3 (no NAT) to 204.11.192.132:5060:
    OPTIONS sip:doll3.callcentric.com SIP/2.0
    Via: SIP/2.0/UDP 70.27.176.52:25069;branch=z9hG4bK042cdde7
    Max-Forwards: 70
    From: “asterisk” <sip:17778376747@70.27.176.52:25069>;tag=as34949b70
    To: <sip:doll3.callcentric.com>
    Contact: <sip:17778376747@70.27.176.52:25069>
    Call-ID: 65ee92341561d29e42c37b2006a143bd@70.27.176.52:25069
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 08 Jun 2018 04:35:11 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Content-Length: 0


    Retransmitting #4 (no NAT) to 204.11.192.134:5060:
    OPTIONS sip:doll5.callcentric.com SIP/2.0
    Via: SIP/2.0/UDP 70.27.176.52:25069;branch=z9hG4bK59bb1bba
    Max-Forwards: 70
    From: “asterisk” <sip:17778376747@70.27.176.52:25069>;tag=as4682022c
    To: <sip:doll5.callcentric.com>
    Contact: <sip:17778376747@70.27.176.52:25069>
    Call-ID: 352550dc24ad521f7c4b855957e603ec@70.27.176.52:25069
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 08 Jun 2018 04:35:11 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Content-Length: 0


    Retransmitting #4 (no NAT) to 204.11.192.133:5060:
    OPTIONS sip:doll4.callcentric.com SIP/2.0
    Via: SIP/2.0/UDP 70.27.176.52:25069;branch=z9hG4bK62c88c95
    Max-Forwards: 70
    From: “asterisk” <sip:17778376747@70.27.176.52:25069>;tag=as480ef614
    To: <sip:doll4.callcentric.com>
    Contact: <sip:17778376747@70.27.176.52:25069>
    Call-ID: 322056d9091831182582fec32ede3085@70.27.176.52:25069
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 08 Jun 2018 04:35:11 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Content-Length: 0


    Really destroying SIP dialog ‘352550dc24ad521f7c4b855957e603ec@70.27.176.52:25069’ Method: OPTIONS
    [2018-06-08 00:35:15] DEBUG[3797]: chan_sip.c:22347 sip_dump_history:
    ———- SIP HISTORY for ‘352550dc24ad521f7c4b855957e603ec@70.27.176.52:25069’
    [2018-06-08 00:35:15] DEBUG[3797]: chan_sip.c:22351 sip_dump_history: * SIP Call
    [2018-06-08 00:35:15] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 001. TxReqRel OPTIONS / 102 OPTIONS – OPTIONS
    [2018-06-08 00:35:15] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 002. ReTx 1000 OPTIONS sip:doll5.callcentric.com SIP/2.0
    [2018-06-08 00:35:15] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 003. ReTx 1000 OPTIONS sip:doll5.callcentric.com SIP/2.0
    [2018-06-08 00:35:15] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 004. ReTx 1000 OPTIONS sip:doll5.callcentric.com SIP/2.0
    [2018-06-08 00:35:15] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 005. ReTx 1000 OPTIONS sip:doll5.callcentric.com SIP/2.0
    [2018-06-08 00:35:15] DEBUG[3797]: chan_sip.c:22360 sip_dump_history:
    ———- END SIP HISTORY for ‘352550dc24ad521f7c4b855957e603ec@70.27.176.52:25069’
    Really destroying SIP dialog ‘322056d9091831182582fec32ede3085@70.27.176.52:25069’ Method: OPTIONS
    [20
    18-06-08 00:35:15] DEBUG[3797]: chan_sip.c:22347 sip_dump_history:
    ———- SIP HISTORY for ‘322056d9091831182582fec32ede3085@70.27.176.52:25069’
    [2018-06-08 00:35:15] DEBUG[3797]: chan_sip.c:22351 sip_dump_history: * SIP Call
    [2018-06-08 00:35:15] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 001. TxReqRel OPTIONS / 102 OPTIONS – OPTIONS
    [2018-06-08 00:35:15] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 002. ReTx 1000 OPTIONS sip:doll4.callcentric.com SIP/2.0
    [2018-06-08 00:35:15] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 003. ReTx 1000 OPTIONS sip:doll4.callcentric.com SIP/2.0
    [2018-06-08 00:35:15] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 004. ReTx 1000 OPTIONS sip:doll4.callcentric.com SIP/2.0
    [2018-06-08 00:35:15] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 005. ReTx 1000 OPTIONS sip:doll4.callcentric.com SIP/2.0
    [2018-06-08 00:35:15] DEBUG[3797]: chan_sip.c:22360 sip_dump_history:
    ———- END SIP HISTORY for ‘322056d9091831182582fec32ede3085@70.27.176.52:25069’
    Retransmitting #4 (no NAT) to 204.11.192.132:5060:
    OPTIONS sip:doll3.callcentric.com SIP/2.0
    Via: SIP/2.0/UDP 70.27.176.52:25069;branch=z9hG4bK042cdde7
    Max-Forwards: 70
    From: “asterisk” <sip:17778376747@70.27.176.52:25069>;tag=as34949b70
    To: <sip:doll3.callcentric.com>
    Contact: <sip:17778376747@70.27.176.52:25069>
    Call-ID: 65ee92341561d29e42c37b2006a143bd@70.27.176.52:25069
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 08 Jun 2018 04:35:11 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Content-Length: 0


    Really destroying SIP dialog ’65ee92341561d29e42c37b2006a143bd@70.27.176.52:25069′ Method: OPTIONS
    [2018-06-08 00:35:15] DEBUG[3797]: chan_sip.c:22347 sip_dump_history:
    ———- SIP HISTORY for ’65ee92341561d29e42c37b2006a143bd@70.27.176.52:25069′
    [2018-06-08 00:35:15] DEBUG[3797]: chan_sip.c:22351 sip_dump_history: * SIP Call
    [2018-06-08 00:35:15] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 001. TxReqRel OPTIONS / 102 OPTIONS – OPTIONS
    [2018-06-08 00:35:15] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 002. ReTx 1000 OPTIONS sip:doll3.callcentric.com SIP/2.0
    [2018-06-08 00:35:15] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 003. ReTx 1000 OPTIONS sip:doll3.callcentric.com SIP/2.0
    [2018-06-08 00:35:15] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 004. ReTx 1000 OPTIONS sip:doll3.callcentric.com SIP/2.0
    [2018-06-08 00:35:15] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 005. ReTx 1000 OPTIONS sip:doll3.callcentric.com SIP/2.0
    [2018-06-08 00:35:15] DEBUG[3797]: chan_sip.c:22360 sip_dump_history:
    ———- END SIP HISTORY for ’65ee92341561d29e42c37b2006a143bd@70.27.176.52:25069′

    <— SIP read from UDP:192.168.1.1:13400 —>
    SUBSCRIBE sip:700@mmcourier.com:25069 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.131:13400;branch=z9hG4bK344655456;rport
    From: <sip:300@mmcourier.com:25069>;tag=499047225
    To: <sip:700@mmcourier.com:25069>
    Call-ID: 584768104-13400-66@192.168.1.131
    CSeq: 200620 SUBSCRIBE
    Contact: <sip:300@192.168.1.131:13400>
    Max-Forwards: 70
    User-Agent: Grandstream Wave 1.0.3.10
    Expires: 3600
    Supported: replaces, path, timer, eventlist
    Event: dialog
    Accept: application/dialog-info+xml, multipart/related, application/rlmi+xml
    Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, INFO, REFER, UPDATE, MESSAGE
    Content-Length: 0

    <————->
    — (15 headers 0 lines) —
    Sending to 192.168.1.1:13400 (NAT)
    Creating new subscription
    Sending to 192.168.1.1:13400 (NAT)
    sip_route_dump: route/path hop: <sip:300@192.168.1.131:13400>
    Found peer ‘300’ for ‘300’ from 192.168.1.1:13400

    <— Transmitting (NAT) to 192.168.1.1:13400 —>
    SIP/2.0 401 Unauthorized
    Via: SIP/2.0/UDP 192.168.1.131:13400;branch=z9hG4bK344655456;received=192.168.1.1;rport=13400
    From: <sip:300@mmcourier.com:25069>;tag=499047225
    To: <sip:700@mmcourier.com:25069>;tag=as4a8ce361
    Call-ID: 584768104-13400-66@192.168.1.131
    CSeq: 200620 SUBSCRIBE
    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=”6fb0c033″
    Content-Length: 0

    <————>
    Scheduling destruction of SIP dialog ‘584768104-13400-66@192.168.1.131’ in 6400 ms (Method: SUBSCRIBE)

    <— SIP read from UDP:192.168.1.1:13400 —>
    SUBSCRIBE sip:700@mmcourier.com:25069 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.131:13400;branch=z9hG4bK587815612;rport
    From: <sip:300@mmcourier.com:25069>;tag=499047225
    To: <sip:700@mmcourier.com:25069>
    Call-ID: 584768104-13400-66@192.168.1.131
    CSeq: 200621 SUBSCRIBE
    Contact: <sip:300@192.168.1.131:13400>
    Authorization: Digest username=”300″, realm=”asterisk”, nonce=”6fb0c033″, uri=”sip:700@mmcourier.com:25069″, response=”202edc5f9e4c923e0fd06dd21df7d127″, algorithm=MD5
    Max-Forwards: 70
    User-Agent: Grandstream Wave 1.0.3.10
    Expires: 3600
    Supported: replaces, path, timer, eventlist
    Event: dialog
    Accept: application/dialog-info+xml, multipart/related, application/rlmi+xml
    Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, INFO, REFER, UPDATE, MESSAGE
    Content-Length: 0

    <————->
    — (16 headers 0 lines) —
    Creating new subscription
    Sending to 192.168.1.1:13400 (NAT)
    Found peer ‘300’ for ‘300’ from 192.168.1.1:13400
    Looking for 700 in cos-all (domain mmcourier.com)

    <— Transmitting (NAT) to 192.168.1.1:13400 —>
    SIP/2.0 404 Not Found
    Via: SIP/2.0/UDP 192.168.1.131:13400;branch=z9hG4bK587815612;received=192.168.1.1;rport=13400
    From: <sip:300@mmcourier.com:25069>;tag=499047225
    To: <sip:700@mmcourier.com:25069>;tag=as4a8ce361
    Call-ID: 584768104-13400-66@192.168.1.131
    CSeq: 200621 SUBSCRIBE
    Server: VitalPBX
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Content-Length: 0

    <————>
    Really destroying SIP dialog ‘584768104-13400-66@192.168.1.131’ Method: SUBSCRIBE
    [2018-06-08 00:35:15] DEBUG[3797]: chan_sip.c:22347 sip_dump_history:
    ———- SIP HISTORY for ‘584768104-13400-66@192.168.1.131’
    [2018-06-08 00:35:15] DEBUG[3797]: chan_sip.c:22351 sip_dump_history: * SIP Call
    [2018-06-08 00:35:15] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 001. Rx SUBSCRIBE / 200620 SUBSCRIBE / sip:700@mmcourier.com:25069
    [2018-06-08 00:35:15] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 002. AuthChal Auth challenge sent for – nc 0
    [2018-06-08 00:35:15] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 003. TxResp SIP/2.0 / 200620 SUBSCRIBE – 401 Unauthorized
    [2018-06-08 00:35:15] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 004. SchedDestroy 6400 ms
    [2018-06-08 00:35:15] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 005. Rx SUBSCRIBE / 200621 SUBSCRIBE / sip:700@mmcourier.com:25069
    [2018-06-08 00:35:15] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 006. AuthOK Auth challenge successful for 300
    [2018-06-08 00:35:15] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 007. TxResp SIP/2.0 / 200621 SUBSCRIBE – 404 Not Found
    [2018-06-08 00:35:15] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 008. NeedDestroy Setting needdestroy because subscription target not found
    [2018-06-08 00:35:15] DEBUG[3797]: chan_sip.c:22360 sip_dump_history:
    ———- END SIP HISTORY for ‘584768104-13400-66@192.168.1.131’

    <— SIP read from UDP:192.168.1.1:13400 —>
    SUBSCRIBE sip:700@mmcourier.com:25069 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.131:13400;branch=z9hG4bK
    1290161742;rport
    From: <sip:300@mmcourier.com:25069>;tag=1615109175
    To: <sip:700@mmcourier.com:25069>
    Call-ID: 1163375587-13400-67@192.168.1.131
    CSeq: 200630 SUBSCRIBE
    Contact: <sip:300@192.168.1.131:13400>
    Max-Forwards: 70
    User-Agent: Grandstream Wave 1.0.3.10
    Expires: 3600
    Supported: replaces, path, timer, eventlist
    Event: dialog
    Accept: application/dialog-info+xml, multipart/related, application/rlmi+xml
    Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, INFO, REFER, UPDATE, MESSAGE
    Content-Length: 0

    <————->
    — (15 headers 0 lines) —
    Sending to 192.168.1.1:13400 (NAT)
    Creating new subscription
    Sending to 192.168.1.1:13400 (NAT)
    sip_route_dump: route/path hop: <sip:300@192.168.1.131:13400>
    Found peer ‘300’ for ‘300’ from 192.168.1.1:13400

    <— Transmitting (NAT) to 192.168.1.1:13400 —>
    SIP/2.0 401 Unauthorized
    Via: SIP/2.0/UDP 192.168.1.131:13400;branch=z9hG4bK1290161742;received=192.168.1.1;rport=13400
    From: <sip:300@mmcourier.com:25069>;tag=1615109175
    To: <sip:700@mmcourier.com:25069>;tag=as2492835c
    Call-ID: 1163375587-13400-67@192.168.1.131
    CSeq: 200630 SUBSCRIBE
    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=”1fa0bd51″
    Content-Length: 0

    <————>
    Scheduling destruction of SIP dialog ‘1163375587-13400-67@192.168.1.131’ in 6400 ms (Method: SUBSCRIBE)

    <— SIP read from UDP:192.168.1.1:13400 —>
    SUBSCRIBE sip:700@mmcourier.com:25069 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.131:13400;branch=z9hG4bK74108118;rport
    From: <sip:300@mmcourier.com:25069>;tag=1615109175
    To: <sip:700@mmcourier.com:25069>
    Call-ID: 1163375587-13400-67@192.168.1.131
    CSeq: 200631 SUBSCRIBE
    Contact: <sip:300@192.168.1.131:13400>
    Authorization: Digest username=”300″, realm=”asterisk”, nonce=”1fa0bd51″, uri=”sip:700@mmcourier.com:25069″, response=”31ca64bfb60df388ac879715f1c82462″, algorithm=MD5
    Max-Forwards: 70
    User-Agent: Grandstream Wave 1.0.3.10
    Expires: 3600
    Supported: replaces, path, timer, eventlist
    Event: dialog
    Accept: application/dialog-info+xml, multipart/related, application/rlmi+xml
    Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, INFO, REFER, UPDATE, MESSAGE
    Content-Length: 0

    <————->
    — (16 headers 0 lines) —
    Creating new subscription
    Sending to 192.168.1.1:13400 (NAT)
    Found peer ‘300’ for ‘300’ from 192.168.1.1:13400
    Looking for 700 in cos-all (domain mmcourier.com)

    <— Transmitting (NAT) to 192.168.1.1:13400 —>
    SIP/2.0 404 Not Found
    Via: SIP/2.0/UDP 192.168.1.131:13400;branch=z9hG4bK74108118;received=192.168.1.1;rport=13400
    From: <sip:300@mmcourier.com:25069>;tag=1615109175
    To: <sip:700@mmcourier.com:25069>;tag=as2492835c
    Call-ID: 1163375587-13400-67@192.168.1.131
    CSeq: 200631 SUBSCRIBE
    Server: VitalPBX
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Content-Length: 0

    <————>
    Really destroying SIP dialog ‘1163375587-13400-67@192.168.1.131’ Method: SUBSCRIBE
    [2018-06-08 00:35:16] DEBUG[3797]: chan_sip.c:22347 sip_dump_history:
    ———- SIP HISTORY for ‘1163375587-13400-67@192.168.1.131’
    [2018-06-08 00:35:16] DEBUG[3797]: chan_sip.c:22351 sip_dump_history: * SIP Call
    [2018-06-08 00:35:16] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 001. Rx SUBSCRIBE / 200630 SUBSCRIBE / sip:700@mmcourier.com:25069
    [2018-06-08 00:35:16] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 002. AuthChal Auth challenge sent for – nc 0
    [2018-06-08 00:35:16] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 003. TxResp SIP/2.0 / 200630 SUBSCRIBE – 401 Unauthorized
    [2018-06-08 00:35:16] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 004. SchedDestroy 6400 ms
    [2018-06-08 00:35:16] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 005. Rx SUBSCRIBE / 200631 SUBSCRIBE / sip:700@mmcourier.com:25069
    [2018-06-08 00:35:16] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 006. AuthOK Auth challenge successful for 300
    [2018-06-08 00:35:16] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 007. TxResp SIP/2.0 / 200631 SUBSCRIBE – 404 Not Found
    [2018-06-08 00:35:16] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 008. NeedDestroy Setting needdestroy because subscription target not found
    [2018-06-08 00:35:16] DEBUG[3797]: chan_sip.c:22360 sip_dump_history:
    ———- END SIP HISTORY for ‘1163375587-13400-67@192.168.1.131’
    Retransmitting #6 (no NAT) to 192.168.1.149:5060:
    REGISTER sip:192.168.1.149 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.149:25069;branch=z9hG4bK21655d35
    Max-Forwards: 70
    From: <sip:310@192.168.1.149>;tag=as0ee36123
    To: <sip:310@192.168.1.149>
    Call-ID: 37eb67f31d99933716e88fc063090695@192.168.1.149
    CSeq: 187 REGISTER
    Supported: replaces, timer
    User-Agent: VitalPBX
    Expires: 120
    Contact: <sip:310@192.168.1.149:25069>
    Content-Length: 0

    <— SIP read from UDP:192.168.1.143:25069 —>

    <————->
    Really destroying SIP dialog ‘bf9d195b2343-hkzr8tvkarws@snomSoft-000413FFFFFF’ Method: REGISTER
    [2018-06-08 00:35:19] DEBUG[3797]: chan_sip.c:22347 sip_dump_history:
    ———- SIP HISTORY for ‘bf9d195b2343-hkzr8tvkarws@snomSoft-000413FFFFFF’
    [2018-06-08 00:35:19] DEBUG[3797]: chan_sip.c:22351 sip_dump_history: * SIP Call
    [2018-06-08 00:35:19] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 001. Rx REGISTER / 30 REGISTER / sip:192.168.1.149:25069
    [2018-06-08 00:35:19] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 002. AuthChal Auth challenge sent for – nc 0
    [2018-06-08 00:35:19] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 003. TxResp SIP/2.0 / 30 REGISTER – 401 Unauthorized
    [2018-06-08 00:35:19] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 004. RegRequest Succeeded : Account “303” <sip:303@192.168.1.149:25069>
    [2018-06-08 00:35:19] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 005. SchedDestroy 32000 ms
    [2018-06-08 00:35:19] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 006. Rx REGISTER / 31 REGISTER / sip:192.168.1.149:25069
    [2018-06-08 00:35:19] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 007. AuthOK Auth challenge successful for 303
    [2018-06-08 00:35:19] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 008. TxResp SIP/2.0 / 31 REGISTER – 200 OK
    [2018-06-08 00:35:19] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 009. RegRequest Succeeded : Account “303” <sip:303@192.168.1.149:25069>
    [2018-06-08 00:35:19] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 010. CancelDestroy
    [2018-06-08 00:35:19] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 011. SchedDestroy 32000 ms
    [2018-06-08 00:35:19] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 012. AutoDestroy bf9d195b2343-hkzr8tvkarws@snomSoft-000413FFFFFF
    [2018-06-08 00:35:19] DEBUG[3797]: chan_sip.c:22360 sip_dump_history:
    ———- END SIP HISTORY for ‘bf9d195b2343-hkzr8tvkarws@snomSoft-000413FFFFFF’
    Retransmitting #7 (no NAT) to 192.168.1.149:5060:
    REGISTER sip:192.168.1.149 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.149:25069;branch=z9hG4bK21655d35
    Max-Forwards: 70
    From: <sip:310@192.168.1.149>;tag=as0ee36123
    To: <sip:310@192.168.1.149>
    Call-ID: 37eb67f31d99933716e88fc063090695@192.168.1.149
    CSeq: 187 REGISTER
    Supported: replaces, timer
    User-Agent: VitalPBX
    Expires: 120
    Contact: <sip:310@192.168.1.149:25069>
    Content-Length: 0


    REGISTER 11 headers, 0 lines
    Reliably Transmitting (no NAT) to 192.168
    .1.149:5060:
    REGISTER sip:192.168.1.149 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.149:25069;branch=z9hG4bK5800df58
    Max-Forwards: 70
    From: <sip:310@192.168.1.149>;tag=as0ee36123
    To: <sip:310@192.168.1.149>
    Call-ID: 37eb67f31d99933716e88fc063090695@192.168.1.149
    CSeq: 188 REGISTER
    Supported: replaces, timer
    User-Agent: VitalPBX
    Expires: 120
    Contact: <sip:310@192.168.1.149:25069>
    Content-Length: 0


    [2018-06-08 00:35:21] NOTICE[3797]: chan_sip.c:15906 sip_reg_timeout: — Registration for ‘310@192.168.1.149’ timed out, trying again (Attempt #87)
    Really destroying SIP dialog ’37eb67f31d99933716e88fc063090695@192.168.1.149′ Method: REGISTER
    [2018-06-08 00:35:21] DEBUG[3797]: chan_sip.c:22347 sip_dump_history:
    ———- SIP HISTORY for ’37eb67f31d99933716e88fc063090695@192.168.1.149′
    [2018-06-08 00:35:21] DEBUG[3797]: chan_sip.c:22351 sip_dump_history: * SIP Call
    [2018-06-08 00:35:21] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 001. RegistryInit Account: 310@192.168.1.149
    [2018-06-08 00:35:21] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 002. TxReqRel REGISTER / 187 REGISTER – REGISTER
    [2018-06-08 00:35:21] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 003. ReTx 1000 REGISTER sip:192.168.1.149 SIP/2.0
    [2018-06-08 00:35:21] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 004. ReTx 2000 REGISTER sip:192.168.1.149 SIP/2.0
    [2018-06-08 00:35:21] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 005. ReTx 4000 REGISTER sip:192.168.1.149 SIP/2.0
    [2018-06-08 00:35:21] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 006. ReTx 4000 REGISTER sip:192.168.1.149 SIP/2.0
    [2018-06-08 00:35:21] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 007. ReTx 4000 REGISTER sip:192.168.1.149 SIP/2.0
    [2018-06-08 00:35:21] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 008. ReTx 4000 REGISTER sip:192.168.1.149 SIP/2.0
    [2018-06-08 00:35:21] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 009. ReTx 4000 REGISTER sip:192.168.1.149 SIP/2.0
    [2018-06-08 00:35:21] DEBUG[3797]: chan_sip.c:22355 sip_dump_history: 010. NeedDestroy Setting needdestroy because registration timeout
    [2018-06-08 00:35:21] DEBUG[3797]: chan_sip.c:22360 sip_dump_history:
    ———- END SIP HISTORY for ’37eb67f31d99933716e88fc063090695@192.168.1.149′
    Retransmitting #1 (no NAT) to 192.168.1.149:5060:
    REGISTER sip:192.168.1.149 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.149:25069;branch=z9hG4bK5800df58
    Max-Forwards: 70
    From: <sip:310@192.168.1.149>;tag=as0ee36123
    To: <sip:310@192.168.1.149>
    Call-ID: 37eb67f31d99933716e88fc063090695@192.168.1.149
    CSeq: 188 REGISTER
    Supported: replaces, timer
    User-Agent: VitalPBX
    Expires: 120
    Contact: <sip:310@192.168.1.149:25069>
    Content-Length: 0


    Retransmitting #2 (no NAT) to 192.168.1.149:5060:
    REGISTER sip:192.168.1.149 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.149:25069;branch=z9hG4bK5800df58
    Max-Forwards: 70
    From: <sip:310@192.168.1.149>;tag=as0ee36123
    To: <sip:310@192.168.1.149>
    Call-ID: 37eb67f31d99933716e88fc063090695@192.168.1.149
    CSeq: 188 REGISTER
    Supported: replaces, timer
    User-Agent: VitalPBX
    Expires: 120
    Contact: <sip:310@192.168.1.149:25069>
    Content-Length: 0


    Reliably Transmitting (no NAT) to 192.168.1.149:5060:
    OPTIONS sip:310@192.168.1.147:5060 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.149:25069;branch=z9hG4bK696b31d9
    Max-Forwards: 70
    From: “asterisk” <sip:asterisk@192.168.1.149:25069>;tag=as1990f1e6
    To: <sip:310@192.168.1.147:5060>
    Contact: <sip:asterisk@192.168.1.149:25069>
    Call-ID: 5b46c8a12b212ddb71a895ff1a66f37b@192.168.1.149:25069
    CSeq: 102 OPTIONS
    User-Agent: VitalPBX
    Date: Fri, 08 Jun 2018 04:35:23 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Content-Length: 0


    vitalpbx*CLI>
    Disconnected from Asterisk server
    Asterisk cleanly ending (0).
    Executing last minute cleanups
    [root@vitalpbx ~]#

    0