
| Key: |
XCL-110
|
| Type: |
Improvement
|
| Status: |
Open
|
| Priority: |
Minor
|
| Assignee: |
Unassigned
|
| Reporter: |
Dale R. Worley
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
|
| Component/s: |
sipXcallLib
|
| Affects Version/s: |
None
|
| Fix Version/s: |
None
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
|
The application layer of a UA should be able to specify the SIP response code (404, 486, etc.) to send back to the caller when rejecting a call. But neither interface for doing so (sipxCallReject and CallManager::rejectConnection) provides this capabillity. (sipxCallReject has arguments for this purpose, but they are ignored.)
The call-reject request is bucket-brigaded through this sequence of operations:
sipXcallReject
CallManager::rejectConnection
CP_REJECT_CONNECTION message to CallManager
CP_REJECT_CONNECTION message to CpCall
CpPeerCall::handleRejectConnection
SipConnection::reject
But SipConnection::reject determines the response code to use based entirely on the current state of the call; the application can provide no information.
|
|
Description
|
The application layer of a UA should be able to specify the SIP response code (404, 486, etc.) to send back to the caller when rejecting a call. But neither interface for doing so (sipxCallReject and CallManager::rejectConnection) provides this capabillity. (sipxCallReject has arguments for this purpose, but they are ignored.)
The call-reject request is bucket-brigaded through this sequence of operations:
sipXcallReject
CallManager::rejectConnection
CP_REJECT_CONNECTION message to CallManager
CP_REJECT_CONNECTION message to CpCall
CpPeerCall::handleRejectConnection
SipConnection::reject
But SipConnection::reject determines the response code to use based entirely on the current state of the call; the application can provide no information.
|
Show » |
| There are no comments yet on this issue.
|
|