Summary: | ASTERISK-16978: [patch] Translations from SIP 480 responses to cause codes, esp. Do Not Disturb | ||
Reporter: | Birger "WIMPy" Harzenetter (wimpy) | Labels: | |
Date Opened: | 2010-11-17 18:55:26.000-0600 | Date Closed: | 2012-02-23 10:54:21.000-0600 |
Priority: | Minor | Regression? | No |
Status: | Closed/Complete | Components: | Channels/chan_sip/Interoperability |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ( 0) dnd.patch | |
Description: | I found that a SIP UA responding 480 Do not disturb will cause Dail() to exit with HANGUPCAUSE=0x13, which isn't optimal. 480 is generally a Service unavailable where 0x13 doesn't fit at all. Cahnged to cause 0x2F generally, and cause 0x15 on Do Not Disturb. ****** ADDITIONAL INFORMATION ****** 480 Service unavailable and 480 Do not disturb are rather different things so I had to change hangup_sip2cause to take the text as well. | ||
Comments: | By: Leif Madsen (lmadsen) 2010-12-06 13:52:45.000-0600 This might be a good candidate for reviewboard. By: Joshua C. Colp (jcolp) 2012-02-23 10:54:21.977-0600 After looking at this issue, examining how things currently work, and the proposed change I believe this is no longer required. This information is accurately reflected across calling attempts now. By: Birger "WIMPy" Harzenetter (wimpy) 2012-02-23 13:01:17.443-0600 No, the issue is still the same in TRUNK. |