Try this scenario (I know it’s
working):
<?xml version="1.0" encoding="ISO-8859-1"
?>
<scenario name="Subscribe Test"
rrs="true">
<!-- In client mode (sipp placing
calls), the Call-ID MUST be -->
<!-- generated by sipp. To do so, use
[call_id] token. -->
<send>
<![CDATA[
SUBSCRIBE sip:[remote_ip]:[remote_port] SIP/2.0
Via: SIP/2.0/[transport] [local_ip]:[local_port];branch=z9hG4bK71[pid][pid][pid]
From: <sip:car3>;tag=[call_number]
To: <sip:[service]>
Contact: <sip:[local_ip]:[local_port];transport=[transport]>
Call-ID: [call_id]
event: presence
CSeq: 1 SUBSCRIBE
Max-Forwards: 70
Expires: 3600
Accept: application/pidf+xml
Content-Length: 0
]]>
</send>
<label id="1" />
<recv response="200" optional="true"
/>
<!-- Initial NOTIFY -->
<recv request="NOTIFY" />
<send next="1"> <![CDATA[
SIP/2.0 200 OK
[last_Via:]
[last_Call-ID:]
[last_From:];[peer_tag_param]
[last_To:]
[last_CSeq:]
Contact: <sip:[service] >
[last_Event:]
Content-Length: 0
]]>
<pause milliseconds="250"/>
</send>
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Mak b
Sent: Tuesday, September 12, 2006
7:28 PM
To: Ronnie Jones; sipp-users
Subject: Re: [Sipp-users] problem
with NOTIFY messages
Hi Ronnie,
Thanks for the xmls
I tried the files that you sent but with the same results
here;s the screen capture of what I receive when I run the xml. Were you able
to run the scenarios in your environment ?
Thanks once again,
Makarand
[EMAIL PROTECTED]
sipp.2006-08-21]# ./sipp -sf mak-b-sub-not.xml -l 1 -m 1 -i 192.168.0.4 1.1.1.1:5060
-trace_err
Resolving remote host '1.1.1.1'... Done.
------------------------------ Scenario Screen -------- [1-5]: Change Screen --
Call-rate(length) Port
Total-time Total-calls Remote-host
10.0(0 ms)/1.000s 5060
0.00 s
0 1.1.1.1:5060(UDP)
0 new calls during 0.003 s period 3 ms
scheduler resolution
0 concurrent calls (limit
1) Peak was 0
calls, after 0 s
0 out-of-call msg (discarded)
1 open sockets
Messages Retrans Timeout Unexpected-Msg
SUBSCRIBE
---------->
0
0 0
200
<----------
0
0
0
200
---------->
0 0
BYE
---------->
0
0 0
BYE
---------->
0
0 0
200
<----------
0
0
0
------------------------------ Test Terminated --------------------------------
----------------------------- Statistics Screen ------- [1-5]: Change Screen --
Start
Time |
2006-09-12 06:04:56
Last Reset Time | 2006-09-12
06:04:56
Current Time
| 2006-09-12 06:04:56
-------------------------+---------------------------+--------------------------
Counter Name
| Periodic
value |
Cumulative value
-------------------------+---------------------------+--------------------------
Elapsed Time
|
00:00:00:004
| 00:00:00:004
Call
Rate
| 0.000
cps
| 0.000 cps
-------------------------+---------------------------+--------------------------
Incoming call created |
0
| 0
OutGoing call created |
0
| 0
Total Call created
|
| 0
Current Call
|
0
|
-------------------------+---------------------------+--------------------------
Successful call
|
0
| 0
Failed
call
|
0
| 0
-------------------------+---------------------------+--------------------------
Response Time |
00:00:00:000
| 00:00:00:000
Call
Length |
00:00:00:000
| 00:00:00:000
------------------------------ Test Terminated --------------------------------
2006-09-12 06:04:56: Scenario command not implemented in display
.
sipp: There were more errors, see scenarioname_pid_errors.log file
On 9/12/06, Ronnie
Jones <[EMAIL PROTECTED]>
wrote:
Mak,
try this xmk file...
Ronnie,
Thanks for the reply. I am attaching my client side xml which
causes the problems.
Please let me know if it works fine. Also which sipp version are
you using ?
Makarand
On 9/7/06, Ronnie Jones
<[EMAIL PROTECTED] >
wrote:
Mark b,
Can you post you xml files to be reviewed? I've
done tests with SUB and NOT using SIPp without any problems.. I like to try
your scripts/xmls on by SIPp system.
Ronnie
I tried a simple Subscribe - notify scenario however with the same issue.
Whenever I have a NOTIFY within the <recv> parameters sipp exits with the
message below. however when I have a Notify message between the <send>
</send> parameters it has no issues.
Could this be something that may have changed between the earlier sipp version
and a newer one ? I'm using
Sipp v1.1-TLS-PCAP, version 20060818, built Aug 23 2006, 10:04:19.
Rgds,
Makarand
On 9/7/06, Mak b <[EMAIL PROTECTED] >
wrote:
Hi all,
I'm trying to implement a scenario where the server would send a NOTIFY
message.
However when I insert the following in the client xml to receive the NOTIFY
message, sipp exits with the following error
"2006-09-07 08:44:57: Scenario command not implemented in display"
Does sipp support such a scenario ?
Thanks in advance.
Regards,
Makarand
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support
web services, security?
Get stuff done quickly with pre-integrated
technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1
based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support
web services, security?
Get stuff done quickly with pre-integrated
technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1
based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users
