Re: Re: Workaround for sip agents

От: Vladimir Mendelevich <CGatePro_at_mx_ru>
Дата: Mon 21 Nov 2005 - 17:07:29 MSK

Hello, Dmitry!
You wrote to "CommuniGate Pro Russian Discussions" <CGatePro@mx.ru> on Mon, 21 Nov 2005 15:54:24 +0300:

 DA> При уровне лога SIP установленном в All Info в пакетах, посылаемых этим  DA> клиентом, должен быть виден заголовок User-Agent:. Вот его содержимое и надо
 DA> использовать.

Стоит All Info. В олгах нет слова agent.


17:04:40.90 5 SIP [172.20.128.44:5060] inp(602): INVITE sip:112@hedgehog.lan.rarus.ru SIP/2.0\r\nVia: SIP/2.0/UDP 172.20.128.44:5060\r\nMax-Forwards: 70\r\nFrom: dlink-port1
<sip:111@hedgehog.lan.rarus.ru>;tag=c0ac518841d6d962\r\nTo:
sip:112@hedgehog.lan.rarus.ru\r\nCall-ID: 6fb9e2716beb66d6@172.20. 17:04:40.92 2 SIPDATA-01951 inp: req udp [172.20.128.44:5060] INVITE(602 bytes) sip:112@hedgehog.lan.rarus.ru
17:04:40.92 5 SIPDATA-01951 inp: INVITE sip:112@hedgehog.lan.rarus.ru SIP/2.0 
17:04:40.92 5 SIPDATA-01951 inp: Via: SIP/2.0/UDP 172.20.128.44:5060
17:04:40.92 5 SIPDATA-01951 inp: Max-Forwards: 70
17:04:40.92 5 SIPDATA-01951 inp: From: dlink-port1

<sip:111@hedgehog.lan.rarus.ru>;tag=c0ac518841d6d962 
17:04:40.92 5 SIPDATA-01951 inp: To: sip:112@hedgehog.lan.rarus.ru
17:04:40.92 5 SIPDATA-01951 inp: Call-ID: 6fb9e2716beb66d6@172.20.128.44
17:04:40.92 5 SIPDATA-01951 inp: CSeq: 1 INVITE
17:04:40.92 5 SIPDATA-01951 inp: Contact: dlink-port1

