Re: [Kamailio-Users] [Bulk] Re: [Kamailio-Devel] [Bulk] Re: [Bulk] Re: Kamailio 1.4.2 : Weird Retransmission

9 Dec 2008

I am able to reproduce it with 1 call / second without my module on BYE 
requests.
here are traces.

ps: I added the ms on Logs.

Aurelien

Daniel-Constantin Mierla a écrit :
...
  On 12/09/08 17:56, Klaus Darilion wrote:

  Daniel-Constantin Mierla schrieb:

  Hello,

 On 12/09/08 17:31, Klaus Darilion wrote:

  Aurelien Grimaud schrieb:

> Fair enough.
> If no one already experienced this strange behavior, it should be my 
> module ...
> I'll try to make it again without my module.
>     
>         
>           
 See my other email.

> However, in the log, after the 200 response, there is a 
> cleanup_uac_timers: RETR/FR timers reset.
> So those timers are cleared.
>     
>         
>           
 But the problem is, that the process which handles the INVITE has not 
 finished yet and those (re)SETS the timer.

 @Daniel - Have you investigated the problem?

           so this is the half of the issue reported via:

https://sourceforge.net/tracker/index.php?func=detail&aid=2105813&g…

         yes.

 Can it be related to other modules which register callbacks (e.g. pua 
 module or Aurelien's module?

       what is the requests/second rate when the issue appears?

 At first look, between sending and setting retransmission timer, there 
 is no much processing for the request. The callback executed there is in 
 use by siptrace, are you using this module?

 Cheers,
 Daniel

  This one got lost, but as I started to fix the
other half (replying 
 using proper mode to do retransmission), will investigate this as well ...

 Cheers,
 Daniel

> regards
> klaus
>
>  
>       
>         
>> To investigate any further, could you point me where in the source 
>> the retransmission timers are cleared ?
>>
>> Aurelien
>>
>> Klaus Darilion a écrit :
>>    
>>         
>>           
>>> Is it also happening WITHOUT your module?
>>>
>>> klaus
>>>
>>> Aurelien Grimaud schrieb:
>>>      
>>>           
>>>             
>>>> As a matter of fact, I already checked this.
>>>> There is a reply route set before t_relay, and log outputs in it.
>>>> The log line is well seen on 180 and on 200.
>>>> This does not avoid retransmission.
>>>>
>>>> Here is a log file with much trace for a call that was answered but 
>>>> retransmitted.
>>>>
>>>> on an INVITE, a module of mine is collecting all contacts for a 
>>>> serial forking.
>>>> an on_reply_route is set, with a trace of mine in it
>>>>
>>>> My log format is :
>>>> T000 [date] [time] bin#ser#<pid>#-1 = <log>
>>>>
>>>> This was on a 1 call only.
>>>> I cannot figure out what is happening.
>>>>
>>>> Any comment  is welcome.
>>>>
>>>> Thanks !
>>>> Aurelien
>>>>
>>>> Klaus Darilion a écrit :
>>>>        
>>>>             
>>>>               
>>>>> Hi!
>>>>>
>>>>> 1. Not the ACK, but the 200 Ok will stop retransmission. I suspect 
>>>>> that the 200 ok is not identified as belonging to the INVITE 
>>>>> transaction.
>>>>>
>>>>> Try this:
>>>>>
>>>>> 1. before t_relay() activate a certain reply_route
(t_on_reply("3"))
>>>>> 2. put some xlog in the the default reply route
>>>>>
>>>>> onreply_route {
>>>>>     xlog("===========================");
>>>>>     xlog("default reply route ...\n");
>>>>>     xlog("response: $$rm = $rm\n");
>>>>>     xlog("response: $mb\n");
>>>>>     xlog("===========================");
>>>>> }
>>>>>
>>>>> 3. put some xlog in the reply route you activated with t_on_reply()
>>>>>
>>>>> onreply_route[3] {
>>>>>     xlog("===========================");
>>>>>     xlog("reply route 3 ...\n");
>>>>>     xlog("response: $$rm = $rm\n");
>>>>>     xlog("response: $mb\n");
>>>>>     xlog("===========================");
>>>>> }
>>>>>
>>>>> 4. watch the log output
>>>>>
>>>>> If both reply routes are exectued then kamailio successfully 
>>>>> matched the reply to the response. If only the default reply route 
>>>>> is executed then the transaction matching failed.
>>>>>
>>>>> Try only with a single call (not 1000 calls/s) first.
>>>>>
>>>>> regards
>>>>> klaus
>>>>>
>>>>> Aurelien Grimaud schrieb:
>>>>>          
>>>>>               
>>>>>                 
>>>>>> Hi, I am using kamailio 1.4.2 and testing it with sipp.
>>>>>> one sipp is client a uac (port 5066), the other is a uas (port 
>>>>>> 5063).
>>>>>> kamailio is using 5060.
>>>>>>
>>>>>> I am generating 100 calls per second for 1000 calls and message 
>>>>>> were retransmitted 4 times.
>>>>>>
>>>>>> Here is a tcpdump of sip packets.
>>>>>> Can anyone tell me why there is an INVITE retransmission at 
>>>>>> 16:16:38.627198 though the ACK for invite was received at 
>>>>>> 16:16:38.126096 ?
>>>>>> Is there a known problem with retransmission timers ?
>>>>>>
>>>>>> 16:16:38.120384 IP 192.168.168.33.5066 > 192.168.168.33.5060:

>>>>>> SIP, length: 579
>>>>>> E.._..@.@.f....!...!.....K..INVITE sip:otest@testg5 SIP/2.0
>>>>>> Via: SIP/2.0/UDP 127.0.0.1:5066;branch=z9hG4bK-23096-730-1
>>>>>> From: sipp 
>>>>>>
<sip:730-23096-127.0.0.1@127.0.0.1:5066>;tag=23096SIPpTag09730
>>>>>> To: sut <sip:otest@testg5>
>>>>>> Call-ID: 730-23096-127.0.0.1
>>>>>> CSeq: 1 INVITE
>>>>>> Contact: sip:sipp@127.0.0.1:5066
>>>>>> Max-Forwards: 70
>>>>>> Expires: 180
>>>>>> Subject: Performance Test
>>>>>> Content-Type: application/sdp
>>>>>> Content-Length:   188
>>>>>>
>>>>>> v=0
>>>>>> o=user1 53655765 2353687637 IN IP4 127.0.0.1
>>>>>> s=-
>>>>>> c=IN IP4 127.0.0.1
>>>>>> t=0 0
>>>>>> m=audio 8925 RTP/AVP 8 101
>>>>>> a=rtpmap:8 PCMA/8000
>>>>>> a=rtpmap:101 telephone-event/8000
>>>>>> a=fmtp:101 0-11,16
>>>>>>
>>>>>> 16:16:38.123426 IP 192.168.168.33.5060 > 192.168.168.33.5066:

>>>>>> SIP, length: 325
>>>>>> E..a..@.@.g....!...!.....M..SIP/2.0 100 Giving a try
>>>>>> Via: SIP/2.0/UDP 
>>>>>>
127.0.0.1:5066;branch=z9hG4bK-23096-730-1;received=192.168.168.33
>>>>>> From: sipp 
>>>>>>
<sip:730-23096-127.0.0.1@127.0.0.1:5066>;tag=23096SIPpTag09730
>>>>>> To: sut <sip:otest@testg5>
>>>>>> Call-ID: 730-23096-127.0.0.1
>>>>>> CSeq: 1 INVITE
>>>>>> Server: Kamailio (1.4.2-notls (i386/linux))
>>>>>> Content-Length: 0
>>>>>>
>>>>>>
>>>>>> 16:16:38.123554 IP 192.168.168.33.5060 > 192.168.168.33.5063:

>>>>>> SIP, length: 731
>>>>>> E.....@.@.fZ...!...!........INVITE sip:otest@testg5 SIP/2.0
>>>>>> Record-Route:
<sip:192.168.168.33;lr=on;ftag=23096SIPpTag09730>
>>>>>> Via: SIP/2.0/UDP 192.168.168.33;branch=z9hG4bKcb7d.7c08af34.0
>>>>>> Via: SIP/2.0/UDP 
>>>>>>
127.0.0.1:5066;received=192.168.168.33;branch=z9hG4bK-23096-730-1
>>>>>> From: sipp 
>>>>>>
<sip:730-23096-127.0.0.1@127.0.0.1:5066>;tag=23096SIPpTag09730
>>>>>> To: sut <sip:otest@testg5>
>>>>>> Call-ID: 730-23096-127.0.0.1
>>>>>> CSeq: 1 INVITE
>>>>>> Contact: sip:sipp@127.0.0.1:5066
>>>>>> Max-Forwards: 69
>>>>>> Expires: 180
>>>>>> Subject: Performance Test
>>>>>> Content-Type: application/sdp
>>>>>> Content-Length:   188
>>>>>>
>>>>>> v=0
>>>>>> o=user1 53655765 2353687637 IN IP4 127.0.0.1
>>>>>> s=-
>>>>>> c=IN IP4 127.0.0.1
>>>>>> t=0 0
>>>>>> m=audio 8925 RTP/AVP 8 101
>>>>>> a=rtpmap:8 PCMA/8000
>>>>>> a=rtpmap:101 telephone-event/8000
>>>>>> a=fmtp:101 0-11,16
>>>>>>
>>>>>> 16:16:38.123830 IP 192.168.168.33.5063 > 192.168.168.33.5060:

>>>>>> SIP, length: 451
>>>>>> E.....@.@.gz...!...!.......pSIP/2.0 180 Ringing
>>>>>> Via: SIP/2.0/UDP 192.168.168.33;branch=z9hG4bKcb7d.7c08af34.0, 
>>>>>> SIP/2.0/UDP 
>>>>>>
127.0.0.1:5066;received=192.168.168.33;branch=z9hG4bK-23096-730-1
>>>>>> From: sipp 
>>>>>>
<sip:730-23096-127.0.0.1@127.0.0.1:5066>;tag=23096SIPpTag09730
>>>>>> To: sut <sip:otest@testg5>;tag=17278SIPpTag01696
>>>>>> Call-ID: 730-23096-127.0.0.1
>>>>>> CSeq: 1 INVITE
>>>>>> Record-Route:
<sip:192.168.168.33;lr=on;ftag=23096SIPpTag09730>
>>>>>> Contact: <sip:127.0.0.1:5063>
>>>>>> Content-Length: 0
>>>>>>
>>>>>>
>>>>>> 16:16:38.124169 IP 192.168.168.33.5060 > 192.168.168.33.5066:

>>>>>> SIP, length: 393
>>>>>> E.....@.@.g....!...!.......6SIP/2.0 180 Ringing
>>>>>> Via: SIP/2.0/UDP 
>>>>>>
127.0.0.1:5066;received=192.168.168.33;branch=z9hG4bK-23096-730-1
>>>>>> From: sipp 
>>>>>>
<sip:730-23096-127.0.0.1@127.0.0.1:5066>;tag=23096SIPpTag09730
>>>>>> To: sut <sip:otest@testg5>;tag=17278SIPpTag01696
>>>>>> Call-ID: 730-23096-127.0.0.1
>>>>>> CSeq: 1 INVITE
>>>>>> Record-Route:
<sip:192.168.168.33;lr=on;ftag=23096SIPpTag09730>
>>>>>> Contact: <sip:127.0.0.1:5063>
>>>>>> Content-Length: 0
>>>>>>
>>>>>>
>>>>>> 16:16:38.124326 IP 192.168.168.33.5063 > 192.168.168.33.5060:

>>>>>> SIP, length: 634
>>>>>> E.....@.@.f....!...!.......'SIP/2.0 200 OK
>>>>>> Via: SIP/2.0/UDP 192.168.168.33;branch=z9hG4bKcb7d.7c08af34.0, 
>>>>>> SIP/2.0/UDP 
>>>>>>
127.0.0.1:5066;received=192.168.168.33;branch=z9hG4bK-23096-730-1
>>>>>> From: sipp 
>>>>>>
<sip:730-23096-127.0.0.1@127.0.0.1:5066>;tag=23096SIPpTag09730
>>>>>> To: sut <sip:otest@testg5>;tag=17278SIPpTag01696
>>>>>> Call-ID: 730-23096-127.0.0.1
>>>>>> CSeq: 1 INVITE
>>>>>> Record-Route:
<sip:192.168.168.33;lr=on;ftag=23096SIPpTag09730>
>>>>>> Contact: <sip:127.0.0.1:5063>
>>>>>> Content-Type: application/sdp
>>>>>> Content-Length:   153
>>>>>>
>>>>>> v=0
>>>>>> o=user1 53655765 2353687637 IN IP4 127.0.0.1
>>>>>> s=-
>>>>>> c=IN IP4 127.0.0.1
>>>>>> t=0 0
>>>>>> m=audio 6004 RTP/AVP 0 8
>>>>>> a=rtpmap:0 PCMU/8000
>>>>>> a=rtpmap:8 PCMA/8000
>>>>>>
>>>>>> 16:16:38.124883 IP 192.168.168.33.5060 > 192.168.168.33.5066:

>>>>>> SIP, length: 581
>>>>>> E..a..@.@.f....!...!.....M..SIP/2.0 200 OK
>>>>>> Via: SIP/2.0/UDP 
>>>>>>
127.0.0.1:5066;received=192.168.168.33;branch=z9hG4bK-23096-730-1
>>>>>> From: sipp 
>>>>>>
<sip:730-23096-127.0.0.1@127.0.0.1:5066>;tag=23096SIPpTag09730
>>>>>> To: sut <sip:otest@testg5>;tag=17278SIPpTag01696
>>>>>> Call-ID: 730-23096-127.0.0.1
>>>>>> CSeq: 1 INVITE
>>>>>> Record-Route:
<sip:192.168.168.33;lr=on;ftag=23096SIPpTag09730>
>>>>>> Contact: <sip:192.168.168.33:5063>
>>>>>> Content-Type: application/sdp
>>>>>> Content-Length:   153
>>>>>>
>>>>>> v=0
>>>>>> o=user1 53655765 2353687637 IN IP4 127.0.0.1
>>>>>> s=-
>>>>>> c=IN IP4 127.0.0.1
>>>>>> t=0 0
>>>>>> m=audio 6004 RTP/AVP 0 8
>>>>>> a=rtpmap:0 PCMU/8000
>>>>>> a=rtpmap:8 PCMA/8000
>>>>>>
>>>>>> 16:16:38.125532 IP 192.168.168.33.5066 > 192.168.168.33.5060:

>>>>>> SIP, length: 427
>>>>>> E.....@.@.g....!...!.......XACK sip:192.168.168.33:5063 SIP/2.0
>>>>>> Via: SIP/2.0/UDP 127.0.0.1:5066;branch=z9hG4bK-23096-730-11
>>>>>> From: sipp 
>>>>>>
<sip:730-23096-127.0.0.1@127.0.0.1:5066>;tag=23096SIPpTag09730
>>>>>> To: sut <sip:otest@testg5>;tag=17278SIPpTag01696
>>>>>> Route: <sip:192.168.168.33;lr=on;ftag=23096SIPpTag09730>
>>>>>> Call-ID: 730-23096-127.0.0.1
>>>>>> CSeq: 1 INVITE
>>>>>> Contact: sip:sipp@127.0.0.1:5066
>>>>>> Max-Forwards: 70
>>>>>> Subject: Performance Test
>>>>>> Content-Length: 0
>>>>>>
>>>>>>
>>>>>> 16:16:38.126096 IP 192.168.168.33.5060 > 192.168.168.33.5063:

>>>>>> SIP, length: 521
>>>>>> E..%..@.@.g,...!...!........ACK sip:192.168.168.33:5063 SIP/2.0
>>>>>> Record-Route:
<sip:192.168.168.33;lr=on;ftag=23096SIPpTag09730>
>>>>>> Via: SIP/2.0/UDP 192.168.168.33;branch=z9hG4bKcb7d.7c08af34.2
>>>>>> Via: SIP/2.0/UDP 
>>>>>>
127.0.0.1:5066;received=192.168.168.33;branch=z9hG4bK-23096-730-11
>>>>>> From: sipp 
>>>>>>
<sip:730-23096-127.0.0.1@127.0.0.1:5066>;tag=23096SIPpTag09730
>>>>>> To: sut <sip:otest@testg5>;tag=17278SIPpTag01696
>>>>>> Call-ID: 730-23096-127.0.0.1
>>>>>> CSeq: 1 INVITE
>>>>>> Contact: sip:sipp@127.0.0.1:5066
>>>>>> Max-Forwards: 69
>>>>>> Subject: Performance Test
>>>>>> Content-Length: 0
>>>>>>
>>>>>>
>>>>>> 16:16:38.627198 IP 192.168.168.33.5060 > 192.168.168.33.5063:

>>>>>> SIP, length: 731
>>>>>> E.....@.@.fZ...!...!........INVITE sip:otest@testg5 SIP/2.0
>>>>>> Record-Route:
<sip:192.168.168.33;lr=on;ftag=23096SIPpTag09730>
>>>>>> Via: SIP/2.0/UDP 192.168.168.33;branch=z9hG4bKcb7d.7c08af34.0
>>>>>> Via: SIP/2.0/UDP 
>>>>>>
127.0.0.1:5066;received=192.168.168.33;branch=z9hG4bK-23096-730-1
>>>>>> From: sipp 
>>>>>>
<sip:730-23096-127.0.0.1@127.0.0.1:5066>;tag=23096SIPpTag09730
>>>>>> To: sut <sip:otest@testg5>
>>>>>> Call-ID: 730-23096-127.0.0.1
>>>>>> CSeq: 1 INVITE
>>>>>> Contact: sip:sipp@127.0.0.1:5066
>>>>>> Max-Forwards: 69
>>>>>> Expires: 180
>>>>>> Subject: Performance Test
>>>>>> Content-Type: application/sdp
>>>>>> Content-Length:   188
>>>>>>
>>>>>> v=0
>>>>>> o=user1 53655765 2353687637 IN IP4 127.0.0.1
>>>>>> s=-
>>>>>> c=IN IP4 127.0.0.1
>>>>>> t=0 0
>>>>>> m=audio 8925 RTP/AVP 8 101
>>>>>> a=rtpmap:8 PCMA/8000
>>>>>> a=rtpmap:101 telephone-event/8000
>>>>>> a=fmtp:101 0-11,16
>>>>>>
>>>>>> 16:16:38.627677 IP 192.168.168.33.5063 > 192.168.168.33.5060:

>>>>>> SIP, length: 474
>>>>>> E.....@.@.gc...!...!........SIP/2.0 180 Ringing
>>>>>> Via: SIP/2.0/UDP 192.168.168.33;branch=z9hG4bKcb7d.7c08af34.2, 
>>>>>> SIP/2.0/UDP 
>>>>>>
127.0.0.1:5066;received=192.168.168.33;branch=z9hG4bK-23096-730-11
>>>>>> From: sipp 
>>>>>>
<sip:730-23096-127.0.0.1@127.0.0.1:5066>;tag=23096SIPpTag09730
>>>>>> To: sut 
>>>>>>
<sip:otest@testg5>;tag=17278SIPpTag01696;tag=17278SIPpTag01696
>>>>>> Call-ID: 730-23096-127.0.0.1
>>>>>> CSeq: 1 INVITE
>>>>>> Record-Route:
<sip:192.168.168.33;lr=on;ftag=23096SIPpTag09730>
>>>>>> Contact: <sip:127.0.0.1:5063>
>>>>>> Content-Length: 0
>>>>>>
>>>>>>
>>>>>> 16:16:38.627970 IP 192.168.168.33.5060 > 192.168.168.33.5066:

>>>>>> SIP, length: 416
>>>>>> E.....@.@.g....!...!.......MSIP/2.0 180 Ringing
>>>>>> Via: SIP/2.0/UDP 
>>>>>>
127.0.0.1:5066;received=192.168.168.33;branch=z9hG4bK-23096-730-11
>>>>>> From: sipp 
>>>>>>
<sip:730-23096-127.0.0.1@127.0.0.1:5066>;tag=23096SIPpTag09730
>>>>>> To: sut 
>>>>>>
<sip:otest@testg5>;tag=17278SIPpTag01696;tag=17278SIPpTag01696
>>>>>> Call-ID: 730-23096-127.0.0.1
>>>>>> CSeq: 1 INVITE
>>>>>> Record-Route:
<sip:192.168.168.33;lr=on;ftag=23096SIPpTag09730>
>>>>>> Contact: <sip:127.0.0.1:5063>
>>>>>> Content-Length: 0
>>>>>>
>>>>>>
>>>>>> 16:16:39.642356 IP 192.168.168.33.5060 > 192.168.168.33.5063:

>>>>>> SIP, length: 731
>>>>>> E.....@.@.fZ...!...!........INVITE sip:otest@testg5 SIP/2.0
>>>>>> Record-Route:
<sip:192.168.168.33;lr=on;ftag=23096SIPpTag09730>
>>>>>> Via: SIP/2.0/UDP 192.168.168.33;branch=z9hG4bKcb7d.7c08af34.0
>>>>>> Via: SIP/2.0/UDP 
>>>>>>
127.0.0.1:5066;received=192.168.168.33;branch=z9hG4bK-23096-730-1
>>>>>> From: sipp 
>>>>>>
<sip:730-23096-127.0.0.1@127.0.0.1:5066>;tag=23096SIPpTag09730
>>>>>> To: sut <sip:otest@testg5>
>>>>>> Call-ID: 730-23096-127.0.0.1
>>>>>> CSeq: 1 INVITE
>>>>>> Contact: sip:sipp@127.0.0.1:5066
>>>>>> Max-Forwards: 69
>>>>>> Expires: 180
>>>>>> Subject: Performance Test
>>>>>> Content-Type: application/sdp
>>>>>> Content-Length:   188
>>>>>>
>>>>>> v=0
>>>>>> o=user1 53655765 2353687637 IN IP4 127.0.0.1
>>>>>> s=-
>>>>>> c=IN IP4 127.0.0.1
>>>>>> t=0 0
>>>>>> m=audio 8925 RTP/AVP 8 101
>>>>>> a=rtpmap:8 PCMA/8000
>>>>>> a=rtpmap:101 telephone-event/8000
>>>>>> a=fmtp:101 0-11,16
>>>>>>
>>>>>> 16:16:39.642587 IP 192.168.168.33.5063 > 192.168.168.33.5060:

>>>>>> SIP, length: 474
>>>>>> E.....@.@.gc...!...!........SIP/2.0 180 Ringing
>>>>>> Via: SIP/2.0/UDP 192.168.168.33;branch=z9hG4bKcb7d.7c08af34.2, 
>>>>>> SIP/2.0/UDP 
>>>>>>
127.0.0.1:5066;received=192.168.168.33;branch=z9hG4bK-23096-730-11
>>>>>> From: sipp 
>>>>>>
<sip:730-23096-127.0.0.1@127.0.0.1:5066>;tag=23096SIPpTag09730
>>>>>> To: sut 
>>>>>>
<sip:otest@testg5>;tag=17278SIPpTag01696;tag=17278SIPpTag01696
>>>>>> Call-ID: 730-23096-127.0.0.1
>>>>>> CSeq: 1 INVITE
>>>>>> Record-Route:
<sip:192.168.168.33;lr=on;ftag=23096SIPpTag09730>
>>>>>> Contact: <sip:127.0.0.1:5063>
>>>>>> Content-Length: 0
>>>>>>
>>>>>>
>>>>>> 16:16:39.643723 IP 192.168.168.33.5060 > 192.168.168.33.5066:

>>>>>> SIP, length: 416
>>>>>> E.....@.@.g....!...!.......MSIP/2.0 180 Ringing
>>>>>> Via: SIP/2.0/UDP 
>>>>>>
127.0.0.1:5066;received=192.168.168.33;branch=z9hG4bK-23096-730-11
>>>>>> From: sipp 
>>>>>>
<sip:730-23096-127.0.0.1@127.0.0.1:5066>;tag=23096SIPpTag09730
>>>>>> To: sut 
>>>>>>
<sip:otest@testg5>;tag=17278SIPpTag01696;tag=17278SIPpTag01696
>>>>>> Call-ID: 730-23096-127.0.0.1
>>>>>> CSeq: 1 INVITE
>>>>>> Record-Route:
<sip:192.168.168.33;lr=on;ftag=23096SIPpTag09730>
>>>>>> Contact: <sip:127.0.0.1:5063>
>>>>>> Content-Length: 0
>>>>>>
>>>>>>
>>>>>> 16:16:39.797641 IP 192.168.168.33.5066 > 192.168.168.33.5060:

>>>>>> SIP, length: 434
>>>>>> E.....@.@.g....!...!......._BYE sip:127.0.0.1:5063 SIP/2.0
>>>>>> Via: SIP/2.0/UDP 127.0.0.1:5066;branch=z9hG4bK-23096-730-46
>>>>>> From: sipp 
>>>>>>
<sip:730-23096-127.0.0.1@127.0.0.1:5066>;tag=23096SIPpTag09730
>>>>>> To: sut
<sip:service@192.168.168.33:5060>;tag=17278SIPpTag01696
>>>>>> Route: <sip:192.168.168.33;lr=on;ftag=23096SIPpTag09730>
>>>>>> Call-ID: 730-23096-127.0.0.1
>>>>>> CSeq: 2 BYE
>>>>>> Contact: sip:sipp@127.0.0.1:5066
>>>>>> Max-Forwards: 70
>>>>>> Subject: Performance Test
>>>>>> Content-Length: 0
>>>>>>
>>>>>>
>>>>>> 16:16:39.798436 IP 192.168.168.33.5060 > 127.0.0.1.5063: SIP,

>>>>>> length: 528
>>>>>> E..,..@.@.P....!............BYE sip:127.0.0.1:5063 SIP/2.0
>>>>>> Record-Route:
<sip:192.168.168.33;lr=on;ftag=23096SIPpTag09730>
>>>>>> Via: SIP/2.0/UDP 192.168.168.33;branch=z9hG4bK9b7d.0423bf25.0
>>>>>> Via: SIP/2.0/UDP 
>>>>>>
127.0.0.1:5066;received=192.168.168.33;branch=z9hG4bK-23096-730-46
>>>>>> From: sipp 
>>>>>>
<sip:730-23096-127.0.0.1@127.0.0.1:5066>;tag=23096SIPpTag09730
>>>>>> To: sut
<sip:service@192.168.168.33:5060>;tag=17278SIPpTag01696
>>>>>> Call-ID: 730-23096-127.0.0.1
>>>>>> CSeq: 2 BYE
>>>>>> Contact: sip:sipp@127.0.0.1:5066
>>>>>> Max-Forwards: 69
>>>>>> Subject: Performance Test
>>>>>> Content-Length: 0
>>>>>>
>>>>>>
>>>>>> 16:16:39.798535 IP 192.168.168.33.5063 > 192.168.168.33.5060:

>>>>>> SIP, length: 394
>>>>>> E.....@.@.g....!...!.......7SIP/2.0 200 OK
>>>>>> Via: SIP/2.0/UDP 192.168.168.33;branch=z9hG4bK9b7d.0423bf25.0, 
>>>>>> SIP/2.0/UDP 
>>>>>>
127.0.0.1:5066;received=192.168.168.33;branch=z9hG4bK-23096-730-46
>>>>>> From: sipp 
>>>>>>
<sip:730-23096-127.0.0.1@127.0.0.1:5066>;tag=23096SIPpTag09730
>>>>>> To: sut
<sip:service@192.168.168.33:5060>;tag=17278SIPpTag01696
>>>>>> Call-ID: 730-23096-127.0.0.1
>>>>>> CSeq: 2 BYE
>>>>>> Contact: <sip:127.0.0.1:5063>
>>>>>> Content-Length: 0
>>>>>>
>>>>>>
>>>>>> 16:16:39.798814 IP 192.168.168.33.5060 > 192.168.168.33.5066:

>>>>>> SIP, length: 336
>>>>>> E..l..@.@.g....!...!.....X..SIP/2.0 200 OK
>>>>>> Via: SIP/2.0/UDP 
>>>>>>
127.0.0.1:5066;received=192.168.168.33;branch=z9hG4bK-23096-730-46
>>>>>> From: sipp 
>>>>>>
<sip:730-23096-127.0.0.1@127.0.0.1:5066>;tag=23096SIPpTag09730
>>>>>> To: sut
<sip:service@192.168.168.33:5060>;tag=17278SIPpTag01696
>>>>>> Call-ID: 730-23096-127.0.0.1
>>>>>> CSeq: 2 BYE
>>>>>> Contact: <sip:127.0.0.1:5063>
>>>>>> Content-Length: 0
>>>>>>
>>>>>>
>>>>>> 16:16:40.257973 IP 192.168.168.33.5060 > 127.0.0.1.5063: SIP,

>>>>>> length: 528
>>>>>> E..,..@.@.P....!............BYE sip:127.0.0.1:5063 SIP/2.0
>>>>>> Record-Route:
<sip:192.168.168.33;lr=on;ftag=23096SIPpTag09730>
>>>>>> Via: SIP/2.0/UDP 192.168.168.33;branch=z9hG4bK9b7d.0423bf25.0
>>>>>> Via: SIP/2.0/UDP 
>>>>>>
127.0.0.1:5066;received=192.168.168.33;branch=z9hG4bK-23096-730-46
>>>>>> From: sipp 
>>>>>>
<sip:730-23096-127.0.0.1@127.0.0.1:5066>;tag=23096SIPpTag09730
>>>>>> To: sut
<sip:service@192.168.168.33:5060>;tag=17278SIPpTag01696
>>>>>> Call-ID: 730-23096-127.0.0.1
>>>>>> CSeq: 2 BYE
>>>>>> Contact: sip:sipp@127.0.0.1:5066
>>>>>> Max-Forwards: 69
>>>>>> Subject: Performance Test
>>>>>> Content-Length: 0
>>>>>>
>>>>>>
>>>>>> 16:16:40.258080 IP 192.168.168.33.5063 > 192.168.168.33.5060:

>>>>>> SIP, length: 394
>>>>>> E.....@.@.g....!...!.......7SIP/2.0 200 OK
>>>>>> Via: SIP/2.0/UDP 192.168.168.33;branch=z9hG4bK9b7d.0423bf25.0, 
>>>>>> SIP/2.0/UDP 
>>>>>>
127.0.0.1:5066;received=192.168.168.33;branch=z9hG4bK-23096-730-46
>>>>>> From: sipp 
>>>>>>
<sip:730-23096-127.0.0.1@127.0.0.1:5066>;tag=23096SIPpTag09730
>>>>>> To: sut
<sip:service@192.168.168.33:5060>;tag=17278SIPpTag01696
>>>>>> Call-ID: 730-23096-127.0.0.1
>>>>>> CSeq: 2 BYE
>>>>>> Contact: <sip:127.0.0.1:5063>
>>>>>> Content-Length: 0
>>>>>>
>>>>>>
>>>>>> 16:16:41.285493 IP 192.168.168.33.5060 > 127.0.0.1.5063: SIP,

>>>>>> length: 528
>>>>>> E..,..@.@.P....!............BYE sip:127.0.0.1:5063 SIP/2.0
>>>>>> Record-Route:
<sip:192.168.168.33;lr=on;ftag=23096SIPpTag09730>
>>>>>> Via: SIP/2.0/UDP 192.168.168.33;branch=z9hG4bK9b7d.0423bf25.0
>>>>>> Via: SIP/2.0/UDP 
>>>>>>
127.0.0.1:5066;received=192.168.168.33;branch=z9hG4bK-23096-730-46
>>>>>> From: sipp 
>>>>>>
<sip:730-23096-127.0.0.1@127.0.0.1:5066>;tag=23096SIPpTag09730
>>>>>> To: sut
<sip:service@192.168.168.33:5060>;tag=17278SIPpTag01696
>>>>>> Call-ID: 730-23096-127.0.0.1
>>>>>> CSeq: 2 BYE
>>>>>> Contact: sip:sipp@127.0.0.1:5066
>>>>>> Max-Forwards: 69
>>>>>> Subject: Performance Test
>>>>>> Content-Length: 0
>>>>>>
>>>>>>
>>>>>> 16:16:41.285593 IP 192.168.168.33.5063 > 192.168.168.33.5060:

>>>>>> SIP, length: 394
>>>>>> E.....@.@.g....!...!.......7SIP/2.0 200 OK
>>>>>> Via: SIP/2.0/UDP 192.168.168.33;branch=z9hG4bK9b7d.0423bf25.0, 
>>>>>> SIP/2.0/UDP 
>>>>>>
127.0.0.1:5066;received=192.168.168.33;branch=z9hG4bK-23096-730-46
>>>>>> From: sipp 
>>>>>>
<sip:730-23096-127.0.0.1@127.0.0.1:5066>;tag=23096SIPpTag09730
>>>>>> To: sut
<sip:service@192.168.168.33:5060>;tag=17278SIPpTag01696
>>>>>> Call-ID: 730-23096-127.0.0.1
>>>>>> CSeq: 2 BYE
>>>>>> Contact: <sip:127.0.0.1:5063>
>>>>>> Content-Length: 0
>>>>>>
>>>>>>
>>>>>> 16:16:41.695686 IP 192.168.168.33.5060 > 192.168.168.33.5063:

>>>>>> SIP, length: 731
>>>>>> E.....@.@.fZ...!...!........INVITE sip:otest@testg5 SIP/2.0
>>>>>> Record-Route:
<sip:192.168.168.33;lr=on;ftag=23096SIPpTag09730>
>>>>>> Via: SIP/2.0/UDP 192.168.168.33;branch=z9hG4bKcb7d.7c08af34.0
>>>>>> Via: SIP/2.0/UDP 
>>>>>>
127.0.0.1:5066;received=192.168.168.33;branch=z9hG4bK-23096-730-1
>>>>>> From: sipp 
>>>>>>
<sip:730-23096-127.0.0.1@127.0.0.1:5066>;tag=23096SIPpTag09730
>>>>>> To: sut <sip:otest@testg5>
>>>>>> Call-ID: 730-23096-127.0.0.1
>>>>>> CSeq: 1 INVITE
>>>>>> Contact: sip:sipp@127.0.0.1:5066
>>>>>> Max-Forwards: 69
>>>>>> Expires: 180
>>>>>> Subject: Performance Test
>>>>>> Content-Type: application/sdp
>>>>>> Content-Length:   188
>>>>>>
>>>>>> v=0
>>>>>> o=user1 53655765 2353687637 IN IP4 127.0.0.1
>>>>>> s=-
>>>>>> c=IN IP4 127.0.0.1
>>>>>> t=0 0
>>>>>> m=audio 8925 RTP/AVP 8 101
>>>>>> a=rtpmap:8 PCMA/8000
>>>>>> a=rtpmap:101 telephone-event/8000
>>>>>> a=fmtp:101 0-11,16
>>>>>>
>>>>>> 16:16:43.338592 IP 192.168.168.33.5060 > 127.0.0.1.5063: SIP,

>>>>>> length: 528
>>>>>> E..,..@.@.P....!............BYE sip:127.0.0.1:5063 SIP/2.0
>>>>>> Record-Route:
<sip:192.168.168.33;lr=on;ftag=23096SIPpTag09730>
>>>>>> Via: SIP/2.0/UDP 192.168.168.33;branch=z9hG4bK9b7d.0423bf25.0
>>>>>> Via: SIP/2.0/UDP 
>>>>>>
127.0.0.1:5066;received=192.168.168.33;branch=z9hG4bK-23096-730-46
>>>>>> From: sipp 
>>>>>>
<sip:730-23096-127.0.0.1@127.0.0.1:5066>;tag=23096SIPpTag09730
>>>>>> To: sut
<sip:service@192.168.168.33:5060>;tag=17278SIPpTag01696
>>>>>> Call-ID: 730-23096-127.0.0.1
>>>>>> CSeq: 2 BYE
>>>>>> Contact: sip:sipp@127.0.0.1:5066
>>>>>> Max-Forwards: 69
>>>>>> Subject: Performance Test
>>>>>> Content-Length: 0
>>>>>>
>>>>>>
>>>>>> 16:16:43.338785 IP 192.168.168.33.5063 > 192.168.168.33.5060:

>>>>>> SIP, length: 408
>>>>>> E.....@.@.g....!...!.......ESIP/2.0 200 OK
>>>>>> Via: SIP/2.0/UDP 192.168.168.33;branch=z9hG4bK9b7d.0423bf25.0, 
>>>>>> SIP/2.0/UDP 
>>>>>>
127.0.0.1:5066;received=192.168.168.33;branch=z9hG4bK-23096-730-46
>>>>>> From: sipp 
>>>>>>
<sip:730-23096-127.0.0.1@127.0.0.1:5066>;tag=23096SIPpTag09730
>>>>>> To: sut
<sip:service@192.168.168.33:5060>;tag=17278SIPpTag01696
>>>>>> Call-ID: 730-23096-127.0.0.1
>>>>>> CSeq: 2 BYE
>>>>>> Contact: <sip:127.0.0.1:5063;transport=UDP>
>>>>>> Content-Length: 0
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Users mailing list
>>>>>> Users(a)lists.kamailio.org
>>>>>> http://lists.kamailio.org/cgi-bin/mailman/listinfo/users
>>>>>>             
>>>>>>                 
>>>>>>                   
>>     
>>         
>>           
> _______________________________________________
> Devel mailing list
> Devel(a)lists.kamailio.org
> http://lists.kamailio.org/cgi-bin/mailman/listinfo/devel
>
>   
>       
>           _______________________________________________
 Devel mailing list
 Devel(a)lists.kamailio.org
 http://lists.kamailio.org/cgi-bin/mailman/listinfo/devel

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Re: [Kamailio-Users] [Bulk] Re: [Kamailio-Devel] [Bulk] Re: [Bulk] Re: Kamailio 1.4.2 : Weird Retransmission