I tried your suggestion, Vanessa, but unfortunately I got the same result
("Malformed Packet").
Anyone have any other suggestions?
Jeffrey Wright
System Test Engineering Manager
Aztek Networks, Inc.
________________________________
From: Vanesa Tejada [mailto:[email protected]]
Sent: Wed 11/25/2009 3:19 PM
To: Jeff Wright
Cc: [email protected]
Subject: Re: [Sipp-users] Difficulty registering using authentication
[authentication [email protected] password=schmo]
Regards
On Wed, Nov 25, 2009 at 11:12 PM, Jeff Wright <[email protected]> wrote:
Hi Vanessa,
Thank you for your response. I looked at the documentation for SIPP
and in the Authentication section, it shows (example: [authentication
username=joe password=schmo]). This seems to be the same format I am using. I
do not see anywhwere in the CSV file that I would place a domain.
What am I missing here?
Thanks,
Jeffrey Wright
System Test Engineering Manager
Aztek Networks, Inc.
________________________________
From: Vanesa Tejada [mailto:[email protected]]
Sent: Wed 11/25/2009 1:48 PM
To: Jeff Wright
Cc: [email protected]
Subject: Re: [Sipp-users] Difficulty registering using authentication
You need to write the domain in csv file for username.
On Wed, Nov 25, 2009 at 9:04 PM, Jeff Wright
<[email protected]> wrote:
Greetings,
I was wondering if someone might be able to assist me in
understanding why I am having problems getting SIPP to register with a proxy,
using authentication. The initial REGISTER request from SIPP receives 401 from
the proxy (as expected); SIPP then re-sends a REGISTER request, but with only
partial authentication credentials. SIPP seems to be omitting some of the
required parameters. There is a telltale empty space and a leading comma that
occur before the nonce parameter in the second REGISTER. I think this is where
the realm, username and password would go. Anyway, the proxy ignores this
second REGISTER request. Wireshark tags it as a "Malformed packet".
Here is my command line invocation of SIPP:
sipp 172.22.20.80 -sf register_clients_sideA_w_auth.xml -inf
clients.csv -l 1 -i 172.22.20.151 -p 5063 -m 1
Here's my SIPP scenario file:
<?xml version="1.0" encoding="ISO-8859-1" ?>
<scenario name="register_clients_sideA_w_auth">
# SideA
<send>
<![CDATA[
REGISTER sip:[field1] SIP/2.0
Via: SIP/2.0/[transport]
[local_ip]:[local_port];branch=[branch]
From: <sip:[fiel...@[field1]>;tag=[call_number]
To: <sip:[fiel...@[field1]>
Call-ID: [call_id]
CSeq: [cseq] REGISTER
Contact: sip:[fiel...@[local_ip]:[local_port]
Event: message-summary
Max-Forwards: 70
Expires: 3600
User-Agent: SIPp/Linux
Content-Length: 0
]]>
</send>
<recv response="200" optional="true" next="1">
</recv>
<recv response="401" auth="true">
</recv>
<send>
<![CDATA[
REGISTER sip:[field1] SIP/2.0
Via: SIP/2.0/[transport]
[local_ip]:[local_port];branch=[branch]
From: <sip:[fiel...@[field1]>;tag=[call_number]
To: <sip:[fiel...@[field1]>
Call-ID: [call_id]
CSeq: [cseq] REGISTER
Contact: sip:[fiel...@[local_ip]:[local_port]
Event: message-summary
[field2]
Max-Forwards: 70
Expires: 3600
User-Agent: SIPp/Linux
Content-Length: 0
]]>
</send>
<recv response="200">
</recv>
<label id="1"\>
</scenario>
Here is the CSV file used as input:
SEQUENTIAL
sipp1;test.azteknetworks.net <http://test.azteknetworks.net/>
;[authentication username=sipp1 password=sipp1];sipp2;test.azteknetworks.net
<http://test.azteknetworks.net/> ;[authentication username=sipp2 password=sipp2]
And here is a trace of the attempted registration. You can see
in the last line of the last packet that Wireshark thinks this is a malformed
packet (and it appears as if Wireshark is right). Why is SIPP not properly
filling out the authentication information?
No. Time Source Destination
Protocol Info
75 11:11:54.742211 172.22.20.151 172.22.20.80
SIP Request: REGISTER sip:test.azteknetworks.net
<http://test.azteknetworks.net/>
Frame 75 (428 bytes on wire, 428 bytes captured)
Ethernet II, Src: Elitegro_7c:d4:89 (00:16:ec:7c:d4:89), Dst:
Giga-Byt_d2:63:ab (00:16:e6:d2:63:ab)
Internet Protocol, Src: 172.22.20.151 (172.22.20.151), Dst:
172.22.20.80 (172.22.20.80)
User Datagram Protocol, Src Port: 5063 (5063), Dst Port: sip
(5060)
Session Initiation Protocol
Request-Line: REGISTER sip:test.azteknetworks.net
<http://test.azteknetworks.net/> SIP/2.0
Message Header
Via: SIP/2.0/UDP
172.22.20.151:5063;branch=z9hG4bK-15651-1-0
From: <sip:[email protected]
<mailto:sip%[email protected]> >;tag=1
To: <sip:[email protected]
<mailto:sip%[email protected]> >
Call-ID: [email protected]
<mailto:[email protected]>
CSeq: 1 REGISTER
Contact: sip:[email protected]:5063
<http://sip:[email protected]:5063/>
Event: message-summary
Max-Forwards: 70
Expires: 3600
User-Agent: SIPp/Linux
Content-Length: 0
No. Time Source Destination
Protocol Info
78 11:11:54.749600 172.22.20.80 172.22.20.151
SIP Status: 401 Unauthorized (0 bindings)
Frame 78 (645 bytes on wire, 645 bytes captured)
Ethernet II, Src: Giga-Byt_d2:63:ab (00:16:e6:d2:63:ab), Dst:
Elitegro_7c:d4:89 (00:16:ec:7c:d4:89)
Internet Protocol, Src: 172.22.20.80 (172.22.20.80), Dst:
172.22.20.151 (172.22.20.151)
User Datagram Protocol, Src Port: sip (5060), Dst Port: 5063
(5063)
Session Initiation Protocol
Status-Line: SIP/2.0 401 Unauthorized
Message Header
From: <sip:[email protected]
<mailto:sip%[email protected]> >;tag=1
To: <sip:[email protected]
<mailto:sip%[email protected]>
>;tag=ae6f22e0-501416ac-13d8-50017-1f1-42187878-1f1
Call-ID: [email protected]
<mailto:[email protected]>
CSeq: 1 REGISTER
WWW-Authenticate: Digest realm="test.azteknetworks.net
<http://test.azteknetworks.net/>
",nonce="2d41b28f3dea718c50b9cf3bbda3a84c1259172080",algorithm=MD5
User-Agent: sipX/3.8.1 sipX/registry (Linux)
Accept-Language: en
Date: Wed, 25 Nov 2009 18:01:20 GMT
Allow:
INVITE,ACK,CANCEL,BYE,REFER,OPTIONS,REGISTER,SUBSCRIBE
Supported: gruu
Via: SIP/2.0/UDP
172.22.20.151:5063;branch=z9hG4bK-15651-1-0
Content-Length: 0
No. Time Source Destination
Protocol Info
79 11:11:54.750290 172.22.20.151 172.22.20.80
SIP Request: REGISTER sip:test.azteknetworks.net
<http://test.azteknetworks.net/> [Malformed Packet]
Frame 79 (554 bytes on wire, 554 bytes captured)
Ethernet II, Src: Elitegro_7c:d4:89 (00:16:ec:7c:d4:89), Dst:
Giga-Byt_d2:63:ab (00:16:e6:d2:63:ab)
Internet Protocol, Src: 172.22.20.151 (172.22.20.151), Dst:
172.22.20.80 (172.22.20.80)
User Datagram Protocol, Src Port: 5063 (5063), Dst Port: sip
(5060)
Session Initiation Protocol
Request-Line: REGISTER sip:test.azteknetworks.net
<http://test.azteknetworks.net/> SIP/2.0
Message Header
Via: SIP/2.0/UDP
172.22.20.151:5063;branch=z9hG4bK-15651-1-3
From: <sip:[email protected]
<mailto:sip%[email protected]> >;tag=1
To: <sip:[email protected]
<mailto:sip%[email protected]> >
Call-ID: [email protected]
<mailto:[email protected]>
CSeq: 2 REGISTER
Contact: sip:[email protected]:5063
<http://sip:[email protected]:5063/>
Event: message-summary
Authorization:
,nonce="2d41b28f3dea718c50b9cf3bbda3a84c1259172080",response="b1c5f73f5497011ae29f6e6a69b466cd",algorithm=MD5
[Malformed Packet: SIP]
Any assistance would be greatly appreciated.
Jeffrey Wright
System Test Engineering Manager
Aztek Networks, Inc.
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports
2008 30-Day
trial. Simplify your report design, integration and deployment
- and focus on
what you do best, core application coding. Discover what's new
with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users
--
Vanessa Tejada
--
Vanessa Tejada
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users