<sip:111@172.20.128.44:5060> 
17:04:40.92 5 SIPDATA-01951 inp: Supported: timer
17:04:40.92 5 SIPDATA-01951 inp: Session-Expires: 180
17:04:40.92 5 SIPDATA-01951 inp: Content-Type: application/sdp
17:04:40.92 5 SIPDATA-01951 inp: Content-Length: 192
17:04:40.92 5 SIPDATA-01951 inp:
17:04:40.92 5 SIPDATA-01951 inp: v=0
17:04:40.92 5 SIPDATA-01951 inp: o=- 1 0 IN IP4 172.20.128.44
17:04:40.92 5 SIPDATA-01951 inp: s=-
17:04:40.92 5 SIPDATA-01951 inp: c=IN IP4 172.20.128.44
17:04:40.92 5 SIPDATA-01951 inp: t=0 0
17:04:40.92 5 SIPDATA-01951 inp: m=audio 30000 RTP/AVP 0 4 8 18
17:04:40.92 5 SIPDATA-01951 inp: a=rtpmap:0 PCMU/8000
17:04:40.92 5 SIPDATA-01951 inp: a=rtpmap:4 G723/8000
17:04:40.92 5 SIPDATA-01951 inp: a=rtpmap:8 PCMA/8000
17:04:40.92 5 SIPDATA-01951 inp: a=rtpmap:18 G729/8000
17:04:40.92 5 SIPDATA-01951 Hash=87103
17:04:40.92 5 SIPS 1754: enqueued
17:04:40.92 2 SIPS-01754 enqueued
17:04:40.92 5 SIPS-01754 INITIAL posted
17:04:40.92 2 SIPDATA-01951 created SIPS-01754
17:04:40.92 5 SIPS(3) 1754: processing INITIAL
17:04:40.92 2 SIPS-01754 [01951] INVITE sip:112@hedgehog.lan.rarus.ru from
udp [172.20.128.44:5060]
17:04:40.92 2 SIPDATA-01952 out: rsp udp [172.20.128.44:5060] 100-INVITE(295 bytes)
17:04:40.92 5 SIPDATA-01952 out: SIP/2.0 100 Trying 17:04:40.92 5 SIPDATA-01952 out: Via: SIP/2.0/UDP 172.20.128.44:5060;received=172.20.128.44 17:04:40.92 5 SIPDATA-01952 out: From: dlink-port1
<sip:111@hedgehog.lan.rarus.ru>;tag=c0ac518841d6d962 
17:04:40.92 5 SIPDATA-01952 out: To: sip:112@hedgehog.lan.rarus.ru
17:04:40.92 5 SIPDATA-01952 out: Call-ID: 6fb9e2716beb66d6@172.20.128.44
17:04:40.92 5 SIPDATA-01952 out: CSeq: 1 INVITE
17:04:40.92 5 SIPDATA-01952 out: Server: CommuniGatePro/5.0.2
17:04:40.92 5 SIPDATA-01952 out: Content-Length: 0
17:04:40.92 5 SIPDATA-01952 out:
17:04:40.92 5 SIP [172.20.128.44:5060] out(295): SIP/2.0 100 Trying\r\nVia:
SIP/2.0/UDP 172.20.128.44:5060;received=172.20.128.44\r\nFrom: dlink-port1
<sip:111@hedgehog.lan.rarus.ru>;tag=c0ac518841d6d962\r\nTo:
sip:112@hedgehog.lan.rarus.ru\r\nCall-ID: 6fb9e2716beb66d6@172.20.128.44\r\nCSeq: 1 INVIT 17:04:40.92 2 SIPS-01754 [01952] 100-INVITE(trying) sent to udp [172.20.128.44:5060] 
17:04:40.92 2 SIGNAL-00858 enqueued
17:04:40.92 2 SIPS-01754 created SIGNAL-00858
17:04:40.92 5 SIPS(3) 1754: idling
17:04:40.92 2 SIGNAL-00858 SIPS-01754: INVITE sip:112@hedgehog.lan.rarus.ru
17:04:40.92 2 SIGNAL-00858 INVITE sip:112@hedgehog.lan.rarus.ru via
sip:112@hedgehog.lan.rarus.ru
17:04:40.92 2 SIGNAL-00858 dlink-port2@hedgehog.lan.rarus.ru has 1 registrations 
17:04:40.92 5 SIPC 88: enqueued
17:04:40.92 2 SIPC-00088 enqueued
17:04:40.92 5 SIPC-00088 INITIAL posted
17:04:40.92 5 SIPC(3) 88: processing INITIAL
17:04:40.92 2 SIPC-00088 INVITE sip:112@172.20.128.44:5061 via
sip:112@172.20.128.44:5061 
17:04:40.92 4 SIPC-00088 resolving sip:112@172.20.128.44:5061
17:04:40.92 4 SIPC-00088 resolved: 1 address(es)
17:04:40.92 4 SIPC-00088 trying: sip:172.20.128.44:5061
17:04:40.92 5 SIPC-00088 timeout set for 2 secs
17:04:40.92 2 SIPDATA-01953 out: req udp [172.20.128.44:5061] INVITE(664
bytes) sip:112@172.20.128.44:5061
17:04:40.92 5 SIPDATA-01953 out: INVITE sip:112@172.20.128.44:5061 SIP/2.0 17:04:40.92 5 SIPDATA-01953 out: Via: SIP/2.0/UDP 172.20.128.45:5060;branch=z9hG4bK88
17:04:40.92 5 SIPDATA-01953 out: Via: SIP/2.0/UDP 172.20.128.44:5060;received=172.20.128.44 17:04:40.92 5 SIPDATA-01953 out: Max-Forwards: 69 17:04:40.92 5 SIPDATA-01953 out: From: dlink-port1
<sip:111@hedgehog.lan.rarus.ru>;tag=c0ac518841d6d962 
17:04:40.92 5 SIPDATA-01953 out: To: sip:112@hedgehog.lan.rarus.ru
17:04:40.92 5 SIPDATA-01953 out: Call-ID: 6fb9e2716beb66d6@172.20.128.44
17:04:40.92 5 SIPDATA-01953 out: Contact: <sip:111@172.20.128.44:5060>
17:04:40.92 5 SIPDATA-01953 out: CSeq: 1 INVITE
17:04:40.92 5 SIPDATA-01953 out: Supported: timer
17:04:40.92 5 SIPDATA-01953 out: Session-Expires: 180
17:04:40.92 5 SIPDATA-01953 out: Content-Type: application/sdp
17:04:40.92 5 SIPDATA-01953 out: Content-Length: 192
17:04:40.92 5 SIPDATA-01953 out:
17:04:40.92 5 SIPDATA-01953 out: v=0
17:04:40.92 5 SIPDATA-01953 out: o=- 1 0 IN IP4 172.20.128.44
17:04:40.92 5 SIPDATA-01953 out: s=-
17:04:40.92 5 SIPDATA-01953 out: c=IN IP4 172.20.128.44
17:04:40.92 5 SIPDATA-01953 out: t=0 0
17:04:40.92 5 SIPDATA-01953 out: m=audio 30000 RTP/AVP 0 4 8 18
17:04:40.92 5 SIPDATA-01953 out: a=rtpmap:0 PCMU/8000
17:04:40.92 5 SIPDATA-01953 out: a=rtpmap:4 G723/8000
17:04:40.92 5 SIPDATA-01953 out: a=rtpmap:8 PCMA/8000
17:04:40.92 5 SIPDATA-01953 out: a=rtpmap:18 G729/8000
17:04:40.92 5 SIP [172.20.128.44:5061] out(664): INVITE
sip:112@172.20.128.44:5061 SIP/2.0\r\nVia: SIP/2.0/UDP 172.20.128.45:5060;branch=z9hG4bK88\r\nVia: SIP/2.0/UDP 172.20.128.44:5060;received=172.20.128.44\r\nMax-Forwards: 69\r\nFrom: dlink-port1 <sip:111@hedgehog.lan.rarus.ru>;tag=c0ac518841d6d9 
17:04:40.92 4 SIPC-00088 [01953] INVITE sip:112@172.20.128.44:5061 sent to
udp [172.20.128.44:5061]
17:04:40.92 5 SIPC(3) 88: enqueued (2 secs)
17:04:40.92 2 SIGNAL-00858 INVITE relayed to SIPC-00088:
sip:112@172.20.128.44:5061
17:04:40.95 5 SIP [172.20.128.44:5061] inp(319): SIP/2.0 100 Trying\r\nVia: SIP/2.0/UDP 172.20.128.45:5060;branch=z9hG4bK88\r\nVia: SIP/2.0/UDP 172.20.128.44:5060;received=172.20.128.44\r\nFrom: dlink-port1
<sip:111@hedgehog.lan.rarus.ru>;tag=c0ac518841d6d962\r\nTo:
sip:112@hedgehog.lan.rarus.ru\r\n
17:04:40.95 2 SIPDATA-01954 inp: rsp udp [172.20.128.44:5061] 100-INVITE(319 bytes)
17:04:40.95 5 SIPDATA-01954 inp: SIP/2.0 100 Trying 17:04:40.95 5 SIPDATA-01954 inp: Via: SIP/2.0/UDP 172.20.128.45:5060;branch=z9hG4bK88
17:04:40.95 5 SIPDATA-01954 inp: Via: SIP/2.0/UDP 172.20.128.44:5060;received=172.20.128.44 17:04:40.95 5 SIPDATA-01954 inp: From: dlink-port1
<sip:111@hedgehog.lan.rarus.ru>;tag=c0ac518841d6d962 
17:04:40.95 5 SIPDATA-01954 inp: To: sip:112@hedgehog.lan.rarus.ru
17:04:40.95 5 SIPDATA-01954 inp: Call-ID: 6fb9e2716beb66d6@172.20.128.44
17:04:40.95 5 SIPDATA-01954 inp: CSeq: 1 INVITE
17:04:40.95 5 SIPDATA-01954 inp: Content-Length: 0
17:04:40.95 5 SIPDATA-01954 inp:
17:04:40.95 5 SIPC-00088 RESPONSE posted
17:04:40.95 2 SIPDATA-01954 sent to SIPC-00088
17:04:40.95 5 SIPC(1) 88: processing RESPONSE
17:04:40.95 2 SIPC-00088 [01954] 100-INVITE received
17:04:40.95 5 SIPC-00088 timeout set for 180 secs
17:04:40.95 5 SIPC(1) 88: enqueued (180 secs)
17:04:40.98 5 SIP [172.20.128.44:5061] inp(357): SIP/2.0 180 Ringing\r\nVia:
SIP/2.0/UDP 172.20.128.45:5060;branch=z9hG4bK88\r\nVia: SIP/2.0/UDP 172.20.128.44:5060;received=172.20.128.44\r\nFrom: dlink-port1
<sip:111@hedgehog.lan.rarus.ru>;tag=c0ac518841d6d962\r\nTo:
sip:112@hedgehog.lan.rarus.ru;ta
17:04:40.98 2 SIPDATA-01955 inp: rsp udp [172.20.128.44:5061] 180-INVITE(357 bytes)
17:04:40.98 5 SIPDATA-01955 inp: SIP/2.0 180 Ringing 17:04:40.98 5 SIPDATA-01955 inp: Via: SIP/2.0/UDP 172.20.128.45:5060;branch=z9hG4bK88
17:04:40.98 5 SIPDATA-01955 inp: Via: SIP/2.0/UDP 172.20.128.44:5060;received=172.20.128.44 17:04:40.98 5 SIPDATA-01955 inp: From: dlink-port1
<sip:111@hedgehog.lan.rarus.ru>;tag=c0ac518841d6d962
17:04:40.98 5 SIPDATA-01955 inp: To:
sip:112@hedgehog.lan.rarus.ru;tag=769015f4d1ac81ce 
17:04:40.98 5 SIPDATA-01955 inp: Call-ID: 6fb9e2716beb66d6@172.20.128.44
17:04:40.98 5 SIPDATA-01955 inp: CSeq: 1 INVITE
17:04:40.98 5 SIPDATA-01955 inp: P-N-UAType: ip
17:04:40.98 5 SIPDATA-01955 inp: Content-Length: 0
17:04:40.98 5 SIPDATA-01955 inp:
17:04:40.98 5 SIPC-00088 RESPONSE posted
17:04:40.98 2 SIPDATA-01955 sent to SIPC-00088
17:04:40.98 5 SIPC(2) 88: processing RESPONSE
17:04:40.98 2 SIPC-00088 [01955] 180-INVITE received
17:04:40.98 5 SIPC(2) 88: enqueued (180 secs)
17:04:40.98 2 SIGNAL-00858 180 (provisioning) from SIPC-00088
17:04:40.98 5 SIPS-01754 PROVISION posted
17:04:40.98 5 SIPS(1) 1754: processing PROVISION
17:04:40.98 2 SIPDATA-01956 out: rsp udp [172.20.128.44:5060] 180-INVITE(303
bytes)
17:04:40.98 5 SIPDATA-01956 out: SIP/2.0 180 Ringing 17:04:40.98 5 SIPDATA-01956 out: Via: SIP/2.0/UDP 172.20.128.44:5060;received=172.20.128.44 17:04:40.98 5 SIPDATA-01956 out: From: dlink-port1
<sip:111@hedgehog.lan.rarus.ru>;tag=c0ac518841d6d962
17:04:40.98 5 SIPDATA-01956 out: To:
sip:112@hedgehog.lan.rarus.ru;tag=769015f4d1ac81ce 
17:04:40.98 5 SIPDATA-01956 out: Call-ID: 6fb9e2716beb66d6@172.20.128.44
17:04:40.98 5 SIPDATA-01956 out: CSeq: 1 INVITE
17:04:40.98 5 SIPDATA-01956 out: P-N-UAType: ip
17:04:40.98 5 SIPDATA-01956 out: Content-Length: 0
17:04:40.98 5 SIPDATA-01956 out:
17:04:40.98 5 SIP [172.20.128.44:5060] out(303): SIP/2.0 180 Ringing\r\nVia:
SIP/2.0/UDP 172.20.128.44:5060;received=172.20.128.44\r\nFrom: dlink-port1
<sip:111@hedgehog.lan.rarus.ru>;tag=c0ac518841d6d962\r\nTo:
sip:112@hedgehog.lan.rarus.ru;tag=769015f4d1ac81ce\r\nCall-ID: 6fb9e2716beb66d6@172.20.1
17:04:40.98 2 SIPS-01754 [01956] 180-INVITE(provisioning) sent to udp [172.20.128.44:5060]
17:04:40.98 5 SIPS(1) 1754: idling
17:04:56.87 5 SIP [172.20.128.44:5060] inp(286): CANCEL sip:112@hedgehog.lan.rarus.ru SIP/2.0\r\nVia: SIP/2.0/UDP 172.20.128.44:5060\r\nMax-Forwards: 70\r\nFrom: dlink-port1
<sip:111@hedgehog.lan.rarus.ru>;tag=c0ac518841d6d962\r\nTo:
sip:112@hedgehog.lan.rarus.ru\r\nCall-ID: 6fb9e2716beb66d6@172.20. 17:04:56.87 2 SIPDATA-01957 inp: req udp [172.20.128.44:5060] CANCEL(286 bytes) sip:112@hedgehog.lan.rarus.ru
17:04:56.87 5 SIPDATA-01957 inp: CANCEL sip:112@hedgehog.lan.rarus.ru SIP/2.0 
17:04:56.87 5 SIPDATA-01957 inp: Via: SIP/2.0/UDP 172.20.128.44:5060
17:04:56.87 5 SIPDATA-01957 inp: Max-Forwards: 70
17:04:56.87 5 SIPDATA-01957 inp: From: dlink-port1

