< Previous by Date | Date Index | Next by Date > |
Thread Index |
Current DUM behavior/callbacks after sending a REFER is:
Note: Not all endpoints send a Notify 100 if they
choose to accept a refer. I think we are potentially not handling the following scenario
correctly: First Notify from peer contains SipFrag/200 and
state=terminated. We will end up calling onReferRejected. Some other strange behavior is the difference in callbacks
in the following 2 scenarios: Note: Scenario 2 does not contain a Notify
SipFrag/100. Scenario 1:
Scenario 2:
Thoughts? Should we require that the peer send a
Notify/100 to have consistent behavior? To add consistency and fix the problem mentioned, we could call
onReferAccepted on the first Notify, regardless of the content of the Notify.
onReferRejected would only be called if a non 2xx response is received for the Refer
request itself. This would mean that both scenario 1 and 2 have the same
callbacks (onReferAccepted and onTerminated(ClientSub..)). Scott |