[asterisk-bugs] [Asterisk 0016528]: [patch] Bridge application fails when both channels have a similar name

[Asterisk Bug Tracker]

The following issue has been ASSIGNED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16528 
====================================================================== 
Reported By:                telecos82
Assigned To:                jpeeler
====================================================================== 
Project:                    Asterisk
Issue ID:                   16528
Category:                   PBX/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
Asterisk Version:           SVN 
JIRA:                       SWP-618 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.0 
SVN Revision (number only!): 236843 
Request Review:              
====================================================================== 
Date Submitted:             2009-12-30 09:45 CST
Last Modified:              2010-01-06 13:05 CST
====================================================================== 
Summary:                    [patch] Bridge application fails when both channels
have a similar name
Description: 
I've found that when two channels have a similar name (one channel name
contains the other one), for example "IAX2/Corp-1" and "IAX2/Corp-16548",
the Bridge application fails giving the following warning message "Unable
to bridge channel IAX2/Corp-1 with itself".

It's due to the fact that we are comparing only the first 'n' characters
(with strncmp) of both strings where 'n' is the lesser of both string
lengths. The problem can be solved by comparing the whole strings with
strcmp instead of strncmp.
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-01-06 13:05 svnbot         Status                   ready for review =>
assigned
2010-01-06 13:05 svnbot         Assigned To               => jpeeler         
======================================================================