<sip:111@hedgehog.lan.rarus.ru>;tag=c0ac518841d6d962 
17:04:56.87 5 SIPDATA-01957 inp: To: sip:112@hedgehog.lan.rarus.ru
17:04:56.87 5 SIPDATA-01957 inp: Call-ID: 6fb9e2716beb66d6@172.20.128.44
17:04:56.87 5 SIPDATA-01957 inp: CSeq: 1 CANCEL
17:04:56.87 5 SIPDATA-01957 inp: Content-Length: 0
17:04:56.87 5 SIPDATA-01957 inp:
17:04:56.87 5 SIPDATA-01957 Hash=87103
17:04:56.87 5 SIPS-01754 SUPPL posted
17:04:56.87 2 SIPDATA-01957 sent to SIPS-01754
17:04:56.87 5 SIPS(2) 1754: processing SUPPL
17:04:56.87 2 SIPS-01754 [01957] cancel request
17:04:56.87 2 SIGNAL-00858 cancelled
17:04:56.87 2 SIGNAL-00858 cancelling SIPC-00088
17:04:56.87 5 SIPC-00088 CANCEL posted
17:04:56.87 2 SIGNAL-00858 dequeued
17:04:56.87 5 SIPC(1) 88: processing CANCEL
17:04:56.87 5 SIPC 89: enqueued
17:04:56.87 2 SIPC-00089 enqueued
17:04:56.87 5 SIPC-00089 STARTCANCEL posted
17:04:56.87 2 SIPC-00088 cancelling SIPC-00089 created
17:04:56.87 5 SIPC(1) 88: enqueued (164 secs)
17:04:56.87 5 SIPC(1) 89: processing STARTCANCEL
17:04:56.87 2 SIPC-00089 CANCEL INVITE via sip:112@172.20.128.44:5061
17:04:56.87 5 SIPC-00089 timeout set for 2 secs
17:04:56.87 2 SIPDATA-01958 out: req udp [172.20.128.44:5061] CANCEL(345
bytes) sip:112@172.20.128.44:5061 
17:04:56.87 5 SIPDATA-01958 out: CANCEL sip:112@172.20.128.44:5061 SIP/2.0
17:04:56.87 5 SIPDATA-01958 out: Reason: SIP;cause=487;text="CANCEL request"
17:04:56.87 5 SIPDATA-01958 out: Via: SIP/2.0/UDP
172.20.128.45:5060;branch=z9hG4bK88
17:04:56.87 5 SIPDATA-01958 out: Max-Forwards: 69 17:04:56.87 5 SIPDATA-01958 out: From: dlink-port1
<sip:111@hedgehog.lan.rarus.ru>;tag=c0ac518841d6d962 
17:04:56.87 5 SIPDATA-01958 out: To: sip:112@hedgehog.lan.rarus.ru
17:04:56.87 5 SIPDATA-01958 out: Call-ID: 6fb9e2716beb66d6@172.20.128.44
17:04:56.87 5 SIPDATA-01958 out: CSeq: 1 CANCEL
17:04:56.87 5 SIPDATA-01958 out: Content-Length: 0
17:04:56.87 5 SIPDATA-01958 out:
17:04:56.87 5 SIP [172.20.128.44:5061] out(345): CANCEL
sip:112@172.20.128.44:5061 SIP/2.0\r\nReason: SIP;cause=487;text="CANCEL request"\r\nVia: SIP/2.0/UDP
172.20.128.45:5060;branch=z9hG4bK88\r\nMax-Forwards: 69\r\nFrom: dlink-port1
<sip:111@hedgehog.lan.rarus.ru>;tag=c0ac518841d6d962\r\nTo: sip:1 
17:04:56.87 4 SIPC-00089 [01958] CANCEL sip:112@172.20.128.44:5061 sent to
udp [172.20.128.44:5061]
17:04:56.87 5 SIPC(1) 89: enqueued (2 secs)
17:04:56.87 2 SIPS-01754 cancelled
17:04:56.87 2 SIPS-01754 detaching signal
17:04:56.87 5 SIPS 1756: enqueued
17:04:56.87 2 SIPS-01756 enqueued
17:04:56.87 5 SIPS-01756 FINAL posted
17:04:56.87 5 SIPS(3) 1756: processing FINAL
17:04:56.87 2 SIPDATA-01959 out: rsp udp [172.20.128.44:5060] 200-CANCEL(312
bytes)
17:04:56.87 5 SIPDATA-01959 out: SIP/2.0 200 OK 17:04:56.87 5 SIPDATA-01959 out: Via: SIP/2.0/UDP 172.20.128.44:5060;received=172.20.128.44 17:04:56.87 5 SIPDATA-01959 out: From: dlink-port1
<sip:111@hedgehog.lan.rarus.ru>;tag=c0ac518841d6d962
17:04:56.87 5 SIPDATA-01959 out: To:
sip:112@hedgehog.lan.rarus.ru;tag=E20A3035A2291962 
17:04:56.87 5 SIPDATA-01959 out: Call-ID: 6fb9e2716beb66d6@172.20.128.44
17:04:56.87 5 SIPDATA-01959 out: CSeq: 1 CANCEL
17:04:56.87 5 SIPDATA-01959 out: Server: CommuniGatePro/5.0.2
17:04:56.87 5 SIPDATA-01959 out: Content-Length: 0
17:04:56.87 5 SIPDATA-01959 out:
17:04:56.87 5 SIP [172.20.128.44:5060] out(312): SIP/2.0 200 OK\r\nVia:
SIP/2.0/UDP 172.20.128.44:5060;received=172.20.128.44\r\nFrom: dlink-port1
<sip:111@hedgehog.lan.rarus.ru>;tag=c0ac518841d6d962\r\nTo:
sip:112@hedgehog.lan.rarus.ru;tag=E20A3035A2291962\r\nCall-ID: 6fb9e2716beb66d6@172.20.128.44
17:04:56.87 2 SIPS-01756 [01959] 200-CANCEL(final) sent to udp [172.20.128.44:5060] 
17:04:56.87 4 SIPS-01756 completed
17:04:56.87 5 SIPS-01756 timeout set for 32 secs
17:04:56.87 5 SIPS(3) 1756: enqueued (32 secs)
17:04:56.87 2 SIPS-01754 CANCEL transaction SIPS-01756 created
17:04:56.87 2 SIPDATA-01960 out: rsp udp [172.20.128.44:5060] 487-INVITE(331
bytes)
17:04:56.87 5 SIPDATA-01960 out: SIP/2.0 487 SIP request cancelled 17:04:56.87 5 SIPDATA-01960 out: Via: SIP/2.0/UDP 172.20.128.44:5060;received=172.20.128.44 17:04:56.87 5 SIPDATA-01960 out: From: dlink-port1
<sip:111@hedgehog.lan.rarus.ru>;tag=c0ac518841d6d962
17:04:56.87 5 SIPDATA-01960 out: To:
sip:112@hedgehog.lan.rarus.ru;tag=7A2F50C2F725EA16 
17:04:56.87 5 SIPDATA-01960 out: Call-ID: 6fb9e2716beb66d6@172.20.128.44
17:04:56.87 5 SIPDATA-01960 out: CSeq: 1 INVITE
17:04:56.87 5 SIPDATA-01960 out: Server: CommuniGatePro/5.0.2
17:04:56.87 5 SIPDATA-01960 out: Content-Length: 0
17:04:56.87 5 SIPDATA-01960 out:
17:04:56.87 5 SIP [172.20.128.44:5060] out(331): SIP/2.0 487 SIP request
cancelled\r\nVia: SIP/2.0/UDP
172.20.128.44:5060;received=172.20.128.44\r\nFrom: dlink-port1
<sip:111@hedgehog.lan.rarus.ru>;tag=c0ac518841d6d962\r\nTo:
sip:112@hedgehog.lan.rarus.ru;tag=7A2F50C2F725EA16\r\nCall-ID: 6fb9e2716be 17:04:56.87 2 SIPS-01754 [01960] 487-INVITE(final) sent to udp [172.20.128.44:5060] 
17:04:56.87 4 SIPS-01754 completed
17:04:56.87 5 SIPS-01754 timeout set for 2 secs
17:04:56.87 5 SIPS(2) 1754: enqueued (2 secs)
17:04:56.92 5 SIP [172.20.128.44:5061] inp(276): SIP/2.0 200 OK\r\nVia:
SIP/2.0/UDP 172.20.128.45:5060;branch=z9hG4bK88\r\nFrom: dlink-port1
<sip:111@hedgehog.lan.rarus.ru>;tag=c0ac518841d6d962\r\nTo:
sip:112@hedgehog.lan.rarus.ru;tag=769015f4d1ac81ce\r\nCall-ID: 6fb9e2716beb66d6@172.20.128.44\r\nCS
17:04:56.92 2 SIPDATA-01961 inp: rsp udp [172.20.128.44:5061] 200-CANCEL(276 bytes)
17:04:56.92 5 SIPDATA-01961 inp: SIP/2.0 200 OK 17:04:56.92 5 SIPDATA-01961 inp: Via: SIP/2.0/UDP 172.20.128.45:5060;branch=z9hG4bK88
17:04:56.92 5 SIPDATA-01961 inp: From: dlink-port1
<sip:111@hedgehog.lan.rarus.ru>;tag=c0ac518841d6d962
17:04:56.92 5 SIPDATA-01961 inp: To:
sip:112@hedgehog.lan.rarus.ru;tag=769015f4d1ac81ce 
17:04:56.92 5 SIPDATA-01961 inp: Call-ID: 6fb9e2716beb66d6@172.20.128.44
17:04:56.92 5 SIPDATA-01961 inp: CSeq: 1 CANCEL
17:04:56.92 5 SIPDATA-01961 inp: Content-Length: 0
17:04:56.92 5 SIPDATA-01961 inp:
17:04:56.92 5 SIPC-00089 RESPONSE posted
17:04:56.92 2 SIPDATA-01961 sent to SIPC-00088
17:04:56.92 5 SIPC(3) 89: processing RESPONSE
17:04:56.92 2 SIPC-00089 [01961] 200-CANCEL received
17:04:56.92 4 SIPC-00089 completed
17:04:56.92 5 SIPC-00089 timeout set for 5 secs
17:04:56.92 5 SIPC(3) 89: enqueued (5 secs)
17:04:56.95 5 SIP [172.20.128.44:5061] inp(351): SIP/2.0 487 Request
Cancelled\r\nVia: SIP/2.0/UDP 172.20.128.45:5060;branch=z9hG4bK88\r\nVia: SIP/2.0/UDP 172.20.128.44:5060;received=172.20.128.44\r\nFrom: dlink-port1
<sip:111@hedgehog.lan.rarus.ru>;tag=c0ac518841d6d962\r\nTo:
sip:112@hedgehog.lan.r
17:04:56.95 2 SIPDATA-01962 inp: rsp udp [172.20.128.44:5061] 487-INVITE(351 bytes)
17:04:56.95 5 SIPDATA-01962 inp: SIP/2.0 487 Request Cancelled 17:04:56.95 5 SIPDATA-01962 inp: Via: SIP/2.0/UDP 172.20.128.45:5060;branch=z9hG4bK88
17:04:56.95 5 SIPDATA-01962 inp: Via: SIP/2.0/UDP 172.20.128.44:5060;received=172.20.128.44 17:04:56.95 5 SIPDATA-01962 inp: From: dlink-port1
<sip:111@hedgehog.lan.rarus.ru>;tag=c0ac518841d6d962
17:04:56.95 5 SIPDATA-01962 inp: To:
sip:112@hedgehog.lan.rarus.ru;tag=769015f4d1ac81ce 
17:04:56.95 5 SIPDATA-01962 inp: Call-ID: 6fb9e2716beb66d6@172.20.128.44
17:04:56.95 5 SIPDATA-01962 inp: CSeq: 1 INVITE
17:04:56.95 5 SIPDATA-01962 inp: Content-Length: 0
17:04:56.95 5 SIPDATA-01962 inp:
17:04:56.95 5 SIPC-00088 RESPONSE posted
17:04:56.95 2 SIPDATA-01962 sent to SIPC-00088
17:04:56.95 5 SIPC(1) 88: processing RESPONSE
17:04:56.95 2 SIPC-00088 [01962] 487-INVITE received
17:04:56.95 4 SIPC-00088 completed, sending ACK
17:04:56.95 4 SIPC-00088 sending ACK
17:04:56.95 2 SIPDATA-01963 out: req udp [172.20.128.44:5061] ACK(315 bytes)
sip:112@172.20.128.44:5061
17:04:56.95 5 SIPDATA-01963 out: ACK sip:112@172.20.128.44:5061 SIP/2.0 17:04:56.95 5 SIPDATA-01963 out: Via: SIP/2.0/UDP 172.20.128.45:5060;branch=z9hG4bK88
17:04:56.95 5 SIPDATA-01963 out: Max-Forwards: 70 17:04:56.95 5 SIPDATA-01963 out: From: dlink-port1
<sip:111@hedgehog.lan.rarus.ru>;tag=c0ac518841d6d962
17:04:56.95 5 SIPDATA-01963 out: To:
sip:112@hedgehog.lan.rarus.ru;tag=769015f4d1ac81ce 
17:04:56.95 5 SIPDATA-01963 out: Call-ID: 6fb9e2716beb66d6@172.20.128.44
17:04:56.95 5 SIPDATA-01963 out: CSeq: 1 ACK
17:04:56.95 5 SIPDATA-01963 out: Content-Length: 0
17:04:56.95 5 SIPDATA-01963 out:
17:04:56.95 5 SIP [172.20.128.44:5061] out(315): ACK
sip:112@172.20.128.44:5061 SIP/2.0\r\nVia: SIP/2.0/UDP 172.20.128.45:5060;branch=z9hG4bK88\r\nMax-Forwards: 70\r\nFrom: dlink-port1
<sip:111@hedgehog.lan.rarus.ru>;tag=c0ac518841d6d962\r\nTo:
sip:112@hedgehog.lan.rarus.ru;tag=769015f4d1ac81ce\r\nC 17:04:56.95 4 SIPC-00088 [01963] ACK sip:112@172.20.128.44:5061 sent to udp [172.20.128.44:5061] 
17:04:56.95 5 SIPC-00088 timeout set for 32 secs
17:04:56.95 5 SIPC(1) 88: enqueued (32 secs)
17:04:57.37 5 SIP [172.20.128.44:5060] inp(286): CANCEL
sip:112@hedgehog.lan.rarus.ru SIP/2.0\r\nVia: SIP/2.0/UDP 172.20.128.44:5060\r\nMax-Forwards: 70\r\nFrom: dlink-port1
<sip:111@hedgehog.lan.rarus.ru>;tag=c0ac518841d6d962\r\nTo:
sip:112@hedgehog.lan.rarus.ru\r\nCall-ID: 6fb9e2716beb66d6@172.20. 17:04:57.37 2 SIPDATA-01964 inp: req udp [172.20.128.44:5060] CANCEL(286 bytes) sip:112@hedgehog.lan.rarus.ru
17:04:57.37 5 SIPDATA-01964 inp: CANCEL sip:112@hedgehog.lan.rarus.ru SIP/2.0 
17:04:57.37 5 SIPDATA-01964 inp: Via: SIP/2.0/UDP 172.20.128.44:5060
17:04:57.37 5 SIPDATA-01964 inp: Max-Forwards: 70
17:04:57.37 5 SIPDATA-01964 inp: From: dlink-port1

