Hello , This mail is
in response to the mail sent by (Ulrik Svensson) Sipp scenario that
first send a REGISTER and then wait for an INVITE
Sorry I am not able to reply in the thread. Yes you can do that . You
need to have 2 scenario xml files. First registers the number on the
particular port for may be 3600 seconds And the next scenario file
waits for the INVITE request on the same port I have pasted the
sample scenario scripts down below Register scenario <scenario
name="branch_client"> <send retrans="500">
<![CDATA[
REGISTER sip:166.34.160.150 SIP/2.0
Via: SIP/2.0/[transport] [local_ip]:[local_port];branch=[branch]
From: ua1 <sip:4...@[local_ip]:[local_port]>;tag=[call_number]
To: ua1 <sip:4...@[local_ip]:[local_port]>
Call-ID: [call_id]
CSeq: 1 REGISTER
Contact: sip:4...@[local_ip]:[local_port]
Content-Length: 0
Expires: 3600
]]>
</send>
<!-- simple case - just jump over a line -->
<recv response="200" rtd="true" next="5">
</recv>
<recv response="200">
Recv INVITE scenatrio file can be the UAS.xml file .. that is given
with documnetaion
./sipp -m 1 -p 5060 -trace_msg -trace_err -trace_logs -sf
../script/uas_reg.xml 166.34.160.150:5060
./sipp -p 5060 -trace_msg -trace_err -trace_logs -sf ../script/uas.xml
Thankign you Regards,
Siddharth
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users
