| Key: |
XCL-116
|
| Type: |
Bug
|
| Status: |
Open
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
Kwint
|
| Votes: |
0
|
| Watchers: |
1
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
|
| Component/s: |
sipXtapi
|
| Affects Version/s: |
None
|
| Fix Version/s: |
None
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
|
It looks to me that in sipxFireMediaEvent:
if (hCall != SIPX_CALL_NULL)
{
sipxCallSetMediaState(hCall, event, type) ;
}
has to be before if:
if (!bIgnored && !bDuplicateEvent)
because we want to notify user only after all processing is done...
Or, maybe I'm wrong ?
|
|
Description
|
It looks to me that in sipxFireMediaEvent:
if (hCall != SIPX_CALL_NULL)
{
sipxCallSetMediaState(hCall, event, type) ;
}
has to be before if:
if (!bIgnored && !bDuplicateEvent)
because we want to notify user only after all processing is done...
Or, maybe I'm wrong ? |
Show » |
| There are no comments yet on this issue.
|
|
sipxFireMediaEvent processing wrong order