| Summary: | ASTERISK-07357: SIP URI parsing patch to release branch "breaks" interoperability | ||
| Reporter: | Daniel J. Laffin (dan42) | Labels: | |
| Date Opened: | 2006-07-18 15:11:33 | Date Closed: | 2006-07-28 13:55:53 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Channels/chan_sip/Interoperability |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | The patch in 1.2.7 from: http://bugs.digium.com/view.php?id=6409 which changed sip uri parsing in the middle of a release branch caused: http://bugs.digium.com/view.php?id=7208 The same problem exists in 1.2.10. In 1.2.6 this problem did not exist. ****** ADDITIONAL INFORMATION ****** In 1.2.6 the params before the @domain (ie sip:2028210181;npdi=yes@172.16.0.10:5060;dtg=SIP;user=phone SIP/2.0) would result in the number (2028210181) being looked up properly in the peers context or default. After upgrading past 1.2.6, asterisk searches for "s" in the "2028210181" domain. While I would agree sip uri parsing shouldnt really be changed within a release branch, sip uri parse has been changed and has cause me to not be able to upgrade past 1.2.6. | ||
| Comments: | By: Daniel J. Laffin (dan42) 2006-07-18 15:13:25 I believe more people will experience this as upgrades are made. I do not have the knowledge to backport the trunk patch to 1.2 nor does trunk compile on this machine at the moment, so I am unable to test if this has actually been fixed in trunk. By: Enrique Martinez (enmaca) 2006-07-18 19:36:26 Seems to be the same problem i reported in 0007535 By: istvankocsi (istvankocsi) 2006-07-27 05:39:03 Hello i have same issue in 1.2.10. I don't find solution in this topics, may be only i'm beginner in bug fixing. I read related topics too, Please tell me more information about fixing.Thank You very much. By: Joshua C. Colp (jcolp) 2006-07-28 13:55:51 Fixed in 1.2 and trunk, take THAT SIP parsing! Thanks. | ||