Друзья, кто может помочь интерпретировать этот лог?
<--- SIP read from UDP:213.170.92.166:5068 --->
INVITE sip:00066234@89.208.33.6 SIP/2.0
Record-Route: <sip:74956680761@213.170.92.166:5068;r2=on;lr=on;ftag=1A971764-2665>
Record-Route: <sip:74956680761@213.170.92.166;r2=on;lr=on;ftag=1A971764-2665>
Via: SIP/2.0/UDP 213.170.92.166:5068;branch=z9hG4bK2ec.346bbf36.0
Via: SIP/2.0/UDP 213.170.81.26:5060;x-route-tag="tgrp:TFOP";branch=z9hG4bK2B669C429
From: <sip:9166550184@213.170.81.26>;tag=1A971764-2665
To: <sip:74956680761@213.170.92.166>
P-Preferred-Identity: <sip:79166550184@213.170.81.26>
Call-ID: F85BBE0B-2BF11E0-9E1FEDDE-DE0C03C4@213.170.81.26
Supported: 100rel,timer,resource-priority,replaces
Min-SE: 1800
CSeq: 101 INVITE
Contact: <sip:9166550184@213.170.81.26:5060>
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 419
v=0
o=CiscoSystemsSIP-GW-UserAgent 8096 7171 IN IP4 213.170.81.26
s=SIP Call
c=IN IP4 213.170.81.26
t=0 0
m=audio 19848 RTP/AVP 8 0 18 4 98 3 101
c=IN IP4 213.170.81.26
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=yes
a=rtpmap:4 G723/8000
a=fmtp:4 bitrate=6.3;annexa=yes
a=rtpmap:98 G726-32/8000
a=rtpmap:3 GSM/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
<------------->
--- (16 headers 17 lines) ---
== Using SIP RTP TOS bits 184
== Using SIP RTP CoS mark 5
Sending to 213.170.92.166 : 5068 (no NAT)
Using INVITE request as basis request - F85BBE0B-2BF11E0-9E1FEDDE-DE0C03C4@213.170.81.26
Found peer 'TELPHIN' for '9166550184' from 213.170.92.166:5068
Found RTP audio format 8
Found RTP audio format 0
Found RTP audio format 18
Found RTP audio format 4
Found RTP audio format 98
Found RTP audio format 3
Found RTP audio format 101
Found audio description format PCMA for ID 8
Found audio description format PCMU for ID 0
Found audio description format G729 for ID 18
Found audio description format G723 for ID 4
Found audio description format G726-32 for ID 98
Found audio description format GSM for ID 3
Found audio description format telephone-event for ID 101
Capabilities: us - 0xe (gsm|ulaw|alaw), peer - audio=0x90f (g723|gsm|ulaw|alaw|g726|g729)/video=0x0 (nothing)/text=0x0 (nothing), combined - 0xe (gsm|ulaw|alaw)
Non-codec capabilities (dtmf): us - 0x1 (telephone-event), peer - 0x1 (telephone-event), combined - 0x1 (telephone-event)
Peer audio RTP is at port 213.170.81.26:19848
Looking for 00066234 in inbound_telphin (domain 89.208.33.6)
<--- Reliably Transmitting (no NAT) to 213.170.92.166:5068 --->
SIP/2.0 404 Not Found
Via: SIP/2.0/UDP 213.170.92.166:5068;branch=z9hG4bK2ec.346bbf36.0;received=213.170.92.166
Via: SIP/2.0/UDP 213.170.81.26:5060;x-route-tag="tgrp:TFOP";branch=z9hG4bK2B669C429
From: <sip:9166550184@213.170.81.26>;tag=1A971764-2665
To: <sip:74956680761@213.170.92.166>;tag=as10198989
Call-ID: F85BBE0B-2BF11E0-9E1FEDDE-DE0C03C4@213.170.81.26
CSeq: 101 INVITE
Server: Asterisk PBX 1.6.2.10
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO
Supported: replaces, timer
Content-Length: 0
<------------>
Scheduling destruction of SIP dialog 'F85BBE0B-2BF11E0-9E1FEDDE-DE0C03C4@213.170.81.26' in 32000 ms (Method: INVITE)
<--- SIP read from UDP:213.170.92.166:5068 --->
ACK sip:00066234@89.208.33.6 SIP/2.0
Via: SIP/2.0/UDP 213.170.92.166:5068;branch=z9hG4bK2ec.346bbf36.0
From: <sip:9166550184@213.170.81.26>;tag=1A971764-2665
To: <sip:74956680761@213.170.92.166>;tag=as10198989
Call-ID: F85BBE0B-2BF11E0-9E1FEDDE-DE0C03C4@213.170.81.26
CSeq: 101 ACK
Content-Length: 0
<------------->
--- (7 headers 0 lines) ---
Really destroying SIP dialog 'F85BBE0B-2BF11E0-9E1FEDDE-DE0C03C4@213.170.81.26' Method: ACK
|