Hello All,
I am getting some junk characters printed before NOTIFY when i run the
attached script.
Kindly help.
The junk characters printed are as follows -
*!:E7G@*
*!*
*!C>roP?VXNOTIFY sip: private-ac@10.30.33.12 <private-ac@10.30.33.12>
SIP/2.0*
*Via: SIP/2.0/TCP 10.30.33.10:5060;branch=branch]*
*Max-Forwards: 70*
Thanks,
Anjana
<?xml version="1.0" encoding="ISO-8859-1" ?>
<!DOCTYPE scenario SYSTEM "sipp.dtd">
<scenario name="NOTIFY">
<send retrans="500">
<![CDATA[
NOTIFY sip:private-ac@[remote_ip] SIP/2.0
Via:SIP/2.0/[transport] [local_ip]:[local_port];branch=branch]
Max-Forwards: 70
[last_From:]
[last_To:];tag=[call_number]
[last_Call-ID:]
CSeq: 10 NOTIFY
Event: dialog
Require: eventlist
Subscription-State: active; expires=3599
Contact: <sip:private-ac@[local_ip]:[local_port]>
Content-Type:multipart/related;boundary=UniqueBroadWorksBoundary;type="application/rlmi+xml"
Content-Length: [len]
--UniqueBroadWorksBoundary
Content-Type:application/rlmi+xml
Content-Length:470
Content-ID:<3AddnK@broadworks>
<?xml version="1.0" encoding="UTF-8"?><list xmlns="urn:ietf:params:xml:ns:rlmi" uri="sip:resources@[local_ip]" version="0" fullState="true">
<resource uri="sip:anjana3@[local_ip]"><name>6138 6138</name><instance id="UDTRRpGFJZ" state="active" cid="swncLz@broadworks"/></resource>
<resource uri="sip:anjana2@[local_ip]"><name>6137 6137</name><instance id="3XVQdZypNK" state="active" cid="wWIG4K@broadworks"/></resource>
</list>
--UniqueBroadWorksBoundary
Content-Type:application/dialog-info+xml
Content-Length:535
Content-ID:<swncLz@broadworks>
<?xml version="1.0" encoding="UTF-8"?><dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="0" state="full" entity="sip:anjana3@[local_ip]"><dialog id="Y2FsbGhhbGYtNzUwNjE0Njk6MA==" direction="recipient"><state>confirmed</state><local><identity display="6138 6138">sip:anjana3@[local_ip]</identity><identity display="6138 6138">tel:+16667786138;ext=6138</identity></local><remote><identity display="6137 6137">sip:6137@[local_ip];user=phone</identity></remote></dialog></dialog-info>
--UniqueBroadWorksBoundary
Content-Type:application/dialog-info+xml
Content-Length:535
Content-ID:<wWIG4K@broadworks>
<?xml version="1.0" encoding="UTF-8"?><dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="0" state="full" entity="sip:anjana2@[local_ip]"><dialog id="Y2FsbGhhbGYtNzUwNjE0NjU6MA==" direction="initiator"><state>confirmed</state><local><identity display="6137 6137">sip:anjana2@[local_ip]</identity><identity display="6137 6137">tel:+16667786137;ext=6137</identity></local><remote><identity display="6138 6138">sip:6138@[local_ip];user=phone</identity></remote></dialog></dialog-info>
--UniqueBroadWorksBoundary--
]]>
<recv response="200"></recv>
<!-- Definition of the response time repartition table (unit is ms) -->
<ResponseTimeRepartition value="10, 20, 30, 40, 50, 100, 150, 200"/>
<!-- Definition of the call length repartition table (unit is ms) -->
<CallLengthRepartition value="10, 50, 100, 500, 1000, 5000, 10000"/>
</scenario>
<?xml version="1.0" encoding="ISO-8859-1" ?>
<!DOCTYPE scenario SYSTEM "sipp.dtd">
<scenario name="REGISTER_SUBSCRIBE">
<!-- Generated Scenario for 172.24.144.139 using Snipp v1.3.8 -->
<recv request="SUBSCRIBE">
</recv>
<send>
<![CDATA[
SIP/2.0 200 OK
[last_Via:]
[last_From:]
[last_To:];tag=[call_number]
[last_Call-ID:]
[last_CSeq:]
Event: dialog
Contact: <sip:[local_ip]:[local_port];transport=[transport]>
Expires: 3600
Content-Length: 0
]]>
</send>
<send retrans="500">
<![CDATA[
NOTIFY sip: private-ac@[remote_ip] SIP/2.0
Via: SIP/2.0/[transport] [local_ip]:[local_port];branch=[branch]
Max-Forwards: 70
[last_From:]
[last_To:];tag=[call_number]
[last_Call-ID:]
CSeq: 10 NOTIFY
Event: dialog
Require: eventlist
Subscription-State: active; expires=3599
Contact: <sip:private-ac@[local_ip]:[local_port]>
Content-Type:multipart/related;boundary=UniqueBroadWorksBoundary;type="application/rlmi+xml"
Content-Length: [len]
--UniqueBroadWorksBoundary
Content-Type:application/rlmi+xml
Content-Length:470
Content-ID:<3AddnK@broadworks>
<?xml version="1.0" encoding="UTF-8"?><list xmlns="urn:ietf:params:xml:ns:rlmi" uri="sip:resources@[local_ip]" version="0" fullState="true">
<resource uri="sip:anjana3@[local_ip]"><name>6138 6138</name><instance id="UDTRRpGFJZ" state="active" cid="swncLz@broadworks"/></resource>
<resource uri="sip:anjana2@[local_ip]"><name>6137 6137</name><instance id="3XVQdZypNK" state="active" cid="wWIG4K@broadworks"/></resource>
</list>
--UniqueBroadWorksBoundary
Content-Type:application/dialog-info+xml
Content-Length:535
Content-ID:<swncLz@broadworks>
<?xml version="1.0" encoding="UTF-8"?><dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="0" state="full" entity="sip:anjana3@[local_ip]"><dialog id="Y2FsbGhhbGYtNzUwNjE0Njk6MA==" direction="recipient"><state>confirmed</state><local><identity display="6138 6138">sip:anjana3@[local_ip]</identity><identity display="6138 6138">tel:+16667786138;ext=6138</identity></local><remote><identity display="6137 6137">sip:6137@[local_ip];user=phone</identity></remote></dialog></dialog-info>
--UniqueBroadWorksBoundary
Content-Type:application/dialog-info+xml
Content-Length:535
Content-ID:<wWIG4K@broadworks>
<?xml version="1.0" encoding="UTF-8"?><dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="0" state="full" entity="sip:anjana2@[local_ip]"><dialog id="Y2FsbGhhbGYtNzUwNjE0NjU6MA==" direction="initiator"><state>confirmed</state><local><identity display="6137 6137">sip:anjana2@[local_ip]</identity><identity display="6137 6137">tel:+16667786137;ext=6137</identity></local><remote><identity display="6138 6138">sip:6138@[local_ip];user=phone</identity></remote></dialog></dialog-info>
--UniqueBroadWorksBoundary--
]]>
</send>
<recv response="200"></recv>
<!-- Definition of the response time repartition table (unit is ms) -->
<ResponseTimeRepartition value="10, 20, 30, 40, 50, 100, 150, 200"/>
<!-- Definition of the call length repartition table (unit is ms) -->
<CallLengthRepartition value="10, 50, 100, 500, 1000, 5000, 10000"/>
</scenario>
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://p.sf.net/sfu/Zoho
_______________________________________________
Sipp-users mailing list
Sipp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sipp-users