drachtio-sip-message.log

drachtio.log

2019-06-19 09:51:16.713740 Starting drachtio version v0.8.2-1-ga65722f
2019-06-19 09:51:16.713918 Logging threshold:                     5
2019-06-19 09:51:16.713961 DrachtioController::run: Main thread id: 140338025555776
2019-06-19 09:51:16.714001 DrachtioController::run listening for applications on tcp port 9022 and tls port 0
2019-06-19 09:51:16.714306 ClientController::ClientController done setting tls options: 
2019-06-19 09:51:16.714332 Client controller thread id: 140338025555776
2019-06-19 09:51:16.714447 ClientController::start_accept_tcp
2019-06-19 09:51:16.714499 Prometheus support disabled
2019-06-19 09:51:16.714531 Client controller thread id: 140337920739072
2019-06-19 09:51:16.714590 ClientController::threadFunc - ClientController: io_context run loop started (or restarted)
2019-06-19 09:51:16.714603 DrachtioController::run: starting sip stack on sip:192.168.111.32:5060;transport=udp,tcp
2019-06-19 09:51:16.714641 SipTransport::getBindableContactUri: sip:192.168.111.32:5060;transport=udp,tcp
2019-06-19 09:51:16.715550 SipTransport::addTransports - creating transport: 0x107bed0: udp/192.168.111.32:5060
2019-06-19 09:51:16.716134 SipTransport::addTransports - creating transport: 0x107c380: tcp/192.168.111.32:5060
2019-06-19 09:51:16.716673 SipTransport::logTransports - there are : 2 transports
2019-06-19 09:51:16.716696 SipTransport::logTransports - tcp/192.168.111.32:5060 (sip:192.168.111.32:5060;transport=udp,tcp, external-ip: , local-net: )
2019-06-19 09:51:16.716716 SipTransport::logTransports - udp/192.168.111.32:5060 (sip:192.168.111.32:5060;transport=udp,tcp, external-ip: , local-net: ), mtu size: 1300
2019-06-19 09:51:16.716752 DrachtioController::run - sip timers: T1: 500ms, T2: 4000ms, T4: 5000ms, T1X64: 32000ms
2019-06-19 09:51:16.716788 Starting sofia event loop in main thread: 140338025555776
2019-06-19 09:51:21.080192 ClientController::accept_handler_tcp - got connection
2019-06-19 09:51:21.080305 Client::start - Received connection from client at 192.168.111.145:49922
2019-06-19 09:51:21.080329 ClientController::join - Added client, count of connected clients is now: 1
2019-06-19 09:51:21.080355 ClientController::start_accept_tcp
2019-06-19 09:51:21.082737 Client::read_handler read: 597ec911-2098-4247-8b54-ab9af4848c05|authenticate|cymru|

2019-06-19 09:51:21.082810 Client::processAuthentication - added tags 
2019-06-19 09:51:21.082846 Client::processAuthentication - validating secret cymru
2019-06-19 09:51:21.082906 Client::processAuthentication - secret validated successfully: cymru
2019-06-19 09:51:21.082928 Sending response: 151#55bed681-2180-4a70-a996-2b9263e07d04|response|597ec911-2098-4247-8b54-ab9af4848c05|OK|tcp/192.168.111.32:5060,udp/192.168.111.32:5060|v0.8.2-1-ga65722f

2019-06-19 09:51:21.082972 Client::write_handler - wrote 155 bytes: system:0
2019-06-19 09:51:21.086138 Client::read_handler read: 30554e48-3dbb-4bae-a8ff-ebafa5883662|route|register

2019-06-19 09:51:21.086197 Added client for register requests
2019-06-19 09:51:21.086242 Sending response: 85#737dd0a3-fbc6-41b8-8450-ccbbe37f5c1a|response|30554e48-3dbb-4bae-a8ff-ebafa5883662|OK

2019-06-19 09:51:21.086281 Client::write_handler - wrote 88 bytes: system:0
2019-06-19 09:51:21.086821 Client::read_handler read: 028a6252-0c77-4a00-9b5d-d938fc44ad0d|route|message

2019-06-19 09:51:21.086876 Added client for message requests
2019-06-19 09:51:21.086922 Sending response: 85#551e1453-336a-413c-99d5-625e114bc4bb|response|028a6252-0c77-4a00-9b5d-d938fc44ad0d|OK

