[SFtrack] Closed: (XCF-2670) call set up by sipXconfig does not get disconnected if the 'callee' disconnects the call
[
http://track.sipfoundry.org/browse/XCF-2670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chaitra Sharma closed XCF-2670.
-------------------------------
Assignee: (was: Chaitra Sharma)
This issue is resolved. Verified using the following build:
sipxproxy 3.11.5-013228 2008-08-07T14:21:08 oem-centos5
sipxconfig 3.11.5-013228 2008-08-07T14:43:41 oem-centos5
Verified the call flow. The sipXconfig sends a BYE when it receives a NOTIFY
with terminated state from the calling phone.
Hence closing this issue.
Thanks,
Chaitra
> call set up by sipXconfig does not get disconnected if the 'callee'
> disconnects the call
> ----------------------------------------------------------------------------------------
>
> Key: XCF-2670
> URL: http://track.sipfoundry.org/browse/XCF-2670
> Project: sipXconfig
> Issue Type: Bug
> Components: sip stack
> Affects Versions: 3.11.4
> Environment: sipxproxy 3.11.4-012989 2008-06-29T07:33:20 oem-centos5
> sipxconfig 3.11.4-012989 2008-06-29T07:49:59 oem-centos5
> Reporter: Chaitra Sharma
> Priority: Critical
> Fix For: 3.11.5
>
> Attachments: 0004-XCF-2670.patch, merged.xml, merged.xml,
> snapshot--URI_dialing.tar.gz
>
>
> Precondition:
> 1.Users 401, 402, 500 with phones are registered with sipxchange.
> Steps to reproduce:
> 1. Login to User portal as 500 and navigate to Phonebook page.
> 2. In the 'Number' field enter the phone number 402 and click on Call button.
> 3. User 500 starts ringing. Upon answering, 402 starts ringing.
> 4. Answer the call on 402. Call is established between 500(caller) and
> 402(callee).
> 5. Disconnect the call on 402.
> Expected Result:
> The call should get disconnected and both the phones should return to their
> idle state.
> Actual Result:
> The phone 402 returns to idle state. But TUI of 500 still appears connected
> to 402 untill End call key is pressed.
> Call id: 84b18d85-2489b347-f90619e4@xxxxxxxxxxxx
> Observation:
> 1. This issue does not occur if the 500(caller) disconnects the call.
> 2. This issue is also observed in the click_to_dial feature.
> Attachments:
> snapshot--URI_dialing.tar
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://track.sipfoundry.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
