locked
ms-diagnostics-public 3186 reason Invite dialog terminated since new dialog replaced it RRS feed

  • Question

  • I am getting the following error in at least one conference associated with a Polycom deice.

    ms-diagnostics-public 3186 reason Invite dialog terminated since new dialog replaced it

    The call is then dropped. I haven't much information about it, and was hoping for some direction.

    Here is the full log entry: (Domain and server names replaced)

    TL_INFO(TF_PROTOCOL) [sfbpool-na\SFBServer03]2D5C.159C::12/04/2018-15:15:56.347.1197F37B (SIPStack,SIPAdminLog::ProtocolRecord::Flush:ProtocolRecord.cpp(261)) [265940140]
    Trace-Correlation-Id: 265940140
    Instance-Id: 3A88CC0
    Direction: incoming
    Peer: sfbpool-na.domainName.com:58999;ms-fe=SFBServer01.domainName.pvt
    Message-Type: request
    Start-Line: BYE sip:Scissortail.conferenceroom@domainName.com;opaque=user:epid:6vHxno1EkV6yhuhrdd9nXQAA;gruu SIP/2.0
    From: <sip:todd.akers@domainName.com;gruu;opaque=app:conf:focus:id:RQZNG1B5>;tag=B33D0080
    To: <sip:Scissortail.conferenceroom@domainName.com>;tag=D06CE2B2-2BC71BE8;epid=64167f4ec217
    Call-ID: 4c6441b2c080ef665cf2f215504ec217
    CSeq: 2147483645 BYE
    Via: SIP/2.0/TLS 10.3.0.99:58999;branch=z9hG4bKB18ACF7F.53C0D5C26D5753BC;branched=FALSE
    Route: <sip:sfbpool-na.domainName.com:5061;transport=tls;ms-fe=SFBServer03.domainName.pvt;opaque=state:T;lr>
    Max-Forwards: 70
    Content-Length: 0
    ms-diagnostics-public: 3186;reason="Invite dialog terminated since new dialog replaced it"
    $$end_record

    Diagram:

    HERE ARE THE ASSOCIATED LOGS:

    TL_INFO(TF_PROTOCOL) [sfbpool-na\SFBServer02]2B50.45AC::12/04/2018-15:15:21.648.0DB8C0AA (SIPStack,SIPAdminLog::ProtocolRecord::Flush:ProtocolRecord.cpp(261)) [1090150418]
    Trace-Correlation-Id: 1090150418
    Instance-Id: 25FFDD6
    Direction: incoming
    Peer: sfbedge-na.DomainName.com:56440;ms-fe=SFBServerEDGE02.DomainName.pvt
    Message-Type: request
    Start-Line: UPDATE sip:John.doee@DomainName.com;gruu;opaque=app:conf:focus:id:RQZNG1B5 SIP/2.0
    From: "BKA-133-Scissortail Conference Room" <sip:Scissortail.conferenceroom@DomainName.com>;tag=D06CE2B2-2BC71BE8;epid=64167f4ec217
    To: <sip:John.doee@DomainName.com;gruu;opaque=app:conf:focus:id:RQZNG1B5>;tag=B33D0080
    Call-ID: 4c6441b2c080ef665cf2f215504ec217
    CSeq: 6 UPDATE
    Contact: <sip:Scissortail.conferenceroom@DomainName.com;opaque=user:epid:6vHxno1EkV6yhuhrdd9nXQAA;gruu>
    Via: SIP/2.0/TLS 172.22.1.28:56440;branch=z9hG4bKCCA9C106.FB07C5699B902399;branched=FALSE
    Via: SIP/2.0/TLS 10.4.11.85:41920;branch=z9hG4bKc17931ce2C00FE93;received=4.16.21.154;ms-received-port=41920;ms-received-cid=212FB000
    Route: <sip:sfbpool-na.DomainName.com:5061;transport=tls;ms-fe=SFBServer02.DomainName.pvt;lr;received=10.3.0.83;ms-received-cid=2316FE01>, <sip:sfbpool-na.DomainName.com:5061;transport=tls;ms-fe=SFBServer03.DomainName.pvt;opaque=state:F:Eu;lr>, <sip:sfbpool-na.DomainName.com:5061;transport=tls;ms-fe=SFBServer01.DomainName.pvt;opaque=state:T;lr>
    Max-Forwards: 69
    Content-Length: 0
    ms-edge-proxy-message-trust: ms-source-type=InternetUser;ms-ep-fqdn=sfbedge-na.DomainName.com;ms-source-verified-user=verified
    $$end_record

    TL_INFO(TF_DIAG) [sfbpool-na\SFBServer02]2B50.45AC::12/04/2018-15:15:21.648.0DB8C0AB (SIPStack,SIPAdminLog::WriteDiagnosticEvent:SIPAdminLog.cpp(827)) [1090150418] $$begin_record
    Severity: information
    Text: Routed a request that came from a server trusted for routing
    SIP-Start-Line: UPDATE sip:John.doee@DomainName.com;gruu;opaque=app:conf:focus:id:RQZNG1B5 SIP/2.0
    SIP-Call-ID: 4c6441b2c080ef665cf2f215504ec217
    SIP-CSeq: 6 UPDATE
    Peer: sfbpool-na.DomainName.com:5061;ms-fe=SFBServer03.DomainName.pvt
    $$end_record


    TL_INFO(TF_PROTOCOL) [sfbpool-na\SFBServer02]2B50.45AC::12/04/2018-15:15:21.648.0DB8C0AC (SIPStack,SIPAdminLog::ProtocolRecord::Flush:ProtocolRecord.cpp(261)) [1090150418]
    Trace-Correlation-Id: 1090150418
    Instance-Id: 25FFDD6
    Direction: outgoing
    Peer: sfbpool-na.DomainName.com:5061;ms-fe=SFBServer03.DomainName.pvt
    Message-Type: request
    Start-Line: UPDATE sip:John.doee@DomainName.com;gruu;opaque=app:conf:focus:id:RQZNG1B5 SIP/2.0
    From: "BKA-133-Scissortail Conference Room" <sip:Scissortail.conferenceroom@DomainName.com>;tag=D06CE2B2-2BC71BE8;epid=64167f4ec217
    To: <sip:John.doee@DomainName.com;gruu;opaque=app:conf:focus:id:RQZNG1B5>;tag=B33D0080
    Call-ID: 4c6441b2c080ef665cf2f215504ec217
    CSeq: 6 UPDATE
    Contact: <sip:Scissortail.conferenceroom@DomainName.com;opaque=user:epid:6vHxno1EkV6yhuhrdd9nXQAA;gruu>
    Via: SIP/2.0/TLS 10.3.0.83:63012;branch=z9hG4bKC1D8E307.C3E03DB0F2AAE399;branched=FALSE
    Via: SIP/2.0/TLS 172.22.1.28:56440;branch=z9hG4bKCCA9C106.FB07C5699B902399;branched=FALSE;ms-received-port=56440;ms-received-cid=2E75600
    Via: SIP/2.0/TLS 10.4.11.85:41920;branch=z9hG4bKc17931ce2C00FE93;received=4.16.21.154;ms-received-port=41920;ms-received-cid=212FB000
    Route: <sip:sfbpool-na.DomainName.com:5061;transport=tls;ms-fe=SFBServer03.DomainName.pvt;opaque=state:F:Eu;lr>, <sip:sfbpool-na.DomainName.com:5061;transport=tls;ms-fe=SFBServer01.DomainName.pvt;opaque=state:T;lr>
    Max-Forwards: 68
    Content-Length: 0
    ms-edge-proxy-message-trust: ms-source-type=InternetUser;ms-ep-fqdn=sfbedge-na.DomainName.com;ms-source-verified-user=verified
    P-Asserted-Identity: "BKA-133-Scissortail Conference Room" <sip:Scissortail.conferenceroom@DomainName.com>,<tel:+19182594829;ext=24829>
    $$end_record

    TL_INFO(TF_PROTOCOL) [sfbpool-na\SFBServer02]2B50.45AC::12/04/2018-15:15:21.649.0DB8C0AD (SIPStack,SIPAdminLog::ProtocolRecord::Flush:ProtocolRecord.cpp(261)) [265940140]
    Trace-Correlation-Id: 265940140
    Instance-Id: 25FFDD7
    Direction: incoming
    Peer: sfbpool-na.DomainName.com:5061;ms-fe=SFBServer03.DomainName.pvt
    Message-Type: response
    Start-Line: SIP/2.0 400 Bad request
    From: "BKA-133-Scissortail Conference Room" <sip:Scissortail.conferenceroom@DomainName.com>;tag=D06CE2B2-2BC71BE8;epid=64167f4ec217
    To: <sip:John.doee@DomainName.com;gruu;opaque=app:conf:focus:id:RQZNG1B5>;tag=B33D0080
    Call-ID: 4c6441b2c080ef665cf2f215504ec217
    CSeq: 6 UPDATE
    Via: SIP/2.0/TLS 10.3.0.83:63012;branch=z9hG4bKC1D8E307.C3E03DB0F2AAE399;branched=FALSE;ms-received-port=63012;ms-received-cid=360D500
    Via: SIP/2.0/TLS 172.22.1.28:56440;branch=z9hG4bKCCA9C106.FB07C5699B902399;branched=FALSE;ms-received-port=56440;ms-received-cid=2E75600
    Via: SIP/2.0/TLS 10.4.11.85:41920;branch=z9hG4bKc17931ce2C00FE93;received=4.16.21.154;ms-received-port=41920;ms-received-cid=212FB000
    Content-Length: 0
    ms-diagnostics: 3010;reason="Bad request without Session-Timer extension";processing-cluster="sfbpool-na.DomainName.com";processing-frontend="SFBServer01.DomainName.pvt";source="SFBServer01.DomainName.pvt"
    $$end_record

    TL_INFO(TF_DIAG) [sfbpool-na\SFBServer02]2B50.45AC::12/04/2018-15:15:21.649.0DB8C0AE (SIPStack,SIPAdminLog::WriteDiagnosticEvent:SIPAdminLog.cpp(827)) [265940140] $$begin_record
    Severity: information
    Text: Response successfully routed
    SIP-Start-Line: SIP/2.0 400 Bad request
    SIP-Call-ID: 4c6441b2c080ef665cf2f215504ec217
    SIP-CSeq: 6 UPDATE
    Peer: sfbedge-na.DomainName.com:56440;ms-fe=SFBServerEDGE02.DomainName.pvt
    $$end_record

    TL_INFO(TF_PROTOCOL) [sfbpool-na\SFBServer02]2B50.45AC::12/04/2018-15:15:21.649.0DB8C0AF (SIPStack,SIPAdminLog::ProtocolRecord::Flush:ProtocolRecord.cpp(261)) [265940140]
    Trace-Correlation-Id: 265940140
    Instance-Id: 25FFDD7
    Direction: outgoing
    Peer: sfbedge-na.DomainName.com:56440;ms-fe=SFBServerEDGE02.DomainName.pvt
    Message-Type: response
    Start-Line: SIP/2.0 400 Bad request
    From: "BKA-133-Scissortail Conference Room" <sip:Scissortail.conferenceroom@DomainName.com>;tag=D06CE2B2-2BC71BE8;epid=64167f4ec217
    To: <sip:John.doee@DomainName.com;gruu;opaque=app:conf:focus:id:RQZNG1B5>;tag=B33D0080
    Call-ID: 4c6441b2c080ef665cf2f215504ec217
    CSeq: 6 UPDATE
    Via: SIP/2.0/TLS 172.22.1.28:56440;branch=z9hG4bKCCA9C106.FB07C5699B902399;branched=FALSE;ms-received-port=56440;ms-received-cid=2E75600
    Via: SIP/2.0/TLS 10.4.11.85:41920;branch=z9hG4bKc17931ce2C00FE93;received=4.16.21.154;ms-received-port=41920;ms-received-cid=212FB000
    Content-Length: 0
    ms-diagnostics: 3010;reason="Bad request without Session-Timer extension";processing-cluster="sfbpool-na.DomainName.com";processing-frontend="SFBServer01.DomainName.pvt";source="SFBServer01.DomainName.pvt"
    $$end_record

    TL_INFO(TF_PROTOCOL) [sfbpool-na\SFBServer03]2D5C.5684::12/04/2018-15:15:21.721.1197D33B (SIPStack,SIPAdminLog::ProtocolRecord::Flush:ProtocolRecord.cpp(261)) [1090150418]
    Trace-Correlation-Id: 1090150418
    Instance-Id: 3A8857C
    Direction: incoming
    Peer: sfbpool-na.DomainName.com:63012;ms-fe=SFBServer01.DomainName.pvt
    Message-Type: request
    Start-Line: UPDATE sip:John.doee@DomainName.com;gruu;opaque=app:conf:focus:id:RQZNG1B5 SIP/2.0
    From: "BKA-133-Scissortail Conference Room" <sip:Scissortail.conferenceroom@DomainName.com>;tag=D06CE2B2-2BC71BE8;epid=64167f4ec217
    To: <sip:John.doee@DomainName.com;gruu;opaque=app:conf:focus:id:RQZNG1B5>;tag=B33D0080
    Call-ID: 4c6441b2c080ef665cf2f215504ec217
    CSeq: 6 UPDATE
    Contact: <sip:Scissortail.conferenceroom@DomainName.com;opaque=user:epid:6vHxno1EkV6yhuhrdd9nXQAA;gruu>
    Via: SIP/2.0/TLS 10.3.0.83:63012;branch=z9hG4bKC1D8E307.C3E03DB0F2AAE399;branched=FALSE
    Via: SIP/2.0/TLS 172.22.1.28:56440;branch=z9hG4bKCCA9C106.FB07C5699B902399;branched=FALSE;ms-received-port=56440;ms-received-cid=2E75600
    Via: SIP/2.0/TLS 10.4.11.85:41920;branch=z9hG4bKc17931ce2C00FE93;received=4.16.21.154;ms-received-port=41920;ms-received-cid=212FB000
    Route: <sip:sfbpool-na.DomainName.com:5061;transport=tls;ms-fe=SFBServer03.DomainName.pvt;opaque=state:F:Eu;lr>, <sip:sfbpool-na.DomainName.com:5061;transport=tls;ms-fe=SFBServer01.DomainName.pvt;opaque=state:T;lr>
    Max-Forwards: 68
    Content-Length: 0
    ms-edge-proxy-message-trust: ms-source-type=InternetUser;ms-ep-fqdn=sfbedge-na.DomainName.com;ms-source-verified-user=verified
    P-Asserted-Identity: "BKA-133-Scissortail Conference Room" <sip:Scissortail.conferenceroom@DomainName.com>,<tel:+19182594829;ext=24829>
    $$end_record

    TL_INFO(TF_DIAG) [sfbpool-na\SFBServer03]2D5C.5684::12/04/2018-15:15:21.721.1197D33C (SIPStack,SIPAdminLog::WriteDiagnosticEvent:SIPAdminLog.cpp(827)) [1090150418] $$begin_record
    Severity: information
    Text: Routed a request that came from a server trusted for routing
    SIP-Start-Line: UPDATE sip:John.doee@DomainName.com;gruu;opaque=app:conf:focus:id:RQZNG1B5 SIP/2.0
    SIP-Call-ID: 4c6441b2c080ef665cf2f215504ec217
    SIP-CSeq: 6 UPDATE
    Peer: sfbpool-na.DomainName.com:5061;ms-fe=SFBServer01.DomainName.pvt
    $$end_record


    TL_INFO(TF_PROTOCOL) [sfbpool-na\SFBServer03]2D5C.5684::12/04/2018-15:15:21.721.1197D33D (SIPStack,SIPAdminLog::ProtocolRecord::Flush:ProtocolRecord.cpp(261)) [1090150418]
    Trace-Correlation-Id: 1090150418
    Instance-Id: 3A8857C
    Direction: outgoing
    Peer: sfbpool-na.DomainName.com:5061;ms-fe=SFBServer01.DomainName.pvt
    Message-Type: request
    Start-Line: UPDATE sip:John.doee@DomainName.com;gruu;opaque=app:conf:focus:id:RQZNG1B5 SIP/2.0
    From: "BKA-133-Scissortail Conference Room" <sip:Scissortail.conferenceroom@DomainName.com>;tag=D06CE2B2-2BC71BE8;epid=64167f4ec217
    To: <sip:John.doee@DomainName.com;gruu;opaque=app:conf:focus:id:RQZNG1B5>;tag=B33D0080
    Call-ID: 4c6441b2c080ef665cf2f215504ec217
    CSeq: 6 UPDATE
    Contact: <sip:Scissortail.conferenceroom@DomainName.com;opaque=user:epid:6vHxno1EkV6yhuhrdd9nXQAA;gruu>
    Via: SIP/2.0/TLS 10.3.0.84:52700;branch=z9hG4bK30C80A1E.05476C5CD5659399;branched=FALSE
    Via: SIP/2.0/TLS 10.3.0.83:63012;branch=z9hG4bKC1D8E307.C3E03DB0F2AAE399;branched=FALSE;ms-received-port=63012;ms-received-cid=360D500
    Via: SIP/2.0/TLS 172.22.1.28:56440;branch=z9hG4bKCCA9C106.FB07C5699B902399;branched=FALSE;ms-received-port=56440;ms-received-cid=2E75600
    Via: SIP/2.0/TLS 10.4.11.85:41920;branch=z9hG4bKc17931ce2C00FE93;received=4.16.21.154;ms-received-port=41920;ms-received-cid=212FB000
    Route: <sip:sfbpool-na.DomainName.com:5061;transport=tls;ms-fe=SFBServer01.DomainName.pvt;opaque=state:T;lr>
    Record-Route: <sip:sfbpool-na.DomainName.com:5061;transport=tls;ms-fe=SFBServer03.DomainName.pvt;opaque=state:T;lr>;tag=DB0FC4217E6435F299F1453B2765B608
    Max-Forwards: 67
    Content-Length: 0
    ms-edge-proxy-message-trust: ms-source-type=InternetUser;ms-ep-fqdn=sfbedge-na.DomainName.com;ms-source-verified-user=verified
    P-Asserted-Identity: "BKA-133-Scissortail Conference Room" <sip:Scissortail.conferenceroom@DomainName.com>,<tel:+19182594829;ext=24829>
    $$end_record


    TL_INFO(TF_PROTOCOL) [sfbpool-na\SFBServer03]2D5C.5684::12/04/2018-15:15:21.721.1197D33E (SIPStack,SIPAdminLog::ProtocolRecord::Flush:ProtocolRecord.cpp(261)) [265940140]
    Trace-Correlation-Id: 265940140
    Instance-Id: 3A8857D
    Direction: incoming
    Peer: sfbpool-na.DomainName.com:5061;ms-fe=SFBServer01.DomainName.pvt
    Message-Type: response
    Start-Line: SIP/2.0 400 Bad request
    From: "BKA-133-Scissortail Conference Room" <sip:Scissortail.conferenceroom@DomainName.com>;tag=D06CE2B2-2BC71BE8;epid=64167f4ec217
    To: <sip:John.doee@DomainName.com;gruu;opaque=app:conf:focus:id:RQZNG1B5>;tag=B33D0080
    Call-ID: 4c6441b2c080ef665cf2f215504ec217
    CSeq: 6 UPDATE
    Via: SIP/2.0/TLS 10.3.0.84:52700;branch=z9hG4bK30C80A1E.05476C5CD5659399;branched=FALSE;ms-received-port=52700;ms-received-cid=3991000
    Via: SIP/2.0/TLS 10.3.0.83:63012;branch=z9hG4bKC1D8E307.C3E03DB0F2AAE399;branched=FALSE;ms-received-port=63012;ms-received-cid=360D500
    Via: SIP/2.0/TLS 172.22.1.28:56440;branch=z9hG4bKCCA9C106.FB07C5699B902399;branched=FALSE;ms-received-port=56440;ms-received-cid=2E75600
    Via: SIP/2.0/TLS 10.4.11.85:41920;branch=z9hG4bKc17931ce2C00FE93;received=4.16.21.154;ms-received-port=41920;ms-received-cid=212FB000
    Content-Length: 0
    ms-diagnostics: 3010;reason="Bad request without Session-Timer extension";processing-cluster="sfbpool-na.DomainName.com";processing-frontend="SFBServer01.DomainName.pvt";source="SFBServer01.DomainName.pvt"
    $$end_record


    TL_INFO(TF_DIAG) [sfbpool-na\SFBServer03]2D5C.5684::12/04/2018-15:15:21.721.1197D33F (SIPStack,SIPAdminLog::WriteDiagnosticEvent:SIPAdminLog.cpp(827)) [265940140] $$begin_record
    Severity: information
    Text: Response successfully routed
    SIP-Start-Line: SIP/2.0 400 Bad request
    SIP-Call-ID: 4c6441b2c080ef665cf2f215504ec217
    SIP-CSeq: 6 UPDATE
    Peer: sfbpool-na.DomainName.com:63012;ms-fe=SFBServer01.DomainName.pvt
    $$end_record


    TL_INFO(TF_PROTOCOL) [sfbpool-na\SFBServer03]2D5C.5684::12/04/2018-15:15:21.722.1197D340 (SIPStack,SIPAdminLog::ProtocolRecord::Flush:ProtocolRecord.cpp(261)) [265940140]
    Trace-Correlation-Id: 265940140
    Instance-Id: 3A8857D
    Direction: outgoing
    Peer: sfbpool-na.DomainName.com:63012;ms-fe=SFBServer01.DomainName.pvt
    Message-Type: response
    Start-Line: SIP/2.0 400 Bad request
    From: "BKA-133-Scissortail Conference Room" <sip:Scissortail.conferenceroom@DomainName.com>;tag=D06CE2B2-2BC71BE8;epid=64167f4ec217
    To: <sip:John.doee@DomainName.com;gruu;opaque=app:conf:focus:id:RQZNG1B5>;tag=B33D0080
    Call-ID: 4c6441b2c080ef665cf2f215504ec217
    CSeq: 6 UPDATE
    Via: SIP/2.0/TLS 10.3.0.83:63012;branch=z9hG4bKC1D8E307.C3E03DB0F2AAE399;branched=FALSE;ms-received-port=63012;ms-received-cid=360D500
    Via: SIP/2.0/TLS 172.22.1.28:56440;branch=z9hG4bKCCA9C106.FB07C5699B902399;branched=FALSE;ms-received-port=56440;ms-received-cid=2E75600
    Via: SIP/2.0/TLS 10.4.11.85:41920;branch=z9hG4bKc17931ce2C00FE93;received=4.16.21.154;ms-received-port=41920;ms-received-cid=212FB000
    Content-Length: 0
    ms-diagnostics: 3010;reason="Bad request without Session-Timer extension";processing-cluster="sfbpool-na.DomainName.com";processing-frontend="SFBServer01.DomainName.pvt";source="SFBServer01.DomainName.pvt"
    $$end_record


    TL_INFO(TF_PROTOCOL) [sfbpool-na\SFBServer01]28D4.1D40::12/04/2018-15:15:21.810.10C2CAFF (SIPStack,SIPAdminLog::ProtocolRecord::Flush:ProtocolRecord.cpp(261)) [1090150418]
    Trace-Correlation-Id: 1090150418
    Instance-Id: 2741415
    Direction: incoming
    Peer: sfbpool-na.DomainName.com:52700;ms-fe=SFBServer01.DomainName.pvt
    Message-Type: request
    Start-Line: UPDATE sip:John.doee@DomainName.com;gruu;opaque=app:conf:focus:id:RQZNG1B5 SIP/2.0
    From: "BKA-133-Scissortail Conference Room" <sip:Scissortail.conferenceroom@DomainName.com>;tag=D06CE2B2-2BC71BE8;epid=64167f4ec217
    To: <sip:John.doee@DomainName.com;gruu;opaque=app:conf:focus:id:RQZNG1B5>;tag=B33D0080
    Call-ID: 4c6441b2c080ef665cf2f215504ec217
    CSeq: 6 UPDATE
    Contact: <sip:Scissortail.conferenceroom@DomainName.com;opaque=user:epid:6vHxno1EkV6yhuhrdd9nXQAA;gruu>
    Via: SIP/2.0/TLS 10.3.0.84:52700;branch=z9hG4bK30C80A1E.05476C5CD5659399;branched=FALSE
    Via: SIP/2.0/TLS 10.3.0.83:63012;branch=z9hG4bKC1D8E307.C3E03DB0F2AAE399;branched=FALSE;ms-received-port=63012;ms-received-cid=360D500
    Via: SIP/2.0/TLS 172.22.1.28:56440;branch=z9hG4bKCCA9C106.FB07C5699B902399;branched=FALSE;ms-received-port=56440;ms-received-cid=2E75600
    Via: SIP/2.0/TLS 10.4.11.85:41920;branch=z9hG4bKc17931ce2C00FE93;received=4.16.21.154;ms-received-port=41920;ms-received-cid=212FB000
    Route: <sip:sfbpool-na.DomainName.com:5061;transport=tls;ms-fe=SFBServer01.DomainName.pvt;opaque=state:T;lr>
    Record-Route: <sip:sfbpool-na.DomainName.com:5061;transport=tls;ms-fe=SFBServer03.DomainName.pvt;opaque=state:T;lr>;tag=DB0FC4217E6435F299F1453B2765B608
    Max-Forwards: 67
    Content-Length: 0
    ms-edge-proxy-message-trust: ms-source-type=InternetUser;ms-ep-fqdn=sfbedge-na.DomainName.com;ms-source-verified-user=verified
    P-Asserted-Identity: "BKA-133-Scissortail Conference Room" <sip:Scissortail.conferenceroom@DomainName.com>,<tel:+19182594829;ext=24829>
    $$end_record


    TL_INFO(TF_DIAG) [sfbpool-na\SFBServer01]28D4.1D40::12/04/2018-15:15:21.810.10C2CB03 (SIPStack,SIPAdminLog::WriteDiagnosticEvent:SIPAdminLog.cpp(827)) [1090150418] $$begin_record
    Severity: information
    Text: Routed a locally generated response
    SIP-Start-Line: SIP/2.0 400 Bad request
    SIP-Call-ID: 4c6441b2c080ef665cf2f215504ec217
    SIP-CSeq: 6 UPDATE
    Peer: sfbpool-na.DomainName.com:52700;ms-fe=SFBServer01.DomainName.pvt
    $$end_record


    TL_INFO(TF_PROTOCOL) [sfbpool-na\SFBServer01]28D4.1D40::12/04/2018-15:15:21.810.10C2CB04 (SIPStack,SIPAdminLog::ProtocolRecord::Flush:ProtocolRecord.cpp(261)) [1090150418]
    Trace-Correlation-Id: 1090150418
    Instance-Id: 2741416
    Direction: outgoing;source="local"
    Peer: sfbpool-na.DomainName.com:52700;ms-fe=SFBServer01.DomainName.pvt
    Message-Type: response
    Start-Line: SIP/2.0 400 Bad request
    From: "BKA-133-Scissortail Conference Room" <sip:Scissortail.conferenceroom@DomainName.com>;tag=D06CE2B2-2BC71BE8;epid=64167f4ec217
    To: <sip:John.doee@DomainName.com;gruu;opaque=app:conf:focus:id:RQZNG1B5>;tag=B33D0080
    Call-ID: 4c6441b2c080ef665cf2f215504ec217
    CSeq: 6 UPDATE
    Via: SIP/2.0/TLS 10.3.0.84:52700;branch=z9hG4bK30C80A1E.05476C5CD5659399;branched=FALSE;ms-received-port=52700;ms-received-cid=3991000
    Via: SIP/2.0/TLS 10.3.0.83:63012;branch=z9hG4bKC1D8E307.C3E03DB0F2AAE399;branched=FALSE;ms-received-port=63012;ms-received-cid=360D500
    Via: SIP/2.0/TLS 172.22.1.28:56440;branch=z9hG4bKCCA9C106.FB07C5699B902399;branched=FALSE;ms-received-port=56440;ms-received-cid=2E75600
    Via: SIP/2.0/TLS 10.4.11.85:41920;branch=z9hG4bKc17931ce2C00FE93;received=4.16.21.154;ms-received-port=41920;ms-received-cid=212FB000
    Content-Length: 0
    ms-diagnostics: 3010;reason="Bad request without Session-Timer extension";processing-cluster="sfbpool-na.DomainName.com";processing-frontend="SFBServer01.DomainName.pvt";source="SFBServer01.DomainName.pvt"
    $$end_record


    TL_INFO(TF_PROTOCOL) [sfbpool-na\SFBServer02]2B50.30A4::12/04/2018-15:15:56.276.0DB8DA84 (SIPStack,SIPAdminLog::ProtocolRecord::Flush:ProtocolRecord.cpp(261)) [265940140]
    Trace-Correlation-Id: 265940140
    Instance-Id: 2600340
    Direction: incoming
    Peer: sfbpool-na.DomainName.com:52745;ms-fe=SFBServer03.DomainName.pvt
    Message-Type: request
    Start-Line: BYE sip:Scissortail.conferenceroom@4.16.21.154:41920;transport=tls;ms-received-cid=212FB000;grid SIP/2.0
    From: <sip:John.doee@DomainName.com;gruu;opaque=app:conf:focus:id:RQZNG1B5>;tag=B33D0080
    To: <sip:Scissortail.conferenceroom@DomainName.com>;tag=D06CE2B2-2BC71BE8;epid=64167f4ec217
    Call-ID: 4c6441b2c080ef665cf2f215504ec217
    CSeq: 2147483645 BYE
    Via: SIP/2.0/TLS 10.3.0.84:52745;branch=z9hG4bK161B0AB4.9EBF131EDDD9A3BC;branched=FALSE
    Via: SIP/2.0/TLS 10.3.0.99:58999;branch=z9hG4bKB18ACF7F.53C0D5C26D5753BC;branched=FALSE;ms-received-port=58999;ms-received-cid=360E400
    Route: <sip:sfbpool-na.DomainName.com:5061;transport=tls;ms-fe=SFBServer02.DomainName.pvt;opaque=state:Ee.frVD6r_ZJKKkHwsa6fngKesAAA;lr>
    Route: <sip:sfbedge-na.DomainName.com:5061;transport=tls;ms-fe=SFBServerEDGE01.DomainName.pvt;opaque=state:Ee.bjSMz0O5rLbRhuI6eOrc3tdAAA;lr>
    Max-Forwards: 69
    Content-Length: 0
    ms-diagnostics-public: 3186;reason="Invite dialog terminated since new dialog replaced it"
    $$end_record


    TL_INFO(TF_DIAG) [sfbpool-na\SFBServer02]2B50.2420::12/04/2018-15:15:56.277.0DB8DA8A (SIPStack,SIPAdminLog::WriteDiagnosticEvent:SIPAdminLog.cpp(827)) [265940140] $$begin_record
    Severity: information
    Text: Routed a request that came from a server trusted for routing
    SIP-Start-Line: BYE sip:Scissortail.conferenceroom@4.16.21.154:41920;transport=tls;ms-received-cid=212FB000;grid SIP/2.0
    SIP-Call-ID: 4c6441b2c080ef665cf2f215504ec217
    SIP-CSeq: 2147483645 BYE
    Peer: sfbedge-na.DomainName.com:5061;ms-fe=SFBServerEDGE01.DomainName.pvt
    $$end_record


    TL_INFO(TF_PROTOCOL) [sfbpool-na\SFBServer02]2B50.2420::12/04/2018-15:15:56.277.0DB8DA8B (SIPStack,SIPAdminLog::ProtocolRecord::Flush:ProtocolRecord.cpp(261)) [265940140]
    Trace-Correlation-Id: 265940140
    Instance-Id: 2600340
    Direction: outgoing
    Peer: sfbedge-na.DomainName.com:5061;ms-fe=SFBServerEDGE01.DomainName.pvt
    Message-Type: request
    Start-Line: BYE sip:Scissortail.conferenceroom@4.16.21.154:41920;transport=tls;ms-received-cid=212FB000;grid SIP/2.0
    From: <sip:John.doee@DomainName.com;gruu;opaque=app:conf:focus:id:RQZNG1B5>;tag=B33D0080
    To: <sip:Scissortail.conferenceroom@DomainName.com>;tag=D06CE2B2-2BC71BE8;epid=64167f4ec217
    Call-ID: 4c6441b2c080ef665cf2f215504ec217
    CSeq: 2147483645 BYE
    Via: SIP/2.0/TLS 10.3.0.83:63168;branch=z9hG4bK7C1CC5F2.68B68CC6FB1EF3BC;branched=FALSE
    Via: SIP/2.0/TLS 10.3.0.84:52745;branch=z9hG4bK161B0AB4.9EBF131EDDD9A3BC;branched=FALSE;ms-received-port=52745;ms-received-cid=2E76500
    Via: SIP/2.0/TLS 10.3.0.99:58999;branch=z9hG4bKB18ACF7F.53C0D5C26D5753BC;branched=FALSE;ms-received-port=58999;ms-received-cid=360E400
    Route: <sip:sfbedge-na.DomainName.com:5061;transport=tls;ms-fe=SFBServerEDGE01.DomainName.pvt;opaque=state:Ee.bjSMz0O5rLbRhuI6eOrc3tdAAA;lr>
    Max-Forwards: 68
    Content-Length: 0
    ms-diagnostics-public: 3186;reason="Invite dialog terminated since new dialog replaced it"
    $$end_record


    TL_INFO(TF_PROTOCOL) [sfbpool-na\SFBServer02]2B50.30A4::12/04/2018-15:15:56.292.0DB8DA95 (SIPStack,SIPAdminLog::ProtocolRecord::Flush:ProtocolRecord.cpp(261)) [29452268]
    Trace-Correlation-Id: 29452268
    Instance-Id: 2600344
    Direction: incoming
    Peer: sfbedge-na.DomainName.com:5061;ms-fe=SFBServerEDGE01.DomainName.pvt
    Message-Type: response
    Start-Line: SIP/2.0 200 OK
    From: <sip:John.doee@DomainName.com;gruu;opaque=app:conf:focus:id:RQZNG1B5>;tag=B33D0080
    To: "BKA-133-Scissortail Conference Room" <sip:Scissortail.conferenceroom@DomainName.com>;tag=D06CE2B2-2BC71BE8;epid=64167f4ec217
    Call-ID: 4c6441b2c080ef665cf2f215504ec217
    CSeq: 2147483645 BYE
    Contact: <sip:Scissortail.conferenceroom@DomainName.com;opaque=user:epid:6vHxno1EkV6yhuhrdd9nXQAA;gruu>
    Via: SIP/2.0/TLS 10.3.0.83:63168;branch=z9hG4bK7C1CC5F2.68B68CC6FB1EF3BC;branched=FALSE;ms-received-port=63168;ms-received-cid=23175B00
    Via: SIP/2.0/TLS 10.3.0.84:52745;branch=z9hG4bK161B0AB4.9EBF131EDDD9A3BC;branched=FALSE;ms-received-port=52745;ms-received-cid=2E76500
    Via: SIP/2.0/TLS 10.3.0.99:58999;branch=z9hG4bKB18ACF7F.53C0D5C26D5753BC;branched=FALSE;ms-received-port=58999;ms-received-cid=360E400
    Content-Length: 0
    ms-edge-proxy-message-trust: ms-source-type=InternetUser;ms-ep-fqdn=sfbedge-na.DomainName.com;ms-source-verified-user=verified
    $$end_record


    TL_INFO(TF_DIAG) [sfbpool-na\SFBServer02]2B50.30A4::12/04/2018-15:15:56.293.0DB8DA97 (SIPStack,SIPAdminLog::WriteDiagnosticEvent:SIPAdminLog.cpp(827)) [29452268] $$begin_record
    Severity: information
    Text: Response successfully routed
    SIP-Start-Line: SIP/2.0 200 OK
    SIP-Call-ID: 4c6441b2c080ef665cf2f215504ec217
    SIP-CSeq: 2147483645 BYE
    Peer: sfbpool-na.DomainName.com:52745;ms-fe=SFBServer03.DomainName.pvt
    $$end_record


    TL_INFO(TF_PROTOCOL) [sfbpool-na\SFBServer02]2B50.30A4::12/04/2018-15:15:56.293.0DB8DA98 (SIPStack,SIPAdminLog::ProtocolRecord::Flush:ProtocolRecord.cpp(261)) [29452268]
    Trace-Correlation-Id: 29452268
    Instance-Id: 2600344
    Direction: outgoing
    Peer: sfbpool-na.DomainName.com:52745;ms-fe=SFBServer03.DomainName.pvt
    Message-Type: response
    Start-Line: SIP/2.0 200 OK
    From: <sip:John.doee@DomainName.com;gruu;opaque=app:conf:focus:id:RQZNG1B5>;tag=B33D0080
    To: "BKA-133-Scissortail Conference Room" <sip:Scissortail.conferenceroom@DomainName.com>;tag=D06CE2B2-2BC71BE8;epid=64167f4ec217
    Call-ID: 4c6441b2c080ef665cf2f215504ec217
    CSeq: 2147483645 BYE
    Contact: <sip:Scissortail.conferenceroom@DomainName.com;opaque=user:epid:6vHxno1EkV6yhuhrdd9nXQAA;gruu>
    Via: SIP/2.0/TLS 10.3.0.84:52745;branch=z9hG4bK161B0AB4.9EBF131EDDD9A3BC;branched=FALSE;ms-received-port=52745;ms-received-cid=2E76500
    Via: SIP/2.0/TLS 10.3.0.99:58999;branch=z9hG4bKB18ACF7F.53C0D5C26D5753BC;branched=FALSE;ms-received-port=58999;ms-received-cid=360E400
    Content-Length: 0
    ms-edge-proxy-message-trust: ms-source-type=InternetUser;ms-ep-fqdn=sfbedge-na.DomainName.com;ms-source-verified-user=verified
    P-Asserted-Identity: "BKA-133-Scissortail Conference Room" <sip:Scissortail.conferenceroom@DomainName.com>,<tel:+19182594829;ext=24829>
    $$end_record


    TL_INFO(TF_PROTOCOL) [sfbpool-na\SFBServer03]2D5C.159C::12/04/2018-15:15:56.347.1197F37B (SIPStack,SIPAdminLog::ProtocolRecord::Flush:ProtocolRecord.cpp(261)) [265940140]
    Trace-Correlation-Id: 265940140
    Instance-Id: 3A88CC0
    Direction: incoming
    Peer: sfbpool-na.DomainName.com:58999;ms-fe=SFBServer01.DomainName.pvt
    Message-Type: request
    Start-Line: BYE sip:Scissortail.conferenceroom@DomainName.com;opaque=user:epid:6vHxno1EkV6yhuhrdd9nXQAA;gruu SIP/2.0
    From: <sip:John.doee@DomainName.com;gruu;opaque=app:conf:focus:id:RQZNG1B5>;tag=B33D0080
    To: <sip:Scissortail.conferenceroom@DomainName.com>;tag=D06CE2B2-2BC71BE8;epid=64167f4ec217
    Call-ID: 4c6441b2c080ef665cf2f215504ec217
    CSeq: 2147483645 BYE
    Via: SIP/2.0/TLS 10.3.0.99:58999;branch=z9hG4bKB18ACF7F.53C0D5C26D5753BC;branched=FALSE
    Route: <sip:sfbpool-na.DomainName.com:5061;transport=tls;ms-fe=SFBServer03.DomainName.pvt;opaque=state:T;lr>
    Max-Forwards: 70
    Content-Length: 0
    ms-diagnostics-public: 3186;reason="Invite dialog terminated since new dialog replaced it"
    $$end_record


    TL_INFO(TF_DIAG) [sfbpool-na\SFBServer03]2D5C.159C::12/04/2018-15:15:56.348.1197F37F (SIPStack,SIPAdminLog::WriteDiagnosticEvent:SIPAdminLog.cpp(827)) [265940140] $$begin_record
    Severity: information
    Text: Routed a request that came from a server trusted for routing
    SIP-Start-Line: BYE sip:Scissortail.conferenceroom@4.16.21.154:41920;transport=tls;ms-received-cid=212FB000;grid SIP/2.0
    SIP-Call-ID: 4c6441b2c080ef665cf2f215504ec217
    SIP-CSeq: 2147483645 BYE
    Peer: sfbpool-na.DomainName.com:5061;ms-fe=SFBServer02.DomainName.pvt
    $$end_record


    TL_INFO(TF_PROTOCOL) [sfbpool-na\SFBServer03]2D5C.159C::12/04/2018-15:15:56.348.1197F380 (SIPStack,SIPAdminLog::ProtocolRecord::Flush:ProtocolRecord.cpp(261)) [265940140]
    Trace-Correlation-Id: 265940140
    Instance-Id: 3A88CC0
    Direction: outgoing
    Peer: sfbpool-na.DomainName.com:5061;ms-fe=SFBServer02.DomainName.pvt
    Message-Type: request
    Start-Line: BYE sip:Scissortail.conferenceroom@4.16.21.154:41920;transport=tls;ms-received-cid=212FB000;grid SIP/2.0
    From: <sip:John.doee@DomainName.com;gruu;opaque=app:conf:focus:id:RQZNG1B5>;tag=B33D0080
    To: <sip:Scissortail.conferenceroom@DomainName.com>;tag=D06CE2B2-2BC71BE8;epid=64167f4ec217
    Call-ID: 4c6441b2c080ef665cf2f215504ec217
    CSeq: 2147483645 BYE
    Via: SIP/2.0/TLS 10.3.0.84:52745;branch=z9hG4bK161B0AB4.9EBF131EDDD9A3BC;branched=FALSE
    Via: SIP/2.0/TLS 10.3.0.99:58999;branch=z9hG4bKB18ACF7F.53C0D5C26D5753BC;branched=FALSE;ms-received-port=58999;ms-received-cid=360E400
    Route: <sip:sfbpool-na.DomainName.com:5061;transport=tls;ms-fe=SFBServer02.DomainName.pvt;opaque=state:Ee.frVD6r_ZJKKkHwsa6fngKesAAA;lr>
    Route: <sip:sfbedge-na.DomainName.com:5061;transport=tls;ms-fe=SFBServerEDGE01.DomainName.pvt;opaque=state:Ee.bjSMz0O5rLbRhuI6eOrc3tdAAA;lr>
    Max-Forwards: 69
    Content-Length: 0
    ms-diagnostics-public: 3186;reason="Invite dialog terminated since new dialog replaced it"
    $$end_record


    TL_INFO(TF_PROTOCOL) [sfbpool-na\SFBServer03]2D5C.2700::12/04/2018-15:15:56.365.1197F39B (SIPStack,SIPAdminLog::ProtocolRecord::Flush:ProtocolRecord.cpp(261)) [29452268]
    Trace-Correlation-Id: 29452268
    Instance-Id: 3A88CCA
    Direction: incoming
    Peer: sfbpool-na.DomainName.com:5061;ms-fe=SFBServer02.DomainName.pvt
    Message-Type: response
    Start-Line: SIP/2.0 200 OK
    From: <sip:John.doee@DomainName.com;gruu;opaque=app:conf:focus:id:RQZNG1B5>;tag=B33D0080
    To: "BKA-133-Scissortail Conference Room" <sip:Scissortail.conferenceroom@DomainName.com>;tag=D06CE2B2-2BC71BE8;epid=64167f4ec217
    Call-ID: 4c6441b2c080ef665cf2f215504ec217
    CSeq: 2147483645 BYE
    Contact: <sip:Scissortail.conferenceroom@DomainName.com;opaque=user:epid:6vHxno1EkV6yhuhrdd9nXQAA;gruu>
    Via: SIP/2.0/TLS 10.3.0.84:52745;branch=z9hG4bK161B0AB4.9EBF131EDDD9A3BC;branched=FALSE;ms-received-port=52745;ms-received-cid=2E76500
    Via: SIP/2.0/TLS 10.3.0.99:58999;branch=z9hG4bKB18ACF7F.53C0D5C26D5753BC;branched=FALSE;ms-received-port=58999;ms-received-cid=360E400
    Content-Length: 0
    ms-edge-proxy-message-trust: ms-source-type=InternetUser;ms-ep-fqdn=sfbedge-na.DomainName.com;ms-source-verified-user=verified
    P-Asserted-Identity: "BKA-133-Scissortail Conference Room" <sip:Scissortail.conferenceroom@DomainName.com>,<tel:+19182594829;ext=24829>
    $$end_record


    TL_INFO(TF_DIAG) [sfbpool-na\SFBServer03]2D5C.5BF8::12/04/2018-15:15:56.366.1197F3A0 (SIPStack,SIPAdminLog::WriteDiagnosticEvent:SIPAdminLog.cpp(827)) [29452268] $$begin_record
    Severity: information
    Text: Response successfully routed
    SIP-Start-Line: SIP/2.0 200 OK
    SIP-Call-ID: 4c6441b2c080ef665cf2f215504ec217
    SIP-CSeq: 2147483645 BYE
    Peer: sfbpool-na.DomainName.com:58999;ms-fe=SFBServer01.DomainName.pvt
    $$end_record


    TL_INFO(TF_PROTOCOL) [sfbpool-na\SFBServer03]2D5C.5BF8::12/04/2018-15:15:56.366.1197F3A1 (SIPStack,SIPAdminLog::ProtocolRecord::Flush:ProtocolRecord.cpp(261)) [29452268]
    Trace-Correlation-Id: 29452268
    Instance-Id: 3A88CCA
    Direction: outgoing
    Peer: sfbpool-na.DomainName.com:58999;ms-fe=SFBServer01.DomainName.pvt
    Message-Type: response
    Start-Line: SIP/2.0 200 OK
    From: <sip:John.doee@DomainName.com;gruu;opaque=app:conf:focus:id:RQZNG1B5>;tag=B33D0080
    To: "BKA-133-Scissortail Conference Room" <sip:Scissortail.conferenceroom@DomainName.com>;tag=D06CE2B2-2BC71BE8;epid=64167f4ec217
    Call-ID: 4c6441b2c080ef665cf2f215504ec217
    CSeq: 2147483645 BYE
    Contact: <sip:Scissortail.conferenceroom@DomainName.com;opaque=user:epid:6vHxno1EkV6yhuhrdd9nXQAA;gruu>
    Via: SIP/2.0/TLS 10.3.0.99:58999;branch=z9hG4bKB18ACF7F.53C0D5C26D5753BC;branched=FALSE;ms-received-port=58999;ms-received-cid=360E400
    Content-Length: 0
    ms-edge-proxy-message-trust: ms-source-type=InternetUser;ms-ep-fqdn=sfbedge-na.DomainName.com;ms-source-verified-user=verified
    P-Asserted-Identity: "BKA-133-Scissortail Conference Room" <sip:Scissortail.conferenceroom@DomainName.com>,<tel:+19182594829;ext=24829>
    $$end_record


    TL_INFO(TF_DIAG) [sfbpool-na\SFBServer01]28D4.2D40::12/04/2018-15:15:56.436.10C2F2AD (SIPStack,SIPAdminLog::WriteDiagnosticEvent:SIPAdminLog.cpp(827)) [265940140] $$begin_record
    Severity: information
    Text: Routed a request on behalf of an application
    SIP-Start-Line: BYE sip:Scissortail.conferenceroom@DomainName.com;opaque=user:epid:6vHxno1EkV6yhuhrdd9nXQAA;gruu SIP/2.0
    SIP-Call-ID: 4c6441b2c080ef665cf2f215504ec217
    SIP-CSeq: 2147483645 BYE
    Peer: sfbpool-na.DomainName.com:5061;ms-fe=SFBServer03.DomainName.pvt
    Data: application="http://www.microsoft.com/LCS/UserServices"
    $$end_record


    TL_INFO(TF_PROTOCOL) [sfbpool-na\SFBServer01]28D4.2D40::12/04/2018-15:15:56.436.10C2F2AE (SIPStack,SIPAdminLog::ProtocolRecord::Flush:ProtocolRecord.cpp(261)) [265940140]
    Trace-Correlation-Id: 265940140
    Instance-Id: 2741AE5
    Direction: outgoing;source="local"
    Peer: sfbpool-na.DomainName.com:5061;ms-fe=SFBServer03.DomainName.pvt
    Message-Type: request
    Start-Line: BYE sip:Scissortail.conferenceroom@DomainName.com;opaque=user:epid:6vHxno1EkV6yhuhrdd9nXQAA;gruu SIP/2.0
    From: <sip:John.doee@DomainName.com;gruu;opaque=app:conf:focus:id:RQZNG1B5>;tag=B33D0080
    To: <sip:Scissortail.conferenceroom@DomainName.com>;tag=D06CE2B2-2BC71BE8;epid=64167f4ec217
    Call-ID: 4c6441b2c080ef665cf2f215504ec217
    CSeq: 2147483645 BYE
    Via: SIP/2.0/TLS 10.3.0.99:58999;branch=z9hG4bKB18ACF7F.53C0D5C26D5753BC;branched=FALSE
    Route: <sip:sfbpool-na.DomainName.com:5061;transport=tls;ms-fe=SFBServer03.DomainName.pvt;opaque=state:T;lr>
    Max-Forwards: 70
    Content-Length: 0
    ms-diagnostics-public: 3186;reason="Invite dialog terminated since new dialog replaced it"
    $$end_record


    TL_INFO(TF_PROTOCOL) [sfbpool-na\SFBServer01]28D4.1D40::12/04/2018-15:15:56.456.10C2F2D2 (SIPStack,SIPAdminLog::ProtocolRecord::Flush:ProtocolRecord.cpp(261)) [29452268]
    Trace-Correlation-Id: 29452268
    Instance-Id: 2741AEF
    Direction: incoming
    Peer: sfbpool-na.DomainName.com:5061;ms-fe=SFBServer03.DomainName.pvt
    Message-Type: response
    Start-Line: SIP/2.0 200 OK
    From: <sip:John.doee@DomainName.com;gruu;opaque=app:conf:focus:id:RQZNG1B5>;tag=B33D0080
    To: "BKA-133-Scissortail Conference Room" <sip:Scissortail.conferenceroom@DomainName.com>;tag=D06CE2B2-2BC71BE8;epid=64167f4ec217
    Call-ID: 4c6441b2c080ef665cf2f215504ec217
    CSeq: 2147483645 BYE
    Contact: <sip:Scissortail.conferenceroom@DomainName.com;opaque=user:epid:6vHxno1EkV6yhuhrdd9nXQAA;gruu>
    Via: SIP/2.0/TLS 10.3.0.99:58999;branch=z9hG4bKB18ACF7F.53C0D5C26D5753BC;branched=FALSE;ms-received-port=58999;ms-received-cid=360E400
    Content-Length: 0
    ms-edge-proxy-message-trust: ms-source-type=InternetUser;ms-ep-fqdn=sfbedge-na.DomainName.com;ms-source-verified-user=verified
    P-Asserted-Identity: "BKA-133-Scissortail Conference Room" <sip:Scissortail.conferenceroom@DomainName.com>,<tel:+19182594829;ext=24829>
    $$end_record


    Brody Kilpatrick

    Tuesday, December 4, 2018 4:35 PM