2019-06-19 09:51:21.086957 Client::read_handler processing follow-on message in read buffer, remaining bytes to process: 53
2019-06-19 09:51:21.086981 Client::read_handler follow-on message length of 50 bytes 
2019-06-19 09:51:21.086997 Client::read_handler read: a97cd112-e2ea-45c1-86b1-f4387c550f0d|route|options

2019-06-19 09:51:21.087015 Added client for options requests
2019-06-19 09:51:21.087040 Sending response: 85#aea0f20a-e784-450a-b1b2-7ad2a433106f|response|a97cd112-e2ea-45c1-86b1-f4387c550f0d|OK

2019-06-19 09:51:21.087067 Client::write_handler - wrote 88 bytes: system:0
2019-06-19 09:51:21.087105 Client::write_handler - wrote 88 bytes: system:0
2019-06-19 09:51:29.789441 recv 514 bytes from udp/[192.168.111.160]:5060 at 09:51:29.789283:
REGISTER sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.111.160:5060;rport;branch=z9hG4bK25066853
Route: <sip:[email protected]:5060;lr>
From: <sip:[email protected]:5060>;tag=2135940580
To: <sip:[email protected]:5060>
Call-ID: [email protected]
CSeq: 1 REGISTER
Contact: <sip:[email protected]:5060>
Max-Forwards: 70
User-Agent: SIP UAS V2.1.4.500306
Expires: 3600
Content-Length: 0
 
2019-06-19 09:51:29.789534 processMessageStatelessly - incoming message with call-id [email protected] does not match an existing call leg, processed in thread 140338025555776
2019-06-19 09:51:29.789570 ClientController::selectClientForRequestOutsideDialog - there are 1 possible clients, we are starting with offset 0
2019-06-19 09:51:29.789590 ClientController::route_request_outside_dialog - Selected client at offset 0
2019-06-19 09:51:29.789622 PendingRequestController::add - tport: 0x107bed0, Call-ID: [email protected], transactionId f1687b4b-1001-455a-b128-ec8c7b43e37d
2019-06-19 09:51:29.789642 pending-request: Adding entry to go off in 64000ms
2019-06-19 09:51:29.789659 pending-request: Adding entry to the head (queue was empty), length: 1
2019-06-19 09:51:29.789690 ClientController::addNetTransaction: transactionId f1687b4b-1001-455a-b128-ec8c7b43e37d; size: 1
2019-06-19 09:51:29.789864 Client::write_handler - wrote 656 bytes: system:0
2019-06-19 09:51:29.796101 Client::read_handler read: 271c3f33-fd85-4206-8cd9-af00bf1ddf7f|sip|f1687b4b-1001-455a-b128-ec8c7b43e37d|
SIP/2.0 401 Unauthorized
Call-ID: [email protected]
cseq: 1 REGISTER
from: <sip:[email protected]:5060>;tag=2135940580
to: <sip:[email protected]:5060>
Content-Length: 0



2019-06-19 09:51:29.796186 Client::processMessage - got request with 4 tokens
2019-06-19 09:51:29.796205 Client::processMessage - request id 271c3f33-fd85-4206-8cd9-af00bf1ddf7f, request type: sip transaction id: f1687b4b-1001-455a-b128-ec8c7b43e37d, dialog id: 
2019-06-19 09:51:29.796224 ClientController::addApiRequest: clientMsgId 271c3f33-fd85-4206-8cd9-af00bf1ddf7f; size: 1
2019-06-19 09:51:29.796368 SipDialogController::doRespondToSipRequest thread 140338025555776
2019-06-19 09:51:29.796425 SipDialogController::findAndRemoveTransactionIdForIncomingRequest - searching transactionId f1687b4b-1001-455a-b128-ec8c7b43e37d
2019-06-19 09:51:29.796461 SipDialogController::findAndRemoveTransactionIdForIncomingRequest - failed to find transactionId f1687b4b-1001-455a-b128-ec8c7b43e37d, most likely this is a response to an invite we sent
2019-06-19 09:51:29.796508 pending-request: removing entry, prior to removal length: 1
2019-06-19 09:51:29.796527 pending-request: removed entry, timer not set (queue is empty after removal), length: 0
2019-06-19 09:51:29.796568 SipDialogController::addIncomingRequestTransaction - adding transactionId f1687b4b-1001-455a-b128-ec8c7b43e37d for irq:0x108c5d0
2019-06-19 09:51:29.796593 SipDialogController::findAndRemoveTransactionIdForIncomingRequest - searching transactionId f1687b4b-1001-455a-b128-ec8c7b43e37d
2019-06-19 09:51:29.796611 SipDialogController::doRespondToSipRequest found incoming transaction 0x108c5d0
2019-06-19 09:51:29.796630 SipTransport::getContactUri - created Contact header: sip:192.168.111.32:5060
2019-06-19 09:51:29.796749 makeTags - Adding well-known header 'Call-ID' with value '[email protected]'
2019-06-19 09:51:29.796774 makeTags - Adding well-known header 'cseq' with value '1 REGISTER'
2019-06-19 09:51:29.796792 makeTags - Adding well-known header 'from' with value '<sip:[email protected]:5060>;tag=2135940580'
2019-06-19 09:51:29.796811 makeTags - Adding well-known header 'to' with value '<sip:[email protected]:5060>'
2019-06-19 09:51:29.796943 send 316 bytes to udp/[192.168.111.160]:5060 at 09:51:29.796872:
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.111.160:5060;rport=5060;branch=z9hG4bK25066853
From: <sip:[email protected]:5060>;tag=2135940580
To: <sip:[email protected]:5060>;tag=3186pXm87DXaj
Call-ID: [email protected]
CSeq: 1 REGISTER
Content-Length: 0
 
