Re: [Sipp-users] Facing issue while trying to execute Registration & INVITE in one xml file in Sipp

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 454-5900

In the script I am using call_id & in the UAC side if you see.
 I have tried using the same call_id in INVITE & REGISTRATION suspecting inside one script, all the subsequent requests should use the same call_id.

But it still it also did not work.

Thanks
Samarpita

-----Original Message-----
From: Volkan KUMBASAR [mailto:kumbasar@NETAS.com.tr] 
Sent: Monday, August 17, 2015 5:24 PM
To: Sakharam Thorat; Samarpita Nayak; sipp-users
Subject: RE: [Sipp-users] Facing issue while trying to execute Registration & INVITE in one xml file in Sipp

See documentation:

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.
________________________________________
From: Sakharam Thorat [sak...@ou...]
Sent: Monday, August 17, 2015 2:46 PM
To: Samarpita Nayak; sipp-users
Subject: Re: [Sipp-users] Facing issue while trying to execute Registration & INVITE in one xml file in Sipp

UAS side script have problem , why UAS script is sending Register message ?

Best Regards,
Sakharam Thorat.

________________________________
From: SN00119894@TechMahindra.com
To: sip...@li...
Date: Mon, 17 Aug 2015 06:49:58 +0000
Subject: [Sipp-users] Facing issue while trying to execute Registration & INVITE in one xml file in Sipp

Hi All,

I am trying to make TCP calls using Sipp as my 2 end users within my IMS cloud.

As TCP ports are differing for Registration & Invite, I thought of putting both my Registration & INVITE in one xml file.

To my strange I found it in this execution procedure my UDP calls are also not working.

*UDP calls are working fine when each scenarios are executed separately.

UAS sip is not receiving the INVITE message in this case & generating “Discarding message which can't be mapped to a known SIPp call”

The issue remains same for both UDP & TCP calls.

In the stack “/usr/local/src/sipp-3.3.990/src/socket.cpp:                WARNING("Discarding message which can't be mapped to a known SIPp call:\n%s", msg); is getting called.

I found inside the listen.cpp file, the call-id check is failing.

I have attached the used XML files.

Thanks

Samarpita

________________________________
============================================================================================================================
Disclaimer: This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at http://www.techmahindra.com/Disclaimer.html externally http://tim.techmahindra.com/tim/disclaimer.html internally within TechMahindra.
============================================================================================================================

------------------------------------------------------------------------------
_______________________________________________ Sipp-users mailing list Sip...@li... 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.Ş.

============================================================================================================================
Disclaimer:  This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at http://www.techmahindra.com/Disclaimer.html externally http://tim.techmahindra.com/tim/disclaimer.html internally within TechMahindra.
============================================================================================================================