History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: XCL-110
Type: Improvement Improvement
Status: Open Open
Priority: Minor Minor
Assignee: Unassigned
Reporter: Dale R. Worley
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
sipXtapi: sipXcallLib

Application layer unable to specify response code when rejecting a call

Created: 2006-08-24 13:52   Updated: 2006-11-01 17:30
Component/s: sipXcallLib
Affects Version/s: None
Fix Version/s: None

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown


 Description  « Hide
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.


 All   Comments   Work Log   Change History      Sort Order:
There are no comments yet on this issue.