Hi Mohammed, I don't know a great deal about the IMSBench extensions, I'm afraid, so I may not be much help - but I can take a look into this. Could you send the SIPp XML files that IMSBench is using (I don't think they were attached to your original email), and any information you can give about how you've configured IMSBench?
Thanks, Rob On 19 January 2014 10:17, Mohammad Isargar <[email protected]> wrote: > The following is the trace of the dialogs (important headers included) > between subs5000011 and P-CSCF. > At first, user registers successfully with Call-ID [email protected] , > then re-registers (due to re-registration scenario?) with Call-ID > [email protected]. At the end, user sends a BYE request with a "new" > Call-ID [email protected]. Would anyone please explain about the > purpose of this BYE request? As far as I know, client uses BYE to terminate > an "existing" dialog established by INVITE and it is destined for the > callee. But, here the Request-URI is set to P-CSCF address and the Call-ID > is a new one (I didn't find it in the dumps). And we see the error from > OpenIMSCore: "Status-Line: SIP/2.0 403 Forbidden - Originating subsequent > requests outside dialog not allowed". > > Finally I should mention that I have no subscriber named "service@..." or > "sipp@..." in HSS DB. > > Thanks for any help. > > 7329:User Datagram Protocol, Src Port: talon-disc (7011), Dst Port: > dsmeter-iatc (4060) > 7336:Session Initiation Protocol > 7337: Request-Line: REGISTER sip:open-ims.test SIP/2.0 > 7348: From: "subs5000011" <sip:[email protected]>;tag=13 > 7354: To: "subs5000011" <sip:[email protected]> > 7359: Call-ID: [email protected] > 7363: Contact: <sip:[email protected]:7011>;expires=1000000 > 7369: Expires: 1000000 > -- > 9793:User Datagram Protocol, Src Port: dsmeter-iatc (4060), Dst Port: > talon-disc (7011) > 9800:Session Initiation Protocol > 9801: Status-Line: SIP/2.0 401 Unauthorized - Challenging the UE > 9802: Status-Code: 401 > 9812: From: "subs5000011" <sip:[email protected]>;tag=13 > 9818: To: "subs5000011" > <sip:[email protected]>;tag=4c56058d6355f7ec7bd4f0a9441112ef-fc5d > 9824: Call-ID: [email protected] > > -- > 10077:User Datagram Protocol, Src Port: talon-disc (7011), Dst Port: > dsmeter-iatc (4060) > 10084:Session Initiation Protocol > 10085: Request-Line: REGISTER sip:open-ims.test SIP/2.0 > 10096: From: "subs5000011" <sip:[email protected]>;tag=13 > 10102: To: "subs5000011" <sip:[email protected]> > 10107: Call-ID: [email protected] > 10111: Contact: <sip:[email protected]:7011>;expires=1000000 > 10117: Expires: 1000000 > -- > 13139:User Datagram Protocol, Src Port: dsmeter-iatc (4060), Dst Port: > talon-disc (7011) > 13146:Session Initiation Protocol > 13147: Status-Line: SIP/2.0 200 OK - SAR succesful and registrar saved > 13148: Status-Code: 200 > 13161: From: "subs5000011" <sip:[email protected]>;tag=13 > 13167: To: "subs5000011" > <sip:[email protected]>;tag=4c56058d6355f7ec7bd4f0a9441112ef-625c > 13173: Call-ID: [email protected] > 13178: Contact: <sip:[email protected]:7011>;expires=3600 > -- > 24277:User Datagram Protocol, Src Port: talon-disc (7011), Dst Port: > dsmeter-iatc (4060) > 24284:Session Initiation Protocol > 24285: Request-Line: REGISTER sip:open-ims.test SIP/2.0 > 24296: From: "subs5000011" <sip:[email protected]>;tag=33 > 24302: To: "subs5000011" <sip:[email protected]> > 24307: Call-ID: [email protected] > 24311: Contact: <sip:[email protected]:7011>;expires=1000000 > 24317: Expires: 1000000 > -- > 24582:User Datagram Protocol, Src Port: dsmeter-iatc (4060), Dst Port: > talon-disc (7011) > 24589:Session Initiation Protocol > 24590: Status-Line: SIP/2.0 401 Unauthorized - Challenging the UE > 24591: Status-Code: 401 > 24601: From: "subs5000011" <sip:[email protected]>;tag=33 > 24607: To: "subs5000011" > <sip:[email protected]>;tag=4c56058d6355f7ec7bd4f0a9441112ef-3c3f > 24613: Call-ID: [email protected] > > 24677:User Datagram Protocol, Src Port: talon-disc (7011), Dst Port: > dsmeter-iatc (4060) > 24684:Session Initiation Protocol > 24685: Request-Line: REGISTER sip:open-ims.test SIP/2.0 > 24697: From: "subs5000011" <sip:[email protected]>;tag=33 > 24703: To: "subs5000011" <sip:[email protected]> > 24708: Call-ID: [email protected] > 24712: Contact: <sip:[email protected]:7011>;expires=1000000 > 24718: Expires: 1000000 > -- > 24987:User Datagram Protocol, Src Port: dsmeter-iatc (4060), Dst Port: > talon-disc (7011) > 24994:Session Initiation Protocol > 24995: Status-Line: SIP/2.0 200 OK - SAR succesful and registrar saved > 24996: Status-Code: 200 > 25009: From: "subs5000011" <sip:[email protected]>;tag=33 > 25015: To: "subs5000011" > <sip:[email protected]>;tag=4c56058d6355f7ec7bd4f0a9441112ef-aa78 > 25021: Call-ID: [email protected] > 25026: Contact: <sip:[email protected]:7011>;expires=3600 > -- > 57540:User Datagram Protocol, Src Port: talon-disc (7011), Dst Port: > dsmeter-iatc (4060) > 57547:Session Initiation Protocol > 57548: Request-Line: BYE sip:[email protected]:4060 SIP/2.0 > 57561: From: sipp <sip:[email protected]:7011>;tag=79 > 57568: To: sut <sip:[email protected]:4060> > 57574: Call-ID: [email protected] > 57578: Contact: <sip:open-ims.test:7011;transport=UDP> > > 57627:User Datagram Protocol, Src Port: dsmeter-iatc (4060), Dst Port: > talon-disc (7011) > 57634:Session Initiation Protocol > 57635: Status-Line: SIP/2.0 403 Forbidden - Originating subsequent > requests outside dialog not allowed > 57636: Status-Code: 403 > 57649: From: sipp <sip:[email protected]:7011>;tag=79 > 57656: To: sut > <sip:[email protected]:4060>;tag=bf17b8f52ba8a335422fa78ec37a5922.a875 > 57663: Call-ID: [email protected] > > > > > On Sat, Jan 18, 2014 at 5:03 PM, Mohammad Isargar <[email protected]> > wrote: >> >> Hi all >> >> I'm trying to use IMS Bench to test OpenIMSCore as SUT. >> >> All components are in the same machine. >> >> The manager execution ends with this message: "Over IHS detected ** STOP >> NOW ** ". >> >> I have plenty of the following errors in the SIPp error log: >> ... >> 2014-01-18 16:25:48.889: Call '[email protected]' - pick_user() >> returned NULL in pool 2. >> 2014-01-18 16:25:48.889: Call '[email protected]' - Action 'move_user' >> without a user assigned!. >> 2014-01-18 16:25:48.893: Call '[email protected]' - pick_user() >> returned NULL in pool 2. >> 2014-01-18 16:25:48.893: Call '[email protected]' - Action 'move_user' >> without a user assigned!. >> 2014-01-18 16:25:48.910: !! ERROR !! There should have been calls in SYNC >> !!. >> 2014-01-18 16:25:48.937: Call '[email protected]' - pick_user() >> returned NULL in pool 2. >> 2014-01-18 16:25:48.937: Call '[email protected]' - Action 'move_user' >> without a user assigned!. >> 2014-01-18 16:25:48.950: !! ERROR !! There should have been calls in SYNC >> !!. >> 2014-01-18 16:25:48.956: !! ERROR !! There should have been calls in SYNC >> !!. >> 2014-01-18 16:25:48.977: !! ERROR !! There should have been calls in SYNC >> !!. >> 2014-01-18 16:25:48.992: !! ERROR !! There should have been calls in SYNC >> !!. >> 2014-01-18 16:25:49.090: !! ERROR !! There should have been calls in SYNC >> !!. >> 2014-01-18 16:25:49.096: !! ERROR !! There should have been calls in SYNC >> !!. >> 2014-01-18 16:25:49.109: !! ERROR !! There should have been calls in SYNC >> !!. >> 2014-01-18 16:25:49.122: !! ERROR !! There should have been calls in SYNC >> !!. >> 2014-01-18 16:25:49.133: !! ERROR !! There should have been calls in SYNC >> !!. >> 2014-01-18 16:25:49.155: !! ERROR !! There should have been calls in SYNC >> !!. >> ... >> >> In the tshark dumps, I have this SIP error: >> "Originating subsequent requests outside dialog not allowed". >> which is on behalf of OpenIMSCore. Here are two samples of >> request/response SIP packets involved in this error: >> >> Session Initiation Protocol >> Request-Line: BYE sip:[email protected]:4060 SIP/2.0 >> Method: BYE >> Request-URI: sip:[email protected]:4060 >> Request-URI User Part: service >> Request-URI Host Part: 127.0.0.1 >> Request-URI Host Port: 4060 >> [Resent Packet: False] >> Message Header >> Via: SIP/2.0/UDP 127.0.0.1:7072;branch=z9hG4bK-20969-161--1 >> Transport: UDP >> Sent-by Address: 127.0.0.1 >> Sent-by port: 7072 >> Branch: z9hG4bK-20969-161--1 >> From: sipp <sip:[email protected]:7072>;tag=161 >> SIP Display info: sipp >> SIP from address: sip:[email protected]:7072 >> SIP from address User Part: sipp >> SIP from address Host Part: 127.0.0.1 >> SIP from address Host Port: 7072 >> SIP tag: 161 >> To: sut <sip:[email protected]:4060> >> SIP Display info: sut >> SIP to address: sip:[email protected]:4060 >> SIP to address User Part: service >> SIP to address Host Part: 127.0.0.1 >> SIP to address Host Port: 4060 >> Call-ID: [email protected] >> CSeq: 2 BYE >> Sequence Number: 2 >> Method: BYE >> Contact: <sip:127.0.0.1:7072;transport=UDP> >> Contact-URI: sip:127.0.0.1:7072;transport=UDP >> Contact-URI Host Part: 127.0.0.1 >> Contact-URI Host Port: 7072 >> Contact parameter: transport=UDP> >> Content-Length: 0 >> >> Session Initiation Protocol >> Status-Line: SIP/2.0 403 Forbidden - Originating subsequent requests >> outside dialog not allowed >> Status-Code: 403 >> [Resent Packet: False] >> [Request Frame: 1889] >> [Response Time (ms): 0] >> [Release Time (ms): 0] >> Message Header >> Via: SIP/2.0/UDP >> 127.0.0.1:7072;branch=z9hG4bK-20969-161--1;rport=7072 >> Transport: UDP >> Sent-by Address: 127.0.0.1 >> Sent-by port: 7072 >> Branch: z9hG4bK-20969-161--1 >> RPort: 7072 >> From: sipp <sip:[email protected]:7072>;tag=161 >> SIP Display info: sipp >> SIP from address: sip:[email protected]:7072 >> SIP from address User Part: sipp >> SIP from address Host Part: 127.0.0.1 >> SIP from address Host Port: 7072 >> SIP tag: 161 >> To: sut >> <sip:[email protected]:4060>;tag=bf17b8f52ba8a335422fa78ec37a5922.f9dc >> SIP Display info: sut >> SIP to address: sip:[email protected]:4060 >> SIP to address User Part: service >> SIP to address Host Part: 127.0.0.1 >> SIP to address Host Port: 4060 >> SIP tag: bf17b8f52ba8a335422fa78ec37a5922.f9dc >> Call-ID: [email protected] >> CSeq: 2 BYE >> Sequence Number: 2 >> Method: BYE >> Server: Sip EXpress router (2.1.0-dev1 OpenIMSCore (x86_64/linux)) >> Content-Length: 0 >> Warning: 392 0.0.0.0:4060 "Noisy feedback tells: pid=16999 >> req_src_ip=127.0.0.1 req_src_port=7072 in_uri=sip:[email protected]:4060 >> out_uri=sip:[email protected]:4060 via_cnt==1" >> >> Something that I don't understand here is that the address >> `sip:[email protected]:4060' been used as >> Request-URI of BYE message. But, my OpenIMSCore installation does not work >> with 127.0.0.1 as realm for >> SIP addresses. >> >> I don't know that the problem is with IMS Bench or OpenIMSCore. >> >> Also, the files manager.xml and ims_bench.xml have been attached. >> >> Thanks for any comment. > > > > ------------------------------------------------------------------------------ > CenturyLink Cloud: The Leader in Enterprise Cloud Services. > Learn Why More Businesses Are Choosing CenturyLink Cloud For > Critical Workloads, Development Environments & Everything In Between. > Get a Quote or Start a Free Trial Today. > http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk > _______________________________________________ > Sipp-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/sipp-users > ------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk _______________________________________________ Sipp-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sipp-users