<sip:111@hedgehog.lan.rarus.ru>;tag=c0ac518841d6d962 
17:04:57.37 5 SIPDATA-01964 inp: To: sip:112@hedgehog.lan.rarus.ru
17:04:57.37 5 SIPDATA-01964 inp: Call-ID: 6fb9e2716beb66d6@172.20.128.44
17:04:57.37 5 SIPDATA-01964 inp: CSeq: 1 CANCEL
17:04:57.37 5 SIPDATA-01964 inp: Content-Length: 0
17:04:57.37 5 SIPDATA-01964 inp:
17:04:57.37 5 SIPDATA-01964 Hash=87103
17:04:57.37 5 SIPS-01754 SUPPL posted
17:04:57.37 2 SIPDATA-01964 sent to SIPS-01754
17:04:57.37 5 SIPS(1) 1754: processing SUPPL
17:04:57.37 2 SIPS-01754 [01964] cancel request
17:04:57.37 5 SIPS 1758: enqueued
17:04:57.37 2 SIPS-01758 enqueued
17:04:57.37 5 SIPS-01758 FINAL posted
17:04:57.37 2 SIPS-01754 CANCEL transaction SIPS-01758 created
17:04:57.37 5 SIPS(1) 1754: enqueued (1 secs)
17:04:57.37 5 SIPS(1) 1758: processing FINAL
17:04:57.37 2 SIPDATA-01965 out: rsp udp [172.20.128.44:5060] 200-CANCEL(312
bytes)
17:04:57.37 5 SIPDATA-01965 out: SIP/2.0 200 OK 17:04:57.37 5 SIPDATA-01965 out: Via: SIP/2.0/UDP 172.20.128.44:5060;received=172.20.128.44 17:04:57.37 5 SIPDATA-01965 out: From: dlink-port1
<sip:111@hedgehog.lan.rarus.ru>;tag=c0ac518841d6d962
17:04:57.37 5 SIPDATA-01965 out: To:
sip:112@hedgehog.lan.rarus.ru;tag=4D7072C5D996D29F 
17:04:57.37 5 SIPDATA-01965 out: Call-ID: 6fb9e2716beb66d6@172.20.128.44
17:04:57.37 5 SIPDATA-01965 out: CSeq: 1 CANCEL
17:04:57.37 5 SIPDATA-01965 out: Server: CommuniGatePro/5.0.2
17:04:57.37 5 SIPDATA-01965 out: Content-Length: 0
17:04:57.37 5 SIPDATA-01965 out:
17:04:57.37 5 SIP [172.20.128.44:5060] out(312): SIP/2.0 200 OK\r\nVia:
SIP/2.0/UDP 172.20.128.44:5060;received=172.20.128.44\r\nFrom: dlink-port1
<sip:111@hedgehog.lan.rarus.ru>;tag=c0ac518841d6d962\r\nTo:
sip:112@hedgehog.lan.rarus.ru;tag=4D7072C5D996D29F\r\nCall-ID: 6fb9e2716beb66d6@172.20.128.44
17:04:57.37 2 SIPS-01758 [01965] 200-CANCEL(final) sent to udp [172.20.128.44:5060] 
17:04:57.37 4 SIPS-01758 completed
17:04:57.37 5 SIPS-01758 timeout set for 32 secs
17:04:57.37 5 SIPS(1) 1758: enqueued (32 secs)
---------------------------

То-есть оно свосем мусорное? Не умеет даже сказать Agent? При звонке на WM с этого девайса слово Agent появляется. Но это видимо WM. Оно тогда равно RTC/ 1.3.

С уважением,

Сетевой отдел компании "1С-Рарус"
UIN:9244669
Phone:+7(095)250-6393 Получено Mon Nov 21 14:08:41 2005

Этот архив был сгенерирован hypermail 2.1.8 : Fri 24 Apr 2015 - 16:14:34 MSK