[Serusers] PRACK on forked response

[Michal Matyska]

Hi,

SER does not care about PRACK... it is just another within-dialog
request type, like BYE and many others.

I think you have incorrect routing script logic, where you fork even the
within dialog requests (using lookup_contacts) instead of just following
the record route set.

Michal


Stephen Paterson píše v St 09. 07. 2008 v 14:01 +0100:
> Hi all,
> 
> I'm using SER purely for testing purposes just now. Currently testing
> our handling of forked responses and hit upon the following situation:
> 
> My outgoing INVITE is forked to two UASs (also our own SIP endpoint),
> one of which sends a reliable 180 and the other an unreliable 180. The
> UAC sends a PRACK on the dialog ID of the reliable response but SER
> forwards this response on to both UASs the result being the UAS that
> sent the unreliable 180 responds to the PRACK with a 481 (the PRACK
> contains a To-tag that part defines a dialog unknown to that UAS). I
> confess I can't find anything describing this scenario in any RFC but
> it strikes me as incorrect behaviour on SERs part.
> 
> Does SER support PRACK? If not then no matter, I can live with it - it
> doesn't affect the outcome of any call. If it does, does anyone have
> any thoughts on this?
> 
> Cheers
> 
> Steve
> 
> Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes,
> MK1 1PT, UK
> Registration No: 1397386 (Wales)
>  
>  P Please consider the environment and don't print this e-mail unless
>                           you really need to
> 
> 
> _______________________________________________
> Serusers mailing list
> Serusers at lists.iptel.org
> http://lists.iptel.org/mailman/listinfo/serusers