Hi!
FYI: On serdev is an interesting thread:
http://lists.iptel.org/pipermail/serdev/2007-July/010507.html
The problem is basically that it is not possible to distinguish between
non-2xx ACK (1) and 2xx ACK (2) in stateless mode if the client uses a
pre-loaded route.
(1) for example openser as stateless loadbalancer and the registrar
sends 407 which causes an ACK
(2) ACK after INVITE-200 ok
Both have Route header and both have totag.
This might cause wrong routing of ACK as (1) requires to use dispatcher
based routing again but (2) is just loose_routed and forwarded.
regards
klaus
_______________________________________________
Devel mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/devel