| Summary: | ASTERISK-16527: Asterisk handles 182 Queued event as 180 Ringing | ||
| Reporter: | shays (shays) | Labels: | |
| Date Opened: | 2010-08-09 06:10:11 | Date Closed: | 2011-06-07 14:05:01 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Channels/chan_sip/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ( 0) issue_182_queued_fulllog | |
| Description: | A calls B which is on line B respond with 182 Queued event to PBX PBX repsond to A with 180 Ringing event | ||
| Comments: | By: Olle Johansson (oej) 2010-08-11 07:48:15 Cool, I've never seen any device using 182 queued before. There's no such state in phone calls in any other protocol as I'm aware of, even though there's hints that SS7 has something similar used in emergency call handling (while using google). We need to figure out what to do in different states here. On sip2sip calls we could relay a 182 message, but what should we do with other channels? By: John Todd (jtodd) 2010-08-12 14:56:09 What is the standard response for Queued calls on the SS7 network? Ringing? Silence? How is ringback "wrong"? I'm not saying we're currently doing the right thing, but it's unclear on what we SHOULD be doing in this circumstance. By: Paul Belanger (pabelanger) 2010-09-04 14:28:59 ping! By: Leif Madsen (lmadsen) 2010-09-09 12:28:39 Suspended due to lack of feedback. | ||