Improve Forking to get the Original Dialog

[GoogleCodeExporter]

When processing a response, if the ClientTransaction detects a modification of 
the to-tag, it will spawn a new Dialog. This could happen by example if Alice 
would Invite a forking proxy whom would 180ring Bob but finally 200Ok on Carol. 
In this scenario, Alice's application layer might have difficulty to find back 
its context because the applicationData provided on the initial Dialog had been 
lost since the dialog had been overriden by the stack.

Original issue reported on code.google.com by jean.deruelle on 8 Nov 2012 at 1:10

[GoogleCodeExporter]

This issue was updated by revision 001d9546b3e1.

(gi-repo)

When processing a response, if the ClientTransaction detects a modification of 
the to-tag, it will spawn a new Dialog. This could happen by example if Alice 
would Invite a forking proxy whom would 180ring Bob but finally 200Ok on Carol. 
In this scenario, Alice's application layer might have difficulty to find back 
its context because the applicationData provided on the initial Dialog had been 
lost since the dialog had been overriden by the stack.

git-svn-id: https://svn.java.net/svn/jsip~svn/trunk@2170 
8e71dc83-d81e-6649-80f2-80b843a9b2be
(cherry picked from commit ffd4f548b611ffe35a430fb0d991aa6276634951)

Original comment by jean.deruelle on 8 Nov 2012 at 1:16

[GoogleCodeExporter]

This issue was updated by revision 9577ae2a3c53.

When processing a response, if the ClientTransaction detects a modification of 
the to-tag, it will spawn a new Dialog. This could happen by example if Alice 
would Invite a forking proxy whom would 180ring Bob but finally 200Ok on Carol. 
In this scenario, Alice's application layer might have difficulty to find back 
its context because the applicationData provided on the initial Dialog had been 
lost since the dialog had been overriden by the stack.

___
Using DialogExt, add a mapping between the new forked dialog and the former 
know dialog

git-svn-id: https://svn.java.net/svn/jsip~svn/trunk@2171 
8e71dc83-d81e-6649-80f2-80b843a9b2be
(cherry picked from commit 17afeef36dcc90c33f9a0d1b6cfe6873c581b4e1)

Original comment by jean.deruelle on 8 Nov 2012 at 1:16

[GoogleCodeExporter]

This issue was updated by revision af9df6e17304.

Backport to TelScale Branch

When processing a response, if the ClientTransaction detects a modification of 
the to-tag, it will spawn a new Dialog. This could happen by example if Alice 
would Invite a forking proxy whom would 180ring Bob but finally 200Ok on Carol. 
In this scenario, Alice's application layer might have difficulty to find back 
its context because the applicationData provided on the initial Dialog had been 
lost since the dialog had been overriden by the stack.

git-svn-id: https://svn.java.net/svn/jsip~svn/trunk@2170 
8e71dc83-d81e-6649-80f2-80b843a9b2be
(cherry picked from commit ffd4f548b611ffe35a430fb0d991aa6276634951)
(cherry picked from commit 001d9546b3e1fca74a125769786a67ab1171476f)

Original comment by jean.deruelle on 8 Nov 2012 at 1:22

[GoogleCodeExporter]

This issue was updated by revision 36ec38ff806b.

Backport to TelScale branch

When processing a response, if the ClientTransaction detects a modification of 
the to-tag, it will spawn a new Dialog. This could happen by example if Alice 
would Invite a forking proxy whom would 180ring Bob but finally 200Ok on Carol. 
In this scenario, Alice's application layer might have difficulty to find back 
its context because the applicationData provided on the initial Dialog had been 
lost since the dialog had been overriden by the stack.

___
Using DialogExt, add a mapping between the new forked dialog and the former 
know dialog

git-svn-id: https://svn.java.net/svn/jsip~svn/trunk@2171 
8e71dc83-d81e-6649-80f2-80b843a9b2be
(cherry picked from commit 17afeef36dcc90c33f9a0d1b6cfe6873c581b4e1)
(cherry picked from commit 9577ae2a3c534371d42ff0d33b43c9ad8bb6660f)

Original comment by jean.deruelle on 8 Nov 2012 at 1:22

[GoogleCodeExporter]

Original comment by jean.deruelle on 8 Nov 2012 at 1:43

• Changed state: Fixed

[GoogleCodeExporter]

This issue was updated by revision af9df6e17304.

Backport to TelScale Branch

When processing a response, if the ClientTransaction detects a modification of 
the to-tag, it will spawn a new Dialog. This could happen by example if Alice 
would Invite a forking proxy whom would 180ring Bob but finally 200Ok on Carol. 
In this scenario, Alice's application layer might have difficulty to find back 
its context because the applicationData provided on the initial Dialog had been 
lost since the dialog had been overriden by the stack.

git-svn-id: https://svn.java.net/svn/jsip~svn/trunk@2170 
8e71dc83-d81e-6649-80f2-80b843a9b2be
(cherry picked from commit ffd4f548b611ffe35a430fb0d991aa6276634951)
(cherry picked from commit 001d9546b3e1fca74a125769786a67ab1171476f)

Original comment by jean.der...@telestax.com on 19 Aug 2014 at 4:59

[GoogleCodeExporter]

This issue was updated by revision 36ec38ff806b.

Backport to TelScale branch

When processing a response, if the ClientTransaction detects a modification of 
the to-tag, it will spawn a new Dialog. This could happen by example if Alice 
would Invite a forking proxy whom would 180ring Bob but finally 200Ok on Carol. 
In this scenario, Alice's application layer might have difficulty to find back 
its context because the applicationData provided on the initial Dialog had been 
lost since the dialog had been overriden by the stack.

___
Using DialogExt, add a mapping between the new forked dialog and the former 
know dialog

git-svn-id: https://svn.java.net/svn/jsip~svn/trunk@2171 
8e71dc83-d81e-6649-80f2-80b843a9b2be
(cherry picked from commit 17afeef36dcc90c33f9a0d1b6cfe6873c581b4e1)
(cherry picked from commit 9577ae2a3c534371d42ff0d33b43c9ad8bb6660f)

Original comment by jean.der...@telestax.com on 19 Aug 2014 at 4:59