As far as I can see, the following is the current Jingle session flow if the recipient is busy:
Romeo Juliet
| |
| session-initiate |
|---------------------------->|
| ack |
|<----------------------------|
| session-info (busy) |
|<----------------------------|
| ack |
|---------------------------->|
| session-terminate |
|<----------------------------|
| ack |
|---------------------------->|
| |
That seems rather verbose!
Why not this?
Romeo Juliet
| |
| session-initiate |
|---------------------------->|
| error |
| (recipient-unavailable) |
|<----------------------------|
We should also define a Jingle-specific error message of <busy/> so that
the full error stanza would be as follows:
<iq from='[EMAIL PROTECTED]/balcony'
id='accept1'
to='[EMAIL PROTECTED]/orchard'
type='error'>
<error type='wait'>
<recipient-unavailable xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/>
<busy xmlns='http://www.xmpp.org/extensions/xep-0166.html#ns-errors'/>
</error>
</iq>
That flow maps much better to the 486 error in SIP:
http://www.apps.ietf.org/rfc/rfc3665.html#sec-3.9
Peter
--
Peter Saint-Andre
https://stpeter.im/
smime.p7s
Description: S/MIME Cryptographic Signature
