Ticket #98 (closed defect: fixed)
Handle multiple final responses to transactions
| Reported by: | adigeo | Owned by: | adigeo |
|---|---|---|---|
| Priority: | major | Milestone: | 1st |
| Component: | SIP core | Version: | trunk |
| Keywords: | Cc: |
Description (last modified by adigeo) (diff)
When using unreliable transport like UDP, it is possible that we receive multiple answers. The transaction must return to the upper layer a single final winning response.
Change History
comment:1 Changed 2 years ago by adigeo
- Owner changed from support@ag-projects.com to adigeo
- Status changed from new to accepted
- Description modified (diff)
comment:4 Changed 23 months ago by adigeo
- Description modified (diff)
- Summary changed from Bug fixes to Handle multiple final responses to MESSAGE
comment:5 Changed 23 months ago by adigeo
- Version changed from 1.0.0 to trunk
- Milestone changed from Release 1.0.0 to Future release
comment:9 Changed 16 months ago by adigeo
This must be handled by PJSIP who now re-transmits the messages in case of no reply, only the wining code must be passed back to the application.
comment:10 Changed 15 months ago by adigeo
- Type changed from enhancement to defect
- Summary changed from Handle multiple final responses to MESSAGE to Handle multiple final responses to transactions
- Component changed from Middleware to SIP core
- Description modified (diff)
- Milestone changed from Nice to have to Next
comment:11 Changed 15 months ago by adigeo
- Status changed from accepted to closed
- Resolution set to fixed
The only possible situation to obtain multiple responses is when we have a locally generated 408 and an answer is received later form the SIP server. The only improvement possible is to sent 100 Trying from the server, this will lower the window of possible multiple replies.
Note: See
TracTickets for help on using
tickets.
