Dear all,
I am making a test with ims - bench, opensips and open ims.
I am generating traffic (ims call and ims registration= ims_uac and ims_reg)
from ims bench and passing this traffic opensips load balancer. Traffic is
ended at open ims.
When traffic is passed through open sips although in Wireshark log it is
successful , at ims bench output I receive recvrmt timeout and call is marked
as failed.
When I remove the opensips loadbalancer between opensips and open ims call flow
in Wireshark is similar and ims bench output call is counted as successful call.
What can be the reason of recvrmt timeouts and marking the call as failed in
ims bench when opensips is used?
Samsung Mobile tarafından gönderildi
<div>-------- Orjinal mesaj --------</div><div>Kimden: "kaan.dandin"
<kaan.dan...@gmail.com> </div><div>Tarih:12 09 2014 14:06 (GMT+02:00)
</div><div>Alıcı: Gunes Kurt <gk...@itu.edu.tr> </div><div>Cc: "Ibrahim
Hokelek(BİLGEM-UEKAE)" <ibrahim.hoke...@tubitak.gov.tr>,Suat Aksu
<suata...@itu.edu.tr> </div><div>Konu: YNT: Re: Kaan Dandin-Telekom.YL.Tezi son
durum(11 Eylul 14) </div><div>
</div>
wireshark trace of the call without load balancer
No. Time Source Destination Protocol Info
16334 585.948752 192.168.2.11 192.168.2.5 SIP/SDP
Request: INVITE sip:subs002...@open-ims.test, with session description
16336 585.969847 192.168.2.5 192.168.2.11 SIP
Status: 100 trying -- your call is important to us
16337 585.995807 192.168.2.5 192.168.2.11 SIP/SDP
Request: INVITE sip:subs002591@192.168.2.11:9591, with session description
16338 585.996053 192.168.2.11 192.168.2.5 SIP
Status: 180 Ringing
16339 586.028300 192.168.2.5 192.168.2.11 SIP
Status: 180 Ringing
16455 590.945008 192.168.2.11 192.168.2.5 SIP/SDP
Status: 200 OK, with session description
16456 590.962826 192.168.2.5 192.168.2.11 SIP/SDP
Status: 200 OK, with session description
16457 590.963108 192.168.2.11 192.168.2.5 SIP
Request: ACK sip:subs002591@192.168.2.11:9591;transport=UDP
16458 590.975914 192.168.2.5 192.168.2.11 SIP
Request: ACK sip:subs002591@192.168.2.11:9591;transport=UDP
18533 626.082044 192.168.2.11 192.168.2.5 SIP
Request: BYE sip:subs002591@192.168.2.11:9591;transport=UDP
18534 626.102656 192.168.2.5 192.168.2.11 SIP
Request: BYE sip:subs002591@192.168.2.11:9591;transport=UDP
18535 626.102843 192.168.2.11 192.168.2.5 SIP
Status: 200 OK
18536 626.127539 192.168.2.5 192.168.2.11 SIP
Status: 200 OK
wireshark trace with load balancer
No. Time Source Destination Protocol Info
104249 960.673077 192.168.2.11 192.168.2.141 SIP/SDP
Request: INVITE sip:subs002...@open-ims.test, with session description
104283 960.991448 192.168.2.141 192.168.2.11 SIP
Status: 100 Giving a try
104284 960.991872 192.168.2.141 192.168.2.5 SIP/SDP
Request: INVITE sip:subs002...@open-ims.test, with session description
104346 961.511031 192.168.2.141 192.168.2.5 SIP/SDP
Request: INVITE sip:subs002...@open-ims.test, with session description
104440 962.528467 192.168.2.141 192.168.2.5 SIP/SDP
Request: INVITE sip:subs002...@open-ims.test, with session description
104464 962.879294 192.168.2.5 192.168.2.141 SIP
Status: 100 trying -- your call is important to us
104629 964.710950 192.168.2.5 192.168.2.141 SIP
Status: 100 trying -- your call is important to us
104865 967.141658 192.168.2.5 192.168.2.141 SIP
Status: 100 trying -- your call is important to us
105000 968.473821 192.168.2.5 192.168.2.141 SIP/SDP
Request: INVITE sip:subs002826@192.168.2.11:9826, with session description
105033 968.795276 192.168.2.141 192.168.2.5 SIP
Status: 100 Giving a try
105035 968.795643 192.168.2.141 192.168.2.11 SIP/SDP
Request: INVITE sip:subs002826@192.168.2.11:9826, with session description
105036 968.795885 192.168.2.11 192.168.2.141 SIP
Status: 180 Ringing
105046 968.953619 192.168.2.5 192.168.2.141 SIP/SDP
Request: INVITE sip:subs002826@192.168.2.11:9826, with session description
105058 969.095800 192.168.2.141 192.168.2.5 SIP
Status: 180 Ringing
106347 969.209840 192.168.2.141 192.168.2.5 SIP
Status: 180 Ringing
106437 969.953537 192.168.2.5 192.168.2.141 SIP/SDP
Request: INVITE sip:subs002826@192.168.2.11:9826, with session description
106473 970.259560 192.168.2.141 192.168.2.5 SIP
Status: 180 Ringing
106642 971.953157 192.168.2.5 192.168.2.141 SIP/SDP
Request: INVITE sip:subs002826@192.168.2.11:9826, with session description
106665 972.271918 192.168.2.141 192.168.2.5 SIP
Status: 180 Ringing
106833 973.737574 192.168.2.11 192.168.2.141 SIP/SDP
Status: 200 OK, with session description
106908 974.240565 192.168.2.11 192.168.2.141 SIP/SDP
Status: 200 OK, with session description
106989 974.748866 192.168.2.141 192.168.2.5 SIP/SDP
Status: 200 OK, with session description
107026 975.252601 192.168.2.11 192.168.2.141 SIP/SDP
Status: 200 OK, with session description
107111 975.952774 192.168.2.5 192.168.2.14 SIP/SDP Request:
INVITE sip:subs002826@192.168.2.11:9826, with session description
107131 976.253561 192.168.2.141 192.168.2.5 SIP/SDP
Status: 200 OK, with session description
107225 977.262307 192.168.2.11 192.168.2.141 SIP/SDP
Status: 200 OK, with session description
107261 977.590296 192.168.2.141 192.168.2.5 SIP/SDP
Status: 200 OK, with session description
107590 981.264348 192.168.2.11 192.168.2.141 SIP/SDP
Status: 200 OK, with session description
107917 985.273276 192.168.2.11 192.168.2.141 SIP/SDP
Status: 200 OK, with session description
108043 986.733541 192.168.2.5 192.168.2.141 SIP
Status: 180 Ringing
108261 989.157151 192.168.2.5 192.168.2.141 SIP/SDP
Status: 200 OK, with session description
108927 989.278207 192.168.2.11 192.168.2.141 SIP/SDP
Status: 200 OK, with session description
109278 989.487741 192.168.2.141 192.168.2.11 SIP/SDP
Status: 200 OK, with session description
109279 989.487992 192.168.2.11 192.168.2.141 SIP
Request: ACK sip:subs002826@192.168.2.11:9826;transport=UDP
109531 993.287227 192.168.2.11 192.168.2.141 SIP/SDP
Status: 200 OK, with session description
110513 1001.305112 192.168.2.11 192.168.2.141 SIP/SDP
Status: 200 OK, with session description
116624 1038.227317 192.168.2.11 192.168.2.141 SIP
Request: BYE sip:subs002826@192.168.2.11:9826;transport=UDP
116643 1038.583434 192.168.2.141 192.168.2.11 SIP
Status: 200 OK
118145 1046.585829 192.168.2.11 192.168.2.141 SIP
Request: BYE sip:service@192.168.2.141:4060
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
Sipp-users mailing list
Sipp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sipp-users
