and it gives following error log at IMS bench side:
2014-10-19 07:39:39.504: C:'12-5099@192.168.2.11' UNEXP-Cont(2) expecting '200'
rsp, rcv 'SIP/2.0 408 Request Timeout^M
Via: SIP/2.0/UDP 192.168.2.11:9440;branch=z9hG4bK-5099-12-4^M
From: "subs002440" <sip:subs002...@open-ims.test>;tag=5099SIPpTag0012^M
To: "subs000233" <sip:subs000...@open-ims.test>;tag=5099SIPpTag0113^M
Call-ID: 12-5099@192.168.2.11^M
CSeq: 2 BYE^M
Server: OpenSIPS (1.9.2-notls (x86_64/linux))^M
Content-Length: 0^M
^M
Somehow 200 OK received at IMS bench side is not accepted and it remains in 200
expecting state although it receives 200 OK.
Windows Posta'dan gönderildi
Kimden: kaan.dan...@gmail.com
Gönderme tarihi: 19 Ekim 2014 Pazar 20:21
Kime: Volkan KUMBASAR
Bilgi: sipp-users@lists.sourceforge.net; Gunes Kurt; Ibrahim Hokelek,
(BİLGEM-UEKAE)
Hi Volkan,
With OpenSIPS scripting I am able to send messages to correct IMS node,
although it seems there is truncated route problem.
But 200 OK, ACK and BYE messages are sent more than once from IMS bench.
What can be reason for this ?
Below you can see unsuccesful and succesful scenarios.
Unsuccesful scenario
===================
No. Time Source Destination Protocol Info
4184 33.561877 192.168.2.11 192.168.2.141 SIP/SDP
Request: INVITE sip:subs000...@open-ims.test, with session description
4185 33.568347 192.168.2.141 192.168.2.11 SIP
Status: 100 Giving a try
4186 33.569632 192.168.2.141 192.168.2.5 SIP/SDP
Request: INVITE sip:subs000...@open-ims.test, with session description
4187 33.623958 192.168.2.5 192.168.2.141 SIP
Status: 100 trying -- your call is important to us
4188 33.704902 192.168.2.5 192.168.2.141 SIP/SDP
Request: INVITE sip:subs000233@192.168.2.11:7233, with session description
4189 33.707290 192.168.2.141 192.168.2.5 SIP
Status: 100 Giving a try
4191 33.707781 192.168.2.141 192.168.2.11 SIP/SDP
Request: INVITE sip:subs000233@192.168.2.11:7233, with session description
4192 33.708110 192.168.2.11 192.168.2.141 SIP
Status: 180 Ringing
4193 33.709311 192.168.2.141 192.168.2.5 SIP
Status: 180 Ringing
4199 33.779809 192.168.2.5 192.168.2.141 SIP
Status: 180 Ringing
4200 33.780385 192.168.2.141 192.168.2.11 SIP
Status: 180 Ringing
4704 38.573437 192.168.2.11 192.168.2.141 SIP/SDP
Status: 200 OK, with session description
4705 38.577606 192.168.2.141 192.168.2.5 SIP/SDP
Status: 200 OK, with session description
4706 38.657685 192.168.2.5 192.168.2.141 SIP/SDP
Status: 200 OK, with session description
4707 38.659102 192.168.2.141 192.168.2.11 SIP/SDP
Status: 200 OK, with session description
4708 38.659372 192.168.2.11 192.168.2.141 SIP
Request: ACK sip:subs000233@192.168.2.11:7233;transport=UDP
4709 38.660744 192.168.2.141 192.168.2.5 SIP
Request: ACK sip:subs000233@192.168.2.11:7233;transport=UDP
4710 38.699408 192.168.2.5 192.168.2.141 SIP
Request: ACK sip:subs000233@192.168.2.11:7233;transport=UDP
4711 38.700960 192.168.2.141 192.168.2.11 SIP
Request: ACK sip:subs000233@192.168.2.11:7233;transport=UDP
4733 39.083414 192.168.2.11 192.168.2.141 SIP/SDP
Status: 200 OK, with session description
4734 39.088023 192.168.2.141 192.168.2.5 SIP/SDP
Status: 200 OK, with session description
4743 39.159362 192.168.2.5 192.168.2.141 SIP/SDP
Status: 200 OK, with session description
4744 39.160384 192.168.2.141 192.168.2.11 SIP/SDP
Status: 200 OK, with session description
4745 39.160385 192.168.2.11 192.168.2.141 SIP
Request: ACK sip:subs000233@192.168.2.11:7233;transport=UDP
4746 39.161709 192.168.2.141 192.168.2.5 SIP
Request: ACK sip:subs000233@192.168.2.11:7233;transport=UDP
4747 39.205534 192.168.2.5 192.168.2.141 SIP
Request: ACK sip:subs000233@192.168.2.11:7233;transport=UDP
4748 39.206673 192.168.2.141 192.168.2.11 SIP
Request: ACK sip:subs000233@192.168.2.11:7233;transport=UDP
4767 40.091534 192.168.2.11 192.168.2.141 SIP/SDP
Status: 200 OK, with session description
4768 40.093989 192.168.2.141 192.168.2.5 SIP/SDP
Status: 200 OK, with session description
4769 40.171695 192.168.2.5 192.168.2.141 SIP/SDP
Status: 200 OK, with session description
4770 40.173129 192.168.2.141 192.168.2.11 SIP/SDP
Status: 200 OK, with session description
4771 40.173129 192.168.2.11 192.168.2.141 SIP
Request: ACK sip:subs000233@192.168.2.11:7233;transport=UDP
4772 40.174084 192.168.2.141 192.168.2.5 SIP
Request: ACK sip:subs000233@192.168.2.11:7233;transport=UDP
4773 40.214572 192.168.2.5 192.168.2.141 SIP
Request: ACK sip:subs000233@192.168.2.11:7233;transport=UDP
4774 40.215756 192.168.2.141 192.168.2.11 SIP
Request: ACK sip:subs000233@192.168.2.11:7233;transport=UDP
5502 42.098294 192.168.2.11 192.168.2.141 SIP/SDP
Status: 200 OK, with session description
5503 42.100903 192.168.2.141 192.168.2.5 SIP/SDP
Status: 200 OK, with session description
5504 42.176642 192.168.2.5 192.168.2.141 SIP/SDP
Status: 200 OK, with session description
5505 42.177724 192.168.2.141 192.168.2.11 SIP/SDP
Status: 200 OK, with session description
5506 42.177725 192.168.2.11 192.168.2.141 SIP
Request: ACK sip:subs000233@192.168.2.11:7233;transport=UDP
5507 42.179758 192.168.2.141 192.168.2.5 SIP
Request: ACK sip:subs000233@192.168.2.11:7233;transport=UDP
5508 42.227497 192.168.2.5 192.168.2.141 SIP
Request: ACK sip:subs000233@192.168.2.11:7233;transport=UDP
5509 42.228623 192.168.2.141 192.168.2.11 SIP
Request: ACK sip:subs000233@192.168.2.11:7233;transport=UDP
5633 46.106052 192.168.2.11 192.168.2.141 SIP/SDP
Status: 200 OK, with session description
6433 50.112541 192.168.2.11 192.168.2.141 SIP/SDP
Status: 200 OK, with session description
7015 54.114420 192.168.2.11 192.168.2.141 SIP/SDP
Status: 200 OK, with session description
7574 58.124284 192.168.2.11 192.168.2.141 SIP/SDP
Status: 200 OK, with session description
7575 58.148345 192.168.2.11 192.168.2.141 SIP
Request: BYE sip:subs000233@192.168.2.11:7233;transport=UDP
7576 58.150336 192.168.2.141 192.168.2.5 SIP
Request: BYE sip:subs000233@192.168.2.11:7233;transport=UDP
7584 58.215542 192.168.2.5 192.168.2.141 SIP
Request: BYE sip:subs000233@192.168.2.11:7233;transport=UDP
7585 58.217673 192.168.2.141 192.168.2.11 SIP
Request: BYE sip:subs000233@192.168.2.11:7233;transport=UDP
7591 58.649930 192.168.2.11 192.168.2.141 SIP
Request: BYE sip:subs000233@192.168.2.11:7233;transport=UDP
7592 58.675945 192.168.2.5 192.168.2.141 SIP
Request: BYE sip:subs000233@192.168.2.11:7233;transport=UDP
7593 58.705736 192.168.2.141 192.168.2.5 SIP
Request: BYE sip:subs000233@192.168.2.11:7233;transport=UDP
7594 58.705916 192.168.2.141 192.168.2.11 SIP
Request: BYE sip:subs000233@192.168.2.11:7233;transport=UDP
7616 59.651455 192.168.2.11 192.168.2.141 SIP
Request: BYE sip:subs000233@192.168.2.11:7233;transport=UDP
7617 59.676531 192.168.2.5 192.168.2.141 SIP
Request: BYE sip:subs000233@192.168.2.11:7233;transport=UDP
7621 59.804890 192.168.2.141 192.168.2.5 SIP
Request: BYE sip:subs000233@192.168.2.11:7233;transport=UDP
7622 59.804892 192.168.2.141 192.168.2.11 SIP
Request: BYE sip:subs000233@192.168.2.11:7233;transport=UDP
7929 61.652761 192.168.2.11 192.168.2.141 SIP
Request: BYE sip:subs000233@192.168.2.11:7233;transport=UDP
7930 61.675803 192.168.2.5 192.168.2.141 SIP
Request: BYE sip:subs000233@192.168.2.11:7233;transport=UDP
7942 62.029256 192.168.2.141 192.168.2.5 SIP
Request: BYE sip:subs000233@192.168.2.11:7233;transport=UDP
7943 62.029526 192.168.2.141 192.168.2.11 SIP
Request: BYE sip:subs000233@192.168.2.11:7233;transport=UDP
7944 62.135168 192.168.2.11 192.168.2.141 SIP/SDP
Status: 200 OK, with session description
7951 63.650261 192.168.2.141 192.168.2.11 SIP
Status: 408 Request Timeout
7952 63.650575 192.168.2.141 192.168.2.5 SIP
Status: 408 Request Timeout
7954 63.669734 192.168.2.5 192.168.2.141 SIP
Status: 408 Request Timeout
7967 65.656863 192.168.2.11 192.168.2.141 SIP
Request: BYE sip:subs000233@192.168.2.11:7233;transport=UDP
7968 65.659895 192.168.2.141 192.168.2.11 SIP
Status: 408 Request Timeout
7986 66.145280 192.168.2.11 192.168.2.141 SIP/SDP
Status: 200 OK, with session description
8726 69.660979 192.168.2.11 192.168.2.141 SIP
Request: BYE sip:subs000233@192.168.2.11:7233;transport=UDP
8727 69.664354 192.168.2.141 192.168.2.5 SIP
Request: BYE sip:subs000233@192.168.2.11:7233;transport=UDP
8729 69.746630 192.168.2.5 192.168.2.141 SIP
Request: BYE sip:subs000233@192.168.2.11:7233;transport=UDP
8730 69.748521 192.168.2.141 192.168.2.11 SIP
Request: BYE sip:subs000233@192.168.2.11:7233;transport=UDP
8738 70.183413 192.168.2.141 192.168.2.5 SIP
Request: BYE sip:subs000233@192.168.2.11:7233;transport=UDP
8739 70.238765 192.168.2.5 192.168.2.141 SIP
Request: BYE sip:subs000233@192.168.2.11:7233;transport=UDP
8740 70.284864 192.168.2.141 192.168.2.11 SIP
Request: BYE sip:subs000233@192.168.2.11:7233;transport=UDP
8744 71.238532 192.168.2.5 192.168.2.141 SIP
Request: BYE sip:subs000233@192.168.2.11:7233;transport=UDP
8745 71.293687 192.168.2.141 192.168.2.5 SIP
Request: BYE sip:subs000233@192.168.2.11:7233;transport=UDP
8746 71.395602 192.168.2.141 192.168.2.11 SIP
Request: BYE sip:subs000233@192.168.2.11:7233;transport=UDP
9429 73.238296 192.168.2.5 192.168.2.141 SIP
Request: BYE sip:subs000233@192.168.2.11:7233;transport=UDP
9431 73.520599 192.168.2.141 192.168.2.5 SIP
Request: BYE sip:subs000233@192.168.2.11:7233;transport=UDP
9434 73.621659 192.168.2.141 192.168.2.11 SIP
Request: BYE sip:subs000233@192.168.2.11:7233;transport=UDP
9436 73.668693 192.168.2.11 192.168.2.141 SIP
Request: BYE sip:subs000233@192.168.2.11:7233;transport=UDP
9451 74.732878 192.168.2.141 192.168.2.11 SIP
Status: 408 Request Timeout
9452 75.724162 192.168.2.141 192.168.2.5 SIP
Status: 408 Request Timeout
9453 75.734353 192.168.2.5 192.168.2.141 SIP
Status: 408 Request Timeout
9778 77.678617 192.168.2.11 192.168.2.141 SIP
Request: BYE sip:subs000233@192.168.2.11:7233;transport=UDP
9779 77.682733 192.168.2.141 192.168.2.11 SIP
Status: 408 Request Timeout
9850 81.681704 192.168.2.11 192.168.2.141 SIP
Request: BYE sip:subs000233@192.168.2.11:7233;transport=UDP
10493 81.708817 192.168.2.141 192.168.2.5 SIP
Request: BYE sip:subs000233@192.168.2.11:7233;transport=UDP
10495 81.801249 192.168.2.5 192.168.2.141 SIP
Request: BYE sip:subs000233@192.168.2.11:7233;transport=UDP
10496 81.802852 192.168.2.141 192.168.2.11 SIP
Request: BYE sip:subs000233@192.168.2.11:7233;transport=UDP
10513 82.238889 192.168.2.5 192.168.2.141 SIP
Request: BYE sip:subs000233@192.168.2.11:7233;transport=UDP
10514 82.290788 192.168.2.141 192.168.2.5 SIP
Request: BYE sip:subs000233@192.168.2.11:7233;transport=UDP
10515 82.392127 192.168.2.141 192.168.2.11 SIP
Request: BYE sip:subs000233@192.168.2.11:7233;transport=UDP
10521 83.238567 192.168.2.5 192.168.2.141 SIP
Request: BYE sip:subs000233@192.168.2.11:7233;transport=UDP
10524 83.402479 192.168.2.141 192.168.2.5 SIP
Request: BYE sip:subs000233@192.168.2.11:7233;transport=UDP
10525 83.503577 192.168.2.141 192.168.2.11 SIP
Request: BYE sip:subs000233@192.168.2.11:7233;transport=UDP
10545 85.238803 192.168.2.5 192.168.2.141 SIP
Request: BYE sip:subs000233@192.168.2.11:7233;transport=UDP
10550 85.608875 192.168.2.141 192.168.2.5 SIP
Request: BYE sip:subs000233@192.168.2.11:7233;transport=UDP
10551 85.692074 192.168.2.11 192.168.2.141 SIP
Request: BYE sip:subs000233@192.168.2.11:7233;transport=UDP
10552 85.709136 192.168.2.141 192.168.2.11 SIP
Request: BYE sip:subs000233@192.168.2.11:7233;transport=UDP
10558 86.821440 192.168.2.141 192.168.2.11 SIP
Status: 408 Request Timeout
11224 87.830878 192.168.2.141 192.168.2.5 SIP
Status: 408 Request Timeout
11225 87.835884 192.168.2.5 192.168.2.141 SIP
Status: 408 Request Timeout
Successful scenario
===================
No. Time Source Destination Protocol Info
4207 70.097183 192.168.2.11 192.168.2.141 SIP/SDP
Request: INVITE sip:subs002...@open-ims.test, with session description
4208 70.097882 192.168.2.141 192.168.2.11 SIP
Status: 100 Giving a try
4209 70.098031 192.168.2.141 192.168.2.3 SIP/SDP
Request: INVITE sip:subs002...@open-ims.test, with session description
4210 70.106394 192.168.2.3 192.168.2.141 SIP
Status: 100 trying -- your call is important to us
4213 70.117344 192.168.2.3 192.168.2.141 SIP/SDP
Request: INVITE sip:subs002737@192.168.2.11:9737, with session description
4216 70.117822 192.168.2.141 192.168.2.3 SIP
Status: 100 Giving a try
4218 70.117825 192.168.2.141 192.168.2.11 SIP/SDP
Request: INVITE sip:subs002737@192.168.2.11:9737, with session description
4219 70.118640 192.168.2.11 192.168.2.141 SIP
Status: 180 Ringing
4220 70.118641 192.168.2.141 192.168.2.3 SIP
Status: 180 Ringing
4221 70.125886 192.168.2.3 192.168.2.141 SIP
Status: 180 Ringing
4222 70.126184 192.168.2.141 192.168.2.11 SIP
Status: 180 Ringing
4497 75.158391 192.168.2.11 192.168.2.141 SIP/SDP
Status: 200 OK, with session description
4498 75.158658 192.168.2.141 192.168.2.3 SIP/SDP
Status: 200 OK, with session description
4499 75.168751 192.168.2.3 192.168.2.141 SIP/SDP
Status: 200 OK, with session description
4500 75.169221 192.168.2.141 192.168.2.11 SIP/SDP
Status: 200 OK, with session description
4501 75.169321 192.168.2.11 192.168.2.141 SIP
Request: ACK sip:subs002737@192.168.2.11:9737;transport=UDP
4502 75.170059 192.168.2.141 192.168.2.3 SIP
Request: ACK sip:subs002737@192.168.2.11:9737;transport=UDP
4503 75.174943 192.168.2.3 192.168.2.141 SIP
Request: ACK sip:subs002737@192.168.2.11:9737;transport=UDP
4504 75.176254 192.168.2.141 192.168.2.11 SIP
Request: ACK sip:subs002737@192.168.2.11:9737;transport=UDP
5329 85.048052 192.168.2.11 192.168.2.141 SIP
Request: BYE sip:subs002737@192.168.2.11:9737;transport=UDP
5330 85.048527 192.168.2.141 192.168.2.3 SIP
Request: BYE sip:subs002737@192.168.2.11:9737;transport=UDP
5331 85.053287 192.168.2.3 192.168.2.141 SIP
Request: BYE sip:subs002737@192.168.2.11:9737;transport=UDP
5332 85.053970 192.168.2.141 192.168.2.11 SIP
Request: BYE sip:subs002737@192.168.2.11:9737;transport=UDP
5333 85.054216 192.168.2.11 192.168.2.141 SIP
Status: 200 OK
5334 85.054346 192.168.2.141 192.168.2.3 SIP
Status: 200 OK
5335 85.058731 192.168.2.3 192.168.2.141 SIP
Status: 200 OK
5336 85.059000 192.168.2.141 192.168.2.11 SIP
Status: 200 OK
Thanks
Windows Posta'dan gönderildi
Kimden: Volkan KUMBASAR
Gönderme tarihi: 19 Ekim 2014 Pazar 19:31
Kime: kaan.dan...@gmail.com
Bilgi: sipp-users@lists.sourceforge.net; Gunes Kurt; Ibrahim Hokelek,
(BİLGEM-UEKAE)
According to the trace msg, it is a wireshark issue.
On 19 Oct 2014, at 19:18, kaan.dan...@gmail.com<mailto:kaan.dan...@gmail.com>
wrote:
and this is the last 200 OK received at IMS bench side at messages.log :
Normally I expect same routes in the ACK message:
----------------------------------------------- 2014-10-19 07:39:14.513
UDP message received: [IP4: 192.168.2.11:9440]
SIP/2.0 200 OK^M
Via: SIP/2.0/UDP 192.168.2.11:9440;branch=z9hG4bK-5099-12-4^M
Record-Route: <sip:192.168.2.141;lr;ftag=5099SIPpTag0012>^M
Record-Route: <sip:m...@pcscf2.open-ims.test:4060;lr>^M
Record-Route: <sip:m...@scscf.open-ims.test:6060;lr>^M
Record-Route: <sip:m...@scscf.open-ims.test:6060;lr>^M
Record-Route: <sip:m...@pcscf2.open-ims.test:4060;lr>^M
Record-Route: <sip:192.168.2.141;lr;ftag=5099SIPpTag0012>^M
From: "subs002440" <sip:subs002...@open-ims.test>;tag=5099SIPpTag0012^M
To: "subs000233" <sip:subs000...@open-ims.test>;tag=5099SIPpTag0113^M
Call-ID: 12-5099@192.168.2.11^M<mailto:12-5099@192.168.2.11^M>
CSeq: 1 INVITE^M
Contact: <sip:subs000233@192.168.2.11:7233;transport=UDP>^M
Content-Type: application/sdp^M
Content-Length: 151^M
P-Asserted-Identity: <sip:subs000...@open-ims.test>^M
^M
v=0^M
o=user1 53655765 2353687637 IN IP4 192.168.2.11^M
s=-^M
c=IN IP4 127.0.0.1^M
t=0 0^M
m=audio 35470 RTP/AVP 0^M
a=rtpmap:0 PCMU/8000^M
a=nortpproxy:yes^M
Windows Posta'dan gönderildi
Kimden: kaan.dan...@gmail.com<mailto:kaan.dan...@gmail.com>
Gönderme tarihi: 19 Ekim 2014 Pazar 19:10
Kime: Volkan KUMBASAR
Bilgi:
sipp-users@lists.sourceforge.net<mailto:sipp-users@lists.sourceforge.net>;
Gunes Kurt; Ibrahim Hokelek, (BİLGEM-UEKAE)
Hi Volkan,
from wireshark
No. Time Source Destination Protocol Info
5506 42.177725 192.168.2.11 192.168.2.141 SIP
Request: ACK sip:subs000233@192.168.2.11:7233;transport=UDP
Frame 5506 (637 bytes on wire, 637 bytes captured)
Ethernet II, Src: Vmware_d2:6a:2a (00:0c:29:d2:6a:2a), Dst: Vmware_22:e0:4c
(00:0c:29:22:e0:4c)
Internet Protocol, Src: 192.168.2.11 (192.168.2.11), Dst: 192.168.2.141
(192.168.2.141)
User Datagram Protocol, Src Port: 9440 (9440), Dst Port: dsmeter_iatc (4060)
Source port: 9440 (9440)
Destination port: dsmeter_iatc (4060)
Length: 603
Checksum: 0x6e48 [correct]
Session Initiation Protocol
Request-Line: ACK sip:subs000233@192.168.2.11:7233;transport=UDP SIP/2.0
Message Header
Via: SIP/2.0/UDP 192.168.2.11:9440;branch=z9hG4bK-5099-12-4
Max-Forwards: 10
[truncated] Route: <sip:192.168.2.141;lr;ftag=5099SIPpTag0012>,
<sip:m...@pcscf2.open-ims.test:4060;lr>,
<sip:m...@scscf.open-ims.test:6060;lr>, <sip:m...@scscf.open-ims.test:6060;lr>,
<sip:m...@pcscf2.open-ims.test:4060;lr>,<sip:192.168.2.141;lr
From: "subs002440" <sip:subs002...@open-ims.test>;tag=5099SIPpTag0012
To: "subs000233" <sip:subs000...@open-ims.test>;tag=5099SIPpTag0113
Call-ID: 12-5099@192.168.2.11<mailto:12-5099@192.168.2.11>
CSeq: 1 ACK
Content-Length: 0
from messages.log , since the log file is big I am just sending the related
part . If you need I can send the complete file.
----------------------------------------------- 2014-10-19 07:39:14.513
UDP message sent: [IP4: 192.168.2.11:9440]
ACK sip:subs000233@192.168.2.11:7233;transport=UDP SIP/2.0^M
Via: SIP/2.0/UDP 192.168.2.11:9440;branch=z9hG4bK-5099-12-4^M
Max-Forwards: 10^M
Route: <sip:192.168.2.141;lr;ftag=5099SIPpTag0012>,
<sip:m...@pcscf2.open-ims.test:4060;lr>,
<sip:m...@scscf.open-ims.test:6060;lr>, <sip:m...@scscf.open-ims.test:6060;lr>,
<sip:m...@pcscf2.open-ims.test:4060;lr>,<sip:192.168.2.141;lr;ftag=5099SIPpTag0012>^M
From: "subs002440" <sip:subs002...@open-ims.test>;tag=5099SIPpTag0012^M
To: "subs000233" <sip:subs000...@open-ims.test>;tag=5099SIPpTag0113^M
Call-ID: 12-5099@192.168.2.11^M<mailto:12-5099@192.168.2.11^M>
CSeq: 1 ACK^M
Content-Length: 0^M
^M
Thanks
Windows Posta'dan gönderildi
Kimden: Volkan KUMBASAR
Gönderme tarihi: 19 Ekim 2014 Pazar 18:32
Kime: kaan.dan...@gmail.com<mailto:kaan.dan...@gmail.com>
Bilgi:
sipp-users@lists.sourceforge.net<mailto:sipp-users@lists.sourceforge.net>;
Gunes Kurt; Ibrahim Hokelek, (BİLGEM-UEKAE)
Could you please provide sipp’s trace message too?
-trace_msg : Displays sent and received SIP messages in <scenario file
name>_<pid>_messages.log
On 19 Oct 2014, at 17:55,
kaan.dan...@gmail.com<mailto:kaan.dan...@gmail.com><mailto:kaan.dan...@gmail.com>
wrote:
Hi all,
I am building a testbed with IMS-Bench - OpenSIPS - OpenIMS .
In the call scenario, I am building an ACK message and sending it from IMS
bench to OpenSIPS.
But in the ACK message from IMS bench to OpenSIPS, route part is truncated .
Related part of the script and wireshark log of ACK message is below.
It seems a limitation in IMS Bench. Are there any workaround for this
limitation?
Kind regards,
Kaan
related part of ims bench ims_uac.xml script
==================================
<!-- By adding rrs="true" (Record Route Sets), the route sets are -->
<!-- saved and used for following messages sent. -->
<recv response="200" rrs="true">
</recv>
<send>
<![CDATA[
ACK [next_url] SIP/2.0
[last_Via:]
Max-Forwards: 70
[routes:]
From: "[field0]" <sip:[field0]@[field1]>;tag=[pid]SIPpTag00[call_number]
[last_To:]
Call-ID: [call_id]
CSeq: 1 ACK
Content-Length: 0
]]>
</send>
ACK from IMS bench to OpenSIPS
=====================
No. Time Source Destination Protocol Info
2255 32.328365 192.168.2.11 192.168.2.141 SIP
Request: ACK sip:subs002590@192.168.2.11:9590;transport=UDP
Frame 2255 (635 bytes on wire, 635 bytes captured)
Ethernet II, Src: Vmware_d2:6a:2a (00:0c:29:d2:6a:2a), Dst: Vmware_22:e0:4c
(00:0c:29:22:e0:4c)
Internet Protocol, Src: 192.168.2.11 (192.168.2.11), Dst: 192.168.2.141
(192.168.2.141)
Version: 4
Header length: 20 bytes
Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)
Total Length: 621
Identification: 0x5204 (20996)
Flags: 0x04 (Don't Fragment)
Fragment offset: 0
Time to live: 64
Protocol: UDP (0x11)
Header checksum: 0x6093 [correct]
Source: 192.168.2.11 (192.168.2.11)
Destination: 192.168.2.141 (192.168.2.141)
User Datagram Protocol, Src Port: 9048 (9048), Dst Port: dsmeter_iatc (4060)
Source port: 9048 (9048)
Destination port: dsmeter_iatc (4060)
Length: 601
Checksum: 0x3460 [correct]
Session Initiation Protocol
Request-Line: ACK sip:subs002590@192.168.2.11:9590;transport=UDP SIP/2.0
Method: ACK
[Resent Packet: False]
Message Header
Via: SIP/2.0/UDP 192.168.2.11:9048;branch=z9hG4bK-3672-12-4
Transport: UDP
Sent-by Address: 192.168.2.11
Sent-by port: 9048
Branch: z9hG4bK-3672-12-4
Max-Forwards: 70
[truncated] Route: <sip:192.168.2.141;lr;ftag=3672SIPpTag0012>,
<sip:m...@pcscf.open-ims.test:4060;lr>, <sip:m...@scscf.open-ims.test:6060;lr>,
<sip:m...@scscf.open-ims.test:6060;lr>,
<sip:m...@pcscf.open-ims.test:4060;lr>,<sip:192.168.2.141;lr;f
From: "subs002048" <sip:subs002...@open-ims.test>;tag=3672SIPpTag0012
SIP Display info: "subs002048"
SIP from address: sip:subs002...@open-ims.test
SIP tag: 3672SIPpTag0012
To: "subs002590" <sip:subs002...@open-ims.test>;tag=3672SIPpTag0113
SIP Display info: "subs002590"
SIP to address: sip:subs002...@open-ims.test
SIP tag: 3672SIPpTag0113
Call-ID:
12-3672@192.168.2.11<mailto:12-3672@192.168.2.11><mailto:12-3672@192.168.2.11>
CSeq: 1 ACK
Sequence Number: 1
Method: ACK
Content-Length: 0
Windows Posta'dan gönderildi
------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho_______________________________________________
Sipp-users mailing list
Sipp-users@lists.sourceforge.net<mailto:Sipp-users@lists.sourceforge.net><mailto:Sipp-users@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/sipp-users
Bu e-posta mesajı ve ekleri gönderildiği kişi ya da kuruma özeldir ve gizlidir.
Ayrıca hukuken de gizli olabilir. Hiçbir şekilde üçüncü kişilere açıklanamaz ve
yayınlanamaz. Eğer mesajın gönderildiği alıcı değilseniz bu elektronik postanın
içeriğini açıklamanız, kopyalamanız, yönlendirmeniz ve kullanmanız kesinlikle
yasaktır ve bu elektronik postayı ve eklerini derhal silmeniz gerekmektedir.
NETAŞ TELEKOMÜNİKASYON A.Ş. bu mesajın içerdiği bilgilerin doğruluğu veya
eksiksiz olduğu konusunda herhangi bir garanti vermemektedir. Bu nedenle bu
bilgilerin ne şekilde olursa olsun içeriğinden, iletilmesinden, alınmasından,
saklanmasından ve kullanılmasından sorumlu değildir. Bu mesajdaki görüşler
gönderen kişiye ait olup, NETAŞ TELEKOMÜNİKASYON A.Ş.’nin görüşlerini
yansıtmayabilir.
-------------------------------------------------------
This e-mail and its attachments are private and confidential and intended for
the exclusive use of the individual or entity to whom it is addressed. It may
also be legally confidential. Any disclosure, distribution or other
dissemination of this message to any third party is strictly prohibited. If you
are not the intended recipient you are hereby notified that any dissemination,
forwarding, copying or use of any of the information is strictly prohibited,
and the e-mail should immediately be deleted. NETAŞ TELEKOMÜNİKASYON A.Ş. makes
no warranty as to the accuracy or completeness of any information contained in
this message and hereby excludes any liability of any kind for the information
contained therein or for the transmission, reception, storage or use of such
information in any way whatsoever. The opinions expressed in this message are
those of the sender and may not necessarily reflect the opinions of NETAŞ
TELEKOMÜNİKASYON A.Ş.
Bu e-posta mesajı ve ekleri gönderildiği kişi ya da kuruma özeldir ve gizlidir.
Ayrıca hukuken de gizli olabilir. Hiçbir şekilde üçüncü kişilere açıklanamaz ve
yayınlanamaz. Eğer mesajın gönderildiği alıcı değilseniz bu elektronik postanın
içeriğini açıklamanız, kopyalamanız, yönlendirmeniz ve kullanmanız kesinlikle
yasaktır ve bu elektronik postayı ve eklerini derhal silmeniz gerekmektedir.
NETAŞ TELEKOMÜNİKASYON A.Ş. bu mesajın içerdiği bilgilerin doğruluğu veya
eksiksiz olduğu konusunda herhangi bir garanti vermemektedir. Bu nedenle bu
bilgilerin ne şekilde olursa olsun içeriğinden, iletilmesinden, alınmasından,
saklanmasından ve kullanılmasından sorumlu değildir. Bu mesajdaki görüşler
gönderen kişiye ait olup, NETAŞ TELEKOMÜNİKASYON A.Ş.’nin görüşlerini
yansıtmayabilir.
-------------------------------------------------------
This e-mail and its attachments are private and confidential and intended for
the exclusive use of the individual or entity to whom it is addressed. It may
also be legally confidential. Any disclosure, distribution or other
dissemination of this message to any third party is strictly prohibited. If you
are not the intended recipient you are hereby notified that any dissemination,
forwarding, copying or use of any of the information is strictly prohibited,
and the e-mail should immediately be deleted. NETAŞ TELEKOMÜNİKASYON A.Ş. makes
no warranty as to the accuracy or completeness of any information contained in
this message and hereby excludes any liability of any kind for the information
contained therein or for the transmission, reception, storage or use of such
information in any way whatsoever. The opinions expressed in this message are
those of the sender and may not necessarily reflect the opinions of NETAŞ
TELEKOMÜNİKASYON A.Ş.------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
_______________________________________________
Sipp-users mailing list
Sipp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sipp-users