2019-06-19 09:51:29.796988 SipDialogController::doRespondToSipRequest destroying irq 0x108c5d0
2019-06-19 09:51:29.797018 ClientController::removeApiRequest: clientMsgId 271c3f33-fd85-4206-8cd9-af00bf1ddf7f; size: 0
2019-06-19 09:51:29.797044 ClientController::removeNetTransaction: transactionId f1687b4b-1001-455a-b128-ec8c7b43e37d; size: 0
2019-06-19 09:51:29.797165 Client::write_handler - wrote 511 bytes: system:0
2019-06-19 09:51:29.804234 recv 515 bytes from udp/[192.168.111.160]:5060 at 09:51:29.804170:
REGISTER sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.111.160:5060;rport;branch=z9hG4bK648194127
Route: <sip:[email protected]:5060;lr>
From: <sip:[email protected]:5060>;tag=2135940580
To: <sip:[email protected]:5060>
Call-ID: [email protected]
CSeq: 2 REGISTER
Contact: <sip:[email protected]:5060>
Max-Forwards: 70
User-Agent: SIP UAS V2.1.4.500306
Expires: 3600
Content-Length: 0
 
2019-06-19 09:51:29.804302 processMessageStatelessly - incoming message with call-id [email protected] does not match an existing call leg, processed in thread 140338025555776
2019-06-19 09:51:29.804333 ClientController::selectClientForRequestOutsideDialog - there are 1 possible clients, we are starting with offset 0
2019-06-19 09:51:29.804356 ClientController::route_request_outside_dialog - Selected client at offset 0
2019-06-19 09:51:29.804379 PendingRequestController::add - tport: 0x107bed0, Call-ID: [email protected], transactionId c00c8f82-13b5-4306-b40c-0d2e75b4239a
2019-06-19 09:51:29.804398 pending-request: Adding entry to go off in 64000ms
2019-06-19 09:51:29.804414 pending-request: Adding entry to the head (queue was empty), length: 1
2019-06-19 09:51:29.804440 ClientController::addNetTransaction: transactionId c00c8f82-13b5-4306-b40c-0d2e75b4239a; size: 1
2019-06-19 09:51:29.804597 Client::write_handler - wrote 657 bytes: system:0
2019-06-19 09:51:29.806243 Client::read_handler read: 02459873-b3ac-48f1-987c-a90facf73560|sip|c00c8f82-13b5-4306-b40c-0d2e75b4239a|
SIP/2.0 200 OK
Call-ID: [email protected]
cseq: 2 REGISTER
from: <sip:[email protected]:5060>;tag=2135940580
to: <sip:[email protected]:5060>
Content-Length: 0



