call: For a re-invite we need to handle the ACK
In case the remote will do a re-invite to verify that we are still aware of the call we need to handle >>#sessionAcked:dialog: This probably got introduced when I introduced the incoming call support that will send a 200 and receive the ACK. The incoming call will print a warning that session->session is not a valid state transition but nothing bad will happen.
This commit is contained in:
parent
91a745ba90
commit
4e38ef3ece
|
@ -212,4 +212,10 @@ will simply ignore everything but the first dialog.'>
|
|||
sdpResult [
|
||||
^sdp_result
|
||||
]
|
||||
|
||||
sessionAcked: anAck dialog: aDialog [
|
||||
"Do nothing. E.g. this could have been a re-invite that we 200 OKed
|
||||
and now get an ACK for our 200. In the future we might want to handle
|
||||
the re-invitation differently."
|
||||
]
|
||||
]
|
||||
|
|
Reference in New Issue