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
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
https://lists.sourceforge.net/lists/listinfo/sipp-users
