Hi Ajana, I used attached files with this mail to create sip subscribe notify scenario, and collected traces i don't seen any problem with NOTIFY msg. please find attachment for details.
Test Env: Sipp ver: SIPp v3.4.1-TLS-PCAP-RTPSTREAM built Sep 9 2014, 15:26:42.commands:UAS:./sipp -sn uas -sf /home/sakharam/Desktop/for_anjana/sub.xml -trace_msg -m 1UAC:./sipp -sn uas -sf /home/sakharam/Desktop/for_anjana/sub_uac.xml -i 192.168.57.2 192.168.57.2 -m 1 -trace_msg Best Regards,Sakharam Thorat. Date: Mon, 13 Oct 2014 15:45:02 +0530 From: linkanj...@gmail.com To: sipp-users@lists.sourceforge.net Subject: [Sipp-users] Junk characters getting inserted in before NOTIFY 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 SIP/2.0Via: SIP/2.0/TCP 10.30.33.10:5060;branch=branch]Max-Forwards: 70 Thanks,Anjana ------------------------------------------------------------------------------ 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
----------------------------------------------- 2014-10-13 16:21:12.875047 UDP message sent (422 bytes): SUBSCRIBE sip:service@192.168.57.2:5060 SIP/2.0 Via: SIP/2.0/UDP 192.168.57.2:5061;branch=z9hG4bK-24239-1-0 From: sipp <sip:sipp@192.168.57.2:5061>;tag=24239SIPpTag001 To: sut <sip:service@192.168.57.2:5060> Call-ID: 1-24239@192.168.57.2 CSeq: 1 SUBSCRIBE Contact: sip:sipp@192.168.57.2:5061 Max-Forwards: 70 Event: presence Expires: 60 Accept: application/pidf+xml Allow-Events: presence Content-Length: 0 ----------------------------------------------- 2014-10-13 16:21:12.875411 UDP message received [331] bytes : SIP/2.0 200 OK Via: SIP/2.0/UDP 192.168.57.2:5061;branch=z9hG4bK-24239-1-0 From: sipp <sip:sipp@192.168.57.2:5061>;tag=24239SIPpTag001 To: sut <sip:service@192.168.57.2:5060>;tag=1 Call-ID: 1-24239@192.168.57.2 CSeq: 1 SUBSCRIBE Event: dialog Contact: <sip:127.0.1.1:5060;transport=UDP> Expires: 3600 Content-Length: 0 ----------------------------------------------- 2014-10-13 16:21:12.875532 UDP message received [2320] bytes : NOTIFY sip: private-ac@ SIP/2.0 Via: SIP/2.0/UDP 127.0.1.1:5060;branch=z9hG4bK-24235-1-2 Max-Forwards: 70 From: sipp <sip:sipp@192.168.57.2:5061>;tag=24239SIPpTag001 To: sut <sip:service@192.168.57.2:5060>;tag=1 Call-ID: 1-24239@192.168.57.2 CSeq: 10 NOTIFY Event: dialog Require: eventlist Subscription-State: active; expires=3599 Contact: <sip:private-ac@127.0.1.1:5060> Content-Type:multipart/related;boundary=UniqueBroadWorksBoundary;type="application/rlmi+xml" Content-Length: 1817 --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@127.0.1.1" version="0" fullState="true"> <resource uri="sip:anjana3@127.0.1.1"><name>6138 6138</name><instance id="UDTRRpGFJZ" state="active" cid="swncLz@broadworks"/></resource> <resource uri="sip:anjana2@127.0.1.1"><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@127.0.1.1"><dialog id="Y2FsbGhhbGYtNzUwNjE0Njk6MA==" direction="recipient"><state>confirmed</state><local><identity display="6138 6138">sip:anjana3@127.0.1.1</identity><identity display="6138 6138">tel:+16667786138;ext=6138</identity></local><remote><identity display="6137 6137">sip:6137@127.0.1.1;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@127.0.1.1"><dialog id="Y2FsbGhhbGYtNzUwNjE0NjU6MA==" direction="initiator"><state>confirmed</state><local><identity display="6137 6137">sip:anjana2@127.0.1.1</identity><identity display="6137 6137">tel:+16667786137;ext=6137</identity></local><remote><identity display="6138 6138">sip:6138@127.0.1.1;user=phone</identity></remote></dialog></dialog-info> --UniqueBroadWorksBoundary-- ----------------------------------------------- 2014-10-13 16:21:12.875694 UDP message sent (299 bytes): SIP/2.0 200 OK Via: SIP/2.0/UDP 127.0.1.1:5060;branch=z9hG4bK-24235-1-2 From: sipp <sip:sipp@192.168.57.2:5061>;tag=24239SIPpTag001 To: sut <sip:service@192.168.57.2:5060>;tag=1 Call-ID: 1-24239@192.168.57.2 CSeq: 10 NOTIFY Contact: <sip:192.168.57.2:5061;transport=UDP> Content-Length: 0
----------------------------------------------- 2014-10-13 16:21:12.875097 UDP message received [422] bytes : SUBSCRIBE sip:service@192.168.57.2:5060 SIP/2.0 Via: SIP/2.0/UDP 192.168.57.2:5061;branch=z9hG4bK-24239-1-0 From: sipp <sip:sipp@192.168.57.2:5061>;tag=24239SIPpTag001 To: sut <sip:service@192.168.57.2:5060> Call-ID: 1-24239@192.168.57.2 CSeq: 1 SUBSCRIBE Contact: sip:sipp@192.168.57.2:5061 Max-Forwards: 70 Event: presence Expires: 60 Accept: application/pidf+xml Allow-Events: presence Content-Length: 0 ----------------------------------------------- 2014-10-13 16:21:12.875362 UDP message sent (331 bytes): SIP/2.0 200 OK Via: SIP/2.0/UDP 192.168.57.2:5061;branch=z9hG4bK-24239-1-0 From: sipp <sip:sipp@192.168.57.2:5061>;tag=24239SIPpTag001 To: sut <sip:service@192.168.57.2:5060>;tag=1 Call-ID: 1-24239@192.168.57.2 CSeq: 1 SUBSCRIBE Event: dialog Contact: <sip:127.0.1.1:5060;transport=UDP> Expires: 3600 Content-Length: 0 ----------------------------------------------- 2014-10-13 16:21:12.875418 UDP message sent (2320 bytes): NOTIFY sip: private-ac@ SIP/2.0 Via: SIP/2.0/UDP 127.0.1.1:5060;branch=z9hG4bK-24235-1-2 Max-Forwards: 70 From: sipp <sip:sipp@192.168.57.2:5061>;tag=24239SIPpTag001 To: sut <sip:service@192.168.57.2:5060>;tag=1 Call-ID: 1-24239@192.168.57.2 CSeq: 10 NOTIFY Event: dialog Require: eventlist Subscription-State: active; expires=3599 Contact: <sip:private-ac@127.0.1.1:5060> Content-Type:multipart/related;boundary=UniqueBroadWorksBoundary;type="application/rlmi+xml" Content-Length: 1817 --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@127.0.1.1" version="0" fullState="true"> <resource uri="sip:anjana3@127.0.1.1"><name>6138 6138</name><instance id="UDTRRpGFJZ" state="active" cid="swncLz@broadworks"/></resource> <resource uri="sip:anjana2@127.0.1.1"><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@127.0.1.1"><dialog id="Y2FsbGhhbGYtNzUwNjE0Njk6MA==" direction="recipient"><state>confirmed</state><local><identity display="6138 6138">sip:anjana3@127.0.1.1</identity><identity display="6138 6138">tel:+16667786138;ext=6138</identity></local><remote><identity display="6137 6137">sip:6137@127.0.1.1;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@127.0.1.1"><dialog id="Y2FsbGhhbGYtNzUwNjE0NjU6MA==" direction="initiator"><state>confirmed</state><local><identity display="6137 6137">sip:anjana2@127.0.1.1</identity><identity display="6137 6137">tel:+16667786137;ext=6137</identity></local><remote><identity display="6138 6138">sip:6138@127.0.1.1;user=phone</identity></remote></dialog></dialog-info> --UniqueBroadWorksBoundary-- ----------------------------------------------- 2014-10-13 16:21:12.875751 UDP message received [299] bytes : SIP/2.0 200 OK Via: SIP/2.0/UDP 127.0.1.1:5060;branch=z9hG4bK-24235-1-2 From: sipp <sip:sipp@192.168.57.2:5061>;tag=24239SIPpTag001 To: sut <sip:service@192.168.57.2:5060>;tag=1 Call-ID: 1-24239@192.168.57.2 CSeq: 10 NOTIFY Contact: <sip:192.168.57.2:5061;transport=UDP> Content-Length: 0
sub_uac.xml
Description: XML document
sub.xml
Description: XML document
------------------------------------------------------------------------------ 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
