[Users] Cancel 183 progress branch (result of forked invite)

Vamsi Pottangi writes:

The problem which I'm facing is that when User2 doesn't answer the call or if rejects the call, Openser never sends CANCEL to SEMS, so the annoucement is being played continously to User1 and User1 is unaware of the remote party status. How can I configure the Openser script to handle such unanswered or call reject cases and send CANCEL to SEMS and inform User1 about the unanswered or cancel status?

openser is not sending cancel to sems, because it has to wait for that branch to give a final response. early media especially with forking is completely broken and should not be used. feel free to read about 200 messages on this topic from sip mailing list archives.

-- juha