Hi, first of all I'm sorry for breaking the thread started by Saul with subject "Some questions before starting a b2bua project", I'm subscribed to this maillist right now. About the desired transparent B2BUA implementation, I would like to comment a bug I've found in other, theorically, transparent B2BUA's: The problem occurs when a request arrives to the B2BUA (forming leg_A), the B2BUA initiates a new request to a proxy as destination (forming leg_B), and that proxy does parallel forking, so B2BUA receives several early-dialog (different To_tag and different SDP in case of 183) in leg_B. For this to work, leg_A should act as a different UAS for each UAS detected in leg_B, this involves that for each early-dialog in leg_B, leg_A should send the same reply with different To_tag (respecting the SDP since it's transparent). So finally there would be so many different To_tags in leg_A as different To_tag received in leg_B. If all the replies in leg_A share the same To_tag, but contain different SDP, then we are breaking RFC 3261, since the SDP cannot be changed during an early-dialog. I refer to the thread I opened reporting the bug in other maillist: http://lists.iptel.org/pipermail/semsdev/2008-November/003309.html So the question is: do you think that the required correct behaviour would be feasible with PjSIP? Thanks a lot. -- I?aki Baz Castillo