All replies

  • Hi,

    Did it work normally before? Or have you made any changes before the issue occurs?

    Please check the DNS record for gateway and the listening port and please make sure you use the correct IP address provided by sip trunk provider.

    I will share a document for your reference:

    https://technet.microsoft.com/en-us/library/gg398170%28v=ocs.15%29.aspx

    http://blog.insidelync.com/2013/04/sip-trunking-101-with-lync-server-2013/

    Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.

     

    Kind regards,

    Calvin Liu


    Please remember to mark the reply as an answer if you find it is helpful. It will assist others who has similar issue. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    • Proposed as answer by Calvin-Liu Friday, December 14, 2018 10:07 AM
    Wednesday, December 5, 2018 9:52 AM
  • It happens in the middle of the conference and doesn't impact other conferences or people. It only happens with this single polycom device. The device may be in the meeting for 15 or more minutes before it happens. I don't think it has to do with DNS or an IP address, otherwise it would be more widespread.

    Brody Kilpatrick

    Wednesday, December 5, 2018 9:38 PM
  • Hi,

    If it only impact the specific device, then yes as you said there won't any changes have to be made from DNS side. It should be caused by some configuration issue from Polycom that blocked the connection. Please have a check and make sure the Polycorn have installed the latest UCS firmware.

    Kind regards,

    Calvin Liu


    Please remember to mark the reply as an answer if you find it is helpful. It will assist others who has similar issue. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    • Proposed as answer by Calvin-Liu Tuesday, December 18, 2018 4:24 PM
    Monday, December 10, 2018 1:41 AM
  • Hi,

    Are there any update for this issue, if the reply is helpful to you, please try to mark it as an answer, it will help others who has similar issue. :) 

    Kind regards,

    Calvin Liu


    Please remember to mark the reply as an answer if you find it is helpful. It will assist others who has similar issue. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Friday, December 14, 2018 10:07 AM