Re: [Sipp-users] What is dead call?
If client (SIPp) has generated the ACK that means Server will not retransmit the response after it received ACK for that response so, that should be safely ignored. Thanks -Sumeet -Original Message- From: Manish Sapariya [mailto:man...@gslab.com] Sent: Friday, April 23, 2010 1:54 PM To: sipp-users@lists.sourceforge.net Subject: Re: [Sipp-users] What is dead call? Thanks Sumit. Should not such message be counted as retransmitted or simply ignored? Thanks and Regards, Manish Office Phone : 46711053 Extension: #1053 On 4/23/2010 12:09 PM, Sumeetkumar Bhardwaj wrote: Hello Manish, I think, When SIPp receives 1st response for the call and if it has generated the ACK for that response then after that if it receives any response for the same call, it will be marked as DEAD calls because after generating ACK it has removed all information for that call. Thanks -Sumeet -Original Message- From: Manish Sapariya [mailto:man...@gslab.com] Sent: Friday, April 23, 2010 10:57 AM To: sipp-users@lists.sourceforge.net Subject: [Sipp-users] What is dead call? I tried to google and even looked at the source. What I understood, is that 'a deadcall, is a call for which there was not responses until deadwait time'. Can somebody please confirm. If my understanding is correct, then how sipp responds to or accounts for the reply received after deadwait period. Thanks and Regards, Manish -- ___ Sipp-users mailing list Sipp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sipp-users DISCLAIMER == This e-mail may contain privileged and confidential information which is the property of Persistent Systems Ltd. It is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are not authorized to read, retain, copy, print, distribute or use this message. If you have received this communication in error, please notify the sender and delete all copies of this message. Persistent Systems Ltd. does not accept any liability for virus infected mails. -- ___ Sipp-users mailing list Sipp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sipp-users DISCLAIMER == This e-mail may contain privileged and confidential information which is the property of Persistent Systems Ltd. It is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are not authorized to read, retain, copy, print, distribute or use this message. If you have received this communication in error, please notify the sender and delete all copies of this message. Persistent Systems Ltd. does not accept any liability for virus infected mails. -- ___ Sipp-users mailing list Sipp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sipp-users
Re: [Sipp-users] What is dead call?
If Server still retransmitting the response that means there is a problem in the ACK which SIPp sends. So Verify the ACK. Thanks -Sumeet -Original Message- From: Sumeetkumar Bhardwaj Sent: Friday, April 23, 2010 2:06 PM To: 'Manish Sapariya'; sipp-users@lists.sourceforge.net Subject: RE: [Sipp-users] What is dead call? If client (SIPp) has generated the ACK that means Server will not retransmit the response after it received ACK for that response so, that should be safely ignored. Thanks -Sumeet -Original Message- From: Manish Sapariya [mailto:man...@gslab.com] Sent: Friday, April 23, 2010 1:54 PM To: sipp-users@lists.sourceforge.net Subject: Re: [Sipp-users] What is dead call? Thanks Sumit. Should not such message be counted as retransmitted or simply ignored? Thanks and Regards, Manish Office Phone : 46711053 Extension: #1053 On 4/23/2010 12:09 PM, Sumeetkumar Bhardwaj wrote: Hello Manish, I think, When SIPp receives 1st response for the call and if it has generated the ACK for that response then after that if it receives any response for the same call, it will be marked as DEAD calls because after generating ACK it has removed all information for that call. Thanks -Sumeet -Original Message- From: Manish Sapariya [mailto:man...@gslab.com] Sent: Friday, April 23, 2010 10:57 AM To: sipp-users@lists.sourceforge.net Subject: [Sipp-users] What is dead call? I tried to google and even looked at the source. What I understood, is that 'a deadcall, is a call for which there was not responses until deadwait time'. Can somebody please confirm. If my understanding is correct, then how sipp responds to or accounts for the reply received after deadwait period. Thanks and Regards, Manish -- ___ Sipp-users mailing list Sipp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sipp-users DISCLAIMER == This e-mail may contain privileged and confidential information which is the property of Persistent Systems Ltd. It is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are not authorized to read, retain, copy, print, distribute or use this message. If you have received this communication in error, please notify the sender and delete all copies of this message. Persistent Systems Ltd. does not accept any liability for virus infected mails. -- ___ Sipp-users mailing list Sipp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sipp-users DISCLAIMER == This e-mail may contain privileged and confidential information which is the property of Persistent Systems Ltd. It is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are not authorized to read, retain, copy, print, distribute or use this message. If you have received this communication in error, please notify the sender and delete all copies of this message. Persistent Systems Ltd. does not accept any liability for virus infected mails. -- ___ Sipp-users mailing list Sipp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sipp-users
Re: [Sipp-users] What is dead call?
If a call has completed, then SIPp maintains a small record of the call for a little bit. This way any messages related to that call; after the call has already been closed can be cataloged as dead call messages. Without keeping this record, the messages for a completed call are counted as out-of-call messages on the UAC. On the UAS, a new call is automatically created and fails because the message is, most likely, unexpected. Charles Manish Sapariya man...@gslab.com wrote on 04/23/2010 01:26:44: Manish Sapariya man...@gslab.com 04/23/2010 01:26 To sipp-users@lists.sourceforge.net cc Subject [Sipp-users] What is dead call? I tried to google and even looked at the source. What I understood, is that 'a deadcall, is a call for which there was not responses until deadwait time'. Can somebody please confirm. If my understanding is correct, then how sipp responds to or accounts for the reply received after deadwait period. Thanks and Regards, Manish -- ___ Sipp-users mailing list Sipp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sipp-users-- ___ Sipp-users mailing list Sipp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sipp-users
Re: [Sipp-users] Subscribe/Notify Call Flow
Hi, you must use the placeholder [call_id] instead of your self-defined Call-ID--Header: http://sipp.sourceforge.net/doc/reference.html#Structure+of+client+(UAC+like)+XML+scenarios -- A call_id identifies a call and is generated by SIPp for each new call. In client mode, it is mandatory to use the value generated by SIPp in the Call-ID header. Otherwise, SIPp will not recognise the answer to the message sent as being part of an existing call. Note: [call_id] can be pre-pended with an arbitrary string using '///'. Example: Call-ID: ABCDEFGHIJ///[call_id] - it will still be recognized by SIPp as part of the same call. -- br Michael On 2010-04-23 13:02, Himanshu Rawat wrote: Hi Michael, Here are the scenario and logs. *XML-Scenario * ?xml version=1.0 encoding=ISO-8859-1 ? scenario name=subscribe-notify send ![CDATA[ SUBSCRIBE sip:4085551...@10.253.253.52 mailto:sip%3a4085551...@10.253.253.52 SIP/2.0 Via: SIP/2.0/UDP 10.253.253.52 From: sip:hra...@10.253.253.52 mailto:sip%3ahra...@10.253.253.52;tag=7D24.0FF3 To: sip:4085551...@10.253.253.52:5060 http://sip:4085551...@10.253.253.52:5060 Call-ID: 00c0.95c9.4050.4103.7d24.0...@10.253.253.52 mailto:00c0.95c9.4050.4103.7d24.0...@10.253.253.52 CSeq: 34211 SUBSCRIBE Content-Length: 0 Max-Forwards: 70 Contact: sip:hra...@10.253.253.52 mailto:sip%3ahra...@10.253.253.52 Event: message-summary Accept: application/simple-message-summary Expires: 3600 Supported: timer ]] /send !-- pause milliseconds=2000/ -- recv response=200/recv recv request=NOTIFY/recv send ![CDATA[ SIP/2.0 200 OK Via: SIP/2.0/UDP 10.160.129.63:5060;branch=z9hG4bKAq46kjXxP7n4GWjpxlfyjg~~6 From: sip:4085551...@10.253.205.110 mailto:sip%3a4085551...@10.253.205.110;bgid=IPUNITY_104;tag=580ce060-f1f5-4b0c-9f28-2571a7f6581e To: sip:4085551...@10.253.205.110:5060;bgid=IPUNITY_104;tag=7D24.0FF3 Call-ID: 00c0.95c9.4050.4103.7d24.0...@10.253.253.52 mailto:00c0.95c9.4050.4103.7d24.0...@10.253.253.52 CSeq: 4 NOTIFY Content-Length: 0 ]] /send - *Errors log file* sipp: The following events occured: 2010-04-1916:13:21:7341271673801.734840: Discarding message which can't be mapped to a known SIPp call: SIP/2.0 200 Ok Via: SIP/2.0/UDP 10.253.253.52 To: sip:4085551...@10.253.253.52:5060 http://sip:4085551...@10.253.253.52:5060;tag=0fa6b9bf-bc7f-41a4-9ddd-b591ae3f1d81 From: sip:hra...@10.253.253.52 mailto:sip%3ahra...@10.253.253.52;tag=7D24.0FF3 Call-ID: 00c0.95c9.4050.4103.7d24.0...@10.253.253.52 mailto:00c0.95c9.4050.4103.7d24.0...@10.253.253.52 CSeq: 34211 SUBSCRIBE Content-Length: 0 Expires: 3600 Allow: INVITE,ACK,BYE,CANCEL,PRACK,NOTIFY,INFO,OPTIONS,UPDATE,SUBSCRIBE Supported: 100rel, timer,precondition Contact: sip:4085551...@10.253.205.110:5060;transport=udp . 2010-04-1916:13:22:0591271673802.059911: Discarding message which can't be mapped to a known SIPp call: NOTIFY sip:4085551...@10.253.253.52:5060;transport=udp SIP/2.0 Via: SIP/2.0/UDP 10.253.205.110:5060;branch=z9hG4bKSa.KQMqlRaANSsThTNnWMw~~8 Max-Forwards: 70 To: sip:4085551...@10.253.253.52 mailto:sip%3a4085551...@10.253.253.52;bgid=IPUNITY_104;tag=7D24.0FF3 From: sip:4085551...@10.253.205.110 mailto:sip%3a4085551...@10.253.205.110;bgid=IPUNITY_104;tag=0fa6b9bf-bc7f-41a4-9ddd-b591ae3f1d81 Call-ID: 00c0.95c9.4050.4103.7d24.0...@10.253.253.52 mailto:00c0.95c9.4050.4103.7d24.0...@10.253.253.52 CSeq: 9 NOTIFY Content-Length: 22 Content-Type: application/simple-message-summary Event: message-summary Subscription-State: active Contact: sip:4085551...@10.253.205.110:5060 http://sip:4085551...@10.253.205.110:5060 Allow: INVITE,ACK,BYE,CANCEL,PRACK,NOTIFY,INFO,OPTIONS,UPDATE,SUBSCRIBE Supported: 100rel, timer,precondition Message-Waiting: yes . 2010-04-1916:13:22:5651271673802.565064: Discarding message which can't be mapped to a known SIPp call: NOTIFY sip:4085551...@10.253.253.52:5060;transport=udp SIP/2.0 Via: SIP/2.0/UDP 10.253.205.110:5060;branch=z9hG4bKSa.KQMqlRaANSsThTNnWMw~~8 Max-Forwards: 70 To: sip:4085551...@10.253.253.52 mailto:sip%3a4085551...@10.253.253.52;bgid=IPUNITY_104;tag=7D24.0FF3 From: sip:4085551...@10.253.205.110 mailto:sip%3a4085551...@10.253.205.110;bgid=IPUNITY_104;tag=0fa6b9bf-bc7f-41a4-9ddd-b591ae3f1d81 Call-ID: 00c0.95c9.4050.4103.7d24.0...@10.253.253.52 mailto:00c0.95c9.4050.4103.7d24.0...@10.253.253.52 CSeq: 9 NOTIFY Content-Length: 22 Content-Type: application/simple-message-summary Event: message-summary Subscription-State: active Contact: sip:4085551...@10.253.205.110:5060 http://sip:4085551...@10.253.205.110:5060 Allow: INVITE,ACK,BYE,CANCEL,PRACK,NOTIFY,INFO,OPTIONS,UPDATE,SUBSCRIBE Supported: 100rel, timer,precondition Message-Waiting: yes Anything else you need