2019-06-19 09:51:29.806303 Client::processMessage - got request with 4 tokens
2019-06-19 09:51:29.806336 Client::processMessage - request id 02459873-b3ac-48f1-987c-a90facf73560, request type: sip transaction id: c00c8f82-13b5-4306-b40c-0d2e75b4239a, dialog id: 
2019-06-19 09:51:29.806366 ClientController::addApiRequest: clientMsgId 02459873-b3ac-48f1-987c-a90facf73560; size: 1
2019-06-19 09:51:29.806415 SipDialogController::doRespondToSipRequest thread 140338025555776
2019-06-19 09:51:29.806459 SipDialogController::findAndRemoveTransactionIdForIncomingRequest - searching transactionId c00c8f82-13b5-4306-b40c-0d2e75b4239a
2019-06-19 09:51:29.806491 SipDialogController::findAndRemoveTransactionIdForIncomingRequest - failed to find transactionId c00c8f82-13b5-4306-b40c-0d2e75b4239a, most likely this is a response to an invite we sent
2019-06-19 09:51:29.806522 pending-request: removing entry, prior to removal length: 1
2019-06-19 09:51:29.806555 pending-request: removed entry, timer not set (queue is empty after removal), length: 0
2019-06-19 09:51:29.806580 SipDialogController::addIncomingRequestTransaction - adding transactionId c00c8f82-13b5-4306-b40c-0d2e75b4239a for irq:0x108b3d0
2019-06-19 09:51:29.806602 SipDialogController::findAndRemoveTransactionIdForIncomingRequest - searching transactionId c00c8f82-13b5-4306-b40c-0d2e75b4239a
2019-06-19 09:51:29.806626 SipDialogController::doRespondToSipRequest found incoming transaction 0x108b3d0
2019-06-19 09:51:29.806645 SipTransport::getContactUri - created Contact header: sip:192.168.111.32:5060
2019-06-19 09:51:29.806745 makeTags - Adding well-known header 'Call-ID' with value '[email protected]'
2019-06-19 09:51:29.806769 makeTags - Adding well-known header 'cseq' with value '2 REGISTER'
2019-06-19 09:51:29.806788 makeTags - Adding well-known header 'from' with value '<sip:[email protected]:5060>;tag=2135940580'
2019-06-19 09:51:29.806806 makeTags - Adding well-known header 'to' with value '<sip:[email protected]:5060>'
2019-06-19 09:51:29.806898 send 307 bytes to udp/[192.168.111.160]:5060 at 09:51:29.806850:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.111.160:5060;rport=5060;branch=z9hG4bK648194127
From: <sip:[email protected]:5060>;tag=2135940580
To: <sip:[email protected]:5060>;tag=4a2Zrr5B5pKXD
Call-ID: [email protected]
CSeq: 2 REGISTER
Content-Length: 0
 
2019-06-19 09:51:29.806926 SipDialogController::doRespondToSipRequest destroying irq 0x108b3d0
2019-06-19 09:51:29.806957 ClientController::removeApiRequest: clientMsgId 02459873-b3ac-48f1-987c-a90facf73560; size: 0
2019-06-19 09:51:29.806981 ClientController::removeNetTransaction: transactionId c00c8f82-13b5-4306-b40c-0d2e75b4239a; size: 0
2019-06-19 09:51:29.807074 Client::write_handler - wrote 502 bytes: system:0
2019-06-19 09:51:29.807879 Client::read_handler read: eb984af1-685b-4111-83ca-f6b6ce7924cd|sip||
MESSAGE sip:192.168.111.160:5060 SIP/2.0
Call-ID: 2886269270
From: sip:[email protected]:5060
To: sip:[email protected]:5060
Content-Type: application/MANSCDP+xml
Max-Forwards: 70
User-Agent: eXosip/4.0.0
Date: 2019-01-10T18:29:26.185
Content-Length: 158

<?xml version="1.0"?>
        <Query>
        <CmdType>Catalog</CmdType>
        <SN>1</SN>
        <DeviceID>34020000001320000001</DeviceID>
        </Query>

