Hi, Your Call-ID is "1-17...@127.0.0.1", where a call-id in sipp in general is composed of "'number of call'-'processid'@'local_ip'". So, IMHO, sipp takes the wrong, the loopback, IP-address for the variable [local_ip].
Try sipp again and use the "-i"-parameter to explicitely define the IP adress which should be used. br Michael PS: as far as I know, sipp uses the same function to detect the "primary" IP-address like the linux-command "hostname -i". So, when "hostname -i" results in "127.0.0.1", you will get the mentioned problem- mustafa rifaee wrote: > Hello all; > I am using SIPp 3.1 with Open IMS Core, but when i send registration the > registration done successfully but the IMS core does not send OK message > back to SIPp. > > *Aborting call on unexpected message for Call-ID '1-17420 at 127.0.0.1 > <https://lists.berlios.de/mailman/listinfo/openimscore-users>': while > > > expecting '200' response, received 'SIP/2.0 401 Unauthorized - Challenging > the UE* > > > > Please Help me. > Best Regards > Rifaee > --------------. > registration scenario:- > <?xml version="1.0" encoding="ISO-8859-1" ?> > <!DOCTYPE scenario SYSTEM "sipp.dtd"> > <scenario name="reg_alice"> > <send retrans="500"> > <![CDATA[ > REGISTER sip:open-ims.test SIP/2.0 > Via: SIP/2.0/[transport] [local_ip]:[local_port] > Route: <sip:pcscf.open-ims.test:4060; > lr> > Max-Forwards: 70 > From: "alice" <sip:al...@open-ims.test:4060> > To: "alice" <sip:al...@open-ims.test:4060> > P-Access-Network-Info: 3GPP-UTRAN-TDD;utran-cell-id-3gpp=C359A3913B20E > Call-ID: [call_id] > Contact: <sip:al...@[local_ip]:[local_port]>;transport=[transport] > Content-Length: 0 > Supported: path > Expires: 300 > CSeq: 1 REGISTER > User-Agent: Sipp v1.1-TLS, version 20061124 > ]]> > </send> > <recv response="401" auth="true" rtd="true"> > <action> > <ereg regexp=".*" search_in="hdr" header="Service-Route" assign_to="1" /> > </action> > </recv> > <send retrans="500"> > <![CDATA[ > REGISTER sip:open-ims.test SIP/2.0 > Via: SIP/2.0/[transport] [local_ip]:[local_port] > Route: <sip:pcscf.open-ims.test:4060;lr> > Max-Forwards: 70 > From: "alice" <sip:al...@open-ims.test> > To: "alice" <sip:al...@open-ims.test> > P-Access-Network-Info: 3GPP-UTRAN-TDD;utran-cell-id-3gpp=C359A3913B20E > Call-ID:[call_id] > CSeq: 2 REGISTER > Contact: <sip:al...@[local_ip]:[local_port]> > Expires: 300 > Content-Length: 0 > [authentication username=al...@open-ims.test password=alice] > Supported: path > User-Agent: Sipp v1.1-TLS, version 20061124 > ]]> > </send> > <recv response="200"> > </recv> > </scenario> > > > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > Throughout its 18-year history, RSA Conference consistently attracts the > world's best and brightest in the field, creating opportunities for Conference > attendees to learn about information security's most important issues through > interactions with peers, luminaries and emerging and established companies. > http://p.sf.net/sfu/rsaconf-dev2dev > > > ------------------------------------------------------------------------ > > _______________________________________________ > Sipp-users mailing list > Sipp-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/sipp-users ------------------------------------------------------------------------------ Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev _______________________________________________ Sipp-users mailing list Sipp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sipp-users
