[asterisk-bugs] [Asterisk 0014993]: [patch] SIP Response 410 incorrectly mapped to Hangupcause 1, should be 22
Asterisk Bug Tracker
noreply at bugs.digium.com
Wed Apr 29 09:49:17 CDT 2009
The following issue has been UPDATED.
======================================================================
http://bugs.digium.com/view.php?id=14993
======================================================================
Reported By: BigJimmy
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 14993
Category: Channels/chan_sip/General
Reproducibility: always
Severity: minor
Priority: normal
Status: new
Asterisk Version: SVN
Regression: No
SVN Branch (only for SVN checkouts, not tarball releases): 1.4
SVN Revision (number only!): 191028
Request Review:
======================================================================
Date Submitted: 2009-04-29 09:48 CDT
Last Modified: 2009-04-29 09:49 CDT
======================================================================
Summary: [patch] SIP Response 410 incorrectly mapped to
Hangupcause 1, should be 22
Description:
According to documentation here:
http://www.cisco.com/en/US/docs/voice_ip_comm/pgw/9/dial_plan/guide/DP_App_B.html#wp1191041
and here:
http://www.voip-info.org/wiki/view/Asterisk+variable+hangupcause
SIP response 410 should map to ISDN Cause code 22. When going from ISDN to
SIP, this mapping is correct, however, when going from SIP to ISDN, it is
incorrectly mapped to cause code 1.
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
2009-04-29 09:49 BigJimmy Summary SIP Response 410
incorrectly mapped to Hangupcause 1, should be 22 => [patch] SIP Response 410
incorrectly mapped to Hangupcause 1, should be 22
======================================================================
More information about the asterisk-bugs
mailing list