Closed ericgiannini closed 6 years ago
Here is code for call state:
Here is an example of call state:
Here is the state enumeration reference in the iOS documents that are 100% complete: https://developer.nexmo.com/sdk/stitch/ios/Classes/Call/State.html#/s:6Stitch4CallC5StateO7startedA2EmF
Here is the Voice API specs with a similar set of state changes: https://developer.nexmo.com/voice/voice-api/guides/handle-call-status
Thanks, @mariatechmaniac! I will update the .md
with your recommendations! ;)
@mheap Should busy
be in this list of states: https://developer.nexmo.com/voice/voice-api/guides/call-flow It is in this current list.
Thanks, @mariatechmaniac. I will update these asap.
Here is a reference to the JIRA DeVX board for this qs:
Here is a reference to the JIRA "Technical Spec":
Here is a reference to the peer reviewed Pull Request that has been merged into master:
Here is the list of requirements outlined by @mariatechmaniac: a small code snippet as to how the dev can retrieve it + a table with all and what each means + a disclaimer that their accuracy depends on the carrier. more specifically, sometimes what is really a busy state is relayed as rejected. + a note stating that they are valid for all 1:1 call combinations( ip ip , ip pstn etc) for group calls;
The only code you would show is the expected response after the end of the call. Showing how one can retrieve the call state, what it means and possibly explaining what those SIP codes mean.