Opened 12 years ago
Closed 12 years ago
#1614 closed enhancement (fixed)
Option to use new URI for To header in processing call redirection
Reported by: | nanang | Owned by: | bennylp |
---|---|---|---|
Priority: | normal | Milestone: | release-2.1 |
Component: | pjsip | Version: | trunk |
Keywords: | Cc: | ||
Backport to 1.x milestone: | Backported: | no |
Description
Currently call redirection will reuse the To header in the original redirected request as recommended by RFC3261 8.1.3.4. However, this may lead to this undesirable scenario:
- B calls A, connected successfully (leg 1)
- B calls C, C redirects to D, so B is connected to D (leg 2)
- B transfers A to D (with replaces), but A ends up ringing C (instead of D)
It happens because in leg 2, B sees that it talks with C (reused original To header) and when transferring the call, B will use the remote URI (i.e: To header) for the Refer-To header in call transfer request. Using new URI for To header in processing call redirection will avoid such scenario.
Thanks Peter Koletzki for the report.
Change History (1)
comment:1 Changed 12 years ago by nanang
- Resolution set to fixed
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
In 4347: