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
