takeshi,
Thank you, between what you had said and talking to my coworkers today,
I was able to figure out my error.
I have another question. I was looking here:
http://sipp.sourceforge.net/doc/reference.html#Structure+of+client+%28UAC+like%29+XML+scenarios,
at the keyword list, specifically at the [remote_port] keyword. I am
confused with the description, I can pass in the Remote IP port on the
command line OR add an offset [remote_port+3]. The offset part is in the
code correct? The offset isn't entered at the command line, right? The
tester just types in what remote port to communicate with just like how
the Remote IP address is entered.
this the remote IP address
| this is the remote port
| | local IP
| |
| local port
| |
| |
sipp -sf test.xml 10.0.47.34 5061 -i 10.0.47.40 -p 5060
Correct? Just type in the remote IP and remote port? There are no
options I need to include?
Thanks,
Doug
On 8/23/2011 8:49 PM, mayamatakeshi wrote:
On Wed, Aug 24, 2011 at 10:13 AM, Douglas Beach <[email protected]
<mailto:[email protected]>> wrote:
Hello,
All I'm trying to do is register a phone to SIPp. Send a REGISTER
from my phone to SIPp and then SIPp sends an OK.
That's it. I'm new with SIPp but I understand basic SIP. After I
register with SIPp then I'll make a call to my phone. Right now I
just want to register.
SIPp is not a registrar server. Instead, it can be used to load test
registrar servers.
So, you could make you scenario below to work, but SIPp will just
reply with "200 OK" for your phone request but it will not do anything
else like saving the current location of the phone and proxying
requests to it.
That being said, there is a lot of things in SIPp (read
http://sipp.sourceforge.net/doc/reference.html), like updating
in-memory injection files
(http://sipp.sourceforge.net/doc/reference.html#Updating+In-Memory+Injection+files)
that could be used to make SIPp to behave like a registrar server and
proxy/generate calls to it
(http://sipp.sourceforge.net/doc/reference.html#3PCC) but I think it
would be a worthless effort as you would be testing SIPp instead of
using SIPp to test SIP entities.
Here's my source code:
<?xml version="1.0" encoding="ISO-8859-1" ?>
<scenario name="register">
<recv request="REGISTER" crlf="true">
</recv>
<send>
<![CDATA[
SIP/2.0 200 OK
[last_Via:]
[last_From:]
[last_To:];
[last_CSeq:]
Contact: <sip:[local_ip]:[local_port];transport=[transport]>
Content-Type: application/sdp
Content-Length: [len]
]]>
</send>
</scenario>
I named the test case register.xml. Here's what I type in to run
the test case:
sipp -sf register.xml 10.0.47.46
You must pass the ip and port sipp should listen on for requests, like
this:
sipp -sf register.xml -i 10.0.47.46 -p 5060
Then nothing happens. I have Wireshark running, watching the ports
my phone and SIPp are transmitting on. I'm just not getting any
packets transferring.
If you don't see even the packets from your phone then wireshark is
not properly set, or your phone is using a network wireshark is not
sniffing on etc.
regards,
takeshi
------------------------------------------------------------------------------
EMC VNX: the world's simplest storage, starting under $10K
The only unified storage solution that offers unified management
Up to 160% more powerful than alternatives and 25% more efficient.
Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users