2019-06-19 09:51:29.807935 Client::processMessage - got request with 4 tokens
2019-06-19 09:51:29.807967 Client::processMessage - request id eb984af1-685b-4111-83ca-f6b6ce7924cd, request type: sip transaction id: , dialog id: 
2019-06-19 09:51:29.808000 Client::processMessage - sending a request outside of a dialog
2019-06-19 09:51:29.808023 ClientController::addAppTransaction: transactionId fd71f4a2-538f-4d5f-b757-47bb41d37d6f; size: 1
2019-06-19 09:51:29.808040 ClientController::addApiRequest: clientMsgId eb984af1-685b-4111-83ca-f6b6ce7924cd; size: 1
2019-06-19 09:51:29.808825 SipTransport::findAppropriateTransport: searching for a transport to reach udp/sip:192.168.111.160:5060
2019-06-19 09:51:29.808857 SipTransport::findAppropriateTransport - after filtering for transport we have 2 candidates
2019-06-19 09:51:29.808876 SipTransport::findAppropriateTransport - after filtering for protocol we have 1 candidates
2019-06-19 09:51:29.808894 SipTransport::findAppropriateTransport: - returning the best match 0x107bed0: udp/192.168.111.32:5060
2019-06-19 09:51:29.808911 SipTransport::getContactUri - created Contact header: sip:192.168.111.32:5060
2019-06-19 09:51:29.808926 SipDialogController::doSendRequestOutsideDialog selected transport 0x107bed0udp/192.168.111.32:5060
2019-06-19 09:51:29.809025 makeTags - Adding well-known header 'Call-ID' with value '2886269270'
2019-06-19 09:51:29.809049 makeTags - Adding well-known header 'From' with value 'sip:[email protected]:5060'
2019-06-19 09:51:29.809068 makeTags - Adding well-known header 'To' with value 'sip:[email protected]:5060'
2019-06-19 09:51:29.809088 makeTags - Adding well-known header 'Content-Type' with value 'application/MANSCDP+xml'
2019-06-19 09:51:29.809107 makeTags - Adding well-known header 'Max-Forwards' with value '70'
2019-06-19 09:51:29.809129 makeTags - Adding well-known header 'User-Agent' with value 'eXosip/4.0.0'
2019-06-19 09:51:29.809147 makeTags - Adding well-known header 'Date' with value '2019-01-10T18:29:26.185'
2019-06-19 09:51:29.809173 SipDialogController::doSendRequestOutsideDialog - from: sip:[email protected]:5060
2019-06-19 09:51:29.809189 SipDialogController::doSendRequestOutsideDialog - to: sip:[email protected]:5060
2019-06-19 09:51:29.809204 SipDialogController::doSendRequestOutsideDialog - contact: <sip:192.168.111.32:5060>
2019-06-19 09:51:29.809218 SipDialogController::doSendRequestOutsideDialog - using client-specified call-id: 2886269270
2019-06-19 09:51:29.809237 isLocalSipUri: checking to see if this is one of mine: sip:192.168.111.160:5060
2019-06-19 09:51:29.809373 send 542 bytes to udp/[192.168.111.160]:5060 at 09:51:29.809322:
MESSAGE sip:192.168.111.160:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.111.32;rport;branch=z9hG4bK3937XcBSK19QH
Max-Forwards: 70
From: <sip:[email protected]:5060>;tag=5KUrtKpF2Z9FS
To: <sip:[email protected]:5060>
Call-ID: 2886269270
CSeq: 5900752 MESSAGE
User-Agent: eXosip/4.0.0
Content-Type: application/MANSCDP+xml
Content-Length: 158

<?xml version="1.0"?>
<Query>
<CmdType>Catalog</CmdType>
<SN>1</SN>
<DeviceID>34020000001320000001</DeviceID>
</Query 
2019-06-19 09:51:29.809407 SipDialogController::addRIP adding orq 0x10920f0
2019-06-19 09:51:29.809437 ClientController::removeApiRequest: clientMsgId eb984af1-685b-4111-83ca-f6b6ce7924cd; size: 0
2019-06-19 09:51:29.809547 Client::write_handler - wrote 737 bytes: system:0
2019-06-19 09:51:29.829875 recv 607 bytes from udp/[192.168.111.160]:5060 at 09:51:29.829781:
MESSAGE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.111.160:5060;rport;branch=z9hG4bK158996978
From: <sip:[email protected]:5060>;tag=1606072809
To: <sip:[email protected]:5060>
Call-ID: [email protected]
CSeq: 20 MESSAGE
Max-Forwards: 70
User-Agent: SIP UAS V2.1.4.500306
Content-Type: Application/MANSCDP+xml
Content-Length:   182

