Re: [Sipp-users] Presence, SUBSCRIBE-NOTIFY scenario incorrect 200 OK
Hi, I found my mistake. I was using regex for *header *inside the , I guess it can be used only in recv or send operation. However, I am not getting the regex correct. I'll try it. Thanks & Regards, Suryaveer Singh Chauhan On 18 October 2016 at 19:01, Suryaveer Chauhan wrote: > Hi Pavel, > > Thanks for this. This is working but I have a problem still. I am not able > to use regex. > > I tried hard-coding the values as below and that worked: > > > ** > * * > > * * > * * > * * > * * > * * > * * > ** > > But whenever I try any regex as simple as (.*) or even the ones given in > the manual I get a segmentation fault. > > This is what I tried: > > > >assign_to="1" /> > >assign_to="1" /> > >assign_to="host" /> > >search_in="hdr" header="Via: " check_it="false" assign_to="host" /> > > > > > > I am not able to figure out what's the problem. > > Thanks & Regards, > Suryaveer Singh Chauhan > > On 18 October 2016 at 04:16, sindelka wrote: > >> Hi Suryaveer, >> >> I understand that the reponse is sent to the via header address and the >> via on NOTIFY msg is of the presence server then why the response is >> sent to dispatcher? >> >> Your understanding is correct in terms what RFC3261 requires. However, >> SIPp does not follow these rules automatically - after all, it is a test >> tool, so you want to be able to test various "what if this is incorrect" >> scenarios. >> >> Therefore, SIPp sends all messages of a given call to the same IP address >> and port until you use the action to change that for that >> particular call. The initial values common for all calls are given at the >> command line. >> >> So before sending the first 200 to the NOTIFY, you have to use >> to change the peer's address and port. The manual recommends not to use >> too often because it is a resource-expensive operation, so I >> would do something like >> >> >> >> >> >> >> >> >> between receiving the NOTIFY (from which you may eventually extract the >> host and port using necessary) and sending the 200 to it. >> >> P. >> >> Dne 18.10.2016 v 7:22 Suryaveer Chauhan napsal(a): >> >> Hi, >> >> I have a simple presence test setup as below: >> >> Sipp --> opensips_dispatcher --> opensips_presence_server >> >> >> The SUBSCRIBE request and its 200 response pass thru dispatcher while the >> NOTIFY goes directly to the Sipp. >> >> The problem is, the 200 OK response to NOTIFY is sent to dispatcher >> instead of the presence server, the dispatcher rejects the response as it >> does not finds any transaction for it. >> >> I understand that the reponse is sent to the via header address and the >> via on NOTIFY msg is of the presence server then why the response is sent >> to dispatcher? >> >> Below is the command I used: >> >> *./sipp 172.17.0.6 -sf ../SubscribeNotify.xml -m 1 -i 172.17.0.5* >> >> and the used scenario file: >> >> >> - >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> - >> >> >> If required I can provide pcap too. >> Please help me understand the issue. >> >> Thanks & Regards, >> Suryaveer Singh Chauhan >> >> >> -- >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, SlashDot.org! http://sdm.link/slashdot >> >> >> >> ___ >> Sipp-users mailing >> listSipp-users@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/sipp-users >> >> >> >> >> -- >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, SlashDot.org! http://sdm.link/slashdot >> ___ >> Sipp-users mailing list >> Sipp-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/sipp-users >> >> > -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot___ Sipp-users mailing list Sipp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sipp-users
Re: [Sipp-users] Presence, SUBSCRIBE-NOTIFY scenario incorrect 200 OK
Hi Pavel, Thanks for this. This is working but I have a problem still. I am not able to use regex. I tried hard-coding the values as below and that worked: ** * * * * * * * * * * * * * * ** But whenever I try any regex as simple as (.*) or even the ones given in the manual I get a segmentation fault. This is what I tried: I am not able to figure out what's the problem. Thanks & Regards, Suryaveer Singh Chauhan On 18 October 2016 at 04:16, sindelka wrote: > Hi Suryaveer, > > I understand that the reponse is sent to the via header address and the > via on NOTIFY msg is of the presence server then why the response is sent > to dispatcher? > > Your understanding is correct in terms what RFC3261 requires. However, > SIPp does not follow these rules automatically - after all, it is a test > tool, so you want to be able to test various "what if this is incorrect" > scenarios. > > Therefore, SIPp sends all messages of a given call to the same IP address > and port until you use the action to change that for that > particular call. The initial values common for all calls are given at the > command line. > > So before sending the first 200 to the NOTIFY, you have to use > to change the peer's address and port. The manual recommends not to use > too often because it is a resource-expensive operation, so I > would do something like > > > > > > > > > between receiving the NOTIFY (from which you may eventually extract the > host and port using necessary) and sending the 200 to it. > > P. > > Dne 18.10.2016 v 7:22 Suryaveer Chauhan napsal(a): > > Hi, > > I have a simple presence test setup as below: > > Sipp --> opensips_dispatcher --> opensips_presence_server > > > The SUBSCRIBE request and its 200 response pass thru dispatcher while the > NOTIFY goes directly to the Sipp. > > The problem is, the 200 OK response to NOTIFY is sent to dispatcher > instead of the presence server, the dispatcher rejects the response as it > does not finds any transaction for it. > > I understand that the reponse is sent to the via header address and the > via on NOTIFY msg is of the presence server then why the response is sent > to dispatcher? > > Below is the command I used: > > *./sipp 172.17.0.6 -sf ../SubscribeNotify.xml -m 1 -i 172.17.0.5* > > and the used scenario file: > > > - > > > > > > > > > > > > > > > > > > - > > > If required I can provide pcap too. > Please help me understand the issue. > > Thanks & Regards, > Suryaveer Singh Chauhan > > > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, SlashDot.org! http://sdm.link/slashdot > > > > ___ > Sipp-users mailing > listSipp-users@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/sipp-users > > > > > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, SlashDot.org! http://sdm.link/slashdot > ___ > Sipp-users mailing list > Sipp-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/sipp-users > > -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot___ Sipp-users mailing list Sipp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sipp-users
Re: [Sipp-users] Presence, SUBSCRIBE-NOTIFY scenario incorrect 200 OK
Hi Suryaveer, I understand that the reponse is sent to the via header address and the via on |NOTIFY| msg is of the presence server then why the response is sent to dispatcher? Your understanding is correct in terms what RFC3261 requires. However, SIPp does not follow these rules automatically - after all, it is a test tool, so you want to be able to test various "what if this is incorrect" scenarios. Therefore, SIPp sends all messages of a given call to the same IP address and port until you use the || action to change that for that particular call. The initial values common for all calls are given at the command line. So before sending the first |200| to the |NOTIFY|, you have to use || to change the peer's address and port. The manual recommends not to use || too often because it is a resource-expensive operation, so I would do something like ||| || || |||| |||| || || | between receiving the |NOTIFY| (from which you may eventually extract the host and port using || necessary) and sending the |200| to it. P. Dne 18.10.2016 v 7:22 Suryaveer Chauhan napsal(a): Hi, I have a simple presence test setup as below: Sipp --> opensips_dispatcher --> opensips_presence_server The SUBSCRIBE request and its 200 response pass thru dispatcher while the NOTIFY goes directly to the Sipp. The problem is, the 200 OK response to NOTIFY is sent to dispatcher instead of the presence server, the dispatcher rejects the response as it does not finds any transaction for it. I understand that the reponse is sent to the via header address and the via on NOTIFY msg is of the presence server then why the response is sent to dispatcher? Below is the command I used: *./sipp 172.17.0.6 -sf ../SubscribeNotify.xml -m 1 -i 172.17.0.5* * * and the used scenario file: * * - - If required I can provide pcap too. Please help me understand the issue. Thanks & Regards, Suryaveer Singh Chauhan -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot ___ Sipp-users mailing list Sipp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sipp-users -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot___ Sipp-users mailing list Sipp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sipp-users
[Sipp-users] Presence, SUBSCRIBE-NOTIFY scenario incorrect 200 OK
Hi, I have a simple presence test setup as below: Sipp --> opensips_dispatcher --> opensips_presence_server The SUBSCRIBE request and its 200 response pass thru dispatcher while the NOTIFY goes directly to the Sipp. The problem is, the 200 OK response to NOTIFY is sent to dispatcher instead of the presence server, the dispatcher rejects the response as it does not finds any transaction for it. I understand that the reponse is sent to the via header address and the via on NOTIFY msg is of the presence server then why the response is sent to dispatcher? Below is the command I used: *./sipp 172.17.0.6 -sf ../SubscribeNotify.xml -m 1 -i 172.17.0.5* and the used scenario file: - - If required I can provide pcap too. Please help me understand the issue. Thanks & Regards, Suryaveer Singh Chauhan -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot___ Sipp-users mailing list Sipp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sipp-users
