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-19 16:13:21:734 1271673801.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-19 16:13:22:059 1271673802.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-19 16:13:22:565 1271673802.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 please do tell. > > > > Cheers, > Rawat > > > On Thu, Apr 22, 2010 at 21:40, Michael Hirschbichler > <s...@hirschbichler.biz <mailto:s...@hirschbichler.biz>> wrote: > > Can you send us the xml-scenario and the "-trace_msg" - Logfile? > > br > Michael > > > On 2010-04-20 08:20, Himanshu Rawat wrote: > > Hi Michael, > > > > I made sample Subscribe/Notify XML scenario and getting below error in > > sipp error log files. Error log files shows me 200 response > received but > > with below error. > > * > > "Discarding message which can't be mapped to a known SIPp call:"* > > > > Scenario: > > > > SUBSCRIBE ----------> > > 200 <---------- > > NOTIFY <---------- > > 200 ----------> > > > > In the voice mail server I can see SUBSCRIBE getting processed and 200 > > response is getting sent. Also Call-id, from tag and CSeq values > are same. > > > > Any idea why this error is coming ??? > > > > > > Cheers, > > Rawat > > > > > > > > > > On Mon, Apr 19, 2010 at 12:28, Himanshu Rawat > <himanshu.ra...@gmail.com <mailto:himanshu.ra...@gmail.com> > > <mailto:himanshu.ra...@gmail.com > <mailto:himanshu.ra...@gmail.com>>> wrote: > >> Thanks Michale. > >> > >> Tried and worked though with some errors. Will get back if not > >> resolved + more Questions. > >> > >> Cheers, > >> Rawat > >> > >> > >> > >> On Fri, Apr 16, 2010 at 17:46, Michael Hirschbichler > >> <s...@hirschbichler.biz <mailto:s...@hirschbichler.biz> > <mailto:s...@hirschbichler.biz <mailto:s...@hirschbichler.biz>>> wrote: > >>> Well, this is not tricky, just > >>> > >>> <send> > >>> SUBSCRIBE... > >>> </send> > >>> > >>> <recv response="200"></recv> > >>> > >>> <recv request="NOTIFY"></recv> > >>> > >>> <send> > >>> 200 OK ... > >>> </send> > >>> > >>> For the SIP-messages, just start the SIP-client of your choice and > >>> record the messages with wireshark > >>> > >>> br > >>> Michael > >>> > >>> On 2010-04-16 13:55, Himanshu Rawat wrote: > >>>> Hi Guys, > >>>> > >>>> Can anyone tell me on how to write a simple customized > >>>> Subscribe/Notify Call scenario. > >>>> > >>>> Subscribe needs to be send to voice mail server ( which i > already have). > >>>> > >>>> ----------> SUBSCRIBE ( to my voice mail server which will > process > > it ) > >>>> > >>>> <---------- 200 > >>>> [ 50ms] Pause > >>>> <---------- NOTIFY ( Will come from my voice mail server ) > >>>> ----------> 200 > >>>> > >>>> Any link/docs will help :) > >>>> > >>>> Cheers, > >>>> Rawat > >>>> > >>>> > > > > ------------------------------------------------------------------------------ > >>>> Download Intel® Parallel Studio Eval > >>>> Try the new software tools for yourself. Speed compiling, find bugs > >>>> proactively, and fine-tune applications for parallel performance. > >>>> See why Intel Parallel Studio got high marks during beta. > >>>> http://p.sf.net/sfu/intel-sw-dev > >>>> _______________________________________________ > >>>> Sipp-users mailing list > >>>> Sipp-users@lists.sourceforge.net > <mailto: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 > >>> > >>> > >>> > > > > ------------------------------------------------------------------------------ > >>> Download Intel® Parallel Studio Eval > >>> Try the new software tools for yourself. Speed compiling, find bugs > >>> proactively, and fine-tune applications for parallel performance. > >>> See why Intel Parallel Studio got high marks during beta. > >>> http://p.sf.net/sfu/intel-sw-dev > >>> _______________________________________________ > >>> Sipp-users mailing list > >>> Sipp-users@lists.sourceforge.net > <mailto: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 > >>> > >> > > > > > > > > > > > > ------------------------------------------------------------------------------ > > Download Intel® Parallel Studio Eval > > Try the new software tools for yourself. Speed compiling, find bugs > > proactively, and fine-tune applications for parallel performance. > > See why Intel Parallel Studio got high marks during beta. > > http://p.sf.net/sfu/intel-sw-dev > > > > > > > > _______________________________________________ > > Sipp-users mailing list > > Sipp-users@lists.sourceforge.net > <mailto:Sipp-users@lists.sourceforge.net> > > https://lists.sourceforge.net/lists/listinfo/sipp-users > > > > ------------------------------------------------------------------------------ > _______________________________________________ > Sipp-users mailing list > Sipp-users@lists.sourceforge.net > <mailto: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
