Closed GoogleCodeExporter closed 9 years ago
Sorry I pasted wrong part of log.. This is more proper part:
==================
16:31:19.871 2 SIPDATA-727268 relayed for [192.168.40.76]: [212.53.40.40]:5060
-> udp[95.26.159.95]:5060 as [-40027]
16:31:25.175 2 SIPDATA-721883 inp: req [0.0.0.0]:0 <- tcp[95.26.159.95]:50555
INVITE(1373 bytes) sip:+38062XXXXXXX@sipnet.ru
INVITE sip:+38062XXXXXXX@sipnet.ru SIP/2.0
Via: SIP/2.0/TCP 192.169.1.11:50555;rport;branch=z9hG4bKPjhGIvgc6c8G7ZysuZfgKR0LdtqMajlamf
Max-Forwards: 70
From: <sip:XXXX.XXXX@sipnet.ru>;tag=paKFu9the.jxFAe3ww-8G2SEZevQBoWf
To: <sip:+38062XXXXXXX@sipnet.ru>
Contact: <sip:XXXX.XXXX@192.169.1.11:48156;transport=TCP;ob>
Call-ID: n.xgw.nTno0p-WyOFTxop2uu1ynzm4q1
CSeq: 4358 INVITE
Route: <sip:sipnet.ru;transport=tcp;lr>
Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS
Supported: replaces, 100rel, timer, norefersub
Session-Expires: 1800
Min-SE: 90
User-Agent: CSipSimple_pyramid-15/r1916
Content-Type: application/sdp
Content-Length: 665
v=0
o=- 3557737776 3557737776 IN IP4 95.26.159.95
s=pjmedia
c=IN IP4 95.26.159.95
t=0 0
m=audio 4000 RTP/AVP 8 18 3 102 0 9 111 106 99 101
c=IN IP4 95.26.159.95
a=rtcp:4001 IN IP4 95.26.159.95
a=sendrecv
a=rtpmap:8 PCMA/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:3 GSM/8000
a=rtpmap:102 ILBC/8000
a=fmtp:102 mode=30
a=rtpmap:0 PCMU/8000
a=rtpmap:9 G722/8000
a=rtpmap:111 opus/48000
a=fmtp:111 maxcodedaudiobandwidth=16000
a=rtpmap:106 speex/16000
a=rtpmap:99 SILK/24000
a=fmtp:99 useinbandfec=0
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=zrtp-hash:1.10 c60dfcf4d26cb3e92b07fb21934b148363b81dfa2faa3aeb55e3ad1721973e83
16:31:25.175 4 SIPDATA-721883 NATed [192.169.1.11]:50555 via
[95.26.159.95]:50555
16:31:25.175 4 SIPDATA-721883 Hash=48417659
16:31:25.175 4 SIPDATA-721883 self-route removed:
<sip:sipnet.ru;transport=tcp;lr>
16:31:25.175 2 SIPDATA-721883 created SIPS-659408
16:31:25.176 2 SIPDATA-731522 out: rsp -> tcp[95.26.159.95]:50555
100-INVITE(364 bytes)
SIP/2.0 100 Trying
Via: SIP/2.0/TCP 192.169.1.11:50555;rport=50555;branch=z9hG4bKPjhGIvgc6c8G7ZysuZfgKR0LdtqMajlamf;received=95.26.159.95
From: <sip:XXXX.XXXX@sipnet.ru>;tag=paKFu9the.jxFAe3ww-8G2SEZevQBoWf
To: <sip:+38062XXXXXXX@sipnet.ru>
Call-ID: n.xgw.nTno0p-WyOFTxop2uu1ynzm4q1
CSeq: 4358 INVITE
Server: CommuniGatePro/5.4.6
Content-Length: 0
16:31:25.176 2 SIPDATA-731523 out: rsp -> tcp[95.26.159.95]:50555
401-INVITE(509 bytes)
SIP/2.0 401 Authentication required
Via: SIP/2.0/TCP 192.169.1.11:50555;rport=50555;branch=z9hG4bKPjhGIvgc6c8G7ZysuZfgKR0LdtqMajlamf;received=95.26.159.95
From: <sip:XXXX.XXXX@sipnet.ru>;tag=paKFu9the.jxFAe3ww-8G2SEZevQBoWf
To: <sip:+38062XXXXXXX@sipnet.ru>;tag=A7520AD7
Call-ID: n.xgw.nTno0p-WyOFTxop2uu1ynzm4q1
CSeq: 4358 INVITE
WWW-Authenticate: Digest realm="etc.tario.ru",nonce="688DFD6594E628068718",opaque="opaq",qop="auth",algorithm=MD5
Server: CommuniGatePro/5.4.6
Content-Length: 0
16:31:25.297 2 SIPDATA-731521 inp: req [0.0.0.0]:0 <- tcp[95.26.159.95]:50555
ACK(397 bytes) sip:+38062XXXXXXX@sipnet.ru
ACK sip:+38062XXXXXXX@sipnet.ru SIP/2.0
Via: SIP/2.0/TCP 192.169.1.11:50555;rport;branch=z9hG4bKPjhGIvgc6c8G7ZysuZfgKR0LdtqMajlamf
Max-Forwards: 70
From: <sip:XXXX.XXXX@sipnet.ru>;tag=paKFu9the.jxFAe3ww-8G2SEZevQBoWf
To: <sip:+38062XXXXXXX@sipnet.ru>;tag=A7520AD7
Call-ID: n.xgw.nTno0p-WyOFTxop2uu1ynzm4q1
CSeq: 4358 ACK
Route: <sip:sipnet.ru;transport=tcp;lr>
Content-Length: 0
16:31:25.297 4 SIPDATA-731521 NATed [192.169.1.11]:50555 via
[95.26.159.95]:50555
16:31:25.297 4 SIPDATA-731521 Hash=48417659
16:31:25.297 4 SIPDATA-731521 self-route removed:
<sip:sipnet.ru;transport=tcp;lr>
16:31:25.297 2 SIPDATA-731521 sent to SIPS-659408
16:32:55.883 2 SIPDATA-804572 inp: req [212.53.40.40]:5060 <-
udp[95.26.159.95]:5060 REGISTER(632 bytes) sip:sipnet.ru
REGISTER sip:sipnet.ru SIP/2.0
Via: SIP/2.0/UDP 192.169.1.3:5060;branch=z9hG4bK0a72dbcf;rport
Max-Forwards: 70
From: <sip:XXXX.XXXX@sipnet.ru>;tag=as441a0ba6
To: <sip:XXXX.XXXX@sipnet.ru>
Call-ID: 49c6e62e506a49152ffe53d9332fb2d8@192.169.1.3
CSeq: 19077 REGISTER
User-Agent: Asterisk PBX 1.6.2.9-2+squeeze4
Authorization: Digest username="XXXX.XXXX", realm="etc.tario.ru", algorithm=MD5, uri="sip:sipnet.ru", nonce="78D1F6AFBF6B05DD3EA1", response="6c8572bb3d2dc7ff3433d32d2a7282da", opaque="opaq", qop=auth, cnonce="74ec1e83", nc=0000000b
Expires: 120
Contact: <sip:s@192.169.1.3>
Content-Length: 0
16:32:55.883 4 SIPDATA-804572 NATed [192.169.1.3]:5060 via [95.26.159.95]:5060
16:32:55.883 4 SIPDATA-804572 Hash=1851114500
16:32:55.883 2 SIPDATA-804572 created SIPS-679236
16:32:55.886 2 SIPDATA-804573 out: rsp [212.53.40.40]:5060 ->
udp[95.26.159.95]:5060 200-REGISTER(870 bytes)
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.169.1.3:5060;branch=z9hG4bK0a72dbcf;rport=5060;received=95.26.159.95
Path: <sip:udp-95.26.159.95-5060C192.168.40.72S212.53.40.40-5060.nat.cgatepro;lr>
From: <sip:XXXX.XXXX@sipnet.ru>;tag=as441a0ba6
To: <sip:XXXX.XXXX@sipnet.ru>;tag=6B324512
Call-ID: 49c6e62e506a49152ffe53d9332fb2d8@192.169.1.3
CSeq: 19077 REGISTER
Expires: 120
Contact: <sip:s@192.169.1.3>;expires=120
Contact: <sip:XXXX.XXXX@192.169.1.11:48156;transport=TCP;ob>;+sip.instance="<urn:uuid:00000000-0000-0000-0000-0000e922f243>";pub-gruu="sip:XXXX.XXXX@sipnet.ru;gr=104A49D4";reg-id=1;expires=1694
Event: registration
Date: Thu, 27 Sep 2012 12:32:55 GMT
Allow: PUBLISH,SUBSCRIBE
Supported: path,gruu
Allow-Events: presence,message-summary,reg,dialog,line-seize,keep-alive,refer
Server: CommuniGatePro/5.4.6
Content-Length: 0
16:34:40.898 2 SIPDATA-889384 inp: req [212.53.40.40]:5060 <-
udp[95.26.159.95]:5060 REGISTER(632 bytes) sip:sipnet.ru
REGISTER sip:sipnet.ru SIP/2.0
Via: SIP/2.0/UDP 192.169.1.3:5060;branch=z9hG4bK591dbb18;rport
Max-Forwards: 70
From: <sip:XXXX.XXXX@sipnet.ru>;tag=as638f610e
To: <sip:XXXX.XXXX@sipnet.ru>
Call-ID: 49c6e62e506a49152ffe53d9332fb2d8@192.169.1.3
CSeq: 19078 REGISTER
User-Agent: Asterisk PBX 1.6.2.9-2+squeeze4
Authorization: Digest username="XXXX.XXXX", realm="etc.tario.ru", algorithm=MD5, uri="sip:sipnet.ru", nonce="78D1F6AFBF6B05DD3EA1", response="f121d5ddc717d3efd261996cf273339c", opaque="opaq", qop=auth, cnonce="1b4b0117", nc=0000000c
Expires: 120
Contact: <sip:s@192.169.1.3>
Content-Length: 0
16:34:40.898 4 SIPDATA-889384 NATed [192.169.1.3]:5060 via [95.26.159.95]:5060
16:34:40.898 4 SIPDATA-889384 Hash=1991288895
16:34:40.898 4 SIPDATA-889384 cluster target=[192.168.40.79]
16:34:40.898 2 SIPDATA-889384 passed to cluster member [192.168.40.79] as
[-77911]
16:34:40.904 2 SIPDATA-889394 adding NAT Pinger
16:34:40.904 2 SIPDATA-889394 inp: rly [212.53.40.40]:5060 ->
udp[95.26.159.95]:5060(934 bytes)
16:34:40.904 2 SIPDATA-889395 out: rly [212.53.40.40]:5060 ->
udp[95.26.159.95]:5060 (870 bytes)
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.169.1.3:5060;branch=z9hG4bK591dbb18;rport=5060;received=95.26.159.95
Path: <sip:udp-95.26.159.95-5060C192.168.40.72S212.53.40.40-5060.nat.cgatepro;lr>
From: <sip:XXXX.XXXX@sipnet.ru>;tag=as638f610e
To: <sip:XXXX.XXXX@sipnet.ru>;tag=725E3882
Call-ID: 49c6e62e506a49152ffe53d9332fb2d8@192.169.1.3
CSeq: 19078 REGISTER
Expires: 118
Contact: <sip:s@192.169.1.3>;expires=118
Contact: <sip:XXXX.XXXX@192.169.1.11:48156;transport=TCP;ob>;+sip.instance="<urn:uuid:00000000-0000-0000-0000-0000e922f243>";pub-gruu="sip:XXXX.XXXX@sipnet.ru;gr=104A49D4";reg-id=1;expires=1589
Event: registration
Date: Thu, 27 Sep 2012 12:34:40 GMT
Allow: PUBLISH,SUBSCRIBE
Supported: path,gruu
Allow-Events: presence,message-summary,reg,dialog,line-seize,keep-alive,refer
Server: CommuniGatePro/5.4.6
Content-Length: 0
16:34:40.904 2 SIPDATA-889394 relayed for [192.168.40.79]: [212.53.40.40]:5060
-> udp[95.26.159.95]:5060 as [-77901]
16:36:23.915 2 SIPDATA-973227 inp: req [212.53.40.40]:5060 <-
udp[95.26.159.95]:5060 REGISTER(632 bytes) sip:sipnet.ru
REGISTER sip:sipnet.ru SIP/2.0
Via: SIP/2.0/UDP 192.169.1.3:5060;branch=z9hG4bK52e175ad;rport
Max-Forwards: 70
From: <sip:XXXX.XXXX@sipnet.ru>;tag=as48f5cdfe
To: <sip:XXXX.XXXX@sipnet.ru>
Call-ID: 49c6e62e506a49152ffe53d9332fb2d8@192.169.1.3
CSeq: 19079 REGISTER
User-Agent: Asterisk PBX 1.6.2.9-2+squeeze4
Authorization: Digest username="XXXX.XXXX", realm="etc.tario.ru", algorithm=MD5, uri="sip:sipnet.ru", nonce="78D1F6AFBF6B05DD3EA1", response="0b20b8688ae06f1f7e6ea40734d03699", opaque="opaq", qop=auth, cnonce="197112d1", nc=0000000d
Expires: 120
Contact: <sip:s@192.169.1.3>
Content-Length: 0
16:36:23.915 4 SIPDATA-973227 NATed [192.169.1.3]:5060 via [95.26.159.95]:5060
16:36:23.915 4 SIPDATA-973227 Hash=1578987953
16:36:23.915 4 SIPDATA-973227 cluster target=[192.168.40.76]
16:36:23.915 2 SIPDATA-973227 passed to cluster member [192.168.40.76] as
[-94068]
16:36:23.915 2 SIPDATA-973229 inp: rly [212.53.40.40]:5060 ->
udp[95.26.159.95]:5060(539 bytes)
16:36:23.915 2 SIPDATA-973230 out: rly [212.53.40.40]:5060 ->
udp[95.26.159.95]:5060 (486 bytes)
SIP/2.0 401 AUTH error: stale nonce
Via: SIP/2.0/UDP 192.169.1.3:5060;branch=z9hG4bK52e175ad;rport=5060;received=95.26.159.95
From: <sip:XXXX.XXXX@sipnet.ru>;tag=as48f5cdfe
To: <sip:XXXX.XXXX@sipnet.ru>;tag=B81FBE67
Call-ID: 49c6e62e506a49152ffe53d9332fb2d8@192.169.1.3
CSeq: 19079 REGISTER
WWW-Authenticate: Digest realm="etc.tario.ru",nonce="A3DA744B005359D2BEE4",opaque="opaq",qop="auth",algorithm=MD5,stale=true
Server: CommuniGatePro/5.4.6
Content-Length: 0
16:36:23.915 2 SIPDATA-973229 relayed for [192.168.40.76]: [212.53.40.40]:5060
-> udp[95.26.159.95]:5060 as [-94066]
16:36:23.923 2 SIPDATA-973239 inp: req [212.53.40.40]:5060 <-
udp[95.26.159.95]:5060 REGISTER(632 bytes) sip:sipnet.ru
REGISTER sip:sipnet.ru SIP/2.0
Via: SIP/2.0/UDP 192.169.1.3:5060;branch=z9hG4bK48443469;rport
Max-Forwards: 70
From: <sip:XXXX.XXXX@sipnet.ru>;tag=as4b09b9e7
To: <sip:XXXX.XXXX@sipnet.ru>
Call-ID: 49c6e62e506a49152ffe53d9332fb2d8@192.169.1.3
CSeq: 19080 REGISTER
User-Agent: Asterisk PBX 1.6.2.9-2+squeeze4
Authorization: Digest username="XXXX.XXXX", realm="etc.tario.ru", algorithm=MD5, uri="sip:sipnet.ru", nonce="A3DA744B005359D2BEE4", response="5a54ff37be6df43a3f58dcf5849416da", opaque="opaq", qop=auth, cnonce="4d732175", nc=00000001
Expires: 120
Contact: <sip:s@192.169.1.3>
Content-Length: 0
16:36:23.923 4 SIPDATA-973239 NATed [192.169.1.3]:5060 via [95.26.159.95]:5060
16:36:23.923 4 SIPDATA-973239 Hash=1467310585
16:36:23.923 4 SIPDATA-973239 cluster target=[192.168.40.76]
16:36:23.923 2 SIPDATA-973239 passed to cluster member [192.168.40.76] as
[-94056]
16:36:23.927 2 SIPDATA-973245 adding NAT Pinger
16:36:23.927 2 SIPDATA-973245 inp: rly [212.53.40.40]:5060 ->
udp[95.26.159.95]:5060(934 bytes)
16:36:23.927 2 SIPDATA-973246 out: rly [212.53.40.40]:5060 ->
udp[95.26.159.95]:5060 (870 bytes)
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.169.1.3:5060;branch=z9hG4bK48443469;rport=5060;received=95.26.159.95
Path: <sip:udp-95.26.159.95-5060C192.168.40.72S212.53.40.40-5060.nat.cgatepro;lr>
From: <sip:XXXX.XXXX@sipnet.ru>;tag=as4b09b9e7
To: <sip:XXXX.XXXX@sipnet.ru>;tag=8A15D8F4
Call-ID: 49c6e62e506a49152ffe53d9332fb2d8@192.169.1.3
CSeq: 19080 REGISTER
Expires: 113
Contact: <sip:s@192.169.1.3>;expires=113
Contact: <sip:XXXX.XXXX@192.169.1.11:48156;transport=TCP;ob>;+sip.instance="<urn:uuid:00000000-0000-0000-0000-0000e922f243>";pub-gruu="sip:XXXX.XXXX@sipnet.ru;gr=104A49D4";reg-id=1;expires=1486
Event: registration
Date: Thu, 27 Sep 2012 12:36:23 GMT
Allow: PUBLISH,SUBSCRIBE
Supported: path,gruu
Allow-Events: presence,message-summary,reg,dialog,line-seize,keep-alive,refer
Server: CommuniGatePro/5.4.6
Content-Length: 0
16:36:23.927 2 SIPDATA-973245 relayed for [192.168.40.76]: [212.53.40.40]:5060
-> udp[95.26.159.95]:5060 as [-94050]
16:38:01.938 2 SIPDATA-052465 inp: req [212.53.40.40]:5060 <-
udp[95.26.159.95]:5060 REGISTER(632 bytes) sip:sipnet.ru
REGISTER sip:sipnet.ru SIP/2.0
Via: SIP/2.0/UDP 192.169.1.3:5060;branch=z9hG4bK5488ec17;rport
Max-Forwards: 70
From: <sip:XXXX.XXXX@sipnet.ru>;tag=as23f356cc
To: <sip:XXXX.XXXX@sipnet.ru>
Call-ID: 49c6e62e506a49152ffe53d9332fb2d8@192.169.1.3
CSeq: 19081 REGISTER
User-Agent: Asterisk PBX 1.6.2.9-2+squeeze4
Authorization: Digest username="XXXX.XXXX", realm="etc.tario.ru", algorithm=MD5, uri="sip:sipnet.ru", nonce="A3DA744B005359D2BEE4", response="32b89a4f08e0a569d12413b3802311b1", opaque="opaq", qop=auth, cnonce="1935bf43", nc=00000002
Expires: 120
Contact: <sip:s@192.169.1.3>
Content-Length: 0
16:38:01.938 4 SIPDATA-052465 NATed [192.169.1.3]:5060 via [95.26.159.95]:5060
16:38:01.938 4 SIPDATA-052465 Hash=1092744674
16:38:01.938 4 SIPDATA-052465 cluster target=[192.168.40.77]
16:38:01.938 2 SIPDATA-052465 passed to cluster member [192.168.40.77] as
[-14830]
16:38:01.945 2 SIPDATA-052481 adding NAT Pinger
16:38:01.945 2 SIPDATA-052481 inp: rly [212.53.40.40]:5060 ->
udp[95.26.159.95]:5060(934 bytes)
16:38:01.945 2 SIPDATA-052483 out: rly [212.53.40.40]:5060 ->
udp[95.26.159.95]:5060 (870 bytes)
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.169.1.3:5060;branch=z9hG4bK5488ec17;rport=5060;received=95.26.159.95
Path: <sip:udp-95.26.159.95-5060C192.168.40.72S212.53.40.40-5060.nat.cgatepro;lr>
From: <sip:XXXX.XXXX@sipnet.ru>;tag=as23f356cc
To: <sip:XXXX.XXXX@sipnet.ru>;tag=4BFD29BA
Call-ID: 49c6e62e506a49152ffe53d9332fb2d8@192.169.1.3
CSeq: 19081 REGISTER
Expires: 119
Contact: <sip:s@192.169.1.3>;expires=119
Contact: <sip:XXXX.XXXX@192.169.1.11:48156;transport=TCP;ob>;+sip.instance="<urn:uuid:00000000-0000-0000-0000-0000e922f243>";pub-gruu="sip:XXXX.XXXX@sipnet.ru;gr=104A49D4";reg-id=1;expires=1388
Event: registration
Date: Thu, 27 Sep 2012 12:38:01 GMT
Allow: PUBLISH,SUBSCRIBE
Supported: path,gruu
Allow-Events: presence,message-summary,reg,dialog,line-seize,keep-alive,refer
Server: CommuniGatePro/5.4.6
Content-Length: 0
16:38:01.945 2 SIPDATA-052481 relayed for [192.168.40.77]: [212.53.40.40]:5060
-> udp[95.26.159.95]:5060 as [-14813]
16:39:45.956 2 SIPDATA-137044 inp: req [212.53.40.40]:5060 <-
udp[95.26.159.95]:5060 REGISTER(632 bytes) sip:sipnet.ru
REGISTER sip:sipnet.ru SIP/2.0
Via: SIP/2.0/UDP 192.169.1.3:5060;branch=z9hG4bK1f4455d1;rport
Max-Forwards: 70
From: <sip:XXXX.XXXX@sipnet.ru>;tag=as5adfef7a
To: <sip:XXXX.XXXX@sipnet.ru>
Call-ID: 49c6e62e506a49152ffe53d9332fb2d8@192.169.1.3
CSeq: 19082 REGISTER
User-Agent: Asterisk PBX 1.6.2.9-2+squeeze4
Authorization: Digest username="XXXX.XXXX", realm="etc.tario.ru", algorithm=MD5, uri="sip:sipnet.ru", nonce="A3DA744B005359D2BEE4", response="6545068ae5f67c9859c1466208ac5ad5", opaque="opaq", qop=auth, cnonce="4a94a0a2", nc=00000003
Expires: 120
Contact: <sip:s@192.169.1.3>
Content-Length: 0
16:39:45.957 4 SIPDATA-137044 NATed [192.169.1.3]:5060 via [95.26.159.95]:5060
16:39:45.957 4 SIPDATA-137044 Hash=1317044088
16:39:45.957 2 SIPDATA-137044 created SIPS-769654
16:39:45.959 2 SIPDATA-137045 out: rsp [212.53.40.40]:5060 ->
udp[95.26.159.95]:5060 200-REGISTER(870 bytes)
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.169.1.3:5060;branch=z9hG4bK1f4455d1;rport=5060;received=95.26.159.95
Path: <sip:udp-95.26.159.95-5060C192.168.40.72S212.53.40.40-5060.nat.cgatepro;lr>
From: <sip:XXXX.XXXX@sipnet.ru>;tag=as5adfef7a
To: <sip:XXXX.XXXX@sipnet.ru>;tag=FF15E931
Call-ID: 49c6e62e506a49152ffe53d9332fb2d8@192.169.1.3
CSeq: 19082 REGISTER
Expires: 118
Contact: <sip:s@192.169.1.3>;expires=118
Contact: <sip:XXXX.XXXX@192.169.1.11:48156;transport=TCP;ob>;+sip.instance="<urn:uuid:00000000-0000-0000-0000-0000e922f243>";pub-gruu="sip:XXXX.XXXX@sipnet.ru;gr=104A49D4";reg-id=1;expires=1284
Event: registration
Date: Thu, 27 Sep 2012 12:39:45 GMT
Allow: PUBLISH,SUBSCRIBE
Supported: path,gruu
Allow-Events: presence,message-summary,reg,dialog,line-seize,keep-alive,refer
Server: CommuniGatePro/5.4.6
Content-Length: 0
16:41:28.970 2 SIPDATA-221359 inp: req [212.53.40.40]:5060 <-
udp[95.26.159.95]:5060 REGISTER(632 bytes) sip:sipnet.ru
REGISTER sip:sipnet.ru SIP/2.0
Via: SIP/2.0/UDP 192.169.1.3:5060;branch=z9hG4bK46e3e8cc;rport
Max-Forwards: 70
From: <sip:XXXX.XXXX@sipnet.ru>;tag=as073f7e66
To: <sip:XXXX.XXXX@sipnet.ru>
Call-ID: 49c6e62e506a49152ffe53d9332fb2d8@192.169.1.3
CSeq: 19083 REGISTER
User-Agent: Asterisk PBX 1.6.2.9-2+squeeze4
Authorization: Digest username="XXXX.XXXX", realm="etc.tario.ru", algorithm=MD5, uri="sip:sipnet.ru", nonce="A3DA744B005359D2BEE4", response="88f253ed8d893c81043dc361b471ea90", opaque="opaq", qop=auth, cnonce="0fad86e1", nc=00000004
Expires: 120
Contact: <sip:s@192.169.1.3>
Content-Length: 0
Original comment by voicedes...@gmail.com
on 27 Sep 2012 at 2:59
After
-------------
out: rsp -> tcp[95.26.159.95]:50555 401-INVITE(509 bytes)
SIP/2.0 401 Authentication required
-----------------------------
CSIPCimple has to send INVITE with my password...
Original comment by voicedes...@gmail.com
on 27 Sep 2012 at 3:07
By we manage to see only REGISTER
Original comment by voicedes...@gmail.com
on 27 Sep 2012 at 3:09
The same issues are 1958, 1997 and related to SIP stack functionality..
Original comment by voicedes...@gmail.com
on 27 Sep 2012 at 3:14
Issue 1958 has been merged into this issue.
Original comment by r3gis...@gmail.com
on 15 Nov 2012 at 11:29
Issue 1997 has been merged into this issue.
Original comment by r3gis...@gmail.com
on 15 Nov 2012 at 11:30
Issue 2081 has been merged into this issue.
Original comment by r3gis...@gmail.com
on 24 Nov 2012 at 12:08
From 2081 feedback seems fixed with latest nightly builds.
Original comment by r3gis...@gmail.com
on 24 Nov 2012 at 12:09
[deleted comment]
Re-opened as apparently not fixed on all devices. Sounds somehow linked to
device in use. Maybe something with some 4.x tcp layer.
Original comment by r3gis...@gmail.com
on 30 Nov 2012 at 11:03
Issue 2098 has been merged into this issue.
Original comment by r3gis...@gmail.com
on 30 Nov 2012 at 11:03
How i can help? how i can attach log file?
Original comment by KYA...@gmail.com
on 1 Dec 2012 at 11:10
Log file on google drive
https://docs.google.com/open?id=0B3yNMqS1gcfpQTJYbERDclRDQ2s
Original comment by KYA...@gmail.com
on 1 Dec 2012 at 11:31
For all having the problem a temporary workaround is to switch to UDP transport.
(long press account row, choose wizard and pick expert; then in "transport"
select UDP)
Meanwhile, I'll try to understand why on some devices TCP layer is broken.
Apparently it's not all devices as I'm able to get things working on my devices
with sipnet.ru
Original comment by r3gis...@gmail.com
on 1 Dec 2012 at 1:03
just a quick thought: i think it's more about the firmwares than the devices,
but it's just a wild guess.
e.g. the tethering on my cyanogenmod 9.1 running on galaxy s2 just stopped
working (dhcp doesn't answer) after working fine for half a year.
random note: my internal dialer works with sipnet.ru on the same device where
CSipSimple times out.
thanks for the workaround, and especially for your work!
Original comment by attila.l...@gmail.com
on 1 Dec 2012 at 1:57
yes, internal dialer works well with sipnet.ru....
BTW
I use ARHD 6.8.0 on my HTC Sensation...
Original comment by voicedes...@gmail.com
on 1 Dec 2012 at 2:05
lI'd add another things... CSIPSimple worked well with authorization so w/o 408
err. couple releases ago. Sorry that I can't indicated the exact version of
it....
Original comment by voicedes...@gmail.com
on 1 Dec 2012 at 2:08
with UDP work fine
Original comment by KYA...@gmail.com
on 1 Dec 2012 at 5:43
I was able to find a device where to reproduce the same kind of problems.
So I found a fix that works pretty well on this device and pushed it in nightly
build version. Could some of you try to download and upgrade using
http://nightlies.csipsimple.com/trunk/CSipSimple-latest-trunk.apk
(it's revision 2038)
Let me know how it goes with TCP with this version.
Original comment by r3gis...@gmail.com
on 4 Dec 2012 at 8:49
Arg, update : the r2038 is somehow broken with timers. I've just fixed that.
However I'm still interested by tests (as may still fix the issue). But tests
with r2039+ will be more relevant.
Original comment by r3gis...@gmail.com
on 4 Dec 2012 at 9:34
First time when csipsimple try to register sipnet account the app crashed and
louncher crashed.
I restart csipsimple, sipnet registered successfully, but when i try to call,
the app freez and i can't end the call, processor is noticeably warmer.
LOG file https://docs.google.com/open?id=0B3yNMqS1gcfpY043VjFSd2xSTzg
Original comment by KYA...@gmail.com
on 4 Dec 2012 at 9:39
Thanks a lot for the log.
Sounds the problem I detected with timers. A new version r2040 will be produced
in about 1h20.
Original comment by r3gis...@gmail.com
on 4 Dec 2012 at 10:15
thank's for your work :) but on r2041 the same error, log
https://docs.google.com/open?id=0B3yNMqS1gcfpTUhoVUtxUWstdkU
Original comment by KYA...@gmail.com
on 4 Dec 2012 at 5:37
also the same for me with r2041. galaxy s2 with CM 9.1.
tried with TCP disabled, then it can't register on sipnet.hu (although it does
register to https://ostel.me)
Original comment by attila.l...@gmail.com
on 6 Dec 2012 at 11:53
On update on the issue :
I spent all my day trying to debug it as was able to reproduce.
In fact the key point to reproduce is to use a server with TCP on port 5060 and
to try invites with big packets : for example a lot of codecs, ice enabled,
video enabled, sip mode compact disabled - the combination of these allows to
generate big sdp.
As soon as the packet is bigger than a value, the app get totally blacklisted
for this socket and any new sip packets sent (even lower than the limit) will
not be transmitted.
So, it appears that it's something that happens when packet size is bigger than
the MTU.
I found some very crappy workaround to fake the socket layer (basically
changing the MSS etc), but all workarounds I found had limits and can't be
introduced in stable.
So after these debugs, I started to search with correct keywords on google and
found some very interesting topics :
http://bugzilla.netfilter.org/show_bug.cgi?id=760
and finally :
http://code.google.com/p/android/issues/detail?id=32736
And the best workaround that is described in these issues ... and that works !
... is to have :
- remote server listening on a different port than 5060 (I tested with 6060)
- local app not bound to 5060 port (should be fine by default as default is 0 = random free port).
So if you can try this workaround on your side and tell me how it goes.
BTW, I'm very surprised there is such a rule on netfilter. SIP uses TCP to
solve the MTU limit... so they are absolutely silly to block a sip app trying
to send packets bigger than mtu limit ! And apparently it's not platform
specific... so I fear the guy that introduced this limit will break a lot of
apps !
Another workaround is to try to reduce SIP packet size (to do so, having less
codecs activated, sip compact mode enabled, disabling ICE can help).
Original comment by r3gis...@gmail.com
on 17 Feb 2013 at 9:55
Issue 2113 has been merged into this issue.
Original comment by r3gis...@gmail.com
on 17 Feb 2013 at 9:55
Issue 2184 has been merged into this issue.
Original comment by r3gis...@gmail.com
on 17 Feb 2013 at 9:56
Issue 1789 has been merged into this issue.
Original comment by r3gis...@gmail.com
on 4 Mar 2013 at 5:39
Original comment by r3gis...@gmail.com
on 6 Mar 2013 at 10:45
Latest version from market... getting "408 Request timeout" all the time.
Trying to dial from LG 4x HD (4.1.2) and sipnet account.. :( tried to reduce
codec list.. stun/no stun.. no difference. simply doesn't work
Original comment by nevgen...@gmail.com
on 14 Apr 2013 at 12:53
Issue 2220 has been merged into this issue.
Original comment by r3gis...@gmail.com
on 21 Apr 2013 at 10:10
still exist in latest version CSipSimple-latest-trunk.apk 2014-07-30 12:20
Original comment by TheExtranion
on 30 Jul 2014 at 11:33
Had similar issues, sip compact mode helped.
Original comment by freegli...@gmail.com
on 10 Oct 2014 at 6:07
Original issue reported on code.google.com by
voicedes...@gmail.com
on 27 Sep 2012 at 2:37