<?xml version="1.0" encoding="GB2312" ?>
<Notify>
<CmdType>Keepalive</CmdType>
<SN>15637</SN>
<DeviceID>34020000001320000001</DeviceID>
<Status>OK</Status>
</Notify> 
2019-06-19 09:51:29.829931 processMessageStatelessly - incoming message with call-id [email protected] does not match an existing call leg, processed in thread 140338025555776
2019-06-19 09:51:29.829960 ClientController::selectClientForRequestOutsideDialog - there are 1 possible clients, we are starting with offset 0
2019-06-19 09:51:29.829979 ClientController::route_request_outside_dialog - Selected client at offset 0
2019-06-19 09:51:29.830001 PendingRequestController::add - tport: 0x107bed0, Call-ID: [email protected], transactionId 28808b86-20e5-4879-85b3-2bf29ab5ac6c
2019-06-19 09:51:29.830018 pending-request: Adding entry to go off in 64000ms
2019-06-19 09:51:29.830034 pending-request: Adding entry to the head (queue was empty), length: 1
2019-06-19 09:51:29.830059 ClientController::addNetTransaction: transactionId 28808b86-20e5-4879-85b3-2bf29ab5ac6c; size: 1
2019-06-19 09:51:29.830248 Client::write_handler - wrote 749 bytes: system:0
2019-06-19 09:51:29.832106 Client::read_handler read: a412cb75-d2d4-4657-af11-1d4df63b410f|sip|28808b86-20e5-4879-85b3-2bf29ab5ac6c|
SIP/2.0 200 OK
Call-ID: [email protected]
cseq: 20 MESSAGE
from: <sip:[email protected]:5060>;tag=1606072809
to: <sip:[email protected]:5060>
Content-Length: 0



2019-06-19 09:51:29.832164 Client::processMessage - got request with 4 tokens
2019-06-19 09:51:29.832198 Client::processMessage - request id a412cb75-d2d4-4657-af11-1d4df63b410f, request type: sip transaction id: 28808b86-20e5-4879-85b3-2bf29ab5ac6c, dialog id: 
2019-06-19 09:51:29.832229 ClientController::addApiRequest: clientMsgId a412cb75-d2d4-4657-af11-1d4df63b410f; size: 1
2019-06-19 09:51:29.832366 SipDialogController::doRespondToSipRequest thread 140338025555776
2019-06-19 09:51:29.832423 SipDialogController::findAndRemoveTransactionIdForIncomingRequest - searching transactionId 28808b86-20e5-4879-85b3-2bf29ab5ac6c
2019-06-19 09:51:29.832470 SipDialogController::findAndRemoveTransactionIdForIncomingRequest - failed to find transactionId 28808b86-20e5-4879-85b3-2bf29ab5ac6c, most likely this is a response to an invite we sent
2019-06-19 09:51:29.832506 pending-request: removing entry, prior to removal length: 1
2019-06-19 09:51:29.832533 pending-request: removed entry, timer not set (queue is empty after removal), length: 0
2019-06-19 09:51:29.832562 SipDialogController::addIncomingRequestTransaction - adding transactionId 28808b86-20e5-4879-85b3-2bf29ab5ac6c for irq:0x108f870
2019-06-19 09:51:29.832584 SipDialogController::findAndRemoveTransactionIdForIncomingRequest - searching transactionId 28808b86-20e5-4879-85b3-2bf29ab5ac6c
2019-06-19 09:51:29.832601 SipDialogController::doRespondToSipRequest found incoming transaction 0x108f870
2019-06-19 09:51:29.832618 SipTransport::getContactUri - created Contact header: sip:192.168.111.32:5060
2019-06-19 09:51:29.832718 makeTags - Adding well-known header 'Call-ID' with value '[email protected]'
2019-06-19 09:51:29.832742 makeTags - Adding well-known header 'cseq' with value '20 MESSAGE'
2019-06-19 09:51:29.832761 makeTags - Adding well-known header 'from' with value '<sip:[email protected]:5060>;tag=1606072809'
2019-06-19 09:51:29.832780 makeTags - Adding well-known header 'to' with value '<sip:[email protected]:5060>'
2019-06-19 09:51:29.832871 send 306 bytes to udp/[192.168.111.160]:5060 at 09:51:29.832827:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.111.160:5060;rport=5060;branch=z9hG4bK158996978
From: <sip:[email protected]:5060>;tag=1606072809
To: <sip:[email protected]:5060>;tag=6vmHve7jZ8Z2m
Call-ID: [email protected]
CSeq: 20 MESSAGE
Content-Length: 0
 
2019-06-19 09:51:29.832903 SipDialogController::doRespondToSipRequest destroying irq 0x108f870
2019-06-19 09:51:29.832930 ClientController::removeApiRequest: clientMsgId a412cb75-d2d4-4657-af11-1d4df63b410f; size: 0
2019-06-19 09:51:29.832955 ClientController::removeNetTransaction: transactionId 28808b86-20e5-4879-85b3-2bf29ab5ac6c; size: 0
2019-06-19 09:51:29.833069 Client::write_handler - wrote 501 bytes: system:0
2019-06-19 09:51:29.849275 recv 328 bytes from udp/[192.168.111.160]:5060 at 09:51:29.849181:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.111.32;rport=5060;branch=z9hG4bK3937XcBSK19QH
From: <sip:[email protected]:5060>;tag=5KUrtKpF2Z9FS
To: <sip:[email protected]:5060>;tag=1613541069
Call-ID: 2886269270
CSeq: 5900752 MESSAGE
User-Agent: SIP UAS V2.1.4.500306
Content-Length: 0
 
2019-06-19 09:51:29.849334 SipDialogController::processResponseOutsideDialog
2019-06-19 09:51:29.849360 SipDialogController::findRIPByOrq orq 0x10920f0
2019-06-19 09:51:29.849379 SipDialogController::clearRIP clearing orq 0x10920f0
2019-06-19 09:51:29.849409 ClientController::removeAppTransaction: transactionId fd71f4a2-538f-4d5f-b757-47bb41d37d6f; size: 0
2019-06-19 09:51:29.849517 Client::write_handler - wrote 466 bytes: system:0
2019-06-19 09:51:29.850759 recv 1324 bytes from udp/[192.168.111.160]:5060 at 09:51:29.850628:
MESSAGE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.111.160:5060;rport;branch=z9hG4bK2005368187
From: <sip:[email protected]:5060>;tag=466432968
To: <sip:[email protected]:5060>
Call-ID: [email protected]
CSeq: 20 MESSAGE
Max-Forwards: 70
User-Agent: SIP UAS V2.1.4.500306
Content-Type: Application/MANSCDP+xml
Content-Length:   900

<?xml version="1.0" encoding="GB2312" ?>
<Response>
<CmdType>Catalog</CmdType>
<SN>1</SN>
<DeviceID>34020000001320000001</DeviceID>
<SumNum>1</SumNum>
<DeviceList Num="1">
<Item>
<DeviceID>34020000001310000001</DeviceID>
<Name>�ֿ����</Name>
<Manufacturer>Dahua</Manufacturer>
<Model>IPC-HFW3236M-I1</Model>
<Owner>0</Owner>
<CivilCode>340200</CivilCode>
<Address>axy</Address>
<Parental>0</Parental>
<ParentID>34020000001320000001</ParentID>
<RegisterWay>1</RegisterWay>
<Secrecy>0</Secrecy>
<StreamNum>2</StreamNum>
<Status>ON</Status>
<Info>
<PTZType>3</PTZType>
<DownloadSpeed>1/2/4/8</DownloadSpeed>
</Info>
</Item>
</DeviceList>
</Response> 
2019-06-19 09:51:29.850827 processMessageStatelessly - incoming message with call-id [email protected] does not match an existing call leg, processed in thread 140338025555776
2019-06-19 09:51:29.850859 ClientController::selectClientForRequestOutsideDialog - there are 1 possible clients, we are starting with offset 0
2019-06-19 09:51:29.850878 ClientController::route_request_outside_dialog - Selected client at offset 0
2019-06-19 09:51:29.850900 PendingRequestController::add - tport: 0x107bed0, Call-ID: [email protected], transactionId b2a6e42b-a13b-40b7-8df3-ec1737ac4b47
2019-06-19 09:51:29.850919 pending-request: Adding entry to go off in 64000ms
2019-06-19 09:51:29.850935 pending-request: Adding entry to the head (queue was empty), length: 1
2019-06-19 09:51:29.850963 ClientController::addNetTransaction: transactionId b2a6e42b-a13b-40b7-8df3-ec1737ac4b47; size: 1
2019-06-19 09:51:29.851159 Client::write_handler - wrote 1465 bytes: system:0
2019-06-19 09:51:29.857454 Client::read_handler - bouncing client due to error reading: asio.misc:2
2019-06-19 09:51:29.857507 ClientController::leave - Removed client, count of connected clients is now: 0
2019-06-19 09:51:29.857580 BaseClient::~BaseClient