From: "Bharrat, Shaun" <[EMAIL PROTECTED]> Can someone more familiar with this situation comment on whether it is fact the expected behavior for such a UAC with many AORs? Appreciate any info or links to prior email threads.
After my misconceptions of the situation were corrected, and thinking about the rules prescribed for processing REGISTERs in section 10.3, it's clear that it was clearly intended for this behavior to be permitted (though not required). Within the pseudo-dialogs (series of REGISTERs with the same Call-Id), REGISTERs are strictly ordered, and it's expected that for an one AOR/contact pair, its registrations will (normally) be only in one pseudo-dialog. But beyond that, each AOR/contact binding is maintained separately from all others, so there is no confusion. It's a bit weird that different REGISTERs with the same Call-Id will go to different UASs, but assuming that the registrars are conformant, they shouldn't be confused by the situation. (Any intermediate proxies must be routing the REGISTERs as out-of-dialog requests anyway, so they shouldn't be getting confused either.) Dale _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
