| Summary: | ASTERISK-05836: [patch] Routing based on the Diversion SIP Header REASON code | ||
| Reporter: | mk (mklein) | Labels: | |
| Date Opened: | 2005-12-13 17:42:01.000-0600 | Date Closed: | 2006-01-26 08:36:09.000-0600 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Channels/chan_sip/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ( 0) 20051213__sip_diversion_reason.diff.txt | |
| Description: | SIP Headers: Diversion: <sip:1231230001@123.12.0.123>;reason=no-answer Diversion: <sip:1231230001@123.12.0.123>;reason=user-busy I need to be able to route on 'no-answer' or 'user-busy', accordingly. Scenario currently applies only to voicemail, but should be considered as a feature for other routing scenarios as well. ****** ADDITIONAL INFORMATION ****** RDNIS can be retrieved from this header, I think? | ||
| Comments: | By: Olle Johansson (oej) 2006-01-09 14:45:59.000-0600 Still on my todo-list. Not forgotten. By: Olle Johansson (oej) 2006-01-26 08:34:49.000-0600 Moving this discussion to issue 5484 where we can evaluate the best approach to create a generic solution. By: Olle Johansson (oej) 2006-01-26 08:35:54.000-0600 Moving to issue ASTERISK-5336 | ||