Klaus Darilion a écrit : > I do not know where the problem comes from, but indeed Kamailio should > forward the 200 OK from B to A. Well, the 200 from B comes *after* tm timer is triggered. So tm considers this transaction as finished ... Should tm forward 200 from B, or should it reply with a Transaction does not exist or 408 as it seems to be?
The 200 from B does match a transaction (the t_reply is called) and transaction modules says : *reply_received: org. status uas=180, uac[0]=408 local=0 is_invite=1* But is not finally relayed : *relay_reply: branch=0, save=0, relay=-1* Is this because of the 180 from C ? Should not tm relay the 200 Ok and Cancel the dialog with C ? Regards. Aurelien > > regards > klaus > > Aurelien Grimaud schrieb: >> Hi, >> >> Using kamailio 1.4.2, I experienced this : >> A INVITE -> kamailio >> kamailio INVITE -> B >> >> B does not send any provisional, my config enables fail over (serial >> forking) when B does not answer so : >> kamailio retransmit INVITE to B. >> >> then kamailio fails over to C >> kamailio INVITE -> C >> C 180 -> kamailio >> kamailio 180 -> A >> >> Then B answers 200 OK. (It's alive !) >> B 200 -> kamailio >> tm does not relay. >> Retransmission : >> B 200 -> kamailio >> tm does not relay. >> >> Then C : >> C 200 -> kamailio >> kamailio 200 -> A >> Dialog is established between A and C >> >> B goes on retransmitting 200 Ok, kamailio TM drops it. >> >> Then A/C dialogs ends with BYE >> C BYE -> kamailio >> kamailio BYE -> A >> A 200 -> kamailio >> kamailio 200 -> C >> >> B goes on retransmitting 200 Ok >> B 200 -> kamailio >> *and kamailio relays the answer* >> kamailio 200 -> A >> >> NOTE that dialog module complains : >> Jan 6 16:44:47 [25047] DBG:tm:t_should_relay_response: T_code=200, >> new_code=200 >> Jan 6 16:44:47 [25047] DBG:tm:t_should_relay_response: 200 OK for >> INVITE after final sent >> Jan 6 16:44:47 [25047] DBG:tm:relay_reply: branch=0, save=0, relay=0 >> Jan 6 16:44:47 [25047] DBG:tm:run_trans_callbacks: trans=0xb64d8418, >> callback type 16, id 0 entered >> Jan 6 16:44:47 [25047] DBG:core:build_res_buf_from_sip_res: old >> size: 704, new size: 646 >> Jan 6 16:44:47 [25047] DBG:core:build_res_buf_from_sip_res: copied >> size: orig:445, new: 387, rest: 259 msg= >> SIP/2.0 200 OK^M >> Via: SIP/2.0/UDP >> 192.168.160.141:5063;received=127.0.0.1;branch=z9hG4bk171-1^M >> From: sipp >> <sip:[email protected]:5063>;tag=22740SIPpTag09171^M >> >> To: sut <sip:si...@agent>;tag=21152SIPpTag01266^M >> Call-ID: 171-22740-192.168.160.141^M >> CSeq: 1 INVITE^M >> Record-Route: >> <sip:127.0.0.1;lr=on;ftag=22740SIPpTag09171;did=aaf.ae11fa93>^M >> Contact: <sip:127.0.0.1:5061>^M >> >> Jan 6 16:44:47 [25047] DBG:tm:update_totag_set: new totag >> Jan 6 16:44:47 [25047] DBG:tm:relay_reply: sent buf=0x81a3fe0: >> SIP/2.0 2..., shmem=0xb5d09a90: SIP/2.0 2 >> Jan 6 16:44:47 [25047] DBG:tm:run_trans_callbacks: trans=0xb64d8418, >> callback type 128, id 0 entered >> *Jan 6 16:44:47 [25047] CRITICAL:dialog:next_state_dlg: bogus event >> 3 in state 5 (with BYE) for dlg with clid '171-22740-192.168.160.141' >> and tags '22740SIPpTag09171' '21199SIPpTag01391' * >> Jan 6 16:44:47 [25047] DBG:dialog:next_state_dlg: dialog 0xb5b912a0 >> changed from state 5 to state 5, due event 3 >> Jan 6 16:44:47 [25047] DBG:tm:t_unref: UNREF_UNSAFE: after is 0 >> Jan 6 16:44:47 [25047] DBG:core:destroy_avp_list: destroying list (nil) >> Jan 6 16:44:47 [25047] DBG:core:receive_msg: cleaning up >> >> and A takes the Call >> A ACK -> kamailio >> kamailio ACK -> B >> >> A, B and C are sipp >> A = localhost:5063 >> B = localhost:5061 >> C = localhost:5062 >> >> 200 Ok Should be dropped : this transaction was considered a failure >> when tm timer triggered because of lack of provisional. >> What do you think ? >> >> A openser B c >> | | | | >> | -- INVITE --> | | | >> | <-- 100 --- | | | >> | | -- INVITE --> | | >> | | -- INVITE --> | | >> | | -- INVITE --> | | >> >> Serial forking towards C after tm timer triggers >> | | -----------------INVITE --> | >> | | <----------------180 ------ | >> | <-- 180 --- | | | >> | | | | >> | | <-- 200 --- | | >> | | <-- 200 --- | | >> | | <-- 200 --- | | >> | | | | >> | | | | >> | | <--------------- 200 ------ | >> | <-- 200 --- | | | >> | -- ACK --> | | | >> | | ------------------ ACK ---> | >> | -- BYE --> | | | >> | | ------------------ BYE ---> >> | | <--------------- 200 ------ | >> | <-- 200 --- | | | >> >> New Retransmission of 200 Ok from B which is relayed ! >> | | <-- 200 --- | | >> | <-- 200 --- | | | >> | -- ACK --> | | | >> >> Here is the tcpdump. >> >> >> 16:44:30.853951 IP 127.0.0.1.5063 > 127.0.0.1.5060: SIP, length: 612 >> e.....@.@.:k.............l..INVITE sip:si...@agent SIP/2.0 >> Via: SIP/2.0/UDP 192.168.160.141:5063;branch=z9hG4bk171-1 >> From: sipp >> <sip:[email protected]:5063>;tag=22740SIPpTag09171 >> >> To: sut <sip:si...@agent> >> Call-ID: 171-22740-192.168.160.141 >> CSeq: 1 INVITE >> Contact: sip:[email protected]:5063 >> Max-Forwards: 70 >> Expires: 180 >> Subject: Performance Test >> Content-Type: application/sdp >> Content-Length: 200 >> >> v=0 >> o=user1 53655765 2353687637 IN IP4 192.168.160.141 >> s=- >> c=IN IP4 192.168.160.141 >> t=0 0 >> m=audio 6684 RTP/AVP 8 101 >> a=rtpmap:8 PCMA/8000 >> a=rtpmap:101 telephone-event/8000 >> a=fmtp:101 0-11,16 >> >> 16:44:30.855266 IP 127.0.0.1.5060 > 127.0.0.1.5063: SIP, length: 336 >> e.....@.@.;w.............X.kSIP/2.0 100 Giving a try >> Via: SIP/2.0/UDP >> 192.168.160.141:5063;branch=z9hG4bk171-1;received=127.0.0.1 >> From: sipp >> <sip:[email protected]:5063>;tag=22740SIPpTag09171 >> >> To: sut <sip:si...@agent> >> Call-ID: 171-22740-192.168.160.141 >> CSeq: 1 INVITE >> Server: Kamailio (1.4.2-notls (i386/linux)) >> Content-Length: 0 >> >> >> 16:44:30.855390 IP 127.0.0.1.5060 > 127.0.0.1.5061: SIP, length: 765 >> e.....@[email protected] sip:si...@agent SIP/2.0 >> Record-Route: >> <sip:127.0.0.1;lr=on;ftag=22740SIPpTag09171;did=aaf.ae11fa93> >> Via: SIP/2.0/UDP 127.0.0.1;branch=z9hG4bKc109.ba08ceb.0 >> Via: SIP/2.0/UDP >> 192.168.160.141:5063;received=127.0.0.1;branch=z9hG4bk171-1 >> From: sipp >> <sip:[email protected]:5063>;tag=22740SIPpTag09171 >> >> To: sut <sip:si...@agent> >> Call-ID: 171-22740-192.168.160.141 >> CSeq: 1 INVITE >> Contact: sip:[email protected]:5063 >> Max-Forwards: 69 >> Expires: 180 >> Subject: Performance Test >> Content-Type: application/sdp >> Content-Length: 200 >> >> v=0 >> o=user1 53655765 2353687637 IN IP4 192.168.160.141 >> s=- >> c=IN IP4 192.168.160.141 >> t=0 0 >> m=audio 6684 RTP/AVP 8 101 >> a=rtpmap:8 PCMA/8000 >> a=rtpmap:101 telephone-event/8000 >> a=fmtp:101 0-11,16 >> >> 16:44:31.333183 IP 127.0.0.1.5060 > 127.0.0.1.5061: SIP, length: 765 >> e.....@[email protected] sip:si...@agent SIP/2.0 >> Record-Route: >> <sip:127.0.0.1;lr=on;ftag=22740SIPpTag09171;did=aaf.ae11fa93> >> Via: SIP/2.0/UDP 127.0.0.1;branch=z9hG4bKc109.ba08ceb.0 >> Via: SIP/2.0/UDP >> 192.168.160.141:5063;received=127.0.0.1;branch=z9hG4bk171-1 >> From: sipp >> <sip:[email protected]:5063>;tag=22740SIPpTag09171 >> >> To: sut <sip:si...@agent> >> Call-ID: 171-22740-192.168.160.141 >> CSeq: 1 INVITE >> Contact: sip:[email protected]:5063 >> Max-Forwards: 69 >> Expires: 180 >> Subject: Performance Test >> Content-Type: application/sdp >> Content-Length: 200 >> >> v=0 >> o=user1 53655765 2353687637 IN IP4 192.168.160.141 >> s=- >> c=IN IP4 192.168.160.141 >> t=0 0 >> m=audio 6684 RTP/AVP 8 101 >> a=rtpmap:8 PCMA/8000 >> a=rtpmap:101 telephone-event/8000 >> a=fmtp:101 0-11,16 >> >> 16:44:32.333228 IP 127.0.0.1.5060 > 127.0.0.1.5061: SIP, length: 765 >> e.....@[email protected] sip:si...@agent SIP/2.0 >> Record-Route: >> <sip:127.0.0.1;lr=on;ftag=22740SIPpTag09171;did=aaf.ae11fa93> >> Via: SIP/2.0/UDP 127.0.0.1;branch=z9hG4bKc109.ba08ceb.0 >> Via: SIP/2.0/UDP >> 192.168.160.141:5063;received=127.0.0.1;branch=z9hG4bk171-1 >> From: sipp >> <sip:[email protected]:5063>;tag=22740SIPpTag09171 >> >> To: sut <sip:si...@agent> >> Call-ID: 171-22740-192.168.160.141 >> CSeq: 1 INVITE >> Contact: sip:[email protected]:5063 >> Max-Forwards: 69 >> Expires: 180 >> Subject: Performance Test >> Content-Type: application/sdp >> Content-Length: 200 >> >> v=0 >> o=user1 53655765 2353687637 IN IP4 192.168.160.141 >> s=- >> c=IN IP4 192.168.160.141 >> t=0 0 >> m=audio 6684 RTP/AVP 8 101 >> a=rtpmap:8 PCMA/8000 >> a=rtpmap:101 telephone-event/8000 >> a=fmtp:101 0-11,16 >> >> 16:44:34.337925 IP 127.0.0.1.5060 > 127.0.0.1.5061: SIP, length: 765 >> e.....@[email protected] sip:si...@agent SIP/2.0 >> Record-Route: >> <sip:127.0.0.1;lr=on;ftag=22740SIPpTag09171;did=aaf.ae11fa93> >> Via: SIP/2.0/UDP 127.0.0.1;branch=z9hG4bKc109.ba08ceb.0 >> Via: SIP/2.0/UDP >> 192.168.160.141:5063;received=127.0.0.1;branch=z9hG4bk171-1 >> From: sipp >> <sip:[email protected]:5063>;tag=22740SIPpTag09171 >> >> To: sut <sip:si...@agent> >> Call-ID: 171-22740-192.168.160.141 >> CSeq: 1 INVITE >> Contact: sip:[email protected]:5063 >> Max-Forwards: 69 >> Expires: 180 >> Subject: Performance Test >> Content-Type: application/sdp >> Content-Length: 200 >> >> v=0 >> o=user1 53655765 2353687637 IN IP4 192.168.160.141 >> s=- >> c=IN IP4 192.168.160.141 >> t=0 0 >> m=audio 6684 RTP/AVP 8 101 >> a=rtpmap:8 PCMA/8000 >> a=rtpmap:101 telephone-event/8000 >> a=fmtp:101 0-11,16 >> >> 16:44:34.938729 IP 127.0.0.1.5060 > 127.0.0.1.5062: SIP, length: 765 >> e.....@[email protected] sip:si...@agent SIP/2.0 >> Record-Route: >> <sip:127.0.0.1;lr=on;ftag=22740SIPpTag09171;did=aaf.ae11fa93> >> Via: SIP/2.0/UDP 127.0.0.1;branch=z9hG4bKc109.ba08ceb.1 >> Via: SIP/2.0/UDP >> 192.168.160.141:5063;received=127.0.0.1;branch=z9hG4bk171-1 >> From: sipp >> <sip:[email protected]:5063>;tag=22740SIPpTag09171 >> >> To: sut <sip:si...@agent> >> Call-ID: 171-22740-192.168.160.141 >> CSeq: 1 INVITE >> Contact: sip:[email protected]:5063 >> Max-Forwards: 69 >> Expires: 180 >> Subject: Performance Test >> Content-Type: application/sdp >> Content-Length: 200 >> >> v=0 >> o=user1 53655765 2353687637 IN IP4 192.168.160.141 >> s=- >> c=IN IP4 192.168.160.141 >> t=0 0 >> m=audio 6684 RTP/AVP 8 101 >> a=rtpmap:8 PCMA/8000 >> a=rtpmap:101 telephone-event/8000 >> a=fmtp:101 0-11,16 >> >> 16:44:35.001710 IP 127.0.0.1.5062 > 127.0.0.1.5060: SIP, length: 474 >> e.....@.@.:.................SIP/2.0 180 Ringing >> Via: SIP/2.0/UDP 127.0.0.1;branch=z9hG4bKc109.ba08ceb.1, SIP/2.0/UDP >> 192.168.160.141:5063;received=127.0.0.1;branch=z9hG4bk171-1 >> From: sipp >> <sip:[email protected]:5063>;tag=22740SIPpTag09171 >> >> To: sut <sip:si...@agent>;tag=21199SIPpTag01391 >> Call-ID: 171-22740-192.168.160.141 >> CSeq: 1 INVITE >> Record-Route: >> <sip:127.0.0.1;lr=on;ftag=22740SIPpTag09171;did=aaf.ae11fa93> >> Contact: <sip:192.168.160.141:5062> >> Content-Length: 0 >> >> >> 16:44:35.002835 IP 127.0.0.1.5060 > 127.0.0.1.5063: SIP, length: 422 >> e.....@.@.;!................SIP/2.0 180 Ringing >> Via: SIP/2.0/UDP >> 192.168.160.141:5063;received=127.0.0.1;branch=z9hG4bk171-1 >> From: sipp >> <sip:[email protected]:5063>;tag=22740SIPpTag09171 >> >> To: sut <sip:si...@agent>;tag=21199SIPpTag01391 >> Call-ID: 171-22740-192.168.160.141 >> CSeq: 1 INVITE >> Record-Route: >> <sip:127.0.0.1;lr=on;ftag=22740SIPpTag09171;did=aaf.ae11fa93> >> Contact: <sip:192.168.160.141:5062> >> Content-Length: 0 >> >> >> 16:44:36.409301 IP 127.0.0.1.5061 > 127.0.0.1.5060: SIP, length: 704 >> e.....@.@.:.................SIP/2.0 200 OK >> Via: SIP/2.0/UDP 127.0.0.1;branch=z9hG4bKc109.ba08ceb.0, SIP/2.0/UDP >> 192.168.160.141:5063;received=127.0.0.1;branch=z9hG4bk171-1 >> From: sipp >> <sip:[email protected]:5063>;tag=22740SIPpTag09171 >> >> To: sut <sip:si...@agent>;tag=21152SIPpTag01266 >> Call-ID: 171-22740-192.168.160.141 >> CSeq: 1 INVITE >> Record-Route: >> <sip:127.0.0.1;lr=on;ftag=22740SIPpTag09171;did=aaf.ae11fa93> >> Contact: <sip:192.168.160.141:5061> >> Content-Type: application/sdp >> Content-Length: 200 >> >> v=0 >> o=user1 53655765 2353687637 IN IP4 192.168.160.141 >> s=- >> c=IN IP4 192.168.160.141 >> t=0 0 >> m=audio 7060 RTP/AVP 8 101 >> a=rtpmap:8 PCMA/8000 >> a=rtpmap:101 telephone-event/8000 >> a=fmtp:101 0-11,16 >> >> 16:44:36.909862 IP 127.0.0.1.5061 > 127.0.0.1.5060: SIP, length: 704 >> e.....@.@.:.................SIP/2.0 200 OK >> Via: SIP/2.0/UDP 127.0.0.1;branch=z9hG4bKc109.ba08ceb.0, SIP/2.0/UDP >> 192.168.160.141:5063;received=127.0.0.1;branch=z9hG4bk171-1 >> From: sipp >> <sip:[email protected]:5063>;tag=22740SIPpTag09171 >> >> To: sut <sip:si...@agent>;tag=21152SIPpTag01266 >> Call-ID: 171-22740-192.168.160.141 >> CSeq: 1 INVITE >> Record-Route: >> <sip:127.0.0.1;lr=on;ftag=22740SIPpTag09171;did=aaf.ae11fa93> >> Contact: <sip:192.168.160.141:5061> >> Content-Type: application/sdp >> Content-Length: 200 >> >> v=0 >> o=user1 53655765 2353687637 IN IP4 192.168.160.141 >> s=- >> c=IN IP4 192.168.160.141 >> t=0 0 >> m=audio 7060 RTP/AVP 8 101 >> a=rtpmap:8 PCMA/8000 >> a=rtpmap:101 telephone-event/8000 >> a=fmtp:101 0-11,16 >> >> 16:44:37.911855 IP 127.0.0.1.5061 > 127.0.0.1.5060: SIP, length: 704 >> e.....@.@.:.................SIP/2.0 200 OK >> Via: SIP/2.0/UDP 127.0.0.1;branch=z9hG4bKc109.ba08ceb.0, SIP/2.0/UDP >> 192.168.160.141:5063;received=127.0.0.1;branch=z9hG4bk171-1 >> From: sipp >> <sip:[email protected]:5063>;tag=22740SIPpTag09171 >> >> To: sut <sip:si...@agent>;tag=21152SIPpTag01266 >> Call-ID: 171-22740-192.168.160.141 >> CSeq: 1 INVITE >> Record-Route: >> <sip:127.0.0.1;lr=on;ftag=22740SIPpTag09171;did=aaf.ae11fa93> >> Contact: <sip:192.168.160.141:5061> >> Content-Type: application/sdp >> Content-Length: 200 >> >> v=0 >> o=user1 53655765 2353687637 IN IP4 192.168.160.141 >> s=- >> c=IN IP4 192.168.160.141 >> t=0 0 >> m=audio 7060 RTP/AVP 8 101 >> a=rtpmap:8 PCMA/8000 >> a=rtpmap:101 telephone-event/8000 >> a=fmtp:101 0-11,16 >> >> 16:44:39.912893 IP 127.0.0.1.5061 > 127.0.0.1.5060: SIP, length: 704 >> e.....@.@.:.................SIP/2.0 200 OK >> Via: SIP/2.0/UDP 127.0.0.1;branch=z9hG4bKc109.ba08ceb.0, SIP/2.0/UDP >> 192.168.160.141:5063;received=127.0.0.1;branch=z9hG4bk171-1 >> From: sipp >> <sip:[email protected]:5063>;tag=22740SIPpTag09171 >> >> To: sut <sip:si...@agent>;tag=21152SIPpTag01266 >> Call-ID: 171-22740-192.168.160.141 >> CSeq: 1 INVITE >> Record-Route: >> <sip:127.0.0.1;lr=on;ftag=22740SIPpTag09171;did=aaf.ae11fa93> >> Contact: <sip:192.168.160.141:5061> >> Content-Type: application/sdp >> Content-Length: 200 >> >> v=0 >> o=user1 53655765 2353687637 IN IP4 192.168.160.141 >> s=- >> c=IN IP4 192.168.160.141 >> t=0 0 >> m=audio 7060 RTP/AVP 8 101 >> a=rtpmap:8 PCMA/8000 >> a=rtpmap:101 telephone-event/8000 >> a=fmtp:101 0-11,16 >> >> 16:44:43.915886 IP 127.0.0.1.5061 > 127.0.0.1.5060: SIP, length: 704 >> e.....@.@.:.................SIP/2.0 200 OK >> Via: SIP/2.0/UDP 127.0.0.1;branch=z9hG4bKc109.ba08ceb.0, SIP/2.0/UDP >> 192.168.160.141:5063;received=127.0.0.1;branch=z9hG4bk171-1 >> From: sipp >> <sip:[email protected]:5063>;tag=22740SIPpTag09171 >> >> To: sut <sip:si...@agent>;tag=21152SIPpTag01266 >> Call-ID: 171-22740-192.168.160.141 >> CSeq: 1 INVITE >> Record-Route: >> <sip:127.0.0.1;lr=on;ftag=22740SIPpTag09171;did=aaf.ae11fa93> >> Contact: <sip:192.168.160.141:5061> >> Content-Type: application/sdp >> Content-Length: 200 >> >> v=0 >> o=user1 53655765 2353687637 IN IP4 192.168.160.141 >> s=- >> c=IN IP4 192.168.160.141 >> t=0 0 >> m=audio 7060 RTP/AVP 8 101 >> a=rtpmap:8 PCMA/8000 >> a=rtpmap:101 telephone-event/8000 >> a=fmtp:101 0-11,16 >> >> 16:44:44.611276 IP 127.0.0.1.5062 > 127.0.0.1.5060: SIP, length: 704 >> e.....@.@.:.................SIP/2.0 200 OK >> Via: SIP/2.0/UDP 127.0.0.1;branch=z9hG4bKc109.ba08ceb.1, SIP/2.0/UDP >> 192.168.160.141:5063;received=127.0.0.1;branch=z9hG4bk171-1 >> From: sipp >> <sip:[email protected]:5063>;tag=22740SIPpTag09171 >> >> To: sut <sip:si...@agent>;tag=21199SIPpTag01391 >> Call-ID: 171-22740-192.168.160.141 >> CSeq: 1 INVITE >> Record-Route: >> <sip:127.0.0.1;lr=on;ftag=22740SIPpTag09171;did=aaf.ae11fa93> >> Contact: <sip:192.168.160.141:5062> >> Content-Type: application/sdp >> Content-Length: 200 >> >> v=0 >> o=user1 53655765 2353687637 IN IP4 192.168.160.141 >> s=- >> c=IN IP4 192.168.160.141 >> t=0 0 >> m=audio 7561 RTP/AVP 8 101 >> a=rtpmap:8 PCMA/8000 >> a=rtpmap:101 telephone-event/8000 >> a=fmtp:101 0-11,16 >> >> 16:44:44.612769 IP 127.0.0.1.5060 > 127.0.0.1.5063: SIP, length: 646 >> e.....@.@.:A................SIP/2.0 200 OK >> Via: SIP/2.0/UDP >> 192.168.160.141:5063;received=127.0.0.1;branch=z9hG4bk171-1 >> From: sipp >> <sip:[email protected]:5063>;tag=22740SIPpTag09171 >> >> To: sut <sip:si...@agent>;tag=21199SIPpTag01391 >> Call-ID: 171-22740-192.168.160.141 >> CSeq: 1 INVITE >> Record-Route: >> <sip:127.0.0.1;lr=on;ftag=22740SIPpTag09171;did=aaf.ae11fa93> >> Contact: <sip:127.0.0.1:5062> >> Content-Type: application/sdp >> Content-Length: 200 >> >> v=0 >> o=user1 53655765 2353687637 IN IP4 192.168.160.141 >> s=- >> c=IN IP4 192.168.160.141 >> t=0 0 >> m=audio 7561 RTP/AVP 8 101 >> a=rtpmap:8 PCMA/8000 >> a=rtpmap:101 telephone-event/8000 >> a=fmtp:101 0-11,16 >> >> 16:44:44.622443 IP 127.0.0.1.5063 > 127.0.0.1.5060: SIP, length: 455 >> e.....@.@.;.................ACK sip:127.0.0.1:5062 SIP/2.0 >> Via: SIP/2.0/UDP 192.168.160.141:5063;branch=z9hG4bk171-1 >> From: sipp >> <sip:[email protected]:5063>;tag=22740SIPpTag09171 >> >> To: sut <sip:si...@agent>;tag=21199SIPpTag01391 >> Route: <sip:127.0.0.1;lr=on;ftag=22740SIPpTag09171;did=aaf.ae11fa93> >> Call-ID: 171-22740-192.168.160.141 >> CSeq: 1 INVITE >> Contact: sip:[email protected]:5063 >> Max-Forwards: 70 >> Subject: Performance Test >> Content-Length: 0 >> >> >> 16:44:44.625685 IP 127.0.0.1.5060 > 127.0.0.1.5062: SIP, length: 521 >> e.....@.@.:................%ACK sip:127.0.0.1:5062 SIP/2.0 >> Record-Route: <sip:127.0.0.1;lr=on;ftag=22740SIPpTag09171> >> Via: SIP/2.0/UDP 127.0.0.1;branch=z9hG4bKc109.ba08ceb.3 >> Via: SIP/2.0/UDP >> 192.168.160.141:5063;received=127.0.0.1;branch=z9hG4bk171-1 >> From: sipp >> <sip:[email protected]:5063>;tag=22740SIPpTag09171 >> >> To: sut <sip:si...@agent>;tag=21199SIPpTag01391 >> Call-ID: 171-22740-192.168.160.141 >> CSeq: 1 INVITE >> Contact: sip:[email protected]:5063 >> Max-Forwards: 69 >> Subject: Performance Test >> Content-Length: 0 >> >> >> 16:44:47.678942 IP 127.0.0.1.5063 > 127.0.0.1.5060: SIP, length: 463 >> e.....@.@.;.................BYE sip:127.0.0.1:5062 SIP/2.0 >> Via: SIP/2.0/UDP 192.168.160.141:5063;branch=z9hG4bk171-1 >> From: sipp >> <sip:[email protected]:5063>;tag=22740SIPpTag09171 >> >> To: sut <sip:[email protected]:5060>;tag=21199SIPpTag01391 >> Route: <sip:127.0.0.1;lr=on;ftag=22740SIPpTag09171;did=aaf.ae11fa93> >> Call-ID: 171-22740-192.168.160.141 >> CSeq: 2 BYE >> Contact: sip:[email protected]:5063 >> Max-Forwards: 70 >> Subject: Performance Test >> Content-Length: 0 >> >> >> 16:44:47.682771 IP 127.0.0.1.5060 > 127.0.0.1.5062: SIP, length: 530 >> e.....@.@.:.................BYE sip:127.0.0.1:5062 SIP/2.0 >> Record-Route: <sip:127.0.0.1;lr=on;ftag=22740SIPpTag09171> >> Via: SIP/2.0/UDP 127.0.0.1;branch=z9hG4bK9109.f38911a7.0 >> Via: SIP/2.0/UDP >> 192.168.160.141:5063;received=127.0.0.1;branch=z9hG4bk171-1 >> From: sipp >> <sip:[email protected]:5063>;tag=22740SIPpTag09171 >> >> To: sut <sip:[email protected]:5060>;tag=21199SIPpTag01391 >> Call-ID: 171-22740-192.168.160.141 >> CSeq: 2 BYE >> Contact: sip:[email protected]:5063 >> Max-Forwards: 69 >> Subject: Performance Test >> Content-Length: 0 >> >> >> 16:44:47.694205 IP 127.0.0.1.5062 > 127.0.0.1.5060: SIP, length: 401 >> e.....@.@.;>................SIP/2.0 200 OK >> Via: SIP/2.0/UDP 127.0.0.1;branch=z9hG4bK9109.f38911a7.0, SIP/2.0/UDP >> 192.168.160.141:5063;received=127.0.0.1;branch=z9hG4bk171-1 >> From: sipp >> <sip:[email protected]:5063>;tag=22740SIPpTag09171 >> >> To: sut <sip:[email protected]:5060>;tag=21199SIPpTag01391 >> Call-ID: 171-22740-192.168.160.141 >> CSeq: 2 BYE >> Contact: <sip:192.168.160.141:5062> >> Content-Length: 0 >> >> >> 16:44:47.695965 IP 127.0.0.1.5060 > 127.0.0.1.5063: SIP, length: 348 >> e.....@.@.;k.............d.wSIP/2.0 200 OK >> Via: SIP/2.0/UDP >> 192.168.160.141:5063;received=127.0.0.1;branch=z9hG4bk171-1 >> From: sipp >> <sip:[email protected]:5063>;tag=22740SIPpTag09171 >> >> To: sut <sip:[email protected]:5060>;tag=21199SIPpTag01391 >> Call-ID: 171-22740-192.168.160.141 >> CSeq: 2 BYE >> Contact: <sip:192.168.160.141:5062> >> Content-Length: 0 >> >> >> 16:44:47.917129 IP 127.0.0.1.5061 > 127.0.0.1.5060: SIP, length: 704 >> e.....@.@.:.................SIP/2.0 200 OK >> Via: SIP/2.0/UDP 127.0.0.1;branch=z9hG4bKc109.ba08ceb.0, SIP/2.0/UDP >> 192.168.160.141:5063;received=127.0.0.1;branch=z9hG4bk171-1 >> From: sipp >> <sip:[email protected]:5063>;tag=22740SIPpTag09171 >> >> To: sut <sip:si...@agent>;tag=21152SIPpTag01266 >> Call-ID: 171-22740-192.168.160.141 >> CSeq: 1 INVITE >> Record-Route: >> <sip:127.0.0.1;lr=on;ftag=22740SIPpTag09171;did=aaf.ae11fa93> >> Contact: <sip:192.168.160.141:5061> >> Content-Type: application/sdp >> Content-Length: 200 >> >> v=0 >> o=user1 53655765 2353687637 IN IP4 192.168.160.141 >> s=- >> c=IN IP4 192.168.160.141 >> t=0 0 >> m=audio 7060 RTP/AVP 8 101 >> a=rtpmap:8 PCMA/8000 >> a=rtpmap:101 telephone-event/8000 >> a=fmtp:101 0-11,16 >> >> 16:44:47.918042 IP 127.0.0.1.5060 > 127.0.0.1.5063: SIP, length: 646 >> e.....@.@.:A................SIP/2.0 200 OK >> Via: SIP/2.0/UDP >> 192.168.160.141:5063;received=127.0.0.1;branch=z9hG4bk171-1 >> From: sipp >> <sip:[email protected]:5063>;tag=22740SIPpTag09171 >> >> To: sut <sip:si...@agent>;tag=21152SIPpTag01266 >> Call-ID: 171-22740-192.168.160.141 >> CSeq: 1 INVITE >> Record-Route: >> <sip:127.0.0.1;lr=on;ftag=22740SIPpTag09171;did=aaf.ae11fa93> >> Contact: <sip:127.0.0.1:5061> >> Content-Type: application/sdp >> Content-Length: 200 >> >> v=0 >> o=user1 53655765 2353687637 IN IP4 192.168.160.141 >> s=- >> c=IN IP4 192.168.160.141 >> t=0 0 >> m=audio 7060 RTP/AVP 8 101 >> a=rtpmap:8 PCMA/8000 >> a=rtpmap:101 telephone-event/8000 >> a=fmtp:101 0-11,16 >> >> 16:44:47.918855 IP 127.0.0.1.5063 > 127.0.0.1.5060: SIP, length: 455 >> e.....@.@.;.................ACK sip:127.0.0.1:5061 SIP/2.0 >> Via: SIP/2.0/UDP 192.168.160.141:5063;branch=z9hG4bk171-1 >> From: sipp >> <sip:[email protected]:5063>;tag=22740SIPpTag09171 >> >> To: sut <sip:si...@agent>;tag=21152SIPpTag01266 >> Route: <sip:127.0.0.1;lr=on;ftag=22740SIPpTag09171;did=aaf.ae11fa93> >> Call-ID: 171-22740-192.168.160.141 >> CSeq: 1 INVITE >> Contact: sip:[email protected]:5063 >> Max-Forwards: 70 >> Subject: Performance Test >> Content-Length: 0 >> >> >> 16:44:47.920021 IP 127.0.0.1.5060 > 127.0.0.1.5061: SIP, length: 521 >> e.....@.@.:................%ACK sip:127.0.0.1:5061 SIP/2.0 >> Record-Route: <sip:127.0.0.1;lr=on;ftag=22740SIPpTag09171> >> Via: SIP/2.0/UDP 127.0.0.1;branch=z9hG4bKc109.ba08ceb.3 >> Via: SIP/2.0/UDP >> 192.168.160.141:5063;received=127.0.0.1;branch=z9hG4bk171-1 >> From: sipp >> <sip:[email protected]:5063>;tag=22740SIPpTag09171 >> >> To: sut <sip:si...@agent>;tag=21152SIPpTag01266 >> Call-ID: 171-22740-192.168.160.141 >> CSeq: 1 INVITE >> Contact: sip:[email protected]:5063 >> Max-Forwards: 69 >> Subject: Performance Test >> Content-Length: 0 >> >> >> 16:44:58.598262 IP 127.0.0.1.5063 > 127.0.0.1.5060: SIP, length: 463 >> e.....@.@.;.................BYE sip:127.0.0.1:5061 SIP/2.0 >> Via: SIP/2.0/UDP 192.168.160.141:5063;branch=z9hG4bk171-1 >> From: sipp >> <sip:[email protected]:5063>;tag=22740SIPpTag09171 >> >> To: sut <sip:[email protected]:5060>;tag=21152SIPpTag01266 >> Route: <sip:127.0.0.1;lr=on;ftag=22740SIPpTag09171;did=aaf.ae11fa93> >> Call-ID: 171-22740-192.168.160.141 >> CSeq: 2 BYE >> Contact: sip:[email protected]:5063 >> Max-Forwards: 70 >> Subject: Performance Test >> Content-Length: 0 >> >> >> 16:44:58.599586 IP 127.0.0.1.5060 > 127.0.0.1.5061: SIP, length: 530 >> e.....@.@.:.................BYE sip:127.0.0.1:5061 SIP/2.0 >> Record-Route: <sip:127.0.0.1;lr=on;ftag=22740SIPpTag09171> >> Via: SIP/2.0/UDP 127.0.0.1;branch=z9hG4bK9109.048911a7.0 >> Via: SIP/2.0/UDP >> 192.168.160.141:5063;received=127.0.0.1;branch=z9hG4bk171-1 >> From: sipp >> <sip:[email protected]:5063>;tag=22740SIPpTag09171 >> >> To: sut <sip:[email protected]:5060>;tag=21152SIPpTag01266 >> Call-ID: 171-22740-192.168.160.141 >> CSeq: 2 BYE >> Contact: sip:[email protected]:5063 >> Max-Forwards: 69 >> Subject: Performance Test >> Content-Length: 0 >> >> >> 16:44:58.611193 IP 127.0.0.1.5061 > 127.0.0.1.5060: SIP, length: 401 >> e.....@.@.;>................SIP/2.0 200 OK >> Via: SIP/2.0/UDP 127.0.0.1;branch=z9hG4bK9109.048911a7.0, SIP/2.0/UDP >> 192.168.160.141:5063;received=127.0.0.1;branch=z9hG4bk171-1 >> From: sipp >> <sip:[email protected]:5063>;tag=22740SIPpTag09171 >> >> To: sut <sip:[email protected]:5060>;tag=21152SIPpTag01266 >> Call-ID: 171-22740-192.168.160.141 >> CSeq: 2 BYE >> Contact: <sip:192.168.160.141:5061> >> Content-Length: 0 >> >> >> 16:44:58.612182 IP 127.0.0.1.5060 > 127.0.0.1.5063: SIP, length: 348 >> e.....@.@.;k.............d.wSIP/2.0 200 OK >> Via: SIP/2.0/UDP >> 192.168.160.141:5063;received=127.0.0.1;branch=z9hG4bk171-1 >> From: sipp >> <sip:[email protected]:5063>;tag=22740SIPpTag09171 >> >> To: sut <sip:[email protected]:5060>;tag=21152SIPpTag01266 >> Call-ID: 171-22740-192.168.160.141 >> CSeq: 2 BYE >> Contact: <sip:192.168.160.141:5061> >> Content-Length: 0 >> >> >> >> _______________________________________________ >> Devel mailing list >> [email protected] >> http://lists.kamailio.org/cgi-bin/mailman/listinfo/devel > _______________________________________________ Devel mailing list [email protected] http://lists.kamailio.org/cgi-bin/mailman/listinfo/devel
