Skip to content
This repository has been archived by the owner on May 6, 2020. It is now read-only.

Should be possible to set reason for a <hangup/> command #53

Open
benlangfeld opened this issue Mar 1, 2013 · 5 comments
Open

Should be possible to set reason for a <hangup/> command #53

benlangfeld opened this issue Mar 1, 2013 · 5 comments

Comments

@benlangfeld
Copy link
Member

SIP Reason header should be settable, probably indirectly via named reasons in the Rayo spec.

@benlangfeld
Copy link
Member Author

We have a few options here:

  1. Borrow SIP cause codes
  2. Borrow ISDN (Q.850) cause codes
  3. Borrow from Jingle (http://xmpp.org/extensions/xep-0166.html#def-reason).
  4. Make up our own enumerations and map them to SIP codes in implementations (informally document best-practice mappings) very much like we do for <reject/> etc. If we do this, what should the allowed values be?

@bklang
Copy link

bklang commented Mar 26, 2013

I'm personally inclined to stick close to SIP. FreeSWITCH has a mapping of ISDN to SIP hangup causes: http://wiki.freeswitch.org/wiki/Hangup_causes

@benlangfeld
Copy link
Member Author

If we stick close to SIP, should we migrate other cases where we do a loose mapping to also borrow from SIP (end events, etc)?

@benlangfeld
Copy link
Member Author

Missing use case

@emcgee
Copy link

emcgee commented Apr 12, 2013

The granularity of the SIP cause codes seems preferable at this point, although I personally think the XMPP codes being more generic would allow for greater future extensibility.